Welcome back everyone. It’s been awhile! ☺
The past six blogs were about implementing the structure of IFC within the functionality of Autodesk Revit and talking about IFC in its conceptual data model form.
It’s now worth noting that we need to package up the data model so that it can be exchanged. IFC can be exchanged in several different formats which can be viewed here. The most commonly used format is STEP (SPF) and when we say ‘IFC file’ we actually mean a STEP file.
For this post we will look at the remaining items which are needed to be configured before you hit the export button to create an IFC STEP file. I’m not going to go through all the settings of the IFC exporter just the ones I have tested and use. A list of all the settings can be found here.
This blog post together with the next one have been based on the testing done in Autodesk Revit 2019 and we are still using IFC 2×3. Autodesk have been working hard to improve bugs therefore there could be changes/improvements in later versions.
Welcome back everyone ☺
I hope you’ve all had fun testing the workflows in the previous blog posts. As I’ve explained IFC provides a good basic method of structuring information, we should think of this as the default way which should be used across every project and every information management activity.
In addition to this there will be other ways in which information needs to be ordered to enable further identification, better understanding, different uses, or even for certain software. This post is all about how we can add additional ways of allowing information to be ordered. Continue reading
In the last blog post we looked at IFC attributes which allows you to add certain basic information about IFC entities. However, we need to be able to add much more information (such as performance) to entities, to do this we use properties. Continue reading
In blog post 01 we described what Attributes are and listed the four core ones:
In this blog we are going to skip the main section on Attributes (see the next blog) and focus on one specific Attribute the Predefined Type as this is closely related to Entities.
In blog post 01 we explained that Predefined Types were the next level below Entities in determining what something is. Continue reading
In the last blog I had a bit of moan and we learnt about some basic IFC principles. In this blog we’re going to take what we have learnt and apply it to the world of Revit. Therefore, if you haven’t read it please do so.
I wanted to start by giving a friendly warning – this isn’t for the faint hearted. In fact, I’ve heard it described as black magic, performed by wizards with the patience of saints. Continue reading
After a year at Bond Bryan Digital and to coincide with our new website, it’s time I rolled up my sleeves and finally started blogging. For those who don’t know me my name is Emma and I’m an Autodesk Revit user. I’m a technician by trade and the more I used Revit over the years the more I craved structure to my information to get the best out of the software and my models. This is why I started to look at standards and ways of implementing them within Revit. In particular openBIM standards like Industry Foundation Classes (IFC) because I want my information to be as useful as possible to everyone who needs it, now and in the future. Continue reading
Models are often exchanged between different stakeholders working on projects. Model authors and those using the models use a variety of software for their own needs. In order for BIM to work it is imperative that geometry and information are exchanged reliably between each software tool. Continue reading
There are a number of things to understand when exporting an IFC model. What is often misunderstood is that an IFC file is not simply one file. IFC files are exported for different purposes so when issuing an IFC file it is important to understand the purpose of the exchange. Once you understand the needs of the recipient you can begin to filter your model for different uses. Continue reading
One of the challenges faced as we move into this brave new world of information is what information we want users to complete within their models. When you first start looking at data it can be fairly daunting trying to work out what is and isn’t required. Of course we could leave this to individual users but then this creates inconsistencies between individuals, offices and projects. Without creating a standard approach it also makes it harder to set up standardised schedules and provide consistent training. Continue reading