Working through software changes and improvements.

Written by Marco Cecala

Created on Sunday, 02 September 2012 15:42

Things are never as easy as they seem. We have dedicated years to the production and processing of data for the 3D world. For many years it was not hard to feel complacent after you had a few years under your belt. Not to worry, all good things must come to an end.

The bar continues to be raised by the manufacturers of hardware and software. I don’t need to single out any particular manufacturer; everybody is making their stuff faster and better. The downside to this is that you need to stay on top of all these changes, often for more than one type of software.

I will use the example of the biggest player in our world, Autodesk. AutoCAD introduces a format change every 3 years, the most recent being 2013. That means you cannot open a 2013 file on the version 2012 program. Yes, Autodesk makes free viewer software that will allow you to open the file and save it back to an earlier version. That works, for the most part. You will want some functionality in the new version that gets wiped out when you save back to an earlier version. Three days after the release of 2013 we got a file in that format. Guess I needed to upgrade quicker than I thought.

I agree with the upgrade path the manufacturers follow. Everything from new commands to a total rebuild, as in the case of Trimble Business Center. The new underlying software engine is robust and is suited for the new century. Is it hard to learn again? Will I long for the old days? Yes to this and more. Until you decide to do a job from start to finish in the software, you are doing nothing but playing around. The commitment to do actual production is a great motivator for getting to know a product.

The switch from old to new needs to be planned thoughtfully; here are some tips to make the process smoother:

• Turn it on and play. By all means don’t jump right in and do a big job with new software.
• Break your learning into stages. Consider a site for instance; the three main elements are 2D lines, 3D lines and points. Take on each of these at your own pace and learn the specifics. When you get good at these pieces, you can proceed to build a site with confidence.
• Get training. Trust me, I know software. Even though I can get through a program and learn it, training shortens the time and aggravation. Online resources are a great way to work at your own pace and keep your regular production from suffering.
• Get over the words. I still get hung on this. Line, polyline, vertex, line string; it is what they call it. Don’t ever say, “Why can’t they call it a polyline instead of a line string” You are learning a new language; impress friends with the new big words.
• Don’t try to do production too quick. Get used to the product. In a perfect world do part of a job you did with your current program and compare. That’s the best way to feel comfortable.
• Stay on top of releases and provide feedback. Many commands in different software packages came about because we said we really needed it. The program gets improved when you propose changes; after all, you are the end user. Who better to help development?
• Shop wisely. You are getting improved software for one of several reasons. The old product is going away, substantial improvements make the new version completely different, or you are looking to change. Do your homework, talk to people and get a clear picture of what you will need to do to get proficient with the new program.

You are not the first to upgrade or change platforms; unfortunately guys like me have already experienced the growing pains of software advances. Take advantage of our pain and ask questions. The time you save will be worth the little effort it takes.

Read Marco's articles
Read Marco's blog