3DTRAN

PDS 3D VAX to Workstation Translation (PD_3DTRAN)
Reference Guide
August 1999 DEA503781
For PDS version 06.04.00.**
This document replaces DEA503772.
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. The information and the software discussed in this document are subject to change without notice and should not be considered commitments by Intergraph Corporation. Intergraph Corporation assumes no responsibility 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.
Trademarks
CLIX, Intergraph, and RIS are registered trademarks of Intergraph Corporation. SEE is a trademark of Intergraph Corporation. All other brands and product names are trademarks of their respective owners.
Copyright
1999 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 and trade secret law and may not be provided or otherwise made available without proper authorization. RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of The Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c) (1) and (2) of Commercial Computer Software Restricted Rights at 48 CFR 52.227-19, as applicable. Unpublished rights reserved under the copyright laws of the United States. Intergraph Corporation Huntsville, Alabama 35894-0001
_ _______________
If You Need Assistance
Intergraph Online
Our web site brings you fast, convenient, up-to-the-minute information about Intergraphs products, services, and direction. Our web address is: http://www.intergraph.com
If You Need Assistance
Telephone Support
All Intergraph products are delivered with a 30-day warranty for full coverage of physical media. In the United States, call Intergraphs standard support number at 1-800-633-7248 from 7:00 AM to 7:00 PM CST, Monday through Friday, except holidays. If you are outside of the United States, please call your local Intergraph office. The most upto-date list of international offices and distributors is available on the web at http://www.intergraph.com. Please have the following information available when you call: The products serial number. This can be found on the license agreement or by using the About command in the product. Your name and telephone number. The products name. Your CPIN number and service number. A brief description of the problem.
_ _______________
Intergraph Directory
The following numbers are only valid in the United States unless otherwise indicated. If you are outside the United States, please call your local Intergraph office.
Intergraph General Information

U.S. 1-800-345-4856 Canada 1-800-461-5297 All countries 1-256-730-2000
Customer Response Center (U.S. Only)

Customer Support 1-800-633-7248 U.S. Customer Care Center 1-888-779-3824 FAX 1-800-239-2972
Training Registration (U.S. Only)

1-800-240-3000
Regional Sales Information (U.S. Only)

1-800-240-1000
Mailing Address
Intergraph Corporation Huntsville, Alabama 35894-0001 U.S.A. You can also reach us by electronic mail at info@intergraph.com.
_ _______________
Educational Media Contacts
We are constantly working on updates and improvements to the documents and other educational media. If you have any suggestions on where we can improve the documentation or where you think more information is needed, let us know. You can reach us by: Mail Intergraph Corporation Manager, PBS Documentation GD3006 Huntsville, AL 35894-0001 PBS Documentation 1-256-730-3300 pds_doc@metron.b30.ingr.com
Educational Media Contacts
FAX
Electronic Mail
_ _______________
_ _______________
Table of Contents
If You Need Assistance ........................................................................................................ Intergraph Directory ............................................................................................................. Educational Media Contacts .......................................................................................... Preface ................................................................................................................................................. Document Purpose ................................................................................................................ Document Prerequisites / Audience ...................................................................................... Related Documents/Products ................................................................................................ About this Document ............................................................................................................ Additional Information ......................................................................................................... General Conventions .................................................................................................................... Keyboard Conventions ......................................................................................................... Terminology ......................................................................................................................... Summary of Technical Changes ......................................................................................................... Version 06.00.00.00 Changes ............................................................................................... 1. Translating VAX PDS 3D Data ................................................................................................... 1.1 VAX Setup .......................................................................................................................... 1.2 Workstation Setup ............................................................................................................... 2. Translating Project Environment and Design Data ...................................................................... 2.1 2.2 2.3 2.4 Defining Discipline Data ..................................................................................................... Translating Seed Data ......................................................................................................... Translating Models .............................................................................................................. Translating Drawings .......................................................................................................... 2.4.1 3. Drawing Borders .....................................................................................................
Table of Contents
3 4 5 9 9 9 9 10 10 11 12 13 15 15 17 18 29 31 31 32 37 48 52 55 55 57 59 61 63
Translating Reference Data .......................................................................................................... 3.1 3.2 3.3 3.4 3.5 Label Description Library ................................................................................................... Physical and Graphic Commodity Libraries ....................................................................... Material Description Library ............................................................................................... Piping Job Specification Files ............................................................................................. Alphanumeric Commodity Library .....................................................................................
_ _______________
PDS 3D VAX to Workstation Translation August 1999
Size Dependent Data ........................................................................................................... Implied Data ........................................................................................................................ 3.6 3.7 MTO Format Files .............................................................................................................. Alphanumeric Model Builder Language Files .................................................................... Piping Designer Forms ............................................................................................... 63 64 66 67 69 69 69 71 72 72 74 74 77 85 Appendix A:
Fire and Safety .................................................................................................................... Instruments .......................................................................................................................... Piping Assemblies ............................................................................................................... Piping Commodities ............................................................................................................ Piping Specialties ................................................................................................................ Pipe Supports ...................................................................................................................... Valve Operators .................................................................................................................. Glossary ............................................................................................................................................... Index ....................................................................................................................................................
_ _______________
Preface
Document Purpose
This document is a reference guide for the 3D Vax to Workstation Translator module of the PDS 3D products. PDS 3D uses interactive graphics and database management techniques to integrate the engineering and design/drafting execution of plant design.
Preface
The 3D Vax to Workstation Translator is one part of the overall Plant Design System. It is specifically designed to translate PDS 3D data defined on the Vax to a specified project on the workstation. You can transfer project data such as design area definitions and seed files. design data such as piping and equipment models and drawings. reference data such as Eden modules or spec tables. This document is organized around the structure of the product which also represents a typical work flow.
Document Prerequisites / Audience

This document is intended for project managers or system administrators who have a working knowledge of the PDS 3D Modules. Knowledge of relational database systems and basic UNIX file manipulations is recommended. You should also be familiar with a text editor, such as vi or EMACS.
Related Documents/Products
Intergraph Corporations Relational Interface System (RIS)TM is required to operate PDS 3D, along with a relational database management system (RDBMS) supported by RIS. Currently, these include Informix, Oracle, and Sybase. Information about RIS capabilities can be found in the following documents: Relational Interface System (RIS) Reference Manual Relational Interface System (RIS) Operator Training Guide For more information on related aspects of the PDS 3D products, consult the following documents: Project Administrator Reference Guide Reference Data Manager Reference Guide Piping Design Graphics Reference Guide
_ _______________
Equipment Modeling Reference Guide Report Manager Reference Guide
About this Document

This document contains front matter, numbered sections, appendices, a glossary, and an index. Much of this document is devoted to a description of the steps required to setup the VAX and the workstation and translate the specific 3D data. Section 1 Section 2 Section 3 Appendices Describes the steps required to setup the VAX and the workstation. Describes the steps required to translate project environment data and design data. Describes the steps required to translate reference data. Provide additional information related to the 3D Vax to Workstation Translator.
We would like to hear what you think about the reference manual. After you have used this document, please help us improve our products by responding to the questionnaire at the back of the document. If you have more than one response to a question, circle all the responses that apply.
Additional Information
The following informational files are delivered with the 3D Vax to Workstation Translator software in the /usr#/ip32/pd3dtran directory. File Name README Contents Describes changes and additions to the product since the last version. Lists the names and dates of the files in the current release. For a fixes release, the files which have been modified are appended to the top of the initial file to provide a history of all changes to the product. Includes Comments and Trouble Report numbers which describe what problems have been fixed. Provides special notices to the customer. Lists any exceptions made to the certification. Lists all dependencies and related parts for the product.
product.def
10
_ _______________
General Conventions
This document contains many visual cues to help you understand the meaning of certain words or phrases. The use of different fonts for different types of information allows you to scan the document for key concepts or commands. Symbols help abbreviate and identify commonly used words, phrases, or groups of related information.
Preface
Typefaces
Italic Indicates a system response, which is an explanation of what the software is doing. For example, The text is placed in the viewing plane. Bold Indicates a command name, parameter name, or dialog box title. Command paths are shown using an arrow between command names. For example, Choose File > Open to load a new file. Sans serif Indicates a system prompt or message, which requires an action be taken by the user. For example, Select first segment of alignment Bold Typewriter Indicates what you should literally type in. For example, Key in original.dat to load the ASCII file. Normal Typewriter Indicates an actual file or directory name. For example, The ASCII report is stored in the layout.rpt file.
11
_ _______________
Symbols
This document uses the following symbols to represent mouse buttons and to identify special information: <C> <D> <R> <T> Command button Data button (usually the left mouse button) Reset/reject button (usually the right mouse button) Tentative button (usually the center mouse button) Note Important supplemental information.
Warning Critical information that could cause the loss of data if not followed.
Technical tip or information provides information on what the software is doing or how it processes information. Map or path shows you how to get to a specific command or form.
More information indicates there is additional or related information.
Need a hint used with activities and labs, provides a tip or hint for doing the exercises.
Keyboard Conventions
The following list outlines the abbreviations this document uses for keyboard keys and describes how to use them in combination. You can make some menu selections through the use of keyboard accelerators, which map menu selections to key combinations. ALT CTRL DEL ENTER ESC CTRL+z ESC,k Alternate key Control key Delete key Enter key Escape key To hold down the Control key and press Z. To press the Escape key, then K.
12
_ _______________
Terminology
Click To use a mouse or key combination to pick an item that begins an action. For example, Click Apply to save the changes. Select To mark an item by highlighting it with key combinations or by picking it with your cursor. Selecting does not initiate an action. After selecting an item, you click the action you want to affect the item. For example, Select the file original.dat from the list box, then click Delete to remove it from the directory. In addition, you would select items to define parameters, such as selecting toggle buttons. This also applies to selecting graphic elements from the design file. For example, Select the line string to define the graphic template. Tentative-select To place a tentative point on an existing graphic element in a design file. If you are using the CLIX operating system, you tentative-select by double-clicking with a mouse or pressing <T> on a hand-held cursor. If you are using the Windows NT operating system, you tentative-select by pressing a left-button, right-button chord. To select and execute a command by clicking the mouse or hand-held cursor button twice in rapid succession. This term implies that you are clicking the data button (<D>) as part of a menu or dialog box action. For example, Double-click on the file original.dat to load it into the new surface. Drag To press and hold the data button (<D>) while moving the mouse or hand-held cursor. To key a character string into a text box. To type in data and press ENTER to enter the data and execute the default action. In a dialog box, pressing TAB after keying in data will enter the data and move the cursor to the next field.
Preface
Double-click
Type Key in
13
_ _______________
14
_ _______________
Summary of Technical Changes
This section outlines the technical additions, revisions, and deletions made since the last edition of this document. Refer to the designated sections for details on the new information.
Summary of Technical Changes
Version 06.00.00.00 Changes

The operation of the translation software did not change from the 5.0 to 6.0 release. The following document change was made to clarify information. Section 1. Description Added a note under VAX Setup concerning VAX-placed break points in ISOGEN.
15
_ _______________
16
_ _______________
1. Translating VAX PDS 3D Data
This document describes the process of translating PDS 3D data defined for VAX PDS to a workstation project. The translation process is composed of several steps some of which are run on the VAX and some of which are run on the workstation.
Translating VAX PDS 3D Data
1. Translating VAX Data
Required Products
The VAX translators are provided in the 1.5.x fixes release to the Piping Design and Piping Spec products. The following VAX files are required to support the translation software for the 4.3 workstation release.
ATTRIBUTE.MAP DISCIPLINE.MAPW IMPLIED_DATA_FILE_EXTRACTION.EXE MATL_DESCR_FILE_EXTRACTION.EXE SIZE_DEPENDENT_FILE_EXTRACTION.EXE SPECFILE_EXTRACTION.EXE TRANSLATE_LABEL_LIB.EXE TRANS_PHYS_GRAPHICS_COMMODITY.EXE WS_SEED_TRANSLATOR.EXE WS_TRANSLATOR_DRW.EXE WS_TRANSLATOR_MDL.EXE 6-DEC-1991 24-MAR-1991 11-MAY-1992 2-AUG-1991 21-JUN-1991 2-AUG-1991 12-FEB-1994 6-JUL-1992 10-SEP-1992 12-JUL-1994 12-MAY-1994
The workstation translators are contained in the PD_3DTRAN product. NFS must be loaded on both the VAX and the workstation. The VAX must be designated as an NFS server. A project and all of its accompanying files must be defined with the Project Administrator before you can use the 3D Vax to Workstation Translator. Refer to the Project Administrator Reference Guide for information on Loading PDS 3D products. Editing the control script to identify the location of the project data. Setting up a project and creating the associated database schemas. Accessing the PDS 3D products remotely using NFS.
17
_ _______________
1.1
VAX Setup
Complete the following steps to verify the VAX data and setup the network before running the translation process.
VAX Project Environment Data

1. For each piping model to be translated, use the Data Integrity Validation option of the Diagnostics command to check the model for illegal data structures, overlaping segments, or gaps between items. Refer to the PDS Piping Design Task Users Guide for information on running this option. Correct any detected errors before continuing with the translation. When translating ISOGEN drawings, be sure to remove all VAX-placed break points. Failure to do so will cause dimensions and other callout graphics to overlay each other once translated to the workstation. This is because workstation versions of ISOGEN use different algorithms to determine the quantity of data per iso. 2. Use the Verify Project Database option in the Project Manager to verify the project to be translated. Refer to the PDS Piping RDB Users Guide for information on running this option. Any elements identified by database verification as not having a valid database occurrence (weight=6) will NOT be translated to the design files on the workstation. These elements are omitted from the transfer, since they do not have a legal database occurrence. Once you have run database verification on the project, do NOT use the project again until translation is completed. 3. Use the Create Report options in the Project Environment Manager to generate a report of all the models and drawings in the Project Environment Database. Any models in the report which are NOT associated with a design area cannot be translated. The workstation requires an area association.
VAX NFS Setup

Before executing anything on the workstation, you will need to export directories on the VAX so that they can be mounted by the workstation. Refer to the Intergraph Guide to NFS for more information on setting up NFS on a VAX. You will need the report output on the Project Environment Database for models and drawings to do this.
18
_ _______________
1. 2. 3. Using a privileged account, key in set def PRO_DD_NFS: Key in @config to define the configuration for NFS. NFS configuration Utility v1.1 Fstab version: major 1= 1 minor = 1 Command: Key in add filesystem. 4. What FILESYSTEM ?
VAX Setup
Key in zxx:[xxx,xxx] (where zxx is the device and [xxx,xxx] is the directory for a model or a drawing. Repeat this step for each directory listed in the reports. 5. You can key in show to displayed the defined configuration information.
Number of concurrent requests NFSD will process ... 4 Configured File Systems: _ZFB1:[010003] WRITE, MULTIPLE directories Valid Clients: All clients.
6. 7.
When all the directories have been entered, key in exit to exit this procedure. Do you want the PCNFSD server running on this system?: Key in n to define that no PCs will be running on this network via NFS.
8. 9.
Key in @remove Key in @znfs.stu The system defines all the directories you specified to be set up for mounting by the workstation.
Mapping Database Attributes

Copy the file PRO_DD_PDSPIPE:ATTRIBUTE.MAP to the directory of the project being translated. The attribute map file is a map of the VAX attribute numbers to the Workstation attribute numbers. If you have any user defined attributes in this project, you will need to edit the attribute map file for the project.
19
_ _______________
The first column of the attribute map contains the workstation attribute number. A -1 in this column means that the attribute was deleted on the workstation. The second column is the vax attribute number, which can be derived from the DDL in the project directory.
ATTRIBUTE.MAP File
You should insert any user-defined attributes in their appropriate location in the ATTRIBUTE.MAP file and renumber the new workstation (non-existent VAX) attributes sequentially. Be sure to leave at least one space between each column. (Refer to Workstation Setup, Section 1.2, for information on the workstation database structure.)
1. piping_segment_model 1 2 67 68 69 70 4 9 5 10 11 12 13 14 -1 15 16 17 18 19 71 24 25 26 27 28 29 30 31 32 33 8 .1 .2 .3 .4 .5 .6 .7 .8 .9 .10 .11 .12 .13 .14 .15 .16 .17 .18 .19 .20 .21 .22 .23 .24 .25 .26 .27 .28 .29 .30 .31 .32 max_att = 32
pntr_to_pip_segment_anal_data line_number_label end_1_node_number end_2_node_number end_1_nozzle_pointer end_2_nozzle_pointer unit_number fluid_code unit_code line_sequence_number nominal_piping_diameter piping_materials_class gasket_separation insulation_purpose insulation_spec_override_flag insulation_thickness insulation_density heat_tracing_requirements heat_tracing_media heat_tracing_media_temperature ident_of_alphanum_input_descr normal_operating_pressure normal_operating_temperature alternate_operating_pressure alternate_operating_temperatur normal_design_pressure normal_design_temperature alternate_design_pressure alternate_design_temperature steam_outlet_temperature materials_of_construction_clas train_number max_att = 52
2. piping_segment_analysis -1 43 44 45 46 47 48 49 50 -1 .1 .2 .3 .4 .5 .6 .7 .8 .9 .10
pointer_to_segment_data norm_operating_pres_phys_units norm_operating_temp_phys_units altr_operating_pres_phys_units altr_operating_temp_phys_units normal_design_pres_phys_units normal_design_temp_phys_units alter_design_pres_phys_units alter_design_temp_phys_units normal_stress_anal_pres_units
20
_ _______________
-1 -1 -1 51 34 35 36 72 37 52 53 -1 -1 -1 -1 39 40 41 38 6 7 42 56 57 58 20 21 22 23 54 55 59 60 61 62 63 64 65 66 -1 3 73 .11 .12 .13 .14 .15 .16 .17 .18 .19 .20 .21 .22 .23 .24 .25 .26 .27 .28 .29 .30 .31 .32 .33 .34 .35 .36 .37 .38 .39 .40 .41 .42 .43 .44 .45 .46 .47 .48 .49 .50 .51 .52 normal_stress_anal_temp_units altr_stress_anal_pres_units altr_stress_anal_temp_units steam_outlet_temp_phys_units safety_classification design_code_requirements design_area_number standard_note_number design_responsibility stress_analysis_identification stress_analysis_requirement normal_stress_analysis_press normal_stress_analysis_temp alternate_stress_analysis_pres alternate_stress_analysis_temp supply_responsibility coating_requirements cleaning_requirements construction_responsibility module_number packaged_system_number fluid_category specific_gravity_1 specific_gravity_2 specific_gravity_3 construction_status hold_status approval_status sched_thickness_override_flag hydraulics_analysis_id hydraulics_analysis_requiremnt viscosity density specific_heat_ratio sonic_velocity pipe_surface_roughness test_system_number test_fluid test_pressure revision_management_id line_id pid_index_number max_att = 33
VAX Setup
3. piping_component_model_entity 1 -1 2 3 4 5 6 7 49 50 51 52 53 .1 .2 .3 .4 .5 .6 .7 .8 .9 .10 .11 .12 .13
pointer_to_pip_comp_anal_data commodity_item_eng_item_indic piping_component_number item_name new_item_name option_code maximum_temperature sched_thickness_override_flag cp_1_nominal_piping_diameter cp_1_outside_diameter cp_1_end_preparation cp_1_schedule_thickness cp_1_pressure_rating
21
_ _______________
62 63 64 65 66 75 76 77 78 79 88 89 90 91 92 101 102 103 104 105 .14 .15 .16 .17 .18 .19 .20 .21 .22 .23 .24 .25 .26 .27 .28 .29 .30 .31 .32 .33 cp_2_nominal_piping_diameter cp_2_outside_diameter cp_2_end_preparation cp_2_schedule_thickness cp_2_pressure_rating cp_3_nominal_piping_diameter cp_3_outside_diameter cp_3_end_preparation cp_3_schedule_thickness cp_3_pressure_rating cp_4_nominal_piping_diameter cp_4_outside_diameter cp_4_end_preparation cp_4_schedule_thickness cp_4_pressure_rating cp_5_nominal_piping_diameter cp_5_outside_diameter cp_5_end_preparation cp_5_schedule_thickness cp_5_pressure_rating max_att = 92
4. piping_component_analysis_data -1 46 47 48 32 33 -1 37 39 10 31 8 11 12 13 29 14 15 16 17 18 19 20 21 25 26 27 28 30 -1 34 35 36 9 .1 .2 .3 .4 .5 .6 .7 .8 .9 .10 .11 .12 .13 .14 .15 .16 .17 .18 .19 .20 .21 .22 .23 .24 .25 .26 .27 .28 .29 .30 .31 .32 .33 .34 pointer_to_pip_comp_model_data piping_component_remarks standard_note_number_1 standard_note_number_2 construction_status hold_status approval_status isometric_drawing_number piece_mark fabrication_category opening_action piping_commodity_library_code commodity_code_override_flag PDS_sort_code identification_of_phys_data index_pip_graphic_lib_subcomp geometric_industry_standard weight_code generic_dimen_data_select_flag specific_dimen_data_select_flg material_grade bend_radius bend_sweep_angle face_to_face_dimension surface_area dry_weight wet_weight orifice_port_size number_of_miter_joints supply_responsibility heat_tracing_requirement heat_tracing_media heat_tracing_media_temperature no_mto_indicator
22
_ _______________
-1 41 42 43 59 54 55 -1 57 60 61 72 67 68 -1 70 73 74 85 80 81 -1 83 86 87 98 93 94 -1 96 99 100 111 106 107 -1 109 112 113 44 45 22 -1 23 24 38 40 56 69 82 95 108 58 71 84 97 110 .35 .36 .37 .38 .39 .40 .41 .42 .43 .44 .45 .46 .47 .48 .49 .50 .51 .52 .53 .54 .55 .56 .57 .58 .59 .60 .61 .62 .63 .64 .65 .66 .67 .68 .69 .70 .71 .72 .73 .74 .75 .76 .77 .78 .79 .80 .81 .82 .83 .84 .85 .86 .87 .88 .89 .90 .91 revision_management_id stres_anal_node_no_at_comp_ctr stres_intens_factor_at_cmp_ctr head_loss_factor_at_comp_ctr cp_1_stress_anal_node_number cp_1_face_to_center_distance cp_1_weld_id cp_1_reserved cp_1_gasket_separation cp_1_stress_intens_factor cp_1_head_loss_factor cp_2_stress_anal_node_number cp_2_face_to_center_distance cp_2_weld_id cp_2_reserved cp_2_gasket_separation cp_2_stress_intens_factor cp_2_head_loss_factor cp_3_stress_anal_node_number cp_3_face_to_center_distance cp_3_weld_id cp_3_reserved cp_3_gasket_separation cp_3_stress_intens_factor cp_3_head_loss_factor cp_4_stress_anal_node_number cp_4_face_to_center_distance cp_4_weld_id cp_4_reserved cp_4_gasket_separation cp_4_stress_intens_factor cp_4_head_loss_factor cp_5_stress_anal_node_number cp_5_face_to_center_distance cp_5_weld_id cp_5_reserved cp_5_gasket_separation cp_5_stress_intens_factor cp_5_head_loss_factor piping_assembly_name component_group_number dimension_a gasket_type_option_code dimension_b dimension_c isometric_sheet_no color_code cp_1_weld_type cp_2_weld_type cp_3_weld_type cp_4_weld_type cp_5_weld_type cp_1_gasket_option cp_2_gasket_option cp_3_gasket_option cp_4_gasket_option cp_5_gasket_option
VAX Setup
23
_ _______________
114 .92 unique_name max_att = 63 5. pipe_model_entity 1 2 3 4 5 6 15 7 8 9 10 11 38 39 40 27 28 -1 32 34 14 12 -1 16 17 18 19 20 21 22 24 25 23 26 -1 29 30 31 13 -1 41 46 42 -1 44 47 48 49 54 50 -1 52 55 56 .0 .1 .2 .3 .4 .5 .6 .7 .8 .9 .10 .11 .12 .13 .14 .15 .16 .17 .18 .19 .20 .21 .22 .23 .24 .25 .26 .27 .28 .29 .30 .31 .32 .33 .34 .35 .36 .37 .38 .39 .40 .41 .42 .43 .44 .45 .46 .47 .48 .49 .50 .51 .52 .53 unique_system_no pipe_tag_number item_name new_item_name option_code maximum_temperature pipe_tube_hose_indicator nominal_piping_diameter outside_diameter schedule_thickness schedule_thickns_override_flag pressure_rating pipe_remarks standard_note_number_1 standard_note_number_2 construction_status hold_status approval_status isometric_drawing_number piece_mark fabrication_category piping_commodity_library_code commodity_code_override_flag PDS_sort_code geometric_industry_standard weight_code piping_outside_diam_select_flg parameteric_defin_select_flag material_grade pipe_length dry_weight wet_weight surface_area cold_spring_length supply_responsibility heat_tracing_requirement heat_tracing_media heat_tracing_media_temperature no_mto_indicator revision_management_id end_preparation_at_end_1 end_1_stress_analysis_node_no end_1_weld_id end_1_reserved end_1_gasket_separation end_1_stress_intens_factor end_1_head_loss_factor end_preparation_at_end_2 end_2_stress_analysis_node_no end_2_weld_id end_2_reserved end_2_gasket_separation end_2_stress_intens_factor end_2_head_loss_factor
24
_ _______________
36 37 -1 33 35 43 51 45 53 57 .54 .55 .56 .57 .58 .59 .60 .61 .62 .63 piping_assembly_name component_group_number gasket_type_option_code isometric_sheet_no color_code end_1_weld_type end_2_weld_type end_1_gasket_opt end_2_gasket_opt unique_name max_att = 31
VAX Setup
6. instrument_comp_model_entity 1 -1 2 3 4 5 55 56 57 58 59 68 69 70 71 72 81 82 83 84 85 94 95 96 97 98 107 108 109 110 111 .1 .2 .3 .4 .5 .6 .7 .8 .9 .10 .11 .12 .13 .14 .15 .16 .17 .18 .19 .20 .21 .22 .23 .24 .25 .26 .27 .28 .29 .30 .31
pointer_to_inst_comp_anal_data in_line_off_line_instr_indicat instrument_tag_number instrument_name option_code schedule_thcknss_override_flag cp_1_nominal_piping_diameter cp_1_outside_diameter cp_1_end_preparation cp_1_schedule_thickness cp_1_pressure_rating cp_2_nominal_piping_diameter cp_2_outside_diameter cp_2_end_preparation cp_2_schedule_thickness cp_2_pressure_rating cp_3_nominal_piping_diameter cp_3_outside_diameter cp_3_end_preparation cp_3_schedule_thickness cp_3_pressure_rating cp_4_nominal_piping_diameter cp_4_outside_diameter cp_4_end_preparation cp_4_schedule_thickness cp_4_pressure_rating cp_5_nominal_piping_diameter cp_5_outside_diameter cp_5_end_preparation cp_5_schedule_thickness cp_5_pressure_rating max_att = 119
7. inst_component_analysis_entity -1 52 53 54 29 30 -1 43 .1 .2 .3 .4 .5 .6 .7 .8 pntr_to_instr_comp_model_data instrument_component_remarks standard_note_number_1 standard_note_number_2 construction_status hold_status approval_status isometric_drawing_number
25
_ _______________
45 7 28 9 10 25 11 12 13 14 15 24 16 20 21 22 23 -1 -1 36 8 37 38 39 40 -1 31 32 33 34 35 41 42 6 -1 -1 -1 -1 -1 -1 -1 -1 -1 26 27 -1 -1 -1 -1 47 48 49 65 60 61 -1 63 -1 66 67 .9 .10 .11 .12 .13 .14 .15 .16 .17 .18 .19 .20 .21 .22 .23 .24 .25 .26 .27 .28 .29 .30 .31 .32 .33 .34 .35 .36 .37 .38 .39 .40 .41 .42 .43 .44 .45 .46 .47 .48 .49 .50 .51 .52 .53 .54 .55 .56 .57 .58 .59 .60 .61 .62 .63 .64 .65 .66 .67 .68 piece_mark fabrication_category opening_action PDS_sort_code identification_of_phys_data index_pip_graphic_comm_lib_sub geometric_industry_standard weight_code generic_dimen_data_select_flag specific_dimen_data_select_flg material_grade valve_operator_type face_to_face_dimension surface_area dry_weight wet_weight orifice_port_size instrument_reserved_data supply_responsibility insulation_purpose instrument_spec_override_flag insulation_thickness insulation_density cleaning_requirements safety_classification design_area_number design_responsibility construction_responsibility heat_tracing_requirement heat_tracing_media heat_tracing_media_temperature module_number packaged_system_number no_mto_indicator accessory_1 accessory_2 accessory_3 accessory_4 accessory_5 accessory_6 actuator_type fail_path_1 fail_path_2 flow_tap_type pressure_set_point pressure_set_point_units vacuum_set_point vacuum_set_point_units revision_identification stres_anal_node_no_at_comp_ctr stres_intens_factor_at_cmp_ctr head_loss_factor_at_comp_ctr cp_1_stress_anal_node_number cp_1_face_to_origin_distance cp_1_weld_id cp_1_reserved cp_1_gasket_separation cp_1_signal_line_type cp_1_stress_intens_factor cp_1_head_loss_factor
26
_ _______________
78 73 74 -1 76 -1 79 80 91 86 87 -1 89 -1 92 93 104 99 100 -1 102 -1 105 106 117 112 113 -1 115 -1 118 119 50 51 17 -1 18 19 44 46 62 75 88 101 114 64 77 90 103 116 120 .69 .70 .71 .72 .73 .74 .75 .76 .77 .78 .79 .80 .81 .82 .83 .84 .85 .86 .87 .88 .89 .90 .91 .92 .93 .94 .95 .96 .97 .98 .99 .100 .101 .102 .103 .104 .105 .106 .107 .108 .109 .110 .111 .112 .113 .114 .115 .116 .117 .118 cp_2_stress_anal_node_number cp_2_face_to_origin_distance cp_2_weld_id cp_2_reserved cp_2_gasket_separation cp_2_signal_line_type cp_2_stress_intens_factor cp_2_head_loss_factor cp_3_stress_anal_node_number cp_3_face_to_origin_distance cp_3_weld_id cp_3_reserved cp_3_gasket_separation cp_3_signal_line_type cp_3_stress_intens_factor cp_3_head_loss_factor cp_4_stress_anal_node_number cp_4_face_to_origin_distance cp_4_weld_id cp_4_reserved cp_4_gasket_separation cp_4_signal_line_type cp_4_stress_intens_factor cp_4_head_loss_factor cp_5_stress_anal_node_number cp_5_face_to_origin_distance cp_5_weld_id cp_5_reserved cp_5_gasket_separation cp_5_signal_line_type cp_5_stress_intens_factor cp_5_head_loss_factor piping_assembly_name component_group_number dimension_a gasket_type_option_code dimension_b dimension_c isometric_sheet_no color_code cp_1_weld_type cp_2_weld_type cp_3_weld_type cp_4_weld_type cp_5_weld_type cp_1_gasket_option cp_2_gasket_option cp_3_gasket_option cp_4_gasket_option cp_5_gasket_option
VAX Setup
.119 unique_name max_att = 36
8. pipe_support_entity
27
_ _______________
1 2 4 5 -1 12 18 19 21 28 29 30 31 32 33 34 35 36 15 23 24 25 26 27 3 16 17 20 22 6 7 8 9 10 11 13 14 .0 .1 .2 .3 .4 .5 .6 .7 .8 .9 .10 .11 .12 .13 .14 .15 .16 .17 .18 .19 .20 .21 .22 .23 .24 .25 .26 .27 .28 .29 .30 .31 .32 .33 .34 .35 .36 system_unique_no pipe_support_number functional_symbol_item_name pipe_support_type pipe_support_detail_number pipe_support_commodity_code standard_note_number isometric_drawing_number piece_mark transitional_spring_rigidity_x transitional_spring_rigidity_y transitional_spring_rigidity_z rotational_spring_rigidity_x rotational_spring_rigidity_y rotational_spring_rigidity_z spring_gap_length spring_gap_direction number_of_springs pipe_support_weight dimension_1_for_isometric dimension_2_for_isometric dimension_3_for_isometric dimension_4_for_isometric dimension_5_for_isometric physical_symbol_item_name construction_stat hold_status isometric_sheet_no color_code iso_support_type_b iso_support_type_c iso_support_type_d details_for_shop details_for_field fabrication_orient MTO_indicator fabrication_cat
28
_ _______________
1.2 Workstation Setup
Use the Project Administrator to create a project to receive the VAX data. Refer to the Project Administrator Reference Guide for information on creating a project.
Workstation Setup
If user defined attributes were included in the VAX project or any attributes of revisable character lengths were changed, you must edit the database structure (ddl) files before creating database schemas. For the design database, you can do this during the Create Design Schema operation. The following ddl files are used to define the three databases. project.ddl - Project Control Database design.ddl - Design Database. Also referred to as the Task Database on the VAX. reference.ddl - Specification/Material Reference Database. This is a combination of the Piping Job Specification Database and Alphanumeric Commodity Library Database used on the VAX. If you must rename the attributes in the workstation design ddl file, you must place the revised design.ddl file in the /usr/ip32/pdshell/ddl directory before creating the workstation project. Record the following information for use later in the translation process. the names of the Project Schema, Design Schema, and Reference Schema the network address (node name) and directory path of the project.
Editing the PD3DTRAN Scripts

In addition to the setup information specified in the Project Administrator Reference Guide, you should complete the following steps before using the 3D Vax to Workstation Translator. Edit the following shell scripts to identify the location of the project files. /usr/ip32/pd3dtran/seedtrans.sh /usr/ip32/pd3dtran/modeltrans.sh /usr/ip32/pd3dtran/drawtrans.sh
# The PROJect control FILE path and its net ADDRess which defines all # projects currently defined will also be defined in this file, initially # defined through delivery, later redefined through user modification. # export PROJ_FILE=machine_directory export PROJ_ADDR=machine_name
29
_ _______________
This should be the same location specified for the project files in the control.sh file. Add RIS to the default command path.
export PATH=$PATH:/usr/ip32/riscli/bin:/usr/ip32/risutl/bin
30
_ _______________
2. Translating Project Environment and Design Data
This section describes the steps required to translate Project Environment data such as disciplines, design areas, seed files, models and drawings from the VAX to the workstation. It also transfers the associated design data. Pipe Support Only files will not be processed for translation. On the VAX, use the Copy Pipe Support command to copy the pipe supports to a Piping and Pipe Support model for translation.
Translating Project Environment and Design Data
2. Project & Design Data
2.1
Defining Discipline Data

On the VAX, copy the file PRO_DD_PDSPIPE:DISCIPLINE.MAPW to the directory of the project being translated. The discipline map file is a map of the VAX discipline numbers to the Workstation discipline numbers. You may need to edit the discipline map file for the project. The first column of the discipline map contains the workstation discipline number. The second column is the VAX discipline number.
!ws discipline 1 2 3 4 5 6 vax discipline 1 2 3 4 5 6 text Piping Equipment Structural HVAC Raceways Architecture
You may need to edit the VAX discipline numbers for the six disciplines listed. The workstation project is created with six disciplines in the order defined in the file. Change the VAX discipline numbers to reflect the order the disciplines are listed on the VAX. You can determine the order by reviewing the VAX PDS Project Environment report. Information in the report is presented in the order the disciplines were defined. Also add any other disciplines that are required to this list. Be sure to leave at least one space between each column. Use fmu or ftp to copy the project.ddl from the project directory on the workstation to the project directory on the VAX. For example,
fmu ws_node.user.passwd rec ws_projdir/project.ddl vax_projdir/*
31
_ _______________
2.2
Translating Seed Data

VAX
Complete the following actions using a login that has privileges to write to the project directory. 1. Key in RUN XPD:[14,54]WS_SEED_TRANSLATOR.EXE to extract the data from the project environment database of the desired project. Translator for Project Environment Database Enter VAX Project Number for Translating to Workstation Key in the number of the project to be translated. 3. Enter Workstation Project Schema Name Key in the schema name of the workstation project database (for example, pd_proj1). The following messages display. Processing Successfully created project environment load file : project_name.dbsw Processing Completed The system generates the following files. project environment load file (projectname.dbsw) equipment schema definition file (eqp.ddl) a file containing attribute lengths for some piping attributes (attr_lens.dbws) The eqp.ddl and attr_lens.dbws are used later in the translation process and must not be modified.
2.
Sample Project Environment Load File

default schema pd_infproj create table PDtable_101 (system_unique_no int, project_no char(15), project_name char(40), job_no char(40), company_name char(40), plant_name char(40) ) insert into PDtable_101 (system_unique_no, project_no, project_name, job_no, company_name, plant_name) values (?, ?, ?, ?, ?, ?) system_unique_no 1 11 project_no var 13 29 project_name var 31 72 job_no var 74 115 company_name var 117 158 plant_name var 160 201 0 transproj TRANSPROJ 1000 INTERGRAPH ***RIS*** End of Table ***RIS***
32
_ _______________
create table PDtable_112 (discipline_indx_no smallint, area_index_no smallint, area_name char(10), description char(40), volume_low_x int, volume_low_y int, volume_low_z int, volume_high_x int, volume_high_y int, volume_high_z int, interference_mode smallint) insert into PDtable_112 (discipline_indx_no, area_index_no, area_name, description, volume_low_x, volume_low_y, volume_low_z, volume_high_x, volume_high_y, volume_high_z, interference_mode) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) discipline_indx_no 1 6 area_index_no 8 13 area_name var 15 26 description var 28 69 volume_low_x 71 81 volume_low_y 83 93 volume_low_z 95 105 volume_high_x 107 117 volume_high_y 119 129 volume_high_z 131 141 interference_mode 143 148 1 1 trans 0 0 0 0 0 0 1 ***RIS*** End of Table ***RIS*** create table PDtable_113 (model_index_no int, discipline_indx_no smallint, area_index_no smallint, partition_no smallint, model_no char(10), description char(40), model_file_spec char(14), path_name char(36), network_address char(26), lock_owner char(10), lock_status smallint, lock_date int, verification_date int, revision_date int, application_type smallint) insert into PDtable_113 (model_index_no, discipline_indx_no, area_index_no, partition_no, model_no, description, model_file_spec, path_name, network_address, lock_owner, lock_status, lock_date, verification_date, revision_date, application_type) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) model_index_no 1 11 discipline_indx_no 13 18 area_index_no 20 25 partition_no 27 32 model_no var 34 45 description var 47 88 model_file_spec var 90 105 path_name var 107 144 network_address var 146 173 lock_owner var 175 186 lock_status 188 193 lock_date 195 205 verification_date 207 217 revision_date 219 229 application_type 231 236 1 1 1 0 pipe01 PIPE MODEL 01 pipe01.dgn zg0:[140,011] cv112f 0 0 0 0 0 2 1 1 1 pipe02 PIPE MODEL 02 pipe02.dgn zg0:[140,011] cv112f 0 0 0 0 0 3 1 1 2 pipe03 PIPE MODEL 03 pipe03.dgn zg0:[140,011] cv112f 0 0 0 0 0 4 1 1 3 pipe04 PIPE MODEL 04 pipe04.dgn zg0:[140,011] cv112f 0 0 0 0 0 ***RIS*** End of Table ***RIS*** ***RIS*** End of Schema ***RIS***
Workstation
Complete the following steps on the workstation to translate the Project Environment Database to the workstation. 1. Use fmu or ftp to copy the project environment load file (project_name.dbsw) to the workstation. For example, fmu vax_node.user.passwd rec projname.dbsw * 2. 3. Key in rislod to load the schema. Set model ansi ON(y/n) :[y] > Press <Return> to turn this option on. 4. Set mode enable database? all(a) Specific(s) :[a] >
33
_ _______________
Key in s to enable specific databases. 5. enter database name :[return] > Key in the type of database you are using such as informix or oracle. 6. enter database name :[return] > Press <Return> to accept the default. 7. file mode for all output files? overwrite(w) append(a) error out if exists(e) :[e] Key in w to overwrite output files. 8. main file for loading: [ris.dmp] > Key in the name of the project environment load file (from step 1). 9. log file: [ris.log] > Press <Return> to accept the default. 10. bad file :[ris.bad] > Press <Return> to accept the default. 11. enter delimitation used in the files for loading [] > Press <Return> to use the default delimiter. 12. enter commit interval : [25] > Press <Return> to accept the default. 13. Which schemas should be loaded? all (a) prompted (p): [a] > Press <Return> to load all schemas. 14. Which tables should be loaded? all (a) prompted (p) none (n): [a] > Press <Return> to load all tables. 15. both definition and data (b) definition only (o): [b] > Press <Return> for both. 16. ignore create error due to the existence of a table (y/n): [n] >
34
_ _______________
Key in y to ignore these errors. 17. clear existing data from table before loading (y/n): [n] > Key in y clear the tables. 18. Which index definitions should be loaded? all (a) prompted (p) none (n): [a] > Press <Return> to load all index definitions. 19. Which views should be loaded? all (a) prompted (p) none (n): [a]> Press <Return> to load all views. 20. Which privilege definitions should be loaded: all (a) prompted (p) none (n): [a] > Press <Return> to load all privilege definitions.
RIS uses the specified information to load the database. The system will display several create table errors as it processes the load file. This is caused by tables which were created by the Project Administrator during project creation; this is NOT a problem. As it processes, RIS displays the number of rows loaded into each table. When finished, the system returns to the CLIX prompt. 21. 22. Key in /usr/ip32/pd3dtran/seedtrans.sh to transfer the seedz files. Enter Workstation Project Number Key in the name of the workstation project. (This is the value specified for project number when the project was created, such as proj1.) 23. Enter Vax Project Number Key in the name of the VAX project being translated. 24. Enter Vax Project Network Address Key in the node name for the VAX. 25. Enter VAX Project Directory Key in the VAX directory where the project is located in the format ZFxx:[xxx,xxx] (for example, zfb1:[010,003]). Translating Model Seedfile Translating Drawing Seedfile Translating Equipment Seedfile Processing Completed
35
_ _______________
For each piping design area, the system displays the following messages. Creating Marker File for Piping Area: areaname << copying -> /usr/projdir/mdlsdz.dgn (to)-> /usr/projdir/areaname.1 >> The system transfers the model, drawing, and equipment seedz files and translates their type 63 data. It also creates marker files for the piping design areas in the project.
36
_ _______________
2.3 Translating Models
Before running the model unload software, copy the file /usr/ip32/pd3dtran/dat/cp_geo_typ_tap to the workstation project directory.
! This file contains the model code and its connect point geometry type ! for VAX->Workstation translation ! Following is the definition of connect point geometry types: ! LINEAR 1 ! ELBOLET 1 ! BEND 2 ! ANGLE_VALVE 3 ! ECC_REDUCER 4 ! BRANCH_TEE 5 ! BRANCH_LAT 6 ! BRANCH_WYE 7 ! BRANCH_2WYE 8 ! CROSS 9 ! OPERATOR 10 ! LATROLET 11 ! OLET 12 ! SINGLE_CP 13 ! RET_180 14 ! ORIFICE_FLANGE 15 ! GENERIC_COMPONENT 16 GATR 1 GATF 1 GAT 1 GATEX 1 GATEXB 1 GATXBA 12 GATXBB 1 BALR 1 BALSP 1 GLOR 1 GLO 1 NEE 1 BFYLP 1 BFYHP 1 CKL 1 CKLF 1 CKLR 1 CKLRY 1 CKLSP 1 CKS 1 CKSF 1 CKSR 1 CKSSP 1 CKST 1 CKSY 1 CKWF 1 CKAST 3 CKYST 1 BDA 3 BDY 1 HOS 1 HOSA 3 FSW 1 FWN 1 FRSW 1 FOWNAW 15 1 FBLD 13 FRWN 1 FTHD 1 FRTHD 1
Translating Models
37
_ _______________
FOWNA FOTHDA BLSPO BLSPC BLPAD BLSPA PLUG CAPOT CAPBV SWGC SWGE REDC REDE CPL #CPLH CPLR UN BUSH E45TLR E45 E45LR E90TLR E90 E90LR E90SR PIPB PIPB2 M904 #T #TRB #TST L LRB #WOL #SOL #TOL EOLLR LOL FOLHC RPAD RPAD2 RWELD RWELD2 NIP MN1 ME2 SSP1 S49AC S51AC S53AC S70AC S70BC S3AC S3AS S49AS S51AS S78AC SSEW1 I3AS I7AS I8AS I13AS I15AS I17AS I18AS I118BS I209AS I213AS I253AS 15 1 15 1 1 1 1 1 13 13 13 1 4 1 4 1 12 1 1 1 2 2 2 2 2 2 2 2 2 2 5 5 5 6 6 12 12 12 1 11 1 11 11 11 11 1 13 13 13 5 6 1 1 1 16 16 5 6 1 13 16 1 3 1 1 1 1 1 16 1 16
38
_ _______________
I322AS I324FS IND 3OP1 4IND 4BOX 4CYL 3UNO1 1BF1 1GL1 BAL3W BALF BALLP BALVP BDISC BWELD CKAL CKALSP CKAR CKBP DIA DIAGL DIAPL DIASP E11 E22 E453D E45CPL E45L E45LT E45S E45ST E45T3D E45U E5 E60 E903D E90CPL E90LT E90R E90RST E90S E90ST E90T3D E90U EOLSR FCP FEWN FFIL FL FLO FLSL FLSSO FLWN FOOT FOSOA FOSOAW FOSOB FOSOBW FOSWA FOSWAW FOSWB FOSWBW FOWNB FOWNBW FPIPE FPL FRPL FRS 16 16 13 1 16 1 1 1 1 1 5 1 1 1 1 1 3 3 5 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1 15 15 15 15 15 15 15 15 15 15 1 1 1 1
Translating Models
1 1 1 1 1 1 1 1 1 1
39
_ _______________
FRSO FS FSO FSSL FSSPL FSSSO GATBL GATCON GATSP GLO3W GLOA GLOASP GLOF GLOSP GLOY GLOYF GLOYR H3W1 HNIP HRST1 INSR1 INSR2 KNF LRRB M1 M2 M3 M4 M451 M452 M901 M902 M903 ME1 NIPL #NOL OPSPA PIN PLU PLU3W PLU4W PLUF PLUFB PLUR PLUSP PLUVP PS1 PS15 PS19 PS3 PS5 #PT #PTRB #PTREB #PTRRB R180 R180CL R180CP R180LR R180MD R180OP R180SR S90YB S90YRB SLI #SWOL #TBA TDR TDRA 1 1 1 1 1 1 1 1 1 5 3 3 1 1 1 1 1 13 1 13 1 1 1 6 2 2 2 2 2 2 2 2 2 13 1 12 1 1 1 5 9 1 1 1 1 1 16 16 16 16 16 5 5 5 5 14 14 14 14 14 14 14 5 5 1 12 5 15 1 15 1
40
_ _______________
TDRAW TDRB TDRBW TE TER TKDR #TRBT TREB TRI TRIB #TRRB #TUOB #TUOR UND UNO X XBA XRB XRRB Y CF1 CF2 EW1 H3W2 HR1 MF1 MFE1 MFR1 MR1 S1AC H2W1 H2W2 H2WN1 H2WN2 S2W1 S2W901 S32BC S4AC S64BC SPA1 SS1 SW1 15 15 15 5 5 3 5 5 15 5 5 5 5 1 1 9 9 9 9 7 3 13 13 13 13 13 13 13 13 1 13 13 13 13 13 13 3 16 16 13 13 13 1 1 1 1
Translating Models
The connect point geometry type and tap file is used to define the connect point geometry generated by Eden and the number of taps which were created by Eden for the components being translated. You can edit this file. The first column contains the model code (this value should match the Eden module name) The second column contains the connect point geometry type from the Eden module. The third column contains the number of taps as defined in the Piping Job Specification (if any). If the third column contains a value greater than zero, the software reads the number of taps from the user data of the component or instrument and writes that number into the user data slot as the number of taps generated by Eden. This file is used by every piping model in the project. Be sure to separate each column by at least one space and to leave NO blank spaces at the beginning of the line.
41
_ _______________
Dual Connect Point Geometry Type

If the model code could have a dual connect point geometry type, you must key in a # before the model code (for example, #CPLH) to represent a dual connect point geometry. The software uses the following rule for a designated dual connect point geometry type model code: If bend_angle equals 90, use the connect point geometry type in the file. If the bend_angle is not 90, the software changes the connect point geometry type for that model code using the connect point geometry type in the file to the following: if cp geometry type in file = 12, change to 11 if cp geometry type in file = 5, change to 6 These are the only changes that are supported.
VAX
Use fmu or ftp to copy the design.ddl file from the workstation project directory to the project directory on the VAX. For example,
fmu ws_node.user.passwd rec projdir/design.ddl [vaxproj]design.ddl
Complete the following steps for each piping and equipment area using a login that has privileges to write to the project directory. 1. Key in run XPD:[14,54]WS_TRANSLATOR_MDL.EXE to unload the design task database of the desired project based on discipline and area. Enter VAX Project Number for Translating to Workstation Key in the name of the project to be translated. 3. Enter Workstation Design Schema Name Key in the design schema name. 4. Enter Discipline - 1 for Piping or 2 for Equipment Key in 1 to translate piping data or key in 2 to translate equipment data. 5. Enter Area Name Key in the name of the design area to be translated.
2.
Processing Processing Model : zfxx:[xxx,xxx]model_name
42
_ _______________
Successfully created area load file : area_name.db1 (or area_name.db2 if equipment) Processing Completed
Translating Models
Workstation
Complete the following steps on the workstation to translate the design database for the specified area. 1. Use fmu or ftp to copy the database load file for the area to the workstation (area_name.db1 or .db2). For example,
fmu vax_node.user.passwd rec area_name.db# * 2. 3. Key in rislod to load the schema. Set model ansi ON(y/n) :[y] > Press <Return> to turn model ansi on. 4. Set mode enable database? all(a) Specific(s) :[a] > Key in s to enable specific databases. 5. Enter database name :[return] > Key in the type of database you are using: informix, oracle, or ingres. 6. Enter database name :[return] > Press <Return> to accept the default. 7. File mode for all output files? overwrite(w) append(a) error out if exists(e) :[e] Key in w to overwrite output files. 8. main file for loading: [ris.dmp] > Key in the name of the area load file (from Step 1). 9. log file: [ris.log] > Press <Return> to use the default log file. 10. bad file :[ris.bad] >
43
_ _______________
Press <Return> to use the default bad file. 11. enter delimitation used in the files for loading: [] > Press <Return> to use the default delimiter. 12. Enter commit interval : [25] > Press <Return> to use the default interval. 13. Which schemas should be loaded? all (a) prompted (p): [a] > Press <Return> to load all schemas. 14. Which tables should be loaded? all (a) prompted (p) none (n): [a] > Press <Return> to load all tables. 15. both definition and data (b) definition only (o): [b] > Press <Return> for both. 16. ignore create error due to the existence of a table (y/n): [n] > Press <Return> to not ignore errors. 17. Which index definitions should be loaded? all (a) prompted (p) none (n): [a] > Press <Return> to load all index definitions. 18. Which views should be loaded? all (a) prompted (p) none (n): [a] > Press <Return> to load all views. 19. Which privilege definitions should be loaded: all (a) prompted (p) none (n): [a] > Press <Return> to load all privilege definitions. Ris loads the design database with the specified design data. load schema schema_name load table pdtable_12_0 xxx rows loaded load grant statement on PDtable_12_0 : : load table pdtable_80_0 xxx rows loaded load grant statement on PDtable_80_0
44
_ _______________
Once the load is completed, control returns to the CLIX prompt. 20. Key in /usr/ip32/pd3dtran/modeltrans.sh to transfer the design files of the Piping and Equipment area to their newly specified locations. This script will modify the type 63 values and occurrence numbers for the files. Enter Workstation Project Number Key in the name of the workstation project. 22. Enter VAX Project Network Address Key in the VAX node name. 23. Enter VAX Project Directory Key in the VAX directory where the project is located in the format ZFx:[xxx,xxx]. The system displays the Translate Project from Vax form. 21.
Translating Models
24.
Select Discipline Select the discipline and select Confirm ( ). Only Piping and Equipment are acceptable responses. The system displays the area files translated from the VAX for the specified discipline.
25.
Select Design Area Select the area for the model file(s) to be transferred and select confirm.
45
_ _______________
The system displays the following form which displays all the model files for the selected design area, and enables you to specify the destination.
26.
Specify Destinations Select the desired model file and key in the destination. You can use the scroll arrows to scroll through the listings. OR Select Move All to Same Destination to move all the listed files to a specified destination.
27.
Select confirm to accept the defined destination(s). The system generates an error log file in the /usr/tmp directory for each model. The file is named after the design file with a prefix of the letter e. For example, the error log file for the design file area01 is earea01. Each model which is successfully translated will have its source node and directory updated to the workstation. If a model received an error during translation, the screen displays Error Occurred in the destination directory. THEN Select cancel to exit the forms.
28.
Repeat the above steps (2 through 27) for each design area.
46
_ _______________
You can use the Revise Project Location option in the Project Environment Manager to relocate design files for disciplines other than Piping and Equipment. Depending on the discipline, you may need to run translators on these design files. Refer to the associated product documentation for information on translating design files for these disciplines.
Translating Models
Special Processing
The system performs the following actions in translating the model data from the VAX to the workstation. The gasket option is updated at each connect point as follows. If the end is bolted, the gasket option at that connect point inherits the components gasket option from the VAX model. If the end is not bolted, the gasket option defaults to 1. The weld type and weld type source are updated at each connect point as follows. If the weld type from the VAX user data is shop weld, the weld type is set to 11 (the first shop weld code list value) and the weld type source is set to by system. If the weld type from the VAX user data is field weld, the weld type is set to 21 (the first field weld code list value) and the weld type source is set to by user. If the end was not welded, the weld type attribute is set to 1.
Possible Errors
If the message Error Occurred displays for Piping models, examine the generated error log. If the message, Unable to find model_code in cp_geo_typ_tap file appears, you should add these model_codes to the cp_geo_typ_tap file and re-run translation on that model. If the error log is empty, some type of NFS failure occurred while trying to access the model file. Verify that the directories have been properly exported on the VAX. If the message Ref File Error displays, examine the the error log for a list of the reference files the system was unable to access. This error is only a problem if you have labels associated with the components of the inaccessible reference file.
47
_ _______________
2.4
Translating Drawings
Complete the following steps to translate all the drawings for the project. All the drawings generated for the workstation will have drawing type defined as the value for code list entry 2 of Standard Note Type 2000. (For the delivered Standard Note Library this value is piping.) Be sure you have translated all the model files before translating any drawing files. If you do not translate the models first, the translated drawings will not have updated reference file attachments.
VAX
1. Key in Run XPD:[14,54]WS_TRANSLATOR_DRW.EXE to translate ALL the drawing information in the design task database of the specified project. Translator for DRAWINGS Enter VAX Project Number for Translating to Workstation Key in the name of the VAX project to be translated. 3. Enter Workstation Project Schema Name Key in the schema name of the workstation project control database. Processing Drawing: drawing_name Successfully created drawing load file : project_name.drww Processing Completed
2.
Workstation
Complete the following actions to translate the Drawing files to the workstation. 1. 2. 3. Use fmu or ftp to copy the drawing load file (project_name.drww) to the workstation. Key in rislod to load the schema. Set model ansi ON(y/n) :[y] > Press <Return> to set model ansi on. 4. Set mode enable database? all(a) Specific(s) :[a] > Key in s to use specific databases. 5. Enter database name :[return] >
48
_ _______________
Key in the type of database you are using: informix, oracle, or ingres. 6. Enter database name :[return] > Press <Return> to accept the database. 7. File mode for all output files? overwrite(w) append(a) error out if exists(e) :[e] Key in w to overwrite output files. 8. main file for loading: [ris.dmp] >
Key in the name of the drawing load file (from Step 1). 9. log file: [ris.log] > Press <Return> to use the default log file. 10. bad file :[ris.bad] > Press <Return> to use the default bad file. 11. enter delimitation used in the files for loading: [] > Press <Return> to use the default delimiter. 12. Enter commit interval : [25] > Press <Return> to use the default interval. 13. Which schemas should be loaded? all (a) prompted (p): [a] > Press <Return> to load all schemas. 14. Which tables should be loaded? all (a) prompted (p) none (n): [a] > Press <Return> to load all tables. 15. both definition and data (b) definition only (o): [b]> Press <Return> for both. 16. ignore create error due to the existence of a table (y/n): [n] > Key in yes to ignore these errors. 17. clear existing data from table before loading (y/n): [n] >
49
_ _______________
Press <Return> to not clear the tables. These tables should already be empty at this point. 18. Which index definitions should be loaded? all (a) prompted (p) none (n): [a]> Press <Return> to load all index definitions. 19. Which views should be loaded? all (a) prompted (p) none (n): [a] > Press <Return> to load all views. 20. Which privilege definitions should be loaded? all (a) prompted (p) none (n): [a] Press <Return> to load all privilege definitions. RIS loads the database and displays the number of rows loaded into each table. The system will display errors while creating the tables. This is NOT a problem; the tables were created by the Project Administrator during project creation. load existing table pdtable_124 xx rows loaded load grant statement on pdtable_121 : load grant statement on pdtable_124 When the process is complete, control returns to the CLIX prompt. 21. Key in /usr/ip32/pd3dtran/drawtrans.sh to transfer the drawing files to the workstation. This process also modifies the drawings type 63s, occurrence numbers, and reference file attachments. Enter Workstation Project Number Key in the name of the workstation project. 23. Enter VAX Project Network Address Key in the VAX node name. 24. Enter VAX Project Directory Key in the VAX directory where the project is located in the format ZFx:[xxx,xxx]. The system displays the Update Drawing form which displays all the drawing files for the specified project, and enables you to set the destination.
22.
50
_ _______________
25.
Select the desired drawing file and key in the destination node and directory path. You can use the scroll arrows to scroll through the listings. OR Select Move All to Same Destination to move all the listed files to a specified destination.
26.
Select confirm to accept the defined destination(s). Relocation of Drawings Completed For each drawing which is successfully translated, the system updates the source node directory to the workstation. If a drawing received an error during translation, the message Error Occurred displays as the destination directory.
Possible Errors
The system generates an error log for each drawing in the /usr/tmp directory. The log file has the same name as the drawing file with a prefix of e. If the message Error Occurred displays, examine the generated error log. If the error log is empty, some type of NFS failure occurred while trying to access the drawing file. Verify that the directories have been properly exported on the VAX. If the message Ref File Error displays, review the error log for a list of the reference files it was unable to access. This error is only a problem if you have labels associated with the components of the inaccessible reference file.
51
_ _______________
2.4.1
Drawing Borders
If you created customized drawing borders on the VAX, you will need to copy these border files to the workstation. The Drawing Manager uses the following guidelines to determine which drawing border to attach. The directory and network address for the drawing border is defined with the Reference Database Management Data option of the Reference Data Manager. The file specifications for the drawing borders are determined by the following naming convention. dwgbrd_<drawing_type>.<drawing_size> drawing_type is the code-list number from Standard Note Type 2000 for the drawing type.
Standard Note Type 2000 Number 535 537 540 641 643 651 661 663 665 667 731 841 851 865 971 Text Foundation Location Drawings Piling Drawings Structural Perspectives, Plans, Sections and Details Plot Plans Equipment Arrangement Drawings Piping Underground Drawings Equipment Orientations Piping One Line Drawings Piping Perspectives, Plans, Sections and Details Pipeline Alignment Drawings Instrument Location Plans Electrical Area Classification Drawings Electrical Underground Drawings Lighting Perspectives, Plans, Sections and Details HVAC Perspectives, Plans, Sections and Details
drawing_size is the code-list text from Standard Note Type 1202 for the drawing size.
Standard Note Type 1202 Number 1 2 3 4 5 6 101 102 103 104 105 Text A B C D E F A0 A1 A2 A3 A4
For example, the drawing border name for an A size piping drawing is dwgbrd_665.a. To use a drawing border from the VAX, use fmu or ftp to copy the drawing border file to the workstation. Move the border file to the directory defined for drawing borders and use the naming convention described above. For example,
52
_ _______________
fmu vax.user.passwd rec pds_drawing_border:edrwbrda.dgn dwgbrd_665.a fmu vax.user.passwd rec pds_drawing_border:mdrwbrda0.dgn dwgbrd_665.a0
53
_ _______________
54
_ _______________
3. Translating Reference Data
This section describes the steps required to translate reference data such as the Label Description Library or Graphic Commodity Library from the VAX to the workstation.
Translating Reference Data
3.1
Label Description Library

Complete the following steps to translate the label description library to the workstation.
VAX
1. 2. Key in run XPD:[14,54]TRANSLATE_LABEL_LIB.EXE Enter Project Number: Key in the number of the VAX project being translated.
3. Reference Data
3.
Enter Label Library File Name Key in the name of the label library to be translated.
4.
Enter Intermediate File Name Key in the name of the temporary file. The executable displays each label type that it is loading into the temporary file.
5.
When it is finished, use fmu or ftp to copy this file to the workstation for processing by the workstation executable.
Workstation
1. Key in /usr/ip32/pd3dtran/bin/<c?00>/lablib (where <c?00> represent the type of processor c100 or c400) 2. Enter Object file name to be translated Key in the name of the file you copied from the vax. 3. Enter new file name: Key in the name of the label description library to be created.
55
_ _______________
The system processes the temporary file and creates the specified library file. After translating the library, use the Label Description Library Manager to edit the new label library. You will need to account for attributes that may have changed in length or type. One such label that will require editing on the workstation is label 321. In addition, some attributes from the VAX are no longer used.
56
_ _______________
3.2 Physical and Graphic Commodity Libraries
Complete the following steps to create neutral files which can be used to load the Physical Dimension Library, Graphic Commodity Library, Piping Assembly Library, Piping Job Spec Tables, and the Standard Note Library.
Physical and Graphic Commodity Libraries
VAX Before using this command

You must have READ and WRITE privileges for the directories where the files will be extracted. Create a list file to identify the items to be extracted from the library. This is an ASCII file with 1 file name per line. An easy way to create the file is to
3. Reference Data
Key in lib/list=list_file pro_dd_pdsspec:zx_pcdim.tlb to create a list file for the physical dimension library. Edit the created file list_file.lis to remove the header information.
Operating Sequence
1. 2. Key in run xpd:[14,54]trans_phys_graphics_commodity.exe Enter Text Library Name Key in the name of the text library to be translated such as pro_dd_pdsspec:zx_pcdim.tlb. 3. Enter List File Name Key in the name of the list file which defines the table/source files to be processed. 4. Enter Vax Destination Directory Key in the directory that has been set up as an NFS mountable directory. The system extracts all the modules in the list and writes them to the destination directory in a format that is understandable by UNIX. 5. Repeat the above steps for each library to be translated.
57
_ _______________
Library graphic commodity library piping assembly library spec table library standard note library File Name pro_dd_pdspipe:g_commodity.tlb pro_dd_pdspipe:assembly.tlb pro_dd_pdsspec:zx_pjstable.tlb pro_dd_pdsspec:zx_note.tlb
Workstation
Use the Reference Data Manager to load the neutral files into an empty library file. Make sure the default node and path are set to the mounted VAX directory when creating libraries (or use fmu or ftp to copy the neutral files to the workstation).
Replacing Tutorials with Forms

Many of the Eden modules in the Graphic Commodity Library reference tutorials for placement information. For any Eden modules which activated tutorials on the VAX, you should reference the appropriate form from the /usr/ip32/pdshell/forms/ directory. Refer to Appendix A for a listing of the delivered forms used to place components, piping specialties, instruments and pipe supports.
58
_ _______________
3.3 Material Description Library
Complete the following steps to create neutral files which can be used by the workstation to load the Short Description Library, Long Description Library, and Specialty Description Library.
Material Description Library

You must have READ and WRITE privileges for the directories where the files will be extracted. Create a list file which contains a list of the modules to translate. This is an ASCII file with 1 file per line. An easy way to create this list is to: Key in lib/list=list_file pro_dd_pdsspec:zx_shortdescr.tlb
3. Reference Data
Edit the created file list_file.lis to remove the header information.
Operating Sequence
1. 2. Key in run xpd:[14,54]matl_descr_file_extraction.exe Enter Material Description Library Name Key in the name of the text library to be translated such as pro_dd_pdsspec:zx_shortdescr.tlb. 3. Enter List File Name Key in the name of list file which defines the files to be processed. 4. Enter Vax Destination Directory Key in the directory that has been set up as an NFS mountable directory. (You must have privilege to write to this directory.) The system extracts all the modules in the list and generates a new file in the VAX destination directory. This file is written in a format that it is understandable by UNIX.
59
_ _______________
Workstation
Login on the workstation and use the Reference Data Manager to load the neutral files into the desired libraries. Make sure the default node and the path are set to the mounted VAX directory when creating libraries (or use fmu or ftp to copy the neutral files to the workstation).
60
_ _______________
3.4 Piping Job Specification Files
Piping Job Specification Files
Complete the following steps to create neutral files which can be used to load Piping Job Specification data into the Material Reference Database. These translators will process piping materials class data, piping commodity data, instrument data, specialty data and tap data.

You must have READ and WRITE privileges for the world on the directories where the files will be extracted. Create two list files to identify the items to be extracted from the library. These are ASCII files with 1 file name per line. An easy way to create the files is to: Key in lib/list=list_file pro_dd_pdsspec:zx_pjs.tlb
3. Reference Data
Edit the created list_file.lis file to remove the header information. Separate the list file into two separate list files. Copy the original list file. Edit the original list file so that it contains only the .pcd files. Edit the second list file (copy) so that it contains all the piping material classes, instruments, and taps. No .pcd files should be contained in this list. Both lists will be processed by the specfile extraction executable.
Operating Sequence
1. 2. Key in run xpd:[14,54]specfile_extraction.exe Enter Text Library Name Key in the name of the text library to be processed such as pro_dd_pdsspec:zx_pjs.tlb. 3. Enter List File Name Key in the name of the list file which identifies the specification files for piping materials class, instruments, and taps.
61
_ _______________
4. Enter Vax Destination Directory Key in the directory that has been set up as an NFS mountable directory. The system extracts all the modules in the list file and writes the files in a format that is understandable by UNIX. 5. Repeat steps 1 through 4 for the list file which identifies the specification data for piping commodity (.pcd) data.
Workstation
Use the Reference Data Manager to load the neutral files into the Piping Job Spec.
62
_ _______________
3.5 Alphanumeric Commodity Library
Complete the following steps to translate size dependent data and implied data from the Alphanumeric Commodity Library on the VAX. There is no Alphanumeric Commodity Library for Workstation PDS; this information is stored in the Specification/Material Reference Database. You must have READ and WRITE privileges for the world on the directories where the files will be extracted.
Alphanumeric Commodity Library
Size Dependent Data

VAX
Use the following procedure for size dependent data which is in the neutral file. 1. Create a list file which contains a list of the modules to translate. This is an ASCII file with 1 file per line. An easy way to create this list is to:
3. Reference Data
Key in lib/list=list_file
pro_dd_pdsspec:zx_ancom.tlb
Edit the created file list_file.lis to remove the header information. 2. 3. Key in run xpd:[14,54]specfile_extraction.exe Enter Text Library Name Key in the name of the text library to be processed such as pro_dd_pdsspec:zx_ancom.tlb. 4. Enter List File Name Key in the name of the list file which identifies the modules to be processed. 5. Enter Vax Destination Directory Key in the directory that has been set up as an NFS mountable directory. The system extracts all the modules in the list file and writes the files in a format that is understandable by UNIX. 6. 7. key in run xpd:[14,54]size_dependent_file_extraction.exe Enter Neutral File Name
63
_ _______________
Key in the name of the generated neutral file (from Step 5). 8. Enter Size Dependent Output File Name: Key in the name of the output file to be generated for size dependent data. The system extracts all modules in the neutral file and writes the specified output files in a format that is understandable by UNIX. 9. Repeat Steps 6 through 8 for all the neutral files created from the list file.
Workstation
Copy the files to the workstation and use the Piping Job Spec Manager to load these files into the Material Reference Database.
Implied Data
VAX
Use the following procedure for implied data which is in the neutral file. 1. Create a list file which contains a list of the modules to translate. This is an ASCII file with 1 file per line. An easy way to create this list is to: Key in lib/list=list_file pro_dd_pdsspec:zx_ancom.tlb
Edit the created file list_file.lis to remove the header information. 2. 3. Key in run xpd:[14,54]specfile_extraction.exe Enter Text Library Name Key in the name of the text library to be processed such as pro_dd_pdsspec:zx_ancom.tlb. 4. Enter List File Name Key in the name of the list file which identifies the modules to be processed. 5. Enter Vax Destination Directory Key in the directory that has been set up as an NFS mountable directory. The system extracts all the modules in the list file.
64
_ _______________
6. 7. Key in run xpd:[14,54]implied_data_file_extraction.exe Enter Neutral File Name Key in the name of the previously generated neutral file. 8. Enter Implied Data Output File Name Key in the name of the output file to be generated for implied data. The system extracts all modules in the neutral file and writes the specified output files in a format that is understandable by UNIX.
Alphanumeric Commodity Library
Workstation
Copy the files to the workstation and use the Piping Job Spec Manager to load these files into the Material Reference Database.
3. Reference Data
65
_ _______________
3.6
MTO Format Files

Perform the following actions to translate the format files to the workstation. Use fmu or ftp to copy the format files to the workstation. Use the information on report format indexes in the Report Manager Reference Guide to change the indexes to their new format. In several cases the indexes have been combined to match the new DDL attributes. In most of these cases you only need to change a letter or number in each index code field.
66
_ _______________
3.7 Alphanumeric Model Builder Language Files
Perform the following actions to translate the Alphanumeric Model Builder Language files to the workstation. 1. 2. 3. Use fmu to copy the language file to the workstation. Change all the entity/attribute references to the new DDL references. The workstation execution of the piping model builder overrides the PROJECT and FILE keyword values. This allows one language file to be used for more than one project or file. However, these keywords are still required in the language file even though the project and file settings are ignored.
Alphanumeric Model Builder Language Files
3. Reference Data
67
_ _______________
68
_ _______________
Appendix A:
Piping Designer Forms
Appendix A Piping Designer Forms

This appendix lists the forms used to place components, piping specialties, instruments, and pipe supports. These form names are supplied in order for you to quickly access and modify them if necessary. All these forms are delivered with the PD_Shell product in the win32app\ingr\pdshell\forms directory.
Fire and Safety

FS001 FS013 FS10A FS11A FS2B Fire Monitor Fire Hydrant Fire Hydrant Fire Hydrant Fire Monitor
Instruments
A. PD_Design Forms
INA000 INA001 INA003 INA004 INA005 INA006 INA007 INA008 Instrument Components Instrument Instrument Ball Valve Instrument - Rotary Plug Valve Instrument - Butterfly Valve Instrument - Diaphragm Valve Instrument - Solenoid Valve Instrument - 3-Way Globe Valve
69
_ _______________
INA009 INA010 INA011 INA012 INA013 INA014 INA015 INA016 INA017 INA018 INA019 INA020 INA021 INA022 INA023 INA024 INA025 INA026 INA027 INA028 INB000 INB001 INB002 INB003 INB004 Instrument - 3-Way Ball Valve Instrument - 3-Way Rotary Plug Valve Instrument - Knife Valve Instrument - Automatic Recirculation Instrument - Angle Solenoid Valve Instrument - Angle Pressure Relief Valve Instrument - Pressure Refief Rupture Disc Instrument - with Upstream Regulator Instrument - with Downstream Regulator Instrument - Restriction Orifice Union Instrument - Orifice Plate Instrument - with Upstream Valve Instrument - with Downstream Valve Instrument - Cylindrical with 2 CPs Instrument - Rectangular with 2 CPs Instrument - Cylindrical with 3 CPs Instrument - Rectangular with 3 CPs Instrument - Cylindrical with 4 CPs Instrument - Rectangular with 4 CPs Instrument Indicator Instrument Components Instrument Instrument Instrument Instrument
70
_ _______________
Appendix A:
INB005 INB006 INB007 INB008 INB009 INB010 INB011 Instrument Instrument Diaphragm Valve Instrument Instrument 3-Way Globe Valve Instrument Instrument Instrument Orifice Plate
Piping Assemblies
PALCST PALT1A PALT3A PAS000 PAS001 PAS002 PAS003 PAS004 PAS005 PAS006 PAS007 PAS010 PAS011 PAS012 Control Station Assembly Temperature Assembly Dimension Temperature Instrument Construction (T3A) Place Piping Assembly Place Piping Assembly (valves and flanges) Place Piping Assembly (flow instrument connections) Place Piping Assembly (level instrument connections) Place Piping Assembly (temperature instrument connections) Place Piping Assembly (pressure) Place Piping Assembly (hydrostatic vents/drains) Place Piping Assembly (optional vents/drains) Pump Discharge Pump Suction Elbow, Reducer, Flange
A. PD_Design Forms
71
_ _______________
PAS013 PAS014 PAS015 Flange, Eccentric Reducer, Flange Flange, Concentric Reducer, Flange Temperature Indicator
Piping Commodities
PDplace_cmp Place Component
Piping Specialties
PSA000 PSA001 PSA002 PSA003 PSA004 PSA005 PSA006 PSA007 PSA008 PSA009 PSA010 PSA011 PSA012 PSA013 PSA014 Piping Specialty Components Piping Specialty - Flame Arrestor Piping Specialty - Hammer Arrester Piping Specialty - Exhaust Head Piping Specialty - Free Vent without Screen Piping Specialty - Free Vent with Screen Piping Specialty - Expansion Joint Piping Specialty - Swivel Joint Type 1 Piping Specialty - Swivel Joint Type 2 Piping Specialty - Swivel Joint Type 2 Piping Specialty - Dresser Coupling Piping Specialty - Flex Hose Piping Specialty Sample Cooler Piping Specialty - Spary Nozzle Piping Specialty - Single Basket Strainer
72
_ _______________
Appendix A:
PSA015 PSA016 PSA017 PSA018 PSA019 PSA020 PSA021 PSA022 PSA023 PSA024 PSA025 PSA026 PSA027 PSA028 PSA029 PSA030 PSA031 PSA032 PSB000 PSB001 PSB002 PSB003 PSB004 PSB005 PSB006 Piping Specialty - Sump Strainer Piping Specialty - T-Strainer Piping Specialty - Y-Strainer Piping Specialty - Basket Strainer Piping Specialty - Cone Strainer Piping Specialty - Flat Plate Strainer Piping Specialty - Inverted Bucket Steam Trap Piping Specialty - Float Thermostatic Steam Trap Piping Specialty - Liquid Expansion Steam Trap Piping Specialty - Thermostatic Steam Trap Piping Specialty - Thermostatic Steam Trap w/o Strainer Piping Specialty - Thermostatic Steam Trap w/ Strainer Piping Specialty - Box with 2 CPs Piping Specialty - Box with 3 CPs Piping Specialty - Box with 4 CPs Piping Specialty - Cylinder with 2 CPs
A. PD_Design Forms
Piping Specialty - Cylinder with 3 CPs Piping Specialty - Cylinder with 4 CPs Piping Specialty Components Piping Specialty Piping Specialty Piping Specialty Piping Specialty Piping Specialty Piping Specialty
73
_ _______________
PSB007 PSB008 PSB009 PSB010 Piping Specialty Piping Specialty Piping Specialty Piping Specialty
Pipe Supports
PSP000 PSP001 PSP002 PSP003 PSP004 PSP005 PSP006 PSP010 PSP011 Place Pipe Support Pipe Support - Type 1 Pipe Support - Type 2 Pipe Support - Type 3 Pipe Support - Type 4 Pipe Support - Type 5 Pipe Support - Type 6 Pipe Support - Type 7 Pipe Support - Type 8
Valve Operators
VA1003 VA1331 VA1332 VA2003 VA3003 VO0331 Chain Operator Gear Side Mounted Hand Wheel Gear Side Mounted Hand Wheel Valve Appurtenance - Floor Stand Valve Appurtenance - Extension Stem Gear Side Mounted Hand Wheel
74
_ _______________
Appendix A:
VO0332 VO0333 VO0334 VO0351 VOI331 VOP000 VOP003 VOP004 VOP005 VOP006 VOP009 VOP011 VOP017 VOP019 VOP021 VOP025 VOP027 VOP029 VOP031 VOP033 VOP035 VOP039 VOP043 VOP053 VOP331 Gear Side Mounted Hand Wheel Gear Side Mounted Hand Wheel Gear Side Mounted Hand Wheel Gear Side Mounted Hand Wheel Gear Side Mounted Hand Wheel Valve Operators Valve Operator - Handwheel Valve Operator - Type 4 Valve Operator - Inclined Handwheel Valve Operator - Type 6 Valve Operator - Short Wrench Valve Operator - Long Wrench Valve Operator - Lever Valve Operator - Short T-Handle Valve Operator - Long T-Handle Handwheel Special Type
A. PD_Design Forms
Valve Operator - Special Wrench Gear Side Mounted Hand Wheel Gear Top Mounted Inclined Hand Wheel Gear Side Mounted Hand Wheel - Type 1 Gear Side Mounted Inclined Hand Wheel Valve Operator - Lever Quick Action Gear Side Mounted Hand Wheel - Type 2 Gear Side Mounted Hand Wheel - Type 3 Gear Side Mounted Hand Wheel
75
_ _______________
ZO401D Operator
76
_ _______________
Glossary
absolute path name The sequence of directories, beginning with the root directory (/) that locates a file. See also path name and relative path name. The plane in a 3-D design upon which you can place elements and perform manipulations. The process which is displayed in the Process ID field; it controls the message fields, the menus, and the keyboard. The active process has a highlighted window icon strip. Software designed to meet specific needs, unlike system software which runs other software. A method of processing data which collects a series of operations into a group (or batch) and executes the group in a continuous stream without user intervention. A queue, or channel for moving requests, created through NQS. A batch queue handles scheduling for processes submitted through the Batch options screen menu. A point on a pipeline which separates piping segments so that they can be assigned different segment parameters. A branch point allows for placement of branch components. The button located in the upper right corner of a form containing a red X or the word cancel. Select the cancel button to exit the form or option. A permanent association of elements that can be stored and placed as a group, and then manipulated as individual elements. A column data type that stores alphanumeric character data. active depth
Glossary
active process
application software
batch processing
batch queue
branch point
cancel button
cell
character client
In network operations, a node which accesses data or performs a function on the remote resource (usually a server). All network operations (database, NFS, NQS) between two or more nodes establish a client/server relationship.
Glossary
column
An attribute of a database table. A group of columns defines a table in a database. Instructions from the user to perform a function on specified data. A button that appears in the upper right corner of a form and contains a green check mark or the word confirm. Select the confirm button to initiate a specified option.
command confirm button
77
_ _______________
coordinate coordinate system The location of a point along the X, Y, or Z axis. A geometric relation used to denote the location of points in the design cube. The most common coordinate system is the rectangular coordinate system, whereby points are located by traversing the X, Y, and Z axes of the design cube. Normally, coordinate systems have their origin defined as 0,0,0, though this is not required. Other coordinate systems are used to more easily express the coordinates of specific geometric entities. For example, you can use a spherical coordinate system to help define points on a sphere, and you can use a cylindrical coordinate system to help define points on a cylinder. An ordered set of absolute or relative data values that specify a location in a coordinate system. The image files written by System V for a number of reasons, the most common of which are memory violations, illegal instructions, bus errors, and user-generated quit signals. The pointer that the user moves on the screen to indicate an item or area. The mouse button used to place data points and tentative points, to accept previously selected elements, and to select commands from forms and menus. The field on a screen used to accept user-supplied data. Also known as key-in field. A point placed by pressing the data button on the mouse. Data points select commands from the panel menus and Menu Bar, place elements, identify and accept elements, and activate windows and perform window manipulations. A collection of comprehensive informational files having predetermined structure and organization that can then be communicated, interpreted, or processed by a specific program. The part of the database that is made of rows and columns and contains information about the project and design elements. The predetermined value of a parameter that is automatically supplied by the system or program whenever a value is not specified by the user. To remove, destroy, eliminate, or erase. A separating mark or space; a character or sequence of contiguous characters that mark the end of a string of characters. A nonaddressable component of a network, that is, a component onto which a user cannot log, for example, tape drive, disk drive, and floppy disk.
coordinates
core files
cursor data button
data entry field
data point
database
database table
default
delete delimiter
device
78
_ _______________
directory display-list box A file that contains the names of other files.
Glossary
A small box with horizontal dashes located at the end of a form key-in field. When selected, a list of the data available for that field is displayed. Input can then be selected from the list with a data point instead of keying in the information. The set of acceptable values for a value within a component. Another term for the dynamic function that attaches the cursor to an element so you can see it move. A term used in plane surveying that describes an east, or positive, difference in longitude. An object (project, drawing, element, and so forth.) of interest about which information is stored; a relational database table. See interference envelope. A UNIX path name that tells the system where to locate a file. A user-defined name given to an interactively created file. The name should be relevant to the contents of the file. An interface or screen menu designed with the I/FORMS product. Because many of the screen menus in the application software are built with I/FORMS, you must have the FORMS_S product on your workstation. The name of the entire path or directory hierarchy to a file, including the file name. See also relative path name. A portion of a form, such as a button, a field, or a checklist, that responds to information. Gadgets can display default values or act as data entry areas. The first items of information in a file which precede any actual data. The header contains information on the structure and contents of the file. A classified structure with superiors (roots) and subordinates (dependents) for grouping files or commands. A pictorial representation or image; a symbol that graphically identifies a command. A relational database management system supported by RIS. A relational database management system supported by RIS. An equipment modeling primitive or parametric component that is used in conjunction with or instead of model graphics for interference checking. Interference envelopes are given different levels and display symbology to distinguish them from primitives.
domain dragging
easting
entity
envelope file file specification filename
form
full path name
gadget
header
hierarchy
icon
Glossary
Informix Ingres interference envelope
79
_ _______________
invert elevation isometric The lowest point on the internal diameter of the pipe. Relating to or being a drafting system characterized by three equal axes at right angles; a view in which the horizontal lines of an element are drawn at an angle to the horizontal and all verticals are projected at an angle from the base. An attribute (column) in a table which is chosen as the access vehicle to individual rows of the table. The field on a screen used to accept user-supplied data. Also known as a data entry field. A point on an element, including vertices, to which you can snap. A word recognized by the software that provides access to a certain function. The strip at the top of the screen that contains icons for selecting commands. The area that appears in the MicroStation Command Window when you are working in a design file. It is divided into the Command Status field, the Current Command field, the Prompt field, and the Key-in field. A graphic representation or schema. An interconnection of host computers and workstations that enables them to share data and control. The term network can mean the devices that connect the system, or it can mean the connected system. Network File System, the system that provides access to data that is distributed among machines through an interconnection of host computers and workstations. NFS allows you to mount a remote resource to your local workstation so you can access the data as though it were local. NFS is usually used to access centralized data on a server. Any addressable device (such as a workstation or a server) that is connected to a network. The network enables the connected nodes to share data and system control. The hard-wired Ethernet address assigned to each node when it is manufactured. It is necessary for each node to identify and communicate with another node in the network. A name, or alias, that can be assigned to the node address of a device on a network. A term used to describe a north coordinate location in the plant coordinate system.
key
key-in field
keypoint keyword
menubar
message area
model network
NFS
node
node address
node name
northing
80
_ _______________
nozzle A special equipment modeling primitive that contains the connection point to piping. This point does NOT include a gasket allowance, but rather represents the face-of-flange coordinate. Network Queuing System, the software package that allows you to define network-wide batch and device queues. Use of NQS involves setting up local resource queues on the system(s) where the resources reside and setting up pipe queues on the systems that are to have access to the resources. A relational database management system supported by RIS. In coordinate geometry, the point where the x, y, and z-axes intersect. The point at which the coordinate system is placed. A view which is a projection of the model onto a plane along lines which are orthogonal to the plane. A property whose value determines the characteristics or behavior of something. NQS
Glossary
Oracle origin origin point orthogonal view
parameter
path
A sequence of directories leading to a file or a sequence of menus leading to a command. The sequence of directories leading to a file. See also absolute path name and relative path name. Plant Design System A controlled channel for moving requests to batch or device queues on remote systems and for receiving status and/or data in response. To identify a specific element, or indicate a specific point in the design file. A spatial element in geometry that may or may not have a boundary, but is level, having no elevations or depressions, and is three-dimensional. Reference Database. A collection of reference data containing information relative to industry design codes, vendors catalog data, job specifications, commodity libraries, graphics symbology, label descriptions, report formats and other information of a similar manner. The sequence of directories leading from the current directory to a particular file. See also path name and absolute path name. To turn; to change the angular orientation; to transform by revolution about a specific axis.
path name
PDS pipe queue
place data point plane
RDB reference database
Glossary
relative path name
rotate
81
_ _______________
row A unit of related information in a table. One collection of column values for a table. The animation dynamic that enables you to specify the position of a data point while the element changes as you move the cursor. A description of the overall structure of the rulebase or database. A file that outlines the overall logical structure of a rule base or a database. In network operations, the node which maintains common data or performs a common task needed by clients. All network operations (database, NFS, NQS) between two or more nodes establish a client/server relationship. Language developed by IBM for creating, modifying, and querying relational databases. The symbology of an element such as continuous dashes, dash-dot, solid, and so forth. The skin of a three-dimensional geometric element. The display style of an element, including color, style, and weight. A collection of data for quick reference, either stored in sequential locations in memory or printed as an array of rows and columns of data items of the same type. To switch; to change between two alternatives. A name that provides access to an account on the system. Data, either entered by the user or determined by the software, that are stored in an attribute. A quantity that may assume any one of a set of values. A quantity possessing both magnitude and direction, generally represented as a line. Vectors can be manipulated geometrically and are represented as a coordinate triple (x,y,z). The defined area of vision on a screen. A view allows you to see a prescribed volume of the design cube. Views are created with their own x, y, and z axes. The x,y plane of the view is parallel to the screen, while the z-axis can be thought of as coming straight out of the view towards you. The view axes maintain this relationship regardless of the rotation with respect to the design cube. See also active depth. External memory for a computer that can be used as if it were an extension of the computers internal memory. The software uses virtual memory to store data. This means that unneeded files and data, stay on the disk until they are called for. Because the internal processing memory stores a minimal amount of data, the software can perform processing more quickly. rubberbanding schema schema file server
Structured Query Language SQL style
surface symbology table
toggle user name values
variable vector
view
virtual memory
82
_ _______________
working directory The directory from which you are accessing files.
Glossary
Glossary
83
_ _______________
84
_ _______________
Index
A alphanumeric commodity library 63 model builder language files 67 C changes 15 connect point geometry 41 D define discipline data 31 document changes to 15 organization 10 purpose 9 F forms fire and safety 69 instruments 69 pipe supports 74 piping assemblies 71 commodities 72 specialties 72 placement 69 valve operators 74 G graphic commodity library 57 I ISOGEN translating break points 18 isometric drawings translating break points 18 L label description library 55 M material description library 59 MTO format files 66 P physical data library 57 pipe support only files 31 piping job specification translation 61 PJS translation 61 R report format files 66 S summary of technical changes 15 T technical changes 15 translating drawings 48 models 37 project environment and design data 31 discipline data 31 drawings 48 models 37 seed data 32 reference data 55 alphanumeric commodity library 63 model builder language files 67 label description library 55 material description library 59 MTO format files 66 physical and graphic commodity libraries 57 piping job specification 61
Index
Index
85
_ _______________
translating (continued) seed data 32 VAX PDS 3D data 17 VAX setup 18 ISOGEN break points 18 workstation setup 29 typefaces 11 V VAX translation setup 18 W workstation translation setup 29
86

3DTRAN

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

3DTRAN

Caricato da

Copyright:

Formati disponibili

PDS 3D VAX to Workstation Translation (PD_3DTRAN)

This document replaces DEA503772.

Warranties and Liabilities

If You Need Assistance

Intergraph General Information

Customer Response Center (U.S. Only)

Training Registration (U.S. Only)

Regional Sales Information (U.S. Only)

Educational Media Contacts

Document Prerequisites / Audience

About this Document

More information indicates there is additional or related information.

Summary of Technical Changes

Version 06.00.00.00 Changes

Translating VAX PDS 3D Data

1. Translating VAX Data

VAX Project Environment Data

VAX NFS Setup

1. Translating VAX Data

Mapping Database Attributes

1. Translating VAX Data

3. piping_component_model_entity 1 -1 2 3 4 5 6 7 49 50 51 52 53 .1 .2 .3 .4 .5 .6 .7 .8 .9 .10 .11 .12 .13

1. Translating VAX Data

1. Translating VAX Data

7. inst_component_analysis_entity -1 52 53 54 29 30 -1 43 .1 .2 .3 .4 .5 .6 .7 .8 pntr_to_instr_comp_model_data instrument_component_remarks standard_note_number_1 standard_note_number_2 construction_status hold_status approval_status isometric_drawing_number

1. Translating VAX Data

.119 unique_name max_att = 36

1. Translating VAX Data

Editing the PD3DTRAN Scripts

Translating Project Environment and Design Data

2. Project & Design Data

Defining Discipline Data

Translating Seed Data

Sample Project Environment Load File

Translating Seed Data

2. Project & Design Data

Translating Seed Data

2. Project & Design Data

2. Project & Design Data

2. Project & Design Data

2. Project & Design Data

Dual Connect Point Geometry Type

Processing Processing Model : zfxx:[xxx,xxx]model_name

2. Project & Design Data

2. Project & Design Data

2. Project & Design Data

2. Project & Design Data

2. Project & Design Data

2. Project & Design Data

Translating Reference Data

Label Description Library

Physical and Graphic Commodity Libraries

VAX Before using this command

Replacing Tutorials with Forms

Material Description Library

VAX Before using this command

Edit the created file list_file.lis to remove the header information.

Piping Job Specification Files

VAX Before using this command

Alphanumeric Commodity Library

Size Dependent Data

Alphanumeric Commodity Library

MTO Format Files

Alphanumeric Model Builder Language Files