Exporting from the application, all items are exported using millimeters as the distance units.
All reference data, such as any pre-existing reference model, is removed before exporting anything. Details about saving the reference model are available. Refer to Import from SDNF for further information.
Prior to any Export process, all fields are checked for validity.
In addition, there is an SDNF specific UDA, :SDNFEXCLUDE, attached to certain application elements by which you can define whether the item is to be exported or not. Setting this logical flag to true excludes the item from the Export process. Refer to UDAs for further information.
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 data is correct and valid, the external program is called. The interface waits for a certain time until the program is finished. The amount of waiting time is configurable. If there are errors raised by the external program you are 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, you are asked if to carry on waiting for another time unit.

Click Yes and the interface waits for another period of time. Click No to stop the interface where it is. Finally the system indicates its completion, whether successful or not. The completion message should be read in conjunction with the log file, if any errors are indicated.

The message indicates a successful completion.

The error message indicates that a problem was encountered in the external program.
On completion of the external program, the status file is inspected and, if the result is favourable, you are then asked whether or not to view the log file, if that option has been selected on the Run Information window.

To inspect the log file later, save it with the File > Save as option in the File Viewer window which opens a File Browser, or click Save as to the suggested filename. Either way, if the file already exists, you are asked whether to overwrite it. The log file window may then be closed, click Cancel.

If the Brief mode has been chosen on the Run Information window for displaying the log file, the window displaying the log file filters out all warning messages, leaving only the error messages. Saving the log file, however, all messages are retained in the file.
Error and Log File Messages
File does not exist
Somehow there is no log file. Are there issues regarding access rights to the%AVEVA_DESIGN_WORK% folder?
File does not exist
Somehow there is no log file. Are there issues regarding access rights to the%AVEVA_DESIGN_WORK% folder?

File does not exist
Somehow there is no log file. Are there issues regarding access rights to the%AVEVA_DESIGN_WORK% folder?
Is the output file named?
Is anything going to be exported?
Are the mapping tables compatible with the Target Package?
Is there a valid Steel Standard table?
Is the output file named?
Is the output file named?
Is anything going to be exported?
Is anything going to be exported?
Are the mapping tables compatible with the Target Package?
Are the mapping tables compatible with the Target Package?
Is there a valid Steel Standard table?
Is there a valid Steel Standard table?

Import from SDNF
UDAs
Import from SDNF
UDAs
Yes
No
Run Information
File > Save as
File Viewer
Save as
Cancel
Brief
Run Information
Error and Log File Messages
File does not exist


A series of checks is made before a Linear Member is output.
If any of the 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. 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. Consult the section on importing Linear Members for further information about the reconstruction of complex GENSECs.
If the Linear Member is connected, the interface determines the offset of 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.
The SDNF interface may not be able to update the export information on the elements, usually 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. The file is called updateVersionNos<export date/time>.mac and is stored in the AVEVA_DESIGN_WORK folder.
Error and Log File Messages
Illegal or unset SPRE - Not exported
SPRE must be valid.
Zero length Linear Member - Not exported
Length less than user definable tolerance.
No material information - Not exported
Cannot determine material properties for member.
No material match for nnnn. - Unknown material
:SDNFMGRADE cannot be matched with a material in the Properties database.
No material property match
:SDNFMGRADE cannot be matched with a material in the Properties database.
Inconsistent material
specification
The element's MATR and :SDNFMGRADE attributes are not consistent.
Multiply defined entries in Material Table
Either a material to be mapped or a mapped profile appears more than once in the material file.
No match for material
The material is not in the material file
Syntax Error
Other, less specific, errors.
Unrecognized Parse State
The error 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 is also output.
No match for Cardinal Point nnnn
Pline or Cardinal Point not recognized. Neutral axis (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 standard
The profile is in the profile mapping file but is not in any 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 Profile Table
Either a profile to be mapped or a mapped profile appears more than once in the profile mapping file.
Illegal or unset SPRE - Not exported
SPRE must be valid.
Zero length Linear Member - Not exported
Length less than user definable tolerance.
No material information - Not exported
Cannot determine material properties for member.
No material match for nnnn. - Unknown material
:SDNFMGRADE cannot be matched with a material in the Properties database.
No material property match
:SDNFMGRADE cannot be matched with a material in the Properties database.
Inconsistent material
specification
The element's MATR and :SDNFMGRADE attributes are not consistent.
Multiply defined entries in Material Table
Either a material to be mapped or a mapped profile appears more than once in the material file.
No match for material
The material is not in the material file
Syntax Error
Other, less specific, errors.
Unrecognized Parse State
The error 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 is also output.
No match for Cardinal Point nnnn
Pline or Cardinal Point not recognized. Neutral axis (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 standard
The profile is in the profile mapping file but is not in any 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 Profile Table
Either a profile to be mapped or a mapped profile appears more than once in the profile mapping file.

Illegal or unset SPRE - Not exported
SPRE must be valid.
Zero length Linear Member - Not exported
Length less than user definable tolerance.
No material information - Not exported
Cannot determine material properties for member.
No material match for nnnn. - Unknown material
:SDNFMGRADE cannot be matched with a material in the Properties database.
No material property match
:SDNFMGRADE cannot be matched with a material in the Properties database.
Inconsistent material
specification
The element's MATR and :SDNFMGRADE attributes are not consistent.
Multiply defined entries in Material Table
Either a material to be mapped or a mapped profile appears more than once in the material file.
No match for material
The material is not in the material file
Syntax Error
Other, less specific, errors.
Unrecognized Parse State
The error 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 is also output.
No match for Cardinal Point nnnn
Pline or Cardinal Point not recognized. Neutral axis (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 standard
The profile is in the profile mapping file but is not in any 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 Profile Table
Either a profile to be mapped or a mapped profile appears more than once in the profile mapping file.
Is the SPRE set?
Is it a zero length member?
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?
Is the SPRE set?
Is the SPRE set?
Is it a zero length member?
Is it a zero length member?
Does it have a valid material?
Does it have a valid material?
Is the Justification Pline mappable to a Cardinal Point if it is not a Cardinal Point itself?
Is the Justification Pline mappable to a Cardinal Point if it is not a Cardinal Point itself?
Are the start and end points valid?
Are the start and end points valid?
Note:
Subsequent import processes are affected if the member appears to have been deleted by the external steel detailing package since its export. In fact, the linear member might never made the transfer to the Target Package in the first place.

Note:
Error and Log File Messages
Illegal or unset SPRE - Not exported
Zero length Linear Member - Not exported
No material information - Not exported
No material match for nnnn. - Unknown material
No material property match
Inconsistent material
specification
Multiply defined entries in Material Table
No match for material
Syntax Error
Unrecognized Parse State
No match for Cardinal Point nnnn
No Cardinal Point nnnn
Bad Cardinal Point nnnn
Problem exporting entity
Profile cannot be mapped
Profile is not in the standard
Profile is not the default
Multiply defined entries in Profile Table


Panels in the application are to be transferred as Plates using Packet 20, inclusive of stiffeners, floor and toe plates. Bent plates are also 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 Penetration Application is used to generate Catalogue holes, the resultant holes, kicker plates and stiffeners are not exported because they are contained in a Catalogue definition. Some holes and negative primitives can be transferred from the model.
The Description attribute is used to store the flooring type, such as grating or chequer plate and is passed as the type field (up to 24 characters).
The Material Grade transferred in Packet 20 represents the material type. It is a text attribute, rather than the number field in the application. Therefore a User Defined Attribute (UDA), :SDNFMGRADE, has been defined within the application to store this information.
A basic series of tests is performed before the Plate is exported.
If any of the criteria is not satisfied, the plate does not get exported in the SDNF output file.
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.
Although both plates and holes are supposed to have a clockwise definition (right hand screw rule) for their boundaries in either the application or in the SDNF file, the interface must be able to cope with either clockwise or anti clockwise directions. In exporting plates the vertex order is converted 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 the application. Because of the difference between the application and SDNF boundary definitions, vertices 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. It can become 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. The code indicates 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 the application 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 the application. As a result, a certain amount of geometric testing is involved in identifying and exporting circular plates. The interface recognizes only 4 or 5 point circles, where the 5th point is a duplicate of the first point.
Error and Log File Messages
No geometry information - Not exported
No PLOO element. Plate cannot be exported.
Plate too thin - Not exported
Thickness less than user defined minimum. Plate not exported.
Not enough vertices - Not exported
Fewer than 3 vertices. Cannot define valid geometry so Plate is not exported.
No material information - Not exported
Cannot determine material properties for member. A matching set of :SDNFMGRADE and Matref cannot be determined.
No material match for nnnn
Unknown material. :SDNFMGRADE cannot be matched with a material in the Properties database.
No material property match
Unknown material. :SDNFMGRADE cannot be matched with a material in the Properties database.
Inconsistent material specification
The element's MATR and :SDNFMGRADE attributes are not consistent.
Multiply defined entries in Material Table
Either a material to be mapped or a mapped profile appears more than once in the material mapping file.
No match for material
The material is not in the material mapping file.
Syntax Error
Other, less specific, errors.
Unrecognized Parse State
The error 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 is also output.
Problem exporting entity
Other errors found.
No geometry information - Not exported
No PLOO element. Plate cannot be exported.
Plate too thin - Not exported
Thickness less than user defined minimum. Plate not exported.
Not enough vertices - Not exported
Fewer than 3 vertices. Cannot define valid geometry so Plate is not exported.
No material information - Not exported
Cannot determine material properties for member. A matching set of :SDNFMGRADE and Matref cannot be determined.
No material match for nnnn
Unknown material. :SDNFMGRADE cannot be matched with a material in the Properties database.
No material property match
Unknown material. :SDNFMGRADE cannot be matched with a material in the Properties database.
Inconsistent material specification
The element's MATR and :SDNFMGRADE attributes are not consistent.
Multiply defined entries in Material Table
Either a material to be mapped or a mapped profile appears more than once in the material mapping file.
No match for material
The material is not in the material mapping file.
Syntax Error
Other, less specific, errors.
Unrecognized Parse State
The error 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 is also output.
Problem exporting entity
Other errors found.

No geometry information - Not exported
No PLOO element. Plate cannot be exported.
Plate too thin - Not exported
Thickness less than user defined minimum. Plate not exported.
Not enough vertices - Not exported
Fewer than 3 vertices. Cannot define valid geometry so Plate is not exported.
No material information - Not exported
Cannot determine material properties for member. A matching set of :SDNFMGRADE and Matref cannot be determined.
No material match for nnnn
Unknown material. :SDNFMGRADE cannot be matched with a material in the Properties database.
No material property match
Unknown material. :SDNFMGRADE cannot be matched with a material in the Properties database.
Inconsistent material specification
The element's MATR and :SDNFMGRADE attributes are not consistent.
Multiply defined entries in Material Table
Either a material to be mapped or a mapped profile appears more than once in the material mapping file.
No match for material
The material is not in the material mapping file.
Syntax Error
Other, less specific, errors.
Unrecognized Parse State
The error 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 is also output.
Problem exporting entity
Other errors found.
Is there any geometry?
Is the height valid?
Is it justified correctly?
Does it have a valid material?
Are there enough vertices?
Is there any geometry?
Is there any geometry?
Is the height valid?
Is the height valid?
Is it justified correctly?
Is it justified correctly?
Does it have a valid material?
Does it have a valid material?
Are there enough vertices?
Are there enough vertices?
Note:
Any edge preparation details and modelling, such as grinding, will be lost in the transfer operation.
Note:
Subsequent import processes are affected if the plate appears to have been deleted by the external steel detailing package since its export. In fact, the plate might never made the transfer to the Target Package in the first place.
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 Model, you may find the order of vertices to have been reversed. Model is more tolerant about the ways in which you can define a plate.

stiffeners, floor and toe plates
Penetration Application
Note:
Note:
Note
:
Complex Plates (Type 1)
Complex Plates (Type 2 - Circular Ones)
Error and Log File Messages
No geometry information - Not exported
Plate too thin - Not exported
Not enough vertices - Not exported
No material information - Not exported
No material match for nnnn
No material property match
Inconsistent material specification
Multiply defined entries in Material Table
No match for material
Syntax Error
Unrecognized Parse State
Problem exporting entity


There is a limitation as to which holes are exported. Only secondary PLOO boundaries and NXTR elements can be handled as well as NBOX and NCYL under certain conditions. 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 recognized as such, by having 4 unique fillet vertices.
On import, vertices in boundaries are given a DESP value.
Using these values, specific shapes can be detected, For example circles or ellipses.
A message is output when the export process ignores most non loop-based negative primitives. It is 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 still only within tight geometrical constraints. Negative boxes and cylinders can be transferred only if a principal axis is parallel to the plate's normal. 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 extrusion vector parallel to the panel plane normal. Some negatives are not exported at all:
(NBOX)
NPOLYH
(NCYL)
NSLC
NSNO
NDIS
NCON
NPYR
NCTO
NRTO
(NXTR)
NREV
(NBOX)
NPOLYH
(NCYL)
NSLC
NSNO
NDIS
NCON
NPYR
NCTO
NRTO
(NXTR)
NREV

Imported holes are either NXTR or PLOO elements. A full penetration is a PLOO, and a partial penetration is an NXTR.
Any other negatives are not compared or merged on import. Other pre-existing negatives are moved and updated to maintain the original position and orientation.
PVTLastPoint
0
PVTStraight
1
PVTArc
2
PVTFillet
3
PVTCircle
4
(NBOX)
NPOLYH
(NCYL)
NSLC
NSNO
NDIS
NCON
NPYR
NCTO
NRTO
(NXTR)
NREV
PVTLastPoint
0
PVTStraight
1
PVTArc
2
PVTFillet
3
PVTCircle
4
PVTLastPoint
0
PVTStraight
1
PVTArc
2
PVTFillet
3
PVTCircle
4


End connections and base plates are 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 can be created in the external 3D steel detailing package. Once the end has been detailed, the resultant geometry may be returned to Model as Plate members in Packet 20 for graphical and clash checks. In the application, joint selection is controlled by specification.

As it exports Connections (PJOI and SJOI elements), the interface uses only the old connectivity model. New connectivity elements, such as FIXIngs are not handled. 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 member 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.
Error and Log File Messages
Illegal or unset SPRE
SPRE must be valid.
No Connection Type - Not exported
Cannot determine CTYA attribute. Joint cannot be exported.
Inconsistent connectivity - Not exported
Connectivity not consistent, so the joint cannot be exported. There is probably something more fundamentally wrong with the model.
Problem exporting entity
Other errors found.
Illegal or unset SPRE
SPRE must be valid.
No Connection Type - Not exported
Cannot determine CTYA attribute. Joint cannot be exported.
Inconsistent connectivity - Not exported
Connectivity not consistent, so the joint cannot be exported. There is probably something more fundamentally wrong with the model.
Problem exporting entity
Other errors found.

Illegal or unset SPRE
SPRE must be valid.
No Connection Type - Not exported
Cannot determine CTYA attribute. Joint cannot be exported.
Inconsistent connectivity - Not exported
Connectivity not consistent, so the joint cannot be exported. There is probably something more fundamentally wrong with the model.
Problem exporting entity
Other errors found.

Error and Log File Messages
Illegal or unset SPRE
No Connection Type - Not exported
Inconsistent connectivity - Not exported
Problem exporting entity


A test can be performed after installing the AVEVA SDNF product to make sure that the installation is complete and correct. All the required testing material can be found below the sub-folder SDNF\test\results\export in the user data folder.
The test creates an SDNF model file output.
Initial Configuration
Enter Model. You must have write access to the database, even though you are testing the Export process. The interface records the date and time of export as well as the revision numbers of the elements transferred.
Set the test project variables:
Choose the SITE to export to SDNF by selecting SITE /TEST-SDNF-INTERFACE from the hierarchy list and drag it into the 3D display window.
When that is finished, bring the SITE into view by adjusting the view limits. Refer to Limits for further information.
If required, modify the 3D view. Refer to Views for further information.

Prepare for Export
The Export window allows you to export a steel structure to a SDNF file.
You may be asked to install a Configuration details element. If so, accept the request.

On this window and associated windows, fill in the details prior to Export.
Target Information
Click Target information on the Export window to display the Export Target Information window.
Select the Auto option button and select AVEVA from the list of Target Packages on the Target Package drop-down list on the right hand side of the window. The system automatically detects the Target Package's Profile mapping table and Material mapping table.
Select the profile mapping file for the old catalogue named Aveva_E3D1.1.map. located in the Blockmaps\Aveva folder.
When the details are correct click OK.
Export Information
Click Export information on the Export window to display the Export Information window.
In the output file name field, input 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).
When the details are correct click OK.
Run Information
Click Run information on the Export window to display the Export Run Information window.
Select the Log File? check box and choose Verbose for the message mode.
Do not select the Test Run? check box as this is not a test run.
When the details are correct, click OK.
The Main Export
To add the SITE to be exported to SDNF, Select SITE /TEST-SDNF-INTERFACE in the Members list. Click Add CE, all the members in the 3D view change colour to indicate they are being exported.
The Export window look similar to this.

Create Export File
On the AVEVA SDNF - Export window, click Export.
The status line displays the progress of the task.
When the process is complete, you are asked whether to inspect the log file. You can then save it with the File > Save as option on the SDNF File Viewer window to display a File Browser, or click Save as to the suggested filename. The log file window can then be closed, click Cancel.
Check the SDNF Output Files.
Note:
The configuration details should be available to the SDNF interface user always in read/write mode. This is because the export and import processes store information about how many transfers there have been made by the interface, and in which direction.

Limits
Views
AVEVA SDNF
SDNF\test\results\export
Initial Configuration
Model
Limits
Views
Prepare for Export
Export
Note:
Target Information
Target information
Export
Export Target Information
Auto
AVEVA
Target Package
Aveva_E3D1.1.map
Blockmaps\Aveva
OK
Export Information
Export information
Export
Export Information
SDNF-Test.sdn
OK
Run Information
Run information
Export
Export Run Information
Log File?
Verbose
Test Run?
OK
The Main Export
Members
Add CE
Export
Create Export File
AVEVA SDNF - Export
File > Save
Save
Cancel


Imports a steel structure from a SDNF file.


Click Source Information to display the Import Source Information window which contains information about the 3D steel detailing package which the SDNF file is being transferred from.

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 Model. The file arrangement on the system and required format is explained. Refer to Customise SDNF for further information. The interface also needs to know where the external mapping files are located on the computer network. For this internal mapping tables are required. The configuration and location of files is explained. Refer to Internal Mapping Files for further information.
For example, you can have a generic set of mapping tables to map between SDNF and the application for a particular steel fabricator. Or you can have a similar set for each 3D steel detailing package.
The current file settings are indicated on this window. Changing the Source Package using the Source Package drop-down list on the right hand side of the window may cause the text to change giving the full path names of the respective files.
The system also checks that these files are compatible with the Source Package by checking only the identification line at the top of each mapping table. The format of the mapping files is explained.Refer to Internal Mapping Files for further information.
The two main options are Auto and Manual which are activated by selecting the appropriate option button on the left hand side of the window.
The Auto option causes the interface to select automatically the mapping tables for the Source Package indicated by the Source Package drop-down list on the right hand side of the window, according to the system configuration files. When you execute the Import process, the Auto flag causes the correct mapping files to be used based on the Issue field in the Input file header. Details about the Input file header are available. Refer to Technical Information for further information.
The Manual option activates other option buttons, which are initially greyed out for the Auto option. Selecting this option changes the display of the window. For example

You can select the file type using the Profiles/Materials/Orient'n or Unicode radio buttons and input the full path name of the file in the data entry area. You can also include system environment variables in the path name as long as they are in the proper format, for example, %ENVVAR% being the representation of the ENVVAR environment variable.
Press Enter, the interface checks for existence of the file and compatibility with the Source Package indicated by the Package drop-down list.
You can choose by hand which mapping file to use by either inputting its name in the text data entry field, or by using the Browse option to display a File Browser. Use this browser to search for the relevant mapping file.
Once all the correct data has been input on the Source Information window, click OK and the interface variables are updated. Click Cancel to close the window, leaving the original interface variables unchanged.
Error and Log File Messages
Internal error
Internal lists are not in step.
Cannot find suitable internal mapping list
Internal mapping files not found.
Suitable Mapping Table File not found
Mapping table found is not for the correct Source Package, or it does not exist.
Not a suitable Mapping Table File
Incorrect format of file, or empty file, or wrong Source Package.
Bad Map File
Mapping file is not correct format. Possibly it is from another operating system.
Error on SDNF File Browser form
You have input incorrect data on the file browser.
Internal error
Internal lists are not in step.
Cannot find suitable internal mapping list
Internal mapping files not found.
Suitable Mapping Table File not found
Mapping table found is not for the correct Source Package, or it does not exist.
Not a suitable Mapping Table File
Incorrect format of file, or empty file, or wrong Source Package.
Bad Map File
Mapping file is not correct format. Possibly it is from another operating system.
Error on SDNF File Browser form
You have input incorrect data on the file browser.

Internal error
Internal lists are not in step.
Cannot find suitable internal mapping list
Internal mapping files not found.
Suitable Mapping Table File not found
Mapping table found is not for the correct Source Package, or it does not exist.
Not a suitable Mapping Table File
Incorrect format of file, or empty file, or wrong Source Package.
Bad Map File
Mapping file is not correct format. Possibly it is from another operating system.
Error on SDNF File Browser form
You have input incorrect data on the file browser.
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 window.
Note:
The check is only that the file applies to the Source Package and not that it is a correct file type or format.

Customise SDNF
Internal Mapping Files
Internal Mapping Files
Technical Information
Source Information
Import Source Information
Customise SDNF
Internal Mapping Files
Note:
Internal Mapping Files
Auto
Manual
Auto
Technical Information
Manual
Auto
Profiles/Materials/Orient'n
Unicode
Enter
Note:
Source Information
OK
Cancel
Error and Log File Messages
Internal error
Cannot find suitable internal mapping list
Suitable Mapping Table File not found
Not a suitable Mapping Table File
Bad Map File
Error on SDNF File Browser form


Click Import Information to display the Import Information window which contains information about the import process.

Either type the full folder path name of the input file, or click Browse to display a File Browser. The interface checks that the file exists and if it does not you are 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.
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 is analyzed and the check boxes determining which Packets may be Imported are selected or deselected accordingly. Refer to Technical Information for further information.
On inputting the name of the file, if it is from a recognized SDNF Source Package and if Auto mode is set on the Source Information window, the Profile and Material mapping files are selected automatically and indicated in the Source Information window, if it currently displays, along with the updated Source Package drop-down list.
To view the SDNF Header (Packet 00) of the chosen input file, click Inspect to display the Input File Header Details window with which you can determine whether the file is the correct one to Import.

Using the check boxes on the Import Information window, if they are active, you can select whether to import Packet 10 (Linear Members), Packet 60 (Curved Members) and/or Packet 20 (Plates) or Packet 22 (Holes).

Once all the correct data has been input on the Import Information window, click OK and the interface variables are updated. Click Cancel to close the window, leaving the original interface variables unchanged.
Error and Log File Messages
Import file does not exist
File specified does not exist.
Not an SDNF File
File specified is not an SDNF file. The error may also arise if the file you are inspecting has been transferred across hardware platforms.
Nothing to import
You have deselected everything.
Cannot autodetect Source Package
If the AUTO option is on, the header of the Input file does not contain the Source Package information. The mapping table information has to be set by hand.
Import file does not exist
File specified does not exist.
Not an SDNF File
File specified is not an SDNF file. The error may also arise if the file you are inspecting has been transferred across hardware platforms.
Nothing to import
You have deselected everything.
Cannot autodetect Source Package
If the AUTO option is on, the header of the Input file does not contain the Source Package information. The mapping table information has to be set by hand.
Auto-detection of SDNF Formats
The system can automatically detect which version of the file you are inputting.
You can set up the default SDNF format version in the SDNFUserData.pmlfnc file, the default version of which can be found in the SDNF\dflts\user\SDNFPML\functions folder in the user data folder. The !!SDNFSDNFVersion variable must be precisely one of the two suggested text strings.
You can inspect the file header as before and an added line indicates which SDNF version it has found.

If you change the version setting, the system does not work because it is expecting a file of a radically different format. However, the interface fails in a controlled manner producing a "catch-all" error message.

If you manually select the wrong SDNF version, you may also get an error message in the log file about syntax errors in the incoming file, indicating that the Packet 0 records are different.
Import file does not exist
File specified does not exist.
Not an SDNF File
File specified is not an SDNF file. The error may also arise if the file you are inspecting has been transferred across hardware platforms.
Nothing to import
You have deselected everything.
Cannot autodetect Source Package
If the AUTO option is on, the header of the Input file does not contain the Source Package information. The mapping table information has to be set by hand.
  -- Default SDNF file format
  -- currently |2.0| or |3.0|
  !!SDNFSDNFVersion    = |3.0|
Note:
If you do not input the full path name, the input file is assumed to be in the folder from which started the application. You can also include system environment variables in the path name as long as they are in the proper format, for example, %ENVVAR% being the representation of the ENVVAR environment variable.
Note:
You cannot import Packet 40 (Connection Details) with this version of the interface. The interface checks that you are attempting to Import something if both options are unchecked.

Technical Information
Import Information
Import Information
Browse
Note:
Technical Information
Auto
Source Information
Source Information
Input File Header Details
Import Information
Packet 10 (Linear Members)
Packet 60 (Curved Members)
Packet 20 (Plates)
Packet 22 (Holes)
Note:
Import Information
OK
Cancel
Error and Log File Messages
Import file does not exist
Not an SDNF File
Nothing to import
Cannot autodetect Source Package
Auto-detection of SDNF Formats
SDNFUserData.pmlfnc
SDNF\dflts\user\SDNFPML\functions
!!SDNFSDNFVersion


Click Run Information to display the Import Run Information window which allows you to view the Log File after the import process is complete, select the Log File? check box.

Click either the Brief or Verbose option buttons to choose which format messages are displayed.
As part of the Import process a reference model is constructed against which comparisons are made. Save Reference Model allows you to keep this. Otherwise it is deleted on completion of the Import process.
After the Import merging process has been performed, you can sort all new items into FRMW (Framework) elements according to their Material type. Select the Sort on Material Type check box.
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 SDNF system configuration compares all the relevant data transferred in the SDNF file between the models. However, you can select which attributes may be ignored by the comparison process, click Edit Attribute Comparison List.

Using this window you can deselect attributes for comparison but must be aware that strange results may occur especially if you ignore positional and rotational attributes.
Finally, there are two validity checks that you can perform on the incoming data which make sure that a subsequent Import run has a chance of success. Activating these options overrides completely the Import choices made on the main window. With these validity checks you are able to view a log file before any data is merged whatsoever.
Profile Mapping? enables you to view if the incoming Linear Member Profile specifications are successfully mapped between systems. The transaction is relatively fast as the SDNF file is passed through the external program without any subsequent import or comparison in the application. You are then able to view 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 drop-down list enables you to check for duplicate numbers in the incoming model. There are three options: NONE, NEW and GLOBAL. NONE deactivates the drop-down list and no checks are made. The import process just goes through unhindered. The NEW option allows you to check only the new imported items for duplicate mark numbers, while the GLOBAL option enables you 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 have been input on the Run Information window, click OK and the interface variables are updated. Click Cancel to close the window, leaving the original interface variables unchanged
Note:
The reference model is deleted next time you Export or Import anything. Also, it may not be a complete model as some items may already have been transferred into the main model on merging.

Run Information
Import Run Information
Log File?
Brief
Verbose
Save Reference Model
Note:
Sort on Material Type
Edit Attribute Comparison List
Profile Mapping?
Duplicate Mark
NONE
NEW
GLOBAL
NONE
NEW
GLOBAL
Run Information
OK
Cancel


On the Import window the Members list can be used to navigate around the database hierarchy.
You must state where the Imported model is to be located. The location must be a SITE, ZONE or STRU element. Using the Members list, navigate round the database to the correct storage location and click Store in: CE. The window text indicates where the Imported model resides. If there is not enough space on the window, 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, you can control how the Import process is to proceed.
You 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. Refer to Comparison and Merge Processes for further information.
Compare ( + Merge ) imports the model and compares the reference model with the location chosen to be the storage area. At this point you are asked whether to merge the models. Click Yes to continue with the merge process and complete the Import.
Compare + Merge just goes through the complete Import process. For example, the import, comparison and merging are completed without any interaction. The action is only to be performed if you are absolutely sure that the outcome is correct.
Merge from File takes a merge command file produced during the current session only and imports it directly into the model. The reference model must not have been deleted beforehand. Otherwise, you may lose any elements added to the model by the external detailing package. The option is very quick and there are no system checks.
Error and Log File Messages
Bad element type
You are not trying to store imported data at a SITE, ZONE or STRU element.
Bad element type
You are not trying to store imported data at a SITE, ZONE or STRU element.
Import and Cancel
The Control item on the Import window has just one option, Exit, which removes all forms and menus and global variables associated with the interface.
Cancel closes the Import window.
Import executes the Import process. As it proceeds you are kept informed of the progress.
Import Bar Menu
The Control item on the Import window has four options: Re-initialize, Configure, Mapping Convertor and Exit. If you change any mapping files or any other variables:
Re-initialize reloads these files to save you having to rebuild the whole User Interface from scratch.
Configure enables you to define run parameters, model parameters, display colours and environment parameters. Refer to System Configuration for further information.
Map Converter starts the tool that helps you rebuild Profile mapping files, refer to External Mapping Files for further information.
Exit command removes all forms and menus and global variables associated with the interface.
The General item has one option, Highlight which displays the Highlighter window enabling you to identify new, changed and deleted items in the model.
Bad element type
You are not trying to store imported data at a SITE, ZONE or STRU element.
Note:
These options may be completely overridden if you want to perform a validity check as on the Run Information window.

Comparison and Merge Processes
External Mapping Files
Import
Store in: CE
Store in: CE
Operations
Note:
Run Information
Comparison and Merge Processes
Compare ( + Merge )
Yes
Compare + Merge
Merge from File
Error and Log File Messages
Bad element type
Import and Cancel
Import
Exit
Cancel
Import
Import
Import Bar Menu
Control
Import
Re-initialize, Configure, Mapping Convertor
Exit
Re-initialize
Configure
Map Converter
External Mapping Files
Exit
General
Highlight
Highlighter


Click OK to check the fields in the window for validity:
After verifying that all the data is correct and valid, the external program is called. The interface waits for a certain time until the program is finished. The amount of waiting time is configurable. If there are errors raised by the external program you are 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 even exist. You are asked if you want to carry on waiting for another time unit.

Click Yes and the interface waits for another period of time. Click No to stop the interface where it is. Finally the system indicates its completion, whether successful or not. The completion message should be read in conjunction with the log file, if any errors are indicated.
You are alerted to unsuccessful runs by the external program displaying an error message, after which the process exits.

If the external program successfully completes, the processed SDNF file is imported into MODEL. Any reference data which may have been retained is deleted.
The status line informs you 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 is 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 you have chosen to be asked whether to Merge after the Compare operation, a Confirm window displays.

Click Yes to continue with the Merge process.
Click No and the Import process skips the Merge process, you are then given a chance to store the Merging commands in a file for use later only in the current session. You cannot use a file from a previous SDNF session as the Import data may be incorrect.

You can save the Merge command file and then be prompted whether to view the Import log file. The Merge command file may then be used in the Merge from File option on the AVEVA SDNF - Import window. The latter option needs the reference model from this run to be kept. Therefore, some other options become unavailable.
If you have merged the models, you are then asked if you want to keep the reference model, verifying the option selected on the Run Information window.
This reference model will not be the complete model as imported as various attributes and elements might have been modified, deleted or moved around.

Finally, you are then asked whether to view the log file, if you have chosen that option on the Run Information window.

If you want to inspect the log file, you can save it with the File > Save as option in the SDNF File Viewer window which displays a File Browser, or click Save as to the suggested filename. If the file exists, you are asked if you want to overwrite it. The log file window can then be closed, click Cancel.

If you have chosen Brief mode on the Run Information window for displaying the log file, the window displaying the log file filters out all warning messages, leaving only the error messages. To save the log file, however, all messages are be retained in the file.
If you click a line containing an application reference number, the chosen item displays in all graphical views. The interface also navigates to the item in the database, allowing you to perform further queries or operations.
Error and Log File Messages
File does not exist
Somehow there is no log file. Are there issues regarding access rights to the %AVEVA_DESIGN_WORK% folder?
Input file name not specified
Something strange here. The name of the macro generated has been forgotten.
Import file does not exist
Something strange here. The macro file has not been generated or it has been deleted, or is not found in the expected folder. Are there issues regarding access rights to the %AVEVA_DESIGN_WORK% folder?
Data store unset
The data store variable is unset or the SITE you had intended to store the imported data in is invalid. Has it been deleted since you set the store variable?
File does not exist
Somehow there is no log file. Are there issues regarding access rights to the %AVEVA_DESIGN_WORK% folder?
Input file name not specified
Something strange here. The name of the macro generated has been forgotten.
Import file does not exist
Something strange here. The macro file has not been generated or it has been deleted, or is not found in the expected folder. Are there issues regarding access rights to the %AVEVA_DESIGN_WORK% folder?
Data store unset
The data store variable is unset or the SITE you had intended to store the imported data in is invalid. Has it been deleted since you set the store variable?

File does not exist
Somehow there is no log file. Are there issues regarding access rights to the %AVEVA_DESIGN_WORK% folder?
Input file name not specified
Something strange here. The name of the macro generated has been forgotten.
Import file does not exist
Something strange here. The macro file has not been generated or it has been deleted, or is not found in the expected folder. Are there issues regarding access rights to the %AVEVA_DESIGN_WORK% folder?
Data store unset
The data store variable is unset or the SITE you had intended to store the imported data in is invalid. Has it been deleted since you set the store variable?
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?
Is the storage location valid?
Is the storage location valid?
Is there a valid input file?
Is there a valid input file?
Do we need to convert the file across platforms?
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?
Are the Profile and Material mapping files valid for the Source Package as identified in the Header of the input file?
Note:
This calculation can be useful when considering the maximum input file size, the size applies to this file, and not the original SDNF source file.

OK
Yes
No
Note:
Confirm
Yes
No
Merge from File
AVEVA SDNF - Import
Run Information
Run Information
File > Save as
Cancel
Brief
Run Information
Error and Log File Messages
File does not exist
Input file name not specified
Import file does not exist
Data store unset


The Import, Comparison and Merge process involves three stages. First, the model is imported. You then have the option of comparing the imported model with the original model, after which you may merge the new data into the old model, or the comparison and merge process can be performed as one with no interaction. Though you can tell the system to Import, Compare and Merge the model straight away this should only be performed if you are sure of the end result. It is advised that you Compare the models first and inspect the results before Merging.
You can decide to keep the imported reference model, but are 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 is 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.
The Comparison Process
There are three conditions the AVEVA SDNF looks for:
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. The 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 clones imported when the import store location is not the same as it was for the export process.
The diagram illustrates the route through which the data is imported, compared and merged. New items are green, changed items are orange and deleted items are red.

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 moved to another SITE to enable you to recover them if necessary. So parts of models can be merged into the original model with no loss of data.
The Comparison process allows any potential changes, additions and deletions to the original model to be detected and enhanced in a 3D view, if there is one present and if the items are in the current Drawlist.
As for both Linear Members and Plates you can select which attributes are significant for Comparison. The Comparison Checklist window which is a child of the Import Run Information window allows for this. By default, all the attributes transferred through the SDNF file are compared.
Compare Linear Members
The detailed data attributes are compared between the original model and the reference model:
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 you are told what the old value was and the new value is so that you can view how the model has been changed. Details about the brief log file format are available. Refer to Brief Format for further information.
You may get a lot of apparent changes which may be caused by the failure to map the profile types between systems. The log file indicates which profiles have not been mapped. It is advised that you resolve 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 in the incoming model with existing Plines that have been mapped onto them.
Compare Plates (PANE)
The detailed data attributes are compared between the original model and the reference model:
Vertex positions are compared to within the user definable tolerance as described in the section on user customization 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 you are told what the old value was and the new value is so that you can view how the model has been changed. Details about the brief log file format are available. Refer to Brief Format for further information.
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 the application. 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.
Merge Process
Refer to Comparison and Merge Processes for further information. The diagram illustrates the route by which information is transferred from the Import, through the Comparison and on to the Merging processes.
The AVEVA SDNF 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.
You can separate the Comparison and Merging processes, so that you are able to view the log file in between operations. If you choose the Merge from File option on the main SDNF Import window, the Comparison process is deemed to have been completed and all that remains to be done is the actual Merging. The reference model for the current session must still be available. You are prompted for confirmation.

If, during the Merge phase, items are to be merged, the lists of added and deleted items are reconciled with the original model - by being deleted or transferred from the 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 you have chosen the Sort on Material Type option on the Import window, any new items are sorted into FRMW groups according to their material type as specified by the :SDNFMGRADE attribute.
The version numbering system is described. Refer to Technical Information for further 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 transfers 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 you 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 Import window. The components of this name are:
the system prefix
identification of new element container
the current MDB, for example, /DEMO
the current user name, for example, SYSTEM
the current Transfer letter, for example, 'A'
the current revision number, for example, '1'
You would be able to find all the added items to this MDB at this version.
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. The separation of operations allows you to view items that are deleted during the Merge process. Before deletion the objects are changed in colour so that they may be identified.
'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 with the added items, the STRU is named out of components, thereby enabling you 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:
/SDNF-
the system prefix
OLD-
identification of new element container
<mdb name>-
the current MDB, for example, /DEMO
<user name>-/
the current user name, for example, SYSTEM
<transfer nr>.
the current Transfer letter, for example, 'A'
<revision nr>
the current revision number, for example, '1'
/SDNF-
the system prefix
OLD-
identification of new element container
<mdb name>-
the current MDB, for example, /DEMO
<user name>-/
the current user name, for example, SYSTEM
<transfer nr>.
the current Transfer letter, for example, 'A'
<revision nr>
the current revision number, for example, '1'
You would 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 nnnn contains transient data
The reference SITE is likely to be deleted some time.
Model comparison completed
Process was successful.
Failed to compare models
Do they both exist?
WARNING: Reference SITE nnnn contains transient data
The reference SITE is likely to be deleted some time.
Model comparison completed
Process was successful.
Failed to compare models
Do they both exist?

/SDNF-
the system prefix
NEW-
identification of new element container
<mdb name>-
the current MDB, for example, /DEMO
<user name>-/
the current user name, for example, SYSTEM
<transfer nr>.
the current Transfer letter, for example, 'A'
<revision nr>
the current revision number, for example, '1'
/SDNF-
the system prefix
OLD-
identification of new element container
<mdb name>-
the current MDB, for example, /DEMO
<user name>-/
the current user name, for example, SYSTEM
<transfer nr>.
the current Transfer letter, for example, 'A'
<revision nr>
the current revision number, for example, '1'
WARNING: Reference SITE nnnn contains transient data
The reference SITE is likely to be deleted some time.
Model comparison completed
Process was successful.
Failed to compare models
Do they both exist?
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.
items in the imported file that are not in the original model - Added items;
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 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.
items that it can match between the imported file and the original model and checks for modifications - Changed items.
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
Start and end of Pline defined by Cardinal Point
Start and end of Pline defined by Cardinal Point
Orientation and Beta angle
Orientation and Beta angle
Specification Reference
Specification Reference
Start and End releases
Start and End releases
Material grade and reference
Material grade and reference
Hold and Paint Spec UDAs
Hold and Paint Spec UDAs
Fireproofing data
Fireproofing data
Position, orientation
Material grade and reference
Hold and Paint Spec UDAs
Panel loop height and justification
Number of vertices
Fireproofing data
Position, orientation
Position, orientation
Material grade and reference
Material grade and reference
Hold and Paint Spec UDAs
Hold and Paint Spec UDAs
Panel loop height and justification
Panel loop height and justification
Number of vertices
Number of vertices
Fireproofing data
Fireproofing data
Note:
The Reference Model which is created is named according to the user session, so that several Reference Models can coexist at the same time. As they are named according to session, you are advised to take care to manage them and not to leave too many versions around to fill up disk space.
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 Model you may find the order of vertices to have been reversed. Model is more tolerant about the ways in which you can define a plate.
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 Model since the initial Export process had taken place.

Brief Format
Brief Format
Comparison and Merge Processes
Technical Information
The Comparison Process

Added
Deleted
Changed
clones
Note:
Comparison Checklist
Import Run Information
Compare Linear Members
Brief
Verbose
Brief Format
Compare Plates (PANE)
Brief Format
Note:
Merge Process
Comparison and Merge Processes
Merge from File
Import
Sort on Material Type
Import
Technical Information
Additional Items
Store in:
Import
/SDNF-
NEW-
<mdb name>-
<user name>-/
<transfer nr>.
<revision nr>
Deleted Items
Note
:
/SDNF-
OLD-
<mdb name>-
<user name>-/
<transfer nr>.
<revision nr>
Changed Items
Error and Warning Messages
WARNING: Reference SITE nnnn contains transient data
Model comparison completed
Failed to compare models


As has been described in Comparison and Merge Processes there are two validation checks that can be performed prior to the full import and merging of models.
The first option is for profile mapping. The Profile Mapping? check box on the Run Information window turns this on. The Import process initializes 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, you can check that there are not any duplicate external mark numbers. Duplicates can quite easily come about if you copy members in the external detailing package without creating unique mark numbers for them. When they are imported into the application, the Comparison process may fail as it can 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 log file may also list any problems with the mapping tables. So this option is actually a combination of this and the validity checking option.
Refer to Sample Validity Check Log File for further information.
Highlight Changes in the Design
From either the Import or Export windows, select General > Highlight from the top of the window to display the Highlighter window. The window allows you to identify in a graphical window whatever you want, either according to Import date, or by Transfer/Revision number combinations. The By option button switches the window into the appropriate mode. Both options work from the start element selected and indicate only those items that are in the drawlist.
Highlight by Import Date
The window allows you to choose what to enhance on the screen according to the Import Date of an item.

The Selected items box part of the window allows you to select any combination of Added, Changed, or Deleted Items for identification, according to the date range.
By selecting the inclusive dates defining the limits of the range using the From and To date drop-down lists you can locate on the screen those items in the current drawlist which have been changed, added or deleted.
Highlight by Version
The window allows you to choose what to indicate on the screen according to the Version of an item.

The rules of selecting the changed, deleted or added items are the same as Highlighting by Import Date.
By selecting the versions defining the limits of the range using the From and To version drop-down lists you can identify on the screen those items in the current drawlist which have been changed, added or 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.
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.

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.
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 you want to view what has been '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 you want to view what has been 'deleted'.

Comparison and Merge Processes
Sample Validity Check Log File
Comparison and Merge Processes
Profile Mapping?
Run Information
NEW
GLOBAL
NONE
NEW
GLOBAL
Sample Validity Check Log File
Highlight Changes in the Design
Import
Export
General > Highlight
Highlighter
By option
Highlight by Import Date
Selected items
Note:
Highlight by Version
Note:
Error and Warning Messages
Bad date input
Bad version input
Nothing to highlight


The test can be performed after installing the AVEVA SDNF product to make sure that the installation is complete and correct. The test must follow immediately the Export test described. Refer to Test AVEVA SDNF Export for further information. All the required testing material can be found below the sub-folder SDNF\test\results\export in the user data folder.
Take the SDNF file exported in the export test and modify it in a text editor. While referring to the description of the SDNF format. You can modify, for example, a mark number, a material and positions. Comparing the files SDNF-Test.sdn in the SDNF\test\results\export and the SDNF\test\results\import folders, which is found in the user data area, gives you some examples of edits that can be tested. Make sure that the resultant SDNF file is valid SDNF. Save the modified file under a different name, or in a different folder.
The test described imports an SDNF model file.
Initial Configuration
Enter Model. You should have write access to the database to enable you to import the new data. The interface records the date and time of import as well as the revision numbers of the elements transferred.
Set the test project variables:
Select the Structures application.
Choose the SITE to import from SDNF by selecting SITE /TEST-SDNF-INTERFACE from the hierarchy list and drag it into the 3D view.
When that is finished, bring the SITE into view by adjusting the view limits. Refer to Limits for further information.
If required, modify the 3D view. Refer to Views for further information.

Prepare to Import
The Import window allows you to import a steel structure from a SDNF file.
You may be asked to install a Configuration details element. If so, accept the request.

On this window and associated windows, you need to fill in the details prior to Import.
Source Information
Click Source information on the Import window to display the Source Information window.
Select the Auto option button and select AVEVA from the list of Source Packages on the Source Package drop-down list on the right hand side of the window. The system automatically detects the Source Package's Profile mapping table and Material mapping table.
When the details are correct click OK.
Import Information
Click Import information on the Import window to display the Import Information window.
In the file name field, input the full path name of the modified source file.
Select which SDNF Packets to import: Packet 10 (Straight) and Packet 20 (Plates).
When the details are correct click OK.
Run Information
Click Run information on the Import window to display the Import Run Information window.
Select the Log File? check box and choose Verbose for the message mode to get a verbose log file.
Select the Save Reference Model? check box in order to safe any reference model.
Finally, you need to sort any new members added to the model by material type. Select the Sort on Material type? check box.
A validity check on the incoming data, prior to importing it, can be performed.
When the details are correct click OK.
Main Import
Select the SITE into which the SDNF file is to be imported. Select SITE /TEST-SDNF-INTERFACE in the Members list and click CE by Store in:.
A two stage import is then performed. Comparing the models first before Merging. So, select the Compare (+ Merge) option button.
The Import window should now look similar to this.

Import the SDNF File
On the Import window, click OK.
The status line keeps you informed of the progress of the task.
After the first stage of Import has taken place, you are asked by a Prompt window with the message. SDNF Interface (Confirm) - Model comparison completed. OK to merge models?. Click Yes to continue with the Merge process.
When the process is complete a Confirm window is displayed.

You are then asked if you want to inspect the log file. If you do, you can save it with the File > Save as option in the SDNF File Viewer window to display a File Browser, or click Save as to the suggested filename. The log file window can be closed by the Cancel.
Check the log file against the changes made in the source SDNF file. The file should list the differences, changes, additions and deletions which have been made in the file.
Compare Imported Model with the Original
Prior to performing this test, you can copy the /TEST-SDNF-INTERFACE as a reference model to /ORIG-TEST-SDNF-INTERFACE. The reference model can be used to visually compare the imported model with the original. You can do this by adding the original model to the Drawlist in a different colour so that it is superimposed on the modified model. You can then inspect the 3D view closely for the differences recorded in the log file.
You 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 folder.
Perform a Validity Check
If you want to perform a validity check on the incoming data before it is imported, display the Run Information window from the main Import window. Select GLOBAL for the Duplicate Mark Number search criterion. Click OK and fill in all the details on the main Import window.
Once all the details are correct on the Import window, click OK. The validation process is performed and in due course you are 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 folder.

Test AVEVA SDNF Export
Limits
Views
Test AVEVA SDNF Export
SDNF\test\results\export
SDNF-Test.sdn
SDNF\test\results\export
SDNF\test\results\import
Initial Configuration
Model
Limits
Views
Prepare to Import
Import
Source Information
Import
Source Information
Auto
AVEVA
Source Package
OK
Import Information
Import information
Import
Import Information
OK
Run Information
Run information
Import
Import Run Information
Log File?
Verbose
Save Reference Model?
Sort on Material type?
OK
Main Import
CE
Store in:
Compare (+ Merge)
Import
Import the SDNF File
Import
OK
SDNF Interface (Confirm) - Model comparison completed. OK to merge models?
Yes
Confirm
File > Save as
SDNF File Viewer
Save as
Cancel
Compare Imported Model with the Original
SDNF-Test-Mrg.sdn
test/results/import
Perform a Validity Check
Run Information
Import
GLOBAL
OK
Import
Import
OK
SDNF-Test-Vfy.log
test/results/import


You should be aware of certain technical information, which is not immediately specific to AVEVA Products, in order to get the best out of the interface.


SDNF - Structural Steel Detailing Neutral File Format

All of the related Packets must be output at the same time. You 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 non blank character.
Lines, apart from the Packet identifications, are free format delimited by spaces, 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. The SDNF interface attempts to transfer non-ASCII characters where appropriate, but warns if any characters with their 8th bit set are written to an SDNF file.
Export/Import different SDNF Formats
The interface can read SDNF files in both version 2 and version 3 of the format but write to only version 3.
Auto-detection of SDNF Formats
The system can automatically detect which version of the file you are inputting, you should need to do no more.
You can inspect the file header as before and an added line indicates which SDNF version it has found.

Packet 00 - Title Packet
Packet 00 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:

repeat Record 11 as stated in Record 10
Packet 10 - Linear Members
Straight Linear Members are the elements represented in Model by SCTNs and the straight segments of multi-segment GENSECs - straight prismatic profiles. They are described in the SDNF file.

There are several ways of defining a Linear Member using different combinations of the data elements, some of which are not interpretable by other systems. The method of interpretation of these fields is defined.
Location of Linear Members in Space
Close and rigorous study of the definition of Linear Members in SDNF reveals 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 determine the 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:
Record 4 is ignored completely - (2D X/Y offsets)
The Start and End cutbacks (Record 3) are ignored by default but can be enabled. Refer to Linear Member Cutbacks for further information.
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 can be determined. AVEVA SDNF would export this value, but does not do anything with it on import.
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.
Packet 20 - Plates
Plates are represented in the application by PANE elements as loops on the upper and lower faces.

Each plate is represented by a variable number of records:

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.

Rules of interpretation apply to the 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. This can cause confusion on import when the plate's origin has appeared to have changed. The more important thing is to see if the plate is in the same place.
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, in turn determining the local Z axis. The Y axis then becomes the vector cross product of the Z and X axes.
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:

Sometimes, holes have been allocated to the wrong plate, this can be because the plates do not have a unique identifier.
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.

Packet 30 - Member Loading
Loading of elements is not transferred by this interface.

No loads along the member are catered for.
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 explained. The record structure is:

The description is purely textual, no geometry is passed, for example, sniping.
Packet 50 - Grid Packet
Grid Packets are not transferred in this interface.

Packet 60 - Format Definition

For the succeeding records, each arc member is represented by the 11 records, total of 11 times n records, where n is number of members from Record 2 (376 in the example).

Note:
The Issue Code (Record 8) holds the Source Package of the SDNF file.
Note:
The sense of this eccentricity is a vector from the end of the member to the node position.

Linear Member Cutbacks
th
Export/Import different SDNF Formats
Auto-detection of SDNF Formats
Packet 00 - Title Packet
Note:
Packet 10 - Linear Members
Location of Linear Members in Space
Linear Member Cutbacks
Note:
Rotation and Orientation Vector
Packet 20 - Plates
Order of Vertices
Plate Origin
Plate Orientation
Packet 22 - Holes
Packet 30 - Member Loading
Packet 40 - Connection Details
Packet 50 - Grid Packet
Packet 60 - Format Definition


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


The diagram illustrates the positions of the Intergraph FrameWorks Cardinal Points. FrameWorks cannot handle Cardinal Points above Point 10, but for this interface it is expected that all interfaces in this project are able to handle all 14.
On transfer between systems, the Cardinal Point imported should be retained for later export. A source of confusion can be when a member originally laid out on Cardinal Point 14 (Top of Steel) is returned on the Cardinal Point 10 (Neutral Axis). It causes minor problems in model versioning and comparisons.


Cross referencing models is the mechanism by which you can identify members in different models other than by visual comparison. There are two scenarios: one where an element is created in Model; the other is where it was created in any other system, but is to be imported into Model. 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.
Element created in Model
When an element is created in Model it gains a unique internal reference number of the form "=<integer>/<integer>", for example, =13/2305. On export from Model this value, excluding the initial '=' character, is 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 you to identify the Design member in the external steel detailing package.
On Export back to the application, for any member which has this Mark attribute set, the original imported Mark value appears again in the SDNF file. Thus you are able to spot any changes to the model. The AVEVA SDNF Import system, then allows you 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 Model, retain their logical relationships to the steel members.
Element created outside Design
A member created outside Model does not have the Mark field set to be an application internal reference number. The AVEVA SDNF 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 SDNF detects that there are duplicate external mark numbers as it is preparing to export a model, the internal reference number is used in preference. The SDNF interface then has some chance of identifying the element if it returns from the external package. Refer to Issues Concerning Entity Comparison for further information.

Issues Concerning Entity Comparison
Element created in Model
Element created outside Design
Issues Concerning Entity Comparison


The SLH application provides a bespoke database architecture of SLH elements comprising of administrative elements.
The elements are the high level administrative elements that are owned by the existing STRU hierarchy element, the elements, with their easily identifiable element type definition, supports the ‘Assembly’ type concept employed throughout the application where all of the detailed 3D modelling is represented using the existing structural objects such as Gensec, Panel, and Template. For a detailed explanation of the elements, refer to the Structural Design User Guide. Throughout the application, the workflow associated with the creation and modification of the elements follows a consistent format through a common user interface.

Structural Design User Guide


The SLH elements of Stair Flight, Step Ladder, Rung Ladder and Handrail are all POS/ORI elements whose hierarchical ownership is that of a STRU. The SLH elements should be considered as fabrications in their own right as they in turn own specific objects fulfilling an engineering function whose naming convention reflects the engineering function.

The elements have been architected to suit specific functionality and workflow to provide definite engineering purpose and their attributes set accurately mirrors the engineering criteria for that object. The attributes are evaluated by the system in response to the user’s interaction with the 3D model environment and the relevant attributes are managed through the database hierarchy by the SLH application.


For more detailed information regarding Application Data Worlds sets refer to the Design Reference Manual Creating the Model.
Application Data Worlds and their elements assist applications to store assemblies and 3D model parts for copying and propagation within a design. They have some similarities with Templates, but are more general in content.
They are used for SLH assembly data and also by the Piping discipline.
The elements available are administrative elements allowing applications to organize data storage areas of design objects that are not part of the design itself, but supplementary objects used to create and maintain the 3D model. They are not accessed (unless specifically instructed to do so) when performing 3D model queries such as clashing, mass properties, collections and they are similar to catalogue and in particular Template definitions.

Design Reference Manual Creating the Model


The Stair Flight element (STRFLT) is a top level administrative element owned by a STRU element.
The STRFLT as a steelwork assembly enables the user to create a rule based linear Stair Flight and it introduces a middle tier hierarchy to enable the decomposition of the STRFLT assembly into its logical component parts, the existing lower level elements of GENSEC and PANEL are used to represent the detail of the 3D model.

Stair Stringer (STRSTR)
STRSTR owns the two GENSEC elements used to model the main supports of the Stair Flight. The GENSEC elements are automatically miterd by the application at the upper and lower elevations of the STRSTR, dependent upon the relevant Selections.
Route Path (RPATH)
The Routing Path element defines an open path or closed boundary using the following:
Route Point (POINTR)
POINTR elements are significant point references which form the RPath.
Top Extension (TOPEXT)
TOPEXT owns the PANEL element used to model the physical representation of the top extension of the stair flight. It is defined by the extrusion of a profile representing the panel's shape (the Panel Loop. PLOOP) through a given distance (equivalent to the panel thickness). A PAVE element defines each vertex of a Panel Loop.
Bottom Extension (BOTEXT)
BOTEXT owns the PANEL and Stringer elements used to model the physical representation of the bottom extension of the stair flight. It is defined by the extrusion of a profile representing the panel's shape (the Panel Loop. PLOOP) through a given distance (equivalent to the panel thickness). A PAVE element defines each vertex of a Panel Loop.
Intermediate Landing (INTLNG)
INTLNG owns the PANEL and Stringer elements used to model the physical representation of the intermediate landing of the stair flight. It is defined by the extrusion of a profile representing the panel's shape (the Panel Loop. PLOOP) through a given distance (equivalent to the panel thickness). A PAVE element defines each vertex of a Panel Loop.
Tread Set (TREADS)
The TREADS element is used to manage the ownership of individual TREAD elements.
Tread (TREAD)
TREAD owns the elements used to model the rise or tread in the STRFLT. The vertical position between the Tread is measured from Top of Plate to the next Top of Plate and represents the Rise attribute on the STRFLT.
PANEL, TMPL or Catalog elements can be used to model the rise or tread in the STRFLT.
Description of Stair Flight Elements
The following figure shows some of the attributes of the STRFLT elements and the elements that it owns. The figure also indicates the engineering significance of the attributes to the geometrical representation of the STRFLT.

Upon creation of the Stair Flight the system analyzes the horizontal (Overall Going) and vertical (Overall Rise) distances between the Lower and Upper Work Points (LWP/UWP) and validates these positions against the engineering criteria of the Stair Flight to the criteria of the current specification. If the system analysis validates the values against the engineering criteria the system creates the Stair Flight and populates the attributes with the appropriate data.

Free form sketching
Tracing existing profiles or boundaries.
Free form sketching
Free form sketching
Tracing existing profiles or boundaries.
Tracing existing profiles or boundaries.

Stair Stringer (STRSTR)
Route Path (RPATH)
Route Point (POINTR)
Top Extension (TOPEXT)
Bottom Extension (BOTEXT)
Intermediate Landing (INTLNG)
Tread Set (TREADS)
Tread (TREAD)
Description of Stair Flight Elements


The Step Ladder element (SLADDR) is a top level administrative element owned by a STRU element.
The SLADDR as a steelwork assembly enables the user to create a rule based linear step ladder and it introduces a middle tier hierarchy to enable the decomposition of the SLADDR assembly into its logical component parts, the existing lower level elements of GENSEC and PANEL are used to represent the detail of the 3D model.

Stair Stringer (STRSTR)
STRSTR owns the two GENSEC elements used to model the main supports of the Step Ladder. The GENSEC elements are automatically miterd by the application at the upper and lower elevations of the STRSTR, dependent upon the relevant selections.
Tread Set (TREADS)
The TREADS element is used to manage the ownership of individual TREAD elements.
Tread (TREAD)
TREAD owns the elements used to model the rise or tread in the SLADDR. The vertical position between the Tread is measured from Top of Plate to the next Top of Plate and represents the Rise attribute on the SLADDR.
PANEL, TMPL or Catalog elements can be used to model the rise or tread in the SLADDR.
Top Extension (TOPEXT)
TOPEXT owns the PANEL element used to model the physical representation of the top extension of the step ladder. It is defined by the extrusion of a profile representing the panel's shape (the Panel Loop. PLOOP) through a given distance (equivalent to the panel thickness). A PAVE element defines each vertex of a Panel Loop.
Step Ladder Rail (SLRAIL)
SLRAIL owns the GENSEC elements used to model the rails of the Step Ladder.

Stair Stringer (STRSTR)
Tread Set (TREADS)
Tread (TREAD)
Top Extension (TOPEXT)
Step Ladder Rail (SLRAIL)


The Ladder element (RLADDR) is a top level administrative element owned by a STRU element.
The RLADDR as a structural assembly introduces functionality enabling the user to create a rule based RLADDR and also introduces a middle tier hierarchy to enable the decomposition of the RLADDR into its individual assemblies of Stringers, Rungs, Safety Cages. Throughout the middle tier hierarchy the elements owned by GENSECs are used to represent the detail of the 3D model.

Rung Ladder (RLADDR)
The Ladder element (RLADDR) is a top level administrative element owned by other SLH administrative elements i.e STRU, FRWM and /or SBFR.
Rung Ladder Cage (RLCAGE)
The RLCAGE element is an administrative element which owns the Cage Segment (CAGSEG) element.
Cage Segment (CAGSEG)
The CAGSEG element owns the GENSEC and PANEL steelwork elements used to model the physical representation of the cage. By default, there are two cage segments, one representing the entry/exit at the top of the ladder and the other representing the remainder of the cage itself. This mechanism allows the entry/exit detailing of the cage to be modified individually from the remainder of the cage.
Ladder Stringer (LDRSTR)
The LDRSTR element is an administrative element which owns the appropriate number of GENSEC steelwork elements used to model the main supports of the rung ladder.
Ladder Rung Set (RUNGSE)
The RUNGSE element is an administrative element which is used to manage the ownership of individual LDRRUN elements. This is dependent upon the design of the rung and is intended to support a variety of rung types.
Ladder Rung (LDRRUN)
The LDDRUN element owns the GENSEC, PANEL or catalogue elements used to model the physical representation of the rung.

Rung Ladder (RLADDR)
Rung Ladder Cage (RLCAGE)
Cage Segment (CAGSEG)
Ladder Stringer (LDRSTR)
Ladder Rung Set (RUNGSE)
Ladder Rung (LDRRUN)