OpenSteel User Guide

OpenSteel
User Guide
AVEVA Solutions Limited
Disclaimer
1.1 AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free from
viruses.
1.2 AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar losses; loss of
anticipated savings; loss of goods; loss of contract; loss of use; loss or corruption of data or information; any
special, indirect, consequential or pure economic loss, costs, damages, charges or expenses which may be
suffered by the user, including any loss suffered by the user resulting from the inaccuracy or invalidity of any data
created by the AVEVA software, irrespective of whether such losses are suffered directly or indirectly, or arise in
contract, tort (including negligence) or otherwise.
1.3 AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with the
performance of the AVEVA software shall be limited to 100% of the licence fees paid in the year in which the user's
claim is brought.
1.4 Clauses 1.1 to 1.3 shall apply to the fullest extent permissible at law.
1.5 In the event of any conflict between the above clauses and the analogous clauses in the software licence under
which the AVEVA software was purchased, the clauses in the software licence shall take precedence.
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, or is validly licensed by, AVEVA Solutions Limited or its subsidiaries.
All rights are reserved to AVEVA Solutions Limited 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 Limited. Where such permission is granted, it expressly requires
that this copyright notice, and the above disclaimer, 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 Limited. The user may not reverse
engineer, decompile, copy, or adapt the software. Neither the whole, nor part of the software described in this
publication may be incorporated into any third-party software, product, machine, or system without the prior written
permission of AVEVA Solutions Limited, save as permitted by law. Any such unauthorised action is strictly
prohibited, and may give rise to civil liabilities and criminal prosecution.
The AVEVA software described in this guide is to be installed and operated strictly in accordance with the terms
and conditions of the respective software licences, and in accordance with the relevant User Documentation.
Unauthorised or unlicensed use of the software is strictly prohibited.
Copyright 1999 to current year. AVEVA Solutions Limited, and its subsidiaries. All rights reserved. AVEVA shall not
be liable for any breach or infringement of a third party's intellectual property rights where such breach results from
a user's modification of the AVEVA software or associated documentation.
AVEVA Solutions Limited, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom.
Trademark
AVEVA and Tribon are registered trademarks of AVEVA Solutions Limited or its subsidiaries. Unauthorised use of
the AVEVA or Tribon trademarks is strictly forbidden.
AVEVA product/software names are trademarks or registered trademarks of AVEVA Solutions Limited or its
subsidiaries, registered in the UK, Europe and other countries (worldwide).
The copyright, trademark rights, or other intellectual property rights in any other product or software, its name or
logo belongs to its respective owner.
OpenSteel User Guide
Revision Sheet
Date Version Comments / Remarks

1st January 1999 1 First release of PDMS OPEN STEEL DETAIL EXCHANGE
1.1.1
28th February 1999 2 Profile Orientation Mapping Tables added (v1.1.2)
27th July 2000 3 Major Upgrade to PDMS11.3 (v1.2.1)
Product renamed PDMS OpenSteel
30th November 2003 4 Upgrade interface and documentation to VANTAGE Plant
Design OpenSteel 1.3/ VANTAGE PDMS 11.5.SP1
2nd June 2008 5 Upgrade to v.1.5
Product renamed to AVEVA OpenSteel
Merged with OSDE-Bulletin1.4.doc
30th June 2010 6 Upgrade to v2 .1.
30th November 2010 2.2 Upgrade to be compatible with PDMS12.1
January 2012 Copyright added to all pages.
June 2013 2.3 Using AVEVA Licensing System (ALS).
Contents Page
User Guide
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Exporting to SDNF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1
Target Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2
Export/Import different SDNF Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4
Export Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4
Run Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:7
Export Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:8
Export and Cancel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:9
The Export Form Bar Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:9
The Export Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:9
Exporting Linear Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:11
Exporting Plates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:13
Transferring Holes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:15
Exporting Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:16
Testing Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:17
Initial Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:17
Preparing to Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:18
Creation of Export File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:21
Checking the SDNF Output File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:22
Import from SDNF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1

Source Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2
© Copyright 1999 to current year. i 2.3

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
Import Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4

Auto-detection of SDNF Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6
Run Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:7
Import Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:9
Import and Cancel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:10
Import Form Bar Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:10
Import Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:10
Comparison and Merging Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:13
The Comparison Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:14
The Merging Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:16
Deleted Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:17
Validation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:18
Highlighting Changes in the Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:19
Highlighting by Import Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:19
Highlighting by Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:20
Testing AVEVA OpenSteel - Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:21
Initial Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:22
Preparing to Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:23
Importing the SDNF File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:26
Comparing the Imported Model with the Original . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:27
Performing a Validity Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:27
Bolt Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1

Anchor Bolt Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1
Anchor Bolt Quantities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2
Technical Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1

SDNF - Structural Steel Detailing Neutral File Format . . . . . . . . . . . . . . . . . . . . 6:1
Export/Import different SDNF Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1
Auto-detection of SDNF Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:2
Packet 00 - Title Packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:4
Packet 10 - Linear Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5
Location of Linear Members in Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:6
Packet 20 - Plates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:6
Packet 22 - Holes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:8
Packet 30 - Member Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:9
Packet 40 - Connection Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:9
Packet 50 - Grid Packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:10
© Copyright 1999 to current year. ii 2.3

Packet 60 - Format Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:10

Recommended SDNF File Suffix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:11
SDNF File Header Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:11
Member ID Numbers at SDNFv3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:12
Using Linear Member Cutbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:13
Exporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:14
Importing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:17
Cardinal Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:19
Default Orientations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:20
Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:21
Pline Selection Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:22
Use of Pline Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:24
UDAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:24
General Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:24
Structural Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:25
Project Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:25
Cross Referencing Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:26
Element created in DESIGN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:26
Element created outside DESIGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:26
Cross Database Working. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:26
Issues Concerning Entity Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:27
Transfer of Curved Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:27
Version Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:28
On Transfer from Design:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:29
On Transfer into Design: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:29
Exclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:29
Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:30
Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:30
Possible License Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:31
Sample SDNF File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A:1

Sample Export Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B:1
Sample Import Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C:1
Brief Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:1
Linear Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:1
© Copyright 1999 to current year. iii 2.3

Plates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:1
Verbose Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:3
Sample Validity Check Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D:1
© Copyright 1999 to current year. iv 2.3

Introduction
1 Introduction
AVEVA 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, 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 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 produce reports of Anchor Bolts from the
model using the Bolt Report templates
Technical Information contains technical information
Sample SDNF File gives a brief extract of an SDNF file produced by the AVEVA
OpenSteel interface
Sample Export Log File gives an example Export Log file
Sample Import Log Files shows sample log files from an Import process according to
the mode specified
Sample Validity Check shows a sample log file from an Import validity checking
Log File process to check for duplicate mark numbers
© Copyright 1999 to current year. 1:1 2.3

Introduction

Glossary
2 Glossary
This section explains terms used in this manual.
Cardinal Point An SDNF concept representing points 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 (GENSEC)

element. Formerly this was mapped to a SCTN element.
Linear Members can be either Straight or Curved: Straight
members are transferred through Packet 10; Curved ones,
circular arcs, are transferred through Packet 60. In both
cases, the member cross section profile is constant along its
length.
Plate An SDNF Entity mapped to the Design Panel (PANE)

element.
PML/F&M The AVEVA PDMS programmable macro language,

allowing user’s to create their own user interface.
SDNF (Structural Steel Defined by the Intergraph FrameWorks user community for
Detailing Neutral File the transfer of steel data. It is in the public domain and is
Format) 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 An attribute in DESIGN which the user can define and
Attribute) attach to specific elements. This interface requires a certain
set of UDAs for storing SDNF-specific data.

Glossary

Exporting to SDNF
3 Exporting to 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 OpenSteel - Export 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 OpenSteel - Export form from the User General Utilities menu bar,
select Export>(d) AVEVA OpenSteel.

Exporting to SDNF
3.1 Target Information

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 information button on the main AVEVA OpenSteel - Export form.
The interface requires at least 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
and/or the Unicode mapping tables if necessary. The main mapping tables are for the Steel
Profiles, Materials and for mapping the Profile Orientations between PDMS and the neutral
file. The Unicode mapping table is to translate PDMS Unicode strings into ASCII strings
according to the SDNF Format Specification. The section on user customisation in the
Configuration Guide tells the user how to arrange these files on your 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 AVEVA OpenSteel Configuration Guide which explains how to configure the interface to
tell it where all the files are located.
The user may have a generic set of mapping tables to map between PDMS and SDNF for a
particular steel fabricator, for example, or the user may have a similar set 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 these files are compatible with the Target Package by checking
the identification line at the top of each mapping table. Refer to the AVEVA OpenSteel
Configuration Guide for details about the format of these mapping files.
There are two main options on this form: Auto and Manual. These can be activated by
selecting the appropriate toggle button on the left-hand side of the form.

Exporting to SDNF
The Auto option causes the interface to select automatically the 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 other buttons, which are greyed out for the Auto 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 or Unicode 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.
On clicking carriage return, the interface will check for existence of the file and compatibility
with the Target Package indicated by the 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 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 Log File Messages

The following error and log messages are displayed.
Internal error Internal lists are not in step.
Cannot find suitable Internal mapping files not found.

internal mapping list
Suitable Mapping Table Mapping table found is not for the correct Target
File not found Package, or it does not exist.

Exporting to SDNF
Not a suitable Mapping Incorrect format of file, or empty file, or wrong Target
Table File Package.
Bad Map File Mapping file is not correct format. Possibly it is from
another operating system.
Error on OpenSteel File The user has entered incorrect data on the file browser
Browser form form.
3.1.1 Export/Import different SDNF Formats

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, there are many more records attached to each linear member and the method of
plate definition has changed. The interface does use some of this new information,
principally the date and times of creation and modification.
On the Export Information form there is a drop down list which the user can use to select
which SDNF version to output.
3.1.2 Export Information

The Export Information form contains information about the actual Export process. This
form is created by clicking the Export information button on the AVEVA OpenSteel -
Export form.

Exporting to SDNF
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
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 their holes (Packet 22); a set of Connection
Details, Packet 40, and a set of Arc Members (Packet 60). 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 on 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

Exporting to SDNF
not enough space on the form the element's reference number is output rather than its
name.
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 Apply 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 databases.
Using the toggles on the Export Information form, the user can select whether to export
Packet 10 (Straight), Packet 60 (Curved) or Packet 20 (Plates) with the option of their
holes, Packet 22 (Holes). The user cannot output Packet 40 (End Connections) without

Exporting to SDNF
outputting either Packet 10 (Straight) or Packet 60 (Curved). If the user wants neither
Packet 10 nor Packet 60, the sub-options, Members only and Members + End
Connections are inactivated and greyed out. Similarly, one cannot output Packet 22
(Holes) without outputting Packet 20 (Plates). But you will be able to export Plates without
their holes.
The interface will check that the user is attempting to Export something and output a
message accordingly.
Once all the correct data has been entered on the Export Information form, click OK and
the interface variables will be updated. Clicking CANCEL will remove the form, leaving the
original interface variables unchanged.

The following error and log message are displayed.
Export file already exists File exists, the user will get the option to overwrite it.
Wrong place 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
letter increment it.
3.2 Run Information

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 OpenSteel - Export 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

Exporting to SDNF
failure in the Export process. Therefore, the user can select this option to define this as a
test run.
After the Export process 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 the run is a
trial.
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
3.3 Export Form

On the main Export form the Members list may be used to navigate around the database
hierarchy.
The user must enter the elements to be exported, but need not select only SCTNs (Straight
Members), GENSECs (Curved Members), or only PANEs (Plates). The interface will locate
all SCTNs, GENSECs and 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
enhanced 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.

Add CE just adds the current element to the list. This also implies all items below the
current element in the database hierarchy. The WORL can not be added to the list.
The Add by Pick 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.
Add Structure 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 options work only on entries in the Export list, 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 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 Add by Pick 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.

Exporting to SDNF
Clear just removes everything from the list.

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.

Can't export the WORLD the user cannot export the WORLD
No owning Structure Cannot climb to Structure element from current location

in database.
3.3.1 Export and Cancel

Cancel removes the AVEVA OpenSteel Export form from the screen.
Export executes the Export process. As it proceeds the user is kept informed of the
progress by means of messages at the bottom of the main Design window as well as by
forms and prompts.
3.3.2 The Export Form Bar Menu

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 identify 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 The Export Process

Exporting from PDMS all items are exported using millimetres as the distance units.
All reference data, such as any 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.
• Is the output file named?
• Are we going to export anything?
• Are the mapping tables compatible with the Target Package?
• Have we a valid Steel Standard table?
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.

Exporting to SDNF
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 the 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.
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.

Exporting to SDNF
To inspect the log file later, 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. 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 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.

The following error and log messages are displayed
File does not exist Somehow there is no log file. Are there issues regarding
access rights to the %PDMSWK% directory?
3.3.4 Exporting Linear Members

A series of checks are made before a Linear Member is output.
• Is the SPRE set?
• Is it a zero length member?

Exporting to SDNF
• Does it have a valid material?

• Is the Justification Pline mappable to a Cardinal Point if it is not a Cardinal Point itself?
• Are the start and end points valid?
If any of the above criteria is not satisfied, the linear member does not even get exported to
the SDNF output file. As has been indicated before, Linear Members can be transferred as
either Straight in Packet 10 or Curved in Packet 60. In SDNF, curved members are just
circular arcs. In PDMS, curved members are modelled using GENSECs. However,
GENSECs can be compound shapes with both straight and arc sections. As a result,
SCTNs and straight portions of GENSECs are transferred through Packet 10, and the
curved segments are transferred through Packet 60. See the section on importing Linear
Members for more information about the reconstruction of complex GENSECs.
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 transfer 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.
OpenSteel may not be able to update the export information on the elements. This would
usually be because the database is read-only. If this is the case, a session related macro file
is produced for execution immediately afterwards, or when one has write access to the
database. This file is called updateVersionNos<export date/time>.mac and is stored in the
PDMSWK folder.

Illegal or unset SPRE - Not SPRE must be valid.

exported
Zero length Linear Member Length less than user definable tolerance.
- Not exported
No material information - Cannot determine material properties for member.

Not exported
No material match for SDNFMGRADE cannot be matched with a material in

nnnn. - Unknown material the Properties database.
No material property match As above
Inconsistent material The element's MATR and :SDNFMGRADE attributes are

specification not consistent.
Multiply defined entries in Either a material to be mapped or a mapped profile

Material Table appears more than once in the material file.
No match for material The material is not in the material file
Syntax Error Other, less specific, errors.

Exporting to SDNF
Unrecognised Parse 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 will also
be output.
No match for Cardinal Pline or Cardinal Point not recognised. Neutral axis
Point nnnn (Cardinal Point 10) assumed.
No Cardinal Point nnnn JUSL unset.
Bad Cardinal 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 the The profile is in the profile mapping file but is not in any
standard one of the set of standards.
Profile is not the 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 Either a profile to be mapped or a mapped profile

Profile Table appears more than once in the profile mapping file.
3.3.5 Exporting Plates

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
in a Catalogue definition. Some holes and negative primitives can be transferred from the
design. See next section.
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 there any geometry?
• Is the height valid?
• Is it justified correctly?
• Does it have a valid material?
• Are there enough vertices?
If any of the above criteria is not satisfied, the plate does not get exported in the SDNF
output file.

Exporting to SDNF
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 transfer 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.
Although both plates and holes are supposed to have a clockwise definition (right hand
screw rule) for their boundaries in either PDMS or in the SNDF file, the interface must be
able to cope with either clockwise or anti clockwise directions. In exporting plates we
convert vertex order to satisfy the right-hand screw rule.
Complex Plates (Type 1)

Plates with curved and straight segments to their boundaries can be transferred both to and
from PDMS. Because of the difference between PDMS and SDNF boundary definitions,
vertices will stand a high chance of being created in different places. Further, in order to
recreate the shape, there may be a different number of vertices in the boundary. This makes
it very difficult to compare the boundaries, especially on import.
In order to assist the transfer of these complex shapes, the vertices are given a type code
as a design parameter. This code will indicate whether the following boundary segment is
straight, an arc, or whether the vertex is a created one not contained in the SDNF file.
Complex Plates (Type 2 - Circular Ones)

Circular plates in PDMS are identified by the number of vertices, the geometry and possibly
the vertex type codes. There is no short-hand definition of a circular plate in PDMS. As a
result, a certain amount of geometric testing is involved in identifying and exporting circular
plates. The interface recognises only 4 or 5 point circles, where the 5th point is a duplicate
of the first point.

No geometry information - No PLOO element. Plate cannot be exported.

Not exported
Plate too thin - Thickness less than user defined minimum. Plate not
Not exported exported.
Not enough vertices - Fewer than 3 vertices. Cannot define valid geometry so
Not exported Plate is not exported.
No material information - Cannot determine material properties for member. A

Not exported matching set of :SDNFMGRADE and Matref cannot be
determined.

Exporting to SDNF
No material match for nnnn Unknown material. :SDNFMGRADE cannot be matched

with a material in the Properties database.
No material property match As above
Inconsistent material The element's MATR and :SDNFMGRADE attributes are

specification not consistent.
Multiply defined entries in Either a material to be mapped or a mapped profile

Material Table appears more than once in the material mapping file.
No match for material The material is not in the material mapping file.
Syntax Error Other, less specific, errors.
Unrecognised Parse 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 will also
be output.
3.3.6 Transferring Holes

There is a limitation as to which holes are exported. Only secondary > PLOO boundaries (at
PDMS12.0 and beyond) and NXTR elements can be handled. PLOOs are full depth
penetrations: partial penetrations can be modelled using NXTR elements. Circular
boundaries of holes and indentations can be imported and exported if recognised as such,
by having 4 unique fillet vertices.
On import vertices in boundaries are given a DESP value according to the list below.
PVTLastPoint 0
PVTStraight 1
PVTArc 2
PVTFillet 3
PVTCircle 4
Using these values we may be able to detect specific shapes, such as circles, ellipses, etc.
A message will be output when the export process ignores non loop-based negative
primitives. This is because it will be difficult to determine the geometric intersection with the
PANEL, especially if the primitive axis is not perpendicular to the plate plane. In the future it
may be possible to handle some of them, but only within tight geometrical constraints.
Negative boxes and cylinders could be transferred only if a principal axis is parallel to the
plate's normal. This means that the cylinder's Z-axis, and any of the box's X, Y or Z-axis
must be parallel to the plate normal. We even have to limit NXTR elements those with an

Exporting to SDNF
extrusion vector parallel to the panel plane normal. We are not exporting the following
negatives:
NBOX NPOLYH NCYL NSLC NSNO

NDIS NCON NPYR NCTO NRTO
NXTR NREV
Imported holes will be either NXTR or PLOO elements. A full penetration will be a PLOO,
and a partial penetration will be an NXTR.
Any other negatives will not be compared or merged on import. Other pre-existing negatives
will be just moved and updated to maintain their original position and orientation.
3.3.7 Exporting Connections

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.

Exporting to SDNF
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.

Illegal or unset 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

Not exported exported. There is probably something more
fundamentally wrong with your model.
3.4 Testing Export

The following test can be performed after installing the AVEVA OpenSteel 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 PDMS (Series 12).
3.4.1 Initial Configuration

Enter DESIGN.
Set the test project variables:
Project: TST
User Name/Password: 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 > Structures > Beams & Columns from the General Application menu
This displays the Beams & Columns Application menu.
To display the Drawlist, right-click on the Drawlist button and select Drawlist from the
pop-up menu.

Exporting to SDNF
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 Add CE to add it to the Drawlist, answering YES to the
question "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 > Isometric > Iso 3.
The user can add the border sliders to the view window using the View > Settings >
Borders menu option.
3.4.2 Preparing to Export

On the User Beams & Columns Utilities form select Export>(d) AVEVA OpenSteel which
will bring up the main AVEVA OpenSteel Export form.
On this form and associated forms, fill in the details prior to Export.
Target Information Form

Click the Target information button on the AVEVA OpenSteel - Export form to display the
Export Target Information form.

Exporting to SDNF
Select the Auto 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 OpenSteel - Export form to display the
Export Information form.
In the output file name field enter "SDNF-Test.sdn"
Check that the SDNF file header (Packet 00) is coming from /SDNF-CONFIG-DEMO-
SYSTEM. Use the navigator and browser if necessary.
Select which SDNF Packets to export: Packet 10 (Straight), Members + End
Connections and Packet 20 (Plates). Select SDNF version 3.0.
Run Information Form

Click the Run information button on the AVEVA OpenSteel - Export 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.
The Main Export Form

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

Exporting to SDNF

Exporting to SDNF
3.4.3 Creation of Export File

On the AVEVA OpenSteel - Export 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 to

Exporting to SDNF
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 Checking the SDNF Output File

Compare the SDNF-Test.sdn file produced with the one supplied in the test/results/export
directory.

Import from SDNF
4 Import from 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 OpenSteel - Import 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 OpenSteel - Import form.

Import from SDNF
4.1 Source Information

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 OpenSteel - Import form to display the Import Source Information form.
The interface requires at least two external mapping tables for each Source Package to
check that the design can accept the data. It also may use the Profile Orientation and/or the
Unicode mapping table if necessary. The mapping tables are for the Steel Profiles,
Materials, Unicode text string and for mapping the Profile orientations between the Neutral
File and DESIGN. The section on user customisation in the Configuration 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 Configuration 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 set of mapping tables to map between SDNF and PDMS for a
particular steel fabricator, for example. Or the user can have a similar set 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
OpenSteel Configuration Guide for details about the format of these mapping files.
There are two main options on this form: Auto and Manual. These can be activated by
selecting the appropriate toggle button on the left hand side of the form.
The Auto option causes the interface to select automatically the 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 from SDNF
Import process, the Auto flag will cause the correct mapping files 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 other buttons, which are initially greyed out for the Auto
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 or Unicode 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% 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 entered on the Source Information form, click OK and it
will update the interface variables. Clicking CANCEL will remove the form, leaving the

Internal error Internal lists are not in step.
Cannot find suitable Internal mapping files not found.

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

Import from SDNF
Not a suitable Mapping Incorrect format of file, or empty file, or wrong Source
Table File Package.
Bad Map File Mapping file is not correct format. Possibly it is from another
operating system.
Error on OpenSteel The user has entered incorrect data on the file browser form.
File Browser form
4.2 Import Information

The Import Information form contains information about the actual Import process. Click
the Import information button on the AVEVA OpenSteel - Import form to display the
Import Information form.
The user either types 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.
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

Import from SDNF
PDMS format, e.g. %ENVVAR% being the PDMS representation of the ENVVAR
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
Auto 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 form, if they are active, the user can select
whether to import Packet 10 (Linear Members), Packet 60 (Curved Members) and/or
Packet 20 (Plates) or Packet 22 (Holes).
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!

Import from SDNF
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

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 everything.
Cannot autodetect Source If the AUTO option is on, the header of the Input file does
Package not contain the Source Package information. The
mapping table information has to be set by hand.
4.2.1 Auto-detection of SDNF Formats

The system can automatically detect which version of the file the user is inputting and set
the import drop down list accordingly.
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.
-- Default SDNF file format
-- currently |2.0| or |3.0|
!!SDNFSDNFVersion = |3.0|
The user can inspect the file header as before and an added line will show which SDNF
version it has found.

Import from SDNF
If the user changes the version setting, the system 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 because the Packet 0
records are different.
4.3 Run Information

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
Verbose messages. Click the Run information button on the AVEVA OpenSteel - Import
form to display the Import Information form.
As part of the Import process a reference model is constructed against which comparisons
will be made. The Save Reference Model button allows the user to keep this. Otherwise it
will be deleted on completion of the Import process.

Import from SDNF
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 and Curved Members and
Plates between the existing model data and the imported model data. The default AVEVA
OpenSteel 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.
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

Import from SDNF
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? 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.
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 Import Form

On the Import 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 area. At this point the user will be asked 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 from File takes a merge command file produced during the 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.

Import from SDNF
This is a very quick option and there are no checks, except what the user wants to do it.

Bad element type The user is not trying to store imported data at a SITE,
ZONE or STRU element.
4.5 Import and Cancel

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 OpenSteel Import form from the screen.
Import executes the Import process. As it proceeds the user is kept informed of the
progress.
4.6 Import Form Bar Menu

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 identify new, changed and deleted items in the model.
4.7 Import Process

After clicking OK the fields in the form are checked for validity:
• Is the storage location valid?
• Is there a valid input file?
• Do we need to convert the file across platforms?
• Are the Profile and Material mapping files valid for the Source Package as 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.

Import from SDNF
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.
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 the current AVEVA

Import from SDNF
PDMS session. The user cannot use a file from a previous OpenSteel session as the
Import data may be incorrect.
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 OpenSteel - Import 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.

Import from SDNF
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 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 identify it. The interface will also navigate to the item in
the database and leave the user there to perform any queries or operations.

File does not exist Somehow there is no log file Are there issues regarding
access rights to the %PDMSWK% directory?
Input file name not Something strange here. The name of the Design macro
specified 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?
4.8 Comparison and Merging Processes

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

Import from SDNF
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
performed if the user is sure of the end result. It is advised that the user Compares the
models first and inspect the results 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.
If the target area is empty, the Compare/Merge processes are bypassed which can be a lot
faster when importing large amounts of data.
4.8.1 The Comparison Process

There are three conditions the AVEVA OpenSteel looks for:
• items in the imported file that are not in the original model - Added items;
• items in the original model that are not in the imported file - Deleted items;
• items that it can match between the imported file and the original model and 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.

Import from SDNF
It is clear from the above diagram that the interface supports partial model transfer as it just
identifies 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
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 enhanced 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 Linear Members

The following data attributes are compared between the original model and the reference
model:
• Start and end of Pline defined by Cardinal Point
• Orientation and Beta angle
• Specification Reference
• Start and End releases
• Material grade and reference
• Hold and Paint Spec UDAs
• Fireproofing data
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 Configuration Guide.
Comparing Plates (PANE)

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

Import from SDNF
• Material grade and reference

• Hold and Paint Spec UDAs
• Panel loop height and justification
• Number of vertices
• Fireproofing data
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.
We now compare plates with holes as secondary loops (PLOO) or NXTR primitives. We can
now merge the imported model including new holes created outside of PDMS. However,
because of the complexity of the comparison process, it is difficult to compare holes
between the original and imported model. Where possible all other negative primitives
representing holes in the original model are maintained. Therefore the comparison does not
go down to the level of holes.
4.8.2 The Merging Process

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 OpenSteel 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 session must still be available. The user will be prompted for
confirmation.

Import from SDNF
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.
Additional Items
Items added to the model are recorded as such; they are indicated 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.
For example, a new STRU may be created with the name of /SDNF-NEW-DEMO-SYSTEM/
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:
/SDNF- the system prefix
NEW- identification of new element container
<mdb name>- the current MDB, e.g. /DEMO
<user name>-/ the current user name, e.g. SYSTEM
<transfer nr>. the current Transfer letter, e.g. 'A'
<revision nr> 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 Deleted Items

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 identified.
Note: An item is not actually deleted from the original model. The apparent deletion may, in
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 Configuration Guide.
As with the added items, the STRU is named out of components, thereby enabling the user
to determine at which version items may have been removed from the model.

Import from SDNF
For example, a new STRU may be created with the name of /SDNF-OLD-DEMO-SYSTEM/
A.1 under the special SITE /SDNF-OLD-DEMO-SYSTEM. The components of this name
are as follows:
/SDNF- the system prefix
OLD- identification of new element container
<mdb name>- the current MDB, e.g. /DEMO
<user name>-/ the current user name, e.g. SYSTEM
<transfer nr>. the current Transfer letter, e.g. 'A'
<revision nr> the current revision number, e.g. '1'
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 indicated as such by a change in colour.
Error and Warning Messages

WARNING: Reference SITE The reference SITE is likely to be deleted some time.
nnnn contains transient
data
Model comparison Process was successful.

completed
Failed to compare models Do they both exist?
4.9 Validation Process

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

Import from SDNF
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.
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 Sample Validity Check Log File for a sample log file.
4.10 Highlighting Changes in the Design

The user can display an OpenSteel Highlighter form from either the Import or Export
forms by the General > Highlight menu bar option. This form allows the user to identify in a
graphical window whatever they want, either according to Import date, or by Transfer/
Revision number combinations. The Select by toggle switches the form into the appropriate
mode. Both these options work from the start element selected and will indicate only those
items that are in the drawlist.
4.10.1 Highlighting by Import Date

The form below allows the user to choose what to enhance on the screen according to the
Import Date of an item.

Import from SDNF
In the Selected items box, the user can select any combination of Added, Changed, or
Deleted Items for identification, 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 locate 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.10.2 Highlighting by Version

The form below allows the user to choose what to indicate on the screen according to the
Version of an item.

Import from SDNF
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 identify 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'.
Error and Warning Messages

Bad date input 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.
4.11 Testing AVEVA OpenSteel - Import

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 Export. The user will find all the required testing material

Import from SDNF
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 Initial Configuration

Enter DESIGN.
Set the test project variables:
Project: TST
User Name/Password: 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 > Structures > Beams & Columns from the General Application bar menu
This displays the PDMS DESIGN - Beams & Columns Application bar menu.
To display the Drawlist, right-click on the Drawlist button and select Drawlist from the
pop-up menu.
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 Add CE to add it to the Drawlist, answering YES to the
question "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 > Isometric > Iso 3.
The user can add the border sliders to the view window using the View > Settings >
Borders menu option.

Import from SDNF
4.11.2 Preparing to Import

On the User Steelwork Utilities form select Import>(d) AVEVA OpenSteel to display
AVEVA OpenSteel - Import 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 OpenSteel - Import form to display the
Source Information form.
Select the Auto 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.
Import Information Form

Clicking the Import information button on the AVEVA OpenSteel - Import form to display
the Import Information form.
In the input file name field enter "%TSTIMP%/SDNF-Test.sdn"

Import from SDNF
Select which SDNF Packets to import: Packet 10 (Straight) and Packet 20 (Plates).
Run Information Form

Clicking the Run information button on the AVEVA OpenSteel - Import form to display the
Run Information form.
Select the Log File? option and choose Verbose for the message mode to get a verbose
log file.
Select the Save Reference Model? 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.
The Main Import Form

Select the SITE into which the SDNF file is to be imported. Select SITE /TEST-SDNF-
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 OpenSteel - Import forms should now look similar to this.

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

Import from SDNF
4.11.3 Importing the SDNF File

On the AVEVA OpenSteel - Import 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.

Import from SDNF
4.11.4 Comparing the Imported Model with the Original

The supplied test project also contains an original reference model /ORIG-TEST-SDNF-
INTERFACE 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 Performing a Validity Check

If the user wants to perform a validity check on the incoming data before they actually 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.

Import from SDNF

Bolt Reports
5 Bolt Reports
This section explains how to produce 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 Catalogue component name defining an anchor bolt profile contains a '-AB' suffix;
• the start (POSS) of the SCTN is the lower end of the 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 > Standard Reporting >
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 Anchor Bolt Locations

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:
AVEVA OPENSTEEL ANCHOR BOLT LOCATION REPORT

Bolt Reports
============================================================
Date of Report: 2 Jun 2010

Time of Report: 15:21
Selection from: /*
============================================================
Bolt type RefNo Easting Northing Base level

(mm) (mm) (mm)
/M20-AB =15322/225 151200 147940 100170
/M20-AB =15322/1517 151200 147940 100170
/M20-AB =15322/226 151200 148060 100170
/M20-AB =15322/1518 151200 148060 100170
/M20-AB =15322/223 155150 147925 100170
/M20-AB =15322/1515 155150 147925 100170
/M20-AB =15322/221 155150 148075 100170
/M20-AB =15322/1513 155150 148075 100170
/M20-AB =15322/211 155200 153925 100170
/M20-AB =15322/1503 155200 153925 100170
/M20-AB =15322/212 155200 154075 100170
/M20-AB =15322/1504 155200 154075 100170
/M20-AB =15322/224 155250 147925 100170
/M20-AB =15322/1516 155250 147925 100170
/M20-AB =15322/222 155250 148075 100170
/M20-AB =15322/1514 155250 148075 100170
/M24-AB =15322/185 123900 157000 100170
/M24-AB =15322/1477 123900 157000 100170
/M24-AB =15322/187 123900 163000 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 Anchor Bolt Quantities

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 OPENSTEEL ANCHOR BOLT LISTING REPORT

Bolt Reports
=============================================================
Date of Report: 2 Jun 2010

Time of Report: 15:17
Selection from: /*
=============================================================
Bolt Type Quantity

/M20-AB 16
/M24-AB 56
/M30-AB 8
unset 2

Bolt Reports

Technical Information
6 Technical Information
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 - Structural Steel Detailing Neutral File Format

This section describes the format of the version 3 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 values are enclosed in double quotation marks, '"'.
Any '"' characters within such values are replaced with '"'.
The SDNF format is described as an "ASCII" file without further description of encodings or
character sets. OpenSteel attempts to transfer non-ASCII characters where appropriate, but
will warn if any characters with their 8th bit set are written to an SDNF file.
6.1.1 Export/Import different SDNF Formats

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.2 Auto-detection of SDNF Formats

The system can automatically detect which version of the file the user is inputting and set
the import drop down list accordingly. 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.
-- Default SDNF file format
-- currently |2.0| or |3.0|
!!SDNFSDNFVersion = |3.0|

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 system 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…

[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 00 records
are different.
6.1.3 Packet 00 - Title Packet

This Packet is the SDNF file header. Only 1 Packet of this type must be included. It
describes the run for the data transfer. Its record structure is as follows:

repeat Record 11 as stated in Record 10
Note: The Issue Code (Record 8) holds the Source Package of the SDNF file.
6.1.4 Packet 10 - Linear Members

Straight 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 Location of Linear Members in 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 3 to 5 per Linear Member will determine its location. The main
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 5 is ignored completely - (2D offsets)
The Start and End cutbacks (Record 3) 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 3) is the start and end position of the
'real length of steel' located on the line described by the Cardinal Point (Record 1).
The 3D Start and End Eccentricities (Record 5) then define the real start and end of the
Cardinal Point 'Line' relative to the Node, if any. Thus, using Record 5 with Record 3, 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 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.
6.1.6 Packet 20 - Plates

Plates are represented in PDMS by PANE elements as loops on the upper and lower faces.
Each plate is represented by a variable number of records that follow:

Plate periphery defines the type of boundary: 0 is a boundary with straight edges; 1 is a
boundary with straight and curved segments; 2 is a circle. For both boundaries type 0 and 1,
there are 2 loops of vertices, one for the plate top and the other for the plate bottom. For
circular plates (type 2) there are 2 vertices representing the circle centre on the top and
bottom faces.
Each set of vertex coordinates is followed by a flag that indicates whether the following
boundary segment is straight or curved. In the case of the circular plate the "flag" is the
circle radius.
The last vertex in the boundary, a duplicate of the first, has a connection flag of 0. Straight
segments are indicated by the flag value of 1, curved segments by 2.
Below are the rules of interpretation of these fields.
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. For version 3 files, there is less of a requirement
for the vertices to follow this rule as the interface can determine the plane normal from the
separation between the loops.

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.
6.1.7 Packet 22 - Holes

The geometric description of holes is very similar to that of their owning plates. Tests are
made on import to verify that the hole does penetrate the owning plate. A hole completely
penetrating the plate is translated into a secondary PLOO. Partially penetrating holes -
depressions in the plate surface - are represented as NXTR elements.
Packet description
Each hole is represented by a variable number of records that follow:
Hole periphery defines the type of boundary: 0 is a boundary with straight edges; 1 is a
boundary with straight and curved segments; 2 is a circle. For both boundaries type 0 and 1,
there are 2 loops of vertices, one for the hole top and the other for the hole bottom. For
circular holes (type 2) there are 2 vertices representing the circle centre on the top and
bottom faces.
Each set of vertex coordinates is followed by a flag that indicates whether the following
boundary segment is straight or curved. In the case of the circular hole the "flag" is the circle
radius.
The last vertex in the boundary, a duplicate of the first, has a connection flag of 0. Straight
segments are indicated by the flag value of 1, curved segments by 2.

6.1.8 Packet 30 - Member Loading

Loading of elements is not transferred by this interface.
No loads along the member are catered for.
6.1.9 Packet 40 - Connection Details

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:
This is only a textual description. No geometry is passed here, especially concerning

sniping etc.

6.1.10 Packet 50 - Grid Packet

Grid Packets are not transferred in this interface.
6.1.11 Packet 60 - Format Definition
For the succeeding records, each arc member is represented by the 11 records that follow:
total of 11 times n records, where n is number of members from Record 2 above (376 in the
example).

6.2 Recommended SDNF File Suffix

Although it is not critical for this interface, the recommended suffix for the SDNF files is to be
'.sdn'.
6.3 SDNF File Header Information

As has been described in the Customisation 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
# data
# data
# ENDTABLE
#
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
# 20 1
# 40 0
# ENDTABLE
#
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.
If the input SDNF file has the STARTTABLE header that lists the contents of the subsequent
packets, the Import form Packet buttons will be (de)activated accordingly. If there is not this
STARTTABLE block that defines the packets contained therein, all buttons will become
active and it will be for the user to select which packets to import.
You will not be able to import Packet 22 without Packet 20, but you will be able to import
Packet 20 without holes, even if there some. Similarly, you will not be able to import Packet
40 (Connections) without either Packet 10 or Packet 60.
6.4 Member ID Numbers at 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.

On Import the components of a member ID number are stored in the NUMB attribute.
6.5 Using Linear Member Cutbacks

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 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.
-- Flag to handle a supplied trimmed model or one where
cutbacks must be used
-- |CP| = trimmed positions;
-- |WP| = worked out positions
!!SDNFModelType = |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.
1 10 0 0 "ANG" "15322/826" 0
"L60x6" "Steel, carbon" 180.0000 0 0
-287.3480 0.0000 957.8260 138100.0000 166000.0000 … 106000.0000
140796.5000 166000.0000 106808.9530 10.0000 30.0000
0.0000 0.0000
0.0000 0.0000 20.0000 0.0000 10.0000 -50.0000
0 0 0 0 0 0 0 0 0 0 0 0
In the above data the fields are interpreted as shown:
Orientation vector = ( -287, 0, 958 )
Start position = ( 138100, 166000, 106000 )
End position = ( 140796, 166000, 106809 )

Start cutback = 10
End cutback = 30
Start eccentricity = ( 0, 0, 20 )
End eccentricity = ( 0, 10, -50 )
Diagram showing each interpretation. The text below describes this diagram in more detail.
6.5.1 Exporting
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 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.

When the Use Cutbacks checkbox is checked the start and end positions 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 will be start
and/or end position of the Justification Pline and the cutbacks will be zero.

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

6.5.2 Importing
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. Any cutback values will be ignored.

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

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

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 this 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, it will cause minor problems in model versioning and comparisons.

6.7 Default Orientations

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. 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.7.1 Mirroring
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, any desired result
can be achieved just by rotations and mirroring about the Y axis.
6.8 Pline Selection Rules

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. This is later 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 Settings>Pline Rules This
will bring up a form listing the currently available rules for filtering Plines. This will be similar
to the picture below.

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.
#-- Data file containing pline rule definitions
!rule = object RULE()

!rule.name = |OpenSteel Plines|
!rule.rule = |(match( ( attrib PKEY ), 'SNF' ) gt 0)|
!rule.types = ||
!rule.description = |OpenSteel Plines with PKEY = SNF[A-N].|
!!tmpRuleArray.append(!rule)

6.8.1 Use of Pline Filters

The default drawing flags for the Plines have been changed to LEVEL 99 99, CLFLAG
TRUE and TUFLAG TRUE. In the AVEVA PDMS 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 indicating 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 UDAs
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 General Data
Name Type Len On Description

: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)
:SDNFRE/VNO INT 1 SCTN PANE SITE Transfer index(1)
:SDNFTRR/VNO TEXT 10 SCTN PANE SITE Revision Text
:SDNFEX/CLUDE LOG 1 SCTN PANE SJOI PJOI Exclude flag (f)
:SDNFSTA/TUS TEXT 10 SCTN PANE Status text
:SDNFCD/ATE TEXT 30 SCTN PANE GENSEC Date of Creation
:SDNFMD/ATE TEXT 30 SCTN PANE GENSEC Date of Modification
:SDNFCT/IME TEXT 30 SCTN PANE GENSEC Time of Creation
:SDNFCM/TIME TEXT 30 SCTN PANE GENSEC Time of Modification
:SDNFFT/HICK REAL 1 SCTN GENSEC PANE Fireproofing Thickness
:SDNFFD/ESC INT 1 SCTN GENSEC PANE Fireproofing Description
:SDNFFS/TART REAL 1 SCTN GENSEC Fireproofing Start
:SDNFFE/ND REAL 1 SCTN GENSEC Fireproofing End

6.9.2 Structural Data
Name Type Len On Description

: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
:SDNFMA/RK TEXT 24 SCTN PANE Object Mark Nr.
:SDNFEMA/RK TEXT 24 SCTN PANE External Mark
6.9.3 Project Data
Name Type Len On Description/default

: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'
:SDNFMO/DNR INT 1 SITE ZONE STRU SCTN Model Number
PANE GENSEC
: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
: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 not 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 OpenSteel Export form. It is not the final expanded list of SCTN and PANE elements
to appear in the SDNF output file.
6.10 Cross Referencing Models

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 Element created in DESIGN

When an element is created in DESIGN it gains a unique internal reference number of the
form "=<integer>/<integer>", e.g. =13/2305. On export from Design this 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
AVEVA 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 Element created outside 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.
If OpenSteel detects that there are duplicate external mark numbers as it is preparing to
export a model, the internal reference number is used in preference. This should give
OpenSteel some chance of identifying the element if it returns from the external package.
See the section regarding issues concerning entity comparison.
6.11 Cross Database Working

PDMS has the ability to split the design model across several databases, some of which
may be read only.
Exporting the model tries to update variables associated with the version management.
However, if the database is read only, a macro file is produced that should be executed

when the user does have write access to the database. This must be performed before any
import procedure is performed. The file name is built upon the string "updateVersionNos"
but with time stamp information attached so that they can be executed in chronological
sequence. An example file name might be "updateVersionNos201012593744.mac", which
was created at 09:37:44 on 25th January 2010.
Importing an existing, though modified, model is more difficult. Obviously the user must
have write access to the database. The reference site is created in the same database as
the target area specified on the import form. This will allow new items to be transferred
between the reference site and the target site using the INCLUDE command. This
command does not work across databases.
The user should ensure that the incoming data is not to be spread across databases.
If the target area is empty we bypass the Compare/Merge processes which can be a lot
faster when importing large amounts of data.
User’s of multi-write databases need to be aware that elements that are to be exported must
be claimed out prior to export. All elements that are likely to be affected by importing must
also be claimed out.
6.12 Issues Concerning Entity Comparison

Some systems do not use unique piece marks. On import, piece mark values are
transferred to the :SDNFEMARK UDA field. When OpenSteel exports them, the PDMS
reference number is put into the :SDNFMARK UDA field. Theoretically, if these are unique
between and within each system, then OpenSteel can cross refer the members between
packages. However, some packages (XSteel, for example) does not use unique piece
marks. This leads to there being multiple instances of the same piece mark within the
imported model. It then becomes impossible to use :SDNFMARK as a unique pointer to the
incoming member. Therefore, repeated imports and merging from other packages into
PDMS and comparing the differences will give wrong results. In fact, subsequent merging of
the models will give drastically wrong results. Using the memberID as an identifier is also
not reliable as this value is really dependent upon the sequence of export from the other
package. There is no other attribute or flag that can be used to uniquely identify members in
this situation. Trying to use member position as an additional discriminator would actually
hide differences, and not be any better.
This is an impossible problem to solve. When repeatedly importing into PDMS, the best
thing is to delete the old structure, or find some way to merge them.
This applies to both linear and plate members.
6.13 Transfer of Curved Members

Exporting a GENSEC with only a straight segment goes out as a Packet 10 element: with
just a curve segment it goes out as a Packet 60 element. Compound GENSECs are split on
export. Importing curves segments come in as GENSECs: straights, currently, are as
SCTNs. If they have the PDMS attributes set, we can rebuild the GENSEC as described
below.
SDNF does not have the same concept of complex curved beams as there is in PDMS.
Packet 60 arc members are just circular arcs. Therefore for export a complex curved beam
in PDMS must be split into its straight and arc segments. These are passed through to
SDNF with an annotated :SDNFMARK attribute. If the member is part of a GENSEC the
:SDNFMARK value has a suffix of ".S<n>" or ".C<n>" indicating a straight or curved

segment. The <n> indicates the segment's sequence position. These suffices allow us to
rebuild the complex GENSEC if these values are returned to PDMS from the other system.
If the distance between neighbouring segment end points is outside the tolerance limits,
OpenSteel will attempt to build a new GENSEC starting from the next unused segment. The
new GENSEC's :SDNFEMARK or :SDNFMARK attribute will have a suffix .PART<int>, from
2 upwards. No imported members will be lost. In the Compare and Merge process, this new
part will appear as an ADDED member while the original part will be indicated as having
changed, as it will have a reduced number of points.
However, if we can restore a GENSEC in PDMS it may well be different from its original as
the types of CURVE element are normalised to be THRU based curves.
New straight linear members may be replaced by GENSECs according to the
!!sdnfSCTNtoGENSEC flag. Members that are already SCTN elements in the model will not
be changed.
Comparing GENSECs is only down to the point count level on the spine. We don't
investigate the actual point attributes, except for the start and end points. We do check that
there are the same numbers of POINSP and CURVE members respectively. Any alteration
to these numbers will indicate changes. They must be inspected visually for comparisons.
The re-imported CURVE element are likely to have changed because we only import 1 type
- a THRU point, although there are 6 or 7 different types of CURVE points in PDMS, each
with different attribute combinations.
6.14 Version Numbering

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 package or client information.
Because of the fact that PDMS may be multi-user and that several user’s 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 for 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".
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 Transfer has a Letter - A...Z

2. Each Revision has a Number - 1,2,3...
3. Each SITE, SCTN and PANE has 3 UDAs attached
4. A TransferLetter e.g. 'C',
5. A RevisionNumber e.g. '2'
6. A TraRevNumber - A character-wise concatenation of the previous two, e.g. 'C.2'
6.14.1 On Transfer from Design:

1. Increment the element's TransferLetter at the SITE level, eg 'A' to 'B'.
2. Reset the SITE's RevisionNumber to '0' and generate the new TraRevNumber -> 'B.0'.
3. If an entity (SCTN or PANE) has not been transferred from PDMS before, its own
TransferLetter is set to be the owning SITE's TransferLetter. This is only done once.
6.14.2 On Transfer into Design:

1. If an entity (SCTN or PANE) has been changed or is new, set its TransferLetter to be
that of the owning SITE and note that there is at least 1 changed item.
2. Update the entity's (SCTN or PANE) RevisionNumber to be the incremented value of
that of the owning SITE, because we haven't yet changed the latter.
3. Increment the SITE's RevisionNumber, e.g. '0' to '1' if any imported entities have
changed.
6.15 Exclusions
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 Holes: SDNF does not allow the description of holes within Linear Members.
Additional data: 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.
Templates: Catalogues are not covered by SDNF. Linear or Arc members and Plates
contained in Templates or Groups will be transferred on export. There is no facility for
constructing a new Template or Group on import. Elements that are in pre-existing
Templates or Groups will be compared and merged, but new elements will not be placed in
the same container.
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.16 Issues
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 user’s 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.
The double quote character “ in text fields, particularly in profile spec names is not allowed.
This can cause problems with imperial sized items in the catalogue that use the character to
indicate inches. It is not allowed in ANY text fields.
6.16.1 Units
This is a statement of how OpenSteel handles units.
1. SDNF has a minimal set of unit definitions. ("feet", "meters", "inches","millimeters")
2. OpenSteel exports in mm, i.e. the units exported in the SDNF file are mm.
3. OpenSteel imports all units from SDNF internally. It reads any SDNF file unit (according
to the "standard"), but...
4. OpenSteel then converts the SDNF input units to mm prior to writing an input "macro",
so the model in PDMS is therefore in mm.
5. To support this, the OpenSteel environment, switches PDMS to MM DIST, and, at
PDMS12.1, UNITS DEGREES units prior to export and import.
6. Because of the way PDMS12.1 handles UNITS, the original units cannot be restored to
be precisely what they were before.
7. Therefore, after an export or import transaction, the units will be set to MM DIST/MM
BORE/UNITS DEGREES.
OpenSteel attempts to keep the behaviour of the system as consistent as possible across
versions of PDMS. There are very few cases of behaviour that are specific to particular
versions of PDMS. Before PDMS12.0, PANE elements were not permitted to have
secondary PLOO elements representing holes in the owning plates. Holes are always
imported as NXTR elements because OpenSteel does not do any shape recognition. This
highlights a possible issue in exporting a PDMS12.0 model and re-importing. While at
PDMS12.0, a secondary PLOO would represent a hole, this would have to be represented
on import as a negative extrusion, NXTR. So even round tripping data at PDMS12.0 and
beyond, will cause secondary PLOO elements as well as other negative primitives, to be
converted to NXTR elements.
When importing into an empty area and using the "Import Packet 10 as GENSECs" option,
Packet 10 (straight members) may not be converted to GENSECS. This often occurs with a
file that was previously exported from another PDMS model. The :SDNFEMARK attribute on
the imported element may refer to an element with the same database reference number in

the current model. Do not use the option to convert all Packet 10 members into GENSECs
when importing a SDNF file containing elements that originated in PDMS.
6.16.2 Possible License Issues

If, for any reason you suspect that there may be an issue with the system getting a license
from the license server, you can try running the executable, that is either pdms2sdnf.exe or
sdnf2pdms.exe, in a black command window. The executable is to be found in the
C:\AVEVA\Plant\Design\OpenSteel2.3\exe folder. By typing the command below in the black
window, you will see if the license can be obtained, or not.
C:\AVEVA\Plant\Design\OpenSteel2.3\exe\pdms2sdnf.exe


Sample SDNF File
A Sample SDNF File
This appendix gives a brief extract of an SDNF file produced by the AVEVA OpenSteel
interface.
#
# Target Contractor: Target Contractor
#
# STARTTABLE PACKET
# 10 281
# 20 6
# 22 0
# 40 65
# 60 0
# ENDTABLE
#
#
# STARTTABLE ANYANYCON
# Default Connection
# BP macro BasePlate
# TP TP
# EP EP
# EPF EPF
# MCT MCT
# MCB MCB
# FPWB FPWB
# FPWC FPWC
# ACD ACD
# SHE SHE
# RECT RECT
# ENDTABLE
#
#
# STARTTABLE ANYMAT
# STRUCAD %SDNFMAIN%/maps/StruCad/StruCadMat.map
# XSTEEL %SDNFMAIN%/maps/XSteel/XSteelMat.map
# STEELCAD %SDNFMAIN%/maps/SteelCad/SteelCadMat.map
# PDMS %SDNFMAIN%/maps/PDMS/PDMSMat.map
# FRAMEWORKS %SDNFMAIN%/maps/FrameWorks/FrameWorksMat.map
# ENDTABLE
#
#
# STARTTABLE ANYORI
# STRUCAD %SDNFMAIN%/maps/StruCad/StruCadOri.map
© Copyright 1999 to current year. A:1 2.3

Sample SDNF File
# XSTEEL %SDNFMAIN%/maps/XSteel/XSteelOri.map
# STEELCAD %SDNFMAIN%/maps/SteelCad/SteelCadOri.map
# PDMS %SDNFMAIN%/maps/PDMS/PDMSOri.map
# FRAMEWORKS %SDNFMAIN%/maps/FrameWorks/FrameWorksOri.map
# ENDTABLE
#
#
# STARTTABLE ANYPRF
# STRUCAD %SDNFMAIN%/maps/StruCad/StruCad.map
# XSTEEL %SDNFMAIN%/maps/XSteel/XSteel.map
# STEELCAD %SDNFMAIN%/maps/SteelCad/SteelCad.map
# PDMS %SDNFMAIN%/maps/PDMS/PDMS.map
# FRAMEWORKS %SDNFMAIN%/maps/FrameWorks/FrameWorks.map
# ENDTABLE
#
#
# STARTTABLE ANYSTD
# EUR Euronorm
# BRI British
# AME American
# GER German
# CAN Canadian
# JAP Japanese
# DIN European
# ENDTABLE
#
#
# STARTTABLE STATUS
# 0 Undefined
# 1 Fixed
# 2 Provision
# 3 Other
# ENDTABLE
#
#
# STARTTABLE CLASS
# 0 Undefined
# ENDTABLE
#
#
# STARTTABLE ANYTSTCON
# Default Connection
# BP macro BasePlate
# TP TP
# EP EP
# EPF EPF
# MCT Moment Connection Top
# MCB Moment Connection Bottom
# FWG FWG
# FPWB FPWB
# FPWC FPWC
# ACD ACD
# SHE SHE

Sample SDNF File
# RECT RECT
# ENDTABLE
#
#
# STARTTABLE TSTMAT
# STRUCAD %SDNFMAIN%/maps/StruCad/StruCadMat.map
# XSTEEL %SDNFMAIN%/maps/XSteel/XSteelMat.map
# STEELCAD %SDNFMAIN%/maps/SteelCad/SteelCadMat.map
# PDMS %SDNFMAIN%/maps/PDMS/PDMSMat.map
# FRAMEWORKS %SDNFMAIN%/maps/FrameWorks/FrameWorksMat.map
# ENDTABLE
#
#
# STARTTABLE TSTPRF
# STRUCAD %SDNFMAIN%/maps/StruCad/StruCad.map
# XSTEEL %SDNFMAIN%/maps/XSteel/XSteel.map
# STEELCAD %SDNFMAIN%/maps/SteelCad/SteelCad.map
# PDMS %SDNFMAIN%/maps/PDMS/PDMS.map
# FRAMEWORKS %SDNFMAIN%/maps/FrameWorks/FrameWorks.map
# ENDTABLE
#
#
# STARTTABLE TSTSTD
# EUR Euronorm
# BRI British
# AME American
# ENDTABLE
#
Packet 00
"SDNF Version 3.0"
"Engineering Firm Id"
"Client Id"
"Structure Id"
"Project Id"
"12 Jan 2010" "15:01"
16 "PDMS"
"Design Code"
0
Packet 10
"MM" 281
00100001 8 0 0 "BEAM" "15322/100" 0
"HE300A" "Steel, carbon" 0.0000 0 0
0.0000 0.0000 1.0000 112000.0000 159822.3830 115000.0000
112000.0000 160177.6170 115000.0000 0.0080 0.0080
0.0000 0.0000
0.0000 0.0080 0.0000 0.0000 -0.0080 0.0000
0 0 0 0 0 0 0 0 0 0 0 0
0 "" 0 "12 Jan 2010" "15:01" "12 Jan 2010" "15:01" 0 0
0 0 0 0 0 0 0 0 0 0 0 0
0 0 0.0000 0 0 0.0000 0.0000
0 0 0 0 0 0
00100002 10 0 0 "SCTN" "15322/1003" 0
"HANDRAIL" "Steel, carbon" 0.0000 0 0
0.0000 0.0000 1.0000 137050.0000 179400.0000 105275.0000

Sample SDNF File
137050.0000 182100.0000 105275.0000 100.0000 0.0000

0.0000 0.0000
-100.0000 100.0000 -1025.0000 0.0000 0.0000 0.0000
0 0 0 0 0 0 0 0 0 0 0 0
0 "" 0 "6 Oct 2009" "10:36" "6 Oct 2009" "10:36" 0 0
0 0 0 0 0 0 0 0 0 0 0 0
0 0 0.0000 0 0 0.0000 0.0000
0 0 0 0 0 0
[more Straight Linear Members]
00100280 1 0 0 "ANG" "15322/998" 0

"L80x8" "Steel, carbon" 0.0000 0 0
0.0000 -0.6843 0.7292 148200.0000 160105.0000 100368.4380
148200.0000 165993.4380 105895.0000 143.9272 4.7847
0.0000 0.0000
0.0000 -105.0000 -98.4380 0.0000 6.5620 0.0000
0 0 0 0 0 0 0 0 0 0 0 0
0 "" 0 "12 Jan 2010" "15:02" "12 Jan 2010" "15:02" 0 0
0 0 0 0 0 0 0 0 0 0 0 0
0 0 0.0000 0 0 0.0000 0.0000
0 0 0 0 0 0
00100281 10 0 0 "BEAM" "15322/999" 0
"HE220A" "Steel, carbon" 0.0000 0 0
0.0000 0.7071 0.7071 148200.0000 165895.0000 107105.0000
148200.0000 160105.0000 112895.0000 148.4924 148.4924
0.0000 0.0000
0.0000 105.0000 -105.0000 0.0000 -105.0000 105.0000
0 0 0 0 0 0 0 0 0 0 0 0
0 "" 0 "12 Jan 2010" "15:02" "12 Jan 2010" "15:02" 0 0
0 0 0 0 0 0 0 0 0 0 0 0
0 0 0.0000 0 0 0.0000 0.0000
0 0 0 0 0 0
Packet 20
"MM" "MM" 6
00100282 -1 0 0 "PANE" 1
"15322/1015" "Steel, carbon" 25.0000 7 0.0 1
137049.9769 179400.0083 104223.6870 1
137049.9769 182100.0083 104224.5820 1
134574.9779 182100.0073 104226.8720 1
134574.9779 181875.0073 104226.7970 1
134349.9779 181875.0073 104227.0050 1
134349.9779 179400.0073 104226.1850 1
137049.9769 179400.0083 104223.6870 0
137050.0000 179400.0000 104248.6870 1

137050.0000 182100.0000 104249.5820 1
134575.0010 182099.9990 104251.8720 1
134575.0010 181874.9990 104251.7970 1
134350.0010 181874.9990 104252.0050 1
134350.0010 179399.9990 104251.1850 1
137050.0000 179400.0000 104248.6870 0
0 "" 0 "12 Jan 2010" "15:02" "12 Jan 2010" "15:02" 0 0

Sample SDNF File
0 0 0
0 0 0.0000 0 0
0 0 0 0 0 0
[more Plates]
00100288 0 0 0 "PANE" 1
"15322/722" "Steel, carbon" 100.0000 5 0.0 1
151320.0000 214050.0000 100170.0860 1
155080.0000 214050.0000 100169.6720 1
155079.6090 214050.0000 104010.0000 1
151319.9370 214050.0000 104010.0000 1
151320.0000 214050.0000 100170.0860 0
151320.0000 213950.0000 100170.0860 1

155080.0000 213950.0000 100169.6720 1
155079.6090 213950.0000 104010.0000 1
151319.9370 213950.0000 104010.0000 1
151320.0000 213950.0000 100170.0860 0
0 "" 0 "12 Jan 2010" "15:02" "12 Jan 2010" "15:02" 0 0
0 0 0
0 0 0.0000 0 0
0 0 0 0 0 0
Packet 40
65
293 120 1 "Base Plate 250 250 0 0"
294 118 1 "Base Plate 250 250 0 0"
303 128 1 "Base Plate 250 250 0 0"
307 139 1 "Base Plate 150 250 0 0"
308 138 1 "Base Plate 300 300 0 0"
[more Connections]
690 203 2 "Moment Connection Bottom"

702 269 1 "FWE"
708 172 2 "Moment Connection Top + Bottom"

Sample SDNF File

Sample Export Log File
B Sample Export Log File
This appendix gives an example Export Log file.

(Error) - SCTN 2 of SBFRAMEWORK /SB3/PB1/5/ELV4.2 - Zero
length Linear Member - Not exported.
(Error) - SCTN 7 of SBFRAMEWORK /SB3/STR1/A/ROW - Illegal or
unset SPRE - Not exported.
(Error) - PANEL 1 of SBFRAMEWORK /SB3/PB1/7/ELV4.2 - Plate too
thin - Not exported.
AVEVA OpenSteel (pdms2sdnf v2.X) (<Build Date>)

Copyright 1974 to current year. AVEVA Solutions Limited and
its subsidiaries. All rights reserved.
START PROCESSING at <run date time>
(Warning) - Line Number[ 3] Multiply defined entries in
Material Table unset maps to MaterialB
The following materials were mapped

Steel, carbon has 287 occurrences
All materials were mapped
The following profiles were mapped

HE220A has 43 occurrences
The following profiles were not mapped

CAGEF500 has 1 occurrences
Earthing-Boss-Dia-40 has 1 occurrences
HANDRAIL has 6 occurrences
HE180B has 2 occurrences
© Copyright 1999 to current year. B:1 2.3

Sample Export Log File

HL1100R has 1 occurrences
HP200x54 has 1 occurrences
INP160 has 3 occurrences
L60x6 has 12 occurrences
LADDER_TS has 1 occurrences
M20-AB has 8 occurrences
OD193.7x5 has 4 occurrences
OD323.9x6.3 has 2 occurrences
RHS200x200x8 has 3 occurrences
ST-STAN has 2 occurrences
T140 has 2 occurrences
TRED has 22 occurrences
UNP180 has 2 occurrences
All mapped profiles were in the specified standards
All mapped profiles were in the default standard

END PROCESSING at 10:30:46
======================================
Files used...
=============
Output file : E:\OpenSteel\sdnfOut.sdn
Profile Mapping file :
W:\PD003\OpenSTEEL\deploy\maps\FrameWorks\FrameWorks.map
Material Mapping file :
W:\PD003\OpenSTEEL\deploy\maps\FrameWorks\FrameWorksMat.map
Standards Table file :
W:\PD003\OpenSTEEL\deploy\test\tstdflts\OSDE\sdnftststd.map
Profile Orientation file:
W:\PD003\OpenSTEEL\deploy\maps\FrameWorks\FrameWorksOri.map
© Copyright 1999 to current year. B:2 2.3

Sample Import Log Files
C Sample Import Log Files
This appendix shows sample log files from an Import process according to the mode
specified.
C.1 Brief Format

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
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 Linear Members

Linear members are either straight or curved. Modifications to straight members are detailed
as below
LINMEM <mark> <state> <point> <hold> <pspec> <size>…
…<material> <rotation> <start> <end> <startRel> <endRel>…
…<fire_thick> <fire_desc> <fire_type> <fire_start> <fire_end>
e.g.
LINMEM =1234/5678 C Y Y N Y Y N Y Y N Y N N N 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.
For curved members the member type is CURMEM but the attributes inspected for
comparison are the same. The individual internal points along the SPINE are not compared.
C.1.2 Plates
PLATE <mark> <state> <point> <hold> <pspec> <height>…
…<material> <pos> <ori> <vertexCount> <changedVertex>…
…<fire_thick> <fire_desc> <fire_type>
The rules for values in each of the above fields are as for the Linear Members.
Note that holes themselves are not compared. This is principally because the transfer is
incomplete anyway. OpenSteel only transfers PLOO and NXTR based penetrations. All
other negative primitives cannot be transferred at the moment.
Below is a sample log file in brief format following an Import:
© Copyright 1999 to current year. C:1 2.3

AVEVA OpenSteel (sdnf2pdms v2.X) (<Build date>)

Copyright 1974 to current year. AVEVA Solutions Limited and its
subsidiaries. All rights reserved.
START PROCESSING at <date time run>


All profiles were mapped
The following profiles were not in the specified standards


======================================
LINMEM =15322/447 C Y N N N N Y N N N N N N N N N
LINMEM =15322/449 C N N N N N Y N N N N N N N N N

PLATE =15322/1015 C N N N N N N Y N Y N N N
PLATE =15322/1104 C N N N N N Y N N Y N N N
PLATE =15322/296 C N N N N N Y Y N Y N N N
PLATE =15322/414 C N N N N N Y Y N Y N N N
LINMEM =15322/423 D N N N N N N N N N N N N N N N
LINMEM =15322/878 D N N N N N N N N N N N N N N N
PLATE =15322/553 D N N N N N N N N N N N N
Files used...
=============
Input file : E:\OpenSteel\sdnfOut.sdn
Profile Mapping file : W:\PD003\OpenSTEEL\deploy\maps\PDMS\PDMS.map
Material Mapping file : W:\PD003\OpenSTEEL\deploy\maps\PDMS\PDMSMat.map
Profile Orientation file: W:\PD003\OpenSTEEL\deploy\maps\PDMS\PDMSOri.map
C.2 Verbose Format

Below is a verbose log file of the same Import as above:
Copyright 1974 to current year. AVEVA Solutions Limited and its
subsidiaries. All rights reserved.
(Warning) - Line Number[ 3090] Ignoring packet type 40






(Warning) - END PROCESSING at 10:28:54
======================================
CHANGES to mapped entities in /TEST-SDNF-INTERFACE
SCTN =15322/447 in /TEST-SDNF-INTERFACE

Rotation 'S 57.2932 D WRT /*' changed from 'N 57.2932 U WRT /*'
Just 'TOAY' changed from 'TOAX'
Rotation 'N 57.3314 D WRT /*' changed from 'S 57.3314 U WRT /*'
Rotation 'E WRT /*' changed from 'W WRT /*'
Rotation 'S 32.925 D WRT /*' changed from 'N 32.925 U WRT /*'
PANE =15322/1015 in /TEST-SDNF-INTERFACE

Ori 'Y is E 0.053013 D WRT /* and Z is W 19.7106 N 89.9437 D WRT
/*' changed from 'Y is W 0.053 U WRT /* and Z is E 19.721 S 89.9437
U WRT /*'
Vertex 1 'E 134350.001 N 179399.999 U 104251.185 WRT /*'
changed from 'E 137050 N 179400 U 104248.687 WRT /*'
Vertex 2 'E 134350.001 N 181874.999 U 104252.005 WRT /*'
changed from 'E 134350.001 N 179399.999 U 104251.185 WRT /*'
Vertex 3 'E 134575.001 N 181874.999 U 104251.797 WRT /*'
Vertex 4 'E 134575.001 N 182099.999 U 104251.872 WRT /*'


Vertex 5 'E 137050 N 182100 U 104249.582 WRT /*' changed from
'E 134575.001 N 182099.999 U 104251.872 WRT /*'
Vertex 6 'E 137050 N 179400 U 104248.687 WRT /*' changed from
'E 137050 N 182100 U 104249.582 WRT /*'
PANE =15322/1104 in /TEST-SDNF-INTERFACE
Position 'E 144350 N 169625 U 104250 WRT /*' changed from 'E
144450 N 172000 U 104250 WRT /*'
Vertex 1 'E 144350 N 172100 U 104250 WRT /*' changed from 'E
144350 N 169625 U 104250 WRT /*'
144350 N 172100 U 104250 WRT /*'
147050 N 172100 U 104250 WRT /*'
147050 N 169400 U 104250 WRT /*'
144575 N 169400 U 104250 WRT /*'
144575 N 169625 U 104250 WRT /*'
===========================
CHANGES >>>> 70 detected
ADDITIONS to mapped entities in /TEST-SDNF-INTERFACE
===========================
ADDITIONS >>>> 0 detected
DELETIONS to mapped entities in /TEST-SDNF-INTERFACE
LINMEM =15322/423 has been deleted.

LINMEM =15322/878 has been deleted.
PLATE =15322/553 has been deleted.
===========================
DELETIONS >>>> 3 detected
Files used...
=============
Input file : E:\OpenSteel\sdnfOut.sdn
Profile Mapping file :
W:\PD003\OpenSTEEL\deploy\maps\PDMS\PDMS.map
Material Mapping file :
W:\PD003\OpenSTEEL\deploy\maps\PDMS\PDMSMat.map
Profile Orientation file:
W:\PD003\OpenSTEEL\deploy\maps\PDMS\PDMSOri.map


Sample Validity Check Log File
D Sample Validity Check Log File
This appendix shows a sample log file from an Import validity checking process to check for
duplicate mark numbers.
Copyright 1974 to current year. AVEVA Solutions Limited and
its subsidiaries. All rights reserved.

Gold, pure cast has 2 occurrences

© Copyright 1999 to current year. D:1 2.3

Sample Validity Check Log File



(Warning) - END PROCESSING at 10:30:46
======================================
Checking GLOBAL Duplicate Mark Numbers in /*
Mark Number ( 12345 ) found on =15322/3358

and =15322/3359
Mark Number ( 67890 ) found on =15322/3360
and =15322/3443
===========================
GLOBAL Duplicate Mark Numbers >>>> 2 detected
Files used...
=============
Input file : Z:\Aveva3-
010\Dev\osde150\test\results\import\SDNF-Test.sdn
Profile Mapping file : Z:\Aveva3-
010\Dev\osde150\maps\PDMS\PDMS.map
Material Mapping file : Z:\Aveva3-
010\Dev\osde150\maps\PDMS\PDMSMat.map
Standards Table file : Z:\Aveva3-
010\Dev\osde150\test\tstdflts\OSDE\sdnftststd.map
Profile Orientation file: Z:\Aveva3-
010\Dev\osde150\maps\PDMS\PDMSOri.map
© Copyright 1999 to current year. D:2 2.3

Index
A G
Anchor Bolt Glossary . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
locations . . . . . . . . . . . . . . . . . . . . . . 5:1 Grid Packet
quantities . . . . . . . . . . . . . . . . . . . . . 5:2 Packet 50 . . . . . . . . . . . . . . . . . . . . 6:10
B I
Bolt Reports . . . . . . . . . . . . . . . . . . . . . . 5:1 Import Form . . . . . . . . . . . . . . . . . . . . . . 4:9
Import Information . . . . . . . . . . . . . . . . . 4:4
C Import Log Files
sample . . . . . . . . . . . . . . . . . . . . . . . C:1
Cardinal Points . . . . . . . . . . . . . . . . . . . 6:19 Import Process . . . . . . . . . . . . . . . . . . . 4:10
Comparison and Merging Processes . . 4:13
Connection Details L
Packet 40 . . . . . . . . . . . . . . . . . . . . . 6:9
Connections Linear Member
export . . . . . . . . . . . . . . . . . . . . . . . 3:16 using cutbacks . . . . . . . . . . . . . . . . 6:13
Cross Referencing Models . . . . . . . . . . 6:26 Linear Members
export . . . . . . . . . . . . . . . . . . . . . . . 3:11
D Packet 10 . . . . . . . . . . . . . . . . . . . . . 6:5
Default Orientations . . . . . . . . . . . . . . . 6:20 M

E Member Loading
Packet 30 . . . . . . . . . . . . . . . . . . . . . 6:9
Export
Process . . . . . . . . . . . . . . . . . . . . . . 3:9 O
Export Form . . . . . . . . . . . . . . . . . . . . . . 3:8
Export Information . . . . . . . . . . . . . . . . . . 3:4 OpenSteel Export
Export Log File testing . . . . . . . . . . . . . . . . . . . . . . 3:17
sample . . . . . . . . . . . . . . . . . . . . . . . B:1
P
Plates
© Copyright 1999 to current year. Index page 1 2.3

export . . . . . . . . . . . . . . . . . . . . . . . 3:13
Pline Selection Rules . . . . . . . . . . . . . . 6:22
R
Run Information . . . . . . . . . . . . . . . 3:7, 4:7
S
SDNF
export . . . . . . . . . . . . . . . . . . . . . . . . 3:1
file header information . . . . . . . . . . 6:11
import . . . . . . . . . . . . . . . . . . . . . . . . 4:1
recommended file suffix . . . . . . . . . 6:11
sample file . . . . . . . . . . . . . . . . . . . . A:1
Source Information . . . . . . . . . . . . . . . . . 4:2
T
Target Information . . . . . . . . . . . . . . . . . . 3:2
Technical Information . . . . . . . . . . . . . . . 6:1
U
UDAs . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:24
V
Validity Check Log File
sample . . . . . . . . . . . . . . . . . . . . . . .D:1
Verbose Format . . . . . . . . . . . . . . . . . . .C:3
Version Numbering . . . . . . . . . . . . . . . . 6:28
© Copyright 1999 to current year. Index page 2 2.3


OpenSteel User Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenSteel User Guide

Uploaded by

Copyright:

Available Formats

OpenSteel

Date Version Comments / Remarks

OpenSteel User Guide

Import from SDNF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1

© Copyright 1999 to current year. i 2.3

Import Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4

Bolt Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1

Technical Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1

© Copyright 1999 to current year. ii 2.3

Packet 60 - Format Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:10

Sample SDNF File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A:1

© Copyright 1999 to current year. iii 2.3

Sample Validity Check Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D:1

© Copyright 1999 to current year. iv 2.3

Glossary explains terms used in this manual

Exporting to SDNF explains how to export a steel structure to an SDNF file

Technical Information contains technical information

Sample Export Log File gives an example Export Log file

© Copyright 1999 to current year. 1:1 2.3

© Copyright 1999 to current year. 1:2 2.3

This section explains terms used in this manual.

Cardinal Point An SDNF concept representing points of significance on the

External Package The system with which this interface is communicating. It

Linear Member An SDNF Entity mapped to the Design Section (GENSEC)

Plate An SDNF Entity mapped to the Design Panel (PANE)

PML/F&M The AVEVA PDMS programmable macro language,

© Copyright 1999 to current year. 2:1 2.3

© Copyright 1999 to current year. 2:2 2.3

© Copyright 1999 to current year. 3:1 2.3

3.1 Target Information

© Copyright 1999 to current year. 3:2 2.3

Error and Log File Messages

Internal error Internal lists are not in step.

Cannot find suitable Internal mapping files not found.

© Copyright 1999 to current year. 3:3 2.3

3.1.1 Export/Import different SDNF Formats

3.1.2 Export Information

© Copyright 1999 to current year. 3:4 2.3

© Copyright 1999 to current year. 3:5 2.3

© Copyright 1999 to current year. 3:6 2.3

Error and Log File Messages

3.2 Run Information

© Copyright 1999 to current year. 3:7 2.3

3.3 Export Form

There are several methods of adding elements to the Export list.

© Copyright 1999 to current year. 3:8 2.3

Clear just removes everything from the list.

Error and Log File Messages

No owning Structure Cannot climb to Structure element from current location

3.3.1 Export and Cancel

3.3.2 The Export Form Bar Menu

3.3.3 The Export Process

© Copyright 1999 to current year. 3:9 2.3

© Copyright 1999 to current year. 3:10 2.3

Error and Log File Messages

3.3.4 Exporting Linear Members

© Copyright 1999 to current year. 3:11 2.3

• Does it have a valid material?

Error and Log File Messages

Illegal or unset SPRE - Not SPRE must be valid.

No material information - Cannot determine material properties for member.

No material match for SDNFMGRADE cannot be matched with a material in

No material property match As above

Inconsistent material The element's MATR and :SDNFMGRADE attributes are