BUSINESS RULES ENGINE
A Business Rules Engine as Dynamic as Your Business
A business rules engine separates business logic from your mission-critical applications in order to gain agility and improve operational performance. To get the most benefit from this application architecture, you need a business rules engine that:
- Empowers business users to create and manage business rules with minimal involvement from IT staff.
- Supports sophisticated, powerful rules that can capture your business workflow and your policies and procedures in all their dynamic complexity.
- Integrates seamlessly with your existing IT assets and scales for enterprise-class performance.
Azstrel is the acknowledged leader in enterprise business rules and business process management solutions.Azstrel has long been an innovator in business rules logic and automated decisioning. For dynamic enterprises striving for greater operational efficiency and effectiveness, we offer our business rules engine either as part of a stand-alone business rules platform, or as a core element in our industry-leading business process management platform.
Azstrel business rules engine puts business users firmly in charge of creating and managing business rules, for maximum agility. Usability features include:
- Intuitive HTML rule forms to easily configure and manage business rules.
- An MS Visio graphical front-end to link rules with applications.
- Built-in review and approval processes.
- A version-controlled rules inventory that supports the efficient reuse of existing rules.
- A secure audit trail for all rules changes.
- Automatic documentation generation.
The Azstrel business rules engine is unmatched in its support for a wide range of rule types, including:
- Process rules that automate workflow management.
- Decisioning rules of all types, including decision tables, decision trees, and decision maps.
- Declarative rules that compute values based on detected changes in other related values.
- Transformation rules that appropriately transform data as it passes across heterogeneous systems.
- Integration rules that determine the right system to invoke in each situation.
With the Azstrel business rules engine, distributed application nodes can share a common rules database, for optimum scalability. The system employs an open Java and XML architecture, and runs on any major operating system, in conjunction with any major application server. Some of the largest corporations in the world run enterprise-scale business transformation programs that utilize the Pega business rules engine.
A business rules engine is a software system that executes one or more business rules in a runtime production environment. Rule engines typically support rules, facts, priority (score), mutual exclusion, preconditions, and other functions.
Rule engine software is commonly provided as a component of a business rule management system which, among other functions, provides the ability to: register, define, classify, and manage all the rules, verify consistency of rules definitions ,define the relationships between different rules, and relate some of these rules to IT applications that are affected or need to enforce one or more of the rules.
In any IT application, business rules change more frequently than the rest of the application code. Rules engines or inference engines are the pluggable software components that execute business rules that have been externalized from application code as part of a business rules approach. This externalization of business rules allows the business users to modify the rules frequently without the need of IT intervention. The system as a whole becomes more adaptable with business rules that can be changed dynamically, although QA and other testing would still be required.
There are a number of different types of rule engines. These types (generally) differ in how Rules are scheduled for execution.
Most rules engines used by businesses are forward chaining, which can be further divided into two classes:
- The first class processes so-called production/inference rules. These types of rules are used to represent behaviors of the type IF condition THEN action. For example, such a rule could answer the question: "Should this customer be allowed a mortgage?" by executing rules of the form "IF some-condition THEN allow-customer-a-mortgage".
- The other type of rule engine processes so-called reaction/Event Condition Action rules. The reactive rule engines detect and react to incoming events and process event patterns. For example, a reactive rule engine could be used to alert a manager when certain items are out of stock.
The biggest difference between these types is that production rule engines execute when a user or application invokes them, usually in a stateless manner. A reactive rule engine reacts automatically when events occur, usually in a stateful manner. Many (and indeed most) popular commercial rule engines have both production and reaction rule capabilities, although they might emphasize one class over another. For example, most business rules engines are primarily production rules engines, whereas complex event processing rules engines emphasize reaction rules.
In addition, some rules engines support backward chaining. In this case a rules engine seeks to resolve the facts to fit a particular goal. It is often referred to as being goal driven because it tries to determine if something exists based on existing information.
A third class of rules engine might be called a deterministic engine. These rules engines may forgo both forward chaining and backward chaining, and instead utilize domain-specific language approaches to better describe policy. This approach is often easier to implement and maintain, and provides performance advantages over forward or backward chaining systems.