Browse Prior Art Database

(ISC) Optimizing Business Processes By Using Business Rules Inference Engine

IP.com Disclosure Number: IPCOM000124925D
Original Publication Date: 2005-May-13
Included in the Prior Art Database: 2005-May-13
Document File: 5 page(s) / 37K

Publishing Venue

IBM

Abstract

This invention will enable for a more optimum process of rule creates/updates with the following capabilities: (1) Allow authorized users to add/update/delete a rule or set of rules through a GUI On-Demand. (2) Provide with a common repository of rules which allows complete information sharing across all IBM the existing systems in the GEOs with enhanced accuracy and minimized duplicity. (3) Ability to perform impact analysis based on a required rule change with reduced application coding (Try for fit capability).

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 54% of the total text.

Page 1 of 5

(ISC) Optimizing Business Processes By Using Business Rules Inference Engine

    Customer Coverage is set up at the beginning of the year, and periodically during the year a country may wish to change the rules used to match customers to the coverage model. At present, when coverage is being set up for the new year, the process is executed in a temporary environment into which data has been copied. From the time the data is copied, until the new year begins, the data becomes stale and may not be a valid representation of the customer mix. In addtion, for the year start up process and each time a country changes it's rules, there is an iterative process requiring human intervention on the part of a development and operations organizations.

Today's environment has the following characteristics:

New changes to customer rules are sent to the operations team as *.123 or *.txt files, which does not allow the countries/GEO operators to do the changes directly via a graphical user interface.

There is not a business rule system that shows the rules in an English like format in a common place so that any interested party can take a look at them at any time. Existing rules are limited to a GEO - No open sharing between data sources and probable duplicity of a rule.

Rule changes are done based upon immediate need not by analyzing the overall impact on the solution.

For any rule change, there is the involvement of development and operations teams in addition of the country/GEO operators. With the enablement of this invention the following is achieved:
Rules changes are done On Demand 24 hrs a day 7 days a week Rules exist in a common repository which allows for data accuracy, minimization of data duplicity and standardarization of rules shared across all systems and open systems.

Remove the human intervention from the process of applying rules to the production environment and allow the users to validate rules submitted using production data. This will allow the user to:

    - Detect and explain potential rule conflicts and redundancies prior to production move.

    - Perform impact analysis on the rule change before it gets deployed. - Correct any other error associated to a rule change before it is moved to production.

     This invention has the following 3 busines processes: (1) Rule Create/Update Process, which describes how the use adds, creates, and updates rules via an automated rules engine 24/7 OnDemand. This process is depicted in depicted in Figure
1. (2) Rule Delete Process, which describes how the user deletes rules also using the inference engine. This process is depicted in Figure 2. and (3)Try for Fit, which describes the process of testing the rule before it is actually deployed in the production environment. The try for fit process is driven by the an inference rule, and it is a sub-process and at the same time a necessary step for both for both the create/update and delete processes.

1

Page 2 of 5

     For all the three processes a...