The setup of the solution is easy. However, if you want to integrate it with on-premises or cloud systems or implement it globally, some additional knowledge is required. When the solution is purchased, it was new to the market, but we were able to test and buy it and received about six or seven days of training sessions. The architecture of the solution is very good, and it is not complicated to install and integrate, especially for those with system administration experience.

The deployment time of the tool depends on the server you are installing it on. If it's only one server, the process is simple, and you can download the necessary files from various locations, including Discord. Installing the tool takes less than 20 minutes, and integration can be difficult, taking around an hour. This is apart from the standalone installation. However, if you want to integrate the tool with many machines, the process can take longer, but it still should not take more than an hour. To begin with, setting up the tool is simple, but to create templates and work groups, you need to have your own templates. After that, it's straightforward to add and configure them. Starting and finishing the process takes only a minute or two, and then the data can be easily retrieved.

The setup was straightforward for our purposes, but the more you want to monitor, the more you have to fine-tune things. This is true for all products. You get some basic functionality and basic monitoring with minimal effort, but if you put in more effort, you get more granular details out of it.

It deployed pretty fast. In one day you can be up and running with basic monitoring, but there were new features added to the system. If you need more, you will want to fine-tune the cluster and the way it monitors things.

In terms of the deployment process, you needed to add a virtual machine or a physical machine if needed. You then install the application, provide credentials, and that's it. You then just need to populate and you can do auto-discovery to populate it, although I'm not sure how the auto-discovery works. Our approach was to use the CMDB. We added the devices and elements that we wanted to monitor based on our CMDB.

I had two people onboarding it, but they did it as a side job, not full-time. It depends on how you set it up, but if you do it yourself, two people are sufficient to address it. They have to have some technical knowledge.

The initial setup was medium. It was not easy, nor was it difficult. You can take any server, install it, and download the OP5 from Google. It takes around 20 to 30 minutes for the main installation.

The initial setup is pretty straightforward. It does take some prior knowledge. You need to be an IT admin person to get it. But if you look at a normal installation on an IT infrastructure with up to, say, 1,000 servers, that is usually managed in under a week. That says something about the ease of implementation.

In terms of an implementation strategy, we have a template that we follow to save time and deliver an efficient setup. We're consultants, so we always try to anticipate questions and make it as easy as possible for the clients. So it makes sense for us to reuse the knowledge we have gained from other implementations.

It's quite well documented with the documentation available online, which is nice. The initial implementation is the smaller part. When you want to add functionality, such as implementing a new application or some new piece of hardware or software, there is a lot of material available online from ITRS on how to do that. That's good.

The initial setup is pretty straightforward and there are some templates that you need to apply. It's not for somebody who is inexperienced, but if you have some IT knowledge then you can get up to speed quickly.

Basically, we just need two parameters to set it up, and then it's up to you to decide what you want to monitor.

It is easy. We have one engineer for its deployment and maintenance.