Operational Decision Manager (ODM) is a platform for capturing, automating and governing business decisions

1. IBM Operational Decision Manager

2. Introduction
• Operational Decision Manager (ODM) is a platform for capturing,
automating and governing business decisions.
• Enables a business to respond to real-time data with intelligent,
automated decisions.
• With ODM, IT and business users can manage the business decision logic
that is used by operational systems within an organization.

3. Introduction
• In the form of business rules, the business logic can be packaged and
called from the Application code/ESB as a decision service.
• Changes to the business policy do not require changes to the Application
or Process code.

4. Operational Decision Manager components

5. Operational Decision Manager components
The Operational Decision Manager provides the below three components,
Decision Server: The Decision Server provides components for the Rule
application development.
Decision Center: The Decision center is used for Rule management and
Authoring.
Rules Execution Environment: The Rules Execution Environment
provides an execution environment for the rules.

6. Decision Server
• The Decision Server provides an eclipse based tool, Rules Designer, for the
development of the Rules.
Steps in Capturing the Rule
The process of capturing rules happens in two steps.
 The first step consists in formalizing the vocabulary that is required to express
the policy as a conceptual object model.
 The second step consists in representing the logic of the business policy as if-
then statements.

7. Decision Server
• A sample rule is shown below,

8. Decision Server
Execution object model (XOM)
• The execution object model (XOM) is the model against which you run the rules.
• XOM is the base implementation of the business object model (BOM).

9. Decision Server
Business object model (BOM)
• A BOM is implicitly mapped to a XOM of the same name.
• Every BOM element (business element) must have a corresponding XOM
element (execution element).

10. Decision Center
• The Decision center provides separate consoles for the business users and the
administrators,
 Decision Center Business Console: The business console allow business users to
Author, test, govern and deploy decision services to the Rules Execution
environment.
 Decision Center Enterprise Console: The Enterprise console allows
administrators or release manager’s option for managing the decision services
or the Rule projects.

11. Decision Center
• With Decision Center, business users can manage decisions that are directly
based on the organizational knowledge, with limited dependence on the IT
department.
• Business and IT functions can work in collaboration. The entire organization can
align in the implementation of the automated decisions.

12. Rule Execution Server
• Rule Execution Server provides the environment for running and monitoring the
rule applications.
• A rule application is deployed to the Rule Execution Server as a Rule App. Each
Rule App contains one or more rule sets, each corresponding to a decision.

13. Change management
• The following steps are involved in the change management,
 Initial release is created by the Developers.
 New release and a new activity is created by the Business Users.
 When all the change activities that are related to the release are complete, the
decision service is published to the Rules Execution server.

14. Testing Rules
• The Rules can be tested in the Decision center Business console using test data
files.
• The Rules can also be tested from the Rules Execution Environment as
REST/SOAP services.

15. Thank You