Deploying DriveWorks Throughout the Organization

Copyright © 2015 Razorleaf Corporation www.razorleaf.com

Deploying DriveWorks

Throughout The OrganizationTools, Techniques and Real Life Examples to Help You Bring

DriveWorks Beyond Your Engineering Group to Realize More Benefits and More

Return on Your Design Automation Investment Using Upstream and Downstream Process Groups From Initiating Event to Final Delivery Leveraging Standard DriveWorks Functionality

to Expand the Reach of Input User Experiences and Output Documents and Information Beyond SolidWorks

Models and Drawings to Include Better Formatted Information for Downstream Internal and External Consumers As

Well As Secondary Information for Detailed Engineering Design and the Generation of Further Production and Manufacturing Outputs

From Hard Copy Machine-Side Documents To Computer-Aided Manufacturing Files To Be Sent Directly To The Machines Are You Still Reading This Don’t You Have Something Better To Do Like Talking To Other DriveWorks Users To Find Out How They Are Using DriveWorks And Making New Contacts for Future Communications

Copyright © 2015 Razorleaf Corporation www.razorleaf.comMarch 19, 2015 Chicago, USA

Welcome to

DriveWorks World 2015 – March 16-20, 2015 – Chicago, USA(even though it’s already Thursday and the conference ends tomorrow)

• Slide Deck will be made available shortly after the conference

▫ www.razorleaf.com

• Slides do not contain full content – see the presenter’s notes

• Yes, the notes contain the … um …”humor”

Do I Really Need To Pay Attention?


• Razorleaf: Getting you the most from your technology

▫ PLM, Design Automation, SharePoint, PDM/TDM, CATIA, and more!

▫ Implementation Services, Training, Project Support, Process/Tool Analysis

▫ Certified DriveWorks Services Partner

▫ DriveWorks and SolidWorks API automation extensions

▫ DriveWorks Integrations with outside systems

• Paul Gimbel: Business Process Sherpa (aka TheSherpa)

▫ Certified DriveWorks Professional (User since DriveWorks 5)

▫ Certified SolidWorks Professional, (AE, Trainer, Services since SW95)

▫ “We do the difficult every day. The impossible just takes a little longer.” – Art. E. Berg, sort of

Who is this guy? Razorleaf?


• You mean there’s more than Engineering? Like what?

• Why leave the safe sanctuary of Engineering

• How to fail at DriveWorks (and how not to)

• Wow, I never though DriveWorks could do that

• You’ve got questions? We’ve got answers. (or we’ll just make them up)

What to Expect When You’re Expectant


DriveWorks: Saving Engineers Since 2001

You don’t have

to jump, Phil.

We have


“It’s All About The Process” – The Sherpa

Hmmm, this is from that

2005 ISO audit. That

should be good enough.


Who should get DriveWorks benefits this year?


Which Is The Best Drawing?


We Don’t Communicate Clearly? (Imagine that)


The Law of Averages

<

<

We’ve got a 529 in progress, attempt to violate the law

of averages…


DriveWorks In the Sales Department


DriveWorks In Marketing


Advertising In DriveWorks


Data Doggy Bags

WHERE USED SearchesHave We Done This Before?

Have We Done This Before?


Who Needs Tables? … Your Users Do.


Do You Want Your Users Using This?


The Care and Feeding of Your New Pet

Macro

Buttons

Upload

Control

Data Table

Control


The Best Kept Secret

Approval Loop

Analysis Loop


Or you can avoid these things and NOT fail, if you really want to. It’s your call.

*Things that we, at Razorleaf, have seen others

do… certainly not the things that we do.


I Know How It Works,

I Don’t Need To Talk To Them


Guaranteed Failure

NO!

I WON’T use your little

engineering techno-

thingamabob. I’ve got a

perfectly good pencil and

lots of Post-It notes.

Hmmph. Nobody’s

going to tell ME how

to do MY job!


Just Try Anything, Forget Use Cases

Is yours

working?

I don’t know. How

can you tell?


Characteristics of the worst User eXperiences• Confusing• Frustrating• Unclear expectations/requirements• Complex/Technical• Vague• Inconsistent• Dragging on• Slow (performance)

You’re Ruining My Engineering Tool!


Of Course You Know That…Right?


The Seven Phases of Testing

KEEPCALM

AND

CONTINUETESTING

Error 404: Image not found

1. Build test cases

2. Document test cases and results

3. Test as you develop

4. Test as each feature is added

5. User eXperience testing

6. Small user pilot testing

7. Production environment testing


• Assume you know how things work

• Develop the process and outputs on your own

• Tell people a better way to work

• Planning is for losers, you’ll know it works when it’s done

• Provide a User eXperience of pain and misery

• Ask your users for what you want to know

• Skip the testing, we never make mistakes

• Throw some random numbers in at the end to see if it works

Sure To Fail List


Got questions?

I’ve got answers! (or I’ll just make them up)

www.razorleaf.com

[email protected]

@TheProcesSherpa (only two S’s for efficiency)

(yes, you may leave to go to the bathroom now)

Wow! You Stayed Awake for Most Of It

mailto:[email protected]

Software

Deploying DriveWorks Throughout the Organization