Services: Integrations configuration overview

BriteCore supports vendor integrations to ensure quoting for auto policies is efficient and accurate. The following integrations for LexisNexis products are currently supported in addition to SmartyStreets and Google Maps:

This guide will walk you through the high-level steps and roles/responsibilities involved in setting up a BriteCore integration.

At its core, the BriteCore integration platform is fairly simple. A BriteCore action, such as a button click or policy renewal, invokes the main component, called the BriteCore Vendor Integration Adapter. When you interact with or execute a task/command in BriteCore, this service looks up integrations configured for that action, and then calls their APIs, using the data mapping service to translate between services.

The following figures illustrate how integrations are set up in BriteCore.

Figure 1: Integration adapters.

Figure 2: BriteQuote communicating with LexisNexis Auto Data Prefill.

Figure 3: LexisNexis vendor setup.

Integration components

Integrations consist to two main components:

  • Steps: Steps form actions to take when events occur or on command from plugins.
  • Plugins: Plugins add graphical user interface (GUI) elements to BriteCore’s UI.

Integrations may also include data mapping when needed.

Integration considerations

  1. Identify how you want the integration to start. Do the steps need to start when an event occurs, such as bc.policies.policy_created? Does a step need to start when the user selects a button?
  2. Identify what steps you want to complete. Are any steps reusable between integrations? Do you have the authentication credentials to communicate with other vendors?
  3. Identify the input and output of data. Does the data need changed to fit an expected shape or structure?

Configure BriteCore integrations

Step 1: Client to request license and trial keys

Note: This step can take months (specifically for LexisNexis products).

Review the client’s role in enabling LexisNexis product integrations.

Step 2: Configuration analyst works with the client to consider their configuration options (questionnaire)

The following questionnaires are available:

Step 3: Configuration analyst adds vendor fields to BriteLines

Once the questionnaires have been filled out, the configuration analyst will add the specific vendor fields to BriteLines.

Step 4: Product/Cloud Operations deploy the LexisNexis Adapter

The Product/Cloud Operation teams are responsible for deploying the LexisNexis adapter to the client site.

Step 5: Technical Services team adds and configures the BriteQuote UI plugin via the UI

The Technical Services team is responsible for adding/configuring the BriteQuote UI plugin.

Step 6: Technical Services team to configure data mapping

The Technical Services team is responsible for configuring the data mapping using the questionnaires filled out in Step 2.

Step 7: BriteCore Project Manager to coordinate going live

The BriteCore project manager is responsible for coordinating the steps to go-live with each client/integration and ensuring the Statement of Work (SOW) is complete.