R*vit is well-known for being data-centric from the ground up. So, I am surprised to see how difficult it is to attach and manage BIM data in R*vit.
1. R*vit has some peculiar restrictions on its parameter types. This results in Shared Parameters being the go-to format for the bulk of the BIM info. Including title block info.
The problem here is that the SPs are stored in an external text file. Not great. This has resulted in the need to use third party addons like Ideate, RF, Exitech,CTC etc to generate and manage this info. Even then the txt file is vulnerable. GUID exposed. Open to duplication. At least OBD stores the data in the file.
Other drawbacks:
- I understand that a lot users also end up exporting the non-schedule-able parameters to the SP file just to be able to schedule them.
- Restricting parameters to certain types of elements. Read only problems
- Family component variations / data stored in component rfa. Datagroup Catalog Item info mirrored.
- ??
OBD's Definitions Editor also allows you to build up parameter/property sets which is a big time saver. OOTB in R*vit: One-by-one adding is pretty slow.
The text / xml-based format also allows for find/replace, move / copy mods for the more techie Notepad++ savvy users. Maybe an Edit-in-Excel tool would be more accesible. Tried editing the Architectural_parts.xml file in Excel which didn't allow saving it back as an xml.
OTOH, Revit SPs advantages have over OBD'd DGS include
- Formulas
- Lookup tables?
- Association?
- Typed parameters
Mstn CE Item Types functiomalitythat would be good to have in DGS...