Difference between revisions of "OpenBIM Manufacturer Content"

From Wiki.OSArch
Line 27: Line 27:
 
A manufacturer will often think of asking a consultant they have worked with on projects to make some content they can share with other consultants. Typically this will then be offered in the format of the consultant company, often this will be the dominant software platform for that type of content in that region.
 
A manufacturer will often think of asking a consultant they have worked with on projects to make some content they can share with other consultants. Typically this will then be offered in the format of the consultant company, often this will be the dominant software platform for that type of content in that region.
  
In this example the client has asked for Revit Families of their zip screen / sun screen. As a supporter of cross platform solutions, and to support the client in widening the market for their product, one would want to make the digital asset available to multiple software platforms. In this case the targets are
+
== File Formats ==
 +
In this example the client has asked for Revit Families of their zip screen / sun screen. As a supporter of cross platform solutions, and to support the client in widening the market for their product, one would want to make the digital asset available to multiple software platforms. In this case the targets are:
 
* Autodesk [[Revit]]
 
* Autodesk [[Revit]]
 
* Trimble [[SketchUp]]
 
* Trimble [[SketchUp]]
 
* Graphisoft [[ArchiCAD]]
 
* Graphisoft [[ArchiCAD]]
 
* McNeil [[Rhinoceros 3D]]
 
* McNeil [[Rhinoceros 3D]]
 +
 +
== Manufacturer Data ==
 +
'''Revit Family'''
 +
The manufacturer has some data they want stored in the native Revit Family RFA file. To standardize this is should be stores according to [[BuildingSMART_Data_Dictionary_(bSDD)|bSDD]] conventions. For example the [http://bsdd.buildingsmart.org/#concept/details/3_kLW3eI10Xem4Z9zSCTzp bSDD data for an electric motor] can be used to structure information about efficiency class, voltage, model and much more.
  
 
[[Category:Industry Foundation Classes (IFC)]]
 
[[Category:Industry Foundation Classes (IFC)]]

Revision as of 20:14, 28 November 2020

This page is unfinished. Feel free to help the project by sharing your knowledge about this subject.


Introduction

OpenBIM is all about making access to data and interoperability easy and lossless. Manufacturer content, such as you can find online at sites like BIMobject, typically offer files to designers authored in proprietary formats specifically for an intended software platform. A better solution would be the exclusive use of Open Formats.

Selecting a file format

Each file format has different strengths and weaknesses. This articles focuses on interoperability and use of open formats.

There are several advantages in using Industry Foundation Classes (IFC) as a format for manufacturer content.

  • There is some ability to store some parametric geometry
  • IFC is an a widely supported open file format
  • All the information contained in an IFC file is available to the owner of the file

There are also some disadvantages to using IFC

  • Each geometric object can only have one material
  • Parametric controls are limited

There is a File_format_comparison useful for selecting relevant file formats.

Storing object data

BuildingSMART_International has developed the BuildingSMART Data Dictionary (bSDD) as a multi lingual standardized description framework for object data.

Example

The following section (and this whole page) is to document an ongoing project and will be updated as the project progresses. Contact Duncan Lithgow if you have some input you think is relevant (or just edit this page).

A manufacturer will often think of asking a consultant they have worked with on projects to make some content they can share with other consultants. Typically this will then be offered in the format of the consultant company, often this will be the dominant software platform for that type of content in that region.

File Formats

In this example the client has asked for Revit Families of their zip screen / sun screen. As a supporter of cross platform solutions, and to support the client in widening the market for their product, one would want to make the digital asset available to multiple software platforms. In this case the targets are:

Manufacturer Data

Revit Family The manufacturer has some data they want stored in the native Revit Family RFA file. To standardize this is should be stores according to bSDD conventions. For example the bSDD data for an electric motor can be used to structure information about efficiency class, voltage, model and much more.