The only thing we have trouble with is integrating IBM ODM with the cloud. The product is on-prem, and we need to migrate the rules to the cloud. It's a hectic process.
Configuring it on the Tomcat site and on the client's cloud environment, we faced a lot of issues. After configuring it on the Tomcat side, getting it on the Unix server was an issue. There are two issues that I am facing right now. The first is that the errors I get from time to time are not easy to debug or easy to understand. They are very vague because if a XOM file is missing or there is a deserialization problem, on the client's side I only get a 500 Internal Server Error. To learn where the problem is, I have to go on the Rule Execution Server and test it myself. The deserialization issue is very vague. The error messages should be more straightforward and easy to understand. I would also like to see the installation part on a single disk only, instead of on three disks. In our local environment we are installing it on Windows, and for the client side we are installing it on a Linux server. For a new user or a new developer or a fresher, it was tricky to understand which disk should be installed first, even if they're labeled Disk 1, Disk 2, Disk 3. Configuration is kind of tricky for a new person. Right now we have to use Installation Manager. It should be like installing any other software. Finally, it should also start supporting the NoSQL DB. Currently, It does not support NoSQL. I don't know if the newer version supports it, but as far as I know it doesn't. It would make the job easier. Right now the client had to buy a MySQL license, so they are maintaining a separate database for ODM. It should be kept on a single system. NoSQL DBs are better and it can be done.
There is some promise of how decisions could take advantage of machine learning and artificial intelligence (AI). That has been slow to develop. It is still not clear where the market will take it, but that is something that I am looking forward to down the road. Today we augment some ODM decisions with AI and with analytics, but I expect that in the next several years we will see much more growth in this area. ODM has recently released support for Decision Modeling and Notation (DMN) models that can be authored and executed right within the product. This too is an area that is in its early stages and I expect will mature quickly to an enterprise level.
Learn what your peers think about IBM Operational Decision Manager. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
Data Manager at a transportation company with 10,001+ employees
Real User
2019-06-18T10:29:00Z
Jun 18, 2019
I would like to have integration of the user interfaces, and they are putting them together in the next version of the solution. There used to be two separate interfaces. Now, they are merging them into one.
One area for improvement is master data integration. That should be more fluid. The others are hierarchical drop-down lists, and hierarchical master data. We have a few hundred others that I have on the list.
IBM Operational Decision Manager is a comprehensive decision automation platform that helps you discover, capture, analyze, automate and govern rules-based business decisions. Anyone can work with it―from IT to business-line leaders. In seconds, it can authorize a loan, decide on a promotion or detect a cross-sell opportunity with high precision and customization. With IBM Operational Decision Manager, your applications will continuously remain up to date and well aligned with the changing...
The solution's licensing cost needs improvement.
The only thing we have trouble with is integrating IBM ODM with the cloud. The product is on-prem, and we need to migrate the rules to the cloud. It's a hectic process.
An area for improvement is that the documentation for ODM is huge and not very clear.
Configuring it on the Tomcat site and on the client's cloud environment, we faced a lot of issues. After configuring it on the Tomcat side, getting it on the Unix server was an issue. There are two issues that I am facing right now. The first is that the errors I get from time to time are not easy to debug or easy to understand. They are very vague because if a XOM file is missing or there is a deserialization problem, on the client's side I only get a 500 Internal Server Error. To learn where the problem is, I have to go on the Rule Execution Server and test it myself. The deserialization issue is very vague. The error messages should be more straightforward and easy to understand. I would also like to see the installation part on a single disk only, instead of on three disks. In our local environment we are installing it on Windows, and for the client side we are installing it on a Linux server. For a new user or a new developer or a fresher, it was tricky to understand which disk should be installed first, even if they're labeled Disk 1, Disk 2, Disk 3. Configuration is kind of tricky for a new person. Right now we have to use Installation Manager. It should be like installing any other software. Finally, it should also start supporting the NoSQL DB. Currently, It does not support NoSQL. I don't know if the newer version supports it, but as far as I know it doesn't. It would make the job easier. Right now the client had to buy a MySQL license, so they are maintaining a separate database for ODM. It should be kept on a single system. NoSQL DBs are better and it can be done.
I don't see a need for additional features. I like it just the way it is.
There is some promise of how decisions could take advantage of machine learning and artificial intelligence (AI). That has been slow to develop. It is still not clear where the market will take it, but that is something that I am looking forward to down the road. Today we augment some ODM decisions with AI and with analytics, but I expect that in the next several years we will see much more growth in this area. ODM has recently released support for Decision Modeling and Notation (DMN) models that can be authored and executed right within the product. This too is an area that is in its early stages and I expect will mature quickly to an enterprise level.
I would like to have integration of the user interfaces, and they are putting them together in the next version of the solution. There used to be two separate interfaces. Now, they are merging them into one.
What I'm really interested in, what I'd really like to see with this technology, is artificial intelligence, RPA. How can that interface with ODM?
One area for improvement is master data integration. That should be more fluid. The others are hierarchical drop-down lists, and hierarchical master data. We have a few hundred others that I have on the list.