Originally Posted by
Steve_Stafford
Well Innovaya focuses on phase and assembly codes (uniformat) so it's biggest battle is with content that doesn't have assembly codes assigned. The other issue is that they recommend that you use phases like "layers" or "containers" to organize the top level of the data and that hoses the use of phases for graphical representation...or at least can impede that use (from the Revit using Architect's standpoint).
Complex elements are not granular enough to dissect in external applications because Revit treats them as assemblies (walls are a good example where the contractor may want multiple walls but the architect uses one wall with layers) but the other software would like bits and pieces. What is good for documents may actually be not so good for field work. If we built the models like the contractor wants then the "drawings" would be secondary and their "looks" might just be irrelevant. If this is really heading where we "want" it to...drawings will be secondary...perhaps even irrelevant. Heresy today...but we will see?