Implementing the OOTB Insurance Submission Quality Score

From PegaWiki
This is the approved revision of this page, as well as being the most recent.
Jump to navigation Jump to search

Implementing the OOTB Insurance Submission Quality Score

Description Underwriting submission quality score radar chart
Version as of 8.1
Application Pega Foundation for Insurance
Capability/Industry Area Insurance



Enter your topic description[edit]

As an Underwriter I'd like to see a section on the application and Proposal that will provide more visual information regarding the company presenting the risk such as graphs and charts related to credit score, revenue, TIV, etc.

Use case examples[edit]

The visual information will analyze new business and renewal transactions and will consider information about the customer, agent, product and book of business and external data e.g. DnB credit scores. The visual graph will be available to the underwriter throughout the underwriting process and compare the attributes of the submission with the target attributes to determine the overall quality score (average submission quality score of 100% = target scores).

Before you begin[edit]

Determine which metrics will be used for each line of business. Assign a Target value and set minimum and maximum values for each metric.

Rules used to plot the chart[edit]

·       RadarChart.js - JavaScript file for plotting the radar chart, also contain styling elements

·       RadarStyleSheet.css – CSS file to style the classes referenced in js file

·       RadarStyleIcons.css- CSS file to include the icons referenced in the chart

Required third party files[edit]

·       D3Legend.js

·       Analytics-engine.woff

·       Analytics-engine.eot

·       Analytics-engine.svg

·       Analytics-engine.ttf

Process/Steps to achieve objective[edit]

What do individuals need to know to achieve the outcome? What do individuals need to know to achieve the outcome? Enter the precise steps to guide the user to achieving the desired outcome. Remember to always state where in the software the user must perform an action, before giving the action.

If “How To…” documents exist for specific configuration procedures please link (using the url) to those assets on the community **

Radar chart is launched from two places – both can use flow actions and launch the chart in modal dialog.

1.     Flow Action – LaunchRadarChart defined in Work-

2.     Section – RadarChart UI defined in Work-

3.     Control – RadarChart used in the section rule

4.     RadarChartSourceJSON – property to store the JSON string

Radar chart is invoked from the control and the JS file RadarChart.js requires a JSON input. Our application should set the property RadarChartSourceJSON with the expected format so that the chart is plotted.

Data model for the radar chart[edit]

·       A property named DataSetConfiguration is defined in Work- to access the underlying data structure.  This is a page property of type (Data-RadarChart-DataSet).

·       Have created two classes:

o  Data-RadarChart-DataSet

§ Key ( must be set either to Current Quote or Target Quote)

§ Values (page list associated to Data-RadarChart-AxisDefinition)

o  Data-RadarChart-AxisDefinition

§ Icon

o  Randomize from a set of few icons

§ Axis

o  The spoke dimension being measured such as clustering capacity score, average vehicle score, appetite by state score, etc.

§ Axis type

o  For Current Quote: This must be set to “Actual values”

o  For Target Quote: This must be set to “Target values”

§ Value

o  For Current Quote: This is set as part of the expression calculated using the properties in submission case.

o  For Target Quote: This is usually a lookup from the data table or other rules.

Sample Dataset[edit]

Mapping Rules[edit]

The chart is created for each LOB such as GL or Comm Property submission. The Target values are stored in data tables so that they can be delegated to users to modify values.

For instance, Years in Business Score, the Target score in years is 15 years. This is set in a decision table or data table and is delegated to business user to change this value. The actual value is determined by an expression calculating from the “Business start Date” and the current date function.

This is a spoke used in all lines, so this has to be set in the data transform invoking the radar chart for all submissions.

A sample data transform named SetupDataForCharting has been created. We need to specialize this for each LOB. There is also a sample activity named InitializeRadarChart is created, currently we are using this to plot the radar chart. This activity must be used as a reference to see how the data structure has been mapped, the data transform has been created which does the same thing that the activity does. The team should create data transform and not the activity. The activity will be removed after we create all data transforms.

We can adopt the similar approach we did for CompareAPI. Note this rule is currently stored in RadarChart ruleset, we need to store this as part of PegaInsureCL ruleset so that we can access the properties defined in submission case.

o  We can create one data transform that has mappings on dimensions that are used across all lines.

o  We will have SetupDataForCharting invoking this data transform and then have custom specialized logic for each LOB.

There are two dimensions namely, DnB Financial Stress Class Score and DnB Credit Score Class. Since the DnB integration is in Verification layer, we need to create a class specialized data transform to set these values for the radar chart to pick it up. Since this is used for all lines of business, it will be sufficient if we just customize the data transform that is shared across all LOB.

IMPORTANT NOTE:[edit]

For the chart to plot accurately, we need to use proportions to convert them into decimals as shown in sample data.  The years in business uses number of years and the range is between 0 and 25. The clustering capacity score uses TIC Value and the range is between 0 and 50,000,000. We need to use proportions to use them to be plotted in the same range.

While estimating stories, we need to come up with the following tasks:

1.     Design of the delegated rules for all target values.

2.     Some of the other dimensions have hardcoded values for actual values as well such as Premium against Agency Quota.

3.     Rules to calculate the actual values

4.     Mapping or writing data transform rules to set the JSON data structure for Radar chart.

There should be no need to update or modify any of the JS files or the stylesheets used in the creation of radar chart.

Results[edit]

As an Underwriter I would like a visual display of the key attributes score for the submission compared with target scores.