The HMS Software technical department gets calls almost every day from existing clients asking questions or for assistance in doing an upgrade. For some of these organizations, we find that upgrade practices are ad-hoc. These organizations don’t have a standard procedure for managing upgrades and are making their best effort to get to the lastest and greatest TimeControl version.
Here are a few lessons about upgrades that we have learned over the years that are common to almost all TimeControl users whether you are moving from version 6.0 to 6.1 or 4.6 to 6.1:
Back it up
You might think that everyone backs up their enterprise data but sadly that’s just not true. No matter how confident you are that your particular deployment of TimeControl will be seamless and instant, back up your data. In some cases, organizations with virtual servers can actually back up the entire TimeControl environment include the database server, the database itself and even the TimeControl instance. That’s fine. But don’t get started on an upgrade without backing it up first.
Look before you leap
This advice is often given to swimmers venturing outdoors into an unknown area. Diving into water that looks deep but turns out to be rock-filled or shallow can be dangerous. In the case of TimeControl, take a look at the Read-Me files, any What’s New in this version files and even the installation and upgrade guide before jumping into a new version. Just because a new version of TimeControl has an exciting new screen doesn’t mean that you need to upgrade right away. If your current TimeControl is happily operating then there is a disincentive to go through the effort of upgrading.
All the world’s a stage
”All the world’s a stage…” said Shakespeare (in As you Like It). In this case, I’m referring to staging your upgrade. Every enterprise system should probably have both a production instance and a staging or development instance. Your TimeControl licensing allows you to do this without extra cost. Establishing an instance of TimeControl that has everything your production configuration has (easy to do by copying the production database back to the staging instance) means that you can test out new updates before they’re made available to the end-users. That’s just a best practice for any enterprise system, not just TimeControl. This allows not only new updates but any configuration changes such as new filters, new reports, new validation rules to be tested out in advance. With a new version like TimeControl 6.0 where the architecture was significantly changed or 6.1 where core functions like table management underwent big changes, you’ll be able to ensure that your system will work just as it should before end users are exposed to it.
Do the whole upgrade
One of the most common upgrade problems reported to our technical staff from clients is finding that the client either skipped a step or didn’t finish the entire process. This is particularly true when clients are trying to upgrade through multiple versions and the client doesn’t let the Administration Transaction Server start and complete the update work in each version before moving onto the next. So, make sure you’ve complete all the steps to the update!
Be prepared to advance to the rear
Not every upgrade goes perfectly and for a wide variety of reasons. When you do your update, be prepared to retreat, regroup and try again. If that happens, HMS Technical support will be available to answer questions on what the issue was.
With a product that is in its sixth generation and 17th year on the market, we’ve seen a lot of updates and full upgrades over the years. If you’d prefer, HMS Consulting services is always available to help you get the very latest version up and running in your office!