IBM Operational Decision Manager vs. Progress Corticon Business Rules Engine

IBM Operational Decision Manager can be used to manage complex business processes with less use of IT infrastructure and more use of centralized decision making. Decision-making depends on a logical framework and the creation of commands for better futuristic decisions with less time consumption and more precision and accuracy. IBM's Operational decision manager application is well suited for such scenarios where complex processes have to be streamlined.

Incentivized

Suited for any place where complex business rules need to be separated for ease of flexibility.

• Excellent stability and performance, as well as the possibility to deploy more quickly.
• Simple but effective web-based user interface that enables us to make direct updates to our policies or rules.
• Effective rule Execution Server, which allows us to assess the rules and their performance
• After the rules are delivered, business users can make changes and keep them up to date without having to know a lot about technology.

Incentivized

• Handle complex business rules.
• Test different scenarios after changes have been made.
• Allow for version control and auditing of queries and responses.

• Business rule application development available only in Java, .net, and Cobol.
• Integration supports with legacy system need to be improved (Mainframe).
• Migration to latest -version (iLog JRules to ODM).

Incentivized

• The UI could be made more appealing.

When compared to other vendors in the business rule management system, IBM Operational Decision Manager stands out in dimensions of rule engine capabilities, deployment flexibility, and ease of maintenance. It offers a wide spectrum of configuration options to build applications that can be used by developed by technical and non-technical/business users.

Incentivized

Corticon is way easier and allows for testing.

• It has a positive impact as it provides a great way to define business rules, execute them, update them, manage different versions of rules.
• Depending on the complexity of the applications, you can have thousands of rules.
• It provides a nice way to test the rules, run simulations with different scenarios, different scales of requests and verify the decisions, performance, etc., and that helps a lot.
• Since the decisions can be exposed through REST interface, it makes it very convenient to integrate with different applications, applications using different technologies.
• The Business console makes it easy for business users to be able to define, modify rules and not have to depend on IT to do a lot of that work. This helps in bringing the time to change and use the rules to be very short as well as lets IT do more IT related tasks and provide better value to the organization.

Incentivized

• It has definitely had a positive ROI. Instead of having developers try to figure out these complex rules and how to code them in a flexible way, we now have business analysts using Corticon.