Ask people in the DriveWorks community about what was introduced in DriveWorks 11 and Triggered Actions will come up frequently. What may not come up is what DriveWorks Triggered Actions really are, how Triggered Actions are used, and why they’re worth digging into. Well it is time to clear this up once and for all.
On February 16, 2012 at the DriveWorks World conference in San Diego, California, the latest version of the DriveWorks Design Automation and Sales Configuration software was released to the world. Along with significant performance increases, DriveWorks 9 introduced a couple of new goodies that most DriveWorks administrators and architects will appreciate. Continue Reading
There are two extremes when driving components in design automation systems: on one end of the spectrum, you can allow users to only select pre-defined components (Configure-to-Order) and on the other end of the spectrum, you can let users create their own parts by driving the dimensions and features of the parts with infinite flexibility (Engineer-to-Order). Which of these models is TactonWorks following with variants? Are we just selecting variants, or are we customizing them, or are we doing both? Continue Reading
One of the biggest complaints about design automation is performance. Companies are outraged that the tool runs for a whole hour to complete a process that used to take four to six weeks. Despite the obvious lack of perspective here, it is a design automation best practice to consider performance and optimize rules wherever possible. Several sources of performance degradation can be avoided with a little foresight. Continue Reading
Design Automation is very powerful when creating unique “same as, but” models for new jobs. But in many cases, people are doing configure-to-order (CTO) just as much as they are doing engineer-to-order (ETO). Configure-to-order means utilizing standard components and using the automation to determine the logic for which component, or which size of a component, to put in an assembly. Configuring an automated design sounds simpler, and in many ways it is, but there are a few things to note and some design automation best practices to follow when planning to swap models in SolidWorks. Continue Reading
When creating your SolidWorks assembly master models and preparing them for automation, a lot of decisions need to be made in developing the best mating schemes. One important consideration in this development is the creation of the relations between components. The design intent in your models can be established by parameters that are driven by your automation tool, or by relations within SolidWorks. Let’s dig into this a bit deeper to uncover some an important design automation best practice related to SolidWorks mating. Continue Reading
DriveWorks recently published service packs for its DriveWorks 6 and DriveWorks 7 platforms, one for each major version (DW6 SP8 and DW7 SP4). With the release of these service packs, the transition from DriveWorks 6 to DriveWorks 7 as the platform-of-focus becomes increasingly clear. There are no major enhancements in DriveWorks 6 Service Pack 8 as DriveWorks spends “the vast majority of [their] development effort” on DriveWorks 7. Continue Reading