As-builts... Problematic as they are, we need them. But do we really need as-built models? Is there a better way to represent as-built conditions? Some firms are starting to put Reality Computing to work as an option.
In his presentation at SPAR International 2014, Magnus Rönnäng of Volvo Car Group described how using 3D CAD for the virtual modeling of their plants has been futile. “It has been much too time consuming to create the model, and by the time the model is ready, the plant itself has been altered many times,” explains Rönnäng. “The point cloud is our digital plant.” He advises us to scan what we have and model what is new. Good advice and a good fit for Reality Computing.
Today we start a new series of posts about how Reality Computing combined with geometric modeling is proving to be a better way to document as-built conditions. We'll explore the importance of as-builts, the drawbacks of using design solutions to create as-built models from scratch, and the use of heterogeneous data sets of captured reality data and modeled objects for new or critical existing elements to document as-built conditions. We’ll also profile two companies using Reality Computing for as-builts: Stiles Corporation and McCarthy Building Companies, Inc.
Volvo Cars no longer tries to maintain as-built geometrical models of the manual assembly cells for their plants because the models are expensive to develop, immediately out of date, and lose the rich detail captured with the reality data. Instead, they scan existing assembly cells and the resulting point cloud is their digital plant.
Image courtesy of Volvo Car Group