100% design automation is generally unachievable. You’ve heard me say it before and I’ll say it again. 100% design automation is generally unachievable. And it is not the fault of the tools, it’s just the nature of process and automation. There will always be a balancing act between investment in time, money and effort with the value of business results. This fact can have some very significant and, to some, unsettling implications.
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.
The “service” in software service packs typically means the same as servicing your vehicle, some repairs, some maintenance, a wash and a vacuuming of the interior.
We’ve heard the questions that are on your mind, and so has DriveWorks.
Understanding how DriveWorks automation helps bring in new business and reduces the load on your engineering team has never been a challenge. But occasionally, there’s a bit of confusion about the components of a DriveWorks implementation.
The quandary often arises concerning managing the data that DriveWorks needs. With the QueryData function, we can access SQL databases and other ODBC sources. This is typically the route that people take when they decide that others outside of the DriveWorks administrators need to manage this type of information.
A long time ago, in an automation far, far away… It is a period of engineering calculations under the flag of Microsoft Excel. Microsoft Excel has enjoyed many years of use and continues to be a weapon of choice for automators and engineers alike.
SolidWorks assembly mates are a powerful 3D design capability, but they are often take for granted. Designers expect them to work every time, all the time, even when mating information isn’t 100% clear to the software. If you’re using SolidWorks assembly mates in a design automation scenario, and you’re experiencing some frustration with SolidWorks’ behavior, […]
Every software is bound to have its idiosyncrasies, and SolidWorks is no exception. One that we have experienced recently involves working with drawings that have dangling dimensions. DriveWorks automations will frequently leave unneeded dimensions dangling on a drawing, and that’s not a problem (they’re unnecessary anyway, right?). But when they are invisible yet still selectable, […]
DriveWorks can push SolidWorks, Microsoft Word, and Microsoft Excel to create Adobe Portable Document Format (PDF) files from drawings, models, documents, and spreadsheets.
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.