TimeControl and TimeControl Industrial are on-premise versions which are both available as in-the-cloud subscriptions as TimeControl Online and TimeControl Industrial Online.  We are committed to continue to sell, support and evolve the on-premise versions.  The code-base of the on-premise TimeControls and the Online TimeControls is the same so new editions of one mean enhancements in both.

Some of our best practices in TimeControl Online are automatic for us so we thought it would be worthwhile to remind our on-premise TimeControl clients of some things they should be doing to maintain a stable, secure system.  Some of these items are seen by technical support when clients with TimeControl on-premise call with issues or concerns.

Who’s in charge?

One of the most critical elements to keeping any TimeControl system operating at peak efficiency is to ensure different roles are clearly defined.  With TimeControl Online, all the technical aspects are handled by HMS but with an on-premise system, sometimes the people responsible for the technical aspects of the system move onto other projects once the system is successfully deployed, leaving only the TimeControl Administrator(s) to manage the system.  Keeping TimeControl running smoothly requires keeping the multiple aspects of this enterprise system maintained so defining roles for that and keeping them current is important.

Hardware

The Servers on which you installed TimeControl need to be monitored and maintained just like we do with TimeControl Online.  If there’s a disk failure warning, then fallback hardware should be able to take over instantaneously with no interruption in service and updates to hardware have to be done in a timely fashion.

Operating System

Whatever operating system you installed TimeControl on will get updates, need upgrades and at some time will need to move up to new hardware.  This is often something we get calls about because TimeControl deployments can last for many years and outlive the versions of the operating system that it was originally installed on.  In some cases, upgrading your operating system may require an upgrade to TimeControl.  There are sometimes upgrades to operating systems that a very old version of TimeControl can’t support because that operating system didn’t even exist at the time.  So, keeping the operating system up to date and keeping your TimeControl close to current is the best practice.

Database

Just like your operating system, TimeControl depends on a SQL database like Microsoft’s SQL Server, Oracle or MySQL.  That database will also receive updates and upgrades and there can be incompatibilities between an old version of TimeControl and a new version of the database.  This category makes up most of the technical calls during on-premise upgrades that we receive.  Checking the compatibility of the version of TimeControl you’re using with the version of the database you want to upgrade to is very important.

Malware protection

We run Malware protection on TimeControl Online at all times and threats to any servers are a constant so you need to make sure that your malware protection is kept current with virus updates and that any changes to the Malware protection accommodates how you set up TimeControl originally.

Firewall

Your on-premise TimeControl may be outward facing meaning that it may be accessible through the Internet.  If that’s the case, then any changes to your firewall can affect TimeControl.  This was almost certainly documented when you did your original installation so keeping track of those details and making sure your firewall people know to include that information in their firewall update is key.  This is the second most common request for technical assistance for on-premise systems.  When we track down the issue, it turns out to be a well-meaning change in the client’s firewall.

Monitoring

We monitor TimeControl Online 24×7 with updates to key personnel if there is ever an outage.  You should be doing the same with your on-premise system. If the system goes down, who is responsible for responding to that?

Browser support

It’s almost in the back of our minds because browsers are the water we swim in but browsers change.  They change usually without notice and resulting changes can affect TimeControl.  Keep track of TimeControl’s hardware requirements for each version and, if you are locked into an older browser or you have new browsers but are locked into an older TimeControl, watch out for incompatibility.

Staging Server

Almost all of our enterprise clients using TimeControl Online elect to have us provide a low-cost second staging server which can be automatically updated from the production database.  This provides a place to test new reports or integrations and to test new updates before they go live.  We highly recommend that on-premise clients do the same.  Your TimeControl licensing allows you to install a server for backup purposes so long as it is not used in production.  That gives you a place to test any new upgrades.

Backups

You never think you need a backup until you do and then with that sinking feeling, you wonder how long it’s been since you backed up your system.  With an enterprise system like TimeControl, your backup process should be automated and multi-tiered with daily, weekly and monthly backups as well as off-site backups in case of disaster.  If you’re doing an upgrade, then taking a backup first is highly recommended.

Managing Upgrades and updates

Updates come out for TimeControl on-premise every few weeks.  They aren’t essential for everyone so we think of them as a hot fix.  There is no new functionality for everyone in an update.  An upgrade or a new version of TimeControl contains changes so planning for your upgrade, making backups before you start and making sure all the right people are available is key.  We recommend highly that on-premise clients stay as close to the most current release as possible since it’s always being improved and any security or performance issues are a natural part of the new version process.

Documenting your system

Finally, the one thing that is least popular and least common is the one thing that can make the most difference to the stability of your on-premise TimeControl.

Document it.

Keep a record of what versions of what elements of the system were required as part of your installation and as part of any upgrade at any time along with what your process is.  One of the most common situations we see is that a personnel change results in someone new trying to figure out how TimeControl works and what elements of their internal systems are connected.  That’s a formula for upset which is easily circumvented by keeping good system documentation.  That’s particularly true when part of the system includes integration with other pieces of software or data that HMS doesn’t even have access to.  Then your internal documentation becomes key.