We performed a comparison between IBM Operational Decision Manager and PegaRULES based on real PeerSpot user reviews.
Find out in this report how the two Business Rules Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It has benefited our organization by having less coding changes. Thus, we save time and don't have to hire as many people."
"The most valuable features are the Decision center, a web UI that allows us to make direct edits to our policies or rules; the Rule Execution Server, which allows us to analyze the rules and performance; and Rule Designer, where you can write rules and decision tables."
"It is a scalable solution."
"The business owns the rules and they're taken away from IT, so business doesn't need to ask IT to implement them, and IT doesn't need to implement them. So the business owns their decisions and their rules, and therefore, finally, they take proper ownership, and model and maintain them properly."
"So far, the usability is great. It's also easy to set up."
"There are absolutely benefits to managing business rules with IBM ODM instead of hard coding them into our applications. Business can change things on the fly and they don't have to deal with us in IT to do so."
"It reduces operating costs because you are taking some of this work out of the high cost IT people, freeing them up to work on new initiatives and getting them out of maintenance mode. Now, the business people are the ones making business decisions on what needs to change. They are hands on making these changes."
"By using ODM, we get rules to our applications, then we get those applications to go to market a lot faster."
"The new PEGA underwriting platform replaced the former underwriting system and helped to integrate other legacy systems and functionalities in one application. It also helped to save licence costs for other legacy systems."
"They're pretty easy to create, and they're pretty easy to deploy."
"We can use the rules as per the class."
"What I found most valuable in PegaRULES is that it allows you to quickly make changes to an existing application. It's pretty easy to do any modification in the tool, which you cannot do in legacy solutions. For example, it takes a lot of time to do it in Java or in .NET. I have worked with both legacy technologies in the past, so that I can tell the difference."
"We find the product to be scalable."
"One of the key advantages of PegaRULES is its out-of-the-box capabilities, which eliminate the need to build certain functionalities from scratch. For instance, features like "get next" in process flows allow for the seamless continuation of a flow without the requirement of additional activity creation. This serves as an illustration of how existing components can be leveraged rather than starting from scratch. It provides a solid foundation, to begin with, and allows for enhancements at a higher level, making it a beneficial starting point."
"The most valuable feature of the product is that it's very customer-centric. It's easy to use for a customer or a user. It's also easy for someone who is developing an application. You can develop different features in just one place. You don't have to go to different places."
"The latest releases of PegaRULES are scalable, advanced, and can be easily integrated into your environment."
"The platform is good. Its footprint is a little heavy. Other than that, the product works great."
"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."
"An area for improvement is that the documentation for ODM is huge and not very clear."
"Get to the cloud."
"One area for improvement is master data integration. That should be more fluid. The others are hierarchical drop-down lists, and hierarchical master data."
"ODM could be improved with better integration with other platforms."
"If merging could be just like SVN, that would help. It should be a lot simpler. That's the only thing I don't like about ODM, merging from our local computer up to the Decision Server. I feel like it could be a lot easier."
"There is some promise of how decisions could take advantage of machine learning and artificial intelligence. 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."
"Implementation is a challenge due to the handling of the code"
"There is room for potential improvement in the performance of PegaRULES, as well as the need to address any existing security concerns. It should be noted that working with an older version of Pega, rather than the latest 8.x versions, may limit certain capabilities and leave room for vulnerabilities that could benefit from increased attention. Furthermore, the user interface (UI) could be a candidate for enhancements. It is worth mentioning that newer versions of Pega may have introduced improvements in these areas."
"PEGA claims that they provide a LOW-CODE-PLATFORM which is easy to use - even for "citizen developers" (i.e. business employees). If you really want to use all the features out of this platform, you definitely need a lot of experience and a lot of training."
"I've spent some hands-on time with the platform, and you can do those things, and it is all low code, but is it as easy as they make it sound? No. That's my two cents. For example, if I want to do something, there is no way to switch from low code. I just want to do a simple If-Then-Else rule, but I have to go through their low-code tool and do dragging and dropping. I'm a development person, and in my opinion, even some business users could do this easier. There is no way to go back and forth to an editor where I can just type in an If-Then-Else rule, which would be much faster than drawing in their low-code editor. They don't support that. They lead you too much."
"The UI has always been the weakest part."
"The usability of the solution for developers is sometimes difficult to work with because instead of fixing the existing bugs in the previous version, there is always a rush to push out a new version leaving the bugs in the old versions unresolved."
"We would like to have a better ability to customize PegaRULES."
"PegaRULES need to improve its JVM. It needs to enhance the operation speed and memory size."
More IBM Operational Decision Manager Pricing and Cost Advice →
IBM Operational Decision Manager is ranked 3rd in Business Rules Management with 15 reviews while PegaRULES is ranked 1st in Business Rules Management with 16 reviews. IBM Operational Decision Manager is rated 8.6, while PegaRULES is rated 8.2. The top reviewer of IBM Operational Decision Manager writes "The solution provides an efficient, comprehensive way to manage polices for all the applications". On the other hand, the top reviewer of PegaRULES writes "Seamless flows, high level capabilities, and straightforward installation". IBM Operational Decision Manager is most compared with FICO Blaze Advisor and Progress Corticon , whereas PegaRULES is most compared with FICO Blaze Advisor and Versata BRMS. See our IBM Operational Decision Manager vs. PegaRULES report.
See our list of best Business Rules Management vendors.
We monitor all Business Rules Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.