Recommendations to others considering DriveWorks:
My first and foremost recommendation for a company evaluating DriveWorks is to audit your own process. One cannot automate a product/process that you do not understand. Check around with your sales or engineering teams, make sure that you understand and document the rules that govern these processes.
Equally important is to document the cost of your existing system. Document how much time your engineers spend to create custom CAD/Drawings/data entry (or, if implementing with your sales/distributor team, how much time is spent by sales or customer care to manage incoming sales details). Keep documenting this after you've implemented DriveWorks, and you will have a detailed record of how much money you've saved from automating your processes. This can go a long way towards pleasing Company Leadership as they evaluate the return on investment of the resources and capital that goes into an implementation. Review collected by and hosted on G2.com.
What problems is DriveWorks solving and how is that benefiting you?
Ostensibly, you buy DriveWorks because you want to automate the creation of new documents (such as SOLIDWORKS CAD drawings), although you can further automate a host of other output document formats (Word, Excel, exports to SQL or other database engines).
DriveWorks helps you document all of the rules that it takes to go from "order input form" to "custom configured output".
However, there is a second problem you are solving with DriveWorks: In order to implement DriveWorks into your company system, you need to audit, document and make repeatable all of the little rules and logic that govern your process. Making your processes DOCUMENTED and REPEATABLE is a major asset to your organization.
The most recent DriveWorks implementation that I did was at a company that did well to track how much time went into their process for creating custom drawings. We also tracked the overhead that went into DriveWorks implementation (capital resources for software, my burden rate for time spent on the project). The payback period was under a year, and we saw a decrease of over 50% of our Engineering team's time spent on drawing creation. The return on investment with DriveWorks is very, very real. Review collected by and hosted on G2.com.