This installment of the series will look at how to get information from DriveWorks into SQL, and we will get a bit more technical and open-ended, exploring some of the more advanced tools available within Microsoft SQL Server.
Visualization can be key in helping your users understand what they are configuring and what your customers will be ordering. And while 3D is a great way to provide an unambiguous representation of a product that may not even exist yet, generating 3D content […]
Recent studies have found that when it comes to how long users are willing to wait for their interactions with a software, they’re not. There’s no way to determine what a reasonable refresh time is because you don’t have reasonable users. So all that we can do is look at the components of the DriveWorks implementation and optimize as many of the steps as we can.
DriveWorks provides a fantastic suite of tools that allows us to create user interfaces where we can capture complete, accurate, manufacturable information which can be used to generate designs and outputs. But there are cases when the front end of a configurator may already exist or our input information is coming from somewhere other than a user entering into a form.
Razorleaf has obtained exclusive information on DriveWorks 17 PreRelease only available to Razorleaf (or anyone else that attended the DriveWorks World conference in Chicago, or select individuals that attended SOLIDWORKS World, and a few others). Well it’s time to break the silence and release the 411 on DriveWorks 17.
The wonderful thing about design automation is that we can work with so many situations where we handle a large number of unknowns.
The frustrating thing about design automation is that we can work with so many situations where we handle a large number of unknowns.