O B OS
Open BIM
O b j e ct sta nda rd
An i n te r n a ti o na l s t a nd a r d f o r
ob jec t d e v e l o pe r s

OCTOBER 2018 v1.0

The Open BIM Object standard(The OBOS)

At NATSPEC, we are dedicated to improving the construction quality and productivity of the built
environment, so I am very pleased that this object standard is now available, following the extensive
joint research and work carried out by the technical teams of NATSPEC and Masterspec .
The OBOS supports the standardisation of BIM Objects across the Australian construction industry,and globally, with the implementation of the buildingSMART IFC schema . The OBOS and the
NATSPEC BIM Properties Generator address the major issues concerning information exchange
and compatibility of BIM objects between disciplines and projects, with the latter being aligned to theinformation requirements of the OBOS .
The implementation of the OBOS and the free exchange of standardised
BIM objects will allow different systems and applications to work together .
This is crucial to driving productivity across the industry and I’m happy that
NATSPEC working together with Masterspec have been able to provide
such a beneficial resource to industry to allow this to occur.
Richard Choy
CEO NATSPEC

The intent of this BIM Object standard is to support the sector’s drive for a more efficient and defined
way of working together . It provides a framework for the consistent creation, maintenance and use of
BIM Objects along the building lifecycle .
The standard is designed as an open standard and utilises the buildingSMART IFC Schema tofacilitate use of various proprietary authoring tools and their exchange with downstream applications .
It complements a number of other existing industry resources, such as the NZ BIM Handbook, the NZ
Asset Metadata standard as well as the soon-to-be-released Masterspec Property Selector .
A big THANK YOU goes to the many industry reviewers who havesupported the extensive research work jointly undertaken by the technicalteams of NATSPEC (Australia) and Masterspec (New Zealand) to arrive at
this internationally-based BIM Object standard .
Rolf Huber
CEO MASTERSPECContents
Introduction.
Document Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.0 BIM Objects.
1.1 BIM components and assemblies .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
1.2 Proprietary and generic BIM objects .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
2.0 Naming Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 General naming requirements.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
2.2 Object file naming requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Property naming requirements.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
2.4 Property set naming requirements.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
2.5 Material naming requirements.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
2.6 View control naming requirements.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
2.7 Material image file naming requirements.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
3.0 Object Classifcation . . 7
3.1 Object IFC designation. .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
3.2 Object classification.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
4.0 Object Properties & Property Grouping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.1 General object property requirements.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
4.2 Object type or instance properties.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
4.3 IFC properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4 Administration properties.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . 1
4.5 Proprietary object properties .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . 1
4.6 Classification properties.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . 1
4.7 Construction specification properties.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . 1
4.8 Asset/Facilities management properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
4.9 Product performance properties. .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
4.10 Property grouping (Property sets) .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . 1
5.0 Graphical/Geometric Object Modelling. 18
5.1 Object graphical detail.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . 
5.2 Geometric modelling requirements .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . 
5.3 What to model .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . .2
6.0 Object Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
6.1 Object performance.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . 2
6.2 Object relationships.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . 26.3 Visibility/Views.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . 2
6.4 Parametric behaviour.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . 2
7.0 Import, Export and Linking. . . . . . . .. . . . . . . . . . . . . . . . . . . . . 23
7.1 Importing information.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . 2
7.2 Exporting BIM objects .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . 2
8.0 Defnitions & Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Appendix A - IfcElementType and PredefinedType enumerator listing. 26

NATSPEC (Construction Information Systems Limited) – Australia

Founded in 1975, NATSPEC, is a not-for-profit organisation owned by the design, build, construct and property
industry through professional associations and government property groups . Its objective is to improve theconstruction quality and productivity of the built environment through leadership in the provision of information . For
over forty years, NATSPEC has been delivering the national, comprehensive construction specification systemendorsed by government and professional bodies .
NATSPEC believes that digital information, including 3-D Modelling and Building Information Modelling, will provide
improved methods of design, construction and communication for the industry, resulting in improved efficiency andquality . Further, NATSPEC supports open global systems . NATSPEC’s primary focus is on the “i” (information) in
BIM and how it is linked to digital models, and the development of BIM guidelines and standards beneficial to theconstruction industry .
NATSPEC is responsible for the Australian National BIM Guide and its associated documents, and the NATSPEC BIM
Properties Generator . For more information visit the NATSPEC website at www .natspec .com .au and click on the BIM
logo .

Masterspec (Construction Information Limited) – New ZealandConstruction Information Limited (CIL), operating as Masterspec, is the market leader in specification systems, related
information and supporting software for the New Zealand (NZ) construction industry . Formed in 1995, CIL provides
Masterspec specification systems to architects, engineers, designers, utility companies, government organisations
and tertiary institutions .
Masterspec is an industry-owned organisation . As such, Masterspec’s primary objective is to support the NZ
construction industry to increase the quality and productivity of the built environment . This is primarily achieved
through the provision of comprehensive, continuously updated and extended construction information systems andresources .
BIM has the potential to create a step change in NZ construction productivity . Masterspec is working with the NZ
construction industry to develop BIM guidelines and standards that will help realise the full potential of BIM for NZ .
For more information please visit www .masterspec .co .nz

Comments and Feedback
We welcome comments or suggestions for improvements to the Open BIM Object standard and encourage readers
to notify us immediately of any apparent inaccuracies or ambiguities . Contact us via email at bim@natspec .com .au or
bim@masterspec .co .nz .

Open BIM Object standard First published 2018 v1.0
Publisher: Construction Information Systems Limited, Sydney, Australia (ABN 20 117 574 606) and Construction
Information Ltd, Auckland, New Zealand .

Copyright
This Document is protected by Copyright © 2018 . You may use this Document for your own purposes . You may
distribute this Document to other persons provided that you attribute the Document as having been generated by
NATSPEC and Masterspec and that the document is available free of charge .

Disclaimer
The Open BIM Object standard, and any associated documents, are intended for use by professional personnel competent to evaluate thesignificance and limitations of its content and able to accept responsibility for the application of the material it contains.
The authors hereby disclaim all warranties and conditions with regard to this information and related graphics, including all implied
warranties, fitness for a particular purpose, workmanlike effort, title and non-infringement. In no event shall the authors be liable for any
direct, indirect, punitive, incidental, special, or consequential damages or damages for loss of profits, revenue, data, down time, or use,arising out of or in any way connected with the use of the Document or performance of any services, whether based on contract, tort,
negligence, strict liability or otherwise . The authors disclaim any responsibility to update any information, including with respect to any newlegal, business, or technology developments. If you are dissatisfied with any portion of the Document, or with any of these terms of use,
your sole and exclusive remedy is to discontinue using the Document .
Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

Introduction
The lack of standards limits the ability to share BIM content across disciplines, projects, and software .
Most jurisdictions have, or are moving to, protocols or standards for BIM processes . There are also a variety of BIM
standards that address some aspects of BIM content or tools . However, many aspects of BIM have no guidance at all .
Currently, it is possible for two organisations to create content about the same topic that complies with existing BIM
standards but has very different implementations .
As a result, many practices develop their own internal standards and are often reluctant to use any content producedby third-parties .
A number of object libraries and BIM authoring system-based groups have developed their own standards to address
this, but the proprietary nature of these standards means that it is difficult for a jurisdiction to adopt these.
The aim of this standard is to cover the primary aspects of BIM object development and provide sufficientcommonality so that practitioners will accept and use the content developed in conformance with its requirements .
This standard is to be open . Local requirements, variations or additions, if desired, are to be dealt with in annexures tothe standard .
The initial version of this standard was developed by NATSPEC, Australia and Masterspec, New Zealand and isavailable for free download from either organisation’s website . Any organisation wishing to adopt it, create a new local
annexure for use in their jurisdiction, or to contribute to its future development should contact either of the initiatingorganisations .

Document Conventions
Requirements of this standard are expressed in sentences which include the word ‘shall’ . To say that an object
complies with or conforms to this standard, all the ‘shall’ requirements of this standard need to be applied to the BIM
object .
Recommendations of this standard are expressed in sentences which include the word ‘should’ . Whilst not arequirement of this standard, it is recommended that an object include these items .
The standard uses the word ‘can’ to nominate that a concept is a possibility, for example, an addition to the mainconcept . The object author can include these items, if required .
Terms are identified within the standard using bold formatted text for the first time they appear in each clause, with
their definition provided in Section 8 - Definitions & Glossary.

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved11.0 BIM Objects
This section of the standard describes what an object is.

1.1

BIM components and assemblies

This sub-section of the standard discusses the concept of individual BIM objects and BIM object assemblies.
Defining the broad requirements for each.
1.1.1

1.1.2

BIM objects
BIM objects shall be modelled as a component object or a system object .
•Component objects are discrete, or loadable, objects where the geometry is created by the object
modeller and represents a specific physical element or component.

•

System objects are objects where the geometry is provided by the BIM authoring system for the user
to configure. Typically, these are layered objects such as walls, ﬂoors, roofs and ceilings, but can also
include, in some BIM authoring systems, windows, doors, piping, columns, beams and similar elements .

BIM assemblies
BIM objects can be grouped into assemblies to allow for reuse of common groupings of physical elements .

1.2

Proprietary and generic BIM objects

This sub-section of the standard discusses the differences between proprietary (manufacturer) BIM objects
and generic BIM objects.
1.2.1

Object typeThe object shall be modelled as a generic object or a proprietary object .

1.2.2

Generic objects
Generic objects shall be, as a minimum, recognisable as a representation of the physical element that it isrepresenting .

1.2.3

Proprietary objects
Proprietary objects shall be an appropriate geometric representation of the physical element with accurate
critical dimensions and metadata .

1.2.4

Project objects
Project objects are unique project-specific objects created as either a generic or proprietary object for use in a
project and not intended for inclusion in a shared library .

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved22.0 Naming Conventions
This section of the standard sets out the requirements and rules for naming object ﬁles, properties,
property sets, materials, views and material image ﬁles.

2.1

General naming requirements

This sub-section of the standard defines the general naming requirements applicable to all situations coveredby this standard.
2.1.1

Naming ﬁelds
Object files, materials and material image files shall be named using the naming ﬁelds from Table 2A,
arranged in accordance with the relevant naming clauses below .
Field

Description

Example<Type>

Shall be used to identify the type of object or material .

Door<Subtype>

Should be used to identify the subtype of the object or material .

Interior<Source>

The product manufacturer identification. Shall be used for

SupaDoors

proprietary objects .
<Product/Range Identiﬁer>

The manufacturer’s product or product range identifier. Shall be

D130ST

used for proprietary objects .
<Differentiator>

Can be used to provide additional information required to identify

760W

the object or material .
<Originator>

A 3 to 6 character code, can be used to identify the object provider .

ABC

Should be used for objects provided by an object library .
Table 2A – Naming ﬁelds

2.1.2

Characters
Names and naming ﬁelds shall include only the following characters:•

Uppercase letters (A to Z) from the ISO basic Latin alphabet .

•Lowercase letters (a to z) from the ISO basic Latin alphabet .

•Numbers (0 to 9) .

•Underscore (_), used only for separating fields within a name.

•A single period character (.), used only to separate the file name from the file extension.

Names and naming fields shall not include any of the following characters:•

Symbols or mathematical operators, including, but not limited to, (! “ ,£ $ % ^ & * { }[ ] + - = < > ? | \ / @ ’~ #¬ ` ‘) .

•Spaces .

The use of the hyphen character should be avoided as it can cause errors when the name (or property) isused within formulae, due to the hyphen also representing the mathematical subtraction operator .
2.1.3

Naming rules
PascalCase shall be used to join separate words within naming ﬁelds and for the naming of properties .
Fields in a name shall be separated by an underscore (_) .
Where required, abbreviations can be used . Recognised industry abbreviations shall be used where they exist,
for example, PVC .

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

3

2.2

Object ﬁle naming requirements

This sub-section of the standard defines the requirements for object file naming. Including Proprietary/Generic/Project object naming, Parametric object naming and Dimensional information in file names.
2.2.1

File naming rules
The object file name shall be a unique human readable description of the object.
The object file name shall be in accordance with clause 2.1.
Relevant dimensional information can be included in the <Differentiator> ﬁeld and should include the unit ofmeasure . For example, 300x700mm, 400mmx30m, 1200mm .

2.2.2

Parametric object ﬁle naming
The subtype ﬁeld of a parametric object file name shall be a pascal case concatenation of the variants
represented by the object . For example, RectangularSquare .

2.2.3

File name structure
The object file name shall be structured as follows, unless specified otherwise by local requirements:<Type>_<Subtype>_< Source>_< Product/Range identifier>_< Differentiator>_< Originator>

2.3

Property naming requirements

This sub-section of the standard defines the requirements for the naming of properties (also known as
attributes or parameters) associated with BIM objects. BIM properties are variables that store data relating
to the object. The naming of properties needs to provide a human readable description of the property
requirement and also adopt the conventions and methodologies used within modern programming language
techniques to allow automated use of the data contained within.
2.3.1

Unique properties
Each unique concept describing information about an object shall have a unique property name .

2.3.2

Property naming rules
Properties shall be named in accordance with clause 2 .1 .
Properties shall be named in a consistent and logical manner to aid clarity and usability .
Each property name shall be a unique human readable description of the property value requirement .

2.3.3

Boolean properties
Properties that require the value to be completed with a Yes/No or True/False enumerator, shall be named toindicate such a requirement, for example, ‘IsExternal’ .

2.3.4

Sufﬁx
If user edited/created property sets are not supported in the BIM authoring system being used (seeclause 4.10), a 3 to 6 character suffix can be added to the end of each property name, separated by anunderscore(_), to identify the source of the property . For example, DoorPanelHeight_ANZRS .
Note: A suffix cannot be added to the end of property names from defined data schemas such as IFC (Industry
Foundation Classes) or COBie. The property names from any defined data schema must not be changed oramended in any way .

2.4

Property set naming requirements

This sub-section of the standard defines requirements for the naming of property sets associated with BIM
objects. This is to facilitate the metadata being in a format consistent with IFC. Not all BIM authoring systems
fully support the concept of property sets for BIM objects, for example Revit only allows the user to assign
object properties to hard-coded groups, however the shared parameter file does assign each property to agroup, which is an equivalent concept to property sets.

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

42.4.1

Property sets
Object properties shall be grouped into logical sets, see clause 4 .10 .

2.4.2

Property set naming rules
Property sets shall be named in accordance with clause 2 .1 .
Property set names shall provide a descriptive context for the grouping .
Property set names shall have a prefix followed by an underscore to identify the origin of the property set, forexample, OBOS_, COBie_, ANZRS_ .
IFC property sets shall be named with the corresponding IFC property set name (Pset_) .
For properties identified in this standard, the property set name shall be as shown in italics in the table title.
For example, for the properties in 'Table 4A – OBOS_Admin properties' the property set name shall be
OBOS_Admin.

2.5

Material naming requirements

This sub-section of the standard defines the requirements for the naming of materials associated with BIM
objects.
2.5.1

Material naming rules
Materials shall be named in accordance with clause 2 .1 .
Material names shall be unique human readable descriptions of the material .

2.5.2

Material name structure
The material name shall be structured as follows:<Type>_<Subtype>_<Differentiator>

2.6

View control naming requirements

This sub-section of the standard defines the requirements for the naming of view controls associated with BIM
objects. BIM authoring systems control object viewing in different ways, such as layers and subcategories.
Where the views can be named by the user, and are shared with objects, then it is important to name themconsistently to avoid a proliferation.
2.6.1

2.6.2

View control naming rules
Where the BIM authoring system allows for user defined view control, views shall be named as follows:•

In accordance with clause 2 .1 .

•In plural form .

•Be consistent and logical to aid clarity and usability .

View control name structure
The view control name shall be structured as follows, using the ﬁelds from Table 2B:<UsageGroup>_<UsageSubGroup>_<Differentiator>
Field

Description<UsageGroup>

Shall be used to name the group’s primary purpose or use, for example, Plumbing .

<UsageSubGroup>

Should be used to name the sub group’s purpose or use if the usage group covers
multiple concepts, for example, Plumbing_Sanitary .

<Differentiator>

Can be used to further differentiate the sub group, for example,
Plumbing_Sanitary_Fittings .

Table 2B – View control naming ﬁelds

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

5

2.7

Material image ﬁle naming requirements

This sub-section of the standard defines the requirements for the naming of image files associated withmaterials.
2.7.1

Material image ﬁle naming rules
Image files shall be named in accordance with clause 2.1.

2.7.2

Material image ﬁle name structure
Image files shall be named identically to their corresponding material (see clause 2.5), with the addition of thefile format extension of either .bmp or .jpg.

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

63.0 Object Classiﬁcation
This section of the standard sets out the requirements for classifying the object and assigning it thecorrect IFC designation.

3.1

Object IFC designation

This sub-section of the standard defines the requirements for the designation of the object in IFC to aidinteroperability of the BIM object between different BIM applications. See Appendix A for the available
IfcElementTypes and PredefinedTypes from the IFC4 schema.
3.1.1

IFC type
The BIM object shall be designated the appropriate IfcElementType and PredefinedType, see clause 4 .3 .2 .

3.2

Object classiﬁcation

This sub-section of the standard defines the requirements for the classification of the BIM object. Due to theproliferation of systems in use, it is likely that an object may need to support multiple classifications (addressedin Section 4 of this standard).
3.2.1

Classiﬁcation system
The object should be classified using a system(s) that reﬂects those of the jurisdiction where the object is
intended for use .
The classification code should be as specific to the object type as possible, see clause 4.6.1.

3.2.2

Hard-coded classiﬁcation
BIM objects can be classified using the BIM authoring system’s hard-coded assembly code (or costing code)and keynote code .

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

74.0 Object Properties & Property Grouping
This section of the standard deﬁnes the properties that should be assigned to a BIM object. It also
discusses the grouping of properties and the assignment of properties to object types or object
instances.

4.1

General object property requirements

This sub-section of the standard defines the general rules for properties associated with BIM objects including
the requirements for using non-conforming hard-coded properties within BIM authoring applications.
4.1.1

Provision of properties
Properties can either be embedded within the object or linked via a unique link to an external database .

4.1.2

Extent of properties
Only properties that are deemed necessary to adequately define the object for its intended BIM use(s), and toprovide for object interoperability between BIM applications, shall be provided .

4.1.3

Duplication of properties
An object shall not include duplicate occurrences of a property .
Where an identical property, either in name or in description/value requirement, exists in multiple sources (forexample, IFC and COBie), only include a single occurrence of that property .
IFC properties shall take precedence over properties from other sources .

4.1.4

Hard-coded properties
Hard-coded properties within the BIM authoring system shall be used .
Where necessary, hard-coded properties shall be mapped to their corresponding IFC properties at export, seeclause 7 .2 .

4.1.5

Proprietary and generic object properties
Proprietary objects shall, as a minimum, include the same properties as those provided for a generic object of
the same object type and subtype .

4.1.6

Property values
Property values shall be completed where known .
Proprietary objects shall have all Type property values completed, see clause 4 .2 .1 .
Property values can be completed with:

4.1.7

•

A fixed value, where only one value is available or a decision has been made on which value is required,for example, 6000 .

•A value range, where a bounded range of values are available and a decision has not been made on
which value is required . The lower and upper bound of the available range shall be separated by ahyphen, for example, 100 – 600 .

•An enumerated value, where a number of values are available from a defined list of enumerators and adecision has not been made on which value is required . Each available enumerator shall be separated by
a comma, for example, X, Y, Z .

•A formula, if the value is reliant on the value of another property .

•Property values shall not:•Finish with a full stop( .) .

•Include units, unless specifically required to do so in the property description.

Property units
Units shall be metric unless specified otherwise by local requirements.

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

84.1.8Property data type
Properties shall have their data type defined using ANSI SQL data types, selected from the following list:•

Character (Text, String) – for fields requiring alpha numeric or text values.

•

Integer – for fields requiring whole numbers.

•

Decimal (Number, Currency) – for fields requiring decimal numbers.

•

Date – for fields requiring a date in the format year-month-day (YYYY-MM-DD).

•

Boolean (Yes/No, True/False) – for fields requiring a choice from two options.

•Hyperlink (URL) – a character field where values are links represented as www.website.domain/path .

If a data type listed above is not available, or a more specific hard-coded data type is available, within the BIM
authoring system being used, use the most appropriate hard-coded data type . For example, if there is no
Date data type, use a Character type and enter the date in the correct format .
4.1.9

Assembly properties
Assemblies shall not have properties assigned to the assembly itself .
All properties shall be assigned to the objects contained within the assembly .

4.2

Object type or instance properties

This sub-section of the standard discusses the concept of properties being type properties or instanceproperties.
Type objects represent defined specifications of physical elements. The type information contained on theobject is common for all instances of the object.
An Instance of an object is a unique placement of a type object in a model. An Instance object can containunique information such as serial numbers and installation or commissioning information.
4.2.1

Type properties
A property that has a consistent value for all instances of that object type shall be treated as a Type property .
Values for Type properties of library objects can be pre-completed .

4.2.2

Instance properties
A property that requires a value that is specific to the instance of that object type shall be treated as an
Instance property . Values for Instance properties of library objects cannot be pre-completed .

4.3

IFC properties

This sub-section of the standard defines the IFC properties to be assigned to a BIM object.
4.3.1

IFC for interoperability
To provide for greater interoperability of objects and models between different BIM applications, all objects
shall include properties from the buildingSMART IFC4 (Addendum 2) schema that directly correspond to that
object type .

4.3.2

IFC object designation properties
The object shall include a property named ‘IfcExportAs’, with the value completed with the relevant
IfcElementType from IFC4 (Add 2) . For example, ‘IfcPile’, for a pile foundation .
The object shall include a property named ‘IfcExportType’, with the value completed with the relevant
PredefinedType, selected from the enumerated list available for the nominated IfcElementType . For example,‘DRIVEN’, for a driven pile foundation .
Note: BIM authoring applications may automatically assign the ‘IfcExportAs’ and ‘IfcExportType’ properties,
based on the in-built tools or templates used for modelling the object, see clause 5 .2 .1 .

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

94.3.3

IFC proxy object designation
If a relevant IfcElementType does not exist in IFC4 (Add2), for the object being modelled, then the ‘IfcExportAs’
property shall be completed with ‘IfcBuildingElementProxy’ and the ‘IfcExportType’ property shall becompleted with ‘USERDEFINED’ .
When the IfcBuildingElementProxy has been nominated, the object shall include an additional property of‘ElementType’, with the value completed with a descriptive name to define the object type.

4.3.4

IFC common properties
If an IFC common property set (Pset_XXXCommon) exists for the object type, the properties from thatproperty set shall be included .
If no IFC common property set exists for the object type, the properties from the IFC
Pset_BuildingElementProxyCommon property set shall be included .

4.3.5

Additional IFC properties
Additional properties and property sets from the IFC schema can be included, such as Quantity sets (Qto_)and environmental impact properties .
If a property in the IFC4 (Add2) schema addresses the same concept to that of a property proposed forinclusion, the IFC property shall be used .

4.4

Administration properties

This sub-section of the standard defines properties to be assigned to a BIM object that relate to theadministration and management of the object.
4.4.1

Object admin properties
The set of properties in Table 4A shall be included for all objects .
Property

CreatedBy

Description

Data type

ExampleType /
Instance

Name of the person, organisation or library

Character

SupaObjects

Typeprovider that created the object .
CreatedByURL

URL hyperlink to the object creator’s website .

Hyperlink

www .SupaObjects  .com

TypeModiﬁedIssue

To record the last date of issue (version or

Date

2018-03-16 .02

Type

revision) of the object within an object library .
Value to be completed in the following format<yyyy-mm-dd.no>. The ‘no’ suffix can be used if
the object is issued multiple times on that date .
Table 4A – OBOS_Admin properties

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

10

4.5

Proprietary object properties

This sub-section of the standard defines properties to be assigned to a proprietary object.
4.5.1

Manufacturer/Product identiﬁcation properties
The sets of properties in Tables 4B and 4C shall be included for all objects that represent a proprietary
manufacturer product (or may be used to do so in the future) .
Property

Description

Manufacturer

Data type

Organisation that manufactured and/or

ExampleType /
Instance

Character

SupaObjects

Type

Character

Solid Timber DoorType

Character

D130STType

Character

D130ST2100X800

Type

Integer

00012345600012

Type

Integer

2018

Type orassembled the product .
ModelLabel

Descriptive model name of the productmodel (or product line) as assigned by the
manufacturer .

ModelReference

Model number or designator of the productmodel (or product line) as assigned by the
manufacturer .

ArticleNumber

Article number or reference that is beapplied to a configured product according
to a standard scheme for article number
definition as defined by the manufacturer. It
is often used as the purchasing number .

GlobalTradeItemNumber

Global Trade Item Number (GTIN) is an
identifier for trade items developed by GS1(www .gs1 .org) .

ProductionYear

Year of production of the manufactured
product .

AssemblyPlaceInstance

Enumeration defining where the assembly is

Characterintended to take place, either in a factory oron the building site .

* Permissible enumerators

Property
ManufacturerURL

FACTORY,OFFSITE, SITE,
OTHER, NOTKNOWN, UNSET*

Type orInstance

Table 4B – Pset_ManufacturerTypeInformation properties

Description
URL hyperlink to the

Data type

ExampleType /
Instance

Hyperlinkwww  . SupaDoors  . com

TypeHyperlinkwww  . SupaDoors  . com / D130ST

Type

manufacturer’s website .
ProductURL

URL hyperlink to further
product information, such astechnical documentation or
installation guides .

Table 4C – OBOS_Manufacturer properties

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

11

4.6

Classiﬁcation properties

This sub-section of the standard defines properties to be assigned to an object to classify the object type. As
there is no universally adopted classification system, this sub-section allows for the application of multiple
classification systems.
4.6.1

Classiﬁcation system properties
Multiple classification systems can be assigned to an object by including the set of properties in Table 4D foreach classification required.
NOTE: Substitute <ClassificationSystemName> in the property name for the required classification system andtable designation, if applicable . For example, OmniclassTable23 . Examples in Table 4D have used Omniclass
Table 23 .
Property

Description

Data type

ExampleType /
Instance<ClassiﬁcationSystemName>CodeRequired classification code.

Character

23-17-11-00

Type<ClassiﬁcationSystemName>Title

Required classification title.

Character

Doors

Type

<ClassiﬁcationSystemName>Version

Published version of the

Character2012-05-16

Typeclassification system.
Table 4D – OBOS_Classiﬁcation properties

4.7

Construction speciﬁcation properties

This sub-section of the standard defines properties to be assigned to an object to link an object to relevant
construction specification information.
4.7.1

Speciﬁcation linking properties
To provide for linking the object to construction specification information, the set of properties in Table 4E canbe included .
NOTE: Substitute <SpecificationSystem> in the property name for the required specification system or project
specification.
Property<SpeciﬁcationSystem>CodeDescription

Data typeSpecification clause or section

Character

ExampleType /
Instance

0453

Type

Doors and accessTypecode/reference .
<SpeciﬁcationSystem>Title

Specification clause or section

Charactertitle .
<SpeciﬁcationSystem>Version

Published version of thepanelsCharacter

Oct-18Typeclassification system.
Table 4E – OBOS_Speciﬁcation properties

4.8

Asset/Facilities management properties

This sub-section of the standard defines properties to be assigned to an object for ongoing asset or facilities
management purposes.
4.8.1

Asset properties
Where the recording of asset data for asset/facilities management purposes is a requirement, the sets ofproperties in tables 4F, 4G and 4H should be included .

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

12Property
AcquisitionDate

Description

Data type

Date that the manufactured product was

ExampleType /
InstanceDate

2018-03-16

Instance

Integer

9781119060055

Instance

Character

P345

Instance

Character

P345-20180214

Instance

ExampleType /
Instancepurchased .
BarCodeBar code given to an occurrence of the
product .

SerialNumber

Serial number assigned to an occurrenceof a product .

BatchReference

Identity of the batch reference from which
an occurrence of a product is taken .

Table 4F – Pset_ManufacturerOccurrence properties

Property
WarrantyIdentiﬁer

Description

Data type

Identifier assigned to a warranty.

Character

D130ST5135

Type orInstance

WarrantyStartDate

Date on which the warranty commences .

Date2018-03-18

Instance

WarrantyEndDate

Date on which the warranty expires .

Date

2020-03-18

Instance

IsExtendedWarranty

Indication of whether this is an extended

Boolean

TRUE or FALSE*

Instance

Integer

2

Type

Character

Product andType orinstallation

Instance

Character

SupaDoors

Type

Character

Vandalism

Type orwarranty whose duration is greater thanthat normally assigned to a product .
WarrantyPeriod

Time duration during which amanufacturer or supplier guarantees orwarrants the performance of a product .

WarrantyContent

PointOfContact

Content of the warranty .

Organisation that should be contacted foraction under the terms of the warranty .

Exclusions

Items, conditions or actions that may be
excluded from the warranty or that may

Instancecause the warranty to become void .
* Permissible enumerators

Property
ServiceLifeDuration

Table 4G – Pset_Warranty properties

Description
Length or duration of a service life . A lower bound

Data
type

ExampleType /
Instance

Integer

2

Type orInstance

Integer

3

Type orInstance

indicates pessimistic service life, an upper boundindicates optimistic service life, and a single value
indicates the typical service life . Suggested units =Years .
MeanTimeBetweenFailure

Average time duration between instances offailure of a product . Suggested units = Years .
Table 4H – Pset_ServiceLife properties

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

134.8.2COBie properties
The COBie properties in Tables 4J and 4K can be included, if the recording of COBie data is required . Do notinclude any duplicate properties from Tables 4J and 4K if also using properties from Tables 4F, 4G and 4H .
Property

Name

Description

Data type

ExampleType /
Instance

Unique human readable name for object

Character

Door

Type

Character

23-17-11-00

Type

Character

Solid pine timber

Type

type .
Category

Unique identifier of the object within an
external source (classification, document
or library) . It may be human readable(such as a classification code) or not(such as a GUID) depending on thecontext of its usage (which has to be
determined by local agreement) .

Description

Concise description of the object .

door
AssetType

Identifies the predefined types ofCharacter

FIXED orType

MOVABLE*

asset from which the type required
may be set .
Manufacturer

Email address of the organisation that

Characterinfo @ SupaDoors  .FRP

Type

Character

D130STType

Character

info @SupaDoors.com

Typemanufacturered and/or assembled the
product .
ModelNumber

Model number or designator of the
product model (or product line) as
assigned by the manufacturer .

WarrantyGuarantorParts

Email address for organisation
responsible for parts warranty .

WarrantyDurationParts

Duration of parts warranty .

Integer

WarrantyGuarantorLabor

Email address for organisation

Character3
info @ SupaDoors  .com

Type
Type

responsible for labour warranty .
WarrantyDurationLabor

Duration of labour warranty .

Integer

3

Type

WarrantyDurationUnit

Units used to record warranty

Character

Years

Type

durations . Suggested units = Years .
ReplacementCost

Cost to replace product .

Decimal1000 .00

Type

ExpectedLife

Expected serviceable life of product .

Integer

15

Type

DurationUnit

Units used to record expected life

Character

Years

Type

Product andTypeduration . Suggested units = Years .
WarrantyDescription

Concise description of warranty
content and any items, conditions

Characterinstallationor actions that are excluded fromwarranty or that will cause thewarranty to become void .

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

14Property
NominalLength

Description
Typically the primary or larger ofData type

ExampleType /
Instance

Integer800

TypeInteger40

TypeInteger

2100

Type

Character

Solid pine timberTypethe two perpendicular horizontal
dimensions of the product .
NominalWidth

Typically the secondary or smallerof the two perpendicular horizontal
dimensions of the product .

NominalHeight

Typically the vertical characteristic
dimension of the product .

ModelReference

Descriptive model name of the
product model (or product line) as

door

assigned by the manufacturer .
ShapeCharacteristic shape of the product .

Character

Rectangular

Type

Size

Characteristic size of the product .

Character

Large

Type

Color

Characteristic colour of the product.

Character

White

Type

FinishSpecification of surface finish.

Character

Gloss paint

Type

Grade

Standard grading(s) to which theCharacterInternal

Type

Character

Pine

Type

product corresponds .
Material

Characteristic material of which the
product is manufactured .

Constituents

Details of various parts of the product .

Character

Solid panel door

Type

Features

Primary features or important

Character

Single leaf

Type

Character

Automated

Type

Character

Fire rated

Type

Character

Recycled timberTypecharacteristics of the product .
AccessibilityPerformance

Accessibility issue(s) that productsatisfies.

CodePerformance

Code compliance requirement(s) that
product satisfies.

SustainabilityPerformance

Sustainability issue(s) that productsatisfies.

* Permissible enumerators
Table 4J – COBie_Type properties

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

15

Property

Description

SerialNumber

Serial number assigned to an occurrence ofData type

ExampleType /
Instance

Character

D130ST2100X800

InstanceDate

2018-03-18

Instance

a product .
InstallationDate

Date that the manufactured product was
installed .

WarrantyStartDate

Date on which the warranty commences .

Date2018-03-18

Instance

TagNumber

Tag identifier (number or label) for theCharacter

D456

Instance

instance of a product or equipment at
installation .
BarCodeBar code given to the instance of a product .

Integer

9781119060055

Instance

AssetIdentiﬁer

Alternative identifier for specific component,

Character

D456-C

Instanceused as defined by contract.
Table 4K – COBie_Component properties

4.9

Product performance properties

This sub-section of the standard provides for properties relating to product performance or compliance toassigned to the object.
4.9.1

Product declaration/certiﬁcation properties
Where a statutory product declaration template (PDT), product technical statement (PTS), appraisal,
certification or similar exists for the physical element, the object shall include the set of properties included inTable 4L .
NOTE: Substitute <TechnicalDocument> in the property name for the name of the technical document, forexample, CodeMark .
Property<TechnicalDocument1>URL

Description
URL hyperlink to technical

Data type

ExampleType /
Instance

Hyperlinkwww  . codemark  . com / 1234

Type

Hyperlinkwww  . productdata  . com / 1234

Type

document .
<TechnicalDocument2>URL

URL hyperlink to technicaldocument .

Table 4L – OBOS_Technical properties

4.9.2

Technical performance properties
The object can include properties for items scheduled within the technical documents nominated in Table 4L, if
required for the intended BIM use of the object .

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

16

4.10 Property grouping (Property sets)
This sub-section of the standard defines the requirements for grouping properties into property sets andthe use of property sets. This is to facilitate the metadata being in a format consistent with IFC. Not all BIM
authoring systems fully support the concept of property sets in their BIM objects, for example Revit only allows
the user to assign object properties to hard-coded groups. However, the shared parameter file in Revit does
assign a group to each property, which is an equivalent concept to property sets.
4.10.1 Property grouping requirements
Properties shall be grouped together into property sets (groups) for ease of property management,
navigation and display .
Property sets shall be named in accordance with clause 2 .4 .
Properties shall be grouped logically and consistently, across all objects, based on their source and intended
use/function .
If user edited/created property sets are not supported in the BIM authoring system being used, properties
shall be assigned to the most relevant hard-coded property group within the BIM authoring system .
4.10.2 IFC property sets
IFC properties shall be grouped in their relevant IFC property sets (Pset_’s and Qto_’s) .
4.10.3 Source of properties
Properties from any source other than IFC, shall be grouped in a property set, named to clearly identify thesource of the properties . For example, COBie_, ANZRS_ .
If user edited/created property sets are not supported in the BIM authoring system being used, a suffix canbe added to each property name to identify its source, see clause 2 .3 .4 .

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

175.0 Graphical/Geometric Object ModellingThis section of the standard deﬁnes the generic modelling requirements for the graphical element of
the BIM object.

5.1

Object graphical detailThis sub-section of the standard discusses the graphical requirements for generic and proprietary objects.
5.1.1

Generic objects
Generic objects shall be visually recognisable as the object type they represent and dimensions shallrepresent the extent of the object and its connectivity .
Generic objects can include sufficient geometric detail for coordination purposes or to create a visualisation of
the object and envisage its operation and use .

5.1.2

Proprietary objects
Proprietary objects shall be visually recognisable as the physical element they represent and criticaldimensions shall be accurate for coordination purposes .
Proprietary objects can include sufficient geometric detail to create a visualisation of the object and envisage
its operation and use .

5.2

Geometric modelling requirements

This sub-section of the standard discusses the requirements for creating the geometric BIM object, including
requirements for the insertion point, units, scale, tools to be used, dimensioning and labelling.
5.2.1

Modelling tools
The object shall be modelled using the corresponding or most appropriate tool/template from within the BIM
authoring system.
Consideration shall be given to the tool/template selected in regards to the IFC designation that will beassigned to the object, see clause 3 .1 .

5.2.2

Object origin point
The object origin point (or base point) shall be established for the BIM object, from which all object geometry
will be set out .
Object origin points shall be consistent for identical or similar object types to allow for simple substitution ofalternative BIM objects .
The object origin point can correspond to the insertion point of the object, see clause 5 .2 .3 .

5.2.3

Insertion points
An insertion point shall be established for the BIM object that logically represents the placement of the object
in the project model .
Insertion points shall be consistent for identical or similar object types to allow for simple substitution ofalternative BIM objects .
The insertion point should be located within the extent of the object .
Particular consideration shall be given to objects with parametric geometry to allow for the geometry of theobject to change in the model environment and the object’s position to remain correct . For example, theinsertion point of a column should be on its centreline to allow the column size to be changed, if necessary,
without changing the position of the centreline of the column .
NOTE: BIM authoring systems usually require structural items to have their insertion point in the centroid ofthat element to aid any analytical calculations that the model may be used for .

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

18

5.2.4Scale
The object shall be modelled at a scale of 1:1 .

5.2.5

Units
Metric geometry in millimetres shall be used unless specified otherwise by local requirements or if the scale ofthe object being modelled would better suit metres or kilometres .

5.2.6

Fixed geometry
Fixed geometry shall be used where it is not intended for the object to be modifiable. For example, aproprietary object that is only available in one size .

5.2.7

Dimensioning
All dimensions shall be constrained to reference items, such as planes, lines or points, rather than directly togeometry .
Dimensions shall be derived automatically using the associative dimensioning functions within the BIM
authoring system .
Dimensions should be located beyond the extents of the object geometry .
Dimensions shall not overlap and shall be clear to read .

5.2.8

LabelsAll labels shall be constrained to reference items, such as planes, lines or points, rather than directly togeometry .
Labels that reﬂect information contained within the object metadata shall match such data .

5.2.9

Object colour
The default colour of grey can be used for objects that represent physical elements available in more than one
colour .
Alternatively, a representative colour for the physical element can be used .

5.2.10 Drafting conventions
Visual drafting conventions such as line types, hatching and fill shall be utilised, using the relevant tools
available within the BIM authoring system, to distinguish between different parts of the object and to show
variances in depth of surface in different views .
Hatching should be assigned to the relevant materials, or part description, for the object, rather than added as
2D information .
Symbolic lines should be used in plan views, rather than solid geometry .
The use of arrays, formulas and voids when modelling the object should be kept to a minimum .
2D lines and symbols can be used to indicate items that may not be modelled or to complement the 3D
geometric information, such as to indicate ﬂow direction or tap operating direction.
5.2.11 Material assignment
Proprietary objects should have appropriate materials assigned to them to represent the physical element’s
constituent materials .
Generic objects can have materials assigned to them .

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

19

5.3

What to modelThis sub-section of the standard defines what should and shouldn’t be included in the geometric model of theobject, such as maintenance zones, hidden content and other spatial requirements.
5.3.1

Pre-planning
The geometric modelling of the object shall be planned, including any parametric relationships, so as toconsider what graphical detail is required/necessary and what information will be visible in different views .
Note: Small elements or non-critical elements of the object may not require modelling as these may impact
model performance .

5.3.2

DetailThe object shall represent the form of the physical element’s external boundary without providing excessive or
unnecessary detail .
Detail that would not be visible (or hidden), should not be modelled, unless required for the intended BIM use .
For example, the face of a chest of drawers only need show the face of each drawer, the drawer itself shall not
be modelled .

5.3.3

Connection points
Objects that are required to connect to other objects, such as a fan unit to a duct, shall have the relative
position of their connection points accurately modelled .

5.3.4

Spatial requirements
Objects representing physical elements that have spatial requirements, such as clearance zones, operation
zones or maintenance zones, shall also have such spatial requirements modelled .
The modelled spatial requirements shall have their visibility controlled, with the default being that the spatial
zones are not visible .

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

206.0 Object Functionality
This section of the standard discusses the requirements for improving the functionality andperformance of BIM objects so as not to detrimentally affect the performance of a model into which
they may be placed.

6.1

Object performanceThis sub-section of the standard details measures to be taken to reduce the file size of BIM objects to improvemodel performance and reliability.
6.1.1

Purging
All unused or temporary modelling content, such as unused line types, reference items, images, constructionlines or CAD content, shall be purged or deleted from the object when modelling is complete.

6.1.2

Saving and compressing
When the object modelling is complete, the file should be saved, using the ‘Save As’ function, with a different
name to that used during its creation, to remove any temporary history data attached to the original file. Where
supported by the BIM authoring system, the resulting file should also be compressed to minimise its size.

6.1.3

Testing
Objects shall be tested as appropriate to the intended function of the object, to ensure that they perform as
intended .

6.2

Object relationships

This sub-section of the standard discusses the requirements for assemblies, nested objects and objects thatare reliant on other objects to perform as expected.
6.2.1

Reliance
Objects shall be modelled so as not to be reliant on other objects, unless it is a specific requirement of that
object type that it requires a host object, such as a wall mounted light fitting that would be reliant on a wall
object .
Objects with parametric behaviour can be reliant on other object types, see clause 6 .4 .

6.2.2

Assemblies
Assemblies should only be created where it may be necessary or beneficial to represent the group ofcomponent objects collectively within the assembly, rather than as individual component objects .
Assemblies can include multiple objects .

6.2.3

Nested objects
Nested objects (objects embedded within objects) shall only be created where it may be necessary or
beneficial to represent the component objects within the nested object individually from the nested object itself.
Nested objects shall be restricted to two levels (i .e . an object within an object within an object) .

6.3

Visibility/Views

This sub-section of the standard discusses the requirements for the visibility of objects and their display views.
BIM authoring systems control object viewing in different ways, such as layers and subcategories, these needto managed to avoid a proliferation of views within models.
6.3.1

Thumbnails and previews
Thumbnail previews shall be set to a clear, appropriate and consistent view orientation and an appropriate size
and resolution .
All reference items and dimensions shall not be visible in these images .

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

216.3.2

Object resolution
Provision for varying object resolution when viewing the object at different scales shall be provided and thegraphical information displayed shall be controlled .
Three scales of resolution should be sufficient and shall be provided for each object as follows:

6.3.3

•

Coarse: Typically used for low detail, low fidelity views, generally at a scale above 1:100. The geometry
visible shall only be indicative of the physical element and can include symbolic 2D linework .

•Medium: Typically used for views at scales of 1:20 to 1:100. The geometry visible shall be sufficient toserve the purpose of representing the physical element .

•Fine: Typically used for highly detailed views, usually at scales of 1:1 to 1:20 . The geometry visible canreﬂect the detailed geometry of the physical element.

View control
Views shall be named in accordance with clause 2 .6 .
Objects shall be assigned, in a consistent and logical manner, to the appropriate view or views .

6.4

Parametric behaviour

This sub-section of the standard discusses the requirements for creating objects with parametric behaviour.
6.4.1

Functional behaviour
Parametric objects that are reliant upon host objects in/on which they are placed, shall be created with thespecific functionality to manipulate the host object, or vice versa, as necessary to suit their purpose. Such asa parametric window object that shall be modelled so as to create a corresponding void in the wall object into
which it would be placed or alternatively if the wall thickness changed the window dimension would adjust to
suit .

6.4.2

Geometric behaviour
Parametric objects shall be created when an object can represent geometrical variants of an object type .
The parametric capability of the object shall be limited to the available variants of the physical element it
represents . For example, if a physical element is available in 4 different lengths, limit the parametric length
function of the object to those 4 available lengths .

6.4.3

Multiple IFC types
Objects shall not be created with parametric capability to allow the object to represent multiple
IfcElementType’s . For example, do not create one object that can represent a bath and also represent a sink,as these objects are represented by different IfcElementType’s .
In this situation duplicate parametric objects shall be created and assigned the corresponding IfcElementType,one to represent each IfcElementType required . For example, one to represent a parametric bath and one torepresent a parametric sink .

6.4.4

Reference items
When modelling objects with parametric geometry, the parametric behaviour shall be controlled by reference
items such as planes, lines or points .

6.4.5

Use limitation
The use of parametric behaviour shall be limited to that deemed necessary, or required, to avoid overconstraining the functionality of the object .

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

227.0 Import, Export and Linking
This section of the standard discusses methods of importing properties and content into a BIM
object and also any requirements for the preparation of a BIM object for export.

7.1

Importing information

This sub-section of the standard discusses the requirements and recommendations for the import of
information (graphical or non-graphical) into the BIM object. Imported geometry can limit functionality andparametric capability, increase possibility of file corruption and cause increased object file sizes.
7.1.1

Geometric information
Where possible, native geometry within the BIM authoring system should be used .
Geometry can be imported from other authoring systems or sources, but should only be used for temporarymodelling purposes and removed when no longer required, see clause 6 .1 .1 .

7.1.2

External data sets
Data sets (properties and property sets) can be imported into objects .
Imported data sets shall be in accordance with the data requirements of this standard .

7.2

Exporting BIM objects

This sub-section of the standard discusses the requirements and recommendations for the preparation of BIM
objects for export to other BIM applications, such as the requirements for mapping non-conforming hard-coded
properties from the BIM authoring system to the correct IFC property.
7.2.1

IFC assignment
The properties of ‘IfcExportAs’ and ‘IfcExportType’ shall be checked and values completed before object
export, see clause 4 .3 .2 .

7.2.2

Mapping of hard-coded properties
Where a hard-coded property is identical in description/value requirement to a defined IFC property, butdoes not identically reﬂect the name of the corresponding IFC property, then that hard-coded property shall bemapped to the corresponding IFC property at export .
Note: Some BIM authoring systems will automatically map hard-coded properties to the relevant IFC
properties .

7.2.3

External data sets
An object can be linked to external data sets . Any properties required by downstream BIM uses/applications
shall be natively stored on the object at or prior to export, unless such downstream BIM applications can also
access the corresponding data sets .

7.2.4

Test export
Objects shall be tested to ensure export results are as intended .

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

238.0 Deﬁnitions & Glossary
This section of the standard provides deﬁnitions and terms used in the standard.
For the purposes of this standard, the following definitions apply:
ANSI SQLA specification describing the official features of the SQL database language. Everyvariant of SQL relational databases implements a subset of ANSI SQL .

Assemblies

A named aggregation of BIM objects that form another object or functional unit .

Associative Dimensioning

A function of a BIM authoring system that automatically updates the value of a dimension
when changes occur to the geometry of the object .

BIM Authoring System

An application used for generating data for multiple uses that includes 3D geometric
information . EXAMPLES: Autodesk® Revit®, Bentley® AECOsim®, Graphisoft®
ArchiCAD®, Nemetschek® Vectorworks® and Tekla® Structures .

COBie

Construction Operation Buildings information exchange . A representation of ahandover view of the IFC schema, typically seen as a spreadsheet . (ISO 15686-4)

Field

A data field is a place where data is stored. Commonly used to refer to a column ina database or a field in a data entry form or web form. It is generally the smallest
component under which data is captured. This standard applies the concept of fields
to the components of a name (property/file/view) which stores a specific piece of
information .

Generic Object

A generic representation of the common features and properties of a physical element,
intended for use in the early stages of design or when the object is not resolved into a
product .

Hard-coded

A field that is coded into a software user interface where the user has no ability tochange the field name.

IFC

Industrial Foundation Classes (ISO 16739). An open file format developed andmaintained by buildingSMART for the exchange of information enhanced models .

Insertion Point

The point on an object used to place it into a model .

Layered Objects

An object typically constructed from one or more layers of materials to form a building
system . Typically these are “system” objects, provided by the BIM Authoring System
without fixed geometry, where the user can modify the layers and thickness but thegeometry is created on placement in the model .

Library

A collection of reusable BIM objects stored as separate files that are used to facilitate theuse of standardised designed or manufactured elements and objects over a project orseries of projects .

Metadata

The term for the collection of properties, names, or data associated with an object,element or file. (Can also be known as Attributes, Parameters and Properties).

Origin Point

A fixed point of reference for the geometry of the surrounding space defined as X, Y, andZ . Objects have an origin point that all other points in the object reference . A model has
an origin point and objects placed in the model reference this .

Parametric

The use of pre-programmed rules or algorithms to provide the user with the ability tochange or configure objects during modelling.

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

24Property

A characteristic, feature or measurable factor associated with an object that can help
define the object (or system). (Can also be known as Attribute, Parameter or Metadata).

Property Set

A grouping of properties that belong together based on some principle, e .g . viewpoint,
lifecycle stage . (ISO 15686-4)

Proprietary Object

A representation of the common features and properties of an obtainable product .

View Control

A function within the BIM Authoring System that controls which objects, or parts ofobjects, are visible at any time in a model . BIM Authoring Systems control object viewing
in different ways, such as layers or subcategories .

Open BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

25Appendix A - IfcElementType and PredefinedType enumerator listingThis appendix to the OBOS provides a list of the IfcElementType’s, and their associated PredefinedType list of
enumerators, from the IFC4 (Add 2) schema . The list below can be used to designate the BIM object in IFC, in
accordance with clause 3 .1 .1 and clause 4 .3 .2 of the OBOS . The IfcElementType’s are listed in bold formatted text
below, immediately followed by the available PredefinedType enumerators for that IfcElementType in CAPITAL letters .
The IfcElementType shall be used as the value for the ‘IfcExportAs’ property and the PredefinedType shall be used
for the ‘IfcExportType’ property . For the example of a Steam Boiler, the value for the ‘IfcExportAs’ property would be‘IfcBoiler’ and the value for the ‘IfcExportType’ property would be ‘STEAM’ .
IfcActuator
ELECTRICACTUATORHANDOPERATEDACTUATORHYDRAULICACTUATORPNEUMATICACTUATOR
THERMOSTATICACTUATORNOTDEFINEDUSERDEFINED

IfcAirTerminalBox
CONSTANTFLOW
VARIABLEFLOWPRESSUREDEPENDANTVARIABLEFLOWPRESSUREINDEPENDANTNOTDEFINEDUSERDEFINED

IfcAirTerminal
DIFFUSERGRILLELOUVREREGISTERNOTDEFINEDUSERDEFINED

IfcAirToAirHeatRecovery
FIXEDPLATECOUNTERFLOWEXCHANGERFIXEDPLATECROSSFLOWEXCHANGERFIXEDPLATEPARALLELFLOWEXCHANGERHEATPIPEROTARYWHEELRUNAROUNDCOILLOOPTHERMOSIPHONCOILTYPEHEATEXCHANGERS
THERMOSIPHONSEALEDTUBEHEATEXCHANGERSTWINTOWERENTHALPYRECOVERYLOOPSNOTDEFINEDUSERDEFINED

IfcAlarm
BELL
BREAKGLASSBUTTONLIGHT
MANUALPULLBOX
SIREN
WHISTLENOTDEFINEDUSERDEFINED

IfcAudioVisualAppliance
AMPLIFIERCAMERADISPLAY
MICROPHONE
PLAYERPROJECTOR
RECEIVER
Open BIM Object Standard October 2018 v1 .0

SPEAKERSWITCHERTELEPHONE
TUNER
USERDEFINED,NOTDEFINED

IfcBeamBEAM
HOLLOWCOREJOISTLINTEL
SPANDREL
T_BEAM
NOTDEFINEDUSERDEFINED

IfcBoiler
STEAM
WATER
NOTDEFINEDUSERDEFINED

IfcBuildingElementPart
INSULATIONPRECASTPANELNOTDEFINEDUSERDEFINED

IfcBuildingElementProxyPROVISIONFORSPACEPROVISIONFORVOIDNOTDEFINEDUSERDEFINED

IfcBuildingSystem
FENESTRATIONFOUNDATIONLOADBEARING
OUTERSHELL
SHADING
TRANSPORTNOTDEFINEDUSERDEFINED

IfcBurner
NOTDEFINEDUSERDEFINED

IfcCableCarrierFitting
BEND
CROSS
REDUCERTEENOTDEFINEDUSERDEFINED

IfcCableCarrierSegment
CABLELADDERSEGMENT
CABLETRAYSEGMENT
CABLETRUNKINGSEGMENTCONDUITSEGMENT
NOTDEFINEDUSERDEFINED

IfcCableFitting
CONNECTOR
ENTRY
EXIT
JUNCTION
TRANSITIONNOTDEFINEDUSERDEFINED

IfcCableSegment
BUSBARSEGMENT
CABLESEGMENTCONDUCTORSEGMENT
CORESEGMENT
NOTDEFINEDUSERDEFINED

IfcChiller
AIRCOOLEDHEATRECOVERY
WATERCOOLEDNOTDEFINEDUSERDEFINED

IfcChimney
NOTDEFINEDUSERDEFINED

IfcCoil
DXCOOLINGCOIL
ELECTRICHEATINGCOILGASHEATINGCOIL
HYDRONICCOIL
STEAMHEATINGCOIL
WATERCOOLINGCOIL
WATERHEATINGCOIL
NOTDEFINEDUSERDEFINED

IfcColumn
COLUMNPILASTERNOTDEFINEDUSERDEFINED© Masterspec, NATSPEC – All rights reserved26

IfcCommunicationsAppliance
ANTENNACOMPUTERFAXGATEWAYMODEM
NETWORKAPPLIANCENETWORKBRIDGENETWORKHUB
PRINTERREPEATERROUTERSCANNERNOTDEFINEDUSERDEFINED

IfcCompressor
BOOSTERDYNAMICHERMETIC
OPENTYPERECIPROCATINGROLLINGPISTONROTARYROTARYVANESCROLL
SEMIHERMETICSINGLESCREWSINGLESTAGE
TROCHOIDALTWINSCREWWELDEDSHELLHERMETICNOTDEFINEDUSERDEFINED

IfcCondenser
AIRCOOLEDEVAPORATIVECOOLEDWATERCOOLEDWATERCOOLEDBRAZEDPLATEWATERCOOLEDSHELLCOILWATERCOOLEDSHELLTUBE
WATERCOOLEDTUBEINTUBENOTDEFINEDUSERDEFINED

IfcController
FLOATING
MULTIPOSITIONPROGRAMMABLE
PROPORTIONALTWOPOSITIONNOTDEFINEDUSERDEFINED

IfcCooledBeam
ACTIVEPASSIVE
NOTDEFINEDUSERDEFINED

IfcCoolingTower
MECHANICALFORCEDDRAFTMECHANICALINDUCEDDRAFT
NATURALDRAFTNOTDEFINEDUSERDEFINEDOpen BIM Object Standard October 2018 v1 .0

IfcCovering
CEILING
CLADDING
FLOORING
INSULATIONMEMBRANEMOLDINGNOT DEFINEDROOFINGSKIRTINGBOARDSLEEVING
WRAPPING
USERDEFINED

IfcCurtainWall
NOTDEFINEDUSERDEFINED

IfcDamper
BACKDRAFTDAMPERBALANCINGDAMPER
BLASTDAMPER
CONTROLDAMPER
FIREDAMPER
FIRESMOKEDAMPER
FUMEHOODEXHAUSTGRAVITYDAMPERGRAVITYRELIEFDAMPERRELIEFDAMPERSMOKEDAMPERNOTDEFINEDUSERDEFINED

IfcDiscreteAccessory
ANCHORPLATE
BRACKETSHOENOTDEFINEDUSERDEFINED

IfcDistributionChamberElement
FORMEDDUCTINSPECTIONCHAMBERINSPECTIONPIT
MANHOLEMETERCHAMBER
SUMP
TRENCHVALVECHAMBERNOTDEFINEDUSERDEFINED

IfcDistributionPort
CABLE
CABLECARRIER
DUCT
PIPE
NOTDEFINEDUSERDEFINED

IfcDistributionSystem
AIRCONDITIONING
AUDIOVISUALCHEMICALCHILLEDWATERCOMMUNICATIONCOMPRESSEDAIR
CONDENSERWATERCONTROLCONVEYINGDATADISPOSALDOMESTICCOLDWATERDOMESTICHOTWATERDRAINAGE
EARTHING
ELECTRICAL
ELECTROACOUSTIC
EXHAUSTFIREPROTECTIONFUELGASHAZARDOUSHEATING
LIGHTING
LIGHTNINGPROTECTIONMUNICIPALSOLIDWASTE
OIL
OPERATIONAL
POWERGENERATIONRAINWATER
REFRIGERATIONSECURITY
SEWAGE
SIGNALSTORMWATERTELEPHONE
TV
VACUUM
VENT
VENTILATIONWASTEWATER
WATERSUPPLYNOTDEFINEDUSERDEFINED

IfcDoorDOOR
GATE
TRAPDOORNOTDEFINED

IfcDuctFitting
BEND
CONNECTOR
ENTRY
EXIT
JUNTION
OBSTRUCTION
TRANSITIONNOTDEFINEDUSERDEFINED

IfcDuctSegment
FLEXIBLESEGMENTRIGIDSEGMENT
NOTDEFINEDUSERDEFINED

IfcDuctSilencer
FLATOVALRECTANGULARROUNDNOTDEFINEDUSERDEFINED© Masterspec, NATSPEC – All rights reserved27

IfcElectricAppliance
DISHWASHER
ELECTRICCOOKERFREESTANDINGELECTRICHEATER
FREESTANDINGFANFREESTANDINGWATERCOOLERFREESTANDINGWATERHEATER
FREEZERFRIDGE_FREEZER
HANDDRYER
KITCHENMACHINEMICROWAVE
PHOTOCOPIERREFRIGERATOR
TUMBLEDRYERVENDINGMACHINEWASHINGMACHINENOTDEFINEDUSERDEFINED

IfcElectricDistributionBoard
CONSUMERUNIT
DISTRIBUTIONBOARD
MOTORCONTROLCENTRE
SWITCHBOARD
NOTDEFINEDUSERDEFINED

IfcElectricFlowStorageDevice
BATTERYCAPACITORBANKHARMONICFILTERINDUCTORBANKUPSNOTDEFINEDUSERDEFINED

IfcElectricGenerator
CHP
ENGINEGENERATORSTANDALONENOTDEFINEDUSERDEFINED

IfcElectricMotorDC
INDUCTION
POLYPHASE
RELUCTANCESYNCHRONOUS
SYNCHRONOUS
NOTDEFINEDUSERDEFINED

IfcElectricTimeControl
RELAY
TIMECLOCKTIMEDELAYNOTDEFINEDUSERDEFINED

IfcEngine
EXTERNALCOMBUSTIONINTERNALCOMBUSTIONNOTDEFINEDUSERDEFINED

IfcEvaporativeCooler
DIRECTEVAPORATIVEAIRWASHER
Open BIM Object Standard October 2018 v1 .0

DIRECTEVAPORATIVEPACKAGEDROTARYAIRCOOLERDIRECTEVAPORATIVERANDOMMEDIAAIRCOOLERDIRECTEVAPORATIVERIGIDMEDIAAIRCOOLERDIRECTEVAPORATIVESLINGERSPACKAGEDAIRCOOLERINDIRECTDIRECTCOMBINATION
INDIRECTEVAPORATIVECOOLINGTOWERORCOILCOOLERINDIRECTEVAPORATIVEPACKAGEAIRCOOLERINDIRECTEVAPORATIVEWETCOIL
NOTDEFINEDUSERDEFINED

IfcEvaporator
DIRECTEXPANSIONDIRECTEXPANSIONBRAZEDPLATE
DIRECTEXPANSIONSHELLANDTUBE
DIRECTEXPANSIONTUBEINTUBEFLOODEDSHELLANDTUBE
SHELLANDCOIL
NOTDEFINEDUSERDEFINEDIfcFanCENTRIFUGALAIRFOIL
CENTRIFUGALBACKWARDINCLINEDCURVED
CENTRIFUGALFORWARDCURVED
CENTRIFUGALRADIALPROPELLORAXIAL
TUBEAXIALVANEAXIALNOTDEFINEDUSERDEFINEDIfcFastener
GLUE
MORTARWELD
NOTDEFINEDUSERDEFINEDIfcFilter
AIRPARTICLEFILTERCOMPRESSEDAIRFILTERODORFILTEROILFILTERSTRAINER
WATERFILTERNOTDEFINEDUSERDEFINEDIfcFireSuppressionTerminal
BREECHINGINLET
FIREHYDRANT
HOSEREELSPRINKLERSPRINKLERDEFLECTORNOTDEFINEDUSERDEFINEDIfcFlowInstrument
AMMETERFREQUENCYMETER
PHASEANGLEMETER
POWERFACTORMETERPRESSUREGAUGETHERMOMETER
VOLTMETER_PEAK
VOLTMETER_RMS
NOTDEFINEDUSERDEFINEDIfcFlowMeter
ENERGYMETERGASMETEROILMETERWATERMETERNOTDEFINEDUSERDEFINEDIfcFooting
CAISSON_FOUNDATIONFOOTING_BEAM
PAD_FOOTINGPILE_CAP
STRIP_FOOTINGNOTDEFINEDUSERDEFINEDIfcFurniture
BED
CHAIR
DESK
FILECABINET
SHELF
SOFA
TABLE
NOTDEFINEDUSERDEFINED

IfcGeographicElement
TERRAINNOTDEFINEDUSERDEFINED

IfcHeatExchanger
PLATE
SHELLANDTUBENOTDEFINEDUSERDEFINED

IfcHumidiﬁer
ADIABATICAIRWASHERADIABATICATOMIZINGADIABATICCOMPRESSEDAIRNOZZLEADIABATICPANADIABATICRIGIDMEDIAADIABATICULTRASONICADIABATICWETTEDELEMENTASSISTEDBUTANEASSISTEDELECTRICASSISTEDNATURALGASASSISTEDPROPANEASSISTEDSTEAM
STEAMINJECTIONNOTDEFINEDUSERDEFINED

IfcInterceptor
CYCLONIC
GREASEOILPETROLNOTDEFINEDUSERDEFINED© Masterspec, NATSPEC – All rights reserved28

IfcJunctionBox
DATA
POWER
NOTDEFINEDUSERDEFINED

IfcLamp
COMPACTFLUORESCENTFLUORESCENT
HALOGENHIGHPRESSUREMERCURYHIGHPRESSURESODIUMLEDMETALHALIDEMETALHALIDEOLEDTUNGSTENFILAMENTNOTDEFINEDUSERDEFINED

IfcLightFixture
DIRECTIONSOURCE
POINTSOURCESECURITYLIGHTINGNOTDEFINEDUSERDEFINED

IfcMechanicalFastener
ANCHORBOLT
BOLT
DOWEL
NAIL
NAILPLATE
RIVET
SCREW
SHEARCONNECTOR
STAPLESTUDSHEARCONNECTORNOTDEFINEDUSERDEFINED

IfcMedicalDevice
AIRSTATIONFEEDAIRUNITOXYGENGENERATOROXYGENPLANT
VACUUMSTATIONNOTDEFINEDUSERDEFINED

IfcMember
BRACE
CHORD
COLLARMEMBER
MULLION
PLATE
POST
PURLINRAFTERSTRINGERSTRUTSTUDNOTDEFINEDUSERDEFINEDOpen BIM Object Standard October 2018 v1 .0

IfcMotorConnection
BELTDRIVE
COUPLING
DIRECTDRIVE
NOTDEFINEDUSERDEFINED

IfcOutlet
AUDIOVISUALOUTLETCOMMUNICATIONSOUTLETDATAOUTLET
POWEROUTLETTELEPHONEOUTLETNOTDEFINEDUSERDEFINED

IfcPileBORED
COHESION
DRIVENFRICTIONJETGROUTINGSUPPORTNOTDEFINEDUSERDEFINED

IfcPipeFitting
BEND
CONNECTOR
ENTRY
EXIT
JUNCTIONOBSTRUCTION
TRANSITIONNOTDEFINEDUSERDEFINED

IfcPipeSegment
CULVERTFLEXIBLESEGMENTGUTTER
RIGIDSEGMENTSPOOL
NOTDEFINEDUSERDEFINED

IfcPlate
CURTAIN_PANELSHEETNOTDEFINEDUSERDEFINED

IfcProtectiveDeviceTrippingUnit
ELECTROMAGNETIC
ELECTRONICRESIDUALCURRENT
THERMALNOTDEFINEDUSERDEFINED

IfcProtectiveDevice
CIRCUITBREAKER
EARTHLEAKAGECIRCUITBREAKER
EARTHINGSWITCHFUSEDISCONNECTORRESIDUALCURRENTCIRCUITBREAKERRESIDUALCURRENTSWITCH
VARISTORNOTDEFINEDUSERDEFINED

IfcPump
CIRCULATORENDSUCTIONSPLITCASE
SUBMERSIBLEPUMP
SUMPPUMP
VERTICALINLINEVERTICALTURBINENOTDEFINEDUSERDEFINED

IfcRailing
BALUSTRADE
GUARDRAIL
HANDRAILNOTDEFINEDUSERDEFINED

IfcRampFlight
SPIRALSTRAIGHT
NOTDEFINEDUSERDEFINED

IfcRamp
HALF_TURN_RAMPQUARTER_TURN_RAMPSPIRAL_RAMP
STRAIGHT_RUN_RAMP
TWO_QUARTER_TURN_RAMP
TWO_STRAIGHT_RUN_RAMP
NOTDEFINEDUSERDEFINED

IfcReinforcingBar
ANCHORINGEDGE
LIGATURE
MAIN
PLAIN
PUNCHING
RING
SHEAR
STUD
TEXTUREDNOTDEFINEDUSERDEFINED

IfcReinforcingElement
BAR
MESH
PUNSHINGSHEARREINFORCEMENTTENDONTENDONANCHORTENDONSHEATHNOTDEFINEDUSERDEFINED

IfcReinforcingMesh
NOTDEFINEDUSERDEFINED© Masterspec, NATSPEC – All rights reserved29

IfcRoof
BARREL_ROOF
BUTTERFLY_ROOF
DOME_ROOF
FLAT_ROOF
FREEFORM
GABLE_ROOF
GAMBREL_ROOF
HIP_ROOF
HIPPED_GABLE_ROOF
MANSARD_ROOF
PAVILION_ROOF
RAINBOW_ROOF
SHED_ROOF
NOTDEFINEDUSERDEFINED

IfcSanitaryTerminal
BATH
BIDET
CISTERN
SANITARYFOUNTAINSHOWERSINK
TOILETPAN
URINAL
WASHHANDBASIN
NOTDEFINEDUSERDEFINED

IfcSensor
CO2SENSORCONDUCTANCESENSORCONTACTSENSORCOSENSORFIRESENSORFLOWSENSORFROSTSENSOR
GASSENSORHEATSENSORHUMIDITYSENSORIDENTIFIERSENSORIONCONCENTRATIONSENSORLEVELSENSOR
LIGHTSENSOR
MOISTURESENSOR
MOVEMENTSENSOR
PHSENSORPRESSURESENSOR
RADIATIONSENSOR
RADIOACTIVITYSENSORSMOKESENSOR
SOUNDSENSORTEMPERATURESENSOR
WINDSENSORNOTDEFINEDUSERDEFINED

IfcShadingDevice
AWNINGJALOUSIE
SHUTTERNOTDEFINEDUSERDEFINED

IfcSlab
BASESLABOpen BIM Object Standard October 2018 v1 .0

FLOOR
LANDINGROOF
NOTDEFINEDUSERDEFINED

IfcSolarDevice
SOLARCOLLECTORSOLARPANELNOTDEFINEDUSERDEFINED

IfcSpaceHeater
CONVECTOR
RADIATORNOTDEFINEDUSERDEFINED

IfcSpace
EXTERNAL
GFA
INTERNAL
PARKINGSPACENOTDEFINEDUSERDEFINED

IfcSpatialZone
CONSTRUCTIONFIRESAFETY
LIGHTING
OCCUPANCYSECURITY
THERMAL
TRANSPORTVENTILATIONNOTDEFINEDUSERDEFINED

IfcStackTerminal
BIRDCAGE
COWL
RAINWATERHOPPERNOTDEFINEDUSERDEFINED

IfcStairFlight
CURVED
FREEFORMSPIRALSTRAIGHT
WINDERNOTDEFINEDUSERDEFINED

IfcStair
CURVED_RUN_STAIR
DOUBLE_RETURN_STAIR
HALF_TURN_STAIR
HALF_WINDING_STAIRQUARTER_TURN_STAIRQUARTER_WINDING_STAIRSPIRAL_STAIR
STRAIGHT_RUN_STAIR
THREE_QUARTER_TURN_STAIR
THREE_QUARTER_WINDING_STAIR
TWO_CURVED_RUN_STAIR
TWO_QUARTER_TURN_STAIR
TWO_QUARTER_WINDING_STAIR

TWO_STRAIGHT_RUN_STAIRNOTDEFINEDUSERDEFINEDIfcSwitchingDevice
CONTACTOR
DIMMERSWITCHEMERGENCYSTOPKEYPADMOMENTARYSWITCH
SELECTORSWITCHSTARTERSWITCHDISCONNECTORTOGGLESWITCHNOTDEFINEDUSERDEFINED

IfcSystemFurnitureElement
PANEL
WORKSURFACENOTDEFINEDUSERDEFINED

IfcTank
BASIN
BREAKPRESSURE
EXPANSIONFEEDANDEXPANSIONPRESSUREVESSELSTORAGEVESSELNOTDEFINEDUSERDEFINED

IfcTendonAnchor
COUPLERFIXED_ENDTENSIONING_END
NOTDEFINEDUSERDEFINED

IfcTendon
BAR
COATEDSTRANDWIRE
NOTDEFINEDUSERDEFINED

IfcTransformer
CURRENTFREQUENCY
INVERTERRECTIFIER
VOLTAGENOTDEFINEDUSERDEFINED

IfcTransportElement
CRANEWAY
ELEVATORESCALATORLIFTINGGEAR
MOVINGWALKWAYNOTDEFINEDUSERDEFINED© Masterspec, NATSPEC – All rights reserved30

IfcTubeBundle
FINNEDNOTDEFINEDUSERDEFINEDIfcUnitaryControlElement
ALARMPANELCONTROLPANELGASDETECTIONPANELHUMIDISTATINDICATORPANELMIMICPANELTHERMOSTATWEATHERSTATIONNOTDEFINEDUSERDEFINEDIfcUnitaryEquipment

IfcWasteTerminal
FLOORTRAP
FLOORWASTEGULLYSUMPGULLYTRAPROOFDRAINWASTEDISPOSALUNITWASTETRAPNOTDEFINEDUSERDEFINED

IfcWindow
LIGHTDOMESKYLIGHT
WINDOWNOTDEFINEDUSERDEFINEDAIRCONDITIONINGUNITAIRHANDLER
DEHUMIDIFIERROOFTOPUNIT
SPLITSYSTEMNOTDEFINEDUSERDEFINED

IfcValve
AIRRELEASEANTIVACUUM
CHANGEOVERCHECKCOMMISSIONING
DIVERTINGDOUBLECHECKDOUBLEREGULATINGDRAWOFFCOCKFAUCET
FLUSHINGGASCOCKGASTAPISOLATINGMIXINGPRESSUREREDUCINGPRESSURERELIEF
REGULATING
SAFETYCUTOFFSTEAMTRAPSTOPCOCKNOTDEFINEDUSERDEFINED

IfcVibrationIsolator
COMPRESSIONSPRINGNOTDEFINEDUSERDEFINED

IfcWall
MOVABLEPARAPETPARTITIONINGPLUMBINGWALLPOLYGONALSHEAR
SOLIDWALLNOTDEFINEDUSERDEFINEDOpen BIM Object Standard October 2018 v1 .0© Masterspec, NATSPEC – All rights reserved

31Open BIM
O b j e ct sta nda rdFirst published 2018 v1.0

PublisherConstruction Information Systems Limited, Sydney, Australia (ABN 20 117 574 606) and Construction Information Ltd, Auckland,
New Zealand .
We welcome comments or suggestions for improvements to the Open BIM Object standard and encourage readers to notify us
immediately of any apparent inaccuracies or ambiguities . Contact us via email at bim@natspec .com .au or bim@masterspec .co .nz .

Copyright
This Document is protected by Copyright © 2018 . You may use this Document for your own purposes . You may distribute thisDocument to other persons provided that you attribute the Document as having been generated by NATSPEC and Masterspec andthat the document is available free of charge .