Working in a single-model environment, something that is missing is non-graphical objects (Objects in a Object Oriented Programming sense), one of which would be Specification information.
Sure, we can create parameters to represent this, but is fragmented.
If there was a Specification Class, we could create groups of information, and then attach that to other Revit objects, the ability (preferably) to be able to attach more than one Specification object at a time.
This could be extended by users being able to create their own parameters for it.
Specification class would have default parameters, such as:
This could be extended, if required, with clauses to address other typical specification clauses like manufacturer, execution, and so on.
This could be linked with by spec writing software (like NBS Chorus which needs an Object to link with), and that could itself add clauses as required. The clauses could also then be scheduled out.
So, in practice, instead of a Room object having text-only fields for finishes, Specification Object parameters could be used, that could then be scheduled out, with all the data attached to them.
As the data is an object, this could be developed further as a project progresses, to include information about installation, maintenance, and so on.
Again, yes we can do this with Parameters, but it seems very fragmented, surely there has to be a better way...
