SupportModeler for PDS Admin Guide

SupportModeler™ for PDS™ Admin Guide

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

1

SupportModeler™ for PDS™ Admin Guide Copyright

Copyright Copyright © 1998-2003 Intergraph Corporation. All Rights Reserved. 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.

Trademarks SupportModeler and SupportManager are trademarks of Pelican Forge Software Corporation. Intergraph, the Intergraph logo, SmartSketch, FrameWorks, SmartPlant, and INtools are registered trademarks and PDS is a trademark of Intergraph Corporation. Microsoft and Windows are registered trademarks of Microsoft Corporation. ISOGEN is a registered trademark of Alias Limited. Other brands and product names are trademarks of their respective owners.

Warranties and Liabilities All warranties given by Intergraph Corporation about equipment or software are set forth in your purchase contract, and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or amendment of such warranties. Intergraph believes the information in this publication is accurate as of its publication date. The information and the software discussed in this document are subject to change without notice and are subject to applicable technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document. The software discussed in this document is furnished under a license and may be used or copied only in accordance with the terms of this license. No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied by Intergraph or its affiliated companies. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.

2

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Restricted Rights Legend

Restricted Rights Legend Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) of the Contractor Rights in Technical Data clause at DFARS 252.227-7013, subparagraph (b) of the Rights in Computer Software or Computer Software Documentation clause at DFARS 252.227-7014, subparagraphs (b)(1) and (2) of the License clause at DFARS 252.227-7015, or subparagraphs (c) (1) and (2) of Commercial Computer Software---Restricted Rights at 48 CFR 52.22719, as applicable. Unpublished---rights reserved under the copyright laws of the United States. Intergraph Corporation Huntsville, Alabama 35894-0001

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

3

SupportModeler™ for PDS™ Admin Guide Admin Guide Purpose

Admin Guide Purpose This guide explains how to create and manage pipe support projects using SupportModeler, Version 7.2.3. This guide is intended for use with Intergraph PDS plant design projects.

Installing the Software System Requirements Make sure that your system has the following hardware and software before installing SupportModeler: •

Pentium III 500Mhz

•

128 MB memory minimum, 256 recommended

•

50 MB hard disk space

•

MS Windows NT 4.0 or higher, or Windows 2000

•

MicroStation SE or J compatible with your version of PDS

•

Microsoft Access drivers installed

SupportModeler does not require PDS installed on the workstation. However, SupportModeler interfaces with Intergraph Plant Design System (PDS™) projects created with version 6.4.1 or higher.

Installing SupportModeler 1. If you have a previous version of SupportModeler, preserve any customizations you have made to the delivered libraries or settings files. Customized files should always be stored securely outside the delivered software directory. 2. Uninstall any previous versions of SupportModeler. 3. Run the self-extracting installation file to install SupportModeler. This is a self-extracting zip-file which automatically runs the setup.exe program it contains. Follow the prompts.

4

•

Use "Full Install" on machines you wish to carry out customization and project set up

•

Use "Client Install" for user workstations. Client installation installs all executables but no libraries or seed files. This reduces the proliferation of libraries and seed files on workstation machines.

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Software Delivery Directory Structure 4. Contact Intergraph Corporation to obtain and install proper licensing for the software. 5. Test SupportModeler to make sure that the software is installed and that it can access the required licenses.

Software Delivery Directory Structure During installation, the software is delivered to your machine’s C:\Program Files\SupMod\directory with the sub-directories shown in the diagram below. The software delivery directory contains the software executables, documentation, a sample tutorial project, and delivered versions of all the project setup files and libraries.

C:\Program Files\SupMod\Docs - contains user, tutorial and administration guides C:\Program Files\SupMod\Mdlapps - contains the executable software programs C:\Program Files\SupMod\Mdlapps\config -configuration files that are used when starting SupportModeler C:\Program Files\SupMod\Lib - the delivered libraries C:\Program Files\SupMod\Seeds - delivered seed files and settings files C:\Program Files\SupMod\Tutorial_PDS - tutorial project - copy to your machine's \Temp directory before using.

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

5

SupportModeler™ for PDS™ Admin Guide Installing the Software

Upgrading a Production Project to Version 7.2.3 Version 7.2.3 of SupportModeler uses a significantly different data storage method than version 7.1. Version 7.1 used JSpace object models for attribute storage while more recent versions use a relational database. Because of this, we highly recommended completing any existing projects using your current version of SupportModeler. For conversion of version 7.1 projects, please contact Pelican Forge for assistance.

Restoring Customizations to the SUPPORT definition Version 7.2.3 of SupportModeler uses significantly different library definitions than version 7.1. Version 7.2.3 uses straightforward script files to define both vendor libraries as well as the SUPPORT definition as opposed to the older JSpace Libraries. The SUPPORT class has been replaced by a support item file --SUPPORT.ITM - found in the ...\lib\sm_core_user\ directory. This is the file that you should save away in an enterprise location and customize to suit your requirements. Presently, there is no automated function to upgrade an old SM_core_user.lib. Changes made to the SUPPORT class of previous versions must be manually made to the SUPPORT.ITM file. Please see the SupportModeler Library Customization Guide for information on how to do this.

Restoring Customizations to the Vendor Databases As recommended, any customized vendor databases (for example customized versions of SM_Anvil.mdb or SM_Utility.mdb) should have been stored in a secure location. Follow this procedure for each customized library to restore any customizations.

➤ To restore your customizations to the vendor databases 1. Open the newly delivered database in Microsoft Access. 2. Delete the tables that correspond to the ones that have been customized. 3. From the menu bar, choose File>Get External Data>Import to import the tables (that were customized from the user-customized database) into the delivered database. 4. Browse and select the database that contains the tables you want to import. 5. From the list of tables that is presented, select the table(s) you wish to import.

6

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Retaining Customizations to the Vendor JSpace Libraries 6. Save the file and exit.

Retaining Customizations to the Vendor JSpace Libraries Version 7.2.3 of SupportModeler uses significantly different library definitions than version 7.1. Version 7.2.3 uses straightforward script files to define vendor libraries. Presently, there is no automated function to upgrade old vendor libraries. Changes made by the user to the preVersion 7.2.3 vendor libraries must be manually made to the new libraries. Please see section for information on how to do this. Any custom library that Pelican Forge has created for customers can be upgraded to the new format by contacting Pelican Forge.

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

7

SupportModeler™ for PDS™ Admin Guide Preparing for Project Creation

Preparing for Project Creation This section describes how to prepare for creating your first production SupportModeler project.

✍ This preparation and the associated company-wide changes are usually

made while setting up the first production project. The process is usually iterative - make changes, copy them to the project, test them in the project, make required changes and copy them back to the master lib and seeds directories.

✍ If you wish to have detailed on-site assistance with this process, Pelican Forge offers a QuickStart customization service to setup and configure your first project. Please contact Pelican Forge for prices and available scheduling.

Create Server Directories for Master Libraries and Seeds Most companies want to centralize their seed and border files, settings files, and libraries on a central server that is accessible to all client machines. Following is the suggested setup of a master reference directory for SupportModeler seeds and libraries. Use whatever directory names make sense to you. All SupportModeler projects would use the files from this location. This directory structure should be backed up regularly.

✍ This directory structure is optional as projects can use the seeds and

libraries delivered in C:\Program Files\SupMod\. A separate serverbased directory is recommended for organizing and standardizing your company's libraries and seed files, and to keep them in a backed-up location outside of the delivered software directories.

8

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Make Company-Wide Changes to Project Setup Files ➤ To create a Master Seeds and Libs directory on your server 1. On your server, create a top level directory to store the master seeds and libraries. For example, create a folder called \SupModMaster or \SuptRef. 2. Create the Seeds, CoreLibs, VendorLibs and MyLibs sub-directories. The names are your choice. 3. From the delivered software directory, C:\Program Files\SupMod\Seeds\ copy all files into your new master \Seeds\ directory. 4. From the delivered software directory C:\Program Files\SupMod\Lib\, copy folders SM_CORE and SM_CORE_USER into your new CoreLibs directory. 5. From the delivered software directory C:\Program Files\SupMod\Lib\, copy all remaining folders, including the \Bmp sub-directory and all of the files it contains, into your new VendorLibs directory. This will take a few minutes as there are many large files in these directories. 6. If you have had custom libraries of your company support standards developed by Pelican Forge, or developed new libraries yourself, move or copy them into your new MyLibs directory.

Make Company-Wide Changes to Project Setup Files Make company-wide changes to project setup files. Some settings will be used by all SupportModeler projects and would be done in the master libraries and seeds. Files such as model seeds, drawing seeds and borders, SM_DRW.DAT, SM_PDS.DAT, and Core Libraries often get companywide changes. After you create individual projects, you can then make project-specific changes to the project-specific files.

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

9

SupportModeler™ for PDS™ Admin Guide Preparing for Project Creation Model Seed Files Model seed files define the working units of the SM project. Sample seed files are delivered with SM in the C:\Program Files\SupMod\Seeds\ directory, with the following working units: Seed File Name Seed_inches Seed_feet (only used with PlantSpace projects) Seed_meters Seed_millimeters Seed_feet_PDS (Only used with PDS projects. Automatically copied and renamed to Seed_feet during project creation)

Name (in SM Setup)

Master Units

Sub Units

Sub/ Master

UOR/ Sub

Inches Feet

In '

tn "

10 12

1000 25400

Meters Millimeters Feet

M Mm '

mm mm "

1000 1 12

80 1000 2032

W The working units must match between SM and PDS. If your PDS project uses one of these standards, just specify the appropriate design file master units name during SM project setup If your PDS project uses different working units, you must edit the SM seed file using MicroStation and set it up to match your PDS project. For feet projects in PDS, make sure to edit the Seed_feet_PDS file. When a PDS project is created, this file is copied to the project's \Seeds directory and renamed to seed_feet. should not edit the delivered seed files directly as any changes you W You make would be overwritten if SupportModeler were reinstalled. Copy the files out to a secure location before making changes.

Drawing Seed and Border Files SupportModeler drawing seed and border files are very similar in concept to seed files used by many other applications. You set up the seed files, annotation text nodes, and other seed file features for the project as a whole and the designers then choose which seed file and which drawing views to use for each support, as explained in the SupportModeler User Guide for PDS. The drawing seed files work together with the SM_DRW.DAT drawing settings file. Sample seed and border files are delivered with SM in the C:\Program Files\SupMod\Seeds\ directory.

10

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Make Company-Wide Changes to Project Setup Files .For detailed information, refer to the section “Customizing the Fabrication Drawings” on page 53 of this guide.

Drawing Settings File SM_DRW.DAT This simple ASCII file controls what annotation is written onto the drawings, and controls the symbology of graphics and annotation, sets project-specific configuration variables, and defines the list of available drawing seed files for the project. The file itself contains detailed comments explaining how to use it. A sample SM_DRW.DAT file is delivered with SM in the C:\Program Files\SupMod\Seeds\ directory. The various sections of the file are summarized as follows: •

SYMBOLOGY - defines the line weight, style, color and level to use for the support and reference graphics in the fabrication drawings.

•

TEXT_NODES - assigns specific project and drawing properties from the supports to specific, user-defined text nodes in the drawing seed file. Allows the use of expressions as well as property names.

•

CONFIGURATION_VARIABLES - allows you to specify projectspecific configuration variables to control drawing behavior and format. The newly delivered SM_DRW.DAT file lists all of the available configuration variables along with extensive comments on how to use them.

For more information, refer to the section “Customizing the Fabrication Drawings” on page 53 of this guide and to the delivered example SM_DRW.DAT file.

PDS Correspondence File SM_PDS.DAT This simple ASCII file controls what data is transferred between PDS and SupportModeler. The file itself contains detailed comments explaining how to use it. A sample SM_PDS.DAT file is delivered with SM in the C:\Program Files\SupMod\Seeds\ directory. The various sections of the file are summarized as follows:

June 20, 2003

•

PIPING_DATA - defines which attributes of the PDS pipe segment from pdtable_12 get transferred into the support when you connect to pipe.

•

PIPING_DATA_WITH_UNITS - exactly the same but is only used for PDS pressures and temperatures.

•

SUPPORT_DATA - defines which support properties get transferred into pdtable_80 during Update PDS.

•

PROJECT_TABLES - primarily for case-sensitivity issues with SQL Server. Most people don't need to change this. You may need to add or remove the FORWARD_SLASH from the pdtable_113 entry to

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

11

SupportModeler™ for PDS™ Admin Guide Preparing for Project Creation make to the paths for SupportModeler models match the format of other PDS models. •

COLUMN_NAMES - primarily for case-sensitivity issues with SQL Server.

•

SYMBOLOGY - defines the symbology to use when SM creates PDS logical supports during Update PDS. This should match the symbology that PDS expects for logical supports.

•

AREA_DEFAULTS and MODEL_DEFAULTS - define which default values should be set in pdtable_112 and pdtable_113 when SupportModeler creates areas and models in the PDS database. Most people don't need to change these.

•

SUPPORT_OBJECTS and COMPONENTS_&_ASSEMBLIES define which properties should be available during a Design Review session.

•

PATH_CONVERSION - defines optional text substitutions to help SupportModeler find PDS models using the model paths from pdtable_113.

For details on the uses of SM_PDS.DAT file, refer to the section “Using SM_PDS.DAT to Configure the PDS Interface” on page 35 of this guide and to the delivered example SM_PDS.DAT file.

Core Libraries Each project uses a specific set of core libraries named SM_CORE and SM_CORE_USER. The delivered libraries (represented as directories) are located in C:\Program Files\SupMod\Lib\. These libraries contain simple script files (***.itm) that can be edited with any text editor. The most important file for administrators is the SUPPORT.ITM file located in the SM_CORE_USER folder. It is a very important, very customizable definition that affects several aspects of SupportModeler. It is used:

12

•

To create the support graphic and object (Yellow or Grey cone)

•

To determine the contents of the Active Parameters Dialog (Must have Prompt entries in the SUPPORT file)

•

As a source for property information for border annotation (Remember the SM_DRW.DAT file and text nodes in the drawing seed files!)

•

As a source for property information for PDS Logical Support generation and subsequent ISO generation (Remember the SUPPORT_DATA section of the SM_PDS.DAT file that controls

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Make Company-Wide Changes to Vendor Libraries. what properties of the support get written into pdtable_80 during Update PDS.) •

As a Receiver for Connect to Pipe Properties (Remember the PIPING_DATA section of the SM_PDS.DAT file that controls what properties of pdtable_12 get written into the support during connect to pipe)

•

To define the automatic format for the Support ID using the SUP_ID_FORMAT property.

Make Company-Wide Changes to Vendor Libraries. If you plan to make changes to the delivered libraries, or get a custom library created for your company by Pelican Forge, you would generally do this before starting modeling in a project. It is a difficult manual process to implement library changes retroactively to already-modeled components. For detailed information on library creation and customization, refer to the SupportModeler Library Customization Guide. For minor changes and customizations, we recommend that you take the Administration and Customization Training course. For creating new libraries or making extensive changes, we would very strongly recommend that you take the Component & Assembly Creation Training course.

Valid Library Installations Libraries can exist anywhere on the disk or a network server. The requirements for installation are as follows:

June 20, 2003

•

Every library must be contained within a folder named the same as the library.

•

The database file must exist within this folder with the same root name.

•

For vendor libraries, which contain specific components and assemblies to be used for modeling, there is a folder below the Library and database files called BMP. This contains all the image files associated with the library

•

Each item file -- ***.ITM is a definition for a particular component or assembly.

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

13

SupportModeler™ for PDS™ Admin Guide Preparing for Project Creation The following is a legitimate library installation:

Delete Local Libraries from Client Machines Optionally, you may want to delete the delivered libraries from each machine if you plan to use only libraries from your server-based master libraries directories. This ensures that all users only have access to the master libraries. The delivered libraries get installed with the software and would be located in C:\Program Files\SupMod\Lib\ on each client machine. If you delete the local libraries, each user will be warned that certain default libraries could not be loaded when they first start SupportModeler. They will then need to load libraries from the serverbased master libraries directory. Alternately, you can load the server-based libraries for them after you install the software on their machines. For

14

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Delete Local Libraries from Client Machines more information on loading and unloading vendor libraries, refer to the SupportModeler User Guide for PDS.

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

15

SupportModeler™ for PDS™ Admin Guide Creating a SupportModeler Project

Creating a SupportModeler Project Once the preparation for project creation is complete, perform the following operations for each project. If you wish to have detailed, on-site assistance with this process, Pelican Forge offers a QuickStart customization service to setup and configure your first project. Please contact Pelican Forge for prices and available scheduling.

Create a Supports discipline in PDS All of the pipe support areas and models that you will create in SupportModeler will be automatically written into the PDS project control database. You must manually create a Supports discipline in PDS, but then SupportModeler will use this discipline when creating areas and models in pdtable_112 and pdtable_113.

➤ To create a support discipline 1. Using PDS, choose Project Administrator > Project Environment Manager > Create Discipline Data. 2. Create a new discipline for pipe supports.

All areas and models created in SM for this project will be automatically added to the PDS project control database using this discipline. You do not need to add areas or models to this discipline using PDS. For example, create a discipline named Supports.

Set up your PDS database server for ODBC Your database administrator needs to set up your PDS database (Oracle or other) to allow ODBC connections from client machines using the database-specific procedures. Generally, this involves setting up an ODBC listener on the server with appropriate database services on each client machine. The details are dependent on your database and version and are beyond the scope of this guide. However, we provide some instructions that work for Oracle Version 8 in “Appendix A” in the section “Oracle ODBC Setup” on page 90

Create ODBC Sources to PDS databases Before you create the SupportModeler project, your database administrator must first create two ODBC sources on the machine you

16

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Decide on project location are working on - one to the PDS design database (dd_*) and one to the PDS project control database (pd_*). If you are using an Oracle database, we recommend using the Microsoft ODBC for Oracle drivers rather than the Oracle ODBC drivers, although either will work. Each client machine will need these same two ODBC sources in order to open the SupportModeler project.

Decide on project location Normally, your SupportModeler project would be located on a server where all client machines can have access to it. Most companies create the SupportModeler project within the PDS project directory.

SupportModeler project within PDS project directory In this case, you would manually create the Supports directory and specify this Supports directory as the location when you use SupportModeler to create the PDS_PROJ1 pipe support project. SupportModeler would create the \Supports\PDS_PROJ1 directory and its contents.

Alternate Directory Structure for shorter path names If length limitations for pdtable_113 path names would be exceeded with the previous structure, the following shorter paths may be used. Name all SupportModeler projects Sup and create them directly within the PDS project directory. The drawback of this method is that all SupportModeler

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

17

SupportModeler™ for PDS™ Admin Guide Creating a SupportModeler Project projects would be called Sup, rather than the project name, which can introduce some confusion.

18

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Create the SupportModeler project

Create the SupportModeler project ➤ To create a SupportModeler project 1. If you will be creating an Oracle-based SupportModeler project, see “Creating an ORACLE SupportModeler™ Project Database” on page 27 for steps you should perform prior to creating the project. 2. Choose File>New Project from the SupportModeler menu bar to create a new SupportModeler project. If you already had a project open, close the project first.

The Create New Project dialog box is displayed.

3. Use the following table to help you fill in all of the appropriate project options, noting which values can be changed later and which cannot.

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

19

SupportModeler™ for PDS™ Admin Guide Creating a SupportModeler Project

Change Later?

Field or Button

Project Option Description

Name Location

The name of the SupportModeler project, up to 50 characters. No Also referred to as project_dir, this is the root directory for the project, where all Auto the SupportModeler files for this project will be stored. These files include models, drawings, seed files and border files. The Browse button to the right of the field displays a file selection dialog box to help select the directory, whether on the local machine or a network drive. This is the actual location of the project files. A project can be moved simply by using Windows commands to move the root directory of the project. The value of this field will be updated automatically the next time the project is opened. Example: Create a project with Name EXAMPLE_PROJ in Location \\machine_name\share_name This step creates a directory called EXAMPLE_PROJ on the machine named "machine_name" in the shared directory called "share_name". Note: Because the SupportModeler project files are different, you should not store them in the c:\Bentley\Workspace\Projects directory that MicroStation/J automatically sets up at installation. The name of the node where this SupportModeler project will exist. PDS uses Yes this name to locate the project. This should be the same server name that you browsed to when setting the Location for this project. The full path to this SupportModeler project as it would be displayed on the Yes server machine. PDS uses this path to locate the pipe support dgn files. If you browse for the project location, this path will get partially set automatically. However, if the location you select is on a remote server, as in most production projects, you would need to edit the Project Directory on Server field to use the actual path on the server (i.e. C:\path\share\ ), rather than the shared path name or UNC path name

Workstation/Server Name Project Directory on Server

PDS Grid File

Plant North

20

This path should represent the same path that you browsed to when setting the Location for the project, except this field contains the directory as it would be specified on the server, not from a remote client machine. The path and file name of an ASCII PDS grid file. This file needs to be the same Yes format as the format produced by Frameworks Plus. This format allows SupportModeler to show the location of supports relative to the grid lines on fabrication drawings. The Plant North direction for the MicroStation global coordinate system. The Yes value you select here will be used for drawing production to display the North arrow on the location plan as well as to display view-direction information (for example Elevation looking West). The default value is MicroStation Global Y.

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Create the SupportModeler project

Field or Button

Project Option Description

Directory for Core Libraries

The path to the directory where the core libraries (folders sm_core and sm_core_user) are found. For production projects, you would select the \CoreLib\ directory from the Master Libs and Seeds directory you created on your company server. You can also use the delivered core libraries which are delivered with SupportModeler in C:\Program Files\SupMod\Lib\

Change Later? Yes

If the selected directory does not contain folders SM_Core, the system will display a warning that the path is not valid. Source Directory for When a new project is created, a set of seed files is copied from this directory to No Seeds the Seeds directory of the new project. For production projects, you would select the \Seeds\ directory from Master Libs and Seeds directory you created on your company server. Interface Mode The interface mode used to run this project. The available options will be deter- No mined by which software licenses you have installed. Select PDS for use with PDS, or PlantSpace for use with PlantSpace. The Stand Alone option is also available and could be used if you are not using any PDS or PlantSpace 3D plant models. Data Source Name, The ODBC data source name corresponding to the PDS design database that No Design you want to associate with this SupportModeler project. The data source name must already have been created. Data Source Name, The ODBC data source name corresponding to the PDS project database that No Project you want to associate with this SupportModeler project. The data source name must already have been created. Note: When a PDS project is created, a file named the same as the project with a *.pwd extension is created in the project directory. This file can hold the username and password associated with each of the two PDS data sources. You must edit this file manually to add the username and password, or see “Using SMpassword.exe” on page -24, to generate an encrypted password file. SupMod ORACLE db If you wish for the SupportModeler Project database to reside in an ORACLE databse, check this box. Refer to the Section “Creating an ORACLE SupportModeler™ Project Database” on page -27 for information on setting up your Oracle database. Project Units Area The values in this grouped area (for length, mass, force, moment, temperature No and pressure) indicate the units that should be used to display data in the BOM description of the fabrication drawing. In addition, the Length units (Length (& Dgn MU’s)) indicate the MicroStation Master Units used in the model. The value chosen here will determine which seed file is used whenever a new model is created. The seed file will be project_dir\Seeds\seed_units.dgn where units is the value you chose for this field. Note: The setting of the Length field should match your PDSproject setup. User Keyin Units Area The values in this grouped area (for length, mass, force, moment, temperature Yes and pressure) indicate the units that should be used to enter data into any key-in prompt (not pull-down menus). The entered value is automatically converted and stored in the object model in the Object units. Nominal Diameter The value of this parameter controls how the user enters nominal diameters (for No Rods and Pipe sizes) and how they appear on the fabrication drawing. If it is imperial, inch sizes will be displayed to the user and will be shown on the fabrication drawing. If it is metric, mm nominal units will be used. June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

21

SupportModeler™ for PDS™ Admin Guide Creating a SupportModeler Project 4. Click OK to accept the project options and create the new project.

✍ Clicking CANCEL exits without creating a project. A new SupportModeler project directory structure is created for the project, with the required subdirectories, seed files, project file and project database.

Project Directory Structure SupportModeler supports the existence of multiple projects, each of which may be in different units and on different computers. A project can be broken down into any number of areas, each of which can contain any number of models, which in turn can contain any number of supports. When you create a new SupportModeler project, you specify a location for the project and SupportModeler creates a directory structure that will contain all of the project files. A typical directory structure for a project named SupportModeler Project #1 containing Area1 and Area2 is shown as follows.

Upon creation, the project directory contains three files:

22

•

projname.spj - this is a binary file that contains certain required project information. This is the file you open when opening a project in SupportModeler. Do not edit this file directly.

•

projname.mdb - the "Project Database" - a Microsoft Access database file that contains information about the project, supports, areas and models. Do not edit this file directly. This is the database that stores all of the attribute and relationship information for all supports, components and assemblies in the project. If you selected

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Windows NT and the Project Database SupMod Oracle DB during project creation, this database will not be included. •

sm_oracle.con. If you selected SupMod Oracle DB during project creation, this file defines the connection parameters for the Oraclebased SupportModeler project database.

•

projname.pwd - can be edited to add a user name and password for the ODBC connection to the PDS project and design database. Examine this file for detailed directions, or see “Using SMpassword.exe” on page -24 for information on how to generate an encrypted password file.

Upon creation, the project directory also includes a Seeds directory that contains the seed files and settings files for this project. A subdirectory is also created for each modeling area that you create within the project. Each of these directories will, in turn, have two subdirectories named: •

\mod\ for support models (*.dgn and *.smj)

•

\drw\ for fabrication drawings

The naming convention for support fabrication drawings is as follows: model_supportID_revision.sht

Where

Means

model supportID revision

The name of the model where the support is located The identification of the support The revision number of the fabrication drawing

Windows NT and the Project Database By default, SupportModeler uses a project database (the database located in the project root directory and used to store all design information) in Access 2000 format. If you are using SupportModeler with Windows NT 4.0, you should convert the database from access 2000 format to Access 97 format. Performance will be significantly improved. To do this, you will need to open the project database in Access 2000 and save it as an Access 97 format. This will need to be done for each project created to work with Windows NT. This is unnecessary if you are using Oracle for the SupportModeler project database by choosing SupMod Oracle DB during project creation.

Password Files SupportModeler now has the capability of reading binary files that contain the username and password information for connection to the June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

23

SupportModeler™ for PDS™ Admin Guide Creating a SupportModeler Project two types of databases that it connects to during a PDS session. The two password files are located in the root of the SupportModeler project folder and are named i) proj_name.pwd and ii) sm_oracle.con

Proj_name.pwd Proj_name.pwd contains the ODBC Data Source Name, username and password information for connecting to the PDS project and design database. This file is created automatically when the project is created. You can either edit this file manually, or use SMpassword.exe.

✍ Ensure that the ODBC data source names exist for the project before continuing with the next step.

➤ Manually editing the Proj_name.pwd file If your PDS database is password protected, you will be prompted for both the dd and pd passwords. You can edit the *.pwd file in the new SupportModeler project directory to automatically fill in the passwords for you. Examine the file itself for instructions. This is an ascii file and must be readable by any designer using SupportModeler for this project. For security reasons, you may with to encrypt this file, using SMPassword.exe. For details, see the next section.

➤ Using SMpassword.exe 1. SMpassword.exe is delivered with SupportModeler. It is located in the SupportModeler\mdlapps folder. 2. Run the executable and enter in the information as seen below:

24

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Oracle Connection File

✍ The file created must be named the same as the project and have a .pwd extension..

3. Once the encrypted password file has been created, you can overwrite the .pwd file in your new or existing SupportModeler project folder.

Oracle Connection File If you selected the SupMod Oracle DB check box during project creation, an sm_oracle.con file will be created in the project’s root directory. This file contains the information necessary to connect to the SupportModeler project database in Oracle.

Automatic Creation of Sm_oracle.con file The sm_oracle.con file is created automatically when a new SupportModeler project is created. The file contains connection

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

25

SupportModeler™ for PDS™ Admin Guide Creating a SupportModeler Project information which you entered into the SupportModeler Project DB Info dialog box: during project creation.

➤ To recreate an sm_oracle.con file If the oracle login information changes, you may need to regenerate the sm_oracle.con file. 1. Create a dummy SupportModeler project in a temp location. 2. Press OK in the Create New Project dialog and fill in the SupportModeler Project DB Info dialog.

✍ If a project already exists in the oracle database that you point to in the

dialog, SupportModeler will tell you that project creation failed, but a new sm_oracle.con file will be created where you asked. 3. Copy this new sm_oracle.con and overwrite the existing sm_oracle.con file of your real SupportModeler Project.

26

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Creating an ORACLE SupportModeler™ Project Database

Creating an ORACLE SupportModeler™ Project Database It is now possible to have the SupportModeler project database reside in an Oracle database. To accomplish this there are a couple of things the Oracle DataBase Administrator must do BEFORE creating the SupportModeler project. These items are described below.

✍ Note: There may be more than one way to create the following items. We describe only one of these.

➤ To Create a New Tablespace in ORACLE for the SupportModeler Project 1. Use Oracle DBA Studio to create a new Tablespace in the oracle database of your choice. 2. Highlight the database of interest (PDS in this case) and click on the Create icon as shown in the figure below

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

27

SupportModeler™ for PDS™ Admin Guide Creating an ORACLE SupportModeler™ Project Database 3. Select Tablespace from the dialog that comes up and press the Create button.

4. Key in a new name for this Tablespace (you should use the same name as the SupportModeler project you intend to create later)

28

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Creating an ORACLE SupportModeler™ Project Database 5. Increase the Size of the file from 5mb to at least 100 mb. This will ensure that there is sufficient storage space. Then click the Create button..

6. Once the Tablespace has been created, you can create a new user. Expand the Security item in the database and select the Users item then click on the Create icon.

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

29

SupportModeler™ for PDS™ Admin Guide Creating an ORACLE SupportModeler™ Project Database 7. From the dialog that appears, click on User then click the Create button

30

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Creating an ORACLE SupportModeler™ Project Database 8. Complete the form by keying in a Name and Password. Usually, the name is the same as entered in step 3. The Password is usually the same as the Name.

9. Under the Tablespaces heading, change the Default from INDX to the project name (in this case, SM_MYPROJ) and Temporary to TEMP_SEGS. 10. Select the Role tab on the Create User Dialog Select RESOURCE form the list of Available Roles, then press the down arrow button to

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

31

SupportModeler™ for PDS™ Admin Guide Creating an ORACLE SupportModeler™ Project Database grant that role to this new user. If the CONNECT role has not already been added, do so as well. Click on OK to create this user.

32

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Creating an ORACLE SupportModeler™ Project Database 11. Start SupportModeler and from the File menu, select New Project.

Check this box to have SupportModeler create the project database in the Oracle database you just created. When you finish completing this form and press OK, you will be asked for additional information about the Oracle database

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

33

SupportModeler™ for PDS™ Admin Guide Creating an ORACLE SupportModeler™ Project Database :

1. Service name as shown in the Oracle DBA Studio. 2. TableSpace name from step 3. Uppercase. 3. Username and Password.

34

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Using SM_PDS.DAT to Configure the PDS Interface

Using SM_PDS.DAT to Configure the PDS Interface To configure a SupportModeler project to work with a PDS project, you need to: •

Set up the PDS database to receive ODBC connections and create ODBC data source names on each client machine to read and write from the PDS database. This has already been completed in the section “Creating a SupportModeler Project” on page -16 because the ODBC must be setup and working before you can create the project.

•

Edit the SM_PDS.DAT file for the project. This is the primary resource used to configure the data transfer and integration between the SupportModeler project and the PDS data, and is the primary focus of this section.

✍ ODBC provides the mechanism for transferring data between SupportModeler and PDS, while the SM_PDS.DAT file determines what data is transferred.

✍ The delivered SM_PDS.DAT file is in C:\Program Files\SupMod\Seeds.

✍ While working on your first production project, the process of

setting up SM_PDS.DAT is usually iterative - make changes and test them in the project’s SM_PDS.DAT file, then copy them back to the master lib and seeds directories to use as a master for future projects. Each project’s SM_PDS.DAT file is often edited after the project has been created in order to meet project-specific requirements.

Overview of the PDS Interface Four Parts of the Interface There are four main parts to the SupportModeler-PDS interface: •

June 20, 2003

Model management - SupportModeler areas and models are automatically entered in the PDS project control database for use by PDS designers and post-processing tools. SupportModeler can attach

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

35

SupportModeler™ for PDS™ Admin Guide Using SM_PDS.DAT to Configure the PDS Interface PDS reference files based on discipline, area and model. Uses pdtable_111, pdtable_112, and pdtable_113. •

Connect to Pipe - transfer PDS segment data based on a graphical selection of a PDS pipe segment center line. Reads data from pdtable_12_xx.

•

Update PDS - writes logical supports into the referenced PDS piping models. Uses pdtable_114 to determine system_unique_no and writes to pdtable_80_xx.

•

Check with PDS - reports discrepancies between PDS and SupportModeler. Compares support locations and data from pdtable_12_xx and pdtable_80_xx.

Integrating with PDS Deliverables The logical supports created in PDS piping files by SupportModeler and the detailed graphics in the SupportModeler design file are used in PDS to: •

Generate and annotate isometric and orthographic drawings

•

Create basic pipe support listings

•

Perform clash detection

•

Provide support locations for stress neutral file generation

All of these post-processing tools are used in the normal manner.

Pipe Segment Attributes to Read from PDS The PIPING_DATA and PIPING_DATA_WITH_UNITS sections control which PDS database attributes are transferred to which SM properties during the Connect to Pipe operation. You can use any attributes from pdtable_12 (segment data). The PIPING_DATA_WITH_UNITS section is used only for pressure and temperature attributes that have an associated code-listed units attribute (for example, NORMAL_DGN_TEMP and NORMAL_DGN_TEMP_UNITS). All other piping attributes are entered in the PIPING_DATA section.

✍ PDS data can be written only into SM properties that have a prompt displayed in the SM Active Support Parameters dialog box.

Support Properties to Write into pdtable_80 The SUPPORT_DATA section controls which SM property values are written into which PDS attributes. Any property in the SM support object can be transferred to any attribute with a similar data type in pdtable_80.

36

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Using PDS Code Listed Attributes in SupportModeler

✍ SupportModeler is intended to be the main repository of detailed design

information and only a minimal amount of data should be transferred to PDS table 80. SupportModeler Reports are better suited to the detailed reporting of pipe support material takeoff than data that is transferred to PDS table 80. In addition, hard-coded values can be written into a specific attribute in pdtable_80 by specifying a value in double quotation marks (“) in place of the Property Name. As delivered, this is used to write PSL into both the model_code_log and commodity_code attributes for each support. Refer to the SUPPORT definition in the SUPPORT.ITM for detailed information. One-line script expressions, to be evaluated on the support item, can also be used as the property name. If an expression requires more than one line, you can externalize the expression into a script item file and refer to it here with the syntax EXECUTE

where is the name of a loaded library, often SM_CORE_USER, and is the name of a script in that library. Refer to the EVAL_SAMPLE.ITM file in ..\SupMod\ Lib\ SM_Core_User\ for an example of a script file for use as an expression.

Using PDS Code Listed Attributes in SupportModeler For SM to understand and use PDS code-listed attributes, the code lists must first be extracted to ASCII neutral files and the SM_PDS.DAT Correspondence File (SM_PDS.DAT) must be edited to point to these code-list files. Use the PDS Standard Note Library Manager to extract the code-lists for those database attributes that SM will use. Make sure that they are stored in a location that is accessible from all client machines using the same path, and specify this path and file name in SM_PDS.DAT. For each row in SM_PDS.dat that uses a code-listed PDS attribute, the code-list path should be specified in the Full Path to Codelist column.

PDS Project Database Table Names The PROJECT_TABLES section tells SupportModeler the exact names of several required PDS project control database tables. Used primarily for case-sensitivity issues with SQL Server, most people don't need to change this section. You may need to add or remove the FORWARD_SLASH option from the pdtable_113 entry to get the paths for SupportModeler models to match the format of other PDS models. When you create the first June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

37

SupportModeler™ for PDS™ Admin Guide Using SM_PDS.DAT to Configure the PDS Interface SupportModeler model in a new project, examine the PATH_NAME column pdtable_113 to see whether the SupportModeler model path has the same format as other PDS models.

PDS Database Column Names The COLUMN_NAMES section tells SupportModeler the exact column names of several required attributes in both the project and design databases. Used primarily for case-sensitivity issues with SQL Server, most people don't need to change this section.

PDS logical support symbology The SYMBOLOGY section defines the symbology to use when SM creates PDS logical supports during Update PDS. This must match the symbology that PDS expects for logical supports or PDS will not recognize them as supports.

➤ To determine and set the logical support symbology for PDS 1. In PDS, place a logical support into a piping model. 2. Use the PDS Analyze tool or the MicroStation Element Information tool to examine its level, color, and weight. 3. Enter the level, color and weight into the SYMBOLOGY section of the SM_PDS.DAT file that will be used on the project.

✍ If all of your PDS projects use the same logical support symbology, you

could make this change to the SM_PDS.DAT file in the master seeds directory. Otherwise, wait until after you have created the project and then make this change to the SM_PDS.DAT file in the project’s \Seeds\ directory.

Area and Model Database Defaults The AREA_DEFAULTS and MODEL_DEFAULTS sections define default hard-coded values, in double quotation marks (“), that must be populated when you create new area and model entries in pdtable_112 and pdtable_113. If your PDS project control database is set up to automatically populate default values, you do not need to use these sections. As an example, this section could be changed to set newly-created pipe support models to a certain model status.

38

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Path to PDS Models

Path to PDS Models In order for SupportModeler to find the PDS reference files, one of the following changes may be required: •

Additional shares may be required on the PDS file server.

•

A PATH_CONVERSION section may be needed in the SM_PDS.dat correspondence file.

➤ To test if SupportModeler can find PDS models: 1. Open a model in your new SupportModeler project 2. Select File | Attach PDS Reference File to attach a valid piping model as a reference model. 3. If you get a warning saying that the file was not found, record the path that it tried to use to access the file. 4. Make changes to the shared directories on the server or add a PATH_CONVERSION section to SM_PDS.DAT based on the explanations outlined below. 5. To retest, close and re-open the SupportModeler project so that it rereads the SM_PDS.DAT file and repeat this procedure.

Understanding How SupportModeler Locates PDS Reference Files SupportModeler uses the model data in pdtable_113 of the PDS project control database to locate PDS reference files. To convert the pdtable_113 data into a standard Windows UNC file path, SupportModeler normally strips any leading drive letter from the PATH_NAME, and then appends the resulting PATH_NAME to the NETWORK_ADDRESS. For example, using the following pdtable_113 model data, SupportModeler looks for the reference model using the path: \\PSERV112\proj\cal25\pds\models\piping\pipea1m3.dgn

Where

Means

MODEL_FILE_SPEC PATH_NAME NETWORK_ADDRESS

pipea1m3.dgn e:\proj\cal25\pds\models\piping PSERV112

Share Names If your PDS file server does not have appropriate share names, the simplest solution is to share the appropriate directories.

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

39

SupportModeler™ for PDS™ Admin Guide Using SM_PDS.DAT to Configure the PDS Interface In the previous example, the PDS file server PSERV112 would need to have the \proj directory shared using the name proj. If it not acceptable for your network operations to add this new share, you can also enter a path conversion in the SM_PDS.dat correspondence file.

Path Conversion in the SM_PDS.DAT File To add a path conversion to the SM_PDS.dat file, create a new entry at the end of SM_PDS.dat using the PATH_CONVERSION keyword followed by pairs of substitution strings, as follows: PATH_CONVERSION txt1 txt2

, sub1 , sub2

… Where

Means

sub1 sub2

sub1 should be substituted for txt1 in PATH_NAME sub2 should be substituted for txt2 in PATH_NAME

For the previous example, suppose your PSERV112 already had the \piping directory shared out cal25p and you do not want to share the proj directory. With the following entry in SM_PDS.dat, SupportModeler will now look for the reference model using the path \\PSERV112\cal25p\pipea1m3.dgn PATH_CONVERSION e:\proj\cal25\pds\models\piping\

, cal25p\

Support Properties for Display in Design Review The SUPPORT_OBJECTS and COMPONENTS_&_ASSEMBLIES sections define which properties should be available during a Design Review session. SupportModeler creates a DRV for each model and populates this file during the Update PDS operation. This section of the SM_PDS.DAT file controls what properties of the SUPPORT object, and of the components and assemblies within the support, get written into the DRV file. You can also use script expressions and relationships in addition to simple property names. One-line script expressions, to be evaluated on the support item, can be used as the property name. Or, if an expression

40

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Control of Interference Envelope File Generation requires more than one line, you can externalize the expression into a script item file and refer to it here with the syntax EXECUTE

where is the name of a loaded library, often SM_CORE_USER, and is the name of a script in that library. Refer to the EVAL_SAMPLE.ITM file in ..\SupMod\ Lib\ SM_Core_User\ for an example of a script file for use as an expression. Refer to the SupportModeler Library Customization Guide for more information.

Control of Interference Envelope File Generation The CLASH_ENVELOPE_SETTINGS section determines what items and what properties of those items get written to the interference envelope file. The envelope file is used by PD_Clash to perform intelligent interference detection. The COMPONENT_FILTER_EXPRESSION is a boolean test that is applied to each SupportModeler component. If the expression evaluates to TRUE on a component, that component will be included in the clash envelope for its support. If FALSE, it will not be included. This is generally used to eliminate items with no physical graphics (welds, notes, etc.) but can be extended to selectively include components. SUPPORT_NAME_EXPRESSION and SUPPORT_DESCRIPTION_EXPRESSION are evaluated on each support item to generate a name and description for the support in the clash envelope file.

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

41

SupportModeler™ for PDS™ Admin Guide Testing a new SupportModeler Project

Testing a new SupportModeler Project Before doing any production work in a new SupportModeler project, we strongly recommend testing the project using the following procedures:

In SupportModeler: 1. Check the project directory structure to make sure that it has been created correctly. See “Project Directory Structure” on page -22 2. Open the project in SupportModeler 3. Create one test area and one test model. For detailed instructions, see “Setting Up Areas and Models” on page -44.

Make sure a directory is properly created in the project directory for the new area you created. Make sure that the new DGN model is properly created in the \mod\ directory of your new area and that a new set of database tables tSupports_xx, tItems_xx, tConnectPoints_xx, and tProperties_xx are created in the project database. 4. Attach PDS Reference Files

Make sure that the lists of disciplines, areas and models are correct for the PDS project you are working on. If not, check the ODBC data source for the project database. Make sure that SupportModeler can find the PDS reference files. If not, see the section “Path to PDS Models” on page 39. 5. Start New Support and connect to pipe segment.

Make sure that the pipe attributes are correctly brought into the support properties in the Active Support Parameters dialog. If not, see the section “Pipe Segment Attributes to Read from PDS” on page 36. Make sure that the format of the support ID matches what you expect it. If not, see the section 6. Model a support. 7. Update PDS. Check the PDS piping model for proper logical supports and check to make sure that the DRV file was created. 8. Ensure that the ENV file was created, for interference detection (these are automatically generated on Update PDS). 9. Check with PDS.

42

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide In the PDS database

In the PDS database 1. Check pdtable_112 for your new area entry. Are any AREA_DEFAULTS changes needed in SM_PDS.DAT? 2. Check pdtable_113 for your new model entry. Are any MODEL_DEFAULTS changes needed in SM_PDS.DAT? Check the model path. Do you need to take out the FORWARD_SLASH from the PROJECT_TABLES section of SM_PDS.DAT? 3. Check pdtable_80_xx for the associated PDS piping model.

In PDS 1. Open the piping model that was associated with your support model. 2. Review the logical support that was created from SupportModeler. If the symbology is incorrect in SM_PDS.DAT, you will not be able to review it. 3. Attach the support model as a reference file using the standard PDS reference file tools. If the path in pdtable_113 has the wrong slashes (back vs. forward) it may not be able to attach the file. Also, if the Workstation/Server Name or Project Directory on Server are incorrect, PDS will not be able to find the files. 4. Create an ISO drawing for the supported line. The logical support created by SupportModeler should appear. Note that ISO annotation is controlled by pdtable_80 entries, ISOGEN options file settings, and PDS Isometric Drawing Labels and can be easily customized. The SM_PDS.DAT file controls what gets written to pdtable_80. 5. Generate and annotate a GA/Ortho drawing. 6. Create a Framework ASCII grid file for testing drawing generation in SupportModeler.

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

43

SupportModeler™ for PDS™ Admin Guide Setting Up Areas and Models

Setting Up Areas and Models To help organize the pipe supports in large engineering projects, a SupportModeler project can be broken down into any number of areas. Each area can contain any number of models, which in turn can contain any number of supports. SupportModeler modeling areas are simply a high-level way of grouping models together and are analogous to folders on your PC’s hard drive.

Adding a New Area ✍ Each SupportModeler area is automatically added to the Design Area table in the PDS project control database (pdtable_112).

➤ To add a new area 1. Start SupportModeler and open the Add/Open Model dialog box. 2. In the Add/Open Model dialog box, choose File>New Area, or click the Add New Area button.

The Area Information dialog box is displayed.

3. At the Name field, type a name for the new area.

Area names are limited to the length allowed in pdtable_112. The area name cannot be changed after creation. 4. At the Description field, type a description for the new area.

Descriptions are limited to the length allowed in pdtable_112. The description can be changed at any time. 5. At the Associated PDS Discipline for this Area field, select Supports from the drop-down list box of disciplines.

The disciplines are populated from the PDS project control database (pdtable_111). You should have previously created a discipline for supports as explained in “Create a Supports discipline in PDS” on page 16.

44

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Adding a New Model 6. Click OK.

Adding a New Model Models in SupportModeler consist of matched sets of MicroStation design (DGN) files and model tables in the project database, which together act as an enhanced design file. The DGN files store the support graphics and the database tables store the rich data associated with each support item. To add a new model 1. In the Add/Open Model dialog box, click an existing area so that it is highlighted in the project hierarchy. 2. Choose File>New Model, or click the Add New Model button.

The Model Information dialog box is displayed.

3. At the Name field, type a name for the new model.

Model files are limited to the column width allowed in pdtable_113 of the PDS project control database.

✍ The model name cannot be changed after creation. 4. Click OK.

✍ Please note that if you name your Support models the same as your

Piping models, you must be sure to delete the models using SupportModeler only. If you deleted Support models through PDS, any other files with the same names are also deleted.

PDS Site Identifier Implementation of a new Site Identifier (Site_ID) attribute in PDS 7.2 to facilitate Data Exchange in Workshare projects A new configuration variable called SUPMOD_PDS_SITE_ID has been added to SupportModeler. When set, SupportModeler will assign newly created models to the site identified by the configuration variable. The text that the configuration variable is set to must match exactly an existing PDS site identifier. An example of this configuration variable is in

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

45

SupportModeler™ for PDS™ Admin Guide Setting Up Areas and Models mslocal.cfg delivered with this version of SupportModeler. You may wish to set the configuration variable in a project specific pcf file.

✍ This configuration variable is valid only with PDS Version 7.2 or later projects.

Changing an Area or Model Description ➤ To change an area or model description 1. In the Add/Open Model dialog box, click the area or model containing the description that you want to change.

✍ The description of a support is automatically set equal to the support ID and cannot be changed.

2. Click the description field and edit the description.

When you leave the field, you are prompted to confirm the description change to prevent inadvertent description changes. 3. Click Yes to accept the change, or No to leave it unchanged.

Deleting an Area is permanent and cannot be undone. The area is removed from W Deletion your hard drive.

➤ To delete an area 1. In the Add/Open Model dialog box, click the area that you want to delete.

✍ An area cannot be deleted if it contains any models. The models must be deleted first.

2. Choose File>Delete Item, or click the Delete Item button.

W

You are prompted to confirm your deletion because deletions are permanent.

When you delete an area, the entry in the Design Area table, pdtable_112, of the PDS project control database is also deleted. project hierarchy is stored both as a directory structure on your hard W The drive and in the SupportModeler project database. Because of this, do not use any Windows file management tools to delete or manipulate areas as these changes would not be reflected in the project database.

46

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Deleting a Model

Deleting a Model deletion is permanent and cannot be undone. The model and the W Model associated supports and drawings are removed from your hard drive.

➤ To delete a model 1. In the Add/Open Model dialog box, click the model you want to delete. 2. Choose File>Delete Item, or click the Delete Item button to delete the model and all of the supports within that model.

A prompt is displayed asking you to confirm your actions because deletions are permanent.

✍ Individual supports cannot be deleted in this manner. See the

sections Deleting Pipe Support Items from Supports and Deleting Entire Pipe Supports, later in this chapter.

When you delete a model, the entry in the Design Area table, pdtable_113, of the PDS project control database is also deleted. project hierarchy of areas and models is stored both as a directory W The structure on your hard drive and in the SupportModeler project database. Because of this, do not use any Windows file management tools to delete or manipulate models as these changes would not be reflected in the project database. With PDS projects, the hierarchy is also stored in the PDS project control database.

Moving, Copying or Renaming Models To move, copy or rename a model, please see the SupportModeler for PDS User’s Guide.

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

47

SupportModeler™ for PDS™ Admin Guide Project Maintenance

Project Maintenance Archiving Projects The model files and project database contain the primary design information.

➤ To archive a project: 1. Backup the project folder recursively. 2. Archive any libraries and their associated database files that were used to model any supports and their bitmap files. For example, your master lib and seeds directories.

✍ You can add these SupportModeler directories as User Data to your PDS Archive.

Retrieving a Model from Backup Normally, the SupportModeler project directory is backed up (probably on a daily basis) as part of the ordinary server backup. Sometimes, you may wish to retrieve a particular model from the nightly backup.

➤ To retrieve a model from backup: 1. Retrieve the project database as well as the design file from your archive device and place these into a temporary location 2. Open the SupportModeler project that you want to import the backup model into. 3. Select File>Copy/Import Model... The Copy/Import Model dialog opens. 4. Follow the procedure outlined in the SupportModeler User Guide for importing a model.

Changing Project Settings Some of the project settings that you use when creating a project can be modified later. For a list of options that can and cannot be changed, along with their meanings, refer to the procedure “To create a SupportModeler project” on page -17.

48

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Checking for Model Inconsistencies ➤ To edit project options 1. Start SupportModeler. 2. Select File>Open Project from the SupportModeler menu bar to open the project or, if the project was opened recently, select it from the Most Recently Opened list near the bottom of the File menu.

The project will open, vendor libraries will be loaded into memory, and the Add/Open Model dialog box will open. 3. Click Done to close the Add/Open Model dialog box. 4. Choose File>Project Options from the SupportModeler menu bar to display a dialog box very similar to the Create Project dialog box. 5. Edit any project options that are not grayed out. 6. Click OK to accept the changes or click Cancel to exit without changing the project options.

✍ Depending on which project options you change, a warning may be

displayed indicating that the changes will not take effect until you exit and restart SupportModeler.

Checking for Model Inconsistencies SupportModeler provides a MicroStation keyin command SMCHECKMODEL which checks the active SupportModeler model for inconsistencies and reports any problems it finds. In particular, it checks for: •

pipe support graphics in the MicroStation DGN file that do not have corresponding project database entry.

•

project database entries that do not have corresponding pipe support graphics in the associated MicroStation DGN file.

•

make sure that every component is part of a support.

These inconsistencies usually result from editing a SupportModeler model using plain MicroStation rather than SupportModeler, but can also occur as a result of network communication problems or crashes of the client or server machines. The SMCHECKMODEL operation creates a log file in the model’s directory named the same as the pipe support model, with the extension *.chk. Upon completion, it displays this file using notepad. Generally, to fix these problems, you would use the SMFIXMODEL tool explained below in the section “Fixing Model Inconsistencies” on page 50. Whenever a user opens a model, SupportModeler automatically runs SMCHECKMODEL in the background, without displaying the log file. June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

49

SupportModeler™ for PDS™ Admin Guide Project Maintenance If it finds any problems, it warns the user and recommends that the administrator run SMFIXMODEL. SMCHECKMODEL does not change the model in any way and can safely be used at any time.

➤ To check a model for inconsistencies 1. Start SupportModeler and open the project containing the model. 2. Open the model to be checked.

SupportModeler automatically runs SMCHECKMODEL in the background and warns if it finds any problems. It will not display the log file. 3. Optionally, in the MicroStation keyin field, type SMCHECKMODEL.

SupportModeler will repeat the model check and will display the log file showing the results.

Fixing Model Inconsistencies SupportModeler provides a MicroStation keyin command SMFIXMODEL which fixes any inconsistencies that it detects in the active SupportModeler model. The SMFIXMODEL operation fixes problems that are reported during an SMCHECKMODEL including: •

deletes pipe support graphics in the MicroStation DGN file that do not have corresponding project database entries.

•

Deletes project database entries that do not have corresponding pipe support graphics in the associated MicroStation DGN file.

•

deletes components, both the graphic and the object, that are not part of a support

•

if a SUPPORT object does not have both a graphic and an object, deletes the components and assemblies associated with that support as well.

The SMFIXMODEL operation creates a log file in the model’s directory named the same as the pipe support model, with the extension *.fix. Upon completion, it displays this file using notepad.

➤ To fix model inconsistencies 4. Start SupportModeler and open the project containing the model.

50

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Reinstancing Supports 5. Open the model to be checked.

SupportModeler automatically runs SMCHECKMODEL in the background and warns if it finds any problems. It will not display the log file. 6. In the MicroStation keyin field, type SMFIXMODEL.

SupportModeler will delete inconsistent elements and fix any mismatched locations. It will display the log file showing the details of what was changed.

Reinstancing Supports SupportModeler provides a function reinstance the supports in the active model based on the current definition of the SUPPORT item in SM_CORE_USER library. This is very useful if you add or remove properties and want to propagate these changes to supports that have already been modeled. The Reinstance Supports command does not reinstance or change components or assemblies, it only changes the SUPPORT object itself.

✍ The SupportManager product, available separately, adds the ability to

reinstance all of the supports in a project, or in specific areas and models, automatically. This is very useful if you want to make retro-active changes to a project that already has numerous supports modeled.

➤ To reinstance supports in a model 1. Make sure that the changes you make to the SUPPORT object are made in the particular SM_CORE_USER library (SUPPORT.ITM) that is used by the project. For example, your master lib and seeds directories as discussed in “Create Server Directories for Master Libraries and Seeds” on page 8. 2. Start SupportModeler and open the project containing the model. 3. Open the model.

SupportModeler automatically runs SMCHECKMODEL in the background and warns if it finds any problems. It will not display the log file. If any problems are reported, these should be fixed before updating the supports. Refer to the section “Fixing Model Inconsistencies” on page 50. 4. From the Support Menu, select Reinstance Supports.

SupportModeler will update each support in the model and change it to match the current definition of the SUPPORT item script, including adding any new properties that were added to the definition. The values of existing properties from the existing support are passed into the new support. June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

51

SupportModeler™ for PDS™ Admin Guide Project Maintenance

Configuration Variables for SupportModeler SupportModeler Version 7.2.3 provides numerous configuration variables which give you control over many aspects of the software. All of the configuration variables are included in two delivered files, with extensive comments on how to use them: •

C:\Program Files\SupMod\mdlapps\config\mslocal.cfg

•

C:\Program Files\SupMod\Seeds\sm_drw.dat

Generally, drawing-related configuration variables are included in sm_drw.dat and all other settings are in mslocal.cfg Please refer to the delivered versions of these files for instructions on how to use the various configuration variables. Specific configuration variables are mentioned in the sections of this guide dealing with the SupportModeler features that the variables control or affect.

52

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Customizing the Fabrication Drawings

Customizing the Fabrication Drawings SupportModeler fabrication drawings are generated automatically based on simple formatting features that you specify in the drawing seed files and an ASCII configuration file called SM_DRW.DAT.

Drawing Seed Files Drawing seed files define the location and size of support graphics in the drawing and contain text nodes that are used for annotating the border and defining annotation symbology. Each drawing seed file can have an optional border file attached as a reference. The drawing seed files work together with the SM_DRW.DAT drawing settings file. SupportModeler creates each fabrication drawing by copying a 3D drawing seed file (*.sht) with an optional attached border reference file (*.brd) into a new 3D drawing file. The user can select the seed file to use for each support in order to most effectively display the graphics of the support and its position in the plant. You determine what seed files are available to the user for the each project. Each project can use standard company-wide drawing formats, or each can have unique project-specific drawing formats.

✍ See the delivered example seeds and borders SM_ASIZE and SM_BSIZE in the C:\Program Files\SupMod\Seeds\ directory.

✍ Seed files must be 3D MicroStation files, not 2D, or the drawing routines will not work properly.

✍ Seed files for a project should be located in the project’s \Seeds\ directory.

Relevant Settings for “Drawing Seed Files” Location ORIENTATION property in SUPPORT definition

SUPPORT.ITM

View Definition Panels A view definition panel is a numerically-tagged rectangular shape in the drawing seed file in which a view of the 3D support model can be displayed.

✍ Maximum number of view panels in a drawing is now 20 (increased from previous limit of 5 in versions prior to Version 7.2.3).

During drawing production, the 3D support model and it’s displayed reference models are attached as reference files for each view panel. Each view is sized and clipped in the orientation specified by the user (in the

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

53

SupportModeler™ for PDS™ Admin Guide Customizing the Fabrication Drawings Active Support Parameters properties View in Panel 1, View in Panel 2, etc.) so that the active support and a portion of the surrounding structure fit within the panel. In addition, view panels can automatically display detail cells on the drawing (see “Automatic Detail Cells” on page 68). The view panels themselves are automatically deleted from the drawing file after the reference files are attached.

➤ To create a view definition panel in a drawing seed file Refer to the MicroStation User’s Guide for detailed instructions on placing a block and working with tags. 1. Using the MicroStation Place Block tool, place an orthogonal block into the seed file (.sht, not the border file), within the boundaries of the border. 2. Using the MicroStation Attach Tags tool, attach a numerical tag to the block with a unique value from 1 to 5.

Once a view panel is created, it can be copied to create additional view panels. For copied panels, use the MicroStation Edit Tags tool to change each tag to a unique numerical value from 1 to 5. Relevant Settings for “View Definition Panels”

Location

SUPMOD_DRAWING_VIEW_PANEL_TAG_SET_NAME

SM_DRW.DAT

SM_DRAWCLIPZ

SM_DRW.DAT

SUPMOD_DRAWING_SUPPRESS_COMMON_ORTHO_SCALE

SM_DRW.DAT

SUPMOD_DRAWING_FAST_FIT

SM_DRW.DAT

SUPMOD_DRAWING_SUPPRESS_REFS_IN_VIEW_PANELS

SM_DRW.DAT

SUPMOD_DRAWING_VIEW_PANEL_FOR_CALLOUTS, SUPMOD_DRAWING_VIEW_PANEL_FOR_WELDS, SUPMOD_DRAWING_VIEW_PANEL_FOR_NOTES, SUPMOD_DRAWING_VIEW_PANEL_FOR_MAIN_DIMENSIONS, SUPMOD_DRAWING_VIEW_PANEL_FOR_SECONDARY_DIMENSIONS, SUPMOD_DRAWING_VIEW_PANEL_FOR_LINEREF_LABELS

SM_DRW.DAT

SUPMOD_DRAWING_VIEW_PANELS_FOR_KEYPLAN_COORDINATE_CALLOUT

SM_DRW.DAT

Tagged View Panel Graphics

Drawing Seed Files

SUPMOD_DRAWING_STARTING_VIEW_PANEL_FOR_DETAIL_CELLS

SM_DRW.DAT

54

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Drawing Seed Files Automatic View Panel Labels When the user generates a drawing, each view panel that displays a drawing view, or the keyplan, gets an automatic text label to clarify the contents of the view. For example, Elevation Looking West, Isometric Looking Northeast, Plan View, or Keyplan. You can control the text of these labels and the symbology but, for now, the label is always placed at the bottom center of the view panel.. Relevant Settings for “Automatic View Panel Labels”

Location

SYMBOLOGY_VIEWLABELS

SM_DRW.DAT

Associated SYMBOLOGY_VIEWLABELS text node

Drawing Seed Files

SUPMOD_DRAWING_NORTH_TEXT SUPMOD_DRAWING_EAST_TEXT SUPMOD_DRAWING_SOUTH_TEXT SUPMOD_DRAWING_WEST_TEXT SUPMOD_DRAWING_NORTHEAST_TEXT SUPMOD_DRAWING_NORTHWEST_TEXT SUPMOD_DRAWING_SOUTHEAST_TEXT SUPMOD_DRAWING_SOUTHWEST_TEXT SUPMOD_DRAWING_TOP_TEXT SUPMOD_DRAWING_BOTTOM_TEXT SUPMOD_DRAWING_ELEVATION_TEXT SUPMOD_DRAWING_ISOMETRIC_TEXT

SM_DRW.DAT

SUPMOD_DRAWING_SUPPRESS_VIEW_LABEL_JUSTIFICATION_CHANGE

SM_DRW.DAT

Description of MicroStation Saved View, if User specifies a saved view in a view panel

Support models

Annotation Text Nodes Text nodes are placed into the seed file to define the location, font, and justification for displaying specific annotation data on a fabrication drawing. Each text node corresponds to a specific SupportModeler property as defined in the SupportModeler drawing settings file, SM_DRW.DAT. For each project, this ASCII data file maps specific properties, or expressions, to specific text node numbers. Each seed file used in a project should use the same text node numbers for the same properties. Data is displayed on a text node by using the text attributes associated with that text node. Refer to the MicroStation User’s Guide for detailed instructions on changing view settings, working with text nodes, and compressing design files.

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

55

SupportModeler™ for PDS™ Admin Guide Customizing the Fabrication Drawings ➤ To add a text node to a drawing seed file 1. Open the drawing seed file in MicroStation. 2. Turn on the display of text nodes by using the MicroStation View Settings dialog box. 3. Set the MicroStation Active Text Attributes as you want. 4. Set the text node number by using the MicroStation key-in: nn=###

where ### is the node number that you want. 5. Using the MicroStation Place Text Node tool, place the text node in the location in the seed file (.sht, not the border file) where you want it. 6. In the same manner, place additional text nodes.

✍ The node number is incremented automatically after each

placement. If the next number is the one you want, you do not have to set the node number again.

7. Turn off the display of text nodes and compress the design file. 8. Add or edit entries in the SM_DRW.DAT file for the new text nodes. Refer to the section “Controlling Drawing Features using SM_DRW.DAT” on page -59 for more information. Unless the text nodes are listed correctly in the drawing settings file, SupportModeler will ignore them during drawing creation.

✍ If you are working on a text node for the display of the BOM listing, you need to manually determine how many lines of BOM text will fit inside the border at that text node location. You need to enter the maximum number of lines into the BOM entry in the drawing settings file for the project.

nodes and view annotation panels must be placed in the seed file, not W Text in the border file. If they are placed in the referenced border file, they will be displayed as graphics but will not be detected or used by the automated drawing production routines.

56

Relevant Settings for “Annotation Text Nodes”

Location

TEXT_NODES section

SM_DRW.DAT

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Drawing Seed Files

Relevant Settings for “Annotation Text Nodes”

Location

Associated annotation text nodes

Drawing Seed Files

Properties in SUPPORT item definition

SUPPORT.ITM

Symbology Text Nodes Symbology text nodes are used to define the symbology and font for the various automatic annotation, such as callout leaders, weld symbols, and view panel labels. They are placed identically to annotation text nodes and there is nothing special about the text nodes themselves. In the TEXT_NODES section of SM_DRW.DAT, they are associated with specific annotation features using the SYMBOLOGY_xx keywords as outlined below.

✍ The symbology text nodes are used only as symbology templates and no

text is written onto them in the drawing. The location of these text nodes is not important. When a drawing is posted, the empty text nodes are removed from the drawing file. Relevant Settings for “Symbology Text Nodes”

Location

SYMBOLOGY_KEYPLAN SYMBOLOGY_CALLOUTS SYMBOLOGY_CALLOUT_TEXT SYMBOLOGY_VIEWLABELS SYMBOLOGY_LINEREF SYMBOLOGY_LINEREF_TEXT SYMBOLOGY_WELDS SYMBOLOGY_WELD_TEXT SYMBOLOGY_NOTES SYMBOLOGY_NOTE_TEXT

SM_DRW.DAT

Associated annotation text nodes

Drawing Seed Files

✍ Dimension symbology is controlled using the MicroStation dimension

symbology settings in the drawing seed file, while the symbology of all other drawing annotation is controlled using symbology text nodes in the seed file. For more information on automatic dimensions, see “Automatic Dimensions” on page 65

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

57

SupportModeler™ for PDS™ Admin Guide Customizing the Fabrication Drawings Recommended View Settings When you have completed your changes to the drawing seed files, we recommend the following view settings for use with the SupportModeler drawing routines.

➤ To use recommended view settings 1. In the MicroStation window, choose Settings>View Attributes from the menu bar. 2. Select the following check boxes in the View Attributes dialog box.

These are the recommended settings when you save a seed file:

3. Click Apply and All, and then close the dialog box.

Drawing Border Reference Files A drawing seed file can have an optional border that contains any fixed border lines, title block lines, or fixed text. These items could be put into the seed file instead but using a separate border minimizes drawing file sizes by only storing the border once. There are several options for how to attach the drawing borders as reference files so the SupportModeler drawings can always locate their border: •

58

Attach the border using the SupportModeler configuration variable SM_BORDER (i.e. SM_BORDER:AutoDrawP.brd). The delivered

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Controlling Drawing Features using SM_DRW.DAT seed files use this method. Each time you open a project, SupportModeler updates the value of SM_BORDER to the \Seeds\ directory of the project so the drawing routines are always able to locate the border reference file. •

If the drawings are stored in a durable location that all machines can access, you can Save Full Path when you attach the border.

•

Or, you can add the border file path to the MicroStation configuration variable MS_RFDIR. Then, attach the reference files without saving full path.

Controlling Drawing Features using SM_DRW.DAT The drawing settings file, SM_DRW.DAT is a simple, self-commented ASCII file with several functions. For detailed instructions for each item, refer to the SM_DRW.DAT file itself. •

The SYMBOLOGY section defines the weights, styles. colors and levels for supports and reference models in the fabrication drawings.

•

The TEXT_NODES section assigns specific project and drawing properties from the support, or expressions that are evaluated on hte support, to specific, user-defined text nodes in the drawing seed file. It also defines text nodes to use for controlling the symbology of the various annotation callouts and controls the format of the bill of material description on the drawing.

•

The CONFIGURATION_VARIABLES section contains configuration variable definitions for controlling drawing behaviour on a project-basis.

•

The DRAWING_SEED_FILES section allows you to specify what drawing seed files are available to the user in the Drawing Page Layout property of the Active Support Parameters dialog.

✍ Each project has its own SM_DRW.DAT file in the project’s \Seeds\ directory.

Key-Plan or Location Plan The key-plan identifies the position of the active support relative to an existing column-grid or to the global origin of the 3D model. The keyplan is oriented relative to Plant North and is automatically generated and

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

59

SupportModeler™ for PDS™ Admin Guide Customizing the Fabrication Drawings annotated. The symbology, text size, and labelling of the key-plan can be controlled, but the overall format can not be customized. Relevant Settings for “Key-Plan or Location Plan”

Location

SUPMOD_DRAWING_KEYPLAN_TEXT

SM_DRW.DAT

SUPMOD_DRAWING_KEYPLAN_STYLE_USE_KP_TEXT

SM_DRW.DAT

SUPMOD_DRAWING_SUPPRESS_KEYPLAN_TEXT_SIZE_CHANGE

SM_DRW.DAT

SUPMOD_SUPPRESS_UNITS_IN_KEYPLAN_COORDINATES

SM_DRW.DAT

SYMBOLOGY_KEYPLAN

SM_DRW.DAT

SUPMOD_DRAWING_NORTH_ARROW_TEXT

SM_DRW.DAT

Associated SYMBOLOGY_KEYPLAN text node

Drawing seed files

PDS Grid File

Project Settings

Frameworks Plus Column Grid Defined For PDS projects with Frameworks Plus structural steel, the key-plan shows the position of the support relative to the nearest intersection of column-grid lines. This assumes that the Frameworks Plus structural grid has been exported to an ASCII file, and that the path of this grid file was specified during SupportModeler project setup. The key-plan is labeled showing the grid line labels of the intersecting grid lines.

No Column Grid

60

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Controlling Drawing Features using SM_DRW.DAT The key-plan shows the position of the support relative to the global origin of the support model.

Keyplan Coordinate Callout Leader A keyplan coordinate callout leader is placed into one or more drawing views to clearly identify which point on the support is being displayed in the keyplan. The callout shows global coordinates, regardless of whether a column grid is defined, or you can display some generic text instead. You can control the symbology, text, terminator size and shape, and what views the callouts are placed into. The callout leader uses the same symbology as notes, unless you choose the old-style KP text, in which case it uses the same symbology as BOM item callouts. Relevant Settings for “Keyplan Coordinate Callout Leader”

Location

SUPMOD_DRAWING_KEYPLAN_STYLE_USE_KP_TEXT

SM_DRW.DAT

SUPMOD_SUPPRESS_UNITS_IN_KEYPLAN_COORDINATES

SM_DRW.DAT

SUPMOD_DRAWING_KEYPLAN_CALLOUT_TERMINATOR_DIA

SM_DRW.DAT

SUPMOD_DRAWING_KEYPLAN_CALLOUT_TERMINATOR_SHAPE

SM_DRW.DAT

SUPMOD_DRAWING_VIEW_PANELS_FOR_KEYPLAN_COORDINATE_CALLOUT

SM_DRW.DAT

SYMBOLOGY_CALLOUTS and SYMBOLOGY_CALLOUT_TEXT or SYMBOLOGY_NOTES and SYMBOLOGY_NOTE_TEXT

SM_DRW.DAT

Associated SYMBOLOGY_xxx text nodes

Drawing seed files

SUPMOD_DRAWING_EASTING_INITIAL, SUPMOD_DRAWING_NORTHING_INITIAL and SUPMOD_DRAWING_ELEVATION_INITIAL

SM_DRW.DAT

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

61

SupportModeler™ for PDS™ Admin Guide Customizing the Fabrication Drawings Callout Leaders Callout leaders are automatically placed in the drawing to associate each component with the BOM line number that displays the description. The arrow of each leader points to the geometric center of the component, and the callout bubbles are placed in what the software thinks is a good location, attempting to avoid occupied space in the drawing.

The automatic format and position of the callout leaders cannot be customized, but they can be adjusted after the drawing is generated, using either the SupportModeler Move Leaders tool or MicroStation Move tools. One callout leader is placed in the drawing for every numbered line item that is displayed in the Bill of Materials. Because the format of the BOM is highly dependent on the BOM_SHOW_ASSEMBLIES setting in the drawing settings file, the number of callout leaders is also dependent on this setting. You can customize the bubble shape, the symbology, and which view panel to display the callouts in. In addition, you can filter which items get callout leaders and control the format of the BOM listing.

62

Relevant Settings for “Callout Leaders”

Location

BOM_SHOW_ASSEMBLIES

SM_DRW.DAT

SUPMOD_RENUMBER_STORED_BOM_ITEMS

SM_DRW.DAT

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Controlling Drawing Features using SM_DRW.DAT

Relevant Settings for “Callout Leaders”

Location

SUPMOD_DRAWING_BOM_ITEM_FILTER_EXPRESSION

SM_DRW.DAT

SUPMOD_DRAWING_VIEW_PANEL_FOR_CALLOUTS

SM_DRW.DAT

SUPMOD_DRAWING_CALLOUT_BUBBLE_SHAPE

SM_DRW.DAT

SYMBOLOGY_CALLOUTS and SYMBOLOGY_CALLOUT_TEXT

SM_DRW.DAT

Associated SYMBOLOGY_CALLOUTS and SYMBOLOGY_CALLOUT_TEXT text nodes

Drawing seed files

BOM_DESC property

Vendor Libraries

Storing Callout Leader BOM Item Numbers By default, when callout leaders are generated in the drawing, the item number is not stored anywhere and can not be reported on. If you wish to store the BOM item numbers with the support components, you can change the BOM_SHOW_ASSEMBLIES option in SM_DRW.DAT to either 4 or 41 (41 displays welds and notes within assemblies, 4 does not). See SM_DRW.DAT file as well. When this option is used, the software stores the BOM item number in a property called BOM_ITEM_NO that is included in all delivered definitiones. In addition, the SUPPORT object has a property HIGHEST_BOM_ITEM_NO in which the software stores the maximum BOM item number that is used in that support. Once a drawing is posted, the BOM item numbers will not change from drawing to drawing. Until posting, the BOM item numbers are renumbered starting at one for each new drawing.

June 20, 2003

Relevant Settings for “Storing Callout Leader BOM Item Numbers”

Location

BOM_SHOW_ASSEMBLIES options 4 and 41

SM_DRW.DAT

BOM_ITEM_NO property in components and assemblies

Vendor Libraries

HIGHEST_BOM_ITEM_NO in SUPPORT definition

SUPPORT.ITM

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

63

SupportModeler™ for PDS™ Admin Guide Customizing the Fabrication Drawings Notes SupportModeler automatically annotates the fabrication drawings with callout notes if the active support contains any note objects. Note objects define a specific text note at a specific location in the support. Notes are placed into the model as individual components or as part of assemblies. As delivered, notes are delivered in the SM_Utility library. The location can be adjusted after the drawing is generated, using either the SupportModeler Move Leaders tool or MicroStation Move tools. In order for SupportModeler to recognize an object as a note object, it’s item name must begin with SM_NOTE or USER_NOTE. The contents of the NOTE_TEXT property are displayed in the note on the drawing.. Relevant Settings for “Notes”

Location

SUPMOD_DRAWING_VIEW_PANEL_FOR_NOTES

SM_DRW.DAT

SYMBOLOGY_NOTES and SYMBOLOGY_NOTE_TEXT

SM_DRW.DAT

Associated SYMBOLOGY_NOTES and SYMBOLOGY_NOTE_TEXT Drawing seed files text nodes SM_NOTE or USER_NOTE item name

Vendor Libraries

NOTE_TEXT property

Vendor Libraries

Welding Symbols If the active support contains any weld objects, SupportModeler automatically annotates the fabrication drawings with welding symbols based on American Welding Society standards. Weld objects define a specific size and type of weld at a specific location in the support. Welds are placed into the model as individual components or as part of assemblies. As delivered, welds are delivered in the SM_Utility library and are included in some of the sample assemblies in the SM_Assembly and SM_TDSL1 libraries. The welding symbols are placed in the view that is displayed in View Definition Panel 1 with the arrows pointing to the geometric center of the weld object. Because the arrow point is relevant for determining the significance of the arrow side or other side types and sizes (also referred to as near side, far side), the placement location of weld objects in the support model is very significant. Refer to the SupportModeler User Guide for PDS for detailed information. The location can be adjusted

64

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Controlling Drawing Features using SM_DRW.DAT after the drawing is generated, using either the SupportModeler Move Leaders tool or MicroStation Move tools..

One welding symbol is placed in the drawing for every weld object in the active support. In order for SupportModeler to recognize an object as a weld object, it’s item name must begin with SM_WELD or USER_WELD. You can customize the symbology and font of the weld symbol but the automatic format of the welding symbols cannot be customized. Relevant Settings for “Welding Symbols”

Location

SUPMOD_DRAWING_VIEW_PANEL_FOR_WELDS

SM_DRW.DAT

SYMBOLOGY_WELDS and SYMBOLOGY_WELD_TEXT

SM_DRW.DAT

Associated SYMBOLOGY_WELDS and SYMBOLOGY_WELD_TEXT Drawing seed files text nodes SM_WELD or USER_WELD item name

Vendor Libraries

Required properties in weld objects. See the SupportModeler Library Customization Guide

Vendor Libraries

Automatic Dimensions SupportModeler can automatically dimension the fabrication drawings if the active support contains dimension points. Dimension points define a specific location in the support that must be called out as a dimension on the drawing. Dimension points can be included as a DIMENSION_PTS property in any component or assembly item, or a DIM_POINT object June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

65

SupportModeler™ for PDS™ Admin Guide Customizing the Fabrication Drawings can be placed into a support manually. As delivered, a DIM_POINT object is delivered in the Drawing category of the SM_Utility library. All of the dimensions are displayed as ordinate dimensions. You can move and stretch the dimensions in the drawing using MicroStation move or Modify Element tools. The symbology, and view panels can be controlled and you can suppress or enable auto dimensions on a project-wide basis.

✍ Dimension symbology is controlled using the MicroStation dimension

symbology settings in the drawing seed file, while the symbology of all other drawing annotation is controlled using symbology text nodes in the seed file..

Relevant Settings for “Automatic Dimensions”

Location

SUPMOD_SUPPRESS_AUTO_DIMENSIONS

SM_DRW.DAT

SUPMOD_DRAWING_VIEW_PANEL_FOR_MAIN_DIMENSIONS SUPMOD_DRAWING_VIEW_PANEL_FOR_SECONDARY_DIMENSIONS

SM_DRW.DAT

SUPMOD_DRAWING_SUPPRESS_COMMON_ORTHO_SCALE

SM_DRW.DAT

SUPMOD_SUPPRESS_UNITS_IN_AUTO_DIMENSIONS

SM_DRW.DAT

In MicroStation, the level, colour, weight, style and font settings in: Element > Dimensions > Dimension Lines Element > Dimensions > Extension Lines Element > Dimensions > Terminators Element > Dimensions > Text

Drawing seed files

Line Reference Labels For ganged or individual supports, SupportModeler can automatically annotate the fabrication drawings with line reference labels to identify each pipe line that is supported by the active support or its children. The line reference labels consist of an alpha callout label (A, B, C, ...) and a corresponding listing of what line A is, what line B is, etc. The line reference labels (A, B, C, ...) are positioned vertically above or below each support object - parent and children. You can control the symbology and the bubble shape and can enable or suppress line reference labels on a project-wide basis. Several properties are required in the SUPPORT object, and an entry is required in SM_DRW.DAT to map the line list on to a text node in the drawing. The location can be adjusted after the drawing is generated, using either the SupportModeler Move Leaders tool or MicroStation Move tools

66

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Controlling Drawing Features using SM_DRW.DAT Once a drawing is posted, the line reference letters will not change from drawing to drawing. Until posting, the line reference letters are regenerated starting at "A" for each new drawing. Relevant Settings for “Line Reference Labels”

Location

SUPMOD_DRAWING_ENABLE_LINEREF_LABELS

SM_DRW.DAT

SUPMOD_DRAWING_VIEW_PANEL_FOR_LINEREF_LABELS

SM_DRW.DAT

SUPMOD_DRAWING_LINEREF_BUBBLE_SHAPE

SM_DRW.DAT

SYMBOLOGY_LINEREF and SYMBOLOGY_LINEREF_TEXT

SM_DRW.DAT

Associated SYMBOLOGY_LINEREF and SYMBOLOGY_LINEREF_TEXT text nodes

Drawing seed files

LINE_REF_LABELS_CHILDREN property in SUPPORT definition

SUPPORT.ITM

LINE_REF_LABELS_CHILDREN

SM_DRW.DAT

Associated LINE_REF_LABELS_CHILDREN text node

Drawing seed files

Drawing Revision Block Automation The delivered core libraries and drawing seed files include an example of how you can automate the population of the revision block on the fabrication drawings. A property "Drawing Revision" is displayed to the user in the Active Support Parameters dialog box with three choices: "none", 0 and 1. In addition, a "Drawn By" prompt allows the user to fill in their initials. The user enters their initials and then changes the Drawing Revision property in a stepwise fashion -- from "none" to "0" and then to "1". Rules in the SUPPORT item definition then set several property values in the SUPPORT.ITM, which are then displayed on text nodes in the drawing based on entries in SM_DRW.DAT. As delivered, the example library fills in the revision number, description, date, and initials. For example if the user has entered his initials (RNR) in the "Drawn By" prompt and then changes the "Drawing Rev" value from "none" to "0" on July 21nd, 2001, the revision block will read as follows: 0

June 20, 2003

Released for Review

21 Jul 01

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

RNR

67

SupportModeler™ for PDS™ Admin Guide Customizing the Fabrication Drawings Then, if the user changes the "Drawing Rev" value from "0" to "1" on July 24, 2001, the revision block will read as follows: 1

Released for Construction

24 Jul 01

RNR

0

Released for Review

21 Jul 01

RNR

Note that the text nodes required for this functionality have only been included on the delivered the B_size drawing sheet. Customization of this functionality is carried out by editing the SUPPORT.ITM and by creating the required text nodes and SM_DRW.DAT entries. The revision number can automatically be used when posting the drawing by setting the SUPMOD_POST_REVISION configuration variable to the REV property. Relevant Settings for “Drawing Revision Block Automation”

Location

All properties beginning with REV in SUPPORT def

SUPPORT.ITM

All rules starting with "if REV..." in SUPPORT def

SUPPORT.ITM

REV_* entries in TEXT_NODES section

SM_DRW.DAT

Associated text nodes

Drawing Seed Files

SUPMOD_POST_REVISION

SM_DRW.DAT

SUPMOD_LATEST_POSTED_DRW

SM_DRW.DAT

Automatic Detail Cells SupportModeler can automatically add detail cells to the fabrication drawings. Cell objects define a specific cell library and cell name and are placed into the model as individual components or as part of assemblies. As delivered, a cell object is delivered in the SM_Utility library.

✍ Cell objects appear as zero-length lines in the model and their location within the support is not important..

In order for SupportModeler to recognize an object as a cell object, it’s item name must begin with SM_CELL or USER_CELL. The

68

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Controlling Drawing Features using SM_DRW.DAT CELL_LIBRARY and CELL_NAMES properties are used by the software to determine which cell to place on the drawing. Values for CELL_LIBRARY

Effect of Those Values

Full Path and Filename i.e. P:\Proj\Cells\SupMod.cel

Uses the specified library.

DEFAULT

Uses the project’s default cell library, which is assumed to be called DEFAULT.CEL and is assumed to be located in the project’s \Seeds\ directory.

SupportModeler Library Uses a cell library found in that SupportModName eler library’s folder, named the same as the Supi.e. SM_ANVIL, or SM_Utility portModeler library. For example, if set to SM_Utility, the software would use ...\Program Files\SupMod\Lib\SM_Utiltiy\SM_Utility.cel. This setting is particularly useful when an assembly or component library has detail cells associated with certain items and you want to store them with the library.

The description of the cell in the cell library is used to label the view. If several cell objects in a support all point to the same cell in the same library, that cell will only be displayed once. The drawing seed file must have additional view panels set up to hold the detail cells. As delivered, view panels 1 to 5 are used for user-selected views of the support and there are properties defined in the SUPPORT item file for panels 1 to 5 so that the user can specify views in the Active Support Parameters dialog. For detail cells, add additional view panels to the drawing seed files, numbered 6 and higher for displaying detail cells.

✍ The cell library itself should contain 2d or 3d MicroStation cells and you should ensure that you Drop Complex Status on dimensions. Otherwise the dimensions will adjust themselves in the drawing to meaningless values. The cells should not be dimension-driven. The cells should be graphic cells, not point cells.

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

69

SupportModeler™ for PDS™ Admin Guide Customizing the Fabrication Drawings

✍ Maximum number of view panels in a drawing is now 20 (increased from previous limit of 5 in versions prior to Version 7.2.3)

Relevant Settings for “Automatic Detail Cells”

Location

SUPMOD_DRAWING_STARTING_VIEW_PANEL_FOR_DETAIL_ CELLS

SM_DRW.DAT

SYMBOLOGY_VIEWLABELS

SM_DRW.DAT

Associated SYMBOLOGY_VIEWLABELS text node

Drawing seed files

SM_CELL or USER_CELL item name

Vendor Libraries

CELL_LIBRARY and CELL_NAME properties

Vendor Libraries

Automatic Pipe End Symbol on Drawing SupportModeler can automatically add a pipe end symbol of your choice to the fabrication drawings. The software places a MicroStation cell at the pipe centerline on views that are along the pipe. There are several settings and requirements for this to work:

1. In SM_DRW.DAT set the configuration variable SUPMOD_DRAWING_PIPE_CL_CELL_LIBRARY to the full path and name of the cell library that contains the desired cell. Or, if you set this variable to DEFAULT, the software will look for a cell library called DEFAULT.CEL in the \Seeds\ directory of the active project. As delivered, the Tutorial_PDS project, contains a DEFAULT.CEL library with a few example cells. 2. In SM_DRW.DAT set the configuration variable SUPMOD_DRAWING_PIPE_CL_CELL_NAME to the name of

70

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Customizing the Drawing-Control Properties in the SUPPORT definition the cell to use for the pipe centerline symbol. The delivered default library contains two sample cells PIPECL and HAPPY. 3. In SM_DRW.DAT set the configuration variable SUPMOD_DRAWING_ROTATE_ORTHO_VIEWS_BY_ANGL E to FRONT_ALONG_PIPE. The automatic pipe end symbol only works if this is set. 4. For a specific support to get automatic pipe end symbols on the drawing, the support must be correctly located on a pipe and at least one drawing view in the Active Support Parameters dialog must be set to FRONT or BACK.

The cell libraries are standard MicroStation cell libraries, and the cell to be placed should be a 2D graphic (not point) cell with equal width and height.

Customizing the Drawing-Control Properties in the SUPPORT definition For each support, the drawing format can be controlled using properties in the Active Parameters dialog box. These properties are defined in the SUPPORT definition and can be customized in the SUPPORT.ITM file. The settings for these properties, in combination with the formats, borders and seed files, determines the final appearance of the drawing. For more information, refer to the SupportModeler Library Customization Guide.

Drawing-Control Active Parameters The drawing-control Active Parameters are all properties of the SUPPORT.ITM as shown in the following table. In each case, the Default value and the User Prompt can be changed.

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

71

SupportModeler™ for PDS™ Admin Guide Customizing the Fabrication Drawings

Active Parameters Description View in Panel 1 View in Panel 2 View in Panel 3 View in Panel 4 View in Panel 5 Also see section “Automatic View Alignment Along and Across Pipe” on page 73

Select from FRONT, BACK, RIGHT, LEFT, TOP, BOTTOM, ISOMETRIC, RIGHT ISO, KEYPLAN, NONE, SAVED VIEWS... If a certain view panel does not exist in the drawing seed file, the View for that panel is ignored. KEYPLAN displays the location of the support relative to: • Column grid lines • Global origin for projects with no grid lines defined If no column grid lines are defined, the global origin is used. If a support is not located within the extents of the column grid, the key plan is displayed in global coordinates. SAVED VIEWS can only be used in view panels that have not been specified for annotation. By default, only view panel 1 is used for annotation but your administrator may have set configuration variables to place annotation in other views as well, or instead. If the pull-down list for a view Panel does not have the saved views at the end of the list, saved views cannot be used in that view. The saved view of the model, with no reference files, is fit into the view panel and annotated with the Description that was entered when the view was saved. See the section on Using Saved Views in the Drawing for more information. You can customize the available options by editing the SUPPORT.ITM. The property names for these prompts are PANEL1, PANEL2, etc. For each panel, you can change the pull-down lists, remove the prompts, pre-specify the views for each panel, or create rules that set one panel based on another.

72

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Customizing the Drawing-Control Properties in the SUPPORT definition Active Parameters Description Drawing Page Layout

• SM_ASIZE A sample 8 1/2" x 11", portrait border file. • SM_BSIZE A sample 17" x 11", landscape border file. You can customize the borders and change what borders show up in the list.

Support Drawing Notes

You can easily change the list of seed files that is presented to the user by editing the SUPPORT definition and change the ORIENTATION property. Text field for entering a single drawing note that is specific to this support You can customize the behaviour of this property, change it to a pull-down list, or add rules to generate notes automatically based on other properties.

Automatic View Alignment Along and Across Pipe In versions prior to Version 7.2.3, when the user set the View in Panel XX properties, the view directions were always relative to MicroStation global directions, with FRONT meaning North, RIGHT meaning East, etc. In Version 7.2.3 and later, you can change this so that these views are relative to the direction of the supported pipe. In this mode, FRONT and BACK mean along the pipe, while RIGHT and LEFT mean across the pipe.

➤ To implement a;utomatic view alignment: 1. In SM_DRW.DAT in the project’s \Seeds\ directory, edit the configuration variable: SUPMOD_DRAWING_ROTATE_ORTHO_VIEWS_BY_ANGLE

2. Set the value of this variable to FRONT_ALONG_PIPE and make sure it is uncommented. 3. Save and close SM_DRW.DAT 4. Start SupportModeler and open the project. 5. Make a support active and generate a fabrication drawing.

✍ A FRONT or BACK view should now be aligned with the direction of

the pipe. A RIGHT or LEFT view should now be a view across the pipe. TOP and BOTTOM views are aligned with the pipe direction while ISOMETRIC and RIGHT ISO views are not changed by this setting.

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

73

SupportModeler™ for PDS™ Admin Guide Customizing the Fabrication Drawings

✍ This is extremely useful for automating fabrication drawings and minimizing touch up, especially in plants with skewed pipe.

74

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Post-Processing in PDS

Post-Processing in PDS This section describes the customizations that you may have to perform in both SupportModeler and PDS to properly handle the post-processing of supports and generation of deliverables.

Isometric Drawing Support Labels ISOGEN provides the ability to automatically annotate each support with an identifying label and SupportModeler supports work seamlessly with this functionality. When you use the Update PDS operation in SupportModeler. logical supports are created in the PDS piping models with pdtable_80 data defined by SM_PDS.DAT. These logical supports drive the ISOGEN annotation. You can completely control the format of the support labels. Relevant Settings for “Isometric Drawing Support Labels”

Location

ISOGEN_OPTIONS_BLOCK settings 64 - pipe support labeling TYPE_1_LABELS

Isogen options file Isogen options file Properties and rules in SUPPORT definition SUPPORT.ITM SUPPORT_DATA section SM_PDS.DAT Isometric Drawing Labels in PDS Label Descrip- PDS Reference tion Library Data Manager

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

75

SupportModeler™ for PDS™ Admin Guide Post-Processing in PDS ➤ To use default support labels The default support labels consist of an ISOGEN item number and the pipe_support_no in pdtable_80 (which is populated with the Support ID from SupportModeler). For ganged children and/or commodity supports, which do not generally have meaningful support_ID’s in SupportModeler, these labels are usually not suitable. .

1. In SM_PDS.DAT, in the SUPPORT_DATA section, the SupportModeler SUP_ID must be mapped to the PDS pipe_support_no attribute. 2. In the ISOGEN options file, option 64 in the ISOGEN OPTIONS BLOCK should be set to 1 or 2, not 0, to enable support names on the ISO.

➤ To suppress display of the pipe_support_no This option allows you to turn off the default display of the pipe_support_no from pdtable_80 (which is populated with the Support ID from SupportModeler) and is often used when the complete support description will be displayed in the material listing in the border of the ISO drawing. This option works for all types of supports - tagged, commodity and ganged - but does not provide much information in the label itself.. You can use this in combination with custom support labels, as described in the procedure “To define a custom support label” on page 77.

1. In the ISOGEN options file, set option 64 in the ISOGEN OPTIONS BLOCK to 0 to suppress support names on the ISO. 2. That’s all folks!

76

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Isometric Drawing Support Labels ➤ To define a custom support label Ideal for all supports, this mode gives you complete control of what appears in the support label. When used in combination with SM_PDS.DAT and custom rules and properties in the SUPPORT definition, you can create very intelligent, adaptive labels for different types of supports. This mode is the most flexible and can handle tagged supports and commodity, ganged parents and children.

1. Remove the pipe_support_no from the ISO label using the procedure “To suppress display of the pipe_support_no” on page 76. Otherwise, the pipe_support_no will be displayed above your custom label for all supports. 2. Use the PDS Reference Data Manager > Label Description Library Manager to create a new Isometric Drawing Label that defines the new pipe support label. The label can be multi-line and can combine hard-coded text with attribute data from pdtable_80.

For example, you might create a label 901 defined as follows: "PIPE SUPPORT - " + DETAILS_FOR_FIELD + "-" + CONSTRUCTION_STAT

3. In the ISOGEN options file used with your PDS project, add the following new entry to the TYPE_1_LABELS section: 5, 80, 4, 901

Where 5 80, 4 901

Means The pipe supports The fourth attribute in pdtable_80, which is MODEL_CODE_LOG The number of the new Isometric Drawing Label created in step 1.

4. After you add this line, make sure you increase the line count by 1 for the TYPE_1_LABELS section. 5. Edit the SUPPORT_DATA section of SM_PDS.DAT to ensure that SM will write values into the desired columns in pdtable_80 during Update PDS. June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

77

SupportModeler™ for PDS™ Admin Guide Post-Processing in PDS

Material Lists on Piping Isometric Drawings ISOGEN provides the ability to automatically display material descriptions for supports on the piping isometric drawings and SupportModeler supports work seamlessly with this functionality. When you use the Update PDS operation in SupportModeler. logical supports are created in the PDS piping models with pdtable_80 data defined by SM_PDS.DAT. These logical supports drive the ISOGEN annotation. You can completely control the format of the material description on the ISO. Relevant Settings for “Material Lists on Piping Isometric Drawings” INTERGRAPH_OPTIONS_BLOCK settings 37 - alternate material description index 54 - pipe_support_no or commodity_code as index PDS Pipe Support Material Description Library ALTERNATE_DESCRIPTION_INDEX Properties and rules in SUPPORT definition SUPPORT_DATA section PDS Label Description Library

Location Isogen options file

PDS Reference Data Manager Isogen options file SUPPORT.ITM SM_PDS.DAT PDS Reference Data Manager

➤ To use default pipe support material listings The default pipe support material listing in ISOGEN uses the pipe_support_no from pdtable_80 as an index into the PDS Pipe Support Material Description Library. to look for a description. Since SupportModeler writes the unique property support ID into pipe_support_no, and these unique support ID’s do not have any

78

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Material Lists on Piping Isometric Drawings corresponding entries in this material description library, the default material listing always fails and should not be used. In the following example, PS-ACC-01 is the support ID from SupportModeler that has been put into the pdtable_80 pipe_support_no attribute during the Update PDS operation.

You could manually enter material descriptions into the description library for each support ID but this is cumbersome and unnecessary. Instead, use one of the other automatic options explained below. If you already have many entries in the material description library that you would like to continue using, see the procedure “To use the Alternate Description Index” on page 81

➤ To use commodity code as the material description index. This commonly-used method demonstrates how to automate the material list, while requiring only a single entry in the PDS Pipe Support Material Description Library. It relies on the BOM_DESC property of the SUPPORT definition which is automatically set based on the placement mode - for tagged supports, it automatically displays the support ID, while for commodity supports, it displays the BOM description. An ISOGEN option switch changes the index into the Material Description Library from pipe_support_no to

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

79

SupportModeler™ for PDS™ Admin Guide Post-Processing in PDS commodity_code and SupportModeler writes appropriate data into pdtable_80. In the following example, PS-ACC-01 is a tagged support ID, and the U-Bolts are commodity supports.

1. Choose a pdtable_80 attribute to store the material description for each SupportModeler pipe support. This attribute should be a character attribute with a generous length (such as 300 characters, although smaller will work). Many companies use the existing attributes DETAILS_FOR_SHOP, or DETAILS_FOR_FIELD, or add a new attribute to pdtable_80 called BOM_DESC. 2. Using PDS, choose Reference Data Manager > Label Description Library Manager to create a new Isometric Drawing Label that points to the chosen attribute in pdtable_80

For example, create a new label 902 that displays the DETAILS_FOR_SHOP attribute from pdtable_80. 3. Using PDS, choose Reference Data Manager > Material Description Library Manager to add a single entry to the PDS Pipe Support Specialty Material Description Library that maps the text "PSL" to the number of your new PDS isometric label.. Example:

PSL

'[902]'

Where 902 is the number of the new Isometric Drawing Label created in step 2. Remember to copy the Unapproved label library to the Approved label library, if needed. 4. In the PDS ISOGEN options file, change option 54 in the INTERGRAPH OPTIONS BLOCK to 1 which tells ISOGEN to use the commodity_code in pdtable_80 as the index into the PDS Pipe Support Material Description Library. The delivered default value is 0 which means use the pipe_support_no. 5. Ensure that the SUPPORT_DATA section of SM_PDS.DAT contains an entry that writes "PSL" into the COMMODITY_CODE attribute of pdtable_80.

80

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Material Lists on Piping Isometric Drawings

✍ You don’t have to use the text "PSL" as long as you write the

same text into commodity_code as you enter in the Pipe Support Material Description Library.

6. Ensure that the SUPPORT_DATA section of SM_PDS.DAT contains an entry that writes the BOM_DESC of the support into the PDS attribute in pdtable_80 you chose above when defining your isometric label. 7. Save all your changes.

✍ Remember that you must Update PDS in order for these changes to take effect. Update PDS writes logical supports into the PDS piping models and these logicals create supports on the ISO.

➤ To use the Alternate Description Index The previous procedure forces ISOGEN to always use the commodity_code "PSL" as the index into the material description library. This assumes that there are no entries in the library that you want to use. The alternate description index allows you to blend the two methods and is suited to a combination of: • PDS-created supports with non-unique support numbers that correspond to entries in the pipe support Specialty Material Description Library, and • SupportModeler-created tagged supports with unique support numbers that are NOT in the material description library. If ISOGEN fails to find the pipe_support_no (or commodity_code INTERGRAPH option 54 is set to 1) in the material description library, it uses the alternate description. In the following example, the SHOE and UBOLTS are PDS-created logcial supports which use

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

81

SupportModeler™ for PDS™ Admin Guide Post-Processing in PDS non-unique pipe_support_no’s, and the PS-ACC-01 is a SupportModeler tagged support..

1. In the ISOGEN options file, change option 37 in the INTERGRAPH OPTIONS BLOCK to 1which tells ISOGEN to enable the use of the ALTERNATE DESCRIPTION INDEX into the PDS pipe support Specialty Material Description Library. The delivered default value is 0. 2. In the ISOGEN options file, in the ALTERNATE DESCRIPTION INDEX section, add an entry that tells PDS what Isometric Drawing Label to use as the index into the material description library. For example:5, 80, 0, 972 says use label number 972 as the alternate index. This will only be used if the primary index pipe_support_no is not found in the library. 3. Using PDS, choose Reference Data Manager > Label Description Library Manager to create a new Isometric Drawing Label that evaluates to a fixed text.

For example, edit label 972 to have the text value "PSUPPORT". This is the alternate index into the material description library. 4. Choose a pdtable_80 attribute to store the material description for each SupportModeler pipe support. 5. Create a new PDS Isometric Drawing Label that points to the chosen attribute in pdtable_80

For example, create a new label 902 that displays the DETAILS_FOR_SHOP attribute from pdtable_80. 6. Using PDS, choose Reference Data Manager > Material Description Library Manager to add a single entry to the PDS Pipe Support Specialty Material Description Library that maps the

82

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Material Lists on Piping Isometric Drawings text "PSUPPORT" to the number of your new PDS isometric label, optionally adding additional text. Example:

PSUPPORT

'SPECIAL PIPE SUPPORT, SEE DETAIL DRAWING [902]'

7. Set the primary material description index to pipe_support_no by setting option 54 in the INTERGRAPH OPTIONS BLOCK to 0. 8. Save all your changes.

✍ Remember that you must Update PDS in order for these changes to take effect. Update PDS writes logical supports into the PDS piping models and these logicals create supports on the ISO.

➤ To display the parent support ID for both parent and child supports. For ganged supports, you can display the parent’s support ID for both parent and children. It relies on the PARENT_SUP_ID property of the SUPPORT definition which is automatically set based on the ganged status.

1. Follow the procedure “To use commodity code as the material description index.” on page 79 with the following changes. 2. Ensure that the SUPPORT_DATA section of SM_PDS.DAT contains an entry that writes the PARENT_SUP_ID property into a suitable attribute in pdtable_80, for example DETAILS_FOR_FIELD. 3. When creating the isometric drawing label, use the new pdtable_80 attribute DETAILS_FOR_FIELD instead of or in addition to the other attributes and text

For example, create label 902 with a definition DETAILS_FOR_SHOP + ", COMMON SUPPORT " + DETAILS_FOR_FIELD June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

83

SupportModeler™ for PDS™ Admin Guide Post-Processing in PDS ➤ To make the material listing adaptive: You can make the format of the material listing change automatically based on user prompts, pipe segment attributes, the kind of components in the support, ganged status, placement mode, or any combination of these conditions. 1. Edit the libraries, particularly the SUPPORT definition in SUPPORT.ITM to add or change properties and rules. You need to end up with properties that contain appropriate text for display on the ISO. For more information, see the SupportModeler Library Customization Guide and the JSpace Concepts and Technical Reference guide. 2. Add appropriate entries to SM_PDS.DAT to transfer the SUPPORT properties to pdtable_80 during Update PDS. 3. Edit the PDS piping isometric labels and ISOGEN settings to display these properties, or combinations of these properties, in the material list on the ISO.

Orthographic Drawing Generation The names and locations of the SM models containing the detailed support graphics are entered in the PDS Project Control database upon creation. They can be attached and displayed in orthographic drawings similarly to any non-PDS MicroStation file. You can use standard PDS tools to annotate the PDS logical supports that SupportModeler creates.

Design Review DRV Label Data Files Design Review uses the SupportModeler MicroStation models (*.dgn) for the graphics to display during a Design Review session. In addition, for intelligent review of the graphics, an ASCII label data file is required as well. SupportModeler automates the creation and management of the label data files for each model. When you create a SupportModeler model, a dummy label data file, with the file extension DRV, is created in the same directory as the new model. For information about creating models, see “Adding a New Model” on page 45. If you really want to, you can suppress the creation of this dummy file using the configuration variable SUPMOD_SKIP_DRV, defined in C:\Program Files\SupMod\mdlapps\config\mslocal.cfg. During the Update PDS operation, the DRV label data file is populated with properties of each support as specified in the SUPPORT_OBJECTS and COMPONENTS_&_ASSEMBLIES sections of the SM_PDS.DAT

84

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Interference Detection file. For more information, see the section “Support Properties for Display in Design Review” on page 40.

DRI Design Review Interface file In PDS, the Design Review Integrator is used to create the Design Review Interface (DRI) file. This ASCII file contains a list of all the design files, label data files and other files that will be used during the Design Review session. By including the Supports discipline when you create the DRI file, the SupportModeler DGN files are automatically included in the DRI file. You created the Supports discipline during SupportModeler project setup - see “Create a Supports discipline in PDS” on page 16. PDS does not know about the SupportModeler-created DRV label data files so SupportModeler includes a tool to add the label data files to the DRI file.

➤ To Update the DRI File to add DRV label data file names 1. Open SupportModeler and open the SupportModeler project. 2. Select File > Update DRI File from the SupportModeler menu.

A browse dialog is displayed. 3. Browse to the DRI file for the PDS project associated with this SupportModeler project and click Open.

The software reads each DGN line in the DRI file and, if the DGN is a SupportModeler model name, it adds the appropriate DRV label data file name to that line. A message is displayed indicating how manu lines were updated.

✍ This operation can be automatically batched and scheduled using the SupportManager product, available separately.

Interference Detection Generating Interference Envelope Files In PDS, the Interference Manager (PD_Clash) is used to detect interferences between supports and other plant items. In SupportModeler Version 7.2.3, intelligent interference envelopes are built for SM model files from within SupportModeler. The envelope files (*.env) are created in the same folder as the pipe support model so PDS and PD_Clash can find the envelopes. Interference detection is then performed as usual by using PDS clash detection.

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

85

SupportModeler™ for PDS™ Admin Guide Post-Processing in PDS ➤ How to Create an Interference Envelope File 1. The Interference Envelope file is created when the user selects File > Update PDS from the SupportModeler menu. Envelope files can also be created using Update PDS in SupportManager. 2. An envelope file is created in the same folder as the model, but with an *.env extension. Envelopes will be generated in this file for each support in the model that contains physical items.

A message is displayed indicating the file name and how many support envelopes were created in the file.

✍ There are several settings in the SM_PDS.DAT file which allow you to

customize the information written to the clash envelope file. You can control the name and description of each support envelope, and can filter which components are to be included or excluded from the envelopes, based on script language expressions. Relevant Settings for “Interference Detection”

Location

Properties and rules in SUPPORT definition CLASH_ENVELOPE_SETTINGS section

SUPPORT.ITM SM_PDS.DAT

✍ This operation can be automatically batched and scheduled using the Update PDS operation in the SupportManager product, available separately.

Interference Checker Interference Checker version 07.02.01.00 will now handle supports in a manner similar to PDS Pipe Supports. This should eliminate the false reporting of clashes between the Pipe and the Supports attached to them. To enable this new feature you must define the environment variable PDS_PF_DISCIPLINE. For example: Set PDS_PF_DISCIPLINE=X

Where x is the discipline index number from the project's PDtable_111 of the Pelican Forge discipline.

✍ A support and its components (for which the support cone is properly on the pipe segment centerline) will NEVER produce a clash with the pipe that it supports. The drawing produced with SupportModeler should be used as a final check in these cases.

86

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Stress Neutral File Generation

Stress Neutral File Generation The SM interface writes attributes into pdtable_80 that are used to extract information to a stress neutral file. As a minimum, the location and support ID is written and is displayed in the neutral file. Depending on the setup at your site, you may have to customize the interface to populate pdtable_80 with the appropriate attributes.

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

87

SupportModeler™ for PDS™ Admin Guide Customizing Reports

Customizing Reports All attribute data of the support, components and assemblies are included in the project database located in the root directory of the SupportModeler project. This information is extracted into a separate database (SupportModeler Reports.MDB) for reporting. Generating reports is covered in the SupportModeler Users Guide. The extraction of data from the project database into the reporting database (SupportModeler Reports.MDB) is controlled by a settings file -SM_RPT..DAT. This is normally located in the project seeds directory. This file controls the following functions: •

Report definitions -- one definition for each report generated

•

Filters -- each report can contain filters to define which items are included in the report

•

Attribute mapping -- each column in the extracted database can be mapped to an attribute or an expression from the project database.

The settings file contains multiple report definitions. Each report definition contains the following sections: REPORT_BEGIN - keyword marks the beginning of a new report definition. Record Format: report_name, type_of_item, neutral_file_name, criteria_expression where: •

report_name - name that should be displayed to the user for selecting this report to generate

•

type_of_item - either SUPPORTS or ITEMS

•

neutral_file_name - filename for the *.dat ASCII neutral output file that will be generated for this report. "sce" and "spe" are reserved for pre-defined error reports.

•

criteria_expression - expression to be evaluated on each item to determine if it should be included in the output file

COLUMNS - keyword marks the beginning of the column definitions for the report. Record Format: column_name, column_type, column_size, column_expression

88

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Customizing Reports where: •

column_name - name that should be given to this column in the output file

•

column_type - a text string that represents the type of column -- valid values are int, long, float, double, number, string

•

column_size - for string columns, enter the number of characters (max 254) - size is ignored for other column types

•

column_expression - property name or expression to output to this column. This can include any built-in function as outlined in the SupportModeler Library Customisation Guide.

✍ Note that if a property name is used within an expression, it must use the

GetSProp or GetNProp functions. If you just want to use a single property name for the expression, you can enter the property name itself. REPORT_END - keyword marks the end of this report definition These .DBF neutral files are read into the reporting database -SupportModeler Reports .MDB. This is a Microsoft Access database. If this database resides in the same directory as the export neutral files, they will be automatically linked into tables in the database. Otherwise, you can manually re-link the tables using a linked table manager within Access. Any further formatting or filtering can be carried out within this database using standard Microsoft Access tools.

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

89

SupportModeler™ for PDS™ Admin Guide Appendix A

Appendix A Oracle ODBC Setup ODBC is an interface between the database and many application programs. SupportModeler uses ODBC to read and write to the PDS database. An ODBC driver must be installed on each client machine for the database that you are using.

Installing Oracle Client Software This section is intended to help administrators set up Oracle ODBC drivers to allow SupportModeler to work with PDS projects using Oracle. The procedures are for Oracle version 8. setup must be performed on all workstations running the W This SupportModeler PDS interface.

➤ To install the Oracle client software 1. On the Oracle installation CD, double-click setup.exe. 2. Select Custom Installation. 3. Select at least the following items to install:

• Java Runtime • Oracle Installer • Oracle Enterprise Manager • Oracle Enterprise Manager Docs (may not be available for version 8.04) • Oracle Net8 • Oracle 8 ODBC driver • Required Support Files for Oracle 8

➤ To set up an Oracle service name on each client machine service name must be installed once for each database accessed. This W Acomponent provides an interface between the ODBC data sources and the actual database server. 1. From the Start>Programs menu, run Oracle Net8 Assistant. 2. Double-click Service Names. 3. Click the plus (+) sign on the tool bar to add a new service name.

90

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003

SupportModeler™ for PDS™ Admin Guide Oracle ODBC Setup 4. Answer the questions in the wizard to add a new service name to your Oracle server, your PDS database. 5. When you click the Finish button in the wizard, make sure that your new Service Name is displayed. 6. Test the connectivity of the Service Name by choosing Tools>Test Service Name Connectivity. 7. Exit and save the data in the Net8 Assistant.

➤ To create ODBC data sources for PDS databases set of two data source names must be set up for each PDS project W Aaccessed by SupportModeler. These provide the actual linkage between SupportModeler and the PDS databases. 1. In Control Panel, double-click ODBC 32 to add two new ODBC data source names. 2. Add a new data source pointing to the PDS Project Control Database using the Microsoft ODBC Driver for Oracle.

Explanations for the fields are: Field

Description

Data Source Name

The DSN for this database, which must match the SupportModeler project definition Your description A valid user name for this database that corresponds to the Project Control Database schema for the PDS project The service name that you created previously with the Net8 Assistant

Description User Name

Connect String

3. Add a new data source pointing to the PDS Design Database using the Microsoft ODBC Driver for Oracle.

Explanations for the fields are: Field

Description

Data Source Name

The DSN for this database, which must match the SupportModeler project definition Your description A valid user name for this database that corresponds to the Design Database schema for the PDS project The service name that you created previously with the Net8 Assistant (the same name used in Step 2)

Description User Name

Connect String

June 20, 2003

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

91

SupportModeler™ for PDS™ Admin Guide Appendix A 4. Using the Oracle ODBC Test utility, test the new data source names by performing the following operation: a. b. c.

Start the application. Click Connect. Type a password. The utility reports if the connection is successful.

Database Server Setup Normally, the server has all the software required to handle ODBC clients. However the server may need to have a listener installed and set up. This system service accepts queries from the ODBC clients.

➤ To install and set up the Listener 1. Make sure that you have the Oracle Net 8 Server installed on the server. 2. Make sure that the OracleTNSListener80 is running as a service on the server. 3. Edit the \orant\net80\admin\listener.ora file and make sure that the service name (as set up on the client machines) is included in the list of ODBC clients to listen for. 4. Stop and start the OracleTNSListener80 service to reload the listener.ora file.

✍ The password is usually "oracl".

92

SupportModeler™ for PDS™ Admin Guide, Version 7.2.3

June 20, 2003