PQ Systems, Inc. | Quality Blog

Last year we deployed a new licensing option for all three of our major software applications. Up until that point, our customers licensed the software on a “per-computer” basis, meaning every computer terminal being used to run the program required its own unique license. As the software industry shifted towards enterprise and network licensing options, we received a steady stream of requests for more flexible “roaming” licenses. Thus, the concurrent-user license was born.

A concurrent-user license allows an organization to install our software on an unlimited number of computers on the same network, giving them the freedom to put these applications into the hands of any/all of their employees without the cost and hassle of managing individual licenses. The only restriction in the concurrent model is the number of people who can access the program simultaneously; when the sixth person attempts to log into a five-user license, they will get a message saying that the server is full.

We still offer the per-computer licenses, but the concurrent-user licenses have been steadily growing in popularity since they were launched.  Consequently, I routinely find myself answering the question “Should I switch to a concurrent-user license?”  My response is always the same:  “It depends.”

The value of a concurrent-user license versus the traditional per-computer license depends heavily on what sort of traffic to the program is anticipated. If you expect infrequent and fairly brief access from many computer terminals, a concurrent-user license would meet your needs for a fraction of what it would cost to license all of those terminals individually. On the other hand, if you have only a few terminals that need near-constant access to the program, it would likely be more cost effective to invest in per-computer licenses. In both scenarios, both licensing options could be applied to grant the required access, but selecting the appropriate license would save a pretty penny.

Please feel free to contact your account representative if you have questions about your specific application or contact me via e-mail at davids@pqsystems.com. We would be happy to discuss different licensing options with you.

Did you know that PQ Systems maintains a robust knowledge base online? It is a repository of common problems and solutions related to using our software and practicing continuous quality improvement. If you are an SQCpack, CHARTrunner, or GAGEpack user, you might just find a solution to your problem here:

http://www.pqsystems.com/kb/activekb/

In a recently-added article, Craig Newland, addresses how to count or group data that has been accumulated during certain periods of time. If you use CHARTrunner, visit: http://www.pqsystems.com/kb/activekb/questions/543/CR%3A+Data+grouping+tardiness to learn how to group your data to make your control chart analysis more telling.

Your first response to this question might be to quote the retail price paid for your SPC software. This would be a factual answer. Fast forward and imagine answering the question after using the software for six months or a year. Would your answer be different?

When evaluating SPC software there are many considerations; price is just one of these. Many other factors will contribute to the full cost of ownership. For example, the software will have to be installed, maintained, and supported. Users will have to be trained. Questions about the software will have to be answered – not just how to use it – but how to apply it in your system.

One of the largest costs might be described as the “make it work in my world” cost. Software designers often have a vision of how work progresses through a system. This vision might or might not align with the way work flows through your organization. I have seen software with impressive feature lists fail to be used – because the workflows just can’t be wedged into the way a firm actually gets work done. A good relationship with an experienced vendor support group can make a big difference – but if the workflows are misaligned – this can prove to be expensive.

Consider also the “manageability” cost. For example, you install the software for several users. They like it, they find it easy use, and they begin using it. However, they each take their own implementation journey. After a few months, important data, and analysis might be strewn about across your network somewhat haphazardly. How will this be managed? Once again, the feature list and price might look impressive – but the long term manageability might increase the real cost of ownership way beyond your initial impression.

It can be difficult to select any software and SPC software is no exception. If you find yourself in this situation, look beyond the initial price and feature list. Take a holistic view. Think about work flows and the long term feasibility of deploying the software and continuing to get knowledgeable support from a reputable vendor. In the end, the retail price might be the least of your worries.