The Savant Business Rule Engine provides a framework to abstract guidelines, policies, regulatory information and general expertise related to your business environment onto a separate layer, where these business artifacts can be managed by the people that specify them in the first place. In brief, the Savant Business Rule Engine delivers the ability for continuous change; change that is smooth, quick, cheap and effective.

Salient Features of the Savant Business Rule Engine

• Based on the Event-Condition-Action (ECA) model
• Capable of acting independent of other datrics products
• Easy definition, modification and management of rules; fine-grained control in rule definition and execution
• Recursive rules support
• Change auditing : capability to rollback definitions to a previous point-in-time
• Support for multiple rule engines
• Synchronous/Asynchronous application call support
• Platform-independent Java product
• Optimum performance for large and growing number of rules
• Capability to scale dynamically based on load levels

Click to Enlarge

Components

• Rule modeler : Rule modeler is the Graphical User Interface (GUI) where users define and deploy Events and related rules.
• Rule repository : The rules defined by users are stored in this persistence layer.
• Event Manager : This is the runtime engine that listens for events, manages them on receipt and responds to calling applications.
• Rule Engine : This runtime engine is the core module, that applies Business Rules from the Rule Repository based on the events that the Event Manager passes to it.

Benefits to the Business:

• Consistency : The abstraction of business rules ensures their consistent application throughtout an enterprise; and change applied at one point is reflected in operations everywhere.
• Pace : The need to change one or more applications' code whenever a policy change occurs is eliminated, thereby reducing the time consumed in applying a patch, testing it, and then deploying it.
• Cost : The policy changes are applied by a business user, avoiding the entire Requirements-Design-Analysis-Development-Test-Deploy cycle, which is invariably expensive and error-prone, due to the number of different people possibly involved in the chain.
• Centralization : The process of abstracting Business Rules to a single repository centralizes knowledge that otherwise resides in various forms and locations, like the expertise of managers or employees, existing application code, policy manuals and other such documentation.