Open Steel User Guide

OpenSteel User Guide

AVEVA Sol ut io n s L t d

Disclaimer Information of a technical nature, and particulars of the product and its use, is given by AVEVA Solutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaim any and all warranties and conditions, expressed or implied, to the fullest extent permitted by law. Neither the author nor AVEVA Solutions Ltd, or any of its subsidiaries, shall be liable to any person or entity for any actions, claims, loss or damage arising from the use or possession of any information, particulars, or errors in this publication, or any incorrect use of the product, whatsoever.

Copyright Copyright and all other intellectual property rights in this manual and the associated software, and every part of it (including source code, object code, any data contained in it, the manual and any other documentation supplied with it) belongs to AVEVA AVEVA Solutions Ltd or its subsidiaries. All other rights are reserved to AVEV VEVA A Solutions Ltd and its subsidiaries. The information contained in this document is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without the prior written permission of AVEVA Solutions Ltd. Where such permission is granted, it expressly requires that this Disclaimer and Copyright notice is prominently displayed at the beginning of every copy that is made. The manual and associated documentation may not be adapted, reproduced, or copied, in any material or electronic form, without the prior written permission of AVEVA Solutions Ltd. The user may also not reverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of the product described in this publication may be incorporated into any third-party software, product, machine, or system without the prior written permission of AVEVA Solutions Ltd, save as permitted by law. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminal prosecution. The AVEVA products described in this guide are to be installed and operated strictly in accordance with the terms and conditions of the respective license agreements, and in accordance with the relevant User Documentation. Unauthorised or unlicensed use of the product is strictly prohibited. First published June 2008 © AVEVA AVEVA Solutions Ltd, and its subsidiaries AVEV AVEVA A Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom

Trademarks AVEV AVEVA A and Tribon are registered trademarks of AVEVA AVEVA Solutions Ltd or its subsidiaries. Unauthorised use of the AVEV VEVA A or Tribon trademarks is strictly forbidden. AVEV AVEVA A product names are trademarks or registered trademarks of AVEV VEVA A Solutions Ltd or its subsidiaries, registered in the UK, Europe and other countries (worldwide). The copyright, trade mark rights, or other intellectual property rights in any other product, its name or logo belongs to its respective owner.

OpenSteel OpenSteel User Guid e

OpenSteel OpenSteel User User Guide Gui de

Co n t en t s

Pag e

User User Guide Guid e Intr oduc od ucti tion on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1 Glos sary sar y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1 Expor Exp or ti ng to SDNF SDNF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1 Target Inf ormati or mation on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2 Export/Import different different SDNF Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4 Auto-detection of of SDNF Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4 Export Information Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:5

Run Infor Inf or matio mat io n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:8 AVEVA OpenSteel Open Steel - Exp or t Fo r m . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3: 9 Export and Cancel Cancel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:10 The Export Form Bar Bar Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:10 The Export Process Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:10 Exporting Linear Linear Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:12 Exporting Plates Plates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:14 Exporting Connections Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:16

Testi ng AVEVA Open Steel Expo Ex port rt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:18 3:18 Initial Configuration. Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:18 Preparing to Export Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:19 Creation of Export File File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:22 Checking the SDNF Output Output File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:22

Impor Imp or t f ro m SDNF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1 Source Sour ce Inf ormati or mati on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2

i

1.5


Import Impo rt Info rmatio rm atio n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4 Run Infor Inf or matio mat io n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6 OpenSt eel - Imp or t Form Fo rm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:9 Impor Imp or t and an d Canc el . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:9 Impor Imp or t Form Fo rm Bar Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:10 Impor Imp or t Pr ocess oc ess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:10 Comparis Comp arison on and Mergi ng Processes Proc esses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:13 The Comparison Comparison Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:14 The Merging Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:16 Deleted Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:17

Validat Vali datio io n Proc Pr ocess ess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:18 Highli High li ght ing in g Chang es in the th e Desi Design gn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:19 Highlighting by Import Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:19 Highlighting by Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:20

Testi ng AVEVA Open Steel - Imp ort or t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:21 Initial Configuration. Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:21 Preparing to Import. Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:22 Importing the SDNF File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:25 Comparing the Imported Imported Model with the Original. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:26 Performing a Validity Validity Check. Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:26

Bo lt Repor ts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1 An ch or Bo lt Lo cat i on s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5: 1 An ch or Bo l t Qu ant it ies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5: 2

Tech Technic nic al Info rmation rmat ion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1 SDNF SDNF - Str Str uct ural ur al Steel Detaili ng Neut ral Fil e Format . . . . . . . . . . . . . . . . . . . . 6:1 Export/Import different different SDNF formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1 Auto-detection of of SDNF formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:2 Packet 00 - Title Packet Packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:4 Packet 10 - Linear Linear Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5 Location of Linear Linear Members in in Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5 Packet 30 - Member Member Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:7 Packet 40 - Connection Connection Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:7 Packet 50 - Grid Packet Packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:8

Recommended Recomm ended SDNF Fil File e Suff ix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:8 SDNF SDNF File Header Info rmatio rm atio n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:8

ii

1.5


Member ID Numb ers at SDNFv3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:9 Using Usin g Li near Member Cut backs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:10 Exporting Exporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:12 Importing Importing

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:15

Cardi nal Point Poi nt s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:18 Defaul t Orien Or ientat tatio ions ns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:19 Mirror Mirroring ing

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:20 6:20

Pline Pli ne Selec ti on Rules Rul es . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:21 Use of Pline Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:23

UDAs UDAs

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:23 6:23

General Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:23 Structural Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:23 Project Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:24

Cross Cro ss Referenci Referen ci ng Models Mod els . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:25 Element created created in DESIGN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:25 Element created created outside DESIGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:25

Versi on Number Num berin in g . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:25 On Transfer from Design:. Design:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:26 On Transfer into Design: Design: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:26

Exclu Exc lu sion si on s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:26 Issues

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:27 6:27

Docum ent Revisi on Histo ry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1 Ap A p pen d i x : Sampl Sam pl e SDNF Fil e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A : 1 App A pp end en d ix : Samp le Expo Ex po r t L o g File Fi le . . . . . . . . . . . . . . . . . . . . . . . . . .B: .B : 1 Ap A p pen d ix : Samp l e Imp Im p or t Lo g Files Fi les . . . . . . . . . . . . . . . . . . . . . . . . .C: . C:1 1 Br ief Format For mat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:1 Linear Members Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:1 Plat Plates es

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:1 C:1

Verbo se For mat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:4

Ap A p pen d i x : Samp l e Vali d it y Chec Ch eck k L o g Fil e. . . . . . . . . . . . . . . . . . . .D:1 .D: 1

ii i

1.5


iv

1.5

OpenSteel OpenSteel User Gui de Introduction

1

In t r o d u c t i o n AVEV AVEVA A OpenSteel is the interface for the PDMS DESIGN module which allows the user to export and import files using the Structural steel Detailing Neutral File (SDNF) format. The SDNF format was originally defined by the Intergraph FrameWorks user community for the transfer of steel data. The format is in the public domain and is therefore available to be considered as a suitable means of transferring data between 3D steel detailing packages and PDMS DESIGN. The AVEVA OpenSteel interface uses a large proportion of the information transferable in SDNF format. Refer to Technical Information describing SDNF, SDNF, its format and contents. This version of AVEVA OpenSteel is compatible with PDMS on the Windows XP operating systems. The manual is in three main parts: Export, Import and Technical Technical Information. Glossary

explains terms used in this manual

Exporting to SDNF

explains how to export a steel structure to an SDNF file

Import from SDNF

explains how to import a steel structure from an SDNF file

Bolt Reports

explains how to extract reports of Anchor Bolts from the model using the Bolt Report templates

Technical Information

contains technical information

Appendix: Sample SDNF File

gives a brief extract of an SDNF file produced by the A the AVEV VEVA A OpenSteel interface

Appendix: Sample Export Log File

gives an example Export Log file

Appendix: Sample Import Log Files

shows sample log files from an Import process according to the mode specified

Appendix: Sample Validity Check Log File

shows a sample log file from an Import validity checking process to check for duplicate mark numbers

1:1

1.5

OpenSteel OpenSteel User Gui de Introduction

1:2

1.5

OpenSteel OpenSteel User Gui de Glossary

2

Gl o s s ar y This section explains terms used in this manual. Cardinal Cardinal Poin t

An SDNF concept representing p oints of significance on the 2D profile and mapped in DESIGN onto the Pline (PLIN) elements in the Catalogue.

External Package

The system with which this interface is communicating. It may be a 3D steel detailing package, an intermediate format or system or even some format related to a particular steel fabricator or producer.

Linear Member

An SDNF Entity mapped to the Design Section (SCTN) element.

Plate

An SDNF Entity mapped to the Design Panel (PANE) (PANE) element.

PML/F&M

The AVEVA AVEVA PDMS programmable macro language, allowing users to create their own user interface.

SDNF SDNF (Stru (Stru ctu ral Steel Detailing Detailing Neutral Neutral File Format)

Defined by the Intergraph FrameWorks user community for the transfer of steel data. It is in the public domain and is therefore available to be considered as a suitable means of transferring data between 3D steel detailing packages and DESIGN.

Source Package

The external package from which an imported SDNF file is coming.

Target Package

The external package for which an exported SDNF file is destined.

UDA (User Defined At tr ib ut e)

An attribute in DESIGN which the user can define and attach to specific elements. This interface requires a certain set of UDAs for storing SDNF-specific data.

2:1

1.5

OpenSteel OpenSteel User Gui de Glossary

2:2

1.5

OpenSteel OpenSteel User Gui de Exporting to SDNF

3

Ex p o r t i n g t o SDNF This section explains how to export a steel structure to an SDNF file. It gives guidance about what options are available. For more detailed information refer to Technical Information and the appendices. The user can display the main AVEVA Open Steel - Exp or t form by one of two ways: On the DESIGN General Application menu bar, select Utilities > General from the drop down menu, or, if the user is in the Steelwork Application select Utilities > Steelwork . The User General Utilities menu bar is displayed.

The user will also find the SDNF entry in the Beams & Columns Application , with the Beams & Columns option under the Utilities menu. To display the AVEVA Open Steel - Expo Ex po rt form from the User General Utilities menu bar, select Expor t>(d) AVEVA AVEVA OpenSteel.

3:1

1.5


3.1

Tar g et In f o r m at i o n The Export Target Information form contains information about the 3D steel detailing package to which the SDNF file is to be transferred. This form is displayed by clicking the Target infor mation button on the main AVEVA Open Steel - Exp or t form.

The interface requires two external mapping tables for each Target Package to check that the Target Package can accept the data. It also may use the Profile Orientation mapping

3:2

1.5


table if necessary. The mapping tables are for the Steel Profiles, Materials and for mapping the Profile Orientations between PDMS and the neutral file. The section on user customisation in the Installation Guide tells the user how to arrange these files on your file system and what format they are to be. The interface a lso needs to know where the external mapping files are located on your computer network. For this, internal mapping tables are required. Refer to the AVEVA AVEVA OpenSteel Installation Guide which explains how to configure the interface to tell it where all the files are located. The user may have a generic pair of mapping tables to map between PDMS and SDNF for a particular steel fabricator, for example, or the user may have a similar pair for each 3D steel detailing package. The current file settings are indicated on this form. The user will notice that changing the Target Package by using the Target Package selector button on the right-hand side of the form may cause the text to change giving the full path names of the respective files. Do not be concerned that the path name may be truncated by the insertion of the ellipsis (…): it is modified only for display purposes on the form. The system also checks that t hese files are compatible with the Target Package by checking the identification line at the top of each mapping table. Refer to the AVEVA AVEVA OpenSteel Installation Guide for details about the format of these mapping files. There are two main options on this form: Au to and Manual . These can be activated by selecting the appropriate toggle button on the left-hand side of the form. The Au to option causes the interface to select automatically the Profile and Material mapping tables for the Target Package indicated by the Target Package selector gadget on the right hand side of the form, according to the system configuration files. The Manual option activates two other buttons, which are greyed out for the Au to option. Selecting this option changes the form to be similar to below.

The user can select the file type using the Profiles , Materials or Orient'n toggle buttons and enter the full path name of the file in the data entry area. The user can also include system environment variables in the path name as long as they are in the proper AVEVA PDMS format, e.g. %ENVVAR% being the PDMS representation of the ENVVAR environment variable.

3:3

1.5


On clicking carriage return, the interface will check for existence of the file and compatibility with the Target Target Package indicated by t he Package option gadget. Note: The check is only that the file applies to the Target Package and not that it is a correct file type.

The user can either choose by hand which mapping file to use by entering its name in the text data entry field, or by using the Browse option to bring up a File Browser. The user may use this browser to search for the relevant mapping file. Once the user has entered all the correct data on the Export Target Target Informatio n form, click OK and the interface variables will be updated. Clicking CANCEL will remove the form, leaving the original interface variables unchanged. Error and L og File Messages Messages

3.1.1

Internal error

Internal lists are not in step

Cannot find suitable internal internal mapping list

Internal mapping files not found.

Suitable Mapping Table File not found

Mapping table found is not for the correct Target Target Package, or it does not exist.

Not a suitable Mapping Table Fil e

Incorrect format of file, or empty file, or wrong Target Package.

Bad Map File

Mapping file is not correct format. Possibly it is from another operating system.

Error o n OpenSteel OpenSteel File Browser form

The user has entered incorrect data on the file browser form.

Export/ xport/IImport mport diffe different rent SDNF Forma ormats The interface can read and write SDNF files to both version 2 and version 3 of the format. The format is described elsewhere, or the user can contact the software supplier for details. Principally, Principally, there are many more records attached to each linear member and the method of plate definition has changed. The interface does not use this information yet. On the Export Target Target Inform ation form there is a drop down list which the user can use to select which SDNF version to output.

3.1.2

Auto Auto--dete detect ctio ion n of of SD SDNF Forma ormatts The system can automatically detect which version of the file the user is inputting and set the import drop down list accord ingly. ingly. The user can set up the default SDNF format version in the SDNFUserData.pmlfnc file in the pml/functions directory. This is the !!SDNFSDNFVersion variable which must be precisely one of the 2 suggested text strings.

- - De Def aul t SD SDNF f i l e f or mat - - cu c ur r ent l y | 2. 0| or or | 3. 0| ! ! SDNFSDNFVer FVer si on

= | 3. 0|

3:4

1.5


The user can inspect the file header as before and an added line will show which SDNF version it has found.

If the user changes the version setting, the s ystem will not work because it is expecting a file of a radically different format. However, the interface will fail in a controlled manner producing a "catch-all" error message.

If the user manually select the wrong SDNF version, the user may also get an error message in the log file about syntax errors in the incoming file. This is beca use the Packet 0 records are different.

3.1.3

Ex p o r t In f or or ma mat i on on The Export Information Information form contains information about the actual Export process. This form is created by clicking the Export information button on the AVEVA Open Steel Export form.

3:5

1.5


The user can either type the full directory path name of the output file, or use the Browse button to bring up a File Browser. The interface tests to see if the file exists and if it does, the user will be asked whether to overwrite it. If the file does exist and the user wants to overwrite it, the file mode beside the Browse button will change from WRITE to OVERWRITE. The output file is rechecked for write/overwrite status during the actual Export process. This is because the user can perform repeat Exports without changing the output file name. Note: If the user does not enter the full path name and just a plain file name, the output file will be created in the directory which started PDMS. The user may also include system environment variables in the path name as long as they are in the proper PDMS format, e.g. %ENVVAR% being the PDMS representation of the ENVVAR environment variable.

The SDNF file may have several sections: a header, Packet 00; a set of Linear Members, Packet 10; a set of Plates, Packet 20; and a set of Connection Details, Packet 40. The header is compulsory: any other Packets are optional. Selecting the information to be contained in Packet 00 is performed by navigating to, or below, the relevant PDMS Design SITE, ZONE or STRU element which contains the required header information. This is done by using the Members list window at the bottom of the main Export form. When at or below the correct element, click the Use CE button on this form and the source text will indicate from where the interface will get the information. If there is not enough space on the form the element's reference number is output rather than its name.

3:6

1.5


The user can look at the information contained by the chosen header element by clicking the Inspect button. This brings up the Export File Header Details form.

At first the entry fields are greyed out but the user can read the contents. To modify the contents of the fields click the Edit button on the Export File Header Details form and the fields become active allowing the user to enter any revised data. Click Ap pl y and the data will be transferred back to the chosen header object, overwriting the original data. Clicking Cancel will leave all the data unchanged.

The Previous Revision and Transfer information, if changed, will be transferred not to the header object but to the Configuration Site for the specific current MDB/user combination. During Export or Import AVEVA OpenSteel will inspect all the available Configuration Sites in order to elucidate the most recent Transfer letter and Revision number. This will then get stored in the site for the current user. This allow multi-user access to the da tabases. Using the toggles on the Export Information form, the user can select whether to export Packet 10 (Lin (Lin ear Members Members ) and/or Packet 20 (Plates) . The user cannot output Packet 40 (End Connections) without outputting Packet 10 (Linear Members). If the user does not want Packet 10, the sub-options, Linear Members only and Linear Members + End Connections are inactivated and greyed out.

3:7

1.5


The interface will check that the user is attempting to Export something and output a message accord ingly. ingly. Once all the correct data has been entered on the Export Information Information form, click OK and the interface variables will be updated. Clicking CANCEL will remove the form, leaving the original interface variables unchanged. Error and L og File Messages Messages Export fi le already already exists

File exists, the user will get the op tion to overwrite it.

Wrong pl ace in database

The user is most likely at the WORLD element in the database.

Illegal Transfer letter

The user can only use transfer letters between A and Z.

Nothing to export

The user has deselected both the Linear Members and Plates options.

Cannot decrement Transfer The user can not decrease the Transfer letter, only increment it. letter

3.2

Ru n In f o r m at i o n On the Run Information form the user can choose whether to be offered to see the Log File after the Export process is complete. The user can also choose between Brief or Verbose messages. The form is created by clicking the Run information button on the AVEVA Open Steel - Exp or t form

The Test Run ? option allows the user to suppress the updating of all the Export flags. This is so that the user can see if there will be a successful Export of the model. The user may find that the Profile or Material mapping files are not quite up to date which might cause a failure in the Export process. Therefore, the user can select this option to define this as a test run. After the Export process pr ocess has completed, the Test Run? button is reset to false. This is so that the user is forced to state categorically each time the model is Exported that t he run is a trial.

3:8

1.5


Once all the correct data has been entered on the Run Information form, click OK and the interface variables will be updated. Clicking CANCEL will remove the form, leaving the original interface variables unchanged.

3.3

AVEVA Ope OpenS nSte tee el - Expor xp ortt For Form m On the main AVEVA Op enSt eel - Exp or t form the Members list may be used to navigate around the da tabase hierarchy. The user must enter the elements to be exported, but need not select only SCTNs (Linear Members) or only PANEs (Plates). The interface will locate all SCTNs and PANEs PANEs contained in, or implied by, the Export list. If the user adds something to the Export list and has the item on display in a 3D Volume View it will be highlighted by changing its colour. The Export list is managed such that duplicate elements are removed and that items are exported only once. Note: Partial model transfers are supported by the interface, however, the user must be aware of how the Import process handles partial model transfers. Refer to Comparison and Merging Processes .

There are several methods of adding elements to the Export list. Ad d CE just adds the current element to the list. This also implies all items below the current element in the database hiera rchy. rchy. The WORL can not be added a dded to the list.

The Ad d by Pic k option allows the user to select an item from the 3D Volume View. It is similar to other PDMS DESIGN pick functions. Selecting this option brings up a Status form and puts the user into a mode where an item from the 3D Volume View can be picked. The user can also pick a sequence of items in succession to add to the Export list. Click the Esc key when complete. If the user does not want to continue, click the Esc key. Ad d Str uc tu re will attempt to climb to the Structure owning the current element and add that to the Export list. A warning will be displayed if there isn't an owning Structure.

There is also a set of methods by which the user can remove items from the Export list. These optio ns work on ly on entries in the Export list , rather rather than in the model . As with adding to the Export list, removing from the Export list will cause the item or items removed to be returned to the default colour as defined by this interface. Note: This colour may be different from the colour in which it may have originally been added to the Drawlist. Remove CE looks for the name of the current element in the list and removes it if present. Remove Remove by Pick allows the user to select something from the 3D Volume View and, if it is present in the Export list, the name will be removed. As with the Ad d by Pic k option, the user may select a series of items to attempt to remove from the Export list until the Esc key is clicked. Remove Selected is a means by which the item selected in the Export list is subsequently removed. Select the item first in the list, then click the Remove Selected button.

just removes everything from the list. Clear just The user may find that items are shown in the Export list do not exist, or have been renamed. The Export process will determine all the valid entries in the Export list and prepare the data accordingly. Clearing the list, or removing individual items will be performed as expected.

3:9

1.5


Error and L og File Messages Messages

3.3.1

Can't Can't export the WORLD WORLD

the user cannot export the WORLD

No owning Structure

Cannot climb to Structure element from current location in database.

Ex p o r t an d Can c el Cancel removes the AVEVA Open Steel Exp or t form from the screen.

Export executes the Export process. As it proceeds the user is kept informed of the progress.

3.3.2

Th e Ex po po rt rt Fo Fo rm rm Ba B ar Me Men u The Control item on the Export form has just two options; Re-initialise and Exit . Changing any mapping files or any other variables, Re-initialise will reload these files to save the user having to rebuild the whole user interface from scratch. The Exit command will remove all forms and menus and global variables associated with the interface. The General item has one option, Highlight. This will bring up the Highlighter form enabling the user to highlight new, changed and deleted items in the model. This has more relevance to the Import process and is described in more detail in Highlighting Changes in the Design.

3.3.3

Th e Ex p o r t Pr o c es s Exporting from PDMS all items are exported using millimetres as the distance units. All reference data, such as any an y pre-existing reference model, is removed before exporting anything. Refer to Import from SDNF on Importing for details about saving the reference model. Prior to any Export process, all form fields are checked for validity. validity. •

Is the the out outpu putt fil file e nam named ed? ?

•

Are Are we we goi going ng to expo export rt anyth anythin ing? g?

•

Are the the mapping mapping tabl tables es compat compatibl ible e with the the Targe Targett Package Package? ?

•

Have Have we we a vali valid d Ste Steel el Sta Standa ndard rd tab table le? ?

In addition, there is an OpenSteel-specific UDA, :SDNFEXCLUDE, attached to certain PDMS elements by which the user can define whether the item is to be exported or not. Setting this logical flag to true will exclude the item from the Export process. Refer to UDAs. Before continuing, the Export process polls all the Configuration objects for the high water mark on Transfer and Revision numbers. It then updates the object applicable to the current MDB and user to contain the latest Transfer value. The list of all items listed in t he Export list is then stored on Header element After verifying that all the form data is correct and valid, the external program is called. The interface waits for a certain time until the program is finished. This waiting time is user configurable. If there are errors raised by the external program the user is notified and more detailed information is placed in the log file. If the waiting period expires without the interface detecting that the external program has completed - it may have crashed, or even not exist, the user will be asked if to carry on waiting for another time unit.

3:10

1.5


Click YES and the interface will wait for another period of time. Clicking NO will cause the interface to stop where it is. Finally the system will indicate its completion, whether successful or not. This completion message should be read in conjunction with the log file, if any errors are indicated.

The above indicates a successful completion, while the below represents some problem encountered in the external program.

On completion of the external program, the status file is inspected and, if the result is favourable, the user will then be asked whether or not to look at the log file, if that option has been selected on the Run Information form.

3:11

1.5


To inspect the log file later, save it with the File > Save as option in the OpenSteel File window which will bring up a File Browser, or by clicking the Save as button to the Viewer window suggested filename. Either way, if the file already exists, the user will be asked whether to overwrite it. The log file window may then be closed by the Cancel button.

If the Brief mode mode has been chosen on the Run Information form for displaying the log file, the form displaying the log file will filter out all Warning messages, leaving only the Error messages. Saving the log file, however, all messages will be retained in the file. Error and L og File Messages Messages File does not exist

3.3.4

Somehow there is no log file. Are there issues regarding access rights to the %PDMSWK% directory?

Ex po po rt rt in in g L in in ea ear Mem be ber s A series of checks are made before a Linear Member is output. •

Is the SPRE set?

•

Is it a zer zero o len lengt gth h mem membe ber? r?

3:12

1.5


•

Does Does it have have a val valid id mate materi rial al? ?

•

Is the Justific Justification ation Pline Pline mappabl mappable e to a Cardinal Cardinal Point ifif it is not not a Cardinal Cardinal Point Point itself? itself?

•

Are Are the the star startt and and end end poin points ts vali valid? d?

If any of the above criteria is not satisfied, the linear member does not even get exported to the SDNF output file. Note: This will have an effect on the subsequent import process as the member will appear to have been deleted by the external steel detailing package since its export. In fact, the linear member never made the tr ansfer to the Target Package in the first place.

If the Linear Member is connected, the interface will determine the offset each end from its associated node. Once the Linear Member has been output, the relevant UDAs specific for the interface associated with Export are updated. These are the mark numbers, the export date and time and transfer and revision numbers.

3:13

1.5


Error and L og File Messages Messages Illegal or unset SPRE - Not SPRE must be valid. exported Zero Zero l ength Li near Member Member - Length less than user definable tolerance. Not exported No material information - Cannot determine material properties for member. Not exported No material match for nnnn. SDNFMGRADE cannot be matched with a material in the Properties database. - Unknown material No material material property m atch

As above

Inconsistent material specification

The element's MATR and :SDNFMGRADE attributes are not consistent.

Multiply defined entries in Material Table

Either a material to be mapped or a mapped profile appears more than once in the material file.

No match for m aterial

The material is not in the material file

Syntax Error

Other, less specific, errors.

Unrecognised Parse State State

This should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state state will also be output.

No match for Cardinal Point nnnn

Pline or Cardinal Point not recognised. Neutral axis (Cardinal Point 10) assumed.

No Cardinal Cardinal Point nnnn

JUSL unset.

Bad Cardin Cardin al Point nnnn

Cardinal Point/Pline identified is not valid. Does it exist? Neutral axis (Cardinal Point 10) assumed.

Problem exporting entity

Other errors found.

Profile cannot be mapped

The profile is not in the profile mapping file.

Profile is not in th e standard standard The profile is in the profile mapping file but is not in any one of the set of standards.

3.3.5

Profile is not th e default default

The profile is in the profile mapping file and is in one of the set of standards, but not the default standard.

Multiply defined entries in Profile Table

Either a profile to be mapped or a mapped profile appears more than once in the profile mapping file.

Ex p o r t i n g Pl Pl at es Panels in PDMS are to be transferred as Plates using Packet 20. This will cover stiffeners, floor and toe plates . Bent plates will also be transferred if they are expressed as their component flat plates. If Bent Plates are to be treated as Angle linear members then they should be modelled as such. If the PDMS Design Penetration Application is used to generate Catalogue holes, the resultant holes, kicker plates and stiffeners will not be exported because they are contained

3:14

1.5


in a Catalogue definition. Neither are holes or negative primitives transferred from the design. The Description attribute will be used to store the flooring type, such as grating or chequer plate. This is passed as the type field (up to 24 characters). The Material Grade transferred in Packet 20 represents the material type. This is a text attribute, rather than the number field in PDMS. Therefore a User Defined Attribute (UDA), :SDNFMGRADE, has been defined within PDMS to store this information. Note: Any edge preparation details and modelling, such as grinding, will be lost in the transfer operation.

A basic series of tests is performed before the Plate is exported. •

Is ther there e any any geom geomet etry ry? ?

•

Is the the heig height ht vali valid? d?

•

Is it just justif ifie ied d cor corre rect ctly ly? ?

•

Does Does it have have a val valid id mate materi rial al? ?

•

Are Are the there re enou enough gh vert vertic ices es? ?

If any of the above criteria is not satisfied, the plate does not get exported in the SDNF output file. Note: This will have an effect on the subsequent import process as the plate will appear to have been deleted by the external steel detailing package since its export. In fact, the plate never made the transf er to the Target Package in the first place.

Once the Plate has been output, the relevant UDAs specific for the interface associated with Export are updated. These are the mark numbers, the Export date and time and transfer and revision numbers. Note: In Exporting a Plate, it has to be converted to the SDNF standard of being defined in a clockwise direction relative to the plane normal. Thus Importing a Plate previously defined in DESIGN, the user may find the order of vertices to have been reversed. This is because DESIGN is more tolerant about the ways in which the user can define a plate.

3:15

1.5


Error and L og File Messages Messages No geometry information - No PLOO element. Plate cannot be exported. Not exported Plate too th in - Not exported Thickness less than user defined minimum. Plate not exported. Not enough vertic es - Not Not exported

Fewer than 3 vertices. Cannot define valid geometry so Plate is not exported.

No material information - Cannot determine material properties for member. A matching set of :SDNFMGRADE and Matref cannot be Not exported determined. No material material match for nn nn

3.3.6

Unknown material. :SDNFMGRADE cannot be matched with a material in the Properties database.

No material material property m atch

As above

Inconsistent material specification

The element's MATR and :SDNFMGRADE attributes are not consistent.

Multiply defined entries in Material Table

Either a material to be mapped or a mapped profile appears more than once in the material mapping file.

No match for m aterial

The material is not in the material mapping file.

Syntax Error

Other, less specific, errors.

Unrecognised Parse State State

This should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state state will also be output.

Problem exporting entity

Other errors found.

Ex p or or ti ti ng ng Co nn nn ec ec t io io n s End connections and base plates will be modelled in DESIGN Catalogue items and transferred to the SDNF file using end coding information stored in the CTYA attribute of the Catalogue component. A mapping table is required to enable the information to be transferred in order that a corresponding entity to be created in the external 3D steel detailing package. Once the end has been detailed, the resultant geometry may be returned to DESIGN as Plate members in Packet 20 for graphical and clash checks. In PDMS Joint selection is controlled by specification.

3:16

1.5


As it exports Connections (PJOI and SJOI elements) the system initially checks that the SPRE attribute is set. If so, the CTYA of the relevant Catalogue component is checked against the Connection mapping table. If it is valid, the local CTYS or CTYE attribute of the attached SCTN is set for the sake of consistency. As it is doing so, the interface also checks that the connectivity references are consistent. The CTYA attribute is then matched against the required text for output in the SDNF file. The interface also determines the identifier and end of the Linear Member to which the joint is attached.

3:17

1.5


Error and L og File Messages Messages Illegal or u nset SPRE

SPRE must be valid.

No Connection Type - Not Cannot determine CTYA attribute. Joint cannot be exported. exported Inconsistent connectivity - Connectivity not consistent, so the joint cannot be exported. There is probably something more Not exported fundamentally wrong with your model. Problem exporting entity

3.4

Other errors found.

Testin sting g AV AVEVA Ope OpenS nSte tee el Exp Expor ortt The following test can be performed after installing the AVEVA OpenSt Ope nSt eel product to make sure that the installation is complete and correct. All the required testing material can be found below the sub-directory test/export. The test described below creates an SDNF model file output. The supplied databases for the TST project are compatible with AVEVA AVEVA PDMS (Series 12).

3.4.1

In i ti ti al al Co nf nf ig ig ur ur at at io io n Enter DESIGN. Set the test project variables: Project: TST User Name/Password: SYSTEM/XXXXXX SYSTEM/XXXXXX MDB: DEMO Enter the DESIGN module, if necessary by answering YES to the question "Leave Session Manager and enter 3D Design Constructor? " When the default set of windows, menus, bar menus and forms appears configure the screen as follows: Select Design Design > Structu res > Beams Beams & Colum ns from the General General Applicatio n menu This displays the Beams & Columns Application menu. To display the Drawlist , right-click on the Drawlist button pop-up menu.

and select Drawlist from the

Select Utilities > Beams & Columns Choose the SITE to export to SDNF by selecting SITE /TEST-SDNF-INTERFACE from the Drawlist form. On this form click Ad d CE to add it to the Drawlist, answering YES to the question " Are Are you sure you want to add a site? " When that is finished, bring the SITE into view by adjusting the view limits in the 3D Volume View window. Change the view in that window by selecting View View > Isometric > Iso 3. The user can add the border sliders to the view window using the View > Settings > Borders menu option.

3:18

1.5


3.4.2

Pr epar in in g to to Ex Ex p o r t On the User Beams Beams & Colum ns Utiliti es form select Expor t>(d) AVEVA AVEVA Op enSteel which will bring up the main AVEVA OpenSteel OpenSteel Export form. On this form and associated forms, fill in the details prior to Export. Target Information Form

Click the Target Target inform ation button on the AVEVA Open Steel - Expo Ex po rt form to display the Export Target Target Inform ation form. Select the Au to mode toggle option and select "PDMS" from the list of Target Packages on the Target Package selector gadget on the right hand side of the form. This causes the system to automatically detect the Target Package's Profile mapping table and Material mapping table. When the details are correct click OK . Export Information Form

Click the Export information button on the AVEVA Open Steel - Exp or t form to display the Export Information form. In the outp ut file name field enter "SDNF-Test.sdn" "SDNF-Test.sdn" Check that the SDNF file header (Packet 00) is coming from /SDNF-CONFIG-DEMOSYSTEM. Use the navigator and browser if necessary. Select which SDNF Packets to export: Packet 10 (Linear Members) , Linear Members + End Connections and Packet 20 (Plates) . When the details are correct click OK .

3:19

1.5


Run Information Form

Click the Run information button on the AVEVA Open Steel - Exp or t form to display the Run Information form. Select the Log File? option and choose Verbose for the message mode. Do not select the Test Run? option as this is not a test run. When the details are correct click OK . The Main Main Expo rt Form

To add the SITE to be exported to SDNF, Select SITE /TEST-SDNF-INTERFACE in the form's Members list. Click Ad d CE . This will cause all the members in the 3D Volume View window change colour to indicate they are being exported. The AVEVA Open Steel - Exp or t forms look similar to this.

3:20

1.5


3:21

1.5


3.4.3

Cr ea eat io io n of of Ex Ex p or or t Fi le le On the AVEVA Open Steel - Expo Ex po rt form, click the Export button. The status line displays the progress of the task. When the process is complete, the user will be asked whether to inspect the log file. The user can then save it with the File > Save as option on the OpenSteel File Viewer window window to bring up a File Browser, or by clicking the Save as button to the suggested filename. The log file window may then be closed by the Cancel button.

3.4.4

Check heckin ing g the the SDNF Outpu utputt Fil File e Compare the SDNF-Test.sdn file produced with the one supplied in the test/results/export directory.

3:22

1.5

OpenSteel OpenSteel User Gui de Import from SDNF

4

Im p o r t f r o m SDNF This section explains how to import a steel structure from an SDNF file. It gives guidance about what options are available, for more detailed information refer to Technical Information and the appendices. The user can display the main AVEVA Open Steel - Imp or t form by one of two ways: On the DESIGN General Application menu bar, select Utilities > General from the drop down menu, or, if the user is in the Steelwork Application select Utilities > Steelwork . The User General Utilities menu bar is displayed.

The user can also find the SDNF entry in the Beams & Columns Application , with the Beams & Columns option under the Utilities menu. On the User General Utilities menu bar select Import>(d) AVEVA OpenSteel to display the AVEVA Open Steel - Imp or t form.

4:1

1.5


4.1

S o u r c e In f o r m a t i o n The Source Information form contains information about the 3D steel detailing package from which the SDNF file is to be transferred. Click the Source information button on the AVEVA Open Steel - Imp or t form to display the Import Source Information form.

The interface requires two external mapping tables for each Source Package to check that the design can accept the data. It also may use the Profile Orientation mapping table if necessary. The mapping tables are for the Steel Profiles, Materials and for mapping the Profile orientations between DESIGN and the Neutral File. The section on user customisation in the Installation Guide explains how the user can arrange these files on the file system and what format they are to be. The interface also needs to know where the external mapping files are located on your computer network. For this internal mapping tables are required. Refer to the Installation Guide which explains how the user can configure the interface to let it know where all the files are located. The user can have a generic pair of mapping tables to map between PDMS and SDNF for a particular steel fabricator, for example. Or the user can have a similar pair for each 3D steel detailing package. The current file settings are indicated on this form. The user will notice that changing the Source Package by using the Source Package selector button on the right hand side of the form may cause the text to change giving the full path names of the respective files. Note: Do not be concerned that the path name may be truncated by the insertion of the ellipsis (…): it is modified only for display purposes on the form.

The system also checks that these files are compatible with the Source Package by checking the identification line at the top of each mapping table. Refer to the AVEVA AVEVA OpenSteel Installation Guide for details about the format of these mapping files. There are two main options on this form: Au to and Manual . These can be activated by selecting the appropriate toggle button on the left hand side of the form. The Au to option causes the interface to select automatically the Profile and Material mapping tables for the Source Package indicated by the Source Package selector gadget on the right hand side of the form, according to the system configuration files. When the user comes to execute the Import process, the Au to flag will cause the correct mapping files

4:2

1.5


to be used based on the Issue field in the Input file header. Refer to Technical Information for details about the format of the header of an SDNF file. The Manual option activates two other buttons, which are greyed out for the Au to option. Selecting this option changes the form to be similar to below.

The user can select the file type using the Profiles/Materials/Orient'n toggle buttons above the text data entry field and enter the full path name of the file in the data entry area. The user can also include system environment variables in the path name as long as they are in the proper PDMS format, e.g. %ENVVAR% %ENVVAR% being the PDMS representation of the ENVVAR environment variable. On clicking carriage return, the interface will check for existence of the file and compatibility with the Source Package indicated by the Package option gadget. Note: The check is only that the file applies to the Source Package and not that it is a correct file type.

The user can either choose by hand which mapping file to use by entering its name in the text data entry field, or by using the Browse option to bring up a File Browser. Use this browser to search for the relevant mapping file. Once all the correct data has been en tered on the Source Information form, click OK and it will update the interface variables. Clicking CANCEL will remove the form, leaving the original interface variables unchanged.

4:3

1.5


Error and L og File Messages Messages Internal error

Internal lists are not in step.

Cannot find suitable internal internal mapping list

Internal mapping files not found.

Suitable Mapping Table File Mapping table found is not for the correct Source Package, or it does not exist. not found

4.2

Not a suitable Mapping Table Fil e

Incorrect format of file, or empty file, or wrong Source Package.

Bad Map File

Mapping file is not correct format. Possibly it is from another operating system.

Error o n OpenSteel OpenSteel File Browser form

The user has entered incorrect data on the file browser form.

Im p o r t In In f o r m at i o n The Import Information Information form contains information about the actual Import process. Click the Import information button on the AVEVA Open Steel - Imp or t form to display the Import Information form.

The user either type the full directory path name of the input file, or use the Browse button to bring up a File Browser. The use of this form is as described in the section above. The interface tests to see if the file exists and if it does not the user will be warned. As well as testing for the existence of the file, it is also tested for being a valid SDNF file by inspection of its header details.

4:4

1.5


Note: If the user does not enter the full path name, the input file will be assumed to be in the directory from which started PDMS. The user can also include system environment variables in the path name as long as they are in the proper AVEVA PDMS format, e.g. %ENVVAR% being the PDMS representation of the ENVVAR environment variable.

In addition to the basic check for the input file being in SDNF format, the initial comments are scanned for the presence of a data table, which may list the Packets to follow and the number of items to be transferred in each one. If this table is present, it will be analysed and the buttons determining which Packets may be Imported will be activated or inactivated accordingly. This table is described in Technical Information. On entering the name of the file, if it is from a recognised SDNF Source Package and if Au to mode is set on the Source Information form, the Profile and Material mapping files will be selected automatically and indicated in the Source Information form, if it is currently shown, along with the updated Source Package selector gadget. The user can view the SDNF Header (Packet 00) of the chosen input file by clicking the Inspect button. This displays the Input File Header Details form with which the user can determine whether the file is the correct one to Import.

Using the toggles on the Import Information Information form, if they are active, the user can select whether to import Packet 10 (Linear Members) and/or Packet 20 (Plates) . Note: The user cannot import Packet 40 (Connection Details) with this version of the interface. The interface will check that the user is attempting to Import something if both options are unchecked!

4:5

1.5


Once all the correct data has been entered on the Import Information form, click OK and the interface variables will be updates. Clicking CANCEL will remove the form, leaving the original interface variables unchanged. Error and L og File Messages Messages

4.3

Import file does not exist

File specified does not exist.

Not an SDNF File

File specified is not an SDNF file. This may also arise if the file the user is inspecting has been transferred across hardware platforms.

Nothing to import

The user deselected both the Linear Members and Plates options.

Cannot Cannot auto detect Source Package

If the AUTO option is on, the header of the Input file does not contain the Source Package information. The mapping table information has to be set by hand.

Ru n In f o r m at i o n On the Run Information form the user can choose whether to be offered to see the Log File after the Import process is complete. The user can also choose whether to display Brief or or Verbose messages. Click the Run information button on the AVEVA Op enSt eel - Im po rt form to display the Import Information Information form.

4:6

1.5


As part of the Import process a reference model is construct ed against which comparisons will be made. The Save Referenc Referenc e Model button allows the user to keep this. Otherwise it will be deleted on completion of the Import process. Note: This reference model will be deleted next time the user Exports or Imports anything and that it is only transient data. Also, it may not be a complete model as some items may already have been transferred into the main model on merging.

After the Import merging process has been performed, the user can sort all new items into FRMW (Framework) elements according to their Material type. This option is selected by clicking the Sort on Material Type option. During the Import process, comparisons are made for Linear Members and Plates between the existing model data and the imported model data. The d efault AVEV AVEVAOpenSteel system configuration compares all the relevant data entries transferred in the SDNF file between the models. However, the user can select which attributes may be ignored by the comparison process by clicking the Edit Attribute Comparison List button.

4:7

1.5


Using this form the user can deselect attributes for comparison but must be aware that strange results may occur especially if the user ignores positional and rotational attributes. Finally, there are two validity checks the user can perform on the incoming data which to ensure a subsequent Import run will have a chance of success. Activating these options overrides completely the Import choices made on the main form. With these validity checks the user will be able to see a log file before any data is merged whatsoever. The Profile Mapping Mapping ? button enables the user to see if the incoming Linear Member Profile specifications will be successfully mapped between systems. This is a relatively fast transaction as the SDNF file is just passed through the external program without any subsequent import or comparison in PDMS. the user will then be able to see the log file produced and take appropriate action. There is a risk in the external detailing package that entity mark numbers may be duplicated. The Duplicate Mark numbers selector gadget enables the user to check for duplicate numbers in the incoming model. There are three options: NONE, NEW and GLOBAL . NONE deactivates the gadget and no checks are made. The import process just goes through unhindered. The NEW option allows the user to check only the new imported items for duplicate mark numbers, while the GLOBAL option enables the user to search all the available DESIGN databases for duplicate numbers. Obviously these searches may involve a certain amount of time, but for the sake of validity, they would be worth using.

4:8

1.5


Once all the correct data has been entered on the Run Information form, click OK and the interface variables will be updated. Clicking CANCEL will remove the form, leaving the original interface variables unchanged

4.4

Op en St eel - Im p o r t Fo Fo r m On the AVEVA OpenSt Op enSt eel - Im po rt form the Members list can be used to navigate around the database hierarchy. The user must state where the Imported model is to be located. This must be a SITE, ZONE or STRU element . Using the Members list, navigate round the database to the correct storage location and click the Store in: CE button. The form text indicates where the Imported model will reside. If there is not enough space on the form, the SITE's reference number is output rather than its name. The Import process is essentially a three phase operation. First a reference model is built which is then compared with the original model identified during the Store in: CE operation. Then, if required, the changes, additions and deletions encountered in the comparison phase are transferred to the actual model. Thus, using the Operations toggles, the user can control how the Import process is to proceed. Note: These options may be completely overridden if the user wants to perform a validity check as on the Run Information form.

The user should be aware of how the model manages partial model transfers and where temporarily imported data goes before it is merged into the pre-existing model. See the sections describing the Import, Comparison and Merging processes. Compare ( + Merge ) will import the model and compare the reference model with the location chosen to be the storage ar ea. At this point the user will be a sked whether to merge the models. Clicking YES will continue with the merge process and complete the Import. Compare + Merge just goes through the complete Import process - i.e. the import, comparison and merging are all completed without any interaction with the user. This is only to be performed if the user is absolutely sure that they will get the desired result. Merge Merge from File takes a merge command file produced during t he current DESIGN session only and imports it directly into the model. The reference model must not have been deleted beforehand. Otherwise, the user may lose any elements added to the model by the external detailing package.

This is a very quick option and there are no checks, except what the user wants to do it. Error and L og File Messages Messages Bad element element typ e

4.5

The user is not trying to store imported data at a SITE, ZONE or STRU element.

Im p o r t an d Can c el The Control item on the Import form has just one option, Exit , which will remove all forms and menus and global variables associated with the interface. Cancel removes the AVEVA Open Steel Imp or t form from the screen.

4:9

1.5


Import executes the Import process. As it proceeds the user is kept informed of the progress.

4.6

Im p o r t Fo r m B ar Men u The Control item on the Import form has just two options; Re-initialise and Exit . If the user changes any mapping files or any other variables, Re-initialise will reload these files to save the user having to rebuild the whole User Interface from scratch. The Exit command will remove all forms and menus and global variables associated with the interface. The General item has one option, Highlight. This will bring up the Highlighter form enabling the user to highlight new, changed and deleted items in the model.

4.7

Im p o r t Pr o c es s After clicking OK the fields in the form are checked for validity: •

Is the the sto stora rage ge loc locat atio ion n vali valid? d?

•

Is ther there e a vali valid d inp input ut file file? ?

•

Do we we need need to to conve convert rt the the file file across across plat platform forms? s?

•

Are the Profile Profile and Materia Materiall mapping mapping files files valid valid for the Source Source Package Package as identified identified in the Header of the input file?

After verifying that all the form data is correct and valid, the external program is called. The interface waits for a certain time until the program is finished. This waiting time is user configurable. If there are errors raised by the external program the user is notified and more detailed information is placed in the log file. If the waiting period expires without the interface detecting that the external program has completed - it may have crashed, or not exist, the user will be asked if they want to carry on waiting for another time unit.

Click YES and the interface will wait for another period of time. Clicking NO will cause the interface to stop where it is. Finally the system will indicate its completion, whether successful or not. This completion message should be read in conjunction with the log file, if any errors are indicated. The user will be alerted to unsuccessful runs by the external program by the following form after which the process exits.

4:10

1.5


If the external program successfully completes, the processed SDNF file will be imported into DESIGN. Any reference data which may have been retained by the user before will have been deleted beforehand. The status line will inform the user of the progress on importing the data. As a rough guide, the length of the input macro is about 25 times the number of elements. Thus a file transferring 300 members will be about 7500 lines long. After the Import of everything, the material properties are reconciled with the :SDNFMGRADE attribute and, if possible, the MATR is also set to point to the appropriate property in the Properties database. At this point, if the user has chosen to be asked whether to Merge after the Compare operation, the prompt form below is shown.

Clicking YES will cause the interface to continue with the Merge process. Click NO and the Import process will skip the Merging, but the user will then be given a chance to store the Merging commands in a file for use later on only in th e current AVEVA AVEVA PDMS session . The user cannot use a file from a previous OpenSteel session as the Import data may be incorrect.

4:11

1.5


The user can save the Merge command file and then be prompted whether to see the Import log file. This Merge command file may then be used in the Merge from File option on the AVEVA Open Steel - Imp or t form. This later option needs the reference model from this run to be kept. Therefore, the user does not have the option below. If the user has Merged the models, they will then be asked if they want to keep the reference model, verifying the option selected on the Run Information form.

Finally, the user will then be asked whether to look at the log file, if they have chosen that option on the Run Information form.

If the user wants to inspect the log file, they can then save it with the File > Save as option in the OpenSteel File Viewer window which will bring up a File Browser, or by clicking the Save as button to the suggested filename. If the file exists, the user will be asked whether they want to overwrite it. The log file window can then be closed by the Cancel button.

4:12

1.5


If the user has chosen Brief mode on the Run Information form for displaying the log file, the form displaying the log file will filter out all Warning messages, leaving only the Error messages. To To save the log file, however, all messages will be retained in the file. Clicking on a line containing an PDMS reference number will cause all graphical views to zoom in to the chosen item and to highlight it. The interface will also navigate to the item in the database and leave the user there to perform any queries or operations. Error and L og File Messages Messages

4.8

File does not exist

Somehow there is no log file Are there issues regarding access rights to the %PDMSWK% directory?

Input file name not specified

Something strange here. The name of the Design macro generated has been forgotten.

Import file does not exist

Something strange here. The DESIGN PDMS macro file has not been generated or it has been deleted, or is not found in the expected directory. Are there issues regarding access rights to the %PDMSWK% directory?

Data store unset

The data store variable is unset or the SITE the user had intended to store the imported data in is invalid. Has it been deleted since the user set the store variable?

Comp omp ariso rison n and and Mergin rg ing g Pro Proce cess sse es The Import, Comparison and Merge process involves three stages. First, the model is imported. The user then has the option of comparing the imported model with the original model, after which they may merge the new data into the old model, or the comparison and merge process can be performed as one with no user interaction. Though the user can tell the system to Import, Compare and Merge the model straight away this should only be

4:13

1.5


performed if the user is sure of the end result. It is advised that the user Compares the models first and inspect the r esults before Merging. The user can decide to keep the imported reference model as has been described above but is warned that this is only to be regarded as transitory information. It may also not be a complete representation of the data imported as some of it will get transferred to the real design area.

4.8.1

Th e Co mp mpar is is on on Pr Pr oc oc es es s There are three conditions the AVEVA OpenSteel looks for: •

items items in in the importe imported d file file that that are not not in the the origi original nal model model - Ad ded items;

•

items items in the the origi original nal mode modell that that are not not in the the importe imported d file -Deleted items;

•

items that it can match match between between the the imported imported file file and the the original original model model and and checks checks for modifications - Changed items.

The fact that an item is in the imported file and not in the original model is indicative of one of two cases: that the item has indeed been added by the external steel detailing package; or that the item was never exported in the first place for some reason. This latter case might also occur if the original model has had items added to it since the export happened. Further, items may appear to have been deleted and their likes imported when the import store location is not the same as it was for the export process. Below is a diagram illustrating the route through which the data is imported, compared and merged. New items are green, changed items are orange and deleted items are red.

It is clear from the above diagram that the interface supports partial model transfer as it just highlights those new or changed items. Anything indicated as deleted is more an indication that the item is not present in the Imported SDNF file. It is not deleted from the Original Model during the Merge process: "Deleted" items are simply moved to another SITE to

4:14

1.5


enable the user to recover them if necessary. So parts of models can be merged into the original model with no loss of data. Note: The Reference Model which is created is named according to the user session, so that several user Reference Models could coexist at the same time. As they are named according to session, the user is advised to take care to manage them and not to leave too many versions around to fill up your disk space.

The Comparison process allows any potential changes, additions and deletions to the original model to be detected and highlighted in a 3D Volume View window, if there is one present and if the items are in the current Drawlist. As for both Linear Members and Plates the user can select which attributes are significant for Comparison. This is performed using the Comparison Checklist form which is a child of the Import Run Information form. By default, all the attributes transferred through the SDNF file are compared. Comparing Li near Members Members

The following data attributes are compared between the original model and the reference model: •

Start tart and end of Plin Pline e defin defined ed by by Cardin Cardinal al Poin Pointt

•

Orie Orient ntat atio ion n and and Beta Beta angl angle e

•

Speci pecifi fica cati tion on Refe Refere renc nce e

•

Start art and and End rele releas ases es

•

Mate Materi rial al gra grade de and and ref refer eren ence ce

•

Hold Hold and and Pai Paint nt Spec pec UDA UDAs s

Importing a Linear Member also sets the Import date and time UDAs. On merging members the revision number, transfer number and code are updated. The log file messages recording any differences are of two formats: in Brief mode the results are presented on one line; in Verbose mode the user is told what the old value was and the new value is so that they can see how the model has been changed. Refer to Brief Format for details about the brief log file format. The user may get a lot of apparent changes which may be caused by the failure to map the profile types between systems. The log file will indicate which profiles have not been mapped. It is advised that the user resolves the Profile Mapping issues first before becoming too concerned with other changes recorded in the log file. During the Import phase, an attempt is made to map the SDNF Cardinal Points (SNFA to SNFN) in the incoming model with existing Plines that have been mapped onto them. Refer to the Installation Guide . Comparin g Plates (PANE) (PANE)

The following data attributes are compared between the original model and the reference model: •

Posi Positi tion on,, orien orienttatio ation n

•

Mate Materi rial al gra grade de and and ref refer eren ence ce

•

Hold Hold and and Pai Paint nt Spec pec UDA UDAs s

•

Pane Panell loop loop heigh heightt and and just justif ific icat atio ion n

•

Number of of ve vertic tices

4:15

1.5


Vertex positions compared to within the user definable tolerance as described in the section on user customisation of the interface. Importing a Plate also sets the Import date and time UDAs. On merging members the revision number, transfer number and code are updated. The log file messages recording any differences are of two formats: in Brief mode the results are presented on one line; in Verbose mode the user is told what the old value was and the new value is so that they can see how the model has been changed. Refer to Brief Format for details about the brief log file format. Note: In Exporting a Plate, it has to be converted to the SDNF standard of being defined in a clockwise direction relative to the plane normal. Thus Importing a Plate previously defined in DESIGN the user may find the order of vertices to have been reversed. This is because DESIGN is more tolerant about the ways in which the user can define a plate.

4.8.2

Th e Mer gi gi ng ng Pr oc o c es s See the diagram in Section 4.8 illustrating the route by which information is transferred from the Import, through the Comparison and on to the Merging processes. The AVEVA Open Steel interface manages the Comparison and Merging of imported models so that other important engineering data is not lost or overwritten. However, other data, including connectivity may be lost. The user can separate the Comparison and Merging processes, so that they are able to view the log file in between operations. If the user chooses the Merge from File option on the main OpenSteel Import form, the Comparison process is deemed to have been completed and so all that remains to be done is the actual Merging. This is why the reference model for the current sess ion must still be available. The user will be prompted for confirmation.

If, during the Merge phase, items are to be merged, then the lists of added and deleted items are reconciled with the original model - by being deleted or transferred from reference model. The storage SITE header details are then merged with the information in the SDNF header (Packet 00). After the main model Merging has been completed, if the user has chosen the Sort on Material Type option on the Import form, any new items will be sorted into FRMW groups according to their material type as specified by the :SDNFMGRADE attribute. The version numbering system is described below, in Technical Information .

4:16

1.5


Ad di ti on al It ems

Items added to the model are recorded as such; they are highlighted by changing their colour, a suitable message is output to the log file and they are then transferred to a special area. Merging will transfer all the added items from the reference model to the original model. If required, they are then sorted according to material type. The new items are gathered together into a site whose name is constructed from the Transfer and Revision Numbers so that the user can easily locate all items added at a specific version or date.

SDNF- NEW- DEMO- SYSTEM SYST EM/ For example, a new STRU may be created with the name of / SDN A. 1 under the container element as specified in the Store in: field on the OpenSteel Import form. The components of this name are as follows: / SDN SDNF-

the system prefix

NEW NEW-

identification of new element container

-

the current MDB, e.g. /DEMO

- /

the current user name, e.g. SYSTEM

.

the current Transfer letter, e.g. 'A'

the current revision number, e.g. '1'

The user would thus be able to find all the added items to this MDB at this version.

4.8.3

Del et ed It em s Deleted items in the model are recorded as deleted during the Compare phase and remain in the reference model to be deleted later if not required. This separation of operations is so that the user can see what will be deleted during the Merge process. Before deletion the objects are changed in colour so that they may be highlighted. may, in Note: An item is not actually deleted from the original model. The apparent deletion may, fact, be because the item was never transferred to the external detailing package in the first place due to some reason. Alternatively it may have been created in DESIGN since the initial Export process had taken place. 'Deleted' items are disconnected from the old model and transferred from the current part of the database into a STRU created under the special 'Deleted' SITE as described in Refer to the AVEVA OpenSteel Installation Guide. As with the added items, the STRU is named out of components, thereby enabling t he user to determine at which version items may have been removed from the model. For example, a new STRU may be created with the name of / SDN SDNF- OL D- DEMO- SYSTEM SYST EM/ A. 1 under the special SI TE / SDN SDNF- OLDLD- DEMO- SYSTEM. The components of this name are as follows:

/ SDN SDNF-

the system prefix

OL D-

identification of new element container

-

the current MDB, e.g. /DEMO

- /

the current user name, e.g. SYSTEM

.

the current Transfer letter, e.g. 'A'

the current revision number, e.g. '1'

4:17

1.5


The user would thus be able to find all the 'deleted' items to this MDB at this version. Changed Items

In merging Plates the interface tries to keep the original vertices as they may have been used for locating dimensions on drawings: it may be that just the positions have been changed. However, the comparison only works in list order: the interface does not look around for another vertex in the same physical place, although it may be in a different list position. Extra unwanted vertices are deleted on merging and all new vertices are added to the end of the list. A totally new Plate is just imported directly. Changed objects are highlighted as such by a change in colour. Error and Warnin Warnin g Messages

4.9

WARNING: Reference SITE nnnn contains transient transient data

The reference SITE is likely to be deleted some time.

Model comparison completed

Process was successful.

Failed Failed to c ompare models

Do they both exist?

Val i d at i o n Pr Pr o c e s s As has been described in Section 4.8 there are two validation checks the user can perform prior to the full import and merging of models. The first option is for profile mapping. The Profile Mapping? Option on the Run Information form turns this on. The Import process initialises normally and calls the external program to process the incoming SDNF file. In so doing it checks for a complete mapping of the profiles in the mapping tables. A log file is produced. No further Import actions are undertaken with this option. Second, the user can check that there are not any duplicate external mark numbers. This can quite easily come about if the user copies members in the external detailing package without creating unique mark numbers for them. When they are imported into PDMS, the Comparison process may fail as it could be uncertain as to which member it is supposed to be comparing. The options for this check are NEW and GLOBAL . NONE turns the facility off. NEW checks among all this run's imported members contained in the reference model for duplicate mark numbers, while GLOBAL checks the whole structural database, both imported and existing elements. These can be quite slow options as the reference model must be created and compared anyway. anyway. As this option also calls the external program which checks the mapping of profile names between systems, the user will see that the log file may also list any problems with the mapping tables. So this option is actually a combination of this and the previously mentioned validity checking option. See Appendix: Sample Validity Check Log File for a sample log file.

4:18

1.5


4.10

Highlig ighlighti hting ng Cha Change nges s in the the Design sign The user can display an OpenSteel Highlighter form from either the Import or Export forms by the General General > Highlig ht menu bar option. This form allows the user to highlight in a graphical window whatever they want, either according to Import date, or by Transfer/ Revision number combinations. The Select Select b y toggle switches the form into the appropriate mode. Both these options work from the start element selected and will highlight only those items that are in the drawlist.

4.10.1

Highlig ighlightin hting g by Import mport Date The form below allows the user to choose what to highlight on the screen according to the Import Date of an item.

In the Selected items box, the user can select any combination of Added, Changed, or Deleted Items for highlighting, according to the date range described below. By selecting the inclusive dates defining the limits of the range using the From and To date selector gadgets the user can highlight on the screen those items in the current drawlist which have been changed, added or deleted.

4:19

1.5


Note: As the 'deleted' elements are relocated in the database after Merging, the area where they are finally located should also be in the drawlist if the user wants to see what has been 'deleted'.

4.10.2

Highl ighlig ight htin ing g by Ve Versio rsion n The form below allows the user to choose what to highlight on the screen according to the Version of an item.

The rules of selecting the changed, deleted or added items are the same as for the previous section, Highlighting by Import Date. By selecting the versions defining the limits of the range using the From and To version selector gadgets the user can highlight on the screen those items in the current drawlist which have been changed, added or deleted. Note: As the 'deleted' elements are relocated in the database after Merging, the area where they are finally located should also be in the drawlist if the user wants to see what has been 'deleted'.

4:20

1.5


Error and Warnin Warnin g Messages

4.11

Bad date inpu t

The configuration of day, month and year is illegal. Or is the start date after the end date?

Bad version input

Is the start version after the end version?

Nothing to highlight

Nothing satisfies the selection criteria.

Testin sting g AVEVA OpenSteel OpenSteel - Impor t The following test can be performed after installing the AVEVA OpenSteel product to make sure that the installation is complete and correct. This test must follow immediately the Export test described in Testing AVEVA OpenSteel Export. The user will find all the required testing material below the sub-directory test/import . The test described below imports an SDNF model file. The supplied databases for the TST project are compatible with PDMS12.

4.11.1

Initia nitiall Con Confi figu gura rati tion on Enter DESIGN. Set the test project variables: Project: TST User Name/Password: SYSTEM/XXXXXX SYSTEM/XXXXXX MDB: DEMO Enter the DESIGN module, if necessary by answering YES to the question "Leave Session Manager and enter 3D Design Constructor? " When the default set of windows, menus, bar menus and forms appears configure the screen as follows: Select Design Design > Structu res > Beams Beams & Colum ns from the General General Application bar menu This displays the PDMS DESIGN - Beams & Columns Application bar menu. To display the Drawlist , right-click on the Drawlist button pop-up menu.

and select Drawlist from the

Select Utilities > Beams & Columns Choose the SITE to export to SDNF by selecting SITE /TEST-SDNF-INTERFACE from the Drawlist form. On this form click Ad d CE to add it to the Drawlist, answering YES to the question " Are Are you sure you want to add a site? " When that is finished, bring the SITE into view by adjusting the view limits in the 3D Volume View window. Change the view in that window by selecting View View > Isometric > Iso 3. The user can add the border sliders to the view window using the View > Settings > Borders menu option.

4:21

1.5


4.11.2

Prep reparing ring to to Imp Impor ortt On the User Steelwork Utilities form select Import>(d) AVEV AVEVA A OpenSteel to display AVEVA Open Steel - Imp or t form. On this form and associated forms, the user now need to fill in the details prior to Import. Source Information Form

Click the Source information button on the AVEVA Open Steel - Imp or t form to display the Source Information form. Select the Au to mode toggle option and select "PDMS" from the list of Source Packages on the Source Package selector gadget on the right hand side of the form. This causes the system to automatically detect the Source Package's Profile mapping table and Material mapping table. When the details are correct click OK . Import Information Form

Clicking the Import information button on the AVEVA Op enSt eel - Im po rt form to display the Import Information form. In the input file name field ent er "%TSTIMP%/SDNF-Test.sdn" "%TSTIMP%/SDNF-Test.sdn" Select which SDNF Packets to import: Packet 10 (Linear Members) and Packet 20 (Plates). When the details are correct click OK . Run Information Form

Clicking the Run information button on the AVEVA Open Steel - Imp or t form to display the Run Information form.

4:22

1.5


Select the Log File? option and choose Verbose for the message mode to get a verbose log file. Select the Save Reference Reference Mod el? option in order to safe any reference model. Finally, we will sort any new members added to the model by material type. Select the Sort on Material type? option. If the user wants to perform a validity check on the incoming data prior to importing it, refer to Performing a Validity Check . When the details are correct click OK . The Main Main Impor t Form

Select the SITE into which the SDNF file is to be imported. Select SITE /TEST-SDNFINTERFACE INTERFACE in the form's Members list and click the CE button by Store in: . We will then want to perform a two stage import, Comparing the models first before Merging. So, select the Compare (+ Merge) radio button. The AVEVA Open Steel - Imp or t forms should now look similar to this.

4:23

1.5


Note: In the above form the environment variable %TSTIMP% has been automatically replaced by its expanded value.

4:24

1.5


4.11.3

Importin mporting g the the SDNF File On the AVEVA Open Steel - Imp or t form, click the OK button. The status line will then keep the user informed of the progress of the task. After the first stage of Import has take place, the user will be asked by a Prompt form with the following message. "OpenSteel (Confirm) - Model comparison completed. OK to merge models?". Click the YES button to continue with the Merge process. When the process is complete the user will see the following message:

The user will then be asked if they want to inspect the log file. If they do, they can save it with the File > Save as option in the OpenSteel File Viewer window to bring up a File Browser, or by clicking the Save as button to the suggested filename. The log file window may be closed by the Cancel button.

4:25

1.5


4.11.4

Compa omparing the Importe Imported d Mode Modell with the Original riginal The supplied test project also contains an original reference model /ORIG-TEST-SDNFINTERFACE which can be used to visually compare the imported model with the original. The user can do this by adding the original model to the Drawlist in a different colour so that it will be superimposed on the modified model. The user can then inspect the 3D Volume View closely for the differences recorded in the log file. The user can then Export the merged model to a file SDNF-Test-Mrg.sdn and compare the new SDNF file with the one provided in the test/results/import directory.

4.11.5

Performin rforming g a Va Validity lidity Che Check ck If the user wants to perform a validity check on the incoming data before they a ctually import it bring up the Run Information form from the main Import form. Select GLOBAL for the Duplicate Mark Number search criterion. Click OK on that form and fill in all the details on the main form as described above. Once all the details are correct on the Import form, click OK. The validation process will be performed and in due course the user will be prompted to view the log file. Save the log file as SDNF-Test-Vfy.log and compare it with the results supplied in the test/results/import directory.

4:26

1.5

OpenSteel OpenSteel User Gui de Bolt Reports

5

B o l t Rep o r t s This section explains how to extract reports of Anchor Bolts from the model using the Bolt Report templates supplied with the interface. This is useful for comparing Import and Export models, locating anchor bolts and purchasing. The report templates are to be found in the directory reports/templates under the main directory which is created on installation of the interface. Modelling of anchor bolts will be by Linear Members, i.e. SCTN elements, in the correct location. Therefore, the anchor bolt report templates assume that: •

the Catalo Catalogue gue compone component nt name name defining defining an anchor anchor bolt bolt profile contains contains a -AB -' AB ' suffix;

•

the star startt (POSS (POSS)) of the the SCTN SCTN is is the lower lower end end of the the SCTN. SCTN.

To change these assumptions, refer to the Reporting Reference Manual on how to modify the report templates. To select and run the report the user must choose the Utilities>Reports>Run option from the Application Menu Bar. This brings up a File Browser which the user can use to navigate to the correct directory and select the correct report template. This will then go and create the report. The user will be prompted to enter the top of the member hierarchy under which the search for anchor bolts is to take place and will also be prompted for the output file.

The values proposed are the default ones which the user can override.

5.1

A n c h o r B o l t L o c at i o n s The user can produce a report of all anchor bolt locations using the report template SDNFBoltLocRep.tmp which creates a file which is called by default SDNFBoltLocation.rep in the current directory, i.e. the directory from which the user initiated PDMS. Below is a part of an anchor bolt location report:

5:1

1.5


AVEVA OPEN PENSTEEL STEEL ANCH ANCHO OR BOL T L OCATI ON REPORT REPORT ============================================================ Dat e of Repor epor t : 2 J un 2008 2008 Ti me of Repor epor t : 15 15: 21 Sel ecti on f r om: / * ============================================================ Bol t t ype ype

Ref No

/ M20- AB / M20- AB / M20- AB / M20- AB / M20- AB / M20- AB / M20- AB / M20- AB / M20- AB / M20- AB / M20- AB / M20- AB / M20- AB / M20- AB / M20- AB / M20- AB / M24- AB / M24- AB

=15322/ 225 =15322/ 1517 =15322/ 226 =15322/ 1518 =15322/ 223 =15322/ 1515 =15322/ 221 =15322/ 1513 =15322/ 211 =15322/ 1503 =15322/ 212 =15322/ 1504 =15322/ 224 =15322/ 1516 =15322/ 222 =15322/ 1514 =15322/ 185 =15322/ 1477

/ M24- AB

=15322/ 187

East i ng ( mm) 151200 151200 151200 151200 155150 155150 155150 155150 155200 155200 155200 155200 155250 155250 155250 155250 123900 123900

123900

Nor t hi ng ( mm) 147940 147940 147940 148060 148060 148060 147925 147925 147925 148075 148075 148075 153925 153925 153925 154075 154075 154075 147925 147925 147925 148075 148075 148075 157000 157000 157000

163000

Base l evel vel ( mm) 100170 100170 100170 100170 100170 100170 100170 100170 100170 100170 100170 100170 100170 100170 100170 100170 100170 100170

100170

The report is sorted according to bolt type and then according to the East, North, Up values of the position of the start of the bolt in the world coordinate system.

5.2

A n c h o r B o l t Qu an t i t i es The user can count the number of each bolt type using the SDNFBoltLisRep.tmp report template. This produces a file which is called by default SDNFBoltListing.rep in the current directory, i.e. the directory from which the user initiated PDMS. Below is a report of bolt quantities in the test model.

AVEVA AVEVA OPENSTEEL ANCH ANCHO OR BOL T L I STI NG REPORT REPORT ================================================================ Dat e of Repor epor t : 2 J un 2008 008 Ti me of Repor epor t : 15 15: 17 Sel ecti on f r om: / * ================================================================

5:2

1.5


Bol t Typ Type / M20- AB / M24- AB / M30- AB unset unset

Quant i t y 16 56 8 2

5:3

1.5


5:4

1.5

OpenSteel OpenSteel User Gui de Technical Information

6

Tec h n i c al In In f o r m at i o n This section contains technical information which is not immediately specific to PDMS but of which the user should be aware in order to get the best out of the interface.

6.1

SDNF - Structura tructurall Ste Stee el De Detailing Ne Neutral utral File File Format ormat This section describes the format of the SDNF file. It appears that all of the related Packets must be output at the same time. We cannot export a set of Linear Members and some time later another set. Comments may be inserted anywhere through the file. They are indicated by the '#' symbol as the first character. Lines, apart from the Packet identifications, are free formatted delimited by blanks, up to a maximum length of 132 characters. Text or character, chara cter, values are enclosed in double quotation marks, '"'.

6.1.1

Export/ xport/IImport mport diffe differe rent nt SDNF forma formats ts The interface can read and write SDNF files to both version 2 and version 3 of the format. The format is described later this section. On the Export Information form there is a drop down list which the user can use to select which SDNF version to output.

6:1

1.5


6.1.2

Auto Auto--dete detect ctio ion n of SDNF form forma ats The system can automatically detect which version of the file the user is inputting and set the import drop down list accord ingly. ingly. The user should need to do no more. The user can set up the default SDNF format version in the SDNFUserData.pmlfnc file in the pml/functions directory. This is the !!SDNFSDNFVersion variable which must be precisely one of the 2 suggested text strings.

- - Def aul t SDNF f i l e f or mat - - c ur r ent l y | 2. 0| or | 3. 0| ! ! SDNFSDNFVer FVer si on

= | 3. 0|

6:2

1.5


The user can inspect the file header as before and an added line will show which SDNF version it has found.

If the user changes the version setting, the s ystem will not work because it is expecting a file of a radically different format. However, the interface will fail in a controlled manner producing a "catch-all" error message such as…

6:3

1.5


[Error] - Fatal processing error in external program.

If the user manually selects the wrong SDNF version, they may also get an error message in the log file about syntax errors in the incoming file. This is because the Packet 0 records are different.

6.1.3

Pac ke ket 00 00 - Ti tl tl e Pac ke ket This Packet is the SDNF file header. Only 1 Packet of this type must be included. It describes the run for the t he data transfer. Its record structure is as follows: Rec or d Rec or d Rec or d Rec or d Rec or d Rec or d Rec or d Rec or d Rec or d

1 2 3 4 5 6 7 8 9

Pac ket header Engg Fi r m I d Cl i ent I d St r uc t ur e I d Pr oj ec t I d Dat e/ Ti me Rev #, I s s ue Code Des i gn gn Code Nr of Load Recor ds

6:4

Fi xe xed C80 C80 C80 C80 C30, C3 C30 I , C64 16 C80 I

“ Pac ket 00” “ ABB” “ XYZ” “ Bui l di ng 1” “ Pr oj ect XYZ” “ 14/ 11/ 97” “ 09: 30” “ St r uC uCad” Des i gn gn Code name” 1

1.5


Rec or d 10 L oad #, Type, Des c

I , I , C64

1 1 “ L i ve and Wi nd”

r epea epeatt Record 10 10 as st at ed i n Record 9

Note: The Issue Code (Record 7) holds the Source Package of the SDNF file.

6.1.4

Pack cke et 10 10 - Line Linea ar Me Membe mbers Linear Members are the elements represented in DESIGN by SCTNs - straight prismatic profiles. They are described in the SDNF file as follows:

There are several ways of defining a Linear Member using different combinations of the above data elements, some of which will not be interpretable by other systems. The method of interpretation of these fields is defined below.

6.1.5

Loca Locatio tion n of of Line Linea ar Me Membe mbers in in Sp Space Close and rigorous study of the definition of Linear Members in SDNF will reveal that there are many ways in which a Linear Member may be located in space. Combinations of information stored in records 5 to 7 per Linear Member will determine its location. The main

6:5

1.5


requirement is that the Cardinal Point is to be used to draw the lines in schematic drawings such that, where possible, a connected model may be deduced. More generally, the interpretation is as follows: Record 6 is ignored completely - (2D offsets) The Start and End cutbacks (Record 5) are ignored by default, but see section 6.5 Using Linear Member Cutbacks for how to enable them. The Start and End Position of the Member (Record 5) is the start and end position of the 'real length of steel' located on the line described by the Cardinal Point (Record 3). The 3D Start and End Eccentricities (Record 7) then define the real start and end of the Cardinal Point 'Line' relative to the Node, if any. Thus, using Record 7 with Record 5, the Node position could be determined. AVEVA OpenSteel would export this value, but could not do much with it on import at the moment. Note: The sense of this eccentricity is a vector from the end of the member to the node position.

All packages are assumed to export the start and end positions of the Linear Member's Cardinal Point Line. Rotation Rotation and Orientation Vector

The Rotation and Orientation Vector attributes of a Linear Member determine the orientation of the element about its axis. The Orientation Vector defines the default orientation of the member before any rotation has been applied to it. The Rotation is then taken as a right handed rotation about the axis from that default vector as one looks along the member from start to end - the local Z axis. Packet 20 - Plates

Plates are represented in PDMS by PANE PANE elements as loops on the upper and lower faces. No enclosed holes are transferable u sing SDNF. SDNF.

Below are the rules of interpretation of these fields.

6:6

1.5


Order of Vertices

When exporting, the vertices describing a Plate are assumed to be defined in a manner according to the "Right Hand Screw Rule", where the vertices are in a clockwise order when viewed along the normal to the Plate plane. When importing, the vertices may be defined in either direction. Plate Origin

The Plate Origin is taken to be the position of the first vertex. Plate Orientation

The vector from the first vertex to the next vertex is taken as the local X axis. Knowing the fact that the plate is defined in a Right Hand Screw Rule manner, the plane normal can be determined. This will determine the local Z axis. The Y axis then becomes the vector cross product of the Z and X axes. Ignored Plate types

OpenSteel can partially cope with new plate types. Plate type 0 is treated, as in previous versions, with straight edges. Plate type 1 is partially handled by placing the vertices, but ignoring the corner radius (connection number). This is because we would have to generate more vertices on the loop for import into PDMS. Plate type 2 (circular plates) are ignored.

6.1.6

Pac ke ket 30 30 - Me Mem be ber L oa oad in in g Loading of elements is not transferred by this interface.

No loads along the member are catered for.

6.1.7

Pack cke et 40 40 - Conne onnect ctio ion n De Details ils The Connection Details attached to one or each end of a Linear Member are described here. In DESIGN terms they are modelled by Primary or Secondary Joints. The mechanism by which the description text in record 3 is obtained is detailed above. The record structure is as follows:

6:7

1.5


This is only a textual description. No geometry is passed here, especially concerning sniping etc.

6.1.8

Pac ke ket 50 50 - Gr id id Pa Pac ke ket Grid Packets are not transferred in this interface.

6.2

Recomm comme ende nded SD SDNF File ile Suffi uffix x Although it is not critical for this interface, the recommended suffix for the SDNF files is to be '.sdn'.

6.3

SDNF File ile Header der Inf Infor orma mati tion on As has been described in the Installation Guide , all the internal maps are exported in the SDNF file as comments for information purposes only. Appendix B gives an example file. Note: All these tables represented in the form:

# # # # # #

STARTTABLE nnnn dat a dat a ENDT ENDTABLE ABL E

with STARTTABLE and ENDTABLE as the keywords. However, a special PACKET table is to be included in the header which indicates how many objects of each Packet are contained in the following SDNF file. In this way, any system importing the file will be able to give some progress feedback as it will know how many items are expected without having to read the whole file at the beginning. An example is…

# # STARTTABLE PACKET # 10 39

6:8

1.5


# 20 1 # 40 0 # ENDT ENDTABLE ABL E # This example is indicating that there are 39 Linear Members in Packet 10, 1 Plate in Packet 20 and no Connection Details in Packet 40. This interface uses this table to modify the behaviour of the Import forms.

6.4

Membe mber ID ID Numbe umbers rs at SD SDNFv3 The SDNFv3 specification describes the member ID as consisting of 2 components in the format xxxyyyyy: 'xxx' represents the model number and 'yyyyy' represents the member id number. It appears that not every system will output member identification marks according to this format. The interface takes this into account, decomposing the id number, if possible and storing them in the right data slots. Exporting to SDNFv3 will produce id numbers to the required format. For Export, the model number that is output in the SDNF file is retrieved from the header object and can be set using the modified dialogs illustrated below.

6:9

1.5


On Import the components of a member ID number are stored in the NUMB attribute.

6.5

Us i ng ng Li L i n ea ear Me Mem be ber Cu Cu tb tb ac ac k s The interface can handle cutbacks as entered in Record 5 of Packet 10 of the SDNF file Refer to Packet 10 - Linear Members . The start and end 3D eccentricities in Record 7 are ignored as in previous releases. The default setting is not to use cutbacks for compatibility with previous versions of OpenSteel. If the user wants to change the default setting, this is set in the sdnfUserData.pmlfnc file in the directory pml/functions .

- - Fl ag t o hand andl e a supp suppl i ed t r i mmed model odel wher e cut backs must be us us ed

or one one

- - | CP| = t r i mmed posi t i ons; - - | WP| = wor ke ked d out out posi t i ons ons ! ! SDNFModel Type

= | CP|

The interpretation of the SDNF record data for Linear Members and their cutbacks is illustrated below. Here is an SDNF description of a Linear Member. Member.

1 10 0 0 " ANG" " 1532 15322/ 2/ 826" 826" 0 " L60 L60x6" x6" " St eel , car bon" on" 180. 0000 0 0 - 287. 287. 3480 3480 0. 0000 0000 957. 957. 8260 8260 1381 138100 00.. 0000 0000 1660 166000 00.. 0000 0000 … 1060 106000 00.. 0000 0000 14079 140796. 6. 5000 5000 16600 166000. 0. 0000 0000 10680 106808. 8. 9530 9530 10. 0000 0000 30. 30. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 20. 20. 0000 0000 0. 0000 0000 10. 10. 0000 0000 - 50. 50. 0000 0000 0 0 0 0 0 0 0 0 0 0 0 0 In the above data the fields are interpreted as shown:

Or i ent at i on vect vect or = ( - 287, 0, 958 )

6:10

1.5


St ar t posi t i on = ( 138100, 166000, 106000 ) End End posi posi t i on = ( 1407 140796 96,, 1660 166000 00,, 1068 106809 09 ) St ar t cut back = 10 End cut back = 30 St ar t ecce ccent r i ci t y = ( 0, 0, 20 ) End eccen ccent r i ci t y = ( 0, 10, - 50 )

6:11

1.5


Diagram showing each interpretation. The text below describes this diagram in more detail.

6.5.1

Ex p o r t i n g The use of the Use Cutbacks option will be the same for exporting a PDMS model in either SDNF format, i.e. v2.0 or v3.0. When the Use Cutbacks checkbox is left unchecked the start and end positions entered in Record 5 will be the start and end positions of the Justification Pline of the member. Where the member is connected, i.e. the Joistart and/or Joiend attributes are set, the start and/or end cutback value will be set to be the absolute length of the vector between the node position and the Justification Pline position as projected along the member's axis. In effect, this calculates a virtual node. For simple, orthogonal structures which have not been manipulated too much, this will tend to be at the same position as the attached node. Where the member is unconnected, i.e. either the Joistart and/or Joiend attributes are unset, the start and/or end cutback value will be set to zero.

6:12

1.5


When the Use Cutbacks checkbox is checked the start and end positions entered in Record 5 will be the positions of the virtual nodes derived from the nodes to which the start/ end is connected. The start and end cutbacks will be set to be the distance between the virtual node position and the Justification Pline position. If either or both member ends are unconnected the start and/or end position in Record 5 will be start and/or end position of the Justification Pline and the cutbacks will be zero.

6:13

1.5


Below is the relevant Export dialog with the Use Cutbacks option indicated.

6:14

1.5


6.5.2

Im p o r t i n g The use of the Use Cutbacks option will be the same for importing a model in either SDNF format, i.e. v2.0 or v3.0. When the Use Cutbacks checkbox is left unchecked the start and end positions of the member will be set to the start and end positions given in Record 5. Any cutback values in Record 5 will be ignored.

6:15

1.5


When the Use Cutbacks checkbox is checked the Start and End positions of the member will be 'trimmed' in accordance with the start an d end cutback values in Record 5.

6:16

1.5


Below is the relevant Import dialog with the Use Cutbacks option indicated.

6:17

1.5


6.6

Car d i n al Po Po i n ts Below is a diagram illustrating the positions of the Intergraph FrameWorks Cardinal Points. FrameWorks cannot handle Cardinal Points above Point 10, but for this interface it is imperative that all interfaces in th is project are able to handle all 14 illustrated below. This is because, especially for unequal angle profiles, the first 10 Cardinal Points are not sufficient. On transfer between systems, the Cardinal Point imported should be retained for later export. This is because it is likely to be a source of confusion when a member originally laid out on Cardinal Point 14 (Top of Steel) is returned on the Cardinal Point 10 (Neutral Axis). Additionally, Additionally, it will cause minor problems in model versioning and comparisons.

6:18

1.5


6.7

Def au l t Or Or i en tat i o n s There is a definition of the default orientation of profile shapes associated with the SDNF Specification produced by the Intergraph FrameWorks User Group. This is closely based on the AISC standard. It is proposed that each software package will translate to this format on export and from this format on import. This would then provide a standard interpretation of the mirroring flags associated with Linear Members (Record 4). The main issue here concerns angle profiles on import to Design. Below is a diagram showing the FrameWorks default orientations of the Catalogue profiles.

Note: The FrameWorks coordinate system defining the Profiles is left-handed. The difference between this and the coordinate system used in PDMS is illustrated by the diagram below.

6:19

1.5


6.7.1

Mi r r o r i n g Although the FrameWorks documentation mentions mirroring about both the X and Y axes, it can only handle mirroring about the Y axis. The results of mirroring about the Y axis are shown below. Note: This also mirrors the Cardinal Points about the Y axis as well.

This interface does not handle mirroring about the X axis either. However, However, any desired result can be achieved just by rotations and mirroring about the Y axis.

6:20

1.5


6.8

Pl i n e Sel ec t i o n Ru l es The user can define which Plines are identifiable or selectable using the supplied DESIGN Appware. Saving the rules generates a file in the default directory. directory. This is later automatically automatically picked up on re-entry into DESIGN. Then, these rules become applicable to various operations in the standard Steelwork Appware. From the DESIGN - Steelwork Application bar menu select Setting Setting s>Pline Rules This will bring up a form listing the currently available rules for filtering Plines. This will be similar to the picture below.

6:21

1.5


Clicking the Define Rules button will bring up a form on which the user can create their own. Above is the form filled in for the supplied AVEVA OpenSteel Pline filter rule. The operation of the form is fairly self explanatory. The supplied Pline rule filter file, called des-pline-rules.pmldat, is listed below. Should the user want to use it, copy it from the pml directory to your log in directory as identified by the %PDMSUSER% environment variable and it will be accessible to the user the next time they enter PDMS.

#- - Dat a f i l e c on ont ai ni ng pl i ne r ul e def i ni t i ons ! r ul ! r ul ! r ul ! r ul ! r ul

e e. name e. r ul e e. t ypes e. descr i pt i on

= = = = =

obj obj ect ect RULE( LE( ) | OpenS enSt eel Pl i nes| | ( mat ch( ch( ( at t r i b PKEY ) , ' SNF' ) gt 0) | || | OpenSt eel Pl i nes wi wi t h PK PKEY = SNF[ A- N] . |

! ! t mpRul eAr r ay. append( ! r ul e)

6:22

1.5


6.8.1

Us e o f Pl Pl i n e Fi l te ter s The default drawing flags for the Plines have been changed to LEVEL 99 99, CLFLAG TRUE and TUFLAG TRUE. In the AVEVA AVEVA PDMS P DMS DESIGN Steelwork Application The user can choose which Pline filters to use using the following method. From the main Bar Menu select Settings>Pline Rules which brings up the Pline Rule filter box. Select which rule set the user wants to use by highlighting it. Click OK . This rule set then becomes available for use when using Appware functionality only. Note: Direct querying, such as "q idpl @" does not access this rule set.

6.9

UDA s This section lists the UDAs defined for this interface. We have attempted to keep the unique abbreviation to 6 characters. The UDAs for this interface are:

6.9.1

6.9.2

Gen er al Da Dat a

Nam e

Ty p e

L en

On

Des c r i p t i o n

:SDNFED/ATE

TEXT

20

SCTN PANE

Date of Export

:SDNFET/IME

TEXT

20

SCTN PANE

Time of Export

:SDNFID/ATE

TEXT

30

SCTN PANE

Date of Import

:SDNFIT/IME

TEXT

30

SCTN PANE

Time of Import

:SDNFRE/VNO

INT

1

SCTN PANE SITE

Revision Nr (0)

:SDNFTRA/NO

INT

1

SCTN PANE SITE

Transfer index(1)

:SDNFTRR/VNO

TEXT

10

SCTN PANE SITE

Revision Text

:SDNFEX/CLUDE

L OG

1

SCTN PANE SJOI PJOI

Exclude flag (f)

:SDNFSTA/TUS

TEXT

10

SCTN PANE

Status text

Nam e

Ty p e

L en

On

Des c r i p t i o n

:SDNFHO/LD

INT

1

SCTN PANE

Hold Status (0)

:SDNFPS/PEC

INT

1

SCTN PANE

Paint Spec (0)

:SDNFMG/RADE

TEXT

24

SCTN PANE FRMW

Material Grade

St r u c t u r al Da Dat a

6:23

1.5


6.9.3

Nam e

Ty p e

L en

On

Des c r i p t i o n

:SDNFMA/RK

TEXT

24

SCTN PANE

Object Mark Nr.

:SDNFEMA/RK

TEXT

24

SCTN PANE

External Mark

Nam e

Ty p e

L en

On

Des c r i p t i o n /d ef au l t

:SDNFEF/ID

TEXT

80

SITE ZONE STRU

'Engineering Firm Id'

:SDNFCL/ID

TEXT

80

SITE ZONE STRU

'Client Id'

:SDNFSTI/D

TEXT

80

SITE ZONE STRU

'Structure Id'

:SDNFPR/ID

TEXT

80

SITE ZONE STRU

'Project Id'

:SDNFDE/CODE

TEXT

80

SITE ZONE STRU

'Design Code'

:SDNFSO/URCE

TEXT

64

SITE ZONE STRU

Data Source

:SDNFTA/RGET

TEXT

64

SITE ZONE STRU

Target Contractor

:SDNFEL/IST

REF

100

SITE ZONE STRU

Export Item List

:SDNFED/ATE

TEXT

20

SITE ZONE STRU

Date of Export

:SDNFET/IME

TEXT

20

SITE ZONE STRU

Time of Export

:SDNFID/ATE

TEXT

30

SITE ZONE STRU

Date of Import

:SDNFIT/IME

TEXT

30

SITE ZONE STRU

Time of Import

Pr o j ec t Data

:SDNFEXCLUDE is a flag the user can set on the items indicated. It is using this flag that the user can control what is exported to the SDNF output file. By default the flag is false, i.e. the item is not excluded from the Export process. :SDNFEMARK is the reference number by which the external 3D steel detailing system identifies the item. If the item originated in AVEVA Design then this value will be the PDMS reference number with the leading equals sign, '=', removed. :SDNFMARK is the DESIGN reference number. It may n ot be the same as :SDNFEMARK if the entity originated in the external system. :SDNFSTATUS is used to give the user a view of the current status of the element. It has 4 different settings: PDMS to signify the item originated in DESIGN; ADDED indicates that the item has been added to the model externally, by Merging; CHANGED means that the item has been modified externally; and DELETED means that the item was in the original DESIGN model but has not returned from the external model. This last case may occur for one of several reasons. The item may not have been exported in the first place; it may have been added after the model was exported or it was deleted by the external system for some reason. On Export, the :SDNFELIST attribute on the Header element is amended to contain a list of all elements exported. This is the list that appears in the Export List window on the main AVEVA AVEVA OpenSteel Export form. It is not the final expanded list of SCTN and PANE elements to appear in the SDNF output file.

6:24

1.5


6.10

Cross ross Refere ferenci ncing ng Models odels This is the mechanism by which we may be able to identify members in different models other than by visual comparison. There are two scenarios: one where an element is created in DESIGN; the other is where it was created in any other system, but is to be imported into DESIGN. The Id field in the SDNF file is not a reliable identifier as it tends to be only a sequential item count produced on the generation of the SDNF file.

6.10.1

Eleme lement nt cre created ted in DESIGN When an element is created in DESIGN it gains a unique internal reference number of the form "=/", e.g. =13/2305. On export from Design t his value, excluding the initial '=' character , will be passed through in Packet 10 or 20 in the Mark fields. These are text strings on Records 3 and 3a respectively. Any system importing this file should be able to take this value and store it, or use it to allow the user of the detailing system to identify the DESIGN member in the external steel detailing package. On Export back to PDMS, for any member which has this Mark attribute set, the original imported Mark value will appear again in the SDNF file. Thus a user of DESIGN will be able to spot any changes to the model. The AVEV AVEVA A OpenSteel Import system, then allows the user to modify the existing structure, rather than just replacing it with a copy. In this way, any drawings for example, which may have been produced between Export from and Import back to DESIGN, will retain their logical relationships to the steel members.

6.10.2

Eleme lement nt crea created ted outside outside DE DESIGN A member created outside DESIGN will not have the Mark field set to be a PDMS internal reference number. The AVEVA OpenSteel interface would therefore know that it was importing a new element and would create it accordingly, whilst recording the external Mark number as well.

6.11

Versio rsion n Num Numbe beri ring ng The management of the attributes relevant to version numbering and revision control, i.e. :SDNFREVNO, :SDNFTRANO and :SDNFTRRVNO, is all performed in the PDMS user interface. The values of these attributes are not taken from the SDNF file. The header, Packet 00, is used to transfer the main TransferLetter for the Configuration object, but the individual items are managed as described below. The Configuration object should not be confused with the Header object. The former is used to store transfer indices - counts of Transfer Numbers and Revision numbers. These are for the whole database. The latter is used to store specific information pertaining to the transfer in question - e.g. Source or Target Target package or client information. Because of the fact that PDMS may be multi-user and that several users may be concurrently accessing the design databases at any one time, there may be several Configuration objects, one for each possible MDB:User combination. At the start of the Export or Import process, a poll is taken of ALL these Configuration objects to determine which is the highwater mark. That is, which is the highest Transfer Number, or Revision Number. We then take that and modify the Configuration object fo r the current MDB:User. In this way, by polling all objects, we can determine the latest values. The rules of precedence for the Transfer and RevisIon numbers are that a Transfer is higher. So that "A.2" is later than "A.1" and "B.1" is later than "A.9".

6:25

1.5


Note: The UDA, :SDNFTRANO, is actually an index into a character string returning the equivalent character as the TransferLetter. Note: This TransferLetter is cycled. As it passes 'Z' it will be succeeded by 'A'.

If there are more than 26 Transfers, the letter is recycled so that there may be slight problems at the wrap around. Below are the rules by which the revision numbering is handled by the interface. 1. Each Each Tran Transfe sferr has a Letter Letter - A...Z A...Z 2. Each Each Revisi Revision on has has a Number Number - 1,2,3. 1,2,3... .. 3. Each SITE, SITE, SCTN SCTN and and PANE PANE has has 3 UDAs UDAs attached attached 4. A Trans Transfer ferLet Letter ter e.g. e.g. 'C', 'C', 5. A Revi Revisio sionNu nNumbe mberr e.g. e.g. '2' '2' 6. A TraRevNum TraRevNumber ber - A character-wise character-wise concatena concatenation tion of the previous previous two, e.g. e.g. 'C.2'

6.11.1

On Tra Transf nsfe er from from De Design: sign: 1. Increment Increment the element's element's Transfe TransferLetter rLetter at the SITE SITE level, level, eg 'A' to 'B'. 'B'. 2. Reset the SITE's SITE's Revision RevisionNumbe Numberr to '0' and generate generate the new TraRevN TraRevNumber umber -> 'B.0'. 'B.0'. 3. If an entity (SCTN (SCTN or PANE) PANE) has not not been transferred transferred from from PDMS before, before, its its own TransferLetter is set to be the owning SITE's TransferLetter. TransferLetter. This is only done once.

6.11.2

On Tra Transf nsfe er into into De Design: sign: 1. If an entity (SCTN (SCTN or PANE) PANE) has been been changed or is new new, set its Transfer TransferLetter Letter to be that of the owning SITE and note that there is at least 1 changed item. 2. Update the entity's entity's (SCTN (SCTN or PANE) PANE) RevisionN RevisionNumber umber to be the incremente incremented d value of that of the owning SITE, because we haven't yet changed the latter. 3. Increment Increment the SITE's SITE's RevisionNum RevisionNumber ber,, e.g. '0' to '1' if any imported imported entities entities have changed.

6.12

Ex c l u s i o n s This section lists the exclusions which have been identified because the interface is using SDNF as the means of data transfer. Note: The exclusions listed here are mainly a result of the format of the SDNF file used. A later SDNF format addresses several of these issues. Penetration Penetration Holes: SDNF does not allow the description of holes within Linear Members or Plates. Ad di ti on al d ata: SDNF is a poor transfer format as the user has few means by which extra information can be transferred between systems. Nodal Model: Connectivity is difficult to reconstruct once lost. SDNF does not transfer the information. Curved Members/Curved Plates: This version of the SDNF format does not contain the description for them. Curved members may be exported in SDNF using Packet 10 as a series of straight segments. Templates: Templates and Catalogues are not covered by SDNF.

6:26

1.5


Non-prismatic end details: SDNF Packet 10 cannot describe any details at member/cleat ends apart from full orthogonal cuts. Hence, all sloped cuts, notches, etc. will be approximated from minimum to maximum local longitudinal co-ordinate, which should be conservative regarding clash detection. SDNF Packet 20 can describe only fully prismatic Plates. Hence, the Plate cuts/intersections which are not fully orthogonal to the Plate's local plane cannot be mapped to SDNF. Such Plates will be exported 'uncut', which again should be conservative for clash detection.

6.13

I s s u es SDNF allows only for the transfer of a character descriptor for a Profile or Connection Detail. For a successful data transfer, there will need to be co-ordination between users of each package to ensure that the geometric description associated with the catalogue name is identical and that there is a means of correlation between the packages. In DESIGN, the structural model may contain two views of the data: one view defined by logical connectivity by references to the connecting items; and the physical view defined by the relative location of items. So, while we may logically relate two items, they may not necessarily be physically close to each other. In external 3D steel detailing packages the means of determining connectivity may be by proximity. Thus, transferring the PDMS model will necessarily involve the loss of real connectivity information which will be difficult to reconstitute correctly on Import. The interface will output a warning message when packets are met which cannot be handled or are unexpected.

6:27

1.5


6:28

1.5

OpenSteel OpenSteel User Gui de Document Revision History

7

Do c u m en t Rev i s i o n Hi s t o r y

Is s u e Nr.

Is s u e Dat e

Co n t en ts / A m en d m en ts

1

1st January 1999

First re release of PD PDMS OPEN STEEL DE DETAIL EXCHANGE 1.1.1

2

28th Fe February 19 1999

Profile Orientation Mapping Tables added (v1.1.2)

3

27th July 2000

Major Upgrade to PDMS11.3 (v1.2.1) Product renamed PDMS OpenSteel

4

30th November 2003

Upgrade interface and documentation to VANTAGE Plant Design OpenSteel 1.3/ VANTAGE PDMS 11.5.SP1

5

2nd June 2008

Upgrade to v.1.5 Product renamed to AVEVA OpenSteel Merged with OSDE-Bulletin1.4.doc

7:1

1.5

OpenSteel OpenSteel User Gui de Document Revision History

7:2

1.5

OpenSteel OpenSteel User Gui de Appendix: Sample SDNF SDNF File

A

A p p end en d i x : Samp Sam p l e SDNF File Fil e This appendix gives a brief extract of an SDNF file produced by the AVEVA OpenSteel interface.

# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #

Tar Tar get Cont ont r act or : Tar Tar get Cont ont r act or STARTTABLE PACKET 10 281 20 6 40 65 ENDT ENDTABLE ABL E

STARTTABLE ANYANYCON Def aul aul t Conn onnect i on BP macr o BasePl at e TP TP EP EP EPF EPF MCT MCT MCB MCB MCTB CTB MCTB CTB MCL MCL MCR MCR MCLR CL R MC SWA SWA SWB SWB SWC SWC SWD SWD SWE SWE SWF SWF SWG SWG FWA FWA FWB FWB

A: 1

1.5


# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #

FWC FWC FWD FWD FWE FWE FWF FWF FWG FWG FPWB FPWB FPWC FPWC ACD ACD ACD ACD SHE SHE RECT RECT ENDT ENDTABLE ABL E

STARTTABLE ANYMAT STRUC STRUCAD %SDN SDNFMAI N%/ maps/ aps / St r uCad/ uCad/ St r uCadM uCadMat . map XSTEEL %SDN SDNFMAI N%/ maps/ aps / XSt eel / XSt eel Mat . map STEELCAD STEELCAD %SDN SDNFMAI N%/ maps/ aps / St eel Cad/ St eel CadMat . map PDMS %SDN SDNFMAI N%/ maps aps / PDMS/ PDMSMat . map FRAMEWORKS %SDN SDNFMAI N%/ maps aps / Fr ameWor ks / Fr ameWor ks Mat . map ENDT ENDTABLE ABL E

STARTTABLE ANYPRF STRUC STRUCAD %SDN SDNFMAI N%/ maps/ aps / St r uCad/ uCad/ St r uCad. uCad. map XSTEEL %SDN SDNFMAI N%/ maps/ aps / XSt eel / XSt eel . map STEELCAD STEELCAD %SDN SDNFMAI N%/ maps/ aps / St eel Cad/ St eel Cad. map PDMS %SDNFMAI N%/ maps / PDMS/ PDMS. map FRAMEWORKS %SDN SDNFMAI N%/ maps aps / Fr ameWor ks / Fr ameWor ks . map ENDT ENDTABLE ABL E

STARTTABLE ANYORI STRU STRUCAD %SDN SDNFMAI N%/ maps/ aps / St r uCad/ uCad/ St r uCadO uCadOrr i . map XSTEEL STEEL %SDNFMAI N%/ maps/ XSt eel / XSt eel Or i . map STEELCA STEELCAD D %SDNFMAI N%/ maps/ St eel Cad/ St eel CadOr i . map PDMS %SDN SDNFMAI N%/ maps aps / PDMS/ PDMSOr SOr i . map FRAMEWORKS %SDN SDNFMAI N%/ maps aps / Fr ameWor ks / Fr ameWks Or i . map ENDT ENDTABLE ABL E

STARTTABLE ANYSTD EUR EUR Eur onor m BRI Br i t i sh

A: 2

1.5


# AME Amer i c an # GER Ger man # CAN CAN Canadi an # J AP J apan apanese ese # DI N Eur opean # ENDT ENDTABLE ABL E # # # STARTTABLE STATUS # 0 Undef ndef i ned # 1 Fi xed # 2 Pr ovi si on # 3 Ot her # ENDT ENDTABLE ABL E # # # STARTTABLE CLASS # 0 Undef ndef i ned # ENDT ENDTABLE ABL E # # Packet Packet 00 "En "Engi neer i ng Fi r m I d" " Cl Cl i ent I d" "St "St r uctur ctur e I d" " Pr Pr oj ec t I d" " 30 Nov 2003 2003"" " 09: 09: 58" 58" 3 " PDM PDMS" " Desi gn Cod Code" e" 0 Packet Packet 10 " MM" 281 1 8 0 0 " BEAM EAM" " 15322/ 15322/ 100" 100" 0 " HE300A" " St ee eell , car bon" on" 0. 0000 0 0 0. 0000 0000 0. 0. 0000 0000 100 1000. 0. 0000 0000 112 11200 000. 0. 0000 0000 159 15982 822. 2. 3900 3900 115 11500 000. 0. 0000 0000 1120 112000 00.. 0000 0000 160 16017 177. 7. 6090 6090 115 11500 000. 0. 0000 0000 0. 0. 0000 0000 0. 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0 0 0 0 0 0 0 0 0 0 0 0 2 10 0 0 "SC " SCTN TN"" " 1532 15322/ 2/ 1003 1003"" 0 " HANDRAI L" " St ee eell , car bon" on" 0. 0000 0 0 0. 0000 0000 0. 0. 0000 0000 100 1000. 0. 0000 0000 137 13705 050. 0. 0000 0000 179 17940 400. 0. 0000 0000 105 10527 275. 5. 0000 0000 1370 137050 50.. 0000 0000 182 18210 100. 0. 0000 0000 105 10527 275. 5. 0000 0000 0. 0. 0000 0000 0. 0. 0000 0000

A: 3

1.5


0. 0000 0000 0. 0000 0000 - 100. 100. 0000 0000 100. 100. 0000 0000 100. 100. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0 0 0 0 0 0 0 0 0 0 0 0 3 10 0 0 "SC " SCTN TN"" " 1532 15322/ 2/ 1008 1008"" 0 " HANDRAI L" " St ee eell , car bon" on" 0. 0000 0 0 0. 0000 0000 0. 0. 0000 0000 100 1000. 0. 0000 0000 134 13435 350. 0. 0000 0000 181 18115 150. 0. 0000 0000 105 10527 275. 5. 0000 0000 1343 134350 50.. 0000 0000 181 18182 825. 5. 0000 0000 105 10527 275. 5. 0000 0000 0. 0. 0000 0000 0. 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0 0 0 0 0 0 0 0 0 0 0 0 4 10 0 0 "SC " SCTN TN"" " 1532 15322/ 2/ 1009 1009"" 0 " HANDRAI L" " St ee eell , car bon" on" 0. 0000 0 0 0. 0000 0000 0. 0. 0000 0000 100 1000. 0. 0000 0000 134 13435 350. 0. 0000 0000 179 17940 400. 0. 0000 0000 105 10527 275. 5. 0000 0000 1343 134350 50.. 0000 0000 180 18035 350. 0. 0000 0000 105 10527 275. 5. 0000 0000 0. 0. 0000 0000 0. 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0 0 0 0 0 0 0 0 0 0 0 0 5 10 0 0 "SC " SCTN TN"" " 1532 15322/ 2/ 1012 1012"" 0 " HANDRAI L" " St ee eell , car bon" on" 0. 0000 0 0 0. 0000 0000 0. 0. 0000 0000 100 1000. 0. 0000 0000 137 13705 050. 0. 0000 0000 179 17940 400. 0. 0000 0000 105 10527 275. 5. 0000 0000 1361 136100 00.. 0000 0000 179 17940 400. 0. 0000 0000 105 10527 275. 5. 0000 0000 0. 0. 0000 0000 0. 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 - 1650 1650.. 0000 0000 100. 100. 0000 0000 100. 100. 0000 0000 0 0 0 0 0 0 0 0 0 0 0 0 … mor e Li near near Member s … 282 1 0 0 "A " ANG" " 15322/ 15322/ 998" 998" 0 " L80 L80x8" x8" " St eel , car car bon" on" 180. 0000 0 0 0. 0000 0000 - 684. 684. 3460 3460 729. 729. 1570 1570 1482 148200 00.. 0000 0000 1601 160105 05.. 0000 0000 1003 100368 68.. 4370 4370 1482 148200 00.. 0000 0000 165 16599 993. 3. 4370 4370 105 10589 895. 5. 0000 0000 0. 0. 0000 0000 0. 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 - 105. 105. 0000 0000 - 105. 105. 0000 0000 0. 0000 0000 6. 5625 5625 6. 5625 5625 0 0 0 0 0 0 0 0 0 0 0 0 283 10 0 0 " BEAM EAM" " 15322/ 15322/ 999" 999" 0 " HE220A" " St ee eell , car bon" on" 0. 0000 0 0 0. 0000 0000 707 707.. 1070 1070 707 707.. 1070 1070 148 14820 200. 0. 0000 0000 165 16589 895. 5. 0000 0000 107 10710 105. 5. 0000 0000 1482 148200 00.. 0000 0000 160 16010 105. 5. 0000 0000 112 11289 895. 5. 0000 0000 0. 0. 0000 0000 0. 0. 0000 0000 0. 0000 0000 0. 0000 0000 0. 0000 0000 105. 105. 0000 0000 105. 105. 0000 0000 0. 0000 0000 - 105. 105. 0000 0000 - 105. 105. 0000 0000 0 0 0 0 0 0 0 0 0 0 0 0 Packet Packet 20 " MM" " MM" 6 284 284 - 1 0 0 " PAN PANE"

A: 4

1.5


" 15322/ 1015" " St eel , car bon" on" 25. 0000 6 137050 137050.. 0000 0000 182100 182100.. 0000 0000 104249 104249.. 5850 5850 134575 134575.. 0000 0000 182100 182100.. 0000 0000 104251 104251.. 8750 8750 134575 134575.. 0000 0000 181875 181875.. 0000 0000 104251 104251.. 7960 7960 134350 134350.. 0000 0000 181875 181875.. 0000 0000 104252 104252.. 0070 0070 134350 134350.. 0000 0000 179400 179400.. 0000 0000 104251 104251.. 1870 1870 137050 137050.. 0000 0000 179400 179400.. 0000 0000 104248 104248.. 6870 6870 285 285 - 1 0 0 " PAN PANE" " 15322/ 1104" " St eel , car bon" on" 10. 0000 6 144575 144575.. 0000 0000 169625 169625.. 0000 0000 104250 104250.. 0000 0000 144575 144575.. 0000 0000 169400 169400.. 0000 0000 104250 104250.. 0000 0000 147050 147050.. 0000 0000 169400 169400.. 0000 0000 104250 104250.. 0000 0000 147050 147050.. 0000 0000 172100 172100.. 0000 0000 104250 104250.. 0000 0000 144350 144350.. 0000 0000 172100 172100.. 0000 0000 104250 104250.. 0000 0000 144350 144350.. 0000 0000 169625 169625.. 0000 0000 104250 104250.. 0000 0000 … mor e Pl Pl at es … 290 0 0 0 "PAN " PANE" " 15322/ 722" " St ee eell , car bon" on" 100. 0000 4 155080 155080.. 0000 0000 214000 214000.. 0000 0000 100169 100169.. 6710 6710 155079 155079.. 6090 6090 214000 214000.. 0000 0000 104010 104010.. 0000 0000 151319 151319.. 9370 9370 214000 214000.. 0000 0000 104010 104010.. 0000 0000 151320 151320.. 0000 0000 214000 214000.. 0000 0000 100170 100170.. 0850 0850 Packet Packet 40 65 295 295 120 120 1 "B " Base Pl at e 250 250 250 250 0 0" 0" 296 296 118 118 1 "B " Base Pl at e 250 250 250 250 0 0" 0" 305 305 128 128 1 "B " Base Pl at e 250 250 250 250 0 0" 0" 309 309 139 139 1 "B " Base Pl at e 150 150 250 250 0 0" 0" 310 310 138 138 1 "B " Base Pl at e 300 300 300 300 0 0" 0" 311 138 138 2 "TP" " TP" 312 312 141 141 1 " Def aul aul t Conne onnect ct i on" on" … mor e Con Conn nect i on Det ai l s … 708 151 151 1 " Moment Connect i on Bot Bot t om" 709 172 172 1 " Moment Connect i on Bot Bot t om" 710 172 2 " Moment Connect i on Top + Bot t om"

A: 5

1.5


A: 6

1.5

OpenSteel OpenSteel User Gui de Appendix: Sample Export Export Log File

B

A p p en d i x : Sa Sam p l e Ex p o r t Lo Lo g Fi Fi l e This appendix gives an example Export Log file.

( Er r or ) - SCTN SCTN 2 of SBFR SBFRA AMEWORK / SB3/ SB3/ PB1/ PB1/ 5/ ELV4. ELV4. 2 - Zer o l engt engt h Li near near Member ber - Not expo exporr t ed. ed. ( Er r or ) - SCTN 7 of SBFRA FRAMEWORK / SB3/ STR1 TR1/ A/ ROW - I l l egal egal or unset unset SPR SPRE - Not expo exporr t ed. ed. ( Er r or ) - PAN PANEL 1 of SBFR SBFRA AMEWORK / SB3/ SB3/ PB1/ PB1/ 7/ ELV4. ELV4. 2 - Pl at e t oo t hi n - Not expo xpor t ed. AVEVA EVA OpenS penStt ee eell ( pdm pdms2sdn s2s dnff v1. 5) ( May 22 2008 2008 : 16: 16: 41: 41: 06) 06) ( c) Cop Copyr yr i ght 1974 t o 2008 AVEVA Sol ut i ons ons Li mi t ed I ssue ssued t o Qui nt i c Lt Lt d ** *War ni ng** *: Li cense cense Feat Feat ur e PDMS2SDNF wi l l exp expi r e i n 14 days days t i me. STA START PRO PROCESSI ESSI NG at 0202- J unun- 2008 2008,,

Monda onday, y, 11: 11: 08: 08: 18

The f ol l owi ng mat er i al s wer e mapped apped St ee eell , car bon has 287 occur occur r ences ences Al l mat er i al s wer e mapp apped The f ol l owi ng pr of i l es wer e mapped apped CAGEF500 has 1 occ ur r ences Ear t hi ng- Boss- Di a- 40 has 1 occur occur r ences ces Ear t hi ng- Boss- Di a- 50 has 1 occur occur r ences ces HANDRAI L has 6 occur occ ur r ences HE120 E120A A has 6 occur occ ur r ences HE140 E140A A has 1 occur occ ur r ences HE160 E160A A has 14 occur occ ur r ences HE180 E180A A has 32 occur occ ur r ences HE180 E180B B has 2 occur occ ur r ences HE200 E200A A has 35 occur occ ur r ences HE200 E200B B has 4 occur occ ur r ences HE220 E220A A has 43 occur occ ur r ences

B: 1

1.5

OpenSteel OpenSteel User Gui de Appendix: Sample Export Export Log File

HE240 E240B B has HE280 E280A A has HE300 E300A A has HL1100R L1100R has I NP160 P160 has has L60x6 L60x6 has has L80x8 L80x8 has has LADDER_ ER_ TS has M2020- AB has M2424- AB has M3030- AB has OD193. 193. 7x5 has OD323. 323. 9x6. 9x6. 3 has has RHS200x200 S200x200x8 x8 has RHS300x300 S300x300x8 x8 has STST- STA STAN has has T140 T140 has TRED TRED has UNP180 P180 has

3 13 11 1 3 12 11 1 8 28 4 4 2 3 2 2 2 22 2

occur occ ur r ences occur occ ur r ences occur occ ur r ences occur occ ur r ences occur r ences ences occur r ences ences occur r ences ences occ ur r ences occur occ ur r ences occur occ ur r ences occur occ ur r ences occur occ ur r ences occur r ences ences occ ur r ences occ ur r ences occur r ences ences occur occ ur r ences occur occ ur r ences occur occ ur r ences

Al l pr of i l es wer e mapp apped The f ol l owi ng pr of i l es wer e not i n t he speci f i ed s t andar andar ds HP200x5 P200x54 4 has 1 occur occ ur r ences Al l mapped pr of i l es wer e i n t he def aul t st andar d END END PRO PROCESSI ESSI NG at 11: 08: 26 ====================================== Fi l es us ed ed. . . ============= Out put f i l e : . \ SDNF- Test . sdn sdn Pr of i l e Mappi ng f i l e : Z: \ Aveva3010\ 010\ Dev\ osde15 os de150\ 0\ maps\ PDM PDMS\ PDM PDMS. map Mat er i al Mappi ng f i l e : Z: \ Aveva3010\ 010\ Dev\ osde15 os de150\ 0\ maps\ PDM PDMS\ PDM PDMSMat . map St andar ds Tabl e f i l e : Z: \ Aveva3010\ Dev\ osde sde150\ t est \ t st df l t s\ OSDE\ sdn sdnf t st st d. map Pr of i l e Or i ent at i on f i l e: Z: \ Aveva3010\ 010\ Dev\ osde15 os de150\ 0\ maps\ PDM PDMS\ PDM PDMSOr i . map

B: 2

1.5

OpenSteel OpenSteel User Gui de Appendix: Sample Import Log Log Files

C

A p p en d i x : Sa Sam p l e Im p o r t L o g Fi Fi l es This appendix shows sample log files from an Import process according to the mode specified.

C.1

B r i ef Fo r m at In order to minimise the size of log files, especially when large models are being compared the user can ask the interface to output Verbose or Brief log files. In Verbose log files, full Brief log details of the comparison will be listed. In Brief log files, details of the comparison will be condensed onto a single line per item. This will be in the form of the following:

C.1.1

L i ne near Mem b er s LINMEM … … e.g. LINMEM =1234/5678 C Y Y N Y Y N Y Y N Y The mark field will contain the mark attribute by which the model components are to be identified between systems. The state field may contain on of three options, A for added, D for deleted or C for changed. The other fields contain either a Y or N indicating whether the attribute at that location has been changed or not.

C.1.2

Pl at es PLATE PLATE … … The rules for values in each of the above fields are as for the Linear Members. Below is a sample log file in brief format following an Import:

AVEVA EVA OpenS penStt ee eell ( sdnf 2pdm 2pdms v1. 5) ( May 22 2008 2008 : 16: 16: 34: 34: 01) 01) ( c) Cop Copyr yr i ght 1974 t o 2008 AVEVA Sol ut i ons ons Li mi t ed I ssue ssued t o Qui nt i c Lt Lt d ** *War ni ng** *: Li cense cense Feat Feat ur e SDNF2PD F2PDMS wi l l exp expi r e i n 14 days days t i me. STA START PRO PROCESSI ESSI NG at 0202- J unun- 2008 2008,,

C:1

Monda onday, y, 11: 11: 56: 56: 26

1.5


The f ol l owi ng mat er i al s wer e mapped apped Gol d, pur e cast has 2 occur occur r ences ences St ee eell , car bon has 285 occur occur r ences ences Al l mat er i al s wer e mapp apped The f ol l owi ng pr of i l es wer e mapped apped CAGEF500 has 1 occ ur r ences Ear t hi ng- Boss- Di a- 40 has 1 occur occur r ences ces Ear t hi ng- Boss- Di a- 50 has 1 occur occur r ences ces HANDRAI L has 6 occur occ ur r ences HE120 E120A A has 6 occur occ ur r ences HE140 E140A A has 1 occur occ ur r ences HE160 E160A A has 14 occur occ ur r ences HE180 E180A A has 33 occur occ ur r ences HE180 E180B B has 2 occur occ ur r ences HE200 E200A A has 35 occur occ ur r ences HE200 E200B B has 4 occur occ ur r ences HE220 E220A A has 42 occur occ ur r ences HE240 E240B B has 3 occur occ ur r ences HE280 E280A A has 13 occur occ ur r ences HE300 E300A A has 11 occur occ ur r ences HL1100R L1100R has 1 occur occ ur r ences I NP160 P160 has has 3 occur r ences ences L60x6 L60x6 has has 12 occur r ences ences L80x8 L80x8 has has 11 occur r ences ences LADDER_ ER_ TS has 1 occ ur r ences M2020- AB has 8 occur occ ur r ences M2424- AB has 28 occur occ ur r ences M3030- AB has 4 occur occ ur r ences OD193. 193. 7x5 has 4 occur occ ur r ences OD323. 323. 9x6. 9x6. 3 has has 2 occur r ences ences RHS200x200 S200x200x8 x8 has 3 occ ur r ences RHS300x300 S300x300x8 x8 has 2 occ ur r ences STST- STA STAN has has 2 occur r ences ences T140 T140 has 2 occur occ ur r ences TRED TRED has 22 occur occ ur r ences UNP180 P180 has 2 occur occ ur r ences Al l pr of i l es wer e mapp apped The f ol l owi ng pr of i l es wer e not i n t he speci f i ed s t andar andar ds HP200x5 P200x54 4 has 1 occur occ ur r ences

C:2

1.5


Al l mapped pr of i l es wer e i n t he def aul t ====================================== LI NMEM =15322/ 15322/ 254 C Y Y Y Y L I NMEM =15322/ 15322/ 447 C Y N N N L I NMEM =15322/ 15322/ 448 C Y N N N L I NMEM =15322/ 15322/ 450 C Y N N N L I NMEM =15322/ 15322/ 451 C Y N N N L I NMEM =15322/ 15322/ 877 C Y N N N L I NMEM =15322/ 15322/ 951 C Y N N N L I NMEM =15322/ 15322/ 952 C Y N N N L I NMEM =15322/ 15322/ 997 C Y N N N L I NMEM =15322/ 15322/ 998 C Y N N N PLATE PL ATE =15322/ 15322/ 1104 C N N N N PLATE PL ATE =15322/ 296 C Y Y Y Y L I NMEM =15322/ 15322/ 2682 A N N N N L I NMEM =15322/ 15322/ 2683 A N N N N L I NMEM =15322/ 15322/ 2684 A N N N N PLATE PL ATE =1532 15322/ 2/ 2767 2767 A N N N N L I NMEM =15322/ 15322/ 423 D N N N N L I NMEM =15322/ 15322/ 628 D N N N N L I NMEM =15322/ 15322/ 632 D N N N N L I NMEM =15322/ 15322/ 644 D N N N N L I NMEM =15322/ 15322/ 878 D N N N N PLATE PL ATE =1532 15322/ 2/ 1015 1015 D N N N N PLATE PL ATE =1532 15322/ 2/ 553 553 D N N N N

st andar d Y N N N N N N N N N N Y N N N N N N N N N N N

Y N N N N N N N N N N N N N N N N N N N N N N

Y N N N N N N N N N Y N N N N N N N N N N N N

Y N N N N N N N N N N Y N N N N N N N N N N N

Y N N N N N N N N N

Y N N N N N N N N N

N N N

N N N

N N N N N

N N N N N

Fi l es us ed ed. . . ============= I nput f i l e : Z: \ Aveva3010\ Dev\ osde sde150\ t est \ r esul sul t s\ i mpor t \ SDNF- Test . sdn sdn Pr of i l e Mappi ng f i l e : Z: \ Aveva3010\ 010\ Dev\ osde15 os de150\ 0\ maps\ PDM PDMS\ PDM PDMS. map Mat er i al Mappi ng f i l e : Z: \ Aveva3010\ 010\ Dev\ osde15 os de150\ 0\ maps\ PDM PDMS\ PDM PDMSMat . map St andar ds Tabl e f i l e : Z: \ Aveva3010\ Dev\ osde sde150\ t est \ t st df l t s\ OSDE\ sdn sdnf t st st d. map Pr of i l e Or i ent at i on f i l e: Z: \ Aveva3010\ 010\ Dev\ osde15 os de150\ 0\ maps\ PDM PDMS\ PDM PDMSOr i . map

C:3

1.5


C.2

Ver b o s e Fo r m at Below is a verbose log file of the same Import as above:

AVEVA EVA OpenS penStt ee eell ( sdnf 2pdm 2pdms v1. 5) ( May 22 2008 2008 : 16: 16: 34: 34: 01) 01) ( c) Cop Copyr yr i ght 1974 t o 2008 AVEVA Sol ut i ons ons Li mi t ed I ssue ssued t o Qui nt i c Lt Lt d ** *War ni ng** *: Li cense cense Feat Feat ur e SDNF2PD F2PDMS wi l l exp expi r e i n 14 days days t i me. STA START PRO PROCESSI ESSI NG at 0202- J unun- 2008 2008,,

Monda onday, y, 11: 11: 45: 45: 10

The f ol l owi ng mat er i al s wer e mapped apped Gol d, pur e cast has 2 occur occur r ences ences St ee eell , car bon has 285 occur occur r ences ences Al l mat er i al s wer e mapp apped The f ol l owi ng pr of i l es wer e mapped apped CAGEF500 has 1 occ ur r ences Ear t hi ng- Boss- Di a- 40 has 1 occur occur r ences ces Ear t hi ng- Boss- Di a- 50 has 1 occur occur r ences ces HANDRAI L has 6 occur occ ur r ences HE120 E120A A has 6 occur occ ur r ences HE140 E140A A has 1 occur occ ur r ences HE160 E160A A has 14 occur occ ur r ences HE180 E180A A has 33 occur occ ur r ences HE180 E180B B has 2 occur occ ur r ences HE200 E200A A has 35 occur occ ur r ences HE200 E200B B has 4 occur occ ur r ences HE220 E220A A has 42 occur occ ur r ences HE240 E240B B has 3 occur occ ur r ences HE280 E280A A has 13 occur occ ur r ences HE300 E300A A has 11 occur occ ur r ences HL1100R L1100R has 1 occur occ ur r ences I NP160 P160 has has 3 occur r ences ences L60x6 L60x6 has has 12 occur r ences ences L80x8 L80x8 has has 11 occur r ences ences LADDER_ ER_ TS has 1 occ ur r ences M2020- AB has 8 occur occ ur r ences M2424- AB has 28 occur occ ur r ences M3030- AB has 4 occur occ ur r ences OD193. 193. 7x5 has 4 occur occ ur r ences

C:4

1.5


OD323. 323. 9x6. 9x6. 3 has has RHS200x200 S200x200x8 x8 has RHS300x300 S300x300x8 x8 has STST- STA STAN has has T140 T140 has TRED TRED has UNP180 P180 has

2 3 2 2 2 22 2

occur r ences ences occ ur r ences occ ur r ences occur r ences ences occur occ ur r ences occur occ ur r ences occur occ ur r ences

Al l pr of i l es wer e mapp apped The f ol l owi ng pr of i l es wer e not i n t he speci f i ed s t andar andar ds HP200x5 P200x54 4 has 1 occur occ ur r ences Al l mapped pr of i l es wer e i n t he def aul t st andar d ( War ni ng) ng) - END PRO PROCESSI ESSI NG at 11: 11: 45: 45: 19 ======================================

CHANGES t o mappe apped d ent ent i t i es i n / TEST TEST-- SDNF- I NTER TERFAC FACE SCTN SCTN =1532 15322/ 2/ 254 254 i n / TESTTEST- SDNF- I NTERFAC TERFACE E Pr of i l e ' HE180A' chan chang ged f r om ' HE220A' Rot at i on ' N WRT / *' chan chang ged f r om ' W WRT / *' St ar t ' E 1552 155200 00 N 1490 149000 00 U 1001 100170 70 WRT / * ' change changed d f r om ' E 155200 N 148000 U 100170 WRT / * ' End End ' E 1552 155200 00 N 1490 149000 00 U 1042 104250 50 WRT / * ' changed changed f r om ' E 155200 N 148000 U 104250 WRT / * ' J ust ' TOS' cha changed f r om ' NA' Sr el ' DX DY DZ RX RY RZ' chang changed ed f r om ' ' Er el ' DX DY DZ RX RY RZ' chang changed ed f r om ' ' : SDNFHo FHol d ' 1' cha changed f r om ' 0' : SDNFPspe FPspec c ' 1' chan chang ged f r om ' 0' Mat r ' =15326/ 30' chan changed f r om ' =15326/ 21' Mgr ade ' Gol d, pur e cast cast ' cha changed f r om ' St eel , car car bon' SCTN SCTN =1532 15322/ 2/ 447 447 i n / TESTTEST- SDNF- I NTERFAC TERFACE E J ust ' TOAY' chan chang ged f r om ' TOAX' SCTN SCTN =1532 15322/ 2/ 448 448 i n / TESTTEST- SDNF- I NTERFAC TERFACE E J ust ' TOAY' chan chang ged f r om ' TOAX' SCTN SCTN =1532 15322/ 2/ 450 450 i n / TESTTEST- SDNF- I NTERFAC TERFACE E J ust ' TOAY' chan chang ged f r om ' TOAX' SCTN SCTN =1532 15322/ 2/ 451 451 i n / TESTTEST- SDNF- I NTERFAC TERFACE E J ust ' TOAY' chan chang ged f r om ' TOAX' SCTN SCTN =1532 15322/ 2/ 877 877 i n / TESTTEST- SDNF- I NTERFAC TERFACE E

C:5

1.5


J ust ' TOAY' chan chang ged f r om ' TOAX' SCTN SCTN =1532 15322/ 2/ 951 951 i n / TESTTEST- SDNF- I NTERFAC TERFACE E J ust ' TOAY' chan chang ged f r om ' TOAX' SCTN SCTN =1532 15322/ 2/ 952 952 i n / TESTTEST- SDNF- I NTERFAC TERFACE E J ust ' TOAY' chan chang ged f r om ' TOAX' SCTN SCTN =1532 15322/ 2/ 997 997 i n / TESTTEST- SDNF- I NTERFAC TERFACE E J ust ' TOAY' chan chang ged f r om ' TOAX' SCTN SCTN =1532 15322/ 2/ 998 998 i n / TESTTEST- SDNF- I NTERFAC TERFACE E J ust ' TOAY' chan chang ged f r om ' TOAX' PANE =1532 15322/ 2/ 1104 1104 i n / TESTTEST- SDNF- I NTERFAC TERFACE E Ver t ex cou count ' 5' cha changed f r om ' 6' PANE =1532 15322/ 2/ 296 296 i n / TESTTEST- SDNF- I NTERFAC TERFACE E : SDNFHo FHol d ' 1' cha changed f r om ' 0' : SDNFPspe FPspec c ' 1' chan chang ged f r om ' 0' Mat r ' =15326/ 30' chan changed f r om ' =15326/ 21' Mgr ade ' Gol d, pur e cast cast ' cha changed f r om ' St eel , car car bon' Hei g ' 50' cha changed f r om ' 25' J ust ' TOP' chan chang ged f r om ' DBOT' Ver t ex 4 ' E 1552 155290 90 N 1598 159890 90 U 1043 104350 50 WRT / * ' changed changed f r om ' E 155290 N 159890 159890 U 104250 WRT / * ' =========================== CHAN CHANG GES >>>> 28 det det ect ec t ed

ADDI TI ONS t o mapp apped ent ent i t i es i n / TEST TEST-- SDNF- I NTER TERFAC FACE LI NMEM =15322/ 15322/ 3023 3023 has been LI NMEM =15322/ 15322/ 3024 3024 has been LI NMEM =15322/ 15322/ 3025 3025 has been PLATE PL ATE =15322/ 3108 has been =========================== ADDI TI ONS >>>> 4 det ect ec t ed

added. added. added. added. added. added. added.

DELETI ELETI ONS t o mappe apped d ent ent i t i es i n / TEST TEST-- SDNF- I NTER TERFAC FACE LI NMEM =1532 15322/ 2/ 423 423 has has been been del del et ed. ed. LI NMEM =1532 15322/ 2/ 628 628 has has been been del del et ed. ed. LI NMEM =1532 15322/ 2/ 632 632 has has been been del del et ed. ed. LI NMEM =1532 15322/ 2/ 644 644 has has been been del del et ed. ed. LI NMEM =1532 15322/ 2/ 878 878 has has been been del del et ed. ed. PLATE PLATE =1532 15322/ 2/ 1015 1015 has been been del et ed. PLATE PLATE =1532 15322/ 2/ 553 553 has been been del et ed.

C:6

1.5


=========================== DELETI EL ETI ONS >>>> 7 det ect ec t ed Fi l es us ed ed. . . ============= I nput f i l e : Z: \ Aveva3010\ Dev\ osde sde150\ t est \ r esul sul t s\ i mpor t \ SDNF- Test . sdn sdn Pr of i l e Mappi ng f i l e : Z: \ Aveva3010\ 010\ Dev\ osde15 os de150\ 0\ maps\ PDM PDMS\ PDM PDMS. map Mat er i al Mappi ng f i l e : Z: \ Aveva3010\ 010\ Dev\ osde15 os de150\ 0\ maps\ PDM PDMS\ PDM PDMSMat . map St andar ds Tabl e f i l e : Z: \ Aveva3010\ Dev\ osde sde150\ t est \ t st df l t s\ OSDE\ sdn sdnf t st st d. map Pr of i l e Or i ent at i on f i l e: Z: \ Aveva3010\ 010\ Dev\ osde15 os de150\ 0\ maps\ PDM PDMS\ PDM PDMSOr i . map

C:7

1.5


C:8

1.5

OpenSteel OpenSteel User Gui de Appendix: Sample Validity Check Check Log File

D

A p pe pen d ix ix : Sa Sam pl pl e Val id id i ty ty Ch Ch ec ec k Lo Lo g Fi le le This appendix shows a sample log file from an Import validity checking process to check for duplicate mark numbers.

AVEVA EVA OpenS penStt ee eell ( sdnf 2pdm 2pdms v1. 5) ( May 22 2008 2008 : 16: 16: 34: 34: 01) 01) ( c) Cop Copyr yr i ght 1974 t o 2008 AVEVA Sol ut i ons ons Li mi t ed I ssue ssued t o Qui nt i c Lt Lt d STA START PRO PROCESSI ESSI NG at 0202- J unun- 2008 2008,,

Monda onday, y, 08: 08: 59: 59: 59

The f ol l owi ng mat er i al s wer e mapped apped Gol d, pur e cast has 2 occur occur r ences ences St ee eell , car bon has 285 occur occur r ences ences Al l mat er i al s wer e mapp apped The f ol l owi ng pr of i l es wer e mapped apped CAGEF500 has 1 occ ur r ences Ear t hi ng- Boss- Di a- 40 has 1 occur occur r ences ces Ear t hi ng- Boss- Di a- 50 has 1 occur occur r ences ces HANDRAI L has 6 occur occ ur r ences HE120 E120A A has 6 occur occ ur r ences HE140 E140A A has 1 occur occ ur r ences HE160 E160A A has 14 occur occ ur r ences HE180 E180A A has 33 occur occ ur r ences HE180 E180B B has 2 occur occ ur r ences HE200 E200A A has 35 occur occ ur r ences HE200 E200B B has 4 occur occ ur r ences HE220 E220A A has 42 occur occ ur r ences HE240 E240B B has 3 occur occ ur r ences HE280 E280A A has 13 occur occ ur r ences HE300 E300A A has 11 occur occ ur r ences HL1100R L1100R has 1 occur occ ur r ences I NP160 P160 has has 3 occur r ences ences L60x6 L60x6 has has 12 occur r ences ences

D:1

1.5


L80x8 L80x8 has has LADDER_ ER_ TS has M2020- AB has M2424- AB has M3030- AB has OD193. 193. 7x5 has OD323. 323. 9x6. 9x6. 3 has has RHS200x200 S200x200x8 x8 has RHS300x300 S300x300x8 x8 has STST- STA STAN has has T140 T140 has TRED TRED has UNP180 P180 has

11 1 8 28 4 4 2 3 2 2 2 22 2

occur r ences ences occ ur r ences occur occ ur r ences occur occ ur r ences occur occ ur r ences occur occ ur r ences occur r ences ences occ ur r ences occ ur r ences occur r ences ences occur occ ur r ences occur occ ur r ences occur occ ur r ences

Al l pr of i l es wer e mapp apped The f ol l owi ng pr of i l es wer e not i n t he speci f i ed s t andar andar ds HP200x5 P200x54 4 has 1 occur occ ur r ences Al l mapped pr of i l es wer e i n t he def aul t st andar d ( War ni ng) ng) - END PRO PROCESSI ESSI NG at 09: 09: 00: 00: 08 ======================================

Checki hecki ng GLOB LOBAL Dup Dupll i cat e Mar k Num Number ber s i n / * Mar k N Num umber ( 12345 12345 ) f ound on =15322/ 15322/ 3358 3358 and =15322/ 3359 Mar k N Num umber ( 67890 67890 ) f ound on =15322/ 15322/ 3360 3360 and =15322/ 3443 =========================== GLOB LOBAL Dupl Dupl i c at e Mar k N Num umber s >>>> 2 det ect ec t ed Fi l es us ed ed. . . ============= I nput f i l e : Z: \ Aveva3010\ Dev\ osde sde150\ t est \ r esul sul t s\ i mpor t \ SDNF- Test . sdn sdn Pr of i l e Mappi ng f i l e : Z: \ Aveva3010\ 010\ Dev\ osde15 os de150\ 0\ maps\ PDM PDMS\ PDM PDMS. map Mat er i al Mappi ng f i l e : Z: \ Aveva3010\ 010\ Dev\ osde15 os de150\ 0\ maps\ PDM PDMS\ PDM PDMSMat . map St andar ds Tabl e f i l e : Z: \ Aveva3010\ Dev\ osde sde150\ t est \ t st df l t s\ OSDE\ sdn sdnf t st st d. map Pr of i l e Or i ent at i on f i l e: Z: \ Aveva3-

D:2

1.5

OpenSteel OpenSteel User Guid e Appendix: Sample Validity Check Check Log File

010\ 010\ Dev\ osde15 os de150\ 0\ maps\ PDM PDMS\ PDM PDMSOr i . map

D:3

1.5


D:4

1.5

OpenSteel OpenSteel User Gui de

Index

A

G

Anchor Bolt locations . . . . . . . . . . . . . . . . . . . . . . 5:1 quantities . . . . . . . . . . . . . . . . . . . . . 5:2 AVEVA OpenSteel - Export Form . . . . . . 3:9

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . 2:1 Grid Packet Packet 50 . . . . . . . . . . . . . . . . . . . . . 6:8

I B Bolt Reports . . . . . . . . . . . . . . . . . . . . . . 5:1

C Cardinal Points . . . . . . . . . . . . . . . . . . . 6:18 Comparison and Merging Processes . . 4:13 Connection Details Packet 40 . . . . . . . . . . . . . . . . . . . . . 6:7 Cross Referencing Models . . . . . . . . . . 6:25

D

Import from SDNF . . . . . . . . . . . . . . . . . 4:1 Import Information . . . . . . . . . . . . . . . . . 4:4 Import Log Files sample . . . . . . . . . . . . . . . . . . . . . . . C:1 Import Process . . . . . . . . . . . . . . . . . . . 4:10

L Linear Member using cutbacks . . . . . . . . . . . . . . . . 6:10 Linear Members Packet 10 . . . . . . . . . . . . . . . . . . . . . 6:5

Default Orientations . . . . . . . . . . . . . . . 6:19

M

E

Member Loading Packet 30 . . . . . . . . . . . . . . . . . . . . . 6:7

Export Information . . . . . . . . . . . . . . . . . . 3:5 Export Log File sample . . . . . . . . . . . . . . . . . . . . . . .B:1 . B:1 Exporting Connections . . . . . . . . . . . . . 3:16 Exporting Linear Members . . . . . . . . . . 3:12 Exporting Plates . . . . . . . . . . . . . . . . . . 3:14 Exporting to SDNF . . . . . . . . . . . . . . . . . 3:1

O OpenSteel - Import Form . . . . . . . . . . . . 4:9 OpenSteel Export testing . . . . . . . . . . . . . . . . . . . . . . 3:18

P Pline Selection Rules . . . . . . . . . . . . . . 6:21

Index page 1

1.5

OpenSteel OpenSteel User Gui de

R Run Information . . . . . . . . . . . . . . . 3:8 4:6 ,

S SDNF file header information . . . . . . . . . . . 6:8 recommended file suffix . . . . . . . . . . 6:8 sample file . . . . . . . . . . . . . . . . . . . . A:1 . A:1 Source Information . . . . . . . . . . . . . . . . . 4:2

T Target Information . . . . . . . . . . . . . . . . . . 3:2 Technical Information . . . . . . . . . . . . . . . 6:1 The Export Process . . . . . . . . . . . . . . . 3:10

U UDAs . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:23

V Validity Check Log File sample . . . . . . . . . . . . . . . . . . . . . . .D:1 .D:1 Verbose Format . . . . . . . . . . . . . . . . . . .C:4 . C:4 Version Numbering . . . . . . . . . . . . . . . . 6:25

Index page 2

1.5

Open Steel User Guide

Recommend Documents