3D Scan to CAD is a service that converts your 3D scans into editable, design-ready, and professional-grade CAD files. But, how does it work? Why should you scan and then move to CAD?
Voyansi Voices Blog
Picture this scenario: You are one of the largest companies in the wood and engineering industry and you want to become more efficient by speeding up your processes. This means redefining practically all of your workflows to fit new demands. They know it's one of those jobs where there's much to be gained if done right, yet much to lose if the results do not meet expectation.
This was the scenario facing RedBuilt and they turned to Voyansi to ensure the project was a success.
We are technology enthusiasts, and we state that software is at the core of how we make BIM accessible for all. But beyond our phrases, there’s a lot of information waiting to be interpreted and told.
It’s like a watch. What we see on our wrists is the result of a series of smaller processes that make the handles move and let us know what time it is. Are you going to tell me that what lies behind the numbers and handles isn’t interesting to you?
What’s behind many of the things we do is Dynamo. But before getting specific about it, we should see the bigger picture.
I believe that humans, like plants and other animals, need time to get used to new environments. Understanding them, familiarizing themselves with their characteristics and peculiarities, is the first step. Of course, this applies to any change you face in your life: From moving to another city, to becoming a new Revit user.
Every week, new platforms emerge to help manage every aspect of the business. There never seems like the right time to hop into something new. However, this week we'll discuss the other side. Understanding where your current software ecosystem is hurting your business. These areas can be hard to detect, especially when you've been running the same systems for years. Technical debt builds up beneath the surface, and before you know it, more agile competitors are producing things at a pace that seems like magic.
Last year, at the beginning of the COVID crisis. Voyansi started experimenting with the latest version of Revit Server (2020) for smaller (>10 person) teams. Our conclusion was that it's a powerful tool and a viable alternate to BIM360, but does not offer the same overall functionality or ease of setup. Often, our work standards are dictated by our clients and end users, so BIM360 is our most commonly used collaboration tool, however there are instances when this may not make the most sense for a small number of users.
In recent years we have assimilated a lot of new ideas. Imagine yourself as a drafter in the 1950s, and how mind-blowing printing technology is today. How about a lot of the tedious calculation-based work that has been replaced with software tools: quantity take-offs, spatially organizing office space in a building, or even in creating models themselves. We work in an industry that is constantly evolving and changing. BIM, our chart and compass guiding us in the right direction.
In our last few posts, we introduced you to our ecosystem design principles and the platforms we chose. Implementation can always be more perfect, and just as we changed a lot internally in the last 5 months, the next year will hold even more surprises for us. We know you are going through similar changes, so this is of how we formed an architecture for our data ecosystem.
Think for a moment about your chest of tools as an architect, engineer, or designer. You have a variety of software systems, years of experience, and training. Experience tells you when things won't work well, like that element can't go there, it will cause a clash. If you are new to BIM, drafting in 3D, or using Dynamo, this probably sounds like a bright future, but how do you get to that level?
In my last post, we covered our rules for software selection and how we found the right pieces for our software ecosystem. Choosing the software is just the beginning, stitching them into a cohesive end to end system takes trust, effort, and time. Our teams have been hard building towards new workflows. In this post, we will cover some of our design principles around our data ecosystem. These keep us aligned in our goals and allow us to decentralized our decisions.
Monday March 2nd, 2020. Voyansi, then AEC Lab consisted of 3 project team members: two software developers and our PjM/ head of Software, Libo. Similar to countless other spinoffs, we began this voyage with the tools we had in hand when we left AEC Resource.
Last year before AEC Lab rolled into Voyansi, we wrote about applying the Pareto Principle to software problems. To summarize in case you missed it, we discussed the fact that organizations can make large impacts by solving the biggest problems first. In summation, correctly identifying your largest “stones” or issues is your challenge. Finding the stone that represents 20% of the causality but solves the 80% of your problems.