OPEN BIM Coordination – Northing and Easting Values in ARCHICAD and REVIT

Decided to re-visit coordinate settings for projects that requires IFC exchange between ARCHICAD and Revit in this blog. In my previous blogs the focus was only on Latitude(Lat) and Longitude(Long). I received some requests to handle Northing and Easting (UTM) as well. To address that I tested the settings of both ARCHICAD and Revit and share the result via this blog.

Before going into how to do the settings we need to understand how both tools work and various coordinate systems available for us to use.

Read More

Advertisements

Quick Tip for Publishing Hotlinks in Large Projects

Just recently came across this issue that unit modules were meant to be linked into a block file, but due to the large amount of small variations within the units, the designers wanted to have a base module to link into the unit file as well, such as:

Module A is linked to the Units file onto different stories. In the Units file, small variations are added to the base A, which eventually results in Unit A1, A2, etc. Similarly with Unit type B, C and so on. Eventually the Unit file was linked story-by story into the Block file.

Though from attribute management point of view such amount of hotlinks is not easy to manage, the designers preferred this solution to deal with the frequent design changes of the 30+ unit types. At the end of the linking process the problem was, that since the Units file already contained more than 20 hotlinks, the total number of links significantly increased in the master file, which caused slowness in general, for scheduling, for updating the links and so on. If the Units file could have been a single file without previously added links it would have been much easier to handle. To overcome this issue, a tiny, but very powerful function of the Publisher was activated: Break nested Hotlinks and Xrefs.

37_embed links.png

Whenever publishing modules – in this case every story that contains one unit type was published as a separate module -, using the embedding function under Options… allows us to get rid of the excess links. At the same time the designers could still use the Units file for doing their work, but the process was not hindered later either.
As an additional benefit, the published modules only need to be linked once into the further files (typical stories or directly into the block), whenever there is an update, they just publish again with a click and update the links.

Labeling IDs of Surfaces and Building Materials

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.

screen-shot-2017-02-02-at-14-00-46 Read More

Tekla Project Base File for the Structural Team

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.

tbf01

Read More