Disadvantages of Desktop Based CMMS

Disadvantages of Desktop Based CMMS


CMMS or Computerized Maintenance Management System is software that allows companies to keep track of maintenance that has been done, or can schedule work needing to be done in the future. This software also allows companies to track the cost of repairs in addition integrate a variety of preventive maintenance techniques. That being said there are basically two ways that CMMS software is implemented.

The first way that a CMMS solution is implemented is by employing a web-based approach. What this method is that the servers that house the software that runs CMMS is typically not the character of the actual company using the CMMS. They basically outsource this task to others. One major reason this is done is that it allows those who need to have access to the CMMS database can have 24/7/365 access from anywhere in the world, as long as they have an internet connection.

The second way that CMMS is implemented is the desktop or network approach. The way that the desktop approach is typically implemented is by allowing the company that requires the use of the CMMS software to have all control over the hardware and software. This system is usually implemented and maintained by the company’s IT department. While there are some advantages and disadvantages to each approach, the disadvantages of a desktop based approach seem to outweigh the advantages.

For one, a major disadvantage of a desktop implementation is the access. If you ingemination, a web-based CMMS allows you to access the servers from anywhere in the world, as long as you have an internet connection. This is not true with a desktop configuration. With a desktop, you can only access when you are on your companies network. Another big disadvantage to a desktop configuration is the high initial costs associated with making this work.

If you ingemination, with a hosted CMMS approach a third party maintains the server hardware that is required to run the CMMS software. So, when something goes wrong, and it ultimately will, you are not responsible to fix the server hardware. Not so with a desktop configuration. With a desktop approach if anything happens to the hardware or software that runs on your company servers, your company pays to have it fixed, not to mention the higher start up costs associated with the desktop approach as you have to buy the hardware and software yourself.

leave your comment