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
As many of you who read this blog regularly know, Bond Bryan Digital promote open standards wherever possible to exchange information between different project stakeholders. The primary methods of exchange we utilise on our projects are PDF, XLSX, IFC, COBie and BCF (and DWG if we really have to!). Many are still sceptical about information exchange using certain formats. This is particularly true of IFC (Industry Foundation Classes) which is described by ISO16739:2013. The truth though is that the IFC schema is not really to blame. The issue is that the exchange is often poor because of either poor implementation of the schema by vendors or poor implementation by users. Continue reading
When I had the original idea for the LEGO series one of the main goals was to demonstrate how open standards could be used throughout the project. Many of these processes are well documented and shared amongst the BIM community. However, little is available on how information is exchanged into Facilities Management (FM) software. Part of my aspiration for the blog was that we could use the LEGO model to demonstrate a little of this digital handover process. So the question is: What does that design and construction information from a BIM process actually look like in an FM tool? Continue reading
We have seen in previous posts specific views of the model. However one difference with a 2D approach is being able to share models with others so that they can view the model geometry and/or data without needing any authoring tools themselves. Continue reading