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 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."
"So far, the usability is great. It's also easy to set up."
"With ODM as a centralized rules engine, it's easy to track. You can version the rules in the ODM engine itself."
"ODM's most valuable features are that it's easy to define and divide business rules, and it can handle very large numbers of transactions per second."
"ODM provides an efficient, comprehensive way to manage all the applications. Regardless of the BPM tool we are using, we choose ODM because it's flexible."
"By using ODM, we get rules to our applications, then we get those applications to go to market a lot faster."
"It's easy to build, easy to adopt for the business. Business can change those rules. I think IBM has done a good job in re-architecting the product with Decision Center as its centralized view, where the business can make changes to the rules dynamically."
"The solution has reduced the backlog for IT."
"Case Management is the most valuable feature of PegaRULES, which is not found in other BPM tools."
"It's not too expensive."
"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."
"getNext removes some of the managements overheads as well as inbuilt reporting."
"They're pretty easy to create, and they're pretty easy to deploy."
"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."
"Offers a unique environment where its entire architecture is very unified"
"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."
"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."
"One area for improvement is master data integration. That should be more fluid. The others are hierarchical drop-down lists, and hierarchical master data."
"I think it's stable, but if they could beef it up a little bit for bigger businesses, that'd be great, because we have so much in there. We have products that we have to split up because they are too big for it to handle sometimes. But that's just in development, within ODM. Again, processing has been fine, but I wish things were a little bit beefier."
"An area for improvement is that the documentation for ODM is huge and not very clear."
"Get to the cloud."
"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."
"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."
"It hasn't totally helped our decision-making."
"Containerization should be improved in relation to Pega because Camunda is deployable in the containerization deployment process."
"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."
"Implementation is a challenge due to the handling of the code"
"The solution needs to invest more in its technology. For public and private clouds, for example, the development environment is slow. Saving events should take one to two seconds, max, and because you are making changes often, the slowness cuts down on productivity because we have to wait for things to save before continuing."
"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."
"PegaRULES should provide a more drag-and-drop interface to make it a low-code, no-code product."
"The quality of partners available with Pega specialisation can be improved."
"Customers expect more out-of-box solutions to be readily available"
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.
