Webinar
Cyril Verley, founder of CDV Systems, last week gave a presentation on his company’s Collectus software. I took in the presentation; here is what I learned.
- - -
Collectus is a Revit standards library of 36,000 imperial and metric components. As well, it is the first to integrate a BIM Execution Plan (BXP). BXPs are used by facility owners to specify modeling requirements for architects, engineers, and contractors working on the design and the construction of the new building.
You would use Collectus, from CDV Systems, to model and then enter all required room and asset data at the following levels of detail
LOD 300: Design and documentation (for architects and engineers)
LOD 400: As-built and manufacturer (for contractors)
LOD 500: Records (for operations and maintenance)
The idea is to take all the data that’s been added with Revit to the model, and then use the data to populate FM [facilities management] and GIS [geographic information systems] software. Collectus includes a CSI [construction specifications institute] classification batch translator between MasterFormat, UniFormat, and OmniClass. (To learn about these standards, start at https://www.csiresources.org/standards/uniformat.)
The reason for needing software like Collectus is due to data incompatibilities that arise during all the stages that a structure goes through, as data is handed from one party to the next. Architects, engineers contractors, interior designers deliver their models along the line, each of which might speak a different language -- this is the source of incompatible data.
For example, take a building with 500 rooms and 1,000 doors. A door family template specifies all its parameters, which can consist of hundreds of parameters for each door -- all of them initially blank. Every door symbol probably has a parameter called Door Fire Rating, and it ougjt to be mapped to data in FM and GIS using software. But when different designers name the parameter differently, such as DR FR RTG or door_fire_rating, then the data is not directly transferable; the different naming systems have to be mapped to each other.
So, BXP would pre-populate many of these fields with Collectus, and specify the names of parameters for all parties involved.
Note that all involved in the building get access to Collectus at no extra cost.
Comments