Editing OpenBIM Manufacturer Content

{{stub}}

= 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 [https://www.bimobject.com 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 [https://en.wikipedia.org/wiki/Open_format Open Formats]. 

= File formats =

== 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

Candidate file formats and criteria are

{| class="wikitable sortable"
! Format
! Open Format?
! Support
! Stores metadata
! Stores materials
! Stores parametric controls
|-
| GSM
| No
| [[ArchiCAD]]
| Yes (proprietary)
| Yes (proprietary)
| Yes (proprietary)
|-
| IFC
| [[Industry_Foundation_Classes_(IFC)|Yes]]
| [[ArchiCAD]], [[Autodesk Revit]], [[Blender]], [[FreeCAD]], Rhino, SketchUp, Tekla, and [https://technical.buildingsmart.org/resources/software-implementations/ over 300 other software].
| Yes (ISO-compliant)
| Yes (ISO-compliant)
| Basic (ISO-compliant)
|-
| RFA
| No
| [[Revit]], [https://www.opendesign.com/products/bimrv bimrv]
| Yes (proprietary)
| Yes (proprietary)
| Yes (proprietary)
|-
| DWG
| No
| Most proprietary CAD, not compatible with most open source CAD
| Basic (proprietary)
| Basic (proprietary)
| No
|-
| DXF
| [http://help.autodesk.com/view/OARX/2018/ENU/?guid=GUID-235B22E0-A567-4CF6-92D3-38A2306D73F3 Yes]
| Supported by all that support DWG, plus all open source CAD
| Basic
| Basic
| No
|-
| STL
| Yes
| [[Blender]], [[FreeCAD]], Rhino, SketchUp
| No
| Possible, but inconvenient
| No
|-
| [https://en.wikipedia.org/wiki/ISO_10303-21 STEP]
| [https://en.wikipedia.org/wiki/ISO_10303-21 Yes]
| Good
| ?
| 
| 
|-
| OBJ
| [https://en.wikipedia.org/wiki/Wavefront_.obj_file Yes]
| Good
| ?
| Yes (.mtl)
| 
|-
| FBX
| No
| Good
| ?
| 
| 
|-
| SKP
| No
| [[SketchUp]]
| Yes (proprietary)
| Yes (proprietary)
| Yes (proprietary)
|}

== 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.

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]]
* Trimble [[SketchUp]]
* Graphisoft [[ArchiCAD]]
* McNeil [[Rhinoceros 3D]]

[[Category:Industry Foundation Classes (IFC)]]