I think this is the biggest mental shift to make when considering OpenUSD.
It allows splitting the data representation from the render pipeline.
On the data side, OpenUSD can support BIM just fine:
• Can store the geo representation, will render as long is there is a plugin written to render it (for systems that don't, the geo is still available to query)
• Can store additional information either on the same file, referenced in a different referenced file (ex.: In-wall pipe layouts can be referenced from the main construction file to keep it small)
• Can 'layer' additional information and resolve conflicts according to a well-defined resolution method, allowing multiple authors.
It allows splitting the data representation from the render pipeline.
On the data side, OpenUSD can support BIM just fine:
• Can store the geo representation, will render as long is there is a plugin written to render it (for systems that don't, the geo is still available to query) • Can store additional information either on the same file, referenced in a different referenced file (ex.: In-wall pipe layouts can be referenced from the main construction file to keep it small) • Can 'layer' additional information and resolve conflicts according to a well-defined resolution method, allowing multiple authors.