OBD and most -if not all- BIM authoring apps on the market are based on placing 'generic' BIM objects like walls, windows/doors, etc and allowing the user to attach or tag those elements with non-graphic or 'business' data as they are placed, or after they are placed.This has been happening for decades. According to BIM canon, the generic objects are then progressively replaced by 'real world' products by the contractor or their subbies downstream. This is built into BIM protocols and the 'Model Progression Schedule'.

The problem is that this now becoming a big source of problems, resulting in questions and repeated efforts to define LOD,,, then LOIN, version control etc etc. Not saying that this will go away but replacing generic objects by real world procurable products is a laborious and error-prone task. This has resulted in increased use of manufacturer's BIM object libraries from the get go, in spite of the heavier models. Especially on small, run-of-the-mill jobs. Finding out that those 'custom' door sizes or piping bends or connections have to be modified by even a small amount before they are usable is a big money waster.

Some portals that serve up manufacturers BIM content have started to provide tools to search and filter for real-world products based on the user's generic object inputs, differentiating between 'custom' and 'product catalog' objects. As usual, no such support for apps like OBD etc which do not have 'big' market share.

OTOH, verticals like TriCADms already provide enhanced Place Cell, manager tools to allow the user to look at the attributes of the Cell not just its name when placing the Cell. This is very different to the old Cell as a symbol to be placed mentality that most CAD users are used to. Even at platform level, there is slow but growing realisation realisation that the user needs to access a lot more info when placing a Cell.

So, I think its time to re-think about the way OBD's Place Object tools work.

Instead of allowing (encouraging, even) the user to place potentially unrealistic or unavailable objects or attributes into the model, it would be good to build in some lookup functionality into the tools. Expressions?

1. When the user inputs a desired attribute into the Place Object panel, there should be some code to scan the Cells in path for the compliant Cells / products. Maybe ComponentCenter (which includes BIMStore) or NBS Chorus can help here. The new AutoUpdate Parametric Cell tool already scans the Cell libraries. So you could use the same scanning tool and cache?

2. The top 'Cell' panel, drop down would only list those qualifiying Cells.

3. If there are no qualifiying Cells or products, the inputted attribute would be highlighted in amber for example. NB: there will be multiple attributes. And some performance attributes will also be restricted to the size or another characteristic of the object.

4. When the user modifies a particular attribute post-placement, the same algo re-runs and gives the user the option to replace the object with a compliant or more compliant product.

5. ??

Yes, I would say just as costly and important as BIM poster child work flow clash detection. maybe even more important as it is harder to spot these kinds of problems. Clash detection is pretty passe these days, any ways