Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

DriveWorks World 2016 - 13 lessons in 12 years

1,393 views

Published on

Presented by Paul Gimbel

Published in: Technology
  • Be the first to comment

  • Be the first to like this

DriveWorks World 2016 - 13 lessons in 12 years

  1. 1. A Bakers' Dozen of Lessons Learned over a Dozen Years Implementing DriveWorks for Fun and Profit (Thatis,I Have Fun So Our Clients CanProfit)
  2. 2. Paul Gimbel, DWCP, CSWP Business Process Sherpa • 12 years DriveWorks experience • 21 years SOLIDWORKS experience • yadda yadda yadda, I’ve been doing this for a long time, I know what I’m doing Slide 1 of 209 A services organization providing Implementation, Support and Training for DriveWorks, PLM, SharePoint, and more!
  3. 3. Introducing: The Sherpa
  4. 4. #1: Process “It’s All About The Process.” - Sherpaism #1
  5. 5. Flexible Process, Flexible Tool FLEXIBLE PROCESS RIGID PROCESS FLEXIBLE TOOL MUTUAL ADAPTATION REPLICATION RIGID TOOL TECHNICAL IMPLEMENTATION NON- IMPLEMENTATION From “The Line Manager and Systems-Induced Organizational Change” by Eliot Levinson, Ph.D.,
  6. 6. Flexible Tool, Flexible Process
  7. 7. #2: Plan and Plan For The Unplanned "If you fail to plan, then you should plan to fail.” - Not a Sherpaism, but I’ll steal it anyway
  8. 8. #3: Start  End  Middle “There are three components to every DriveWorks implementation: Capturing the complete, accurate, manufacturable information, outputting what information your customers need, in the right format for them, and connecting the two with your design intent.” - Sherpaism #9
  9. 9. #3: Start  End  Middle
  10. 10. #4: Don’t Panic “100% Design automation is generally unachievable.“ - Sherpaism #2
  11. 11. Simple Drawings are Happy Drawings
  12. 12. #5: Let DriveWorks Do The Work “I don't care how much work is involved, as long as I am not the one that has to do it over and over.” - Sherpaism #5
  13. 13. Added Reference Geometry and Sketches For Drawing Stability
  14. 14. #6: Your Users Determine Your Success “The biggest indicator of success in any technical implementation is user acceptance.” – Sherpaism #7
  15. 15. Customer-Focused UX Developed In Collaboration with Cadineer
  16. 16. #7: Sure, SOLIDWORKS is Cool, But It’s Not Everything “You can’t save yourself into being a millionaire. If you want to make more money, you need to bring in more money.” – Sherpaism #8
  17. 17. There’s More To Life Than SOLIDWORKS…Really “SOLIDWORKS is just another output type.” – Sherpaism #17
  18. 18. #285/38: Learn Improper Fractions Least Common Denominator 285 19 * 15 15 1 38 19 * 2 2 2 = = = = ___ ______ __ __=7
  19. 19. #8: Brute Force Can Be OK “It’s a one-time effort. Suck it up, buttercup.” - Sherpaism #12
  20. 20. #9: Get Something In Place Quickly “Let’s get DriveWorks in place and paying for itself and for the development of our next phase.” - Sherpaism #19
  21. 21. Small Project, Big Results
  22. 22. #10: ETO Mentality
  23. 23. #11: CTO
  24. 24. Can We Ship Today?
  25. 25. #12: Yes, We Know You Can, But Should You? “Given enough time and money, DriveWorks can do anything.” - Sherpaism #13 …But just because it can, that doesn't mean that it should.
  26. 26. Hey, Look What I Can Do With DriveWorks!
  27. 27. #13: Standards Can Be Good Select your motor brand:
  28. 28. Bonus Lesson (#14)
  29. 29. Final Lesson “Know when to shut up.” - Sherpaism #11 …and that would be right now.
  30. 30. Paul Gimbel, DWCP, CSWP Business Process Sherpa Razorleaf Corporation paul.gimbel@razorleaf.com www.razorleaf.com @TheProcesSherpa (Leave out the 3rd S, that’s for “Savings!”) Proud sponsor of DriveWorks World 2016!!
  31. 31. Sherpaisms • 1. It’s all about the process. • 2. 100% Design automation is generally unachievable. • 3. Automating and inherently flawed process just makes more of the same crap faster. • 5. I don't care how much work is involved, as long as I am not the one that has to do it over and over. • 7. The biggest indicator of success in any technical implementation is user acceptance. • 8. You can’t save yourself into being a millionaire. If you want to make more money, you need to bring in more money. • 9. There are three components to every DriveWorks implementation: Capturing the complete, accurate, manufacturable information, outputting what information your customers need, in the right format for them, and connecting the two with your design intent. • 11. Know when to shut up. • 12. It’s a one-time effort. Suck it up, buttercup. • 13. Given enough time and money, DriveWorks can do anything. • 17. SOLIDWORKS is just another output type • 19. Let’s get DriveWorks in place and paying for itself and for the development of our next phase. • 21. That would be a colossally bad idea. • xx. If you fail to plan, then you should plan to fail.

×