Skip to main content

Quotation engines

Quote you happy...

 

A custom-built quotation engine from Eonic includes all the rules and calculations to take a product or service and return the amount, including a cost breakdown, to the customer.

 
 
 
Clouds-layer-blue-sm
Clouds-layer-white-sm
 

Pick a number; any number...

 

Sometimes solutions are simple. You may already have an established back-end system that contains a quotation engine. In this case, Eonic would typically use web services to access and retrieve the amount. The end result for the customer would be the same; a tempting quotation as their call-to-action.

Other solutions are, however, more complex. This is where you need to take a deep breath before reading on, as we have to get technical! To create a bespoke quotation requires a Business Rules Engine, or BRE. Essentially this is a set of software tools that allows our analysts and developers to build calculation and decision logic that operates against your company's data. Its primary purpose is to separate the business logic from the system logic, allowing substantial changes in system behaviour without substantial changes to code. The "externalised" business rules can be deployed into mission-critical enterprise systems to affect the logic by which the system executes...

...are you still following us? Great, then read on...

Does my business need a BRE?

The simple answer is 'probably'. Virtually every quotation engine has some program logic that needs to often change or needs to change in ways not anticipated in the original design. This can establish grounds for a BRE in many system environments. The time and money saved on generally error-prone change management is often used as a "rule of thumb" when justifying the cost of a rules engine. Even in cases when the collections of rules are minimal or isolated, the benefits of a rules engine can quickly compound when the true cost of maintaining the logic is evaluated. In an era of stiff regulatory penalties and corporate-wide mandates for agile systems, a BRE can immediately add tangible value in many different ways.

What role does it play?

We're going to have to stay technical here, so bear with us...

...a business rules engine is integrated into your quotation engine to replace some or all of the business logic. Generally, it does not function to modify or control the data or user interface tier of the application, although it does provide this functionality. The portion of the application logic that the business rules engine controls varies depending on the type of application. Your application will communicate with the rules engine by specifying what set of rules you wish to execute and passing in the data necessary to make its decisions. Once the rules execute, your application can inspect the rules engine results to display them to the end user or to execute another process.

I've just about got that, so who uses a BRE and for what?

Insurance companies

  • Policy rating
  • Automated underwriting
  • Claims routing and management
  • Suitability/compliance

Financial service providers

  • Loan origination
  • Pro-forma trading models
  • Fraud detection
  • Wealth management

Ecommerce businesses

  • Cross-selling
  • Sales configuration
  • Content and access security

Government agencies

  • Tax calculations
  • Fee calculations
  • Application processing

Manufacturers

  • Supply chain management
  • Product configuration