Reviews (1-1 of 1)
Score 8 out of 10
IBM Operational Decision Manager (ODM) is used for several use cases. It is used on multiple applications where static/stateless rules are needed as well as decision tables. There are rule applications and decision services that have rules, rulesets and decision tables that the business can create and set up and they are exposed to applications through the use of REST API.
- Provides users ability to define business objects and generates an execution object model behind the scenes so they don't have to worry about it.
- It provides an English like rule language to define the rules.
- It provides a Rule designer, an eclipse based IDE for technical users to create projects to have a decision service, rules, rulesets, etc, test it and deploy it on the server. You can use it on a local server or on a server environment to the RES runtime. It provides a context map that tells you what to do next and click on the icon or link to take you there and helps you finish the task. It is intuitive and user friendly.
- It provides a Business console that can be used by non technical users or business users to view, edit and deploy the rules on the RES. They can also create versions and save it in the decision center.
- It provides a way for users to define vocabulary so that the rules can use a user-friendly text instead of names of entity defined in the business object model.
- There is some confusion for users as they have many different tools and consoles to use and write/edit rules. There is the rule designer, an enterprise console, a business console, etc and there is overlapping functionality between the consoles.
- There needs to be support added for creating models using the decision modeling notation (DMN). Businesses need to be able to represent the knowledge using a model and DMN is a standard way of representing the information.
- Also to be able to import and export models that have been created using DMN. There are tools that companies use to create DMN models and represent the business domain and logic. This tool needs to be able to import those models and provide execution runtime for the same.
Read this authenticated review
ODM is well suited wherever there is business logic involved, specifically if the logic does not have a state. If there are business rules that can be defined, the context known and returns the same decision every time the same inputs are provided (stateless), it would be a good fit.
If there are a lot of business rules, set of rules that need to be executed in an order, rules that may need to execute conditionally, etc., basically complex rules and rule flows or decision tables, this is a great product. It helps businesses to manage and make changes to those rules dynamically and quickly and easily to adapt to changes.
When it may not be suitable is if rules can't be verbalized or if there is state or decision changes based on time or location or need context to be built. In that case a complex event processing engine might be a better fit.