Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

European Business Rules Conference 2005 : Rule Standards


Published on

Overview of the need for rule standards and the efforts that are underway.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

European Business Rules Conference 2005 : Rule Standards

  1. 1. Rule Standards ILOGDaniel Selman, Product Manager
  2. 2. Agenda • The problem space • The compliance use case • Conclusions Copyright © 2005 by 2
  3. 3. Traditional Software and Change … are incompatible Internal process Competition Regulation Market Crisis Business Software Change is guaranteed Copyright © 2005 by 3
  4. 4. Dynamic Markets • Mergers and Aquisitions • Industry regulation • BASEL, HIPAA, SOX etc. • From governments • From trade regulatory bodies • Trading partner exchange • Telco local carriers • Regional offices • Affilates • Franchises • Parts supply, complex orders • Personal privacy rules? Copyright © 2005 by 4
  5. 5. Complex Deployments Indirect Channels Front-Office Across Applications Across Touchpoints Direct Sales Middle-Office Self Service Back-Office Direct Mail Call Center Accounting E-mail @ JRules Mobile Other Applications Copyright © 2005 by 5
  6. 6. Business Benefits of Business Rules Reduced IT labor costs Impact Business Value Business Agility • Faster reactive and proactive time to market • Business users empowered to create & manage rules previously hard-coded Decision Making • Test rule-based scenarios at lower cost Revenue Opportunities • Greater product pricing and service flexibility allowing incremental revenue streams Customer Satisfaction • More customizable service offerings Regulatory Compliance • Greater visibility to regulatory bodies and easier change processes Source: Gartner Research Copyright © 2005 by 6
  7. 7. Compliance Automated Controls Internal Policies Automated Controls ILOG Compliance  Fraud Detection Solution Accelerator Reference code Rules Templates  Financial controls Object Model Add-ons Project Mgt Resources  Data cleansing Professional Services Reference Technical Guidance Architecture  Forms/Transactions Validation Project Plan Template Application Integrations ooT gn py o o P d pa R CRM, ERP EAI, BPM i t t r i  Data Validation & routing DB and OS/ Abstraction RDBMS JDO / JCA Application Specific Codel ILOG Products  Eligibility Regulations (HIPAA, SOX, Patriot Act, IAS, etc.) Copyright © 2005 by 7
  8. 8. Automated Controls Usage Scenario Enrich or clean Data Manual Processing Automated Control Data Validation Events and Cases Exceptions Report Copyright © 2005 by 8
  9. 9. Compliance Rule Templates Case handling rule sample Policy rule sample Copyright © 2005 by 9
  10. 10. Compliance Architecture Rules Compliance Rules RulesManagement Rules Repository Reporting Console Edition XML Compliance Events Web Report Middleware Data source Compliance XML Rules Compliance XML Data Engine Case Web Forms Modified Middleware Data Data source Reference Input Data Output Copyright © 2005 by 10
  11. 11. Business Rules Standardisation Status and ILOG involvement • Modelling BR: standardisation activities at OMG • Production Rules Representation meta-model • Drafted by Fair Isaac (editor), IBM, ILOG, LibRT, Pega Systems (joined Nov. 05), RuleML • Business Rules Management meta-model • Decision to issue RFP pending • Business Semantics of Business Rules meta-model • ILOG monitors the activity; not actively involved in drafting the meta-model • Executing BR: standardisation activities within the JCP • JSR 94 (Java API for Rule Engines) released in August 04 • Integrated by SUN into the JDK; now in maintenance mode • Daniel Selman (ILOG) is the current specification lead • Sharing and exchanging BR: standardisation activities at WC3 • ILOG hosted and co-chaired W3C workshop on Rules Languages for Interoperability • 27-28 April 2005, Washington, DC • First step towards a Rules Representation activity in the W3C Copyright © 2005 by 11
  12. 12. Conclusions • Strong standards will… • Drive industry adoption – particularly in govenment • Simplify deployments • Promote vendor competition • Enable rule/policy exchange • Create a 3rd-party tools market • But… it is a difficult problem! • PRR is making good progress Copyright © 2005 by 12