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.
There were four major areas of focus for DriveWorks 17: Scalability, Deployment, 3D and the Web.
Scalability in DriveWorks 17 was driven by a massive project between DriveWorks and Gillette. The Razor Maker project (https://razor-maker.com/) is a full featured DriveWorks web configurator that allows you to design and customize your own Gillette razor handle which will be automatically 3D printed and shipped to you. Naturally, a product like this is going to be immensely popular, requiring a significant infrastructure to support the massive demands. To this end, DriveWorks 17 introduces a lot of technical improvements to load balancing DriveWorks components and supporting the use of off-premises services like Amazon Web Services, Microsoft Azure, and Google Cloud.
All techno-babble aside, one of the most impactful improvements lies in changes to the licensing for DriveWorks Live. New technology allows DriveWorks Live licenses to be pooled across multiple servers. Licenses can be added without bringing any components offline. And most impressive, new OnDemand licenses allow you to handle overflow conditions without any users being rejected due to insufficient licenses. Signing an agreement with DriveWorks will allow access to licenses beyond those purchased in your DriveWorks Live user packs. Through Flex technology, DriveWorks will monitor your peak usage, spread that out over the month, and charge you a nominal fee that amounts to somewhere in the area of $1/day/user. This will allow you to monitor your DriveWorks Live usage and add licenses intelligently as your business grows.
DriveWorks 17 really addresses the needs of developing and growing your DriveWorks implementation by recognizing the need to deploy separate development, test and production environments. Improvements to DriveWorks tasks, like Copy Group, and access to these tasks through Specification Tasks allow you to automate the backup and deployment of your implementation.
DriveWorks 3D has once again taken more steps towards fully immersive, realistic experiences. New support for bump maps allows not only visual texture, but a truly realistic surface representation that takes the experience from looking like animation to looking like video. To boost visualization of systems, Drive3D technology will now allow you to turn components transparent so the user can see inside or through parts to see important details inside. But what can take your models to the next level is the new DriveWorks support for device motion tracking. With the ability to add camera entities to Drive3D models, truly immersive, virtual reality experiences are pretty much a reality in DriveWorks 17.
The release of DriveWorks 17 SP0, along with its ever popular power packs like the Specification Power Pack and SOLIDWORKS Power Pack, will be here before you know it. So watch the DriveWorks community and your DriveWorks Today screen for notifications. As always, if you have questions, we have answers (if not, we might just make them up). Feel free to drop your questions, comments and other choice words below.