|
IBM Operational Decision ManagementIBM Operational Decision Manager (ODM) is IBM's Business Rule Management System (BRMS). IBM ODM also incorporates IBM's implementation of business event processing (also called complex event processing) capabilities. IBM ODM can be installed both independently and as an application running on WebSphere Application Server. This software is currently in V8.11.0 (as of October 2022). Business rules and eventsRulesA business rule is a statement of logic that is used for a business decision to be made. This statement of logic is generally part of a business policy. Rules processing involves a piece of software using this pre-defined rule to make a real-time decision. ExampleA policy states that a borrower's initial loan must not exceed 3 times their annual salary.
The Business Rule would read: EventsA business event is a signal or collection of signals indicating that a change in state has occurred, and consists of a small message. Event processing involves using events to determine if an action needs to occur as a result, and carrying out that action. ExampleIf a customer's withdrawal event on their account causes the balance to drop below zero, then an action is taken to notify that customer. Artifacts of IBM ODMIBM ODM is an implementation of a Business Rule Management System. It allows the creation, management, testing and governance of business rules and events and stores them in a central repository where they can be accessed by multiple individuals and software products. This central storage of the rules and events mean that they can be easily modified without having to rebuild software, and with a reduced testing cycle, and the different software products will pick up this change simultaneously. Action rulesA basic rule expressed in a logical form, stating that if a condition occurs then an action should result. IBM ODM uses Business Action Language (BAL) to define such rules, allowing them to be viewed in a more 'natural' language. ExamplesIf a credit card transaction occurs outside a customer's country, then that customer should be called to confirm the card is not being used fraudulently. At a bank some customers are not allowed to become overdrawn and some are:
otherwise:
Decision tablesExampleA loan company determines the insurance rate of a loan depending on the amount, and the credit rating of the customer.
Presented with a customer in group B asking for a loan of $250,000, the rule would indicate the insurance rate should be 0.002%. Rule flowsThese indicate the order in which rules should be executed. ExampleAn insurance company wants to establish whether a driver should be given a particular insurance policy. The decision depends on: The age of the applicant
Score cardThis is a statistical model that applies a numerical score to an object, such as a customer or an account. The same attributes are applied when calculating this score for each item. ExampleA score is allocated to a borrower depending on their Age, Citizenship and Credit grade.
EventsIf a specific change in state occurs then a message is emitted causing an event to occur. ExampleAt a bank some customers are not allowed to become overdrawn and some are. A customer who has tried to take out a loan is refused by the system because their credit rating is too low. In summaryCombining Business Rules and Events within the same system brings together two complementary technologies to automate real-time decisions. An event may trigger a rule to be run, conversely the outcome of a decision made by a rule may emit an event. ComponentsIBM ODM consists of the following parts: Decision centerThis provides a repository and management component for the creation and maintenance of decision logic, guiding the business system's behavior. It is the central hub for the coordination of the decision life cycle, covering both business rules and business events, and allowing editing of each. Decision serverThis consists of the runtime components for business rules and business events. Decision server rulesThis provides a group of tools for construction and running of rules and automated decisions. Various components give access for different types of users, allowing the design, authoring, review, testing and running of business rules. This includes the Rules Designer, an Eclipse-based application for developing applications in Decision Server Rules. Decision server eventsThis provides an integrated set of components for running events. Various components give access for different types of users, allowing the design, development, testing, deployment and maintenance of business events. This includes the Events Designer, an Eclipse-based application for developing applications in Decision Server Events. Connection between partsRules can be defined in the Decision Center and can also be updated there, using a variety of interfaces, including the Enterprise Console, Business Console. Rules are then stored in a Repository which manages the Decision Artifacts, access and control and versioning. From here the rules are deployed to the Decision Server, which executes these rules, and provides monitoring and measuring facilities. Rules can also be deployed direct to the Decision Server using the Rule Designer or Event Designer. RequirementsDecision Server Rules can run on distributed systems: Decision Server Rules can run on the z/OS mainframe: Decision Server Events and Decision Center can run on Supported platformsHardware and software requirements Version historyPrior to its release at V7.5, the parts of ODM were available as separate products:
Websites claiming or suggesting that ODM is a notable piece of softwareTechnology Blog References
IBM Websphere Business Events External links
|
Portal di Ensiklopedia Dunia
