Hello!

Did you know that logged in users can see a lot more content?

Smart3D Interoperability

Last updated June 25, 2019 by Steel Extensions tekla.extensions-steel@trimble.com

Software version: 
2016
Environment: 
Not environment-specific

Smart3D Interoperability

Contents

Purpose and description
System requirements
Installation
Applications and Components menu
Version history
Usage
Export to Intergraph Smart™ 3D
Creating or editing a subset
Import from Intergraph Smart™ 3D
Additional information
Traffic items
Member Global Unique Identifiers (GUID)
Grids
Known limitations of this version
 

Purpose and description

The Smart3D Interoperability tool is supported for all Tekla Structures configurations, to provide full interoperability with the Intergraph Smart™ 3D plant design system from Intergraph. Interoperability is provided via the CIS/2 (CIMSteel2) data exchange method, a very common format in the structural steel industry. 

System requirements

Tekla Structures and Intergraph Smart™ 3D 2009.1 to 2018.

Please ensure that Intergraph Smart™ 3D is up to date with the latest service releases or hotfixes.

Installation

The extension is available in a *.tsep (Tekla Structures extension package) format.

To install the *.tsep based extensions to Tekla Structures (available in Tekla Structures 2016 to 2019) from Tekla Warehouse:

  1. Download the extension from Tekla Warehouseservice for collaboration and for storing and sharing Tekla Structures content

    In Tekla Warehouse the content items are stored in collections. Tekla Warehouse includes the Tekla Warehouse Service and the Tekla Warehouse web site.

    Tekla Warehouse is one of the Tekla online services.

    .
  2. According to which browser you are using, when the file has been downloaded either the Tekla Structures extension manager will open automatically or you may need to right click on the downloaded file and choose the 'open' option.
  3. The Tekla Structures extension manager dialog will be displayed and will show a list of installed Tekla Structures versions compatible with the extension. Choose the versions you wish to install to by selecting the check boxes next to each version's name, then click 'Import'. You may be asked to accept the License.
  4. The extensions will now be queued for installation to the selected versions. The installation will happen the next time that version is started.

To install a saved *.tsep extension package to additional Tekla Structures installations:

Having downloaded a *.tsep based extension, that file may be saved and installed on multiple Tekla Structures installations:

  1. To import from a running Tekla Structures:
    1. Open the Applications & Components menu and from its 'Access advanced features' button menu select 'Extension manager...' which will open the manager dialog.
    2. Click on the 'Import...' button and browse to the extension you wish to install.
    3. The chosen extension will be added to the import queue for the running version and installed when Tekla Structures is next restarted.
  2. To install from the file manager menu:
    1. Browse to the saved file, right click on the file and select 'Open', the Tekla Structures extension manager dialog will be displayed.
    2. Choose the version(s) to install to and click on 'Import'.
    3. The chosen extension will be added to the import queue for the version(s) selected and installed when Tekla Structures is next restarted.

 Applications and components menu

The extension is accessed from the Applications & components menu. The installer creates a group called 'Smart3D Interoperability' in the root folder with icons for the extension components. If you wish to customise the menu, the two Smart3D Interoperability components may be added to any new or existing groups in the normal way. To remove the automatically created Smart3D Interoperability group it is necessary to locate the file catalog filefile that defines catalog information used by Tekla Structures

Catalog files have the extension .bin, .db, or .inp, for example.

installed as part of this extension and remove it (this will also remove the descriptions of the components so you will need to provide your own). That file is located in the Environments\common\extensions\Smart3DInteroperability folder and is called Smart3DInteroperability_ComponentCatalog.ac.xml. Note that renaming the .ac.xml part of the name will cause it to be ignored too.

Version history

This extension has been the subject of a process of continuous improvement and problem fixing as detailed below.

Version 8.3 for Tekla Structures versions 2016 to 2019, released 7th June 2019.

Fixes and enhancements:

Version 8.3

  • The batch export function now allows multiple files for export based on the project filter settings.
  • Added the ability to see the export status while processing in batch mode.
  • Export and import now have an option to use local coordinates or basepoint.
  • The user may now define the exported assembly and member type.
  • When plates or slabs are exported, from Tekla Structures, the part type is now correctly entered into the assembly_design_structural_member_planar as either PLATE(1) part that represents a flat structure

    (1) In some contexts, for example in analysis, the term plate object may be used to refer to plates.

    (2) plate that represents a steel structure

    (2) Plate is mainly used as a connection piece or as a floor plate.

    or SLABplate that represents a concrete structure

    In Tekla Structures, a slab is created by picking three or more points.

    Slab may be part of a floor, for example.

    .
  • The ability to import and export systems with hierarchy elements has been added.
  • Improved macrosaved series of actions that includes instructions for a program

    Macros are located in the applications and components catalog. They are recorded or created manually and stored as .cs file in a folder defined with the advanced option XS_MACRO_DIRECTORY.

    Macros can, for example, be used for creating drawings or reports.

    Macros are sometimes used to run an application.

    icons.
  • The import revision gridmodeling aid that represents a three-dimensional complex of horizontal and vertical planes

    In Tekla Structures, grids are used as an aid in locating objects in a model. The grid is shown on the view plane by dash-and-dot lines. It is also possible to show grids and grid line labels in drawings, and to modify grid properties in the drawings.

    It is possible to have more than one grid in a model. For example, a large-scale grid for the entire structure, and smaller grids for some detailed sections.

    now shows the GUID of deleted items.
  • Imported part ‘control volume’ placeholders used to display the location of traffic items, imported without reports, now contain any associated part UDA’s.
 
The enhancements listed are detailed further in the Usage section below.

Version 8.2 for Tekla Structures version 2016, 2016i, 2017, 2017i and 2018, released 28th March 2018.

Fixes and enhancements:

Version 8.2

Export to Smart™ 3D

  • Enhancement to export connection / component part user defined attributes.

     
Version 8.1

Export to Smart™ 3D

  • Modification to export the assembly position numberposition number that is assigned to an assembly or a cast unit

    .
  • Fix to ensure the model grids are exported when the user selects export selected objects.
  • Fix to ensure that the updated member part number is always exported.

   

Import to Tekla Structures
  • Fix to resolve an import crash and incorrectly orientated plate members.
  • Fix to ensure that grids with elevation are visible in the view.
  • Fix to ensure that the import revision grid correctly displays the objects unique identifier.
  • Modification to correctly round trip the design part name.

       
Version 7 (msi installer) for Tekla Structures versions 20.1, 21.0 and 21.1 released 26th April 2016.
Version 7.0 (tsep installer) for Tekla Structures version 2016 released 16th June 2016.

Fixes and enhancements:

  • An updated mapping file has been added (US imperial now fully mapped to the Smart™ 3D sections).
  • Modifications to clarify that void ‘Antimaterial’ does not need to be mapped in the section / grade mapping utility.
  • Fix to ensure members with offsets are correctly imported.
  • Fix to resolve an import crash when members have offsets lengths equal to the member length.
  • Fix to resolve an export crash when a radial grid has no Y and Z labels.
  • Several fixes to ensure plate voids are correctly exported, including, when the view display has ‘cuts and materials’ set to off and when selected objects are exported.
  • Improved error reporting when importing a plate with more than 100 contour points.
  • The extension version is now written to the Smart3DInteroperability.log file.
  • Resolve several extension startup issues (due to issues with duplicate user attribute data).
  • Improvements to the import of elipses to ensure they are correctly rotated.
  • Improvements to allow the export of non-circular voids with chamfers.
 
Version 6 released 11th November 2015.

Fixes and enhancements:

  • Enhanced the warning message to inform users that imported unmapped sections may result in member positioning errors.
  • Now exports the selected value, rather than the index number, for option type user defined attributes (see additional information in the known limitations section).
  • Resolved an export failure by supporting the import and export of user defined attributes with spaces in their reference names.
  • Resolved an export failure by supporting grids with duplicate labels.
  • Improved error handling to deal with incorrectly created voids in Tekla Structures (extrusion length of zero or no contour points).
  • Now includes an identifier (GUID) in the warning message for voids that fail to import.
  • The import revision grid now identifies deleted voids as ‘Deleted void’ in the differences column.
  • Data and time information is now provided in the import revision grid for all deleted items.
  • General fixes and stability improvements made to address import and export issues with several models.

 
Version 5, released 29th May 2015.

Fixes and enhancements:

  • Correct import void creation errors, apparent when the Smart™ 3D model has duplicate member part name identifiers.
  • Correct model re-import errors in the wizard revision grid for voids. The revision grid was incorrectly reporting unchanged voids as being modified.
  • Modify handrails to have a variable number of mid rails specified via the new, Smart™ 3D 2011R1 and 2014, traffic item reports.
  • Improve the layout of curved handrail end treatments by ensuring the upright section is vertical.
  • Improve the revision grid reporting of deleted elements when reimporting the conceptual traffic items only.

Version 210.4 released 31st March 2015. Versions 201.4, 200.4 and 191.4 released 1st April 2015.

Fixes and enhancements:

  • Support for the new Smart™ 3D 2011R1 and 2014 traffic item reports.
  • Use of additional traffic item reports data (from Smart™ 3D 2011R1 and 2014) to improve the setting out of handrails.
  • Support for international characters (Russian, Chinese etc.).
  • Modifications to prevent the import and export of illegal xml characters.
  • Addition of Indian, Canadian, Japanese, Cyrillic and Latin Russian profile mappings.
  • Corrections to the placement of traffic item stair treads.
  • Correct errors in the revision grid for round tripped models (sections being incorrectly flagged as new).
  • Ensure that connection plates and cleats are not round tripped.
  • Modifications to ensure that imported grids with a global elevation greater than zero are visible.
  • Correct use of bearing axis and direction (in the Smart™ 3D grid report) to rotate the imported grid.
  • Imported circular plates and voids created using chamfer points (rather than faceted).
  • Support for the export of part cuts.
  • Support for beam and column void export.
  • Translatable user interface.
  • Improvements to the calculation of the handle (cardinal point) locations for exported, connected curved members (available with Tekla Structures v21.0).
  • Error message added to warn the user if the stair setting out plane calculations have failed.
  • Error message added to warn the user if the contour point calculations have failed.
  • Automatic removal of temporary files placed in the Tekla Structures model during the import and export process.
  • Fix added so that circular contour platepart whose outline form the user defines by picking three or more points

    The user can define the shape of the contour plate parallel to the work plane. The profile in use defines the thickness. The corners of the contour plate can be chamfered.

    voids, created from 4 chamfer rounding points, will now be correctly exported.

 
Version 191.3, 200.3 and 201.3 released 19th January 2015.

Fixes and enhancements:

  • Revisions to the member user attribute importimport of user-defined attribute values to a model from a text file

    mechanism to allow attribute data to display in the member properties attribute data tab.
  • Modifications to stop the user selected group name being exported as a member attribute.
  • Modifications to improve the revision grid handling of member end connection codes. If a new Smart3D file is imported the wizard revision system will check the existing Tekla Structures model for member ends with a physical connection, if no connection is found the attribute data will be checked for end code information. When exporting from Tekla Structures, only the physical end type will be exported.
  • Fixed a bug that caused the wizard to crash when importing a file into a Tekla Structures model that contains plates with non-polygon based cuts.
  • Fixed a bug to prevent the creation of duplicate grids in Tekla Structures which would then cause a crash when a second import was run.
  • Modifications to the structure of the exported attribute data to improve member attribute assignment in Smart3D (including removal of TS_ prefix and assigning the attribute to the member assembly data).
  • Bug fix to enable the import of single poly beam curves into Tekla Structures.
  • Prevent duplicate messages being displayed on the wizard run progress control.
  • Allow negative values to be entered for the set and position the model originglobal coordinate system point of origin used for the model

    Model origin is the default project base point.

    points, text boxes, in the wizard UI.

 
Version 191.2, 200.2 and 201.2 released 29th October 2014.

Fixes and enhancements:

  • Curved beams are now imported, into Tekla Structures, as 3 point chamfer polybeams.
  • Help documentation added to the wizard.
  • Errors and warnings sent to the wizard progress page are now written to the log file.
  • The revision grid was incorrectly reporting differences for items marked as unchanged.
  • A warning is issued if a traffic item, in the stp file, has no matching entry in the csv file.
  • Removed unnecessary warning messages.
  • The mapping form 'Save Changes' button is now only enabled if changes have been made to the form entries.
  • Traffic item creation now occurs after the revision grid changes have been committed.
  • Check and report whether the plate contour points are acceptable for creation in Tekla Structures.
  • Correct the placement (cardinal points locations) of 2 and 3 point curved beams and columns.
  • Significantly improved speed and reduced memory usage of the wizard.
  • Plates, voids, curves and traffic items are now correctly handled by the revision system (previously round tripped plates and voids were deleted and recreated and curves were always imported as polybeams). 
  • Improved import and export error message reporting.
  • Automatically adjust the view depththickness of a slice of the model defined starting from, and perpendicular to, the view plane

    and fit the imported model to the view.
  • Ensure the import and export logs are consistent.
  • Ensure that the wizard shuts down if Tekla Structures is closed.
  • Fix to ensure anchor bolts and their associated nuts and washers are not incorrectly exported as cleats.
  • Support the import and export of grids.
  • Slabs with curves created by chamfers will now export.
  • Improvements to the behaviour of the 'Specify mapping dialogs' data grid controls.
  • Mapping file locations have been modified (to improve the multi-user experience and avoid any read / write issues).
  • It is now possible to import traffic items only (previously, this would cause the wizard to crash).
  • Slabs with more than one curve may now be imported.
  • Reset the contents of the StepTools Smart3DInteroperability_StepTools.log file for each import.
  • Improved general stability of the wizard (following canceled and restarted imports).
  • Ensure that the error log is undated when void creation fails.
  • Ensure that revised item attribute data is correctly checked and reported on in the import revision grid.
  • Use the correct units when describing the traffic item profiles in the mapping grid.
  • Concrete grades added to the mapping lists.
  • Enhance the 'Select user-defined attributes' dialog to allow the user to choose a group name from the attribute list.
  • Support added for handrail curved end treatments.
  • Slabs consisting of less than 3 linear sides are now supported (for example, one linear and one trimmed curve side).
  • Individual members that consist of multiple curves are now supported. 
  • The import and export of curved voids is now supported.
  • Improvements to the setting out of traffic items, including correcting the ladder width, raising the level of the stair stringers by half the stringer section depth and modifying the rail end stantion positions.
  • Curves are now exported using the CIS/2 trimmed_curve entity.
  • Support for the creation of curved handrails in Tekla Structure.
  • Improvements to the handling of parametric plate members. Parametric plates can now be modified, in Tekla Structures, following round trip modifications.  
  • Add a new item 'Import Date / Time' column to the import revision grid.
  • Prevent, unconverted, traffic item setting out volumes being re-exported from  Tekla Structures.

 
Version 190.1 and 191.1 released 16th December 2013.

  • First release.

Usage

Instructions on using the extension for exporting a model from Tekla Structures to Intergraph Smart™ 3D, or importing a model from Intergraph Smart™ 3D are detailed below.

 Export to Intergraph Smart™ 3D

Step 1 - Open the model, to be exported, in Tekla Structures.

Step 2 - Select the applications and components side pane and expand Smart3D Interoperability. The following icons will be visible:
 

Double click the Export to Smart™ 3D icon,

Step 3 - Export parameters wizard page.
 

Enter the appropriate details in the Export parameters wizard page:
 
File Name – Enter the preferred export file name. If no name is entered the default export file name will used, as shown. Note; if the export file name already exists in the export location the user will be asked, via a message box, whether to overwrite the file or not (upon pressing the next button).

Folder – Browse to the preferred folder destination. If no action is taken the default Tekla Structures model export folder will be chosen, as shown.

Export – This control has the following options:

  • All (the default setting); exports all model objects, in the model.
  • Selected objects; a user selection of model objects to be exported. To select the objects to be exported, pick the objects in the Tekla Structures model and click on the Export combo box arrow to toggle the selection.
  • Batch export (from version 8.3):
The Smart3D export wizard now contains an additional export option ‘Batch Export’. When Batch Export is selected a list of pre-configured model filters are displayed. The user can select from the existing filters or configure new filters, prior to running the wizard, and a batch export will be completed for each selected filter. The batch exported files will be placed in the model folderfolder that is used for storing files associated with a model

Tekla Structures stores all files associated with a model in a folder it creates with the same name as the model database (.db1).

In multi-user mode all users access the same model folder.

and be named as follows:

BatchMode_Name_Filter_name_model_name.stp

For example:

BatchMode_Name_Column_PlantModelRev1.stp
BatchMode_Name_Beam_ PlantModelRev1.stp

The wizard will report progress on each batch file export as it proceeds.

Use model objectobject that is represented in a model

A model object is either created in a model or imported into it.

/ Use basepoint (from version 8.3)

 

The user has the choice of whether to export or import the model relative to the model origin or relative to pre-defined project base points. Further information on setting project base points can be found here.

During export or import the user should select the Use basepoint option and a drop down list of preconfigured base points (set via the project properties) will be displayed. The user should then select the required basepoint and continue to export or import.


 

When completed, click next to proceed.

 
Step 4 - Select user-defined attributes dialog.
 

This page displays a summary of the user defined attribute data set on the members in the Tekla Structures model. By default, all the user defined attributes found are displayed and selected for export and the user may then choose which of the attributes to export by unchecking the tick box next to the attributes name. 

The Group name attribute combo box control allows the user to select a preconfigured attribute as the group name. This will ensure that the attribute data is loaded to the correct group when members are imported into Intergraph Smart™ 3D.

If a model is imported and the attribute group name has been previously set, in Intergraph Smart™ 3D, the dialog will display and re-export the existing group name.

 

User defined exported assembly and member type (from version 8.3)
 
TS member name
Exported assembly
Member type string in UDA                    
Step file output in ADSM
Beam
assembly_design_
structural_member_beam
JOIST BEAM
GIRDER BEAM
EDGE BEAM
EAVES BEAM
LINTEL BEAM
RAFTER BEAM
PURLIN BEAM
RING BEAM
SIDE BEAM
WALING BEAM
JOIST
GIRDER
EDGE
EAVES
LINTEL
RAFTER
PURLIN
RING
SIDE
WALING
Column
assembly_design_
structural_member_column
BATTENED COLUMN
BOX COLUMN
COMPOUND STRUT COLUMN
PORTAL COLUMN
BATTENED
BOX
COMPOUND
PORTAL
Brace
assembly_design_
structural_member_brace
CROSS BRACE
DIAGONAL BRACE
HORIZONTAL BRACE
KNEE BRACE
LATERAL BRACE
LONGITUDINAL BRACE
PLAN BRACE
RAKER BRACE
SWAY BRACE
VERTICAL BRACE
CROSS
DIAGONAL
HORIZONTAL
KNEE
LATERAL
LONGITUDINAL
PLAN
RAKER
SWAY
VERTICAL
Linear
assembly_design_
structural_member_linear
LINEAR BEAM
LINEAR COLUMN
LINEAR TRUSS
LINEAR BRACE
LINEAR SPRING
LINEAR CABLE
LINEAR PIPE
LINEAR WIRE
LINEAR TIE
LINEAR UNDEFINED
LINEAR ARCH
LINEAR BEAM COLUMN
BEAM
COLUMN
TRUSS
BRACE
SPRING
CABLE
PIPE
WIRE
TIE
UNDEFINED
ARCH
BEAM COLUMN
Plate
assembly_design_
structural_member_planar
 
PLATE
Salb
assembly_design_
structural_member_planar
 
SLAB

The exported assembly category (for example, assembly_design_structural_member_brace) is now defined by the name entered in the individual members name field, in Tekla Structures (table above). If the user does not set a recognised name the export wizard will analyse the part geometry and decide whether it’s a beam, column or brace.

The member type is set by choosing a member user defined attribute and setting a member type string (table above) that is applicable to the member category. So for example, for member name Beam, the user could select a user defined attribute and enter the string “JOIST BEAM”. When the export is started the user should then select the appropriate UDAobject property created by the user in order to widen the range of predefined object properties

User-defined attributes are used when the predefined object properties are not sufficient but more properties are needed. For example, comment, locked, and erection status are user-defined attributes.

that defines the member type, from the ‘User defined attributes to export user interface’, as follows:

The same user defined attribute field name, to define the member type, should be chosen for all members.

If the user sets a member type string, in the user defined attribute field, that does not match any of the recognised strings for the member name, then the member type information will be added to the step file as follows:
 

#22=ITEM_PROPERTY('extended_member_linear_type',$,
DESCRIPTIVE_MEASURE(stringer));

#17=ITEM_PROPERTY_ASSIGNED(#22,#25);

#25=ASSEMBLY_DESIGN_STRUCTURAL_MEMBER_LINEAR(1,
'630f291b-446e-4f59-9566-1aea2055de89','A/0','HEA300',0,$,.F.,.F.,$,$,.F.,
.UNDEFINED_ROLE.,.UNDEFINED_CLASSpart property that groups parts according to identifiers given by the user

The identifiers of classes are usually numbers. Classes can be used for defining the color of parts in the model, for example. Class does not influence the numbering of model objects.

.,.UNDEFINED.);

Note that the assembly will be defined as an assembly_design_structural_member_linear and the member type will be passed as an item property.

Smart™ 3D can be preconfigured to recognise these none standard member types (exported to an stp file in the above format). This allows the import, from Tekla Structures, of none step standard partsteel part that current model parts are compared with in the numbering process in order to give them specific part prefixes

types for, say, traffic items, rails, stairs and ladders etc.

The ability to import and export systems with hierarchy elements (from version 8.3).

Step files imported into Tekla structures, from Smart™ 3D, can have many levels of assemblies / part hierarchy. The imported member now stores the part hierarchy or assembly structure, as user defined attributes, and will correctly round trip this hierarchy.

To define a new structural system assembly for a part in Tekla Structures, set an appropriate assembly name in the part user defined attributes (for example, Assembly1) and select this attribute, during export, as follows:

The beam part assembly will be exported as follows:
 

#18=(
ASSEMBLY(0,$)
ASSEMBLY_DESIGN(.F.,.F.,$,$)
ASSEMBLY_DESIGN_CHILD((#21))
ASSEMBLY_DESIGN_STRUCTURAL_MEMBER(.F.,.UNDEFINED_ROLE.,.PRIMARY_MEMBER.)
ASSEMBLY_DESIGN_STRUCTURAL_MEMBER_LINEAR(.BEAM.)
ASSEMBLY_DESIGN_STRUCTURAL_MEMBER_LINEAR_BEAM((),(),.F.,.F.)
STRUCTURAL_FRAME_ITEM(1,'c2043f56-8474-4a17-bf61-9c3b72564f97','B/0')
STRUCTURAL_FRAME_PRODUCT('HEA300')
);

#21=ASSEMBLY_DESIGN(0,'Assembly1',$,$,0,$,.F.,.F.,$,$);

The current rules are as follows:

  • Newly exported parts from Tekla Structures can only be exported with one level of assembly.
  • Round tripped parts, from S3D, can hold as many assembly levels as defined in S3D. Any modifications to the assembly structure, using the procedure in Tekla Structures, defined above, will overwrite this round tripped structure.

If the user presses cancel the import will be cancelled. Press ok to proceed.

Step 5 - Processing wizard page.

This page displays an export process progress bar and textual information on the export process, including general information, warnings and any errors that have occurred. The user may cancel the import at any time by pressing the cancel button on the main wizard page (bottom right hand corner). This will enable the start and previous buttons, should the user wish to go back a step and change the wizard settings.

Step 6 - Specify mappings dialog.
 

This page allows the user to specify implicit mappings, between Tekla Structures and Intergraph Smart™ 3D profile, material or connection names. This will effectively map items in Tekla Structures to their equivalent item name in Intergraph Smart™ 3D.

The mappings dialog contains the following controls:
 

The mappings (top) grid – Displays the profiles, connections and materials to be mapped.
 
Mapped – Displays whether the item is mapped or not, via a tick box. The setting can be modified by the user.
Tekla Structures Name – The Tekla Structures profile, material or connection name. Upon editing, this control will display the profiles or materials via an appropriate cataloguser interface for displaying or modifying information in categorized lists

For example, profile catalog and shape catalog are catalogs.

dialog.
External Name – The Intergraph Smart™ 3D equivalent name.
Type – The item type, either profile, material or connection name. 
Standard – The relevant international steel standard.
Subset – The relevant standards subsets of profile or material mappings. Upon editing, this control displays the subsets via a drop down list.
Total number of unmapped items – a counter that shows how many unmapped items are present.   
The subsets (bottom) grid – Displays a list of available subsets.
 
Selected – Tick box to show which rows are selected. The user can manually tick or un-tick the boxes.
Type - Displays the subset type, profile, material or connection. Upon editing, this control displays the type via a drop down list.
Name – The subset name.
Standard – The subset standard.
Description – General details on the subset such as the country of origin and units used.
Subset Selection button – Provides the user with options to select all or deselect all subsets and add a new subset to the subsets grid
Search for Mappings button – Will initiate a search, through the selected subsets, for any mappings between the Tekla Structures and Intergraph Smart™ 3D profile, material or connection names. All successful mappings will be displayed in the top grid and the unmapped items counter will be updated.
Save Changes for Next Time button – Allows the user to save any changes to individual item mappings, modifications to existing subsets or any new subsets created.
The stored data can also be shared between other machines, simply locate the Smart3DMappings.xml file and copy to the same location on the machines requiring the same data.

The Smart3DMappings.xml file will be located in the installation folder (if no mapping changes have been saved);

<Program Files>\Tekla Structures\<version>\nt\bin\applications\Tekla\Model\Smart3DInteroperability

or in the current Tekla Structures model attributes (<model>\attributes\) folder, if mapping changes have been saved.
 

 Creating or editing a subset

The user can manually enter a new subset by clicking on the last row in the subset grid and entering the appropriate details. Once the relevant subset details are entered, click on a new row to commit the subset changes. The new subset added will now be visible in the subset drop down list accessed from the subset column in the grid. Press the 'Save Changes for Next Time' button to store the changes to the Smart3DMappings.xml file.

New profile, material or connection mappings can be added to new or existing subsets by manually entering details in the external name column in the top grid and selecting the required subsets in the subset column etc.

Subsets can be edited by simply selecting the relevant subset in the subset grid and making any changes required.

Note: if the user does not save changes made to the item mappings or subsets data the dialog will, following the ok button being pressed, issue a warning. This will prompt the user to either save the changes or ignore to continue, or cancel to return to the mapping dialog. If the user does not map all items a warning will be issued to highlight this to the user, with the option to continue (yes and use the source item values) or select no, to return to the mapping dialog.

Certain formatting rules are required and the mapping dialog will issue guidance and warnings if these are not adhered to.

Step 7 - Export status wizard page
 

This page contains the following controls:
 
Export Status report – Displays the contents of the export run log. All warnings, errors and general progress notes are displayed.
Open export folder button – Opens the folder that contains the file and highlights the exported .stp file.
 

 Import from Intergraph Smart™ 3D

Step 1 - Open the Tekla Structures model.
Step 2 - Click on the Import from Intergraph Smart™ 3D (right) toolbar button  .

Step 3 - Import parameters wizard page.

This page has the following controls:

Import File – Browse for the .stp file to import.
Do not set model origin  – The model will be positioned, in Tekla Structures, according to the coordinates specified in the imported CIS2 file.
Set model origin – The user may manually enter both the imported model origin, overriding that set in the imported CIS2 file, and the position of the model origin relative to the Tekla Structures global origin.
Auto find model origin – The import wizard will automatically find the imported model origin and the user can specify the location of the model origin relative to the global origin.
Set model origin / Position model origin at (x, y, z locations) – Used to specify the X, Y and Z global coordinates of the imported model origin and the position of the model origin relative to the global origin.

From version 8.3
 

Use model object / Use basepoint

The user has the choice of whether to export or import the model relative to the model origin or relative to pre-defined project base points. Further information on setting project base points can be found here.

During export or import the user should select the Use basepoint option and a drop down list of preconfigured base points (set via the project properties) will be displayed. The user should then select the required basepoint and continue to export or import.
 

Click Next to proceed.

Step 4 - The Processing wizard page.

See details for the model export, step 5.

Step 5 - The Specify Mapping dialog.

See details for the model export, step 6.

Step 6 - The Import processing wizard page.

See details for the model export, step 7.

Step 7 - Revisions wizard page.

    

 

The wizard compares the imported member GUID (Global Unique Identifier) to the GUIDs of the existing members in the Tekla Structures model and displays a revision status of the existing and imported model, as detailed below.

The revision grid

Import – Displays a user modifiable check box to determine whether the revision status found is applied. For example, the user may uncheck this control to ignore a ‘Delete’ status etc.
Revision Status – Set as new, modified, old or deleted:

New – The imported item does not already exist in the Tekla Structures model (row will be highlighted in dark green).
Modified – The imported member GUID matches the GUID of an existing member in the Tekla Structures model but the existing or imported version may have been modified (row will be highlighted in yellow).
Unchanged – An imported member GUID matches an existing member GUID in the Tekla Structures model and no differences between the two versions have been detected (row will be highlighted in white).
Deleted – An existing member in the Tekla Structures model does not match with any imported member (via the GUID) and will be deleted (row will be highlighted in red).

ID – The internal object ID.
GUID – Displays the imported objects Global Unique Identifier.
Differences – When any imported objects GUID matches an existing Tekla Structures model objects GUID, the wizard performs a number of checks on the objects geometry and attribute data to determine if any of the objects have changed. Any changes are displayed and include:

• Profile names.
• Handle positions.
• Centre line end positions.
• Rotation angles.
• End types.
• Material.
• All attribute data.
• Plates, the above plus vertices data, thickness and extrusion direction.
• Poly beam point data.
• 3 point curves, the above plus centre of curve, curve plane normal and curve radius.

Import Date / Time - All new and modified members, imported into the Tekla Structures model, are assigned an attribute that retains the import data and time. During subsequent model imports, to update the model, any modified member will display this date and time information providing limited member revision history data.

Revision Control Selection Options - This control contains a drop down list of the following commands:

Select All – Ensures that all the import check boxes, for each row in the revision grid, are checked, so that all actions specified under the revision status are adhered to.
Deselect All – Unchecks each rows import check box to ignore all actions specified in the revision grid.
Select All Members in Selected Rows – The user may highlight specific rows in the revision grid and ensure that the import check box is ticked for each selected row.
Deselect All Members in Selected Rows – As above to uncheck the import check boxes.
Zoom to Extents – Zoom to the Tekla Structures model extents.
Zoom to Member – Toggles the ability (on / off) to select a row / entry in the revision grid and automatically zoom to that member in the Tekla Structures model.

The model revision data supplied here can also be copied and pasted to Excel for further analysis.

The import button is pressed to commit the revision grid defined changes to the model. Cancel will close the wizard UI without committing any import changes. The previous button will roll the wizard back to the previous page and the start button will take the user to the first wizard page.

Once the import has been committed the user should click finish to exit the wizard.
 

 Additional information

 Traffic items

Traffic items, exported from Intergraph Smart™ 3D, with the detailed reports will be imported into Tekla Structures as native items. These reports are to be in .csv format and placed in the same location as the CIS2 file. Tekla Structures will generate handrails, stairs and ladders, to the specification detailed in the relevant .csv files and set out according to the control volume element passed via the CIS/2 step file. The csv files must be given specific names to be recognised by the wizard, as follows:
 
Structure Ladders Detailed Properties.csv
Structure Handrails Detailed Properties.csv
Structure Stairs Detailed Properties.csv
For the new traffic item reports from Smart™ 3D 2011R1, 2014 R1 and 2016:
 
For Detailing - Ladders Detailed Properties.csv
For Detailing - Handrails Detailed Properties.csv
For Detailing - Stairs Detailed Properties.csv
If the Intergraph Smart™ 3D exported stp file is imported into Tekla Structures without the corresponding csv reports, only the traffic item setting out volumes will be placed in the model. Any subsequent export of this model, from Tekla Structures, will not include the undetailed traffic item volumes.

 Member Global Unique Identifier (GUID)

If the model originated in Tekla Structures, upon first export, all members will assigned a GUID to enable tracking of the members. Similarly, if the model originated in Intergraph Smart™ 3D, all exported members will be assigned a GUID by Intergraph Smart™ 3D, the originating software.

 Grids

Tekla Structures will import both standard and radial grids specified in Intergraph Smart™ 3D. The grid file should be exported from Intergraph Smart™ 3D in csv format and placed in the same location as the stp file (to be imported). All grids exported from Tekla Structures will be in the Intergraph Smart™ 3D xml grid file format and will be exported to the export folder specified in the wizard (defaults to the current modelmodel that is active in Tekla Structures

The current model can be a single-user model, a shared model or a working model.

folder).

 Known limitations of version 8.3

• Currently there are no notches or miters passed into Intergraph Smart™ 3D.
• Newly exported parts from Tekla Structures can only be exported with one level of assembly.
• Round tripped parts, from S3D, can hold as many assembly levels as defined in S3D. Any modifications to the assembly structure, using the procedure in Tekla Structures, defined above, will  overwrite this round tripped structure.
• Partial slab penetrations are not supported.
Wallplate that represents a structure such as a wall or roof panel

In Tekla Structures, a panel is created by picking two or more points.

In cast-in-place concrete the term wall refers to a concept similar to panel.

elements in Intergraph Smart™ 3D are not supported, please export via IFCfile format commonly used in BIM that facilitates software interoperability

IFC is an open specification developed by the IAI (International Alliance for Interoperability).

Model can be exported into an IFC file.


• Handrails, with a corresponding report to convert to native Tekla Structures items, which may have more than 2 mid rails in Intergraph Smart™ 3D will be converted to show 2 midrails in the Tekla Structures model.
• Export of 2, 3 point and polybeampart of a certain shape that is created as a continuous chain of beams passing through points that the user picks

The segments of the polybeam are straight, but segment intersections can be curved. For example, a beam that follows a zigzag line is a polybeam.

curved members are supported but care should be taken when exporting or importing curves that are not on the XY or XZ plane.
• It is recommended that curve creation in Tekla Structures uses 3 point or polybeam curves, as these will export with the most accuracy.
• Twin profiles are not managed with round tripping as Tekla Structures will give each member its own GUID, upon passing back to Intergraph Smart™ 3D this will cause one member to be deleted.
• Export of circular voids or plates are supported for polyline, chamfer arc point and chamfer rounding defined profiles.
• Users may model Flats and PLT profiles, in Tekla Structures, as PLT10*150 or PLT150*10 and the rules within the profitab.inp will force the profile to be modelled as if it were a PLT10*150. These rules do not apply in Smart™ 3D, consequently the two profiles mentioned will be imported differently. If no prefix is used i.e. 150*10 the profile will be exported as 150*10.
• It is recommended that part user defined attributes, specified via the objects.inp file, use text boxes only for data entry. The use of, option type, combo box controls have several issues:
1. The Smart™ 3D user has no idea what the bounds of the data are or what increments can be set, should they wish to modify the UDA data.
2. If the Tekla Structures user specifies a reference name greater than 20 characters long the name will be truncated on export and thus the index of the chosen value rather than the actual value displayed will be used
 

Quick feedback

The feedback you give here is not visible to other users. We use your comments to improve our content.
We use this to prevent automated spam submissions.
Content rating: 
No votes yet