Description
This class will be all about defining a common way to exchange data between different authoring tools. In the era of big data and with the increased complexity of projects, how can we ensure that the transfer of design data is consistent and free from data loss? There have been many attempts to come up with a common strategy for the industry. The reality is that usually none of them fit what we’re looking for. Let’s have a look together at what’s already available (Speckle, BHoM, and so on). Maybe what you need already exists. We can come up with some semantic strategy to define the language that works for your company (or that has worked for AECOM). We’ll finish up with some best practice on how to create add-ins, Dynamo custom nodes, and repositories to support the data exchange—as well as how to use the power of Autodesk Design Automation to create data-driven models in a click!
Key Learnings
- Learn the value of speaking the same design language.
- Learn about maximizing what the market already offers and learn how to extend it.
- Learn best practices in creating a new language that suits your company.
- Learn how to develop custom tools to support your data exchange.
Tags
Product | |
Topics |
People who like this class also liked
