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.
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.
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.
Forward migration is usually relatively smooth with ARCHICAD nowadays, but if it’s paired with some hotlinking and IFC export then the new features might cause some confusion.
Two of the latest additions to ARCHICAD are the introduction of Classification Systems and the improved IFC Translator settings, which both provide a lot of opportunities and smart management functions for the user, but during migration+hotlinking+IFC export they will need some extra cautiousness, otherwise the user might get unexpected results. Even though this might not be a mainstream case, we just had a few support issues in Singapore because of this, so let me give a generic explanation, hoping to clear up the confusion as much as possible 🙂
In this article I will be focusing on a simple example to demonstrate RH-GH-AC live connection, another wonderful OPEN BIM workflow from GRAPHISOFT. We will start with an input from a ARCHICAD (AC) file and based on that input a set of balconies will be created using Grasshopper (GH) which is running on top of Rhino (RH). There is not much use of RH but we need Rhino to run Grasshopper.
Make sure all the three applications (AC, RH and GH) were installed along with live connection add-on from GRAPHISOFT running.
Refer to Grasshopper ARCHICAD Live Connection 1.5 User Guide from the following link:
Chapters to focus:
- Getting Started
- Launch the Applications
- Start the Connection
- Grasshopper Palette in ARCHICAD
To understand this exercise there is a need for basic understanding of Grasshopper. Please refer to the following links:
Input from AC
- In ARCHICAD create a simple building with 10 Story + Roof. Set the Story to Story height as 3000 mm. Create a Complex Profile for the railing as well. Alternatively download the file from the link here.
- Use Line tool to draw a line from point P1 to P2, suggest to draw the line in 2nd Storey.
- Select the line just drawn using the Arrow tool.
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.