Management

The Minimalist's Guide to CAD Software Upgrade Decisions

25 Jan, 2012 By: Robert Green

It's a chore you'll have to tackle sooner or later, so apply this methodology and make your evaluation as quickly as possible.


Author's Note: This is the second installment in "The Minimalist's Guide," an occasional series that shares ways to be a more efficient CAD manager. In each installment, my goal is to condense a complex process into a best practices overview document to help you save time and avoid common mistakes. I hope you'll find them useful.

It's a fact that sooner or later, an upgrade will be released for your CAD software. When that happens, you'll need to make a quick decision about whether implementing the upgrade will be worth the time, effort, training, and expense.

In this edition of the CAD Manager's Newsletter, I'll share my methodology for evaluating upgrades, which seems to work for every type of CAD software. Here goes.

Always Test the New Upgrade

Whatever else you do, you simply must put the new upgrade through some basic testing. Of course, if you have a product support subscription you will get your upgrade automatically, but if you don't, consider the following approaches:

  • Use a 30-day trial version to test
  • Get involved with beta-testing programs
  • Ask your software dealer for a limited-time loaner version.

All these methods can offer you a limited amount of time for testing. The beta version has an added advantage: You'll test new software before anyone else can!

By the way, these methods work great for exploring new software as well. So whether you're evaluating the latest upgrade to your ol' faithful program or just looking to kick the tires on an unfamiliar product, do what it takes to actually get your hands on the software.

Document the Evaluation Process

Make sure you build the following elements into your testing protocols:

Use your own data.
Don't use test data supplied with the new software. Instead, use data that you already have, or create new tests using the same types of projects you would normally design. The goal is to see how the software works with a typical cross section of data you would normally use.

Note changes.
Any differences in elements such as ribbons, toolbars, browsing interfaces, or content libraries may cause problems for your users. Sometimes an upgrade can seem like a downgrade when old familiar commands change!

Evaluate new features.
Take some time to go through the new features touted in the upgrade's documentation. Sometimes you can find a new feature that perfectly fits your needs — those are the features you're looking for!

Get a second (and third) opinion.
Once you've identified the changes, new features, and possible problems with the upgraded software, invite a few trusted users to check it out and share their impressions. If they aren't enthusiastic when the software is new, you can bet they won't be excited later on when they have to learn it.

Write it up.
Create a summary document along with your decision about whether the upgrade merits further consideration. This writeup will be the basis for continuing your upgrade process — or not.

1 2 


About the Author: Robert Green

Robert Green

Add comment

Note: Comments are moderated and will appear live after approval by the site moderator.

AutoCAD Tips!

Lynn Allen

Autodesk Technical Evangelist Lynn Allen guides you through a different AutoCAD feature in every edition of her popular "Circles and Lines" tutorial series. For even more AutoCAD how-to, check out Lynn's quick tips in the Cadalyst Video Gallery. Subscribe to Cadalyst's Tips & Tricks Tuesdays free e-newsletter and we'll notify you every time a new video tip is available. All exclusively from Cadalyst!
Follow Lynn on Twitter Follow Lynn on Twitter


Poll


Poll not yet available.



Cadalyst Magazine - Buy Now