Exporting COBie Data from Autodesk Revit via IFC

Transcription

1 Exporting COBie Data from Autodesk Revit via IFC Autodesk supports two methods for creating COBie deliverables from Autodesk Revit: The first method is via a plug in for Autodesk Revit that assists the user in preparing their Models with COBie data and exports directly to both the United States and United Kingdom COBie spreadsheet standard formats. This COBie Extension for Autodesk Revit can be download from: The second method can leverage the COBie plug in for Autodesk Revit but instead of exporting directly to the spreadsheet, the data is exported to IFC using the FM Handover Extended Model View configuration option. FM Handover Extended Model view is also often referred to as COBie IFC. This solution is implemented in the IFC Open Source Exporter for Autodesk Revit. This can be downloaded from either: rforrevit2014%3aen Basic Steps for Exporting COBie Data from Autodesk Revit via IFC 1. Configure Autodesk Revit to use the Open Source IFC Exporter with FM Handover Extended View 2. COBie Enable your Revit Project by introducing COBie specific Parameters and a user defined property set definition file that maps these parameters to COBie Specific IFC property sets. Note: we are providing a suggested set of COBie specific parameters for Revit with the COBie Extension direct exporter but if you already have your own, you can modify this mapping so that the values in your custom parameters go out to IFC. 3. Populate appropriate COBie fields in your Revit Project/Models 4. Export your Revit Project to IFC using FM Handover Extended View configuration 5. Additional notes on Revit IFC Export and COBie 1

2 1. Configuring Autodesk Revit to use the Open Source IFC Exporter with FM Handover Extended View option First download and install the Revit Open source IFC exporter for Autodesk Revit Note that you need to install both the Open Source exporter as well as the Alternate UI. You can get this directly from Revit by clicking on the Autodesk Exchange Icon and searching for Revit IFC or from If you are getting this via the Autodesk Exchange Store for Revit you will see: Verify that this IFC Exporter and Alternate UI (user interface) has installed successfully with Revit. Go to Revit/Export/IFC and verify that you now have a new predefined configuration for COBie export IFC 2X3 Extended FM Handover View as depicted below. 2

3 Copy default user defined property set definition File for COBie Export ( IFC2x3 Extended FM Handover View.txt ) into install directory of IFC exporter. This file is provided with the open source distribution. It must be put in the same location as the IfcExporter dlls: (C:\Users\<your user>\appdata\roaming\autodesk\applicationplugins\adsk IFCExporter2014.bundle\Contents). Note: If you wish to introduce your own custom property set definition file it needs to be given the same name as the saved export configuration. Here is an example of the User Defined property set definition file for COBie: PropertySet definition for COBie PropertySet: COBie_Specification T IfcElementType NominalLength Real COBie.Type.NominalLength NominalWidth Real COBie.Type.NominalWidth NominalHeight Real COBie.Type.NominalHeight Shape Text COBie.Type.Shape Size Text COBie.Type.Size Color Text COBie.Type.Color Finish Text COBie.Type.Finish Grade Text COBie.Type.Grade Material Text COBie.Type.Material Constituents Text COBie.Type.Constituents Features Text Cobie.Type.Features AccessibilityPerformance Text COBie.Type.AccessibilityPerformance CodePerformance Text COBie.Type.CodePerformance SustainabilityPerformance Text COBie.Type.SustainabilityPerformance PropertySet: COBie_Component I IfcElement InstallationDate Text COBie.Component.InstallationDate WarrantyStartDate Text COBie.Component.WarrantyStartDate TagNumber Text COBie.Component.TagNumber AssetIdentifier Text COBie.Component.AssetIdentifier PropertySet: COBie_Space I IfcSpace RoomTag Text COBie.Space.RoomTag PropertySet: COBie_Asset T IfcElementType AssetType Text COBie.Type.AssetType PropertySet: COBie_Warranty T IfcElementType WarrantyGuarantorParts Text COBie.Type.WarrantyGuarantorParts WarrantyDurationParts Real COBie.Type.WarrantyDurationParts WarrantyGuarantorLabor Text COBie.Type.WarrantyGuarantorLabor WarrantyiDurationLabor Real COBie.Type.WarrantyDurationLabor WarrantyiDurationDescription Text COBie.Type.WarrantyDurationDescription PropertySet: Pset_ManufacturerOccurence IfcElement SerialNumber Text COBie.Component.SerialNumber BarCode Text COBie.Component.BarCode PropertySet: COBie_ServiceLife T IfcElementType ExpectedLife Real COBie.Type.ExpectedLife 3

4 Configure Classification Field Name(s) in Classification tab of IFC Assignments Screen. Classification Field Name under Classification tab now accepts multiple field names separated by comma (, ) or semicolon ( ; ), which allows mapping of multiple parameters for a single classification code, e.g. For Space: COBie.Space.Category For Type: COBie.Type.Category For Component: COBie.Component.Category The complete list of the parameters for COBie use: COBie.Facility.Category, COBie.Floor.Category, COBie.Space.Category, COBie.Type.Category, COBie.System.Category 4

5 Load in Revit exportlayers ifc2x3 forcobie.txt into Export Classes. This file is provided with the open source distribution of Revit IFC export. Do this by going to Revit/Export/Options/IFC Options. This is a special classes table for mapping Revit Category to IFC Class Name for COBie. 2. COBie Enable your Revit Project The best way to do this is to install the COBie Extension for Autodesk Revit This will introduce a set of COBie specific Revit Shared Parameters, COBie specific schedules and schedule keys for assisting in the population of some of the data fields. This COBie Extension for Autodesk Revit 2014 can be downloaded from: After installing, you just need to use the Setup feature which will automatically loads in the special COBie Parameters. 5

6 3. Populate appropriate COBie fields in your Revit Project/Models This exercise will require end users to have some basic knowledge of Revit parameters and COBie. They will also need to understand their specific role within their assigned phase of the project. For example, if a COBie spreadsheet (or Drop) is required during a design phase of Project, many of the Operations and Maintenance parameters will be blank as specific equipment for the building project may not yet have been procured. Therefore it is of critical importance that some thought be put into the BIM execution planning of your project to determine roles and responsibilities with respect to this inputting of this data. With the COBie extension for Revit we have provided some sample schedule keys that demonstrate how to semi automate the classification of rooms & spaces with either OmniClass or Uniclass data. More advanced methods for managing the input of non graphic data to Revit BIM objects including linking to external databases are supported in Autodesk Revit but are beyond the scope of what this freely distributed COBie extension is intended for. 4. Export your Revit Project to IFC using FM Handover Extended View configuration The final step is to just export your IFC file from your Revit Model using the FM Handover Extended View configuration option. 5. Additional Notes on Revit IFC Export and COBie IfcExporter now supports user defined Property Set. It is implemented through a text file with the same name as the configuration name. Below is the defined format (All must be separated by a single tab): Format: PropertySet: <Pset Name> I[nstance]/T[ype] <element list separated by ','> <Property Name 1> <Data type> <Revit parameter name (if different from property name)> <Property Name 2> <Data type> <Revit parameter name (if different from property name)>... Example: PropertySet: COBie_Specification T IfcElementType NominalLength Real COBie.Type.NominalLength NominalWidth Real COBie.Type.NominalWidth NominalHeight Real COBie.Type.NominalHeight Shape Text COBie.Type.Shape Currently, only basic data types are supported: Text, Real, Integer and Boolean IfcZone export is extended to support Classification Code export with a new parameter: ZoneClassificationCode IfcZone will be created by IfcExporter using existing support when Room or Space contains Zone related parameters (ZoneName, ZoneDescription, ZoneObjectType, ZoneClassificationCode). Rooms and Spaces that 6

7 are to be included in the same Zone must have the same value in ZoneName parameter, and has ZoneClassificationCode assigned separately from the Space classification code. IfcDistributionPort, IfcRelConnectsPorts, and IfcRelConnectsPortToElement are named using element id (or guid) element id (or guid) Support as been added for creating IfcActorRole, which is needed for COBie contacts COBie Contact Information A minimal integration with COBie Extension is done for contact list via XML export from the COBie Extension. In order to get the list of contacts in Revit using COBie Extension, export the contact information into XML file. The file must be named: <Original Revit name without extension>_cobiecontact.xml. The file should be placed at the same location as the Revit file. IfcExport will find such file and create the corresponding contact information inside IFC file with the appropriate IFC Entities. COBie expects quite a lot of information from Types. In order to export Revit objects especially MEP objects with the types, additional information for the specific IFC entity will be required. This is achieved by adding information into the IfcExportAs shared parameter. The value will be in the following format: <Ifc Type Object Name>.<Predefined Type for the type> E.g IfcElectricApplianceType.WATERHEATER IfcAirTerminalBoxType.CONSTANTFLOW (for Water heater) (for VAV box) Other Type specific attributes that can be entered are: IfcElementType, needed if PREDEFINEDTYPE is set to USERDEFINED IfcName, to override the Name attribute IfcDescription, to set Description attribute IfcTag, to set Tag attribute A stated above a general guideline /practice for a good IFC output is proper assignment of MEP entities to IFC types. However, it is not absolutely necessary that you do this for for COBie. IfcExporter now supports export of IfcBuildingElementProxyType. IfcBuildingElementProxy is now included as part of MEP system and support MEP system connectivity. All MEP related objects will be considered in the System components and connectivity without any special assignment with IfcExportAs. Only the default IFC Option must be updated. 7

8 8