You are currently reviewing an older revision of this page.
Microstran 09.20.01.32 is now available on Bentley SELECTServices Online:
http://selectservices.bentley.com/
Note also you will need the latest version of Structural Synchronizer (ISM) installed as well:
http://www.bentley.com/en-AU/Free+Software/structural+synchronizer.htm
This article discusses the primary enhancement in this release: ISM Interoperability
As shown in the above schematic, all applications can have bidirectional interoperability. Microstran is the latest addition to family of ISM Interop products.
ISM has its own post here, its Key Features are:
Microstran supports the following ISM functionalities.
Download and Extract the exercise files locally on your machine.
You have just created your first ISM repository, you can now read this into Bentley ProStructures, STAAD, STAAD Foundation, AECOsim Building Designer or any other ISM enabled products.
We have just brought in an ISM Repo into Microstran, so now we can bring in models from any ISM enabled product.
Select Update and you will be prompted with a Commit Message Dialog. You can enter what you have done since the last commit.
In ISM enabled application, we modified the ISM Repo by deleting a member, we then want our Microstran file to reflect this change.
We will use the ISM Editor to do the modification .
During ISM Operations, user may want to adjust the settings to achieve desired results.
For ISM Update commands, the program checks to see whether Microstran members and support correspond to a particular ISM member and support via distance tolerances. If this value is too small, it may not find corresponding members when performing update functions. If it’s too large, it may erroneously consider a member to be “identical”.
Show Change Management: This indicates whether Structural Synchronizer will appear, once the “Start” operation is commenced.
Commit Message: if Show Change management is set toFalse. Then the ISM Repository will be updated/created with the commit message in this field
Connectivity Tolerance – This tolerance defines how close two members’ physical locations need to be to trigger the generation of nodes connecting the two members. The distance calculation is performed with 3D volumes, not simplified member lines and polygons. Setting this value too large will result in unwanted nodes (or unwanted members attached to wanted nodes). Setting this value too small will result in missing nodes (or nodes without appropriate members attached). This value is typically set to be a little smaller than the distance between the two closest members that should not be connected.
Node Merging Tolerance – This tolerance defines how close two nodes can be before they are merged into a single node. See also the Member Based Node Merging section below.
Plane Tolerance – This tolerance defines how far from a member’s plane a node can be while still being considered as “near” the member’s plane. Nodes will not be moved further than twice this value.
Node Member Separation Factor – This is a multiplier of member size that defines how far the node can be from the member. Where two members are connected, the value is multiplied by the sum of the two member sizes. This value is typically left as 1.0.
If you noticed disconnected members in Microstran when doing a “New From ISM Repository”, try running again by increasing the Connectivity Tolerance. This value is basically how far do end members have to be before they are deemed to be connected by a common node.
You as the engineer have ultimate control to what you commit to the repository.
For any update operations, you can select which items to commit to the repository.
Green items being added to repository
Blue items in the repository that has been modified
Red items removed from the repository
Notice the status and Change Column, you can select each item and either Accept, or Reject them. After which, you can preview the changes via the preview button. Make sure the click the Update Button once completed.
ISM Revisions Management
Within Windows Explorer, Select the ISM Repository you want to investigate, Right Click à Manage ISM Repository Revisions
Note that ISM is more than just a file format, it is a platform for visualization and change management. Of particular significance is the ability to query the differences between any two revisions in the repository by using the Diff command.
The following describes a workflow utilizing the newly added ISM capabilities.
View “Diff” between 2 versions, provides robust version management solution to your structural modelling.
Microstran Design Members correspond to ISM physical members. You will notice that when performing “New From ISM Repository” or “Update from ISM Repository”, Microstran will have initialized design members. They are always defaulted to the design code AS4100.
Reactions: If you would like your ISM Repository to contain reaction information (STAAD Foundation Advanced), then you need to export your reaction files to the same folder as your Microstran file prior to any ISM Operations. Remember to do this whenever analysis results are updated.
Member Sets: Members in ISM Repository can store the “use” of a member, i.e whether it’s a Beam, Column, Brace, etc. This information can be transmitted by taking advantage of Microstran Sets.
By default, all members in Microstran are placed into the ISM Repository via its centroid. Often times, it is desirable to have these placed via TOS (Top Of Steel). This can be achieved by placing members into a Microstran set and naming the set with particular keywords. Below table illustrates this:
Member Types
Key words in Microstran Set Name
Ism Section Insertion Point
Beams
rafter, beam, bm
CentroidTop --> Top of Steel
Columns
Col, cl
CentroidCentroid
Horizontal Brace
Brace; Horizontal, hor, H-, H_
Vertical Brace
Brace; Vertical, vert, V-, V_