Professional Documents
Culture Documents
User Guide
AVEVA Solutions Ltd
Disclaimer
Information of a technical nature, and particulars of the product and its use, is given by AVEVA
Solutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaim
any and all warranties and conditions, expressed or implied, to the fullest extent permitted by law.
Neither the author nor AVEVA Solutions Ltd, or any of its subsidiaries, shall be liable to any person or
entity for any actions, claims, loss or damage arising from the use or possession of any information,
particulars, or errors in this publication, or any incorrect use of the product, whatsoever.
Copyright
Copyright and all other intellectual property rights in this manual and the associated software, and every
part of it (including source code, object code, any data contained in it, the manual and any other
documentation supplied with it) belongs to AVEVA Solutions Ltd or its subsidiaries.
All other rights are reserved to AVEVA Solutions Ltd and its subsidiaries. The information contained in
this document is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval
system, or transmitted without the prior written permission of AVEVA Solutions Ltd. Where such
permission is granted, it expressly requires that this Disclaimer and Copyright notice is prominently
displayed at the beginning of every copy that is made.
The manual and associated documentation may not be adapted, reproduced, or copied, in any material
or electronic form, without the prior written permission of AVEVA Solutions Ltd. The user may also not
reverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of the
product described in this publication may be incorporated into any third-party software, product,
machine, or system without the prior written permission of AVEVA Solutions Ltd, save as permitted by
law. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminal
prosecution.
The AVEVA products described in this guide are to be installed and operated strictly in accordance with
the terms and conditions of the respective license agreements, and in accordance with the relevant
User Documentation. Unauthorised or unlicensed use of the product is strictly prohibited.
AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom
Trademarks
AVEVA and Tribon are registered trademarks of AVEVA Solutions Ltd or its subsidiaries. Unauthorised
use of the AVEVA or Tribon trademarks is strictly forbidden.
AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Ltd or its
subsidiaries, registered in the UK, Europe and other countries (worldwide).
The copyright, trade mark rights, or other intellectual property rights in any other product, its name or
logo belongs to its respective owner.
OpenSteel User Guide
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
Auto-detection of SDNF Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4
Export Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:5
Run Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:8
AVEVA OpenSteel - Export Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:9
Export and Cancel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:10
The Export Form Bar Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:10
The Export Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:10
Exporting Linear Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:12
Exporting Plates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:14
Exporting Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:16
Testing AVEVA OpenSteel Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:18
Initial Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:18
Preparing to Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:19
Creation of Export File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:22
Checking the SDNF Output File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:22
i 1.5
OpenSteel User Guide
ii 1.5
OpenSteel User Guide
iii 1.5
OpenSteel User Guide
iv 1.5
OpenSteel User Guide
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.
Import from SDNF explains how to import a steel structure from an SDNF file
Bolt Reports explains how to extract reports of Anchor Bolts from the
model using the Bolt Report templates
Appendix: Sample SDNF gives a brief extract of an SDNF file produced by the AVEVA
File OpenSteel interface
Appendix: Sample Import shows sample log files from an Import process according to
Log Files the mode specified
Appendix: Sample Validity shows a sample log file from an Import validity checking
Check Log File process to check for duplicate mark numbers
1:1 1.5
OpenSteel User Guide
Introduction
1:2 1.5
OpenSteel User Guide
Glossary
2 Glossary
2:1 1.5
OpenSteel User Guide
Glossary
2:2 1.5
OpenSteel User Guide
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.
3:1 1.5
OpenSteel User Guide
Exporting to SDNF
The interface requires two external mapping tables for each Target Package to check that
the Target Package can accept the data. It also may use the Profile Orientation mapping
3:2 1.5
OpenSteel User Guide
Exporting to SDNF
table if necessary. The mapping tables are for the Steel Profiles, Materials and for mapping
the Profile Orientations between PDMS and the neutral file. The section on user
customisation in the Installation Guide tells the user how to arrange these files on your file
system and what format they are to be. The interface 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 Installation Guide which explains how to configure
the interface to tell it where all the files are located.
The user may have a generic pair of mapping tables to map between PDMS and SDNF for a
particular steel fabricator, for example, or the user may have a similar pair for each 3D steel
detailing package.
The current file settings are indicated on this form. The user will notice that changing the
Target Package by using the Target Package selector button on the right-hand side of the
form may cause the text to change giving the full path names of the respective files. Do not
be concerned that the path name may be truncated by the insertion of the ellipsis (): it is
modified only for display purposes on the form.
The system also checks that 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
Installation 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 Profile and Material
mapping tables for the Target Package indicated by the Target Package selector gadget on
the right hand side of the form, according to the system configuration files.
The Manual option activates two other buttons, which are greyed out for the Auto option.
Selecting this option changes the form to be similar to below.
The user can select the file type using the Profiles, Materials or Orient'n toggle buttons
and enter the full path name of the file in the data entry area. The user can also include
system environment variables in the path name as long as they are in the proper AVEVA
PDMS format, e.g. %ENVVAR% being the PDMS representation of the ENVVAR
environment variable.
3:3 1.5
OpenSteel User Guide
Exporting to SDNF
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.
3:4 1.5
OpenSteel User Guide
Exporting to SDNF
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.
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.
3:5 1.5
OpenSteel User Guide
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
environment variable.
The SDNF file may have several sections: a header, Packet 00; a set of Linear Members,
Packet 10; a set of Plates, Packet 20; and a set of Connection Details, Packet 40. The
header is compulsory: any other Packets are optional.
Selecting the information to be contained in Packet 00 is performed by navigating to, or
below, the relevant PDMS Design SITE, ZONE or STRU element which contains the
required header information. This is done by using the Members list window at the bottom of
the main Export form. When at or below the correct element, click the Use CE button on
this form and the source text will indicate from where the interface will get the information. If
there is not enough space on the form the element's reference number is output rather than
its name.
3:6 1.5
OpenSteel User Guide
Exporting to SDNF
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 (Linear Members) and/or Packet 20 (Plates). The user cannot output Packet 40
(End Connections) without outputting Packet 10 (Linear Members). If the user does not
want Packet 10, the sub-options, Linear Members only and Linear Members + End
Connections are inactivated and greyed out.
3:7 1.5
OpenSteel User Guide
Exporting to SDNF
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.
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.
The Test Run? option allows the user to suppress the updating of all the Export flags. This
is so that the user can see if there will be a successful Export of the model. The user may
find that the Profile or Material mapping files are not quite up to date which might cause a
failure in the Export process. Therefore, the user can select this option to define this as a
test run.
After the Export process 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.
3:8 1.5
OpenSteel User Guide
Exporting to SDNF
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.
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.
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.
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.
3:9 1.5
OpenSteel User Guide
Exporting to SDNF
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:10 1.5
OpenSteel User Guide
Exporting to 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 above indicates a successful completion, while the below represents some problem
encountered in the external program.
On completion of the external program, the status file is inspected and, if the result is
favourable, the user will then be asked whether or not to look at the log file, if that option has
been selected on the Run Information form.
3:11 1.5
OpenSteel User Guide
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.
File does not exist Somehow there is no log file. Are there issues regarding
access rights to the %PDMSWK% directory?
3:12 1.5
OpenSteel User Guide
Exporting to SDNF
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.
3:13 1.5
OpenSteel User Guide
Exporting to SDNF
3:14 1.5
OpenSteel User Guide
Exporting to SDNF
in a Catalogue definition. Neither are holes or negative primitives transferred from the
design.
The Description attribute will be used to store the flooring type, such as grating or chequer
plate. This is passed as the type field (up to 24 characters).
The Material Grade transferred in Packet 20 represents the material type. This is a text
attribute, rather than the number field in PDMS. Therefore a User Defined Attribute (UDA),
:SDNFMGRADE, has been defined within PDMS to store this information.
Note: Any edge preparation details and modelling, such as grinding, will be lost in the
transfer operation.
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.
3:15 1.5
OpenSteel User Guide
Exporting to SDNF
3:16 1.5
OpenSteel User Guide
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.
3:17 1.5
OpenSteel User Guide
Exporting to SDNF
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.
3:18 1.5
OpenSteel User Guide
Exporting to SDNF
3:19 1.5
OpenSteel User Guide
Exporting to SDNF
3:20 1.5
OpenSteel User Guide
Exporting to SDNF
3:21 1.5
OpenSteel User Guide
Exporting to SDNF
3:22 1.5
OpenSteel User Guide
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.
4:1 1.5
OpenSteel User Guide
Import from SDNF
The interface requires two external mapping tables for each Source Package to check that
the design can accept the data. It also may use the Profile Orientation mapping table if
necessary. The mapping tables are for the Steel Profiles, Materials and for mapping the
Profile orientations between DESIGN and the Neutral File. The section on user
customisation in the Installation Guide explains how the user can arrange these files on the
file system and what format they are to be. The interface also needs to know where the
external mapping files are located on your computer network. For this internal mapping
tables are required. Refer to the Installation Guide which explains how the user can
configure the interface to let it know where all the files are located.
The user can have a generic pair of mapping tables to map between PDMS and SDNF for a
particular steel fabricator, for example. Or the user can have a similar pair for each 3D steel
detailing package.
The current file settings are indicated on this form. The user will notice that changing the
Source Package by using the Source Package selector button on the right hand side of the
form may cause the text to change giving the full path names of the respective files.
Note: Do not be concerned that the path name may be truncated by the insertion of the
ellipsis (): it is modified only for display purposes on the form.
The system also checks that these files are compatible with the Source Package by
checking the identification line at the top of each mapping table. Refer to the AVEVA
OpenSteel Installation 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 Profile and Material
mapping tables for the Source Package indicated by the Source Package selector gadget
on the right hand side of the form, according to the system configuration files. When the
user comes to execute the Import process, the Auto flag will cause the correct mapping files
4:2 1.5
OpenSteel User Guide
Import from SDNF
to be used based on the Issue field in the Input file header. Refer to Technical Information
for details about the format of the header of an SDNF file.
The Manual option activates two other buttons, which are greyed out for the 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 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
original interface variables unchanged.
4:3 1.5
OpenSteel User Guide
Import from SDNF
The user either type the full directory path name of the input file, or use the Browse button
to bring up a File Browser. The use of this form is as described in the section above. The
interface tests to see if the file exists and if it does not the user will be warned. As well as
testing for the existence of the file, it is also tested for being a valid SDNF file by inspection
of its header details.
4:4 1.5
OpenSteel User Guide
Import from SDNF
Note: If the user does not enter the full path name, the input file will be assumed to be in
the directory from which started PDMS. The user can also include system
environment variables in the path name as long as they are in the proper AVEVA
PDMS format, e.g. %ENVVAR% being the PDMS representation of the ENVVAR
environment variable.
In addition to the basic check for the input file being in SDNF format, the initial comments
are scanned for the presence of a data table, which may list the Packets to follow and the
number of items to be transferred in each one. If this table is present, it will be analysed and
the buttons determining which Packets may be Imported will be activated or inactivated
accordingly. This table is described in Technical Information.
On entering the name of the file, if it is from a recognised SDNF Source Package and if
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) and/or Packet 20 (Plates).
Note: The user cannot import Packet 40 (Connection Details) with this version of the
interface. The interface will check that the user is attempting to Import something if
both options are unchecked!
4:5 1.5
OpenSteel User Guide
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
original interface variables unchanged.
Import file does not exist File specified does not exist.
Not an SDNF File File specified is not an SDNF file. This may also arise if
the file the user is inspecting has been transferred across
hardware platforms.
Nothing to import The user deselected both the Linear Members and Plates
options.
Cannot 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:6 1.5
OpenSteel User Guide
Import from SDNF
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.
Note: This reference model will be deleted next time the user Exports or Imports anything
and that it is only transient data. Also, it may not be a complete model as some items
may already have been transferred into the main model on merging.
After the Import merging process has been performed, the user can sort all new items into
FRMW (Framework) elements according to their Material type. This option is selected by
clicking the Sort on Material Type option.
During the Import process, comparisons are made for Linear Members and Plates between
the existing model data and the imported model data. The 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.
4:7 1.5
OpenSteel User Guide
Import from SDNF
Using this form the user can deselect attributes for comparison but must be aware that
strange results may occur especially if the user ignores positional and rotational attributes.
Finally, there are two validity checks the user can perform on the incoming data which to
ensure a subsequent Import run will have a chance of success. Activating these options
overrides completely the Import choices made on the main form. With these validity checks
the user will be able to see a log file before any data is merged whatsoever.
The Profile Mapping? button enables the user to see if the incoming Linear Member Profile
specifications will be successfully mapped between systems. This is a relatively fast
transaction as the SDNF file is just passed through the external program without any
subsequent import or comparison in PDMS. the user will then be able to see the log file
produced and take appropriate action.
There is a risk in the external detailing package that entity mark numbers may be duplicated.
The Duplicate Mark numbers selector gadget enables the user to check for duplicate
numbers in the incoming model. There are three options: NONE, NEW and GLOBAL.
NONE deactivates the gadget and no checks are made. The import process just goes
through unhindered. The NEW option allows the user to check only the new imported items
for duplicate mark numbers, while the GLOBAL option enables the user to search all the
available DESIGN databases for duplicate numbers. Obviously these searches may involve
a certain amount of time, but for the sake of validity, they would be worth using.
4:8 1.5
OpenSteel User Guide
Import from SDNF
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
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.
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:9 1.5
OpenSteel User Guide
Import from SDNF
Import executes the Import process. As it proceeds the user is kept informed of the
progress.
Click YES and the interface will wait for another period of time. Clicking NO will cause the
interface to stop where it is. Finally the system will indicate its completion, whether
successful or not. This completion message should be read in conjunction with the log file, if
any errors are indicated.
The user will be alerted to unsuccessful runs by the external program by the following form
after which the process exits.
4:10 1.5
OpenSteel User Guide
Import from SDNF
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
PDMS session. The user cannot use a file from a previous OpenSteel session as the
Import data may be incorrect.
4:11 1.5
OpenSteel User Guide
Import from SDNF
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.
4:12 1.5
OpenSteel User Guide
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 highlight 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:13 1.5
OpenSteel User Guide
Import from SDNF
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.
It is clear from the above diagram that the interface supports partial model transfer as it just
highlights those new or changed items. Anything indicated as deleted is more an indication
that the item is not present in the Imported SDNF file. It is not deleted from the Original
Model during the Merge process: "Deleted" items are simply moved to another SITE to
4:14 1.5
OpenSteel User Guide
Import from SDNF
enable the user to recover them if necessary. So parts of models can be merged into the
original model with no loss of data.
Note: The Reference Model which is created is named according to the user session, so
that several user Reference Models could coexist at the same time. As they are
named according to session, the user is advised to take care to manage them and
not to leave too many versions around to fill up your disk space.
The Comparison process allows any potential changes, additions and deletions to the
original model to be detected and highlighted in a 3D Volume View window, if there is one
present and if the items are in the current Drawlist.
As for both Linear Members and Plates the user can select which attributes are significant
for Comparison. This is performed using the Comparison Checklist form which is a child of
the Import Run Information form. By default, all the attributes transferred through the
SDNF file are compared.
4:15 1.5
OpenSteel User Guide
Import from SDNF
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.
If, during the Merge phase, items are to be merged, then the lists of added and deleted
items are reconciled with the original model - by being deleted or transferred from reference
model. The storage SITE header details are then merged with the information in the SDNF
header (Packet 00).
After the main model Merging has been completed, if the user has chosen the Sort on
Material Type option on the Import form, any new items will be sorted into FRMW groups
according to their material type as specified by the :SDNFMGRADE attribute.
The version numbering system is described below, in Technical Information.
4:16 1.5
OpenSteel User Guide
Import from SDNF
Additional Items
Items added to the model are recorded as such; they are highlighted by changing their
colour, a suitable message is output to the log file and they are then transferred to a special
area. Merging will transfer all the added items from the reference model to the original
model. If required, they are then sorted according to material type.
The new items are gathered together into a site whose name is constructed from the
Transfer and Revision Numbers so that the user can easily locate all items added at a
specific version or date.
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.
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 Installation 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.
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'
4:17 1.5
OpenSteel User Guide
Import from SDNF
The user would thus be able to find all the 'deleted' items to this MDB at this version.
Changed Items
In merging Plates the interface tries to keep the original vertices as they may have been
used for locating dimensions on drawings: it may be that just the positions have been
changed. However, the comparison only works in list order: the interface does not look
around for another vertex in the same physical place, although it may be in a different list
position. Extra unwanted vertices are deleted on merging and all new vertices are added to
the end of the list. A totally new Plate is just imported directly.
Changed objects are highlighted as such by a change in colour.
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:18 1.5
OpenSteel User Guide
Import from SDNF
In the Selected items box, the user can select any combination of Added, Changed, or
Deleted Items for highlighting, according to the date range described below.
By selecting the inclusive dates defining the limits of the range using the From and To date
selector gadgets the user can highlight on the screen those items in the current drawlist
which have been changed, added or deleted.
4:19 1.5
OpenSteel User Guide
Import from SDNF
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'.
The rules of selecting the changed, deleted or added items are the same as for the previous
section, Highlighting by Import Date.
By selecting the versions defining the limits of the range using the From and To version
selector gadgets the user can highlight on the screen those items in the current drawlist
which have been changed, added or deleted.
Note: As the 'deleted' elements are relocated in the database after Merging, the area
where they are finally located should also be in the drawlist if the user wants to see
what has been 'deleted'.
4:20 1.5
OpenSteel User Guide
Import from SDNF
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.
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.
4:21 1.5
OpenSteel User Guide
Import from SDNF
4:22 1.5
OpenSteel User Guide
Import from SDNF
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.
When the details are correct click OK.
4:23 1.5
OpenSteel User Guide
Import from SDNF
Note: In the above form the environment variable %TSTIMP% has been automatically
replaced by its expanded value.
4:24 1.5
OpenSteel User Guide
Import from SDNF
The user will then be asked if they want to inspect the log file. If they do, they can save it
with the File > Save as option in the OpenSteel File Viewer window to bring up a File
Browser, or by clicking the Save as button to the suggested filename. The log file window
may be closed by the Cancel button.
4:25 1.5
OpenSteel User Guide
Import from SDNF
4:26 1.5
OpenSteel User Guide
Bolt Reports
5 Bolt Reports
This section explains how to extract reports of Anchor Bolts from the model using the Bolt
Report templates supplied with the interface. This is useful for comparing Import and Export
models, locating anchor bolts and purchasing.
The report templates are to be found in the directory reports/templates under the main
directory which is created on installation of the interface.
Modelling of anchor bolts will be by Linear Members, i.e. SCTN elements, in the correct
location. Therefore, the anchor bolt report templates assume that:
the 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>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 1.5
OpenSteel User Guide
Bolt Reports
============================================================
================================================================
5:2 1.5
OpenSteel User Guide
Bolt Reports
5:3 1.5
OpenSteel User Guide
Bolt Reports
5:4 1.5
OpenSteel User Guide
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 1.5
OpenSteel User Guide
Technical Information
6:2 1.5
OpenSteel User Guide
Technical Information
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
6:3 1.5
OpenSteel User Guide
Technical Information
If the user manually selects the wrong SDNF version, they may also get an error message in
the log file about syntax errors in the incoming file. This is because the Packet 0 records are
different.
6:4 1.5
OpenSteel User Guide
Technical Information
Note: The Issue Code (Record 7) holds the Source Package of the SDNF file.
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:5 1.5
OpenSteel User Guide
Technical Information
requirement is that the Cardinal Point is to be used to draw the lines in schematic drawings
such that, where possible, a connected model may be deduced.
More generally, the interpretation is as follows:
Record 6 is ignored completely - (2D offsets)
The Start and End cutbacks (Record 5) are ignored by default, but see section 6.5 Using
Linear Member Cutbacks for how to enable them.
The Start and End Position of the Member (Record 5) is the start and end position of the
'real length of steel' located on the line described by the Cardinal Point (Record 3).
The 3D Start and End Eccentricities (Record 7) then define the real start and end of the
Cardinal Point 'Line' relative to the Node, if any. Thus, using Record 7 with Record 5, the
Node position could be determined. AVEVA OpenSteel would export this value, but could
not do much with it on import at the moment.
Note: The sense of this eccentricity is a vector from the end of the member to the node
position.
All packages are assumed to export the start and end positions of the Linear Member's
Cardinal Point Line.
Packet 20 - Plates
Plates are represented in PDMS by PANE elements as loops on the upper and lower faces.
No enclosed holes are transferable using SDNF.
6:6 1.5
OpenSteel User Guide
Technical Information
Order of Vertices
When exporting, the vertices describing a Plate are assumed to be defined in a manner
according to the "Right Hand Screw Rule", where the vertices are in a clockwise order when
viewed along the normal to the Plate plane.
When importing, the vertices may be defined in either direction.
Plate Origin
The Plate Origin is taken to be the position of the first vertex.
Plate Orientation
The vector from the first vertex to the next vertex is taken as the local X axis. Knowing the
fact that the plate is defined in a Right Hand Screw Rule manner, the plane normal can be
determined. This will determine the local Z axis. The Y axis then becomes the vector cross
product of the Z and X axes.
6:7 1.5
OpenSteel User Guide
Technical Information
#
# 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
6:8 1.5
OpenSteel User Guide
Technical Information
# 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.
6:9 1.5
OpenSteel User Guide
Technical Information
On Import the components of a member ID number are stored in the NUMB attribute.
6:10 1.5
OpenSteel User Guide
Technical Information
6:11 1.5
OpenSteel User Guide
Technical Information
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 entered in
Record 5 will be the start and end positions of the Justification Pline of the member.
Where the member is connected, i.e. the Joistart and/or Joiend attributes are set, the start
and/or end cutback value will be set to be the absolute length of the vector between the
node position and the Justification Pline position as projected along the member's axis. In
effect, this calculates a virtual node. For simple, orthogonal structures which have not been
manipulated too much, this will tend to be at the same position as the attached node.
Where the member is unconnected, i.e. either the Joistart and/or Joiend attributes are
unset, the start and/or end cutback value will be set to zero.
6:12 1.5
OpenSteel User Guide
Technical Information
When the Use Cutbacks checkbox is checked the start and end positions entered in
Record 5 will be the positions of the virtual nodes derived from the nodes to which the start/
end is connected. The start and end cutbacks will be set to be the distance between the
virtual node position and the Justification Pline position.
If either or both member ends are unconnected the start and/or end position in Record 5 will
be start and/or end position of the Justification Pline and the cutbacks will be zero.
6:13 1.5
OpenSteel User Guide
Technical Information
Below is the relevant Export dialog with the Use Cutbacks option indicated.
6:14 1.5
OpenSteel User Guide
Technical Information
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 given in Record 5. Any cutback values in
Record 5 will be ignored.
6:15 1.5
OpenSteel User Guide
Technical Information
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 in Record 5.
6:16 1.5
OpenSteel User Guide
Technical Information
Below is the relevant Import dialog with the Use Cutbacks option indicated.
6:17 1.5
OpenSteel User Guide
Technical Information
6:18 1.5
OpenSteel User Guide
Technical Information
Note: The FrameWorks coordinate system defining the Profiles is left-handed. The
difference between this and the coordinate system used in PDMS is illustrated by the
diagram below.
6:19 1.5
OpenSteel User Guide
Technical Information
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:20 1.5
OpenSteel User Guide
Technical Information
6:21 1.5
OpenSteel User Guide
Technical Information
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
6:22 1.5
OpenSteel User Guide
Technical Information
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:23 1.5
OpenSteel User Guide
Technical Information
: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:24 1.5
OpenSteel User Guide
Technical Information
6:25 1.5
OpenSteel User Guide
Technical Information
Note: The UDA, :SDNFTRANO, is actually an index into a character string returning the
equivalent character as the TransferLetter.
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.12 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 or
Plates.
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.
Curved Members/Curved Plates: This version of the SDNF format does not contain the
description for them. Curved members may be exported in SDNF using Packet 10 as a
series of straight segments.
Templates: Templates and Catalogues are not covered by SDNF.
6:26 1.5
OpenSteel User Guide
Technical Information
Non-prismatic end details: SDNF Packet 10 cannot describe any details at member/cleat
ends apart from full orthogonal cuts. Hence, all sloped cuts, notches, etc. will be
approximated from minimum to maximum local longitudinal co-ordinate, which should be
conservative regarding clash detection. SDNF Packet 20 can describe only fully prismatic
Plates. Hence, the Plate cuts/intersections which are not fully orthogonal to the Plate's local
plane cannot be mapped to SDNF. Such Plates will be exported 'uncut', which again should
be conservative for clash detection.
6.13 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 users of each
package to ensure that the geometric description associated with the catalogue name is
identical and that there is a means of correlation between the packages.
In DESIGN, the structural model may contain two views of the data: one view defined by
logical connectivity by references to the connecting items; and the physical view defined by
the relative location of items. So, while we may logically relate two items, they may not
necessarily be physically close to each other. In external 3D steel detailing packages the
means of determining connectivity may be by proximity. Thus, transferring the PDMS model
will necessarily involve the loss of real connectivity information which will be difficult to
reconstitute correctly on Import.
The interface will output a warning message when packets are met which cannot be
handled or are unexpected.
6:27 1.5
OpenSteel User Guide
Technical Information
6:28 1.5
OpenSteel User Guide
Document Revision History
7:1 1.5
OpenSteel User Guide
Document Revision History
7:2 1.5
OpenSteel User Guide
Appendix: 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
# 40 65
# ENDTABLE
#
#
# STARTTABLE ANYANYCON
# Default Connection
# BP macro BasePlate
# TP TP
# EP EP
# EPF EPF
# MCT MCT
# MCB MCB
# MCTB MCTB
# MCL MCL
# MCR MCR
# MCLR MC
# SWA SWA
# SWB SWB
# SWC SWC
# SWD SWD
# SWE SWE
# SWF SWF
# SWG SWG
# FWA FWA
# FWB FWB
A:1 1.5
OpenSteel User Guide
Appendix: Sample SDNF File
# FWC FWC
# FWD FWD
# FWE FWE
# FWF FWF
# FWG FWG
# 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 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 ANYORI
# STRUCAD %SDNFMAIN%/maps/StruCad/StruCadOri.map
# XSTEEL %SDNFMAIN%/maps/XSteel/XSteelOri.map
# STEELCAD %SDNFMAIN%/maps/SteelCad/SteelCadOri.map
# PDMS %SDNFMAIN%/maps/PDMS/PDMSOri.map
# FRAMEWORKS %SDNFMAIN%/maps/FrameWorks/FrameWksOri.map
# ENDTABLE
#
#
# STARTTABLE ANYSTD
# EUR Euronorm
# BRI British
A:2 1.5
OpenSteel User Guide
Appendix: Sample SDNF File
# 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
#
#
Packet 00
"Engineering Firm Id"
"Client Id"
"Structure Id"
"Project Id"
"30 Nov 2003" "09:58"
3 "PDMS"
"Design Code"
0
Packet 10
"MM" 281
1 8 0 0 "BEAM" "15322/100" 0
"HE300A" "Steel, carbon" 0.0000 0 0
0.0000 0.0000 1000.0000 112000.0000 159822.3900 115000.0000
112000.0000 160177.6090 115000.0000 0.0000 0.0000
0.0000 0.0000
0.0000 0.0000 0.0000 0.0000 0.0000 0.0000
0 0 0 0 0 0 0 0 0 0 0 0
2 10 0 0 "SCTN" "15322/1003" 0
"HANDRAIL" "Steel, carbon" 0.0000 0 0
0.0000 0.0000 1000.0000 137050.0000 179400.0000 105275.0000
137050.0000 182100.0000 105275.0000 0.0000 0.0000
A:3 1.5
OpenSteel User Guide
Appendix: Sample SDNF File
0.0000 0.0000
-100.0000 100.0000 100.0000 0.0000 0.0000 0.0000
0 0 0 0 0 0 0 0 0 0 0 0
3 10 0 0 "SCTN" "15322/1008" 0
"HANDRAIL" "Steel, carbon" 0.0000 0 0
0.0000 0.0000 1000.0000 134350.0000 181150.0000 105275.0000
134350.0000 181825.0000 105275.0000 0.0000 0.0000
0.0000 0.0000
0.0000 0.0000 0.0000 0.0000 0.0000 0.0000
0 0 0 0 0 0 0 0 0 0 0 0
4 10 0 0 "SCTN" "15322/1009" 0
"HANDRAIL" "Steel, carbon" 0.0000 0 0
0.0000 0.0000 1000.0000 134350.0000 179400.0000 105275.0000
134350.0000 180350.0000 105275.0000 0.0000 0.0000
0.0000 0.0000
0.0000 0.0000 0.0000 0.0000 0.0000 0.0000
0 0 0 0 0 0 0 0 0 0 0 0
5 10 0 0 "SCTN" "15322/1012" 0
"HANDRAIL" "Steel, carbon" 0.0000 0 0
0.0000 0.0000 1000.0000 137050.0000 179400.0000 105275.0000
136100.0000 179400.0000 105275.0000 0.0000 0.0000
0.0000 0.0000
0.0000 0.0000 0.0000 -1650.0000 100.0000 100.0000
0 0 0 0 0 0 0 0 0 0 0 0
A:4 1.5
OpenSteel User Guide
Appendix: Sample SDNF File
more Plates
290 0 0 0 "PANE"
"15322/722" "Steel, carbon" 100.0000 4
155080.0000 214000.0000 100169.6710
155079.6090 214000.0000 104010.0000
151319.9370 214000.0000 104010.0000
151320.0000 214000.0000 100170.0850
Packet 40
65
295 120 1 "Base Plate 250 250 0 0"
296 118 1 "Base Plate 250 250 0 0"
305 128 1 "Base Plate 250 250 0 0"
309 139 1 "Base Plate 150 250 0 0"
310 138 1 "Base Plate 300 300 0 0"
311 138 2 "TP"
312 141 1 "Default Connection"
A:5 1.5
OpenSteel User Guide
Appendix: Sample SDNF File
A:6 1.5
OpenSteel User Guide
Appendix: Sample Export Log File
B:1 1.5
OpenSteel User Guide
Appendix: Sample Export Log File
Files used...
=============
Output file : .\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
B:2 1.5
OpenSteel User Guide
Appendix: Sample Import Log Files
This appendix shows sample log files from an Import process according to the mode
specified.
C.1.2 Plates
PLATE <mark> <state> <point> <hold> <pspec> <height>
<material> <pos> <vertexCount> <changedVertex>
The rules for values in each of the above fields are as for the Linear Members.
Below is a sample log file in brief format following an Import:
C:1 1.5
OpenSteel User Guide
Appendix: Sample Import Log Files
C:2 1.5
OpenSteel User Guide
Appendix: Sample Import Log Files
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
C:3 1.5
OpenSteel User Guide
Appendix: Sample Import Log Files
C:4 1.5
OpenSteel User Guide
Appendix: Sample Import Log Files
C:5 1.5
OpenSteel User Guide
Appendix: Sample Import Log Files
C:6 1.5
OpenSteel User Guide
Appendix: Sample Import Log Files
===========================
DELETIONS >>>> 7 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
C:7 1.5
OpenSteel User Guide
Appendix: Sample Import Log Files
C:8 1.5
OpenSteel User Guide
Appendix: Sample Validity Check Log File
This appendix shows a sample log file from an Import validity checking process to check for
duplicate mark numbers.
D:1 1.5
OpenSteel User Guide
Appendix: Sample Validity Check Log File
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-
D:2 1.5
OpenSteel User Guide
Appendix: Sample Validity Check Log File
010\Dev\osde150\maps\PDMS\PDMSOri.map
D:3 1.5
OpenSteel User Guide
Appendix: Sample Validity Check Log File
D:4 1.5
OpenSteel User Guide
Index
A G
Anchor Bolt Glossary . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
locations . . . . . . . . . . . . . . . . . . . . . . 5:1 Grid Packet
quantities . . . . . . . . . . . . . . . . . . . . . 5:2 Packet 50 . . . . . . . . . . . . . . . . . . . . . 6:8
AVEVA OpenSteel - Export Form . . . . . . 3:9
I
B
Import from SDNF . . . . . . . . . . . . . . . . . 4:1
Bolt Reports . . . . . . . . . . . . . . . . . . . . . . 5:1 Import Information . . . . . . . . . . . . . . . . . 4:4
Import Log Files
C sample . . . . . . . . . . . . . . . . . . . . . . . C:1
Import Process . . . . . . . . . . . . . . . . . . . 4:10
Cardinal Points . . . . . . . . . . . . . . . . . . . 6:18
Comparison and Merging Processes . . 4:13 L
Connection Details
Packet 40 . . . . . . . . . . . . . . . . . . . . . 6:7 Linear Member
Cross Referencing Models . . . . . . . . . . 6:25 using cutbacks . . . . . . . . . . . . . . . . 6:10
Linear Members
D Packet 10 . . . . . . . . . . . . . . . . . . . . . 6:5
R
Run Information . . . . . . . . . . . . . . . 3:8, 4:6
S
SDNF
file header information . . . . . . . . . . . 6:8
recommended file suffix . . . . . . . . . . 6:8
sample file . . . . . . . . . . . . . . . . . . . . A:1
Source Information . . . . . . . . . . . . . . . . . 4:2
T
Target Information . . . . . . . . . . . . . . . . . . 3:2
Technical Information . . . . . . . . . . . . . . . 6:1
The Export Process . . . . . . . . . . . . . . . 3:10
U
UDAs . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:23
V
Validity Check Log File
sample . . . . . . . . . . . . . . . . . . . . . . .D:1
Verbose Format . . . . . . . . . . . . . . . . . . .C:4
Version Numbering . . . . . . . . . . . . . . . . 6:25