I recently found a post on LinkedIn discussing the possibilities of labeling an abbreviation (ID or code) of elements, mainly the Surfaces. Since there is no perfect solution, two main ideas emerged other than using external label objects: use Labels along with Properties or IFC mapping. Though the first may seem to be easy to set up with ARCHICAD 20, it has its risks when it comes to change management since the Properties are not tied to other attributes that may change (for example Composite or Surface) unless you ALWAYS use Favorites, so let’s have a look at the Label tool options and the attributes instead.
The MEP Modeler gives good results when it comes to Collision Detection, but sometimes it is not that easy to identify the actual collisions despite the highlight options, especially if the project is larger. Let’s see an example and a quick enhancement of the representation.
This post is a follow-up of previous post Project Base Files for Coordination. In case the Structural team decided to use Tekla Structures for their BIM authoring then they need a Project Base File in Tekla with setup based on Architectural file.
Architectural Project Base File
Setup the Architectural Project Base File in ARCHICAD and export as IFC file as discussed in the post Project Base Files for Coordination.
This post is to follow up on a request for explanation of each step on the post Project Base Files for Coordination. Let me write this post to further explain the steps.
Why there is a need for Project Base Files?
As mentioned in the post Project Base Files (PBF) are project specific templates in various tools used for BIM authoring.
- PBF consists of Location, Orientation, Grids and Levels. These information can be based on national standards or agreed settings by the entire project team through BIM Execution Plan (BEP).
- This is to make sure everyone (BIM Authors) start with the right foot.
- This will ease the co-ordination process when the models from different BIM authors (disciplines or trades) are merged together.
- This is to represent the real world condition of the entire building (including all disciplines) virtually.
This post is to follow up on the previously published ‘Syncing Zone Cover Fills and Floor Finishes’ article where we mapped the Cover Fill value of the Zones to a custom made IFC property and made it appear in the Zone Stamp, this way saving some time, but most importantly reducing the risk of human errors when the user has to manually update the Floor Finish parameter of the Zones.
We also faced a minor (?) problem: since the naming convention of the Fills is diverse, not all Fills can be used right away to be displayed with their names as Floor Finishes. For example all ‘Pavement xx’ fills should only show ‘Pavement’, instead of showing the full name, including the version number.
Splitting the IFC Mapping rules is a way to solve this problem. A similar case where rule splitting was involved for the Zone Names has already been presented on this blog by Chidam, this post intends to give some detailed explanation on the rule splitting particularly, so it is easier to embrace it. IFC Mapping is NOT ONLY for model exchange purposes!
Place a Ramp Object
I felt it is good to share some software specific tips and tricks in between my posts focusing on interoperability. In this post I am sharing a tip on how to create guard walls (parapets) along the edge of a curved ramp using Morph Tool and Solid Element Operation.
Place a ramp object with the settings as shown in the below image and switch to 3D window (press F5).