Decision Server. Combining Business Event Processing and Business Rules Management for Decision Agility and Effectiveness IBM Corporation

Transcription

1 Decision Server Combining Business Event Processing and Business Rules Management for Decision Agility and Effectiveness

2 Agenda Introduction WebSphere Decision Server WebSphere BRMS WebSphere Business Events Summary 2

3 Decision Agility and Effectiveness Requires Situational Awareness and Response Event Account Withdraw Event Started Application For New Account Event Account Withdraw Actionable Situation Numerous small deposits and small withdrawals within short time frame Actionable Situation Did not complete application after 2 days and have had other activity with the bank or are an existing customer Actionable Situation High-value customer and cumulative withdraws G.T. 75% of balance within last 30 days Action: Flag account and initiate money laundering evaluation Action: Trigger follow-up process to assist with completion of the application Action: Alert Account Manager of possible attrition

4 data Key Technologies for Decision Agility and Effectiveness Derive deep understanding of data with analytics Monitor and report on data to provide real-time insight data Event Correlate business events and detect critical business situations Orchestrate business processes and human task applications Event Event Automate high-volume operational decisions with business rules data data

5 Business Events Indicates the Need to Make Decisions Address Change Logged into website Wire transfer Close account Added dependent Suspicious activity Account rollover Bill paid Large Transaction Accept offer Customer complaint Late payment Increase in activity Open account Start Application for New Account 5 5 Events pass silently back and forth as unrelated pieces of communication. They are a source of great power, for when they are correlated, they yield a wealth of information. -Dr. David Luckham, Professor Emeritus, Stanford University

6 Agenda Introduction WebSphere Decision Server WebSphere BRMS WebSphere Business Events Summary 6

7 WebSphere Decision Server WebSphere Business Events (WBE) plus ILOG JRules Detect (WBE) Decide (JRules) Evaluations Correlations Actions WBE - Detects when events or patterns of events occur to notify people or systems to take action Actions JRules - Decides business outcome through execution of business rules against available data

8 Agenda Introduction WebSphere Decision Server WebSphere BRMS WebSphere Business Events Summary 8

9 BRMS What are the steps? 1- Discover, extract and model rules and vocabulary Mainframe Manual Processes Monolithic Applications Rule Repository User Tools 2- Deploy rulesets 5- Maintain Rules as Decision Services Spreadsheets Databases Rule Execution Server 4- Monitor Service 3- Integrate with Orchestration layers/client applications as a business component Business processes Portals Client Apps Queue/Bus Mainframe

10 ILOG JRules Components Rule Studio Rule Team Server Decision Validation Services Sync Rule Solutions for Office Eclipse-based Rule IDE Rule design & development Deploy rules Deploy rules Web-based console for Rule Maintenance & Testing Sync Offline Rule Maintenance Decision Warehouse Rule Repository Runtime environment Audit trail of decisions Rule Execution Server Single node or cluster (J2SE & J2EE compliant) Web-based console to monitor & control rule execution 10

11 Examples of Customer BRMS Applications Banking Loan Origination Credit Decisioning Sales Advisory Payments Accounting Insurance Claims Processing Underwriting Quoting Rating Commissioning Capital Markets Automated Trading Trade Order Management Accounting Compliance KYC / AML On Boarding Public Sector Claims Processing Entitlement and Benefit calculation Fraud Detection and Management Screening and Targeting Telecom Transportation and Travel Retail Manufacturing Offer Configuration Order Management Fraud Detection and Management Loyalty Programs Network Monitoring Promotions Management Loyalty Programs Customer Service Billing Contract Management Online recommendation Campaign Management Order Management Pricing Order Management Billing Contract Management

12 Drivers for implementing the logic in JRules When there are large numbers of rules When the rule logic is complex When the business/policy owners need to be able to view or change the logic When the logic changes frequently When multiple versions of the logic are required for different date/time/regional/etc. criteria When you need high performance When you wish to reduce on-going maintenance costs When the decision services are re-used across systems

13 Agenda Introduction WebSphere Decision Server WebSphere BRMS WebSphere Business Events Summary 13

14 WebSphere Business Events A powerful, scalable, flexible event processing platform Business user oriented interfaces reducing time to value. Built-in Connectivity to the widest range of events. Designed to expect change supports incremental development and deployment The Convergence of Power and Ease of Use The real world is mostly event driven, and event-driven situations are best addressed by event-driven business applications. Roy Schulte, VP Gartner Research

15 Building up some logic and then If Event Conditions Actions (Enrichment) (Value or Correlation) (Enrichment) (Alert or Initiate Systems) If Event-A occurs then initiate Action-X If Event-A occurs and Data Field = <>(value) then initiate Action-X If Event-A occurs 3 times and Data Field = <>(value) then initiate Action-X If Event-A occurs and Event-B occurs and Data Field = <> (value) then initiate Action-X,Y If Event-A occurs and Event-B occurs and Event-C does not occur and Data Field = <> (value) then initiate Action-X,Y If Event-A occurs and Event-B occurs within 15 minutes and Event-C does not occur within 2 days and Data Field = <> (value) then initiate Action-X,Y,Z If Event-A occurs and Event-B occurs 2 times within 15 minutes and Event-C does not occur within 2 days and Data Field = <> (value) then initiate Action-X,Y,Z

16 WebSphere Business Events Design and Runtime Interface Design Data Dashboard Design WBE Object Repository Business Event Tester Event Flow Event Capture and Replay User Console

17 Define Logic with Graphical Interface Empowers IT and Business Analyst to define the logic Event Interaction Data Filter Conditions Actions Drop-down, Point & Click Construction Filters Business Vernacular Reusable Assets Events, Filters, Actions Business Define Logic Users without Maintain Programming Logic

18 Drivers for detecting event patterns in WBE Use WBE to identify event patterns Where the actionable event needs to be derived from physical events Where the action is not an immediate result of a single event Across multiple event types, different event sources Where the non-occurrence of an event is significant Where events may not be ordered Where events are time related - must occur by a particular time, or within a particular time of one another Evaluations Correlations Capture Generate Actions

19 Agenda Introduction WebSphere Decision Server WebSphere BRMS WebSphere Business Events Summary 19

20 WebSphere Decision Server in combination with an ESB A rich source of business events from the ESB Event transformation takes place within the ESB Actions can be routed and transformed by the ESB Rule based routing and transformation Promoting consistent reuse of rules across the organisation Event Event ESB Event Correlate business events and detect critical business situations Automate high-volume operational decisions with business rules WBE provides nodes and primitives for WebSphere Message Broker and WebSphere ESB use JMS or MQ for DataPower BRMS can either be called via web services, embedded as JCA components or run in process

21 Health Care: BEP + BRMS Disease Management Business Challenge: Large, regional Healthcare provider challenged to offer improved patient after-care to reduce readmissions, overall cost and risk for both provider and payer. Solution: WebSphere Business Events and WebSphere ILOG JRules are being used for real-time assessment and decision-making for chronic disease management: capture care events and home health device metrics catch problems before they escalate into a dangerous and costly treatment situation when WBE detects and identifies defined patterns of interest, it initiates JRules to make patient-specific decisions, providing guidance to healthcare provider Goals: Ability for clinicians to customize logic for individual patients Improved patient care and loyalty to the provider Reduced readmissions Reduced cost to patient and provider Mitigates risk for both the provider and payer

22 Insurance & Credit Card Services: BRMS + BEP Maximize the Value of Customer Interactions Customer Acquisition (E.g. Car Insurance) WBE to monitor customer behaviour and offer promotional discounts Detect multiple requests for insurance quote over a short period of time Detect quote requests that have not been accepted within a period of time Trigger action to JRules to determine customer promotional offer JRules to determine whether to make an offer, and if so, for what Tailor offer based on customer demographic and quote details Provides ability to quickly introduce/remove offers as company risk profile changes Value Add Personalized Service and Interaction (E.g. Credit Card Services) WBE to monitor transaction behaviour based on individual customer preferences Detect patterns and subsequently notify cardholders about card activity behavior and thresholds (i.e. purchases exceed threshold over 24 hours) Offers business users the flexibility to change rules and patterns definitions Identify behaviour patterns that meet promotional opportunity JRules to determine whether to offer a targeted offer, and if so, for what Precise offer based on customer profile and behaviour

23 Agenda Introduction WebSphere Decision Server WebSphere BRMS WebSphere Business Events Summary 23

24 Key Technologies for Situational Awareness and Response Business Event Processing Primarily implements a timebased pattern detection model correlating events as data is in motion Main purpose is to determine what of interest is transpiring and coordinate one or more responses by other systems or generate alerts to people Correlating patterns of events coming from different sources is a key capability Business Rules Management Primarily implements a decision model - given a snapshot view of data, determines best course of action at a specific point in a process or application Main purpose is to automate a decision based on a combination of factors (business policies, regs., best practices) Governing the evolution of decision logic used by operational systems is a high priority Gartner characterizes BRMS and CEP systems as complementary notions. The combination being required to implement intelligent decision management programs. Gartner Research Report: Rule Engines and Event Processing, Mar