Structural Analysis Detection from BIM
Converting IFC BIM Models to Structural Analysis
Last updated
Was this helpful?
Converting IFC BIM Models to Structural Analysis
Last updated
Was this helpful?
Within the Geometry Gym tool kit is an engine for automated structural analysis detection which allows for the conversion of BIM models to Structural Analysis. and also IFC allows for automated structural analysis detection, which ****allows for the conversion of a IFC model into a structural analysis model.
Geometry Gyms Structural Detection engine aims to solve 2 problems:
Where no analytical model exists within an IFC export create an analytical model.
Once an analytical model does exist, perform snapping operations to ensure a well connected model.
If an analytical model exists within the .ifc file you can choose to either choose to use it or create a new one from the BIM elements.
We do provide tools for Revit which automate the process of Revit directly to Structural Analysis programs. The primary process is explained below, but for Revit specifics please see page below:
The .ifc file type allows for a structural analysis model definition to exist within an IFC file. This is similar to say the analytical model in Revit if you are familiar.
A lot of authoring programs such as Revit, Tekla, etc do not include the Structural/Analytical model when exporting an IFC file and also provide fairly primitive tools to control it and ensure a well linked model. Typically because a lot of the time it is also not the purpose of the model itself, it may be for documentation or shop detailing purposes.
The Geometry analysis model snapping process completes a series of operations in order to provide the user with a well linked structural analysis model.
The snapping process performs the following steps in order:
Inclusion/Exclusion Element Filters
Member Aggregation
Column Placement, Splitting and Snapping
Member Placement, Splitting and Snapping
Assigning of Restraints (if Applicable)
You may never get a 100% snapped model but the more you can improve this process the less time spent manually adjusting models down stream.
Depending on the nature of the IFC
When exporting directly from Revit you can easily select whether a member should be included in the structural analysis output by deselecting.
To enhance the snapping procedure and allow greater user input we define an element aggregation procedure prior to the conversion taking place. Currently this is not exposed to the user (i.e the user cannot explicitly select how a member can be aggregated) and we do this automatically for the following member types.
Brace
Column
Primary Member
Secondary Member
Purlin
We currently separate the elements by some defining features apparent in the IFC. For example, it is checking whether 'brace' or 'bracing' is defined in the either the instance name or type name. The best way to ensure your members are aggregated correctly is to ensure that authoring of member TYPE designations (i.e IfcMember.BRACE).
For exporting with Revit. You can learn more about this here.
Currently the plan node seek value is used in a couple of instances throughout the snapping process. In the first instance it is used to determine whether a node should be snapped to one of the projection planes and also guides some of the calculations for intermediate node creation along members when selected. Secondly, it is used to check whether an element end point is within the distance of a node in the model. In this instance it is not a true 'plan' node seek but a 'proximity' node seek. This applies to all members except for column elements.
If the element has been defined as a Brace element then this value is overridden with the inputted brace value.
You can include
*****
*****