5 Things To Know About IBM Operational Decision Manager
MartinKeen 1200007VU3 Visits (2732)
IBM Operational Decision Manager is a business rules management system (BRMS). Traditionally, business rules have been implemented in a programming language such as Java or COBOL. Programming the business rules into an application makes them inaccessible to business users and difficult to change. A BRMS allows non-technical business users to easily view, maintain, and test rules, often with little or no assistance from technical resources.
Here are 5 things to know about Operational Decision Manager.
1. More than half of IT managers are using a BRMS
Analysts IDC have noted that the BRMS market for products such as Operational Decision Manager is “having a transformative effect on how organizations think about IT and address application development needs”. An IDC study showed 55% of IT managers were already using BRMS technology, and the BRMS market has exhibited double-digit annual growth.
2. There are two main components: Decision Center and Decision Server
Decision Center is a repository where rules are recorded and stored. It provides the governance capabilities and interfaces that enable business users to work directly with rules. Decision Server is the runtime component where business rules and event applications are installed and executed. Typically, Decision Server is hosted in a Java based application server, and is packaged with WebSphere Application Server. It can also be installed and run on other application servers or without an application server, albeit with limited capabilities.
3. It supports two types of decision: rules and events.
A business rule receives and responds to data synchronously. For example, a business rule could be: “if the value of a claim is greater than $1,000 then set manager approval to mandatory”. A business event, by comparison is called asynchronously and can trigger an asynchronous response. Here's an example business event: “if the number of claims of a customer within the last month is greater than 4 then send a request to the call center to contact the customer”.
4. It's officially intelligent software
The origins of Operational Decision Manager come from the IBM acquired company ILOG. ILOG was an international software company with primary locations near Paris, France and California. ILOG is an abbreviated combination of the French words “Intelligence” and “Logiciel”, which is translated as “Intelligent Software”.
A business process, such as one running in Business Process Manager, tells you what to do. Decision management tells you how to do it. The best solutions combine both products. You can embed dynamic rules into Business Process Manager using a Decision Service. The context of the business rule can be easily changed using the Rule Designer, and the newly changed rule will be picked up the next time the business process is run, without ever having to make changes to the business process itself. Similarly business events can be used to detect various situations that required prompt action, for example that possible fraud has been identified. The business event can then trigger a business process that performs a follow-up action. This is known as a “sen
For more information about Operational Decision Manager, see the IBM Redbooks Solution Guide Decision Management with IBM WebSphere Operational Decision Management and the IBM Redbooks publication IBM Operational Decision Management V8.0 Performance Tuning Guide.
Martin Keen is an IBM Redbooks Project Leader. He works with technical experts to create books, guides, blogs, and videos. Follow @MartinRTP on Twitter.