The two biggest themes in DriveWorks 16 (DW16) seem to be 3D Interaction and CPQ. While DriveWorks has always been quite capable of serving all of the needs of the CPQ community, DriveWorks 15 introduced a CPQ “template” (such an inadequate term for as much as it does).
Well, it’s almost that time. The newest version of DriveWorks is in development now. Actually, the newest version is always in development, I suppose. But now, DriveWorks 16 is getting close to its release date. So, what new magic functionality is going to premiere in DriveWorks 16? That’s one big reason why we all go […]
OK, maybe “happy” isn’t really a term one would use when working with the SOLIDWORKS API. I’m not saying that the SOLIDWORKS API is bad, it just…well, it can be challenging at times. But if you insist that you NEED to write custom code (I find it rare that I need to if I use DriveWorks to its full potential), then you certainly can use DriveWorks and the SOLIDWORKS API together.
One of the greatest assets that Razorleaf can claim is a breadth of knowledge across industries and technologies. Recently, I had the opportunity to jump into something really fun and exciting, where you enter product details into a form and magically, models and drawings appear to suit your use case. I’m talking about DriveWorks design automation software. More importantly, I had the opportunity to work with industry expert, Paul Gimbel and learn some things you can only learn by working on real projects.
Tabular data is one of the foundations of the DriveWorks design rule. Rules generally fall into one of two categories: Calculations or Logic, or Lookups. Three. DriveWorks rules generally fall into one of THREE categories: Calculations, Logic or Lookups. The perennial favorites VLookup() and HLookup() join forces with DWVLookup() to allow DriveWorks architects the ability to store tables of static data, like material properties, available stock parts, and so on, and pull values from data for calculations or decisions.
It’s no secret that here at Razorleaf, we do a lot of DriveWorks implementations. And every implementation is always the start of something larger for our clients. There is no such thing as a completed automation project because you will always want to add new options, new products, new outputs, just adding more and more value. With every implementation being totally different, how can we help our clients to extend their implementations moving forward? Easy, we use intelligent, generic, reusable rules.
DriveWorks provides excellent functionality for collecting information and performing the calculations, lookups and logic that our designs require. There are some situations, however, where tools outside of DriveWorks are still employed.
With the addition of Generation Tasks, DriveWorks has made the move from being the master model push system to one of the only true DriveWorkshybrid design automation systems on the market. Generative modeling, which is the ability to add new SOLIDWORKS features without predefining them in the master model, has been the top request of DriveWorks implementers for years. Let’s take a look at the tools that DriveWorks has provided for the support of generative modeling.
There are a lot of big, game changing new features in DriveWorks 15. And you will probably see posts about them all over the web. Well, you’ll see them here. But first, we wanted to show off a small feature by release notes standards that we think will be huge and game changing in its […]
They came from all over the world and descended upon Atlanta, USA for the annual DriveWorks World Conference. Newer users came for training, others came to earn their DriveWorks Certified Professional (DWCP) certification, and still others came to pick a multitude of brains for the best practices available anywhere. Basic and advanced technical tracks provided […]