COBie User Guide
COBie User Guide
Note: This document is likely to change slightly for the released product.
Table of Contents
1 COBie............................................................................................................................................................................... 4
2 IFC concepts .................................................................................................................................................................... 5
2.1 Type vs. Instance .................................................................................................................................................... 5
2.2 Shared vs. private properties .................................................................................................................................. 5
2.3 ‘Strong’ vs. ‘soft’ typing ........................................................................................................................................... 6
3 AECOsim Building Designer ............................................................................................................................................ 8
3.1 Product overview ..................................................................................................................................................... 8
3.2 Datasets .................................................................................................................................................................. 8
3.2.1 Delivered datasets............................................................................................................................................... 8
3.2.1.1 Terminology IFC / Building Designer .......................................................................................................... 8
3.2.1.2 Creation of ‘strong’ catalog items (types) .................................................................................................... 9
3.2.2 Dataset Extension ............................................................................................................................................. 16
3.2.3 Company dataset .............................................................................................................................................. 16
3.2.4 Project dataset .................................................................................................................................................. 17
4 Workspace operations ................................................................................................................................................... 18
4.1 Create project ........................................................................................................................................................ 18
4.2 Upgrade Projects to COBie ................................................................................................................................... 18
4.2.1 IFC_PROJECT=0 .............................................................................................................................................. 19
4.2.2 IFC_PROJECT=1 .............................................................................................................................................. 19
4.2.3 IFC_PROJECT=2 .............................................................................................................................................. 20
4.3 Start AECOsim Building Designer ......................................................................................................................... 21
4.4 Create design file(s) .............................................................................................................................................. 21
4.5 Open design file .................................................................................................................................................... 22
4.6 Create custom DataGroup catalog type(s) ........................................................................................................... 22
4.7 Create custom DataGroup property definitions ..................................................................................................... 25
4.8 Attach DataGroup types with DataGroup definitions ............................................................................................ 30
4.9 Create a compound cell ........................................................................................................................................ 33
4.10 Create DataGroup catalog items........................................................................................................................... 35
4.11 Create DataGroup Catalog Items for IfcZones ..................................................................................................... 40
4.12 Map DataGroup to IFC .......................................................................................................................................... 42
4.12.1 Map DataGroup types to IFC Entities/Classes ............................................................................................. 42
4.12.2 Map Parts to IFC Entities/Classes ................................................................................................................ 45
4.12.3 Map DataGroup items to IFC Entities/Classes ............................................................................................. 45
4.12.4 Map duplicate properties ............................................................................................................................... 46
5 Building Information Modeling ....................................................................................................................................... 51
5.1 Define the Spatial Structure .................................................................................................................................. 51
5.2 Add Zone information to Spaces ........................................................................................................................... 52
5.3 Assemble the Building Information Model ............................................................................................................. 53
1 COBie
Based on the IFC 'Facility Management Handover' Model View Definition, COBie (Construction Operations Building
information exchange) is an information exchange specification to capture data during design, construction, and
commissioning for handover to operations and management. Data is created by architects and engineers, who provide
floor, space, and equipment layouts, and contractors, who provide make, model, and serial numbers of installed
equipment, possibly provided by product manufacturers.
COBie data can be delivered in 3 formats: IFC STEP Physical File Format (SPFF), ifcXML, and spreadsheets.
Further information at:
http://www.wbdg.org/resources/cobie.php
http://buildingsmartalliance.org/index.php/projects/cobieguide/
http://www.nationalbimstandard.org/nbims-us-v2/pdf/NBIMS-US2_c4.2.pdf
2 IFC concepts
Specified and developed by buildingSMART, IFC (Industry Foundation Classes) is an open, vendor-neutral BIM data
repository for the semantic information of building objects, including geometry, associated properties, and relationships, to
facilitate
cross-discipline coordination of building information models, e.g. architecture, structural and building services,
data sharing and exchange across IFC-compliant applications,
handover and re-use of data for analysis and other downstream tasks.
inherits some or all ‘shared’ properties of its parent type, but can also have additional ‘private’
properties (door no: D001; sound proof: true) and/or redefined ‘shared’ properties that then become
‘private’ properties (color: red).
shared defined by a Type, i.e. shared or common values across multiple instances
private defined at the instance, i.e. unique property values for each instance of that type, which
add to the shared property values
or redefine or override the shared property values
Property values redefined on the instance override the property values defined by the type.
Therefore, an instance can have (in order of ‘strong’ to ‘soft’ typing)
a) only shared property values inherited from its type
b) shared property values inherited from its type, plus additional private property values
c) shared property values inherited from its type, some of which redefined on the instance
d) shared property values inherited from its type, some of which redefined on the instance, plus additional private
property values
e) only private property values
IFC Viewers, such as the ‘FZK Viewer’, may display ‘shared’ properties as ‘PropertySets from entity type’ and ‘private’
properties as ‘PropertySets from entity’
‘PropertySets from entity type’ displays all property values defined for the type (e.g. Frame | Material: STL), even if
redefined in ‘PropertySets from entity’ (e.g. Frame | Material: WD)
‘soft’ does not necessarily require the creation of a new type if a property is changed;
it is up to the user to decide which property changes require a new type;
more applicable during the conceptual design and design development phase;
supports c), d), e).
The IFC specification does not define whether a change of property requires a change of a type or which properties
must be shared by all instances.
Although not defined in the FM Handover Model View Definition specification, COBie has a preference for ‘strong’
typing.
3.2 Datasets
Datasets add the ‘I’ to ‘BIM’, i.e. the Information to Building Information Modeling, powering the AECOsim Building
Designer engine. Without datasets, the application is not able to create a building information model and to generate
drawings, rendered images and animations, reports, schedules, analysis data and other output, which depend on different
inputs from the datasets
.
3.2.1 Delivered datasets
AECOsim Building Designer is delivered with an imperial dataset for use in the US. Metric datasets can be downloaded
from Bentley’s SELECT site that included local standards for a variety of countries, such as the UK, Australia, New
Zealand, Singapore, Sweden, and Denmark.
The delivered datasets should not be modified by users as changes may be overwritten by subsequent installations or
new content may not be included in modified files.
By default, delivered datasets support ‘soft’ typing, i.e. DataGroup Catalog Items only define certain property values, all of
which could be redefined at the instance of that Catalog Item, because all properties are ‘editable’:
Catalog items, typically prefixed with ‘x_’ or ‘x-template |’, are templates that when copied the copies are created in
the project dataset.
Consider a naming convention that indicates a strong type by adding TYPE as a pre- or suffix, e.g. ‘TYPE | Double
Flush Panel 6x7 Egress’.
When placing a ‘strongly typed’ component, ‘non-editable’ properties are greyed out, i.e. cannot be redefined for the
instance, while ‘editable’ properties can be added or redefined.
Instance data of ‘non-editable’ properties are locked, i.e. cannot be activated for editing or redefined, while editable
properties can be added or redefined.
To change soft-typed instances, e.g. used during the early design stages, to strong typed catalog for use in the
construction documentation phase:
Select one instance or create a selection set of instances that should be changed to the same strong-typed catalog
item and click ‘Modify Properties of Selected Components’ to open the ‘Modify’ dialog box.
Activate the DataGroup Catalog Item field (bottom left) by adding a -mark to the ‘Active’ field.
From the pulldown menu, select the strong-typed catalog item, e.g. ‘TYPE | Double Flush Panel 6x7 Egress’.
To add or override (unless disabled) further properties, add -marks in the corresponding row and add further values.
Give a data point into each greyed out field to activate the corresponding property so that the strong-typed property
values are applied to the selected instances.
Be aware that dimensional changes, e.g. door widths, may require repositioning of items!
3.2.1.2.2 MEP
Open the DataGroup Catalog Editor.
Make a copy of the default DataGroup Catalog Item using right-click option ‘Copy’ or ‘Edit’ > ‘Copy’ (Ctrl C), e.g. of
‘Split Coupled’.
Rename the copy, possibly indicating that it is a strong type by adding TYPE as a pre- or suffix, e.g. ‘TYPE | Pump-
Cold Water’.
Enter values for all properties relevant for the type.
Make all properties relevant for the type ‘non-editable’, but leave properties that can be added or redefined for the
instance ‘editable’.
Open the ‘DataGroup Instance Data’ dialog box with the ‘Modify Properties of Selected Elements’ tool or right-
click option ‘Modify Selected Component’.
For the ‘ID | Type ID’ property, enter the typed Catalog Item prefixed with a *-character, e.g. ‘*TYPE | Pump- Cold
Water’; this means the element will be exported as type ‘TYPE | Pump- Cold Water’ instead of ‘Split Coupled’,
including the properties defined for the type.
A configuration variable in the Project Configuration Files (PCFs) must define the configuration variables for the location of
the company content and a statement to read CompanyDataset.cfg must included, e.g.
#======================================================================
# Establish Company Directories
#======================================================================
# Define path and folder name of company dataset
# (change path and folder name as necessary)
#----------------------------------------------------------------------
# COMP_DATASET = $(TF_DATASETS)DatasetExtensions/Company_Dataset/
#
#----------------------------------------------------------------------
# Read company cfg-file to add search paths to company dataset subfolders
#----------------------------------------------------------------------
# %if exists ($(COMP_DATASET)CompanyDataset.cfg)
# %include $(COMP_DATASET)CompanyDataset.cfg
# %endif
4 Workspace operations
4.1 Create project
Start AECOsim Building Designer
In the ‘File Open’ dialog box, select ‘New …’ from the Project dropdown menu to open the ‘Create New Project’ dialog
box
In the ‘Create New Project’ dialog box, select the COBie template project, e.g. ‘COBieTemplate_US’, from the ‘Seed
Project’ dropdown menu
A Project Configuration File (PCF) is created that includes the configuration variable IFC_PROJECT=2, thus
extending the workspace with the ‘IFC2x3_psets’ and ‘FM_Handover_Ext’ (COBie) dataset extensions.
Open the project’s Project Configuration File (PCF) with a text editor, such as Notepad
In the PCF, edit configuration variable IFC_PROJECT=<number>
#======================================================================
# Extended Dataset Content:
#======================================================================
# Enables the Dataset to be extended to include IFC2x3 property sets.
# IFC_PROJECT=0, dataset not extend,
# IFC_PROJECT=1, dataset extended with IFC psets
# IFC_PROJECT=2, dataset extended with IFC psets Plus FM Handover(COBie)
%level 4
IFC_PROJECT : 0
Once the value of IFC_PROJECT has been edited to ‘1’ or ‘2’ it should not be reversed.
4.2.1 IFC_PROJECT=0
Only the properties defined and configured by AECOsim Building Designer plus user-defined property sets and properties
will be available, e.g.
4.2.2 IFC_PROJECT=1
Copyright © 2013 Bentley Systems, Incorporated | COBie User Guide 19
AECOsim Building Designer V8i COBie User Guide
The common IFC2x3 property sets, such as Pset_DoorCommon, Pset_FurnitureTypeCommon, Pset_WallCommon, etc.,
are added to the workspace. Their properties are available for adding instance data, which will subsequently be exported
to IFC.
Editing xml-files could seriously damage the file and corrupt the entire workspace! Therefore, it should only be done
with knowledge of the xml-syntax and ideally using an xml-editor with syntax checker. Always keep a backup of the
original file.
4.2.3 IFC_PROJECT=2
Property sets specified by the Facilities Management Handover/COBie ModelView Definition (MVD) are added to the
workspace for relevant DataGroup types, i.e.
o Site, Building, Floor, and Space: Pset_PropertyAgreement
o Serviceable items, i.e. FFE: Pset_ManufacturerOccurrence
Pset_ManufacturerTypeInformation
Pset_ServiceLife
Pset_Warranty
Note that the DataGroup Catalog Editor (Catalog Items) dialog box opens.
Click ‘Show Catalog Items to open the DataGroup Catalog Editor (Catalog Types) dialog box
o enter a Name for the new catalog type, e.g. ‘Robot’ (Note: no space allowed)
o in the ‘New File’ dialog box, select the Directory for the new file; typically the datagroupcatalogs folder in the
project dataset, e.g. …\MyProject\support\dataset\datagroupcatalogs\
o enter a name for the new file, e.g. ‘Robots’ (Note: no space allowed; they can be added via DisplayNames)
Hint: you may need to switch off the ‘Filter items by Catalog’ option to see the new catalog type.
Optionally: add the new DataGroup catalog type to one of the catalog filters
o open the Catalog Filter
o enter a name for the new file, e.g. ‘RobotProperties’ (Note: no space allowed; they can be added via
DisplayNames)
From the ‘Insert’ tool bar, select ‘Property’ to add a property to the file
Enter a Name for the new property, e.g. ‘V-Reach’ and optionally a Display name, e.g. ‘Vertical reach’
From the Data type drop down menu, select an appropriate data type, e.g. ‘Decimal’
To group properties, select ‘Property Group’ from the ‘Insert’ tool bar to create a property group
Select the property group, then select ‘Property’ from the ‘Insert’ tool bar
You can also right-click on the property file and select ‘New Property Group’ or ‘New Property’ from the menu
ParaDef.xsd is required for furniture, fixture, and equipment types to allow definition of type (CEL, BXC, PAZ) and the
(parametric) cell name
o if necessary, create a new Destination file by clicking the ‘Create a new DataGroup file button
o in the ‘New File’ dialog box, select the Directory, typically the datagroupcatalogs folder in the project
o Attach the property sets required for the FM Handover/COBie MVD from
…\DatasetExtensions\IFC2x3_psets\datagroupsystem as described above, i.e.
Pset_ManufacturerOccurrence
Pset_ManufacturerTypeInformation
Pset_ServiceLife
Pset_Warranty
Click ‘Save’ to save the changes made in the DataGroup Catalog Editor.
or when prompted
o in the ‘Create Compound Cell Library’ dialog box, navigate to the destination folder, e.g.
…\support\dataset\cell, and enter a file name, e.g. Robots
Open the Current Library from the dropdown menu, e.g. Robots.bxc
Click ‘Create’
o enter a Name for the new catalog item, e.g. ‘Robot | Welding Type 01’
o open the Classification Browser by clicking the Classification cell, e.g. for ‘Classification | OmniClass’
Consider informing the IFC-file recipients about the exact property names and formats so that they can add
corresponding properties to their workspaces.
Open the ‘Place User Defined Type’ dialog box and select the Type from the ‘Instance Data Type’ dropdown menu,
e.g. ‘Robot’
Select the item to be placed from the dropdown list, edit or add property values, and place the item.
o if necessary, create a new catalog file ‘Zones’ in the datagroupcatalogs folder of the project
Click ‘Map’ (Map DataGroup Types and Properties) to open the ‘Map DataGroup to IFC’ dialog box.
If necessary, click the ‘Type Mapping’ tab on the ‘Map DataGroup Types and Properties to IFC’ dialog box.
All AECOsim Building Designer DataGroup Catalog Types are mapped to a corresponding IFC entities/class and
should not be remapped unless necessary for a particular project
To map unmapped DataGroup Catalog Types, click on the empty cell in the ‘IFC Mapping’ column to open the ‘IFC
2x3 Entities Classification’ dialog box.
Scroll through the list to find the IFC Class, Type and/or Predefined Type.
Alternatively, enter a search string in the ‘Search’ field to display only items that include the search string, e.g.
or
Double-click on an IfcEntityClass, IfcTypeClass or IfcPredefinedType to add it to the mapping table.
To remove a mapping, select the mapping and double click ‘Clear Mapping in the ‘IFC 2x3 Entities Classification’
dialog box
necessary to override the inherited mapping, e.g. to map certain wall catalog items to IfcCurtainWall. This is done in the
‘Map DataGroup to IFC’ dialog box by expanding the DataGroup type to display the catalog items.
Each localized dataset has different DataGroup catalog item names; hence the mapping overrides for catalog items is
dataset-specific.
Open the ‘Map DataGroup Types and Properties to IFC’ dialog box as described above.
Expand a DataGroup type, e.g. Plumbing Fixture
Catalog items that ‘inherit’ the FC entities/class from their ‘parent’ Catalog type are shown in bold.
Use the same method as described above for Type mapping to override the default item mapping to other IFC Class,
Type and Predefined Type.
AECOsim Building Designer is delivered with a property mapping table, but further properties can be mapped via the ‘Map
DataGroup to IFC’ dialog box.
Open the ‘Map DataGroup Types and Properties to IFC’ dialog box from the from the ‘IFC Export’ dialog
File > Export > IFC…
Click ‘Map’ (Map DataGroup Types and Properties) to open the ‘Map DataGroup to IFC’ dialog box.
If necessary, click the ‘Property Mapping’ tab on the ‘Map DataGroup Types and Properties to IFC’ dialog box.
Note: In the ‘DataGroup Properties’ column, the AECOsim Building Designer and user-defined properties (if any) for
the selected DataGroup type are displayed, except those in property definition files prefixed with a prefix defined by
configuration variable IFC_MAPPED_PROPERTIES. Default is IFC_MAPPED_PROPERTIES=Pset_, i.e. the
Only property sets defined in the buildingSMART IFC specification may be prefixed ‘Pset_’.
Consequently, in the ‘Mapped Properties’ column, the properties in property definition files prefixed with a prefix
defined by configuration variable IFC_MAPPED_PROPERTIES are displayed.
Select a DataGroup type from the DataGroup Type dropdown menu, e.g. ‘Wall’, to display all properties attached to
wall.
In the Destination column cell, click in the same row as a source property to open the dropdown list of available
properties in IFC2x3 property sets.
Click on the property to transfer it to the selected cell and to close the dropdown list.
In placement tools, a mapped property is greyed out indicating that a value cannot be added and to which property it
is mapped, i.e. where the property value should be entered.
o Site: double-click the default site name, rename it and enter Site property values in the right pane as required.
o click ‘Save Edits’
Note: Only one site is allowed.
o Building: if already included in the hierarchy, double-click the default building name, rename it and enter
Building property values as required; otherwise select the site and click the button to create a new
building.
o click ‘Save Edits’
Note: Multiple buildings are allowed.
o Floor: if already included in the hierarchy, double-click the default floor name, rename it and enter Floor
property values as required; otherwise select a building and click the button to create a new floor.
o click ‘Save Edits’
o enter Relative Elevation and Elevation
o optional: change the Rotation angle
For spatial containment, the floor range is calculated based on the floor elevation values in the Floor Manager.
Click ‘Exit’ to close the Floor Manager.
After placement: Open the ‘Edit Space’ dialog box with the ‘Modify Existing Instance Data’ , ‘Modify Properties of
The IfcZones Names must be identical to the DataGroup catalog item names.
Copyright © 2013 Bentley Systems, Incorporated | COBie User Guide 52
AECOsim Building Designer V8i COBie User Guide
While there are many different ways to assemble federated BIMs, a typical strategy is to create an empty ‘master’ model
and then to reference in the ‘sub-BIMs’, either ‘flat’, ‘by discipline’, or ‘by floor’.
Open ‘Master.dgn’ and click on ‘Reference’ to open the ‘References’ dialog box.
6 IFC Export
Click ‘IFC’ from the ‘File’ > ‘Export’ menu list to open the ‘IFC Export’
Select a Model View Definition (MVD) from the ‘Model View Definition’ dropdown list.
A message is displayed in the message field if the ‘IFC2x3’ or FM Handover/COBie’ dataset extension is not part of
the project’s workspace, including information how to add it.
Click ‘Assign’ (Assign Building and Floors) to open the ‘Assign Models to Spatial Containment’ dialog box.
Note: The default ‘Site/Building’ assignment of the active model and all references is to the first (and typically only)
building defined in the Floor Manager, whereas the default ‘Floor’ assignments are ‘Auto Assigned’, i.e. they are
assigned to the Floor into which range the building components in the model fall. The range is defined by the floor
elevation value and the elevation value of the floor above
In the ‘Assign Models to Spatial Containment’ dialog box
o to override the current ‘Site/Building’ assignment of a model or reference, click the corresponding
‘Site/Building’ cell and select another building from the dropdown list;
Note: if ‘Site Name’ is selected, the Floor assignment is removed and disabled.
o to override the current ‘Floor’ assignment, click the corresponding ‘Floor’ cell and select a floor, ‘Auto Detect’,
or ‘(None)’ from the dropdown list;
Note: if ‘(None)’ is selected, the model or reference is assigned to the Building assigned in the ‘Site/Building’
column.
o check the ‘Inherit Floor Assignment from Reference Parent’ to assign all nested references to the same
Building/Site and Floor as the ‘parent’ model.
o Click ‘Open Floor Manager’ to open the ‘Floor Manager’ dialog box (see Define the Spatial Structure)
o Click ‘Restore Defaults’ to restore the original default assignments to Site/Building and auto-assigned floors
o Click ‘Save’ to save the assignments and to close the dialog box
o Click ‘Close’ to close the dialog box
In the ‘IFC Export dialog box, click ‘Export’ to export the model to IFC (STEP Physical File Format, SPFF).
Optional: In the ‘Save As’ dialog box, override the ‘Save in’ folder (default = …\support\out\ifc) and File name (default
= name of DGN with .ifc extension).
Click the ‘Source File’ button and navigate to the directory to select the source file; the default folder location is the
folder defined by TFDIR_IFC.
If ‘Transformation Type’ is ‘IFC to i-model’ or ‘IFC to COBie spreadsheet’, only files with the extension .ifc are
available for selection; if ‘Transformation Type’ is ‘i-model to COBie spreadsheet’, only files with extension .i.dgn.
Check the ‘Open COBie spreadsheet’ box to open the COBie spreadsheet after it has been created.
Microsoft Excel needs to be installed, otherwise a notice is displayed: ‘Cannot open COBie spreadsheet, because
Excel is not installed.’
Note: If the header does not include ‘FMHandOverView’, a warning message is displayed:
Some Facilities Management Handover (COBie) properties may not be included because the source file is not a
'Facilities Management Handover (COBie)' file.
If the file was not created by ‘AECOsim Building Designer’, a warning message is displayed or added to the warning
message above:
The COBie spreadsheet may be incomplete because the source file was not created by AECOsim Building Designer.
Click ‘Continue’ on the warning message to close the warning message and start the process, click ‘Cancel’ to close
the warning message without processing.
Click ‘Cancel’ to close the ‘IFC Transformation Utility’.