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.
The following video illustrates how Razorleaf’s integration platform Clover enables a fluid PLM integration between 3DEXPERIENCE and Aras Innovator. In many environments where there are multiple PLM or CAD systems, it becomes necessary to pass critical data between the two systems to enable end users to do their job better and access the most current, accurate data. Clover can enable single or bi-directional exchange of data depending on the use case, regardless of the applications being used (ERP, CRM, PLM, CAD, PDM, and more).
Earlier in the quarter, Razorleaf Government Solutions represented by Jonathan Scott participated in a presentation at the NIST MBE Summit in April 2018 in Gaithersburg, Maryland. Jonathan, along with co-presenters from Anark and ITI, shared details on the outcome of the 3D Data Exchange Project with NAVAIR’s PMA 261 program.
Those of you who are new to DriveWorks or new to the use of Specification Macros (“spec macros” as Glen Smith is keen to tell us all the cool kids call them) will not notice anything out of the ordinary when you first see the spec macros form in DriveWorks 16. I mean, you’re seeing it for the first time. But those seasoned veterans who have spent time pulling tasks from the toolbox are bound to be taken aback when seeing spec tasks in DriveWorks 16.
Razorleaf supports and sells a suite of software developed by Design Rule called 3dxtools. In this blog, the 3dxdesigner utility will be discussed and how it can be used to manage configuration changes between 3DEXPERIENCE environments.
Razorleaf had the opportunity to participate in a Dassault event called POWER’BY Days. During the event, we learned that POWER’BY is a strategy and that the functionality is real and available both on-premise and on-cloud.
Before we can start troubleshooting anything, we need to first figure out what is wrong. Now I mean this in the most general way. Are we having a problem where the drawing is incorrect? Are we having a problem even getting a drawing to generate when we release? Are we even getting to the point where we can release? Is our computer even able to startup? If the problem is the last one, try turning it off and back on again.
Today’s quick tip is about modifying the 3DEXPERIENCE login text label. In a previous post, I had shown how you could modify the image file, so it is easy to identify what system a user is about to log into. However, some customers may prefer text only, images only, or both. This example shows how easy 3DEXPERIENCE can be tailored to suit your needs.
The two biggest themes in DriveWorks 16 (DW16) seem to be 3D Interaction and CPQ. While DriveWorks has always been quite capable of serving all of the needs of the CPQ community, DriveWorks 15 introduced a CPQ “template” (such an inadequate term for as much as it does).
April 17, 2018 — STOW, OHIO – In a move that reflects manufacturers’ growing demands for PLM tools that help them better manage the increasingly digitized industrial landscape, one of the leading American providers of PLM implementation services has established its first division outside the U.S.