Content Sponsored by SKUR
Full disclosure: SKUR has paid for editorial consideration, but SPAR 3D has retained final discretion over the final content of this article.
SKUR’s cloud-based software solution performs a complex task that seems simple: visualizing variance.
You use it by plugging in two data files, for instance a design model for a large-scale environment and a 3D scan of that same environment as it was actually built. The software processes those data sets using proprietary algorithms and reports on any differences it finds.
For customers in the “AECO” space (architecture, engineering, construction, and *operator*), SKUR sheds light on the differences between what was designed and what was actually built. Or the differences between the scan they took last month and the scan they took this month. And so on.
But seeing the differences is just the start.
Actionable Information for Everyone
As SKUR’s VP of product development Nic Arnold said, “I see the variances as a seed—a central point from which you can derive many other insights.”
For example, changes detected during the construction process can be used to perform quality control. Did a worker put that beam in the wrong place? By comparing the as-built to the design model, SKUR can provide that insight. It enables you to catch the problem before building continues, saving you costly rework in the process.
“When you identify these variances, what you can do is almost endless,” Arnold says. “You can use it for risk mitigation, for detecting challenges, for detecting progress, because it’s all about finding out the difference.”
And SKUR understands that those insights may look different for each project stakeholder. SKUR founder and CEO Adam Cohen explained that SKUR’s core engine is designed to feed a number of different reporting mechanisms that can be tailored for individual project roles. “There may be types of reporting mechanisms or translations of visual information into reports that are consumed by different people through the ecosystem. A project engineer may want to see the same information as the CTO, or a C-level executive wants to see, but they want it presented differently.”