AnsweredAssumed Answered

Driveworks vs Design Tables.

Question asked by Aulio Vasquez on Jul 3, 2015
Latest reply on Jul 23, 2015 by David Mandl
  • Comment • 2

I've been working on a project with Driveworks Solo Trial version, we are doing fine, actually it meets all of our requeriments. Our VAR, however, insist in the use of design tables (evidently is way cheaper).

 

I agree, driveworks is just a fancy way to use design tables with some incredibles add-ins, but I have some doubts on advantages and disadvantages on both:

 

Before answers, consider that none of our design team or engineers have programming skills.

1) Is there a way that DT or macros drives new generations and locations as DW does? I have "Same but different" models but I need to store every new generated piece in the "Customer folder"

2) Can DT at least drive file name?

3) If I drive in DW the file name: MasterModel.sldasm > GeneratedModel.sldasm, then I generate a new model with the same name (GeneratedModel, same location, different specifications) Does it changes the previous model or it just opens it again?

 

Thanks you guys

Regards.

David Mandl
David Mandl Aug 24, 2015 9:03 AM
Correct Answer

Okay, I'll be upfront with my bias here (I work for a VAR as a DriveWorks specialist Applications Engineer... so I do demos, training, implementations and so forth of DriveWorks for our customers/prospects), but I'll say this and answer your questions:

 

I'll try to ignore your comment on your VAR saying to shy away from DriveWorks and so should you.  I don't know if this is an appropriate place for me to get into my usual pre-sales spiel, but I will note that DriveWorks (even at the Solo level) offers MANY advantages over design tables and as such has plenty of opportunity for ROI that would render moot any of their comments about cost.  I can get into some details on those advantages (a) if you ask, and (b) when I have a little more time on my hands.

 

And "programming skills" aren't something required for DriveWorks.  I often tell clients that DriveWorks requires skills on par with a mid-level Excel user, and I've yet to be corrected by anyone in that statement, because:

  • It's true.  Quite literally, the vast majority of the rules and syntax used in DriveWorks is just a carbon copy of corresponding rules and syntax in Excel formulae.
  • DriveWorks was originally developed as a way to supplement design tables with SOLIDWORKS API, and it's grown from there.
  • Most of your users won't be doing any rule-writing, they'll just be filling out forms and generating models anyway.
  • This isn't Autodesk.

 

Now, for your questions...

  1. Not with Design Tables.  API/Macros in SOLIDWORKS make all sorts of things possible, but it's up to you to program, debug and maintain them.  If your engineers don't have that skill set, I'd call that moot point.
  2. Not without API, that I've seen.
  3. Yes, in fact that's a VERY important part of the way DriveWorks functions.  One of our customers has been using DW for quite some time, and they've already generated most combinations and permutations of their product.  So much so, in fact, that it's rare that DriveWorks actually produces a new model when they run a new specification.
  4. Similar to 1 & 2... no.  At least not without API.  The closest you can get without adding on code is to do the pack and go yourself and then modify the tables accordingly.
See the reply in context
No one else had this question

Outcomes