Topics on this page

How quotes are set up in BriteCore

Define Line of Business in BriteLines

You can’t instantiate quotes without a Line of Business (LOB) definition in BriteLines. BriteLines includes a rating engine, which is a service that evaluates field answers and items (coverages) on a quote or policy and provides a premium. The rating engine is one of the primary features of BriteLines.

LOBs define:

  1. Different types of risks. Think of risk types as a class (for example, vehicles) and risks as instances of a risk type (for example, a particular vehicle).
  2. The relationship between risk types; for example, a policy with several drivers who have multiple driving violations.
  3. Fields that can be collected during a quote and their definitions. For example, the Vehicle Identification Number (VIN) field is defined as a string.
  4. Rate tables, rate factors, rate modifiers, and calculations, which are used to determine premiums on coverages.
  5. Items, which are coverages, fees, and other line items that might appear on the Policy Declaration.

BriteLines defines all of the data points that will be captured and evaluated during a quote, so it’s important to understand the structure of the LOB before working on building a quoting front end.

The quoting front end won’t interact with BriteLines directly. Instead, the quoting front end will submit requests to BriteQuote, which will communicate with BriteLines to create new quotes for a given line and new risks from a given risk group.

Define rules in BriteRules

BriteRules evaluates business rules during different transactions like new business (quoting), endorsement, and renewal.

For quoting, the following rule types are important:

  1. Validation rules: Rules that validate that combinations of answer values and items are allowed.
  2. Behavior rules: Rules that change values on a quote, like adding/removing a field, adding/removing a coverage, or showing/hiding a field. It may also restrict the number of options for a given field.
  3. Underwriting rules: Rules that automatically evaluate a quote and approve/refer/decline based on the contents.

BriteQuote handles submitting risks to BriteRules, so the quoting front end won’t be expected to interact directly with BriteRules.

BriteRules returns a list of actions for BriteQuote to perform. BriteQuote performs these actions by updating the risks on the quote and returning the changes. The quoting front end is expected to respond by displaying the changes received from BriteQuote. Those changes will include displaying validation errors, showing/hiding fields, and changing field values.

BriteRules also determines which documents and forms need to be generated by BriteDocs. BriteDocs then interacts directly with BriteQuote to deliver the appropriate forms and deliverables.

Set up vendor integrations (if applicable)

Each vendor integration is an API service that sits between the quoting front end (or other API consumers) and the third-party vendor product. Each vendor integration must provide a well-structured REST API that is documented with OpenAPI.

Vendor Integrations are called from the quoting front end. Requests are sent to the Integration API service. The response data is mapped on the frontend into risks and risk field answers.

Define forms and deliverables in BriteDocs

BriteDocs is the service responsible for document management and generation.

The document generation component is a server infrastructure that lives entirely in AWS. When a document is requested from a requesting service, such as BriteCore, a document request event is submitted to BriteEvents. That event is consumed by a BriteDocs Generation Worker, which generates a document from the requested template. Generated documents are uploaded into S3 and the file location is returned to the requesting service.

BriteDocs also provides a document management component with a user interface to create, import, version, and publish new document templates. Templates can be created, organized, searched, previewed, edited, and generated from these screens.

For more information, refer to Create and manage deliverables.

Quote proposal flow

Figure 1 shows the interactions between BriteQuote, BriteDocs, and BriteRules to deliver the appropriate documentation for a quote application.

Figure 1: Quote proposal flow

Quoting submission flow

Figure 2 shows the quoting submission flow from agent log in to submission, highlighting all of the interactions between different BriteCore services.

Figure 2: The quoting submission flow from agent log in through submission.

Policy binding flow

Figure 3 illustrates how a quote is bound after submission.

Figure 3: Quote binding after submission.