The solution works well, but we need better project planning. Accessing some features is a bit complicated, and we're waiting for improvements from SAP. It should also improve integration.
Senior Director Of Information Technology at a non-tech company with 10,001+ employees
Real User
2021-11-02T13:57:39Z
Nov 2, 2021
The next step for Operations Analytics is the ability to take the data and make intelligent decisions with the software. For example, you could automate the software with statements like: "If the thread count's high and RAM utilization is low, then report this." It would be great to have a monitoring tool that could implement conditional solutions like this. Right now, it comes up with the indicators, but it doesn't necessarily send the lower-level technician to the right spot. The engineer and the database SME have to notice it, then those two come together and tell the low-level engineer what to do. The next step is to remove the middle man and get the notification right to the technician so that you can correct the situation right away. You've also saved staffing costs by using one person instead of three. So there are all kinds of efficiencies that come out of that.
IT operations analytics is a group of practices and processes to monitor systems in order to gather, process, analyze, and interpret data from IT operations to guide decisions and manage risks.
The solution works well, but we need better project planning. Accessing some features is a bit complicated, and we're waiting for improvements from SAP. It should also improve integration.
The next step for Operations Analytics is the ability to take the data and make intelligent decisions with the software. For example, you could automate the software with statements like: "If the thread count's high and RAM utilization is low, then report this." It would be great to have a monitoring tool that could implement conditional solutions like this. Right now, it comes up with the indicators, but it doesn't necessarily send the lower-level technician to the right spot. The engineer and the database SME have to notice it, then those two come together and tell the low-level engineer what to do. The next step is to remove the middle man and get the notification right to the technician so that you can correct the situation right away. You've also saved staffing costs by using one person instead of three. So there are all kinds of efficiencies that come out of that.