The document provides an overview of a Business Rules Management System (BRMS). It discusses that a BRMS allows non-technical business users and technical developers to define and manage decision logic. This improves efficiency, reduces costs, and enables faster response to changes. The document also outlines the components of a BRMS, including a repository to store rules external to applications, tools for defining rules, and a runtime to execute rules.

1. BRMS BASICS
Session By
Karthikeyan S

2. AGENDA
• Why BRMS?
• What BRMS is?
• How BRMS Impact?

3. Why BRMS?
Reasons:
• Lower cost of ownership for software development life cycle
• Faster application development
• Faster response to change
• Reusability of work
• Advanced Personalisation

4. February 25, 2017 4
Managing Change Across the Organization
Production
IT Administrator
System/Ops Manager
Line of Business
Business Partner
Policy Manager
Line of Business Manager
Development
Rule Developer
Rule Modeler
Business Analyst
I need performance,
scalability, monitoring and
reliability of operations
I need easy,
efficient and reliable
policy change delivery
I need a
comprehensive rules
development and
maintenance
environment

5. What BRMS is?
• Business Rule Management System is a software system used to define,
deploy, execute, monitor and maintain the variety and complexity of
decision logic
A BRMS includes, at minimum:
• This needs to be attributed:
• A repository, allowing decision logic to be externalized from core
application code
• Tools, allowing both technical developers and business experts to define
and manage decision logic
• A runtime environment, allowing applications to invoke decision logic
managed within the BRMS and executes it using a business rules engine

6. How BRMS Impact?
Major Themes of the Business Rules Approach
Non-technical origins
• As per BRCommunity ,Business rules did not emerging new class of
software tools. Rather it came to deal real-world, grassroots movement
whose driving force is business practice, not technology.
• It arose from the vision of dedicated professionals with many years of
experience in the trials and challenges of business software.
• Goal: to offer companies the best possible approach to developing
business solutions involving automated systems.
Terms, facts, and rules
• This important breakthrough, sometimes called the Business Rule Mantra,
is credited to the GUIDE Business Rules Project and was originally reported
in its 1995 paper
• Literally, in the business rule approach, rules always build directly on facts
(or fact types), which in turn always build on concepts, as represented by
terms.

7. Fact models
• This term actually refers to the structure of basic
business semantics — that is, terms that stand for concepts and
how they relate to one another in the form of facts.
Level of enforcement
Declarative form of enforcement.
Atomic form
• The word atomic appears explicitly or implicitly in several of the
definitions. This reflects an important goal for business rules to
achieve the most granular level of specification possible.
Reusability
Structured Business-level Rule Syntax
Rule Verification and Management
• This enables verifying the consistency of rules and managing them
from a business, not software, perspective

8. The advantages of a BRMS include:
•Reduced or removed reliance on IT departments for changes in
live systems. Although, QA and Rules testing would still be needed
in any enterprise system.
• Increased control over implemented decision logic for compliance
and better business management
• The ability to express decision logic with increased precision,
using a business vocabulary syntax and graphical rule
representations (decision tables, trees, scorecards and flows)
•Improved efficiency of processes through increased decision
automation

9. Where Business Rules Typically Exist
Applications
ProcessesPeople
Documents
Business Rule Management System
Rules are
Defined,
Analyzed and
Maintained
User Tools
Rules are
Stored and
Shared
Rule Repository
Rules are
Deployed,
Executed and
Monitored
Rule Server
February 25, 2017 9
The Smarter Approach – Easy, Safe, Reliable Change with BRMS
 Make decision logic accessible to Business and IT
 Allow business users to manage rules
 Implement fine-grained, context-specific decision automation
 Reduce maintenance time/cost

10. February 25, 2017 10
Redefined Application Change Cycle
DeveloperBusiness - IT
Weeks / MonthsDays / Weeks
Functions /Tasks / FlowDecisions / Policies

11. Model
Author
Validate
Test
Deploy
Execute
Monitor
Analyze
Business
Analyst
Developer
Policy Manager
Rule Administrator
System Administrator
Enterprise
Rule Repository
February 25, 2017 11
WebSphere ILOG BRMS – Full Rule Lifecycle Support

12. Business Rule Language
 Supports all kind of rules:
 Basic to cross validations
 Derivations
 Inference based rules
 Calculations rules
 Product offering
 Underwriting
 Scoring
 Rating…
if
the credit score of the borrower is less than 200
then
add "Credit score below 200" to the messages of the loan
reject the loan;
if
the type of claim is Veterinary cost
then
Processing type for claim is : Automate
else
Processing type for claim is : Manual
 Customizable vocabulary specific to your
organization, industry, application (etc.)
 Supports language localization
 Integrates with external data sources (e.g. list
of countries)
 Drop down lists for customized domain data
 Templates facilitate new rule creation
February 25, 2017

13. “customer”
• the name of …
• the birthday of …
• the number of accidents of
…
• the … is a high risk driver
• …
Business Object Model Rule Vocabulary Business Rule Language
Developer IT / Business
Rule Developer /
Business User
“client”
• le nom du ...
• l’anniversaire du ...
• Le nombre d’accidents du ...
• le ... est un conducteur à
risque
• …
CustomerInfo
• name
• birthday
• getNumAccidents()
• isHighRiskDriver()
• …
Rule: High risk driver
if
the birthday of customer is after 12/9/1975
and
the number of accidents of customer is at least
3
then
set the customer as a high risk driver
Règle: Conducteur à risque
si
L’anniversaire du client est après le 12/9/1975
et
le nombre d’accident du client est au moins 3
alors
Classer le client comme conducteur à risque
 Automatic generation
of the rule vocabulary.
 Comprehensive industry
focused business terms
to define its data and
associated actions.
 Localizable vocabulary
February 25, 2017
Rule Editing with Domain Specific Languages

14. February 25, 2017 14
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
•Offer Configuration
•Order Management
•Fraud Detection and
Management
•Loyalty Programs
•Network Monitoring
Transportation
and Travel
•Promotions
Management
•Loyalty Programs
•Customer Service
•Billing
•Contract
Management
Retail
•Online
recommendation
•Campaign
Management
•Order Management
•Pricing
Manufacturing
•Order Management
•Billing
•Contract
Management

15. References
Non-Commercial Websites
• www.BusinessRulesGroup.org, launched in 2000.
• www.BRCommunity.com (home of The Business Rules Journal), launched
in 2000.
• www.brportal.org a German-speaking web portal launched in April 2004.
• European Community of BRCommunity.com launched in 2004.

16. QUERIES???
 

17. THANK YOU!!!!
