We use ODM to set complex business rules. For instance, we deploy this solution for most of our banking customers because there are frequent changes in the policies and business rules. These are complex to manage for enterprise applications. 

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.

The primary use case is being able to expose business logic to non-technical users. This logic is traditionally hidden within code. ODM exposes the logic out to the business users for them to be able to manage it over time without IT involvement.

I work with many customers across industries such as healthcare, insurance, finance, manufacturing and others.  In every industry there are business decisions that involve complex logic.  My customers are enabled to have their business teams manage this logic and to change their business rules on demand without IT involvement.  

Objective: The primary use case is being able to expose business logic to
non-technical users. This logic is traditionally hidden within code. ODM
exposes the logic out to the business users for them to be able to
manage it over time without IT involvement.

Before ODM, all the rules were configured on legacy
systems we're transforming all this into a new set of technologies such
as REST microservices, cassandra and with IBM ODM so that Business Users will be able to easily change the rules.

Deployment is done on the client-side only. Business User can update rules through UI

I have used it for few projects in which number of business logic rules varied from the 70  to about 1,800 rules.

We use the solution to resolve complex business rules for our customers.

Our use case is that our business side has to make rules to take care of all the files that we process. Honestly, we do the coding side, I'm the developer on the site, and then the rule authors are the ones who create all the rules.

We have a lot of files that we process throughout the day. We're talking about 32,000 records per second, and it has been holding up really well. We have certain projects within ODM that are gigantic. They can get slowed down sometimes, but we're the only ones - I've looked around - we're the only ones that use that much; it can get slow editing. But when it comes to actually processing it in our production environment, we process things really quickly.

This was primarily to enable rules. I used it before, when I worked with Walmart, so not with my current employer, but the previous company that I worked for, Walmart Humana. The classic use case for Walmart was during Thanksgiving. Thanksgiving is a time when Walmart has huge sales and, at the same time, the most returns the next day. The rules should be competent enough so that business can apply those rules runtime, dynamically, without much involvement from IT. So IT just creates rules to apply discounts, initial discounts, and business has the ability to apply those discounts, change those discounts, dynamically. So that's one of the use cases.

The second use case that we did at Walmart was returns. So, you buy some stuff during Thanksgiving in one store, then you go to the next state and return it in the next state. So the tax rules change a lot. All those rules have been built in ODM. That was a classic example that we did in ODM. That's my first experience working with ODM as well.

The second one was with Humana. Humana is premium Medicare claims processing. There, we implemented ODM on mainframes, AS400. That's the first time I did work on AS400 and implemented ODM on them. There is a huge claims adjudication process that goes on within Humana. Most of the claims processing rules were done in ODM.

ODM tell us if customers are allowed to purchase specific tickets on our carrier.

It is a lot easier to make decisions using this solution. That is what it does.

It is a really good product.

My primary use case is to manage rules for the business.

We use ODM for rules management for many of our systems to manage rules for business coming in. We also use it to manage rules for our BPM solutions.

ODM is mainly used in banks to handle large numbers of transactions.

To automate business decisions and allow businesses to make smarter decisions faster with a moden business friendly Web Application, the users adore.

We use ODM for credit evaluation, online.

We use it for a cable company in a contract with Comcast.

It is to drive our rules engine for our revenue cycle.

We are just signing the contract and migrating to it now.