Business Rules engine backdrop

VisiRule Business Rules Engine

Graphical Business Rules Engine

VisiRule provides a robust Business Rules Engine accessible via a graphical decision modelling environment. Authors can create and deliver applications by drawing decision making charts.

 

Complex knowledge can be represented clearly and elegantly in decision tree software diagrams. VisiRule extends this by offering a dedicated English-like business rule language. Business Rule Engines & Management Systems naturally separate business logic from executable code in order to gain agility and resilience.

VisiRule uses a logic-based Business Rules Engine which enables authors to separate business rule logic from application-specific code. Users can capture business logic visually without coding and implement changes independent of application specific code. This enables greater business clarity and higher degree of maintainability. When combined with RPA, this helps deliver Decision Automation & Intelligent Automation.

Business Rules Engines

Once a chart is completed, VisiRule Publisher will walk through and generate the rules to be executed by the underlying Business Rules Engine (BRE) along with the associated data access calls. The BRE is standards-based and easily integrated into most modern delivery environments and architectures using REST and JSON.


VisiRule encourages authors to represent business process models in a clean, graphical manner using logical expressions to control the execution flow. This enables business professionals to capture, share, discuss, test and automate their business's decision-making processes in a coherent and transparent way.

Business Rule Engines can be used in many parts of organizations, wherever there are clearly defined methods which underpin some decision process. Automation requires well defined rules and a dedicated Business Rules Engine to execute them.

8de7c3_b36221f456524410ac1b93523b22119a_
Insurance Business Rules ChatBot

Incorporating Machine Learning

By incorporating Machine Learning technology, VisiRule FastChart allows charts to be generated from data and then updated and annotated by human experts. Rules used to create the chart are inferred or induced using information gain and entropy.

VisiRule’s approach of "programming via flow charting” permits rapid prototyping and review, and greatly enhances the accurate capture and shared understanding of decision flows. The ability to represent complex decisions in layers enables the decision rules engine to make high quality, transparent decisions. 

Intelligent Automation & VisiRule Business Rules

Document Generation

VisiRule can create automated documents in various formats such as text, PDF, XML, HTML and RTF using the answers gathered and calculations computed in the session.

 

VisiRule can combine complex logic with conditional text selection and insertion.​

Documents can be created one at a time using say a chatbot or en masse via a data driven process.

Business-Rules-Engine-Proposal.png
Business_Rule_Engine_Generated_Policy_Document
Visualizing Business Rules Engine Analytics

Business Rules Automation

Popular target areas for rules-based automation include sales configuration and quotation, insurance underwriting and claims eligibility, financial loan evaluation, robo-advice and robo-lawyer, and also manufacturing and engineering scheduling and support. Business Rules Engines enable business rules software to run both interactively, i.e. "question and answer driven" or automated, i.e. "data-driven". VisiRule supports both, and provides a hybrid Digital Decisioning Platform.
 

Testing & Validation Framework

VisiRule provides a powerful testing framework so that you can see the effect of your rules in various different data-driven scenarios. Furthermore, by including a "compare test results" component, VisiRule AutoAudit also supports regression testing.

Business Process Automation

VisiRule can be used to model various tasks and drive them in an automated fashion using exposed end-points and shared payloads as found in Decision Engineering.

 

Modularity & Multiple Charts

To enable manageability and scalability, decision models can be split across multiple VisiRule charts and files. This means the development of large models can be shared between multiple authors. Individual charts can be developed and tested on their own, and then combined within a larger framework.

Business Rules Engine Rest API
self_assessment.pngBusiness Rules Engine Web Interface

VisiRule REST Services

VisiRule offers a REST API coupled with a JSON (JavaScript Object Notation) state. REST (Representational State Transfer) is widely adopted and relies on stateless, client-server, cacheable communications. JSON is a lightweight data-interchange format, easy for humans to read and write, and easy for machines to parse and generate. This means you can connect the reasoning capability of the VisiRule Business Rules Engine to a web-site to make decisions or automate processes. Indeed, the REST architecture can support interactive ChatBot delivery where required.
 

Windows Containers

You can deploy your VisiRule application using Windows containers. Containers provide the tools to organize and build micro-services. They wrap the VisiRule application up within in a complete file system that contains everything it needs to run:the code, run-time rule engine, system tools and system libraries. This guarantees that it will always run the same, regardless of the environment in which it runs. Containers can be deployed on-premises or as a hosted service.
 

High-Performance Rule Engine

The high-performance VisiRule rule engine is capable of handling over 100K rules in 1 minute on a 2 server installation. As more servers are commissioned, this increases.

Business Rules Engine Integration

VisiRule can be deployed within, and integrated with, a wide variety of programming languages and delivery frameworks such as .NET, Python, Java, Azure, REST, Redis, Json, Azure, JavaScript, ODBC, XML etc. The rules component stays the same, and is just packaged using a different wrapper.

Big Data Decision Making Engines

VisiRule can access data in almost any database system both RDMS (SqlServer, Oracle, MySQL, SAP, Access) and NoSQL such as Redis. VisiRule can receive data from spreadsheets (Excel), text files and remote devices (SCADA etc). VisiRule a Big Data Rules Engine. When coupled with tools such as Azure IoT Hub and the Azure Event Grid VisiRule can provide intelligent support for IOT.

 

VisiRule Mapper provides a UI to map questions on to fields in external tables, so that rather than be asked, they are answered by using existing data. Computed output can be sent back to the screen, uploaded to a server or written back into a database.

Explaining Your Decision-making

Each decision point leaves a marker. By collecting up all these markers, and the values used to determine them, it is possible to reconstruct the reasoning behind how a conclusion was reached based on the data used. VisiRule can produce a justifiable explanation for its decisions. This is essential to produce transparent and trustworthy systems. Contrast this to neural nets which can NOT offer explanations as to how a decision was reached and are very much an unaccountable 'black boxes'.

Decision Visualization & Decision Analytics

Each visitor leaves a footprint of their visit, the path they took, the answers used, rules fired and the conclusion reached. VisiRule collects these. You can visualize and analyze this traffic to gain insight into a chart's performance, and learn how to improve it based on actual usage.

8de7c3_6d791a724a6f4541a937c4b06dd8a05e_

Multi-layered Engine Architecture

VisiRule generates executable rules in terms of the Flex expert systems toolkit. Flex supports both forwards and backward chaining rules and uses an English like Knowledge Specification Language (KSL) and you can use this to define and invoke additional rules. Flex is built on LPA Prolog, a well established logic-based AI language, which supports meta-reasoning and backtracking across alternate solutions.

 

Extra AI-based Tools

Flex also supports frames, procedures, as well as, access to other programming languages such as Prolog, C#, Java, VB and .NET. This provides for a multi-layer development environment. The high-performance LPA Business Rule Engine plus  a wide range of rules tools makes full integration into back-end services easy, and provides a powerful Digital Decisioning Platform.

Single Choice Icon

Single Choice

Multi-Choice Icon

Multiple Choice

Text Input Icon

Text Input

Number Input Icon

Number Input

Wide Range of Question Types

Conditional Rules and Complex Expressions

Many automated Business Rules Engines only allow for simple rules, i.e. atomic tests. VisiRule provides a comprehensive set of logical operators which means the expressions and rules can be as simple or complicated as needed.

Powerful Maths and Logic Processing

VisiRule includes a powerful maths package and complete set of logical operators. This includes scientific maths functions and high-precision floating-point numbers. In addition, you can call code defined in other languages such as Python, C, etc. 

Text Processing

VisiRule includes a powerful package of text handling routines which enables you to parse, analysis and extract text from text fields and documents. 

FourExpertQuadrants.png

Separation of Application Code

Like most modern Business Rules Management Systems (BRMS), VisiRule separates the operational business rules from the application code. This separation means that Business Rules can be managed, updated and maintained more easily without needing to change any program code, and by non-technical staff rather than programmers. The rules are executed by a dedicated high-performance Business Rules Engine. The resulting systems are more robust, resilient and adaptable.

 

This separation empowers business users and means that those people involved in the business can define and validate their business processes. The resultant knowledge base is accessible to colleagues as VisiRule charts and Flex rules can be viewed and easily understood by all those involved with the business process.

Authoring of Executable Rules

VisiRule Author and VisiRule365 are dedicated rules capture and authoring tools aimed specifically at business users rather than programmers. VisiRule Author helps business professionals express the logic behind their decisions graphically. The charts are directly executable and the logic immediately tested and validated. 

Business Rules Management System

VisiRule supports the design, documentation and execution of the dense chain of reasoning that is a common feature of business rules systems, and, thanks to modern server farms, supports solutions that are scalable from internal users to outside business partners and customers. The VisiRule Manager provides a layer of management. Integration with repositories such as BitBucket and GIT provide version control.

VisiRule’s unique approach of "programming via flow-charting” permits rapid prototyping and review, and greatly enhances the accurate capture and shared understanding of business decision flows. The ability to represent complex decisions graphically helps ensure quality, transparency and ease of maintenance.

Business Rules Decision Tree

Business Rule Engine Tools

Backward Chaining Logic

VisiRule is a graphical tool which generates executable rules in the form of Flex backward-chaining rules denoted by the KSL keyword 'relation'. These are goal driven. The logic-based Inference Engine supports complex logic which can be used to solve complex problems in a manner comparable to human experts.
 

Forward Chaining

Flex also supports forward-chaining production rules denoted by the keyword 'rule'. These are data driven. These are not represented graphically in VisiRule but can be used as in the insurance demo on the Financial Expert Systems demo page.

 

Interleaved Forward and Backward Chaining

VisiRule supports both forward and  backward chaining inferencing.​ You can interleave these, so that from within a forward-chaining session you can use backward chaining to establish local provability. You can read Charles Forgy describing the difference between Forward and Backward chaining.