IBM Operational Decision Manager - …

1 IBM Operational Decision ManagerNovember 2013 Subhajit MaitrazChampion What is Decision Management? Introducing IBM Operational Decision Manager business Decisions Defined Components, Architecture and Technical Dive ODM on z/OSAgenda What is Decision Management? Introducing IBM Operational Decision Manager business Decisions Defined Components, Architecture and Technical Dive ODM on z/OSAgendaIBM ODM Technical Presentation IBM 2012 Operational Decision Management Transforms business OutcomesProviding an easily manageable, single source of truth foroperational business decisionsEnables changes to be easily made by business peopleCodifies business policies, practices and regulationsAutomates Decision making with the fidelity of an expert45 business Rules in organizationsSpreadsheetsDatabasesManual ProcessesBatch / COBOLO nline TransactionsCan get quite largeAre scattered everywhereAre subject to changeChallenges for a Change Request Changes are costly.

2 Resource & time-intensive Rules are hidden in COBOL code Most changes have to be programmed costly Lack of consistency No central management No reuse of Decision logic Gap between business analysts & IT administrators Knowledge fades over time Lack of audit ability No easy way to test/simulate changesPeople6 Operational Decision Management approachSpreadsheetsDatabasesManualProce ssesBatch / COBOLO nline TransactionsOperational Decision Manager PlatformRepositoryUser ToolsExecution RuntimeDecision logic is defined, analyzed andmaintainedDecision logic is stored andsharedDecision logic is deployed, executed andmonitoredPeopleIBM ODM Technical Presentation IBM 2012 Externalizing Decisions from Applications into business Rules Manage Decision logic independently from applicationsBusiness RulesApplicationApplicationDecision logic Natural language rules can be easily read Externalized rules are easy to change Centralized rules enable reuse and consistency Rules written in software code cannot be read by business people Hard coded rules are difficult to change Rules intertwined within applications cannot be reused by other systemsWithout Decision ManagementWith Decision Management7 IBM ODM Technical Presentation IBM 2012 DesignConstructTestValidateAuthorAnalyze ChangeRequestManage and MonitorFunctional

3 EnhancementsDesignConstructTestDeployDep loyDeployDeployDeployDeployValidateAutho rAnalyzeValidateAuthorAnalyzeValidateAut horAnalyzeChangeRequestChangeRequestChan geRequestSoftware Development LifecycleRule Management Lifecycle> 4-6 months< 1 month8 Decisions Need to Change Faster Than Software Applications Functional enhancementsIBM ODM Technical Presentation IBM 2012 Harness the Strengths of business Users & IT ExpertsWithout business RulesBusiness AnalystWrites requirementMake changes in monthsMake changes in monthsInformation AnalystCreates specificationsApplication DeveloperCodes implementationFunctional TesterValidates featureIntegration TesterRe-validates entire applicationBusiness AnalystRuns user acceptance testPerformance TesterEnsures application scalabilityIT Systems AdministratorPuts full application into productionIBM ODM Technical Presentation IBM 2012 Eliminate rework from misinterpreted requirements Speed up rule changesHarness the Strengths of business Users & IT ExpertsWithout business RulesWith business RulesBusiness users (SMEs) take control of the Decision logic & minor rule updatesBusiness users (SMEs)

4 Take control of the Decision logic & minor rule updatesSubject Matter Expert Reads existing rules in natural language Edits or adds new rules without any coding Runs testing and simulationPerformance TesterEnsures application scalabilitySME or IT Systems AdministratorPuts updated rules into productionIT experts ensure application availability, reliability & new application developmentIT experts ensure application availability, reliability & new application developmentMake changes in monthsMake changes in monthsMake changes in weeks or daysMake changes in weeks or daysBusiness AnalystInformation AnalystApplication DeveloperFunctional TesterIntegration TesterBusiness AnalystPerformance TesterIT Systems AdministratorIBM ODM Technical Presentation IBM 2012 Simple Decision Artifacts Supporting Complex DecisionsRule Flows11 IBM ODM Technical Presentation IBM 2012 Why Operational Decision Manager ?

5 Operationalize policy changes in days versus months Decrease cost of implementing business practices, policies & regulations Improve straight-through-processing Involve business users for change requests with built-in governance Implement more fine-grained, targeted decisions Perform what-if and impact analyses prior to deployment Automate and consistently enforce Decision policies Ensure policies and associated semantics are consistent across channels Track what decisions were made and why (runtime) Track what policies were changed and by whom (rule management)AgilityEfficiency and ProductivityDecision Quality and PrecisionConsistencyTransparency, Auditability, Compliance12 IBM ODM Technical Presentation IBM 2012 Achieve clearer line-of-sight to business operationsFoster cross-functional and cross-divisional outcomesAlign business operations with strategic intent in the face of changeBusiness Policies Built for Change vs.

6 Built to LastThe Consumerization of Change through Visibility, Collaboration and Governance Easily readable business rules in natural language Testing and simulation to assess impact of rule changes Rule versioning and snapshots to safely and reliably change rules Auditability of changes to ensure traceability Social media style UI to tap into organizational business expertise Single repository for business and IT users to collaborate13 Agenda What is Decision Management? Introducing IBM Operational Decision Manager business Decisions Defined Components, Architecture and Technical Dive ODM on z/OSIBM ODM Technical Presentation IBM 2012 IBM Operational Decision Manager To flexibly and reliably manage repeatable, automated decisions When decisions change frequently To increase straight-through processing When Decision services can be shared across systems To manage and govern large numbers of rules When real-time events require immediate actionsApply Operational Decision Manage business policies at scale Capture.

7 Automate and operationalize your business expertise Enable social collaboration to manage and govern business change15 IBM ODM Technical Presentation IBM 2012 IBM ODM Visibility New business interface to bring more visibility on how decisions are being changes across the teamDesigned to meet Decision management challenges Collaboration New social based communication capabilities to improve interactions across the business team Governance Enriched controls and governance capabilities simplifying version management at the rules and project level16 IBM ODM Technical Presentation IBM 2012 Full text search across all Decision assetsDecision Center What s New quickly displays deployed assetsSearch can return rules, tables and foldersVisibility Through Operational Decision Manager IBM ODM Technical Presentation IBM 2012 Collaboration Through Operational Decision Manager Center enables collaboration on assets of interest and change notificationsDetails on the Activity Stream in the New Features sectionIBM ODM Technical Presentation IBM 2012 Department 1 Timeline enables a quick view of version historyGovernance Through Operational Decision Manager Decision CenterDetails on the Timeline in the New Features sectionIBM ODM Technical Presentation IBM 2012 ModelValidateDeployMonitorBusinessAnalys tPolicy ManagerSystem AdministratorFull Decision Lifecycle ManagementManage changes in a safe and predictable environmentComplexDecisionsRule AdministratorDeveloperIBM ODM Technical Presentation IBM 2012 Why Operational Decision

8 Manager ? Operationalize policy changes in days versus months Decrease cost of implementing business practices, policies & regulations Improve straight-through-processing Involve business users for change requests with built-in governance Implement more fine-grained, targeted decisions Perform what-if and impact analyses prior to deployment Automate and consistently enforce Decision policies Ensure policies and associated semantics are consistent across channels Track what decisions were made and why (runtime) Track what policies were changed and by whom (rule management)AgilityEfficiency and ProductivityDecision Quality and PrecisionConsistencyTransparency, Auditability, Compliance21 IBM ODM Technical Presentation IBM 2012 Achieve clearer line-of-sight to business operationsFoster cross-functional and cross-divisional outcomesAlign business operations with strategic intent in the face of changeBusiness Policies Built for Change vs.

9 Built to LastThe Consumerization of Change through Visibility, Collaboration and Governance Easily readable business rules in natural language Testing and simulation to assess impact of rule changes Rule versioning and snapshots to safely and reliably change rules Auditability of changes to ensure traceability Social media style UI to tap into organizational business expertise Single repository for business and IT users to collaborate22 What is Decision Management? Introducing IBM Operational Decision Manager business Decisions Defined Components, Architecture and Technical Dive ODM on z/OSAgendaIBM ODM Technical Presentation IBM 2012 RulesEventsWhat is a business Decision ? Contextual DecisionsApplication, Process, Service invokes a specific Decision , passing information to be processed by the rules,The contextual rules process the information are form a resultOnce complete the Decision passes a result back to the Application, Process or Service to take action onCombination of contextual and/or time-based rule artifactsValidation Decision EligibilityCalculation Decision PricingClassification Decision Gold, Silver.

10 BronzeOccurrence of Decision If customer asks for 3 quotes in 24 hoursthenprovide 2% discount for immediate acceptanceMissing Events Decision If medical equipment eventis not receive every 1 hourthen send alert to medical staffSituational DecisionsSpecific situations are defined in event rules looking for specific known sequences which should be correlated from a real-time stream of the known sequence of rules matches a specific sequence of events, then either 1. This simple Decision takes some immediate Action 2. A synchronous Decision is invoked to do additional processing, prior to making a Decision and taking some ODM Technical Presentation IBM 2012 IFthe enterprise value of Customeris GOLDANDthe Loyalty of Customeris LOW THENthe personalization action is Call ELSEthe personalization action is email IFpast occurrences the Customerreturned a product in the last 2 months is more than 3 THEN classify Customeras a LOW LOYALTY CustomerIFthe Total purchases of Account> $2,500 THENthe enterprise value of Customeris GOLD= GOLD+ LOW LOYALTYB usiness Decision - ExampleA process or application is required to contact a customer.