Including this data in your BIM objects will ensure you meet the minimum requirements for content to be usable throughout a Building Information Modelling process.

To help illustrate the data required, examples are included for the TEMPOSOFT 2 Time Flow Tap manufactured by Delabie.

Feedback or questions are welcomed in the comments section at the bottom of this page.
COBie Properties
IFC Properties
NBS Properties
Bimstore Properties

Construction Operations Building Information Exchange (COBie)

COBie is a standard for gathering data about a building during design and construction. This digital information is transferred to the operations and maintenance (O&M) team.

Unless specified, not all products require COBie. Download the ‘COBie Responsibility Matrix’ (link below) for a list of building products that require Type and Component data.

Type Properties

Type properties contain specification information. The type of product, references and manufacturer contact information.

Property NameExampleValueRequired
NameTEMPOSOFT 2 Time Flow TapTextRequired
CreatedByinfo@delabie.co.ukEmailRequired
CreatedOn1900-12-31T23:59:59DateRequired
CategoryPr_40_20_87_98:Washbasin tapsPicklistRequired
DescriptionDeck-mounted time flow basin tapTextRequired
AssetTypeFixedPicklistRequired
Manufacturerinfo@delabie.co.ukEmailRequired
ModelNumber740500TextRequired
WarrantyGuarantorPartstechnical@delabie.co.ukEmailRequired
WarrantyDurationParts10IntegerRequired
WarrantyGuarantorLaborn/aEmailRequired
WarrantyDurationLabor0IntegerRequired
WarrantyDurationUnityearPicklistRequired
ReplacementCost0NumberIf Specified
ExpectedLife10IntegerIf Specified
DurationUnityearPicklistRequired
WarrantyDescription10-year warranty on any manufacturing defectTextIf Specified
NominalLength100NumberRequired
NominalWidth35NumberRequired
NominalHeight75NumberRequired
ModelReferenceTEMPOSOFT 2TextIf Specified
ShapeCylinderTextIf Specified
Sizen/aTextIf Specified
ColorChromeTextIf Specified
FinishChrome-platedTextIf Specified
GradeWRAS ApprovedTextIf Specified
MaterialSolid brassTextIf Specified
ConstituentsSolid chrome-plated brass body with flow straightenerTextIf Specified
FeaturesSoft-touch operation, tamperproof scale-resistant flow straightenerTextIf Specified
AccessibilityPerformanceSoft-touch operationTextIf Specified
CodePerformancen/aTextIf Specified
SustainabilityPerformanceWater saving - flow rate pre-set at 3 lpm at 3 barTextIf Specified

Component Properties

Component properties (or ‘Instance’ parameters as referred to in Revit), contain individually scheduled types that require management, such as maintenance, servicing or replacement.

Property NameExampleValueRequired
NameTEMPOSOFT 2 Time Flow TapTextRequired
DescriptionDeck-mounted time flow basin tapTextRequired
SerialNumbern/aTextIf Specified
InstallationDate1900-12-31T23:59:59DateIf Specified
WarrantyStartDate1900-12-31T23:59:59DateIf Specified
TagNumbern/aTextIf Specified
BarCoden/aTextIf Specified
AssetIdentifiern/aTextIf Specified

Source:

COBie Responsibility Matrix (Version 17) – April 2013


Industry Foundation Class (IFC) Properties

IFC is an open industry format that enables the exchange of data between different software platforms.

IFC properties will vary by product, in particular those with performance values. Additional properties may be required if specified by the employer.

Property NameExampleValueRequired
IfcTypeProductIfcValveType FAUCETTextIf Specified
IfcProductIfcFlowControllerTextIf Specified

Source:

IFC2x (Edition 3) – July 2007


National Building Specification (NBS) Type Parameters

Property NameExampleValueRequired
AuthorDelabieTextIf Specified
ManufacturerNameDelabieTextIf Specified
ManufacturerURLhttp://www.delabie.co.uk/URLIf Specified
NBSDescriptionWater supply fittings for wash basins and troughsTextIf Specified
NBSReference45-35-70/371TextIf Specified
ProductInformationhttp://www.delabie.co.uk/products/740500URLIf Specified
Revisionn/aTextIf Specified
Uniclass2015CodePr_40_20_87_98TextIf Specified
Uniclass2015TitleWashbasin tapsTextIf Specified
Uniclass2015VersionProducts v1.10TextIf Specified
Version1IntegerIf Specified

Source:

NBS BIM Object Standard (Version 2.0) – January 2018


Bimstore Type Properties

Property NameExampleValueRequired
_CurrentRevision1IntegerIf Specified
_CreatedByhttp://www.delabie.co.uk/URLIf Specified
_DistributedByhttp://www.bimstore.co.uk/URLIf Specified
_AuthorDelabieTextIf Specified
_BimSpecGuid0IntegerIf Specified
_BSBibleVersion15IntegerIf Specified
SparePartsn/aTextIf Specified
ProductionYearn/aTextIf Specified
ReferencedStandardn/aTextIf Specified
DocumentationTechnicalhttp://www.delabie.co.uk/products/740500URLIf Specified
DocumentationCertificateshttp://www.delabie.co.uk/products/740500URLIf Specified
DocumentationLiteraturehttp://www.delabie.co.uk/products/740500URLIf Specified
DocumentationInstallationGuidehttp://www.delabie.co.uk/products/740500URLIf Specified
ClassificationNameUniclass2015TextIf Specified
ClassificationValuePr_40_20_87_98TextIf Specified

Source:

Bimstore Bible (Version 15) – July 2017


Share this Guide to BIM Object Data with friends and colleagues.

9 Comments

  1. Craig Sewell

    There is little information available on what data manufacturers should embed in BIM objects. I have put this guide together as a starting point.

    It is important we as manufacturers are not providing information for the sake of it. But, we do need some guidance from the industry (and clients) to get this right.

    Please share your experiences on manufacturer data in the box below.

  2. Jonny Morgan

    Hi Craig,

    As an architect and specifier in a BIM environment, a few observations and queries come to mind, that you may be able to develop on:

    We are starting to see more and more suppliers information being made available in the industry, (which is great and aids us as specifiers, as well as assists us in meeting deliverables we are now seeing from clients), however subject to how and who this has been created by, impacts on the integrity and level of data available. Do you know about any further developments regarding common data standards for supplier components? The tables above clearly highlight the data fields that the industry are using, which are being made available by the leading component creators as well as the intended level 2 industry deliverables (COBie), however the amount of duplication of information that would need to be present in components if manufacturers were to add all of these seems over kill to me.

    We have recently completed a project where we had a Final Handover BIModel deliverable, together with asset information fields made available for ongoing maintenance. We swapped out generic components for product specific components (following contractor appointment), if they were available, however there were very specific non graphical data requirements for ongoing FM that were required by the client that would not typically be available in components and are not noted above (client specific). Do you think it is ok for us as architects to make these fields available in a supplier specific component?
    What do you feel is the best way to make these asset data fields available within a suppliers component?

    Whilst we have developed and streamlined our own internal processes aligned to industry standards in existence and continue to develop these as new standards come out and existing ones are revised, one of the most important factors for us is to talk to like minded people in the industry and share experiences. BIM means different things to different people, however only through communication of our experiences, both positive and negative can we learn and move forward as a collaborative industry.

  3. Teejay Gundu

    This is a very very helpful piece of article. I am currently working within my company developing BIM models and I am seeing how ridiculous it is to try and incorporate all specs as Jonny has mentioned. If one model was to be hosted on three different sites, it seems I would have to create 3 separate model, in terms of data.

    I have not yet had experience/encounters with any architects but I’ll be sure to let you know.

    • Craig Sewell

      Thanks Teejay. I look forward to you sharing your feedback as you progress with BIM at Warrior Doors.

  4. Chris Crookes

    Great article – this certainly helps round up the current set of requirements. We broadly agree with what you have listed however we would recommend the addition of Uniclass2015. The IFC parameters would vary depending upon the component to be modelled. Keep up the good work!

    • Craig Sewell

      Thanks Chris, you are correct regarding IFC parameters. Product manufacturers wanting to learn more can visit the link provided under the IFC section above.

  5. Jose Vargas

    Great reflections on BIM Craig! I’m working in Brazil with BIM, and your articles have been helpful for my discussions in many cases! Thank you so much!

    • Craig Sewell

      That’s great to hear Jose – wishing you continued success over in Brazil!

  6. Tim Aikin

    Jonny Morgan makes a really important point about the workflow, quality and availability of BIM Objects. Should the design team be required to swap out generic components for manufacturers ones? It requires common data structures without this then it’s just a big overhead and that means there is no efficiency at this part of the process.

    On a project I am working on, the Contractor is obtaining the Asset Information from the supply chain using spread sheets. We did try to get them to use a PDT format but they were set up for their own method. We are then processing their data in to our Product Library (imports/exports COBie) and completing the data set (photos, associated documents etc.). Then this is being imported/transferred into an Asset Information Model (imports/exports COBie) which is built up from the different 3D BIM models. Asset Types are updated to the actual products in this environment. The Product Library in addition to imports has a direct link for the AIM app to the product library app. It’s our common data environment.

    This workflow is not uncommon and examples are Solibri, 4Projects, Conject not to mention some CAD vendors.

    To speed up the process of getting information into the Product Library we have developed different tools one being an exporter for Revit Families. This exports from a Revit Family a COBie data set (xml, json and xlsx). It parses the parameters data, mapping to the Cobie.Type table and anything else is put in Cobie.Attribute. This process shows up an incredible lack of consistency between object libraries but at least we get the core Asset Information which for clients is Product Name, description, ModelNumber, ModelReference. We already have the Supplier Address which invariably is missing from the objects because supplier information will vary between countries.

    Obviously we have developed our own technology, which we can develop as standalone and connected rather then buried in functionality of one single system. As we are in the FM domain we have to have a product library with depth of quality information. Ultimately for validity and authority this will be synchronised directly with product manufacturers via data services and not through 3rd party objects. (in my opinion)


Leave a reply