Upload
razorleaf-corporation
View
505
Download
0
Embed Size (px)
Citation preview
A Bakers' Dozen of Lessons Learned over a Dozen Years
Implementing DriveWorks for Fun and Profit(That is, I Have Fun So Our Clients Can Profit)
Paul Gimbel, DWCP, CSWPBusiness 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 organizationproviding Implementation, Support and Training
for DriveWorks, PLM, SharePoint, and more!
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.,
#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
#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
#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
#6: Your Users Determine Your Success
“The biggest indicator of success in any technical implementation
is user acceptance.” – Sherpaism #7
#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
There’s More To Life Than SOLIDWORKS…Really
“SOLIDWORKS is just another output type.”
– Sherpaism #17
#285/38: Learn Improper Fractions
Least Common Denominator
285 19 * 15 15 1 38 19 * 2 2 2
= = = =
___ ______ __ __=7
#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
#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.
Paul Gimbel, DWCP, CSWPBusiness Process SherpaRazorleaf [email protected]
@TheProcesSherpa (Leave out the 3rd S, that’s for “Savings!”)
Proud sponsor of DriveWorks World 2016!!
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.