BIM Server Upgrade to BIMcloud Basic

Along with the arrival of ARCHICAD 22 comes a big change in Teamwork as well, the BIM Server is replaced with BIMcloud Basic, which is a great step towards better compatibility (no need for matching builds) and allows the individual updates of ARCHICAD and the BIMcloud Basic components. The overall functions remain the same and the fully-fledged BIMcloud will retain its name as well.

title

Even though it is only a name change from the users’ point of view,¬†and the GRAPHISOFT Help Center also has an article on the upgrade process briefly here, it is worth going through the update process – I will show the before/after stages below.

Read More

Advertisements

Custom Curtain Wall Junctions

Creating custom components from scratch using the default tools and saving them as objects is a relatively simple way to extend the content libraries thanks to the File/Libraries and Objects…/Save Selection as… command. However this menu doesn’t list Curtain Wall Junctions as an option.
As ARCHICAD 22 is on the way with its improved Curtain Wall functions, it is worth going through the trick of converting an existing SketchUp component for example into an ARCHICAD Curtain Wall Junction. (The method is the same when modeling it from scratch with ARCHICAD tools.)cwj14

Read More

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

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.