SolidWorks

Home/Posts/SolidWorks

Better, Faster, Stronger: DriveWorks Performance Tips

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 17 Revealed

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.

Integration Demo: SOLIDWORKS to Aras Innovator to SAP

Integration is one of the key areas that can increase the total value of your business systems. Integrations between CAD, PLM, and ERP are a great example of this. Each of these systems requires the data to support its own business processes. And of course, each system requires that the data be formatted to the system’s specifications so that the system can consume it. Without integration, businesses are left with using people to populate downstream business systems which can become a source of non-value-added cost and discrepancies between the systems.

The Most Misunderstood Concept in DriveWorks Automation

A large number of questions that you see in the DriveWorks forums (you do follow those, right?) all have to do with the interaction between DriveWorks and SOLIDWORKS. Most often, that question involves a DriveWorks user asking how to get the results from a SOLIDWORKS model generation to drive a DriveWorks specification. Whether that means using the mass properties that SOLIDWORKS calculates, a reference dimension from a sketch, Bill of Materials information, or an interference check, people want DriveWorks to run that model while the user is filling in their forms. 

3DEXPERIENCE: Persistent Login Popup Fix

When deploying the SOLIDWORKS Connector with the 3DEXPERIENCE Platform there is a troublesome behavior when a user is actively using Workspace Folders. The Platform persistently presents a login window if the user computer is not connected to the network or the Platform.