It's important to make SAP IT Operations Analytics ( /products/sap-it-operations-analytics-reviews ) tool more flexible in terms of customization because when it comes to specific business models, the requirements of the business may vary, and there's a wide range of variety between each business model. Oil and gas is different than retail, which is different than FMCG. Everything is different, and companies are trying to push toward best of breed. Much of the time, best of breed does not meet the real requirements of each department head or the business model itself, so these tools need to be more flexible. The setup process is not a big deal for us. When we need to configure something or set up something new, the new technology of low-code, no-code is very good, and we are looking forward to more improvement in this part, because sometimes you miss a list of developers and need to write code. Therefore, we need it to be more easy for normal users. It's about how much professional teamwork is needed on these tools. Much of the time, normal users know they need to develop their own dashboard or analytics for a reason, and they are facing the problem of needing to understand how to write code. Recently, lots of tools came under the title of low-code, no-code, where you just need to drag and drop some fields to get your report. This area needs to be more agile and easy for normal users. System usability should be easier.
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 (ITOA) transforms IT data into meaningful insights, helping organizations streamline operations, enhance performance, and optimize resource utilization. This advanced solution uses analytics to prevent disruptions and improve decision-making, ultimately leading to better management of IT resources.IT Operations Analytics focuses on leveraging machine learning and data analytics to monitor and manage IT systems efficiently. It addresses challenges like system failures...
It's important to make SAP IT Operations Analytics ( /products/sap-it-operations-analytics-reviews ) tool more flexible in terms of customization because when it comes to specific business models, the requirements of the business may vary, and there's a wide range of variety between each business model. Oil and gas is different than retail, which is different than FMCG. Everything is different, and companies are trying to push toward best of breed. Much of the time, best of breed does not meet the real requirements of each department head or the business model itself, so these tools need to be more flexible. The setup process is not a big deal for us. When we need to configure something or set up something new, the new technology of low-code, no-code is very good, and we are looking forward to more improvement in this part, because sometimes you miss a list of developers and need to write code. Therefore, we need it to be more easy for normal users. It's about how much professional teamwork is needed on these tools. Much of the time, normal users know they need to develop their own dashboard or analytics for a reason, and they are facing the problem of needing to understand how to write code. Recently, lots of tools came under the title of low-code, no-code, where you just need to drag and drop some fields to get your report. This area needs to be more agile and easy for normal users. System usability should be easier.
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.