1. Expand Your Solution Offerings with Corticon Business Rules Management
AMERICAS PUG CHALLENGE
Dr. Mark Allen Chief Technology Officer, Decision Management Founder and Former CEO, Corticon Technologies

2. Introduction to Business Rules Management
Agenda
Introduction to Business Rules Management
What Is Business Rules Management?
The Business Rules Management Problem
The Corticon Solution
Corticon Customer Success
Corticon Differentiation
Corticon Demo
Corticon and OpenEdge
Summary & Q&A

3. What Is Corticon Business Rules Management?
Software to Help Make The Right Decision at The Right Time With Business Agility
Should we pay this claim?
What offer should we make, now?
What resource should we allocate?
Guidance:
1. Customize list of decisions for your client
2. Engage with client in a discussion of the value of making the right decision, at the right time, with agility. For example, you can tell one or more of the following stories:
claims adjudication – consider our customer Cigna, who are modernizing their healthcare claims system with Corticon
Right decision – impacts profitability and customer satisfaction. Paying invalid claims is a waste of money. And, denying valid claims upsets our customers.
Right time – also impacts profitability and customer satisfaction. It’s well known in the industry that the faster you pay a claim, the lower the overall claims loss
Agility – ability to quickly respond to new fraud tactics, or implement new policies quickly
Making the right offer – consider our customer Turkcell
The right decision is not only the offer the customer is most likely to accept, but also the offer that is most profitable, and that is inventory, and that is compliant with regulation
The right time can dramatically impact uplift, or the likelihood the customer accepts. Turkcell reported that, when they make offers at the right time, they see a 10x uplift. An example is that they make an offer for more minutes to a customer with a pre-paid plan, immediately after they hang up the phone, if they are low on minutes.
Business agility is key because marketing folks are constantly conceiving new campaigns, based on success of current campaigns, inventory, market factors
Fraud – Consider our customer DBS Bank, the largest bank in Singapore, who were hit with ATM fraud. Through traditional BI, they were able to identify patterns. For example
NOTE: Eventually, I would like to build these out into slides with nice graphics.

4. What Is Business Rules Management?
Decisions are governed by business rules
DECISION
RULE
Should We Pay This Claim?
Reject Claims with invalid billing codes
BRMS – Business Rules Management Systems (a.k.a. rule engines) externalize decision logic from applications and represent as business rules
Rule
Claims Management System
BRMS

5. The Problem: Automating Business Rules
Traditional approach is programming based
Simple rules difficult to automate, sophisticated ones impossible
Single change can impact hundreds of rules/processes
Policies
Regulations
Consumer Behavior
Market Shifts
Competition
Fraudsters Adapting
“That change requires 2 years & $5M”
There Is a Better Way…
© 2011 Corticon Technologies, Inc. All rights reserved. - Confidential

6. The Solution: Progress Corticon Business Rules Management System
Separate decision logic from code
Empower business users
Ensure performance & scalability
Enable fast, safe changes
Decision Modelers
Enterprise Systems
Enterprise Data Sources
Execute as Open Standards Decision Services
Model Rules with Integrity
The same decision service can be deployed and executed in a number of technical architectures:
It can be run in the native process of the application, directly in Java or .NET
It can be called as a step in a transaction process or workflow as a SOAP Web Service
It can run in a high performance batch process, directly against a database
It can be triggered by our CEP engine, upon identification of a relevant event
Rules Engine
Business Rules Management
Decision Management

7. Introduction to Business Rules Management
Agenda
Introduction to Business Rules Management
What Is Business Rules Management?
The Business Rules Management Problem
The Corticon Solution
Corticon Customer Success
Corticon Differentiation
Corticon and OpenEdge
Summary & Q&A

8. Progress Corticon: 500+ Customers
INSURANCE
FINANCIAL SERVICES
Financial Services
GOVERNMENT
Federal Government
HEALTH & HUMAN SERVICES
Health & Human Services
eCOMMERCE
Insurance
eCommerce
FBI
OPM
DIA
State Department
© 2011 Corticon Technologies, Inc. All rights reserved. - Confidential

9. Progress Corticon: Key Use Cases
Commerce (Sales & Marketing)
Apply – Price/Quote – Recommend – Police
Customer Servicing
Intake – Validate – Adjudicate – Recover – Fraud
Manufacturing & Supply Chain
Production Planning – Resource Allocation – Logistics
Distill key repeat use cases
Enterprise Rules Management
Decision Analytics as a Business & IT Discipline

10. Corticon Case Study: Online Insurance Sales
Complete Application
Underwrite Application
Quote & Recommend
Close Sale
Generate Policy Docs
Rules-Driven, Web-Based Questionnaire
Automated Underwriting and Product Recommendations
Automated Generation of Custom Policy Documentation
Powered By Corticon Business Rules Management System (BRMS)

11. Grow revenues thru new sales channel
Streamline process from days to minutes
Rapidly respond to changes in market direction 11

12. Corticon Case Study: Claims Processing
After
Corticon
7 Manual Steps
Before
Corticon
21 Manual Steps
Accelerate Service Delivery
Reduce Costs
Improve Service Quality
Improve Agility

13. HOW CAIDAN MAKES PROGRESS
CHALLENGE:
Expand healthcare claims processing business into new states and keep up with changing regulations as HIPPA and the Affordable Care Act (“Obamacare”).
SOLUTION:
Use Progress Corticon BRMS to modernize existing OE architecture.
VALUE:
Empower healthcare domain expert to manage volatile decision rules outside of the OpenEdge ABL.
Accelerate application customization covering the needs of each customer as well as state/local regulatory schemes.

14. Executing Manufacturing Process Excellence
Market Segment:
Application:
Manufacturing
Production Planning System Development
Complete system re-engineering and replacement to:
Increase flexibility and agility in manufacturing process
Accommodate a wide range of ever-changing commercial and production rules
Corticon chosen because:
Accelerated application development and maintenance
Increased business transparency and control – rules managed by industrial engineers
Ease of integration
See:

15. Next Generation eCommerce
Online marketplace
Market Segment:
Application:
World’s largest online marketplace
Corticon used in next generation eBay marketplace
Corticon selected over in-house rules engine, IBM Ilog, and open source due to:
Scalability to millions of transactions per day
Guaranteed rule integrity
Speed of development
Processing >40M transactions per day, <10ms per transaction

16. Claims Processing with BPM
Market Segment:
Insurance
Asset Damage (Property & Casualty)
Application:
One of the world's largest life insurance and pension companies with millions of customers worldwide
Considerable cost and FTEs reductions as result of straight-through processing
Improved customer satisfaction (quicker claims handling)
Less IT dependency, domain experts owns content and change process
Staying compliant and consistent with government regulations
Straight-through processing (STP) achievement circa 85%

17. Introduction to Business Rules Management
Agenda
Introduction to Business Rules Management
What Is Business Rules Management?
The Business Rules Management Problem
The Corticon Solution
Corticon Customer Success
Corticon Differentiation
Corticon and OpenEdge
Summary & Q&A

18. Progress Corticon BRMS Recognized Market “Leader”
Corticon has breakthrough tools for business analysts.
Corticon positioned as Leading Innovator in Gartner Magic Quadrant
Corticon has developed breakthrough technology in the BRMS market.
© 2011 Corticon Technologies, Inc. All rights reserved. - Confidential

19. Corticon Differentiation
Model-driven Development
Automate rules without coding
Guaranteed Rules Integrity
Ensure safe changes
DeTI engine
Market-best performance and scalability

20. Model-Driven Rules Development
Vocabulary consists of your business objects/terms
Out-of-the-box ready for use by
Business Analysts
IT Professionals
Patented Excel-like modeling tool
No programming
Business friendly
One-click deployment
Rules are constructed with drag-and-drop ease
Comprehensive, extensible library of operators (akin to Excel functions)
Rule Statements provide rule documentation and traceability
Proven with the most sophisticated business problems

21. Corticon Studio Demonstration
New Insurance applicant
Validate Information
Determine Risk Profile
Calculate Premium
Route for Approval
Identify the Business Decision Ask: What decision is being made?
What is the applicant’s risk profile?
Sample Rules
Applicants who skydive have a High Risk rating
Applicants under 35 have a Low Risk rating
Identify the Business Rules Ask: How do you make the decision?
Model the Business Rules Use: Corticon Studio

22. OpenEdge Coding: 35 Lines of Code for 4 Business Rules
DEFINE INPUT PARAMETER isSkyDiver AS LOGICAL NO-UNDO.
DEFINE INPUT PARAMETER applicantAge AS INTEGER NO-UNDO.
DEFINE INPUT PARAMETER parmCurrency AS CHARACTER NO-UNDO.
DEFINE INPUT PARAMETER parmAge AS INTEGER NO-UNDO.
DEFINE INPUT PARAMETER parmIncome AS INTEGER NO-UNDO.
DEFINE OUTPUT PARAMETER ruleStatement AS CHARACTER NO-UNDO.
DEFINE VARIABLE riskRating AS CHARACTER NO-UNDO.
DEFINE VARIABLE totalPremium AS DECIMAL NO-UNDO.
IF isSkyDiver THEN
DO:
ruleStatement = "Warning" + CHR(1) + "Applicants who skydive have a high risk rating regardless age." .
riskRating = "High".
totalPremium = 150.
ruleStatement = ruleStatement + CHR(3) + "Info" + CHR(1) + "Applicants who are " + riskRating + " risk pay a premium of " + parmCurrency + STRING(totalPremium) + "." .
RETURN.
END.
ELSE
IF applicantAge < parmAge THEN
ruleStatement = "Info" + CHR(1) + "Applicants less than " + STRING(parmAge) + " years of age have a low risk rating." .
riskRating = "Low" .
totalPremium = 50.
ruleStatement = "Info" + CHR(1) + "Applicants who are " + STRING(parmAge) + " year or older and don't skydive are medium risk." .
riskRating = "Medium" .
totalPremium = 100.
ruleStatement = ruleStatement + CHR(3) + "Info" + CHR(1) + "Applicants who are " + riskRating + " risk pay a premium of " + parmCurrency STRING(totalPremium) + "." .

23. Model-Driven Rules Development
Traditional Approach
Often contains errors and performance issues
Design
Specify
Test
Integrate
Deploy
Templates
Code
Reduce development
and change cycles
by 90%
Higher quality, higher performance, agility
Model
Integrate
Deploy
Corticon Approach
Requires Technical Resource

24. Benefits of Model-Driven Rules Management
Sample ROI Analysis* – Automation of single, decision-making task
1st Generation
Corticon
Initial Development
Analyze
20 hours
Prepare - Design
5 hours
N/A
Prepare - Implement
200 hours
2 hours
Total
225 hours
22 hours
10x
Improvement
Change Cycle
Analyze
15 hours
0.5 hours
Prepare - Design
7 hours
N/A
Prepare - Implement
28 hours
1.5 hours
Total
50 hours
2 hours
25x
Improvement
*Per NCAA customer testimonial. See webinar: Extreme Agility: Achieving 25x Acceleration in Business Cycles with Model-Driven Business Rules Management

25. Guaranteed Rules Integrity
Debugging rules is a major issue with traditional rule development
Corticon identifies logical errors during requirements specification
Most Errors
Introduced
Most Errors
Detected

26. Corticon 5 Difference – Engine Performance
Traditional pattern matching algorithm is Rete
Scales well with increasing number of rules
Degrades exponentially with increasing complexity of data
– the “Rete Wall”
Corticon’s patented DeTI (Design Time) algorithm
Scales linearly with number of rules and complexity of data
© 2011 Corticon Technologies, Inc. All rights reserved. - Confidential

27. Corticon vs. Drools Progress’ Performance & Scalability Tests
Scalability for increasing fact
JBoss
Drools
Corticon
BRMS

28. Introduction to Business Rules Management
Agenda
Introduction to Business Rules Management
What Is Business Rules Management?
The Business Rules Management Problem
The Corticon Solution
Corticon Customer Success
Corticon Differentiation
Corticon and OpenEdge
Summary & Q&A

29. OpenEdge Application Architecture
Physical Schema (Tables)
Client Logic
Application Logic
(ABL)
Abstract Schema
(ProDataSet/ temp-table & Vocabulary)
Application Infrastructure Logic
(ABL)
Business Logic
(Corticon & ABL)
Volatility:
Low
Med
High

30. Why Use Corticon?
Puts volatile decision logic in hands of business (domain experts instead of just IT)
Allows decisions to be managed in a separate tier with a more agile lifecycle – separation of system and business logic
Accelerates logic development time and reduces maintenance time
Reduces volatility of ABL logic and dependence on ABL experts
Improves ease of use through good visual tooling
Build vocabularies and rules declaratively through a model driven approach
Improves application quality
Gaps & overlap analysis – prevent technical inconsistencies
Use case testing on the fly

31. Choosing Between ABL and Corticon
Is the business logic the result of relatively complex decisions?
Is the business logic customized by the client?
Are changes frequently required to the application’s business logic?
Is quality / integrity of logic critical?
Is the business logic the result of relatively complex decisions? Are there many IF-THEN-ELSE blocks and/or CASE statements in the code, relating to setting relatively few, or even just a single, flag or field value(s)?
Is the business logic customised per customer or tenant (in a multi-tenant model), and who determines the changes in the business logic? If changes are made on a per-industry basis (eg. income tax tables, for example) it’s more likely that all customers of an application would require an update; if changes are made per-customer (eg. life insurance risk weightings) then the scope of the changes required are limited to that customer.
How frequently are changes required to the application’s business logic, particularly relative to the application vendor’s release schedule? If business logic changes are relatively infrequent, and releases are relatively frequent, then customers may benefit from the vendor’s development and testing expertise, and not have to perform those actions themselves.
Business analysts and/or business domain experts are readily available at a customer site, but are non-technical.
The more “yes” answers, the better the fit for Corticon!

32. Progress Corticon and OpenEdge
Products Integrated Today
Integration White Paper Available
Integration Options
Web Services Call-Out (Decision Points) – via ABL and OE BPM
Requires OE 10.2 or greater
OE 11.3 Integration Productivity Features
ABL API/macros to eliminate integration code
Shared Data Model
Direct Integration with OpenEdge Database (Batch Processing)
Improved OE BPM Integration

34. Summary Better, faster decisions by automating business rules
Client Benefits:
Mitigate Risk
Optimize Operations
Find New Revenue Opportunities
Better, faster decisions by automating business rules
Patented “no-coding” rules engine
IT Benefits:
Accelerate Rate of Change
Empower Business Users
Ensure Performance and Scalability

35. Learn More / Download Evaluation Software
Contact Details
Mark Allen -
Learn More / Download Evaluation Software
Change color

36. V11.3 Functionality (OE + Corticon)
Simple, fast ABL API
Simple API that hides most if not all complexity
Allows ABL application to reuse existing data structures as inputs/outputs (ProdataSets, Temp Tables)
API hides transport (currently XML payload)
V11.3 Contains following ABL macros:
BR-CONNECT: Establish Decision Service Connection
BR-INVOKE: Invoke Decision Service (Connection Parms, Service Name, Version)
BR-GETMSG: Call Get Rule Messages

37. V11.3 Functionality (OE + Corticon)
Shared Data Model Shared Definition of Vocabulary That Rules Operate on: import Schema definitions, ProDataSets & Temp tables as Corticon vocabulary Entities
Export Temp Table or Prodataset to create a
Corticon vocabulary from Progress Developer Studio

38. V11.3 Functionality (OE + Corticon)
Shared Data Model (continued)
1. Select from Temp Table or Prodataset the business entities (data structures) to export
2. Save to an intermediary business rules vocabulary file (.brvd)

39. V11.3 Functionality (OE + Corticon)
Shared Data Model (continued)
Store your rules vocabulary folder location preference

40. V11.3 Functionality (OE + Corticon)
Shared Data Model (continued)
In Corticon Studio import the .brvd file.
This will create your Corticon vocabulary.

41. V11.3 Functionality (OE + Corticon)
Direct Integration with OpenEdge Database (Batch Processing) Direct OE database access via JDBC for batch processing using the Corticon High Performance Batch Processor (HPBP)
Data retrieval from OE fully delegated to HPBP Retrieves data in configurable chunks and sends multiple requests to Corticon Server concurrently
Corticon Server spins up multiple decision services (reactors) to process load. Massively scalable, ultra fast data processing based on rules
Java Runtime
OE Database
Corticon Server (Rule Execution)
Batch Processor
Hibernate Data Classes
Multi-threaded In-process
Request
Response
Corticon Studio (Rule Modeling)
Multi-threaded
Retrieve Data (JDBC)
Update Data
(JDBC)

42. V11.3 Functionality (OE + Corticon)
Improved OE BPM Integration
From BPM, use an OE Managed Adapter
OE Managed Adapter calls ABL  Use Business Rules macros:
BR-CONNECT : Establish Decision Service Connection
BR-INVOKE: Invoke Decision Service (Connection Parms, Service Name, Version)
BR-GETMSG: Call Get Rule Messages