Attempting to put together standards for our office which is planning to use VW through documentation. I've previously used VW only up through DD (only to create illustrative plans), not for documentation. I've used VW for some time now and understand the difference between classes and layers, but am just now learning about record data and creating worksheets / reports. This brings up the question - what is the benefit of having multiple classes when one can identify a material (just for example) through Record Data?
The addition of record data can create conflicting references. One object on the class "Material A" layer can have record data assigned to it as "B", or something similar.
Ex. File A
Classes - Concrete, Brick, Stone
The benefits I see here is that objects on these three classes can have defined properties at creation. Concrete is always blue, brick is always red...
Would you create a Record Format that uses "class" as a record column if you wanted a list of materials and area takeoffs?
Concrete - 100SF
Brick - 200SF
Stone - 300SF
Ex. File B
Classes - Materials
Record Data - Concrete, Brick, Stone
The benefit I see here is that there are less classes (1 vs. 3) and the application of record data, the ability to create a worksheet / report.
However, material properties (color, pattern, etc.) would have to be defined every time, making it difficult to create an office standard "look".
Is it one or the other, is there a different way or am I not understanding how Record Data relates it with classes?