Risk Modeler, Februrary 2022

Updates to Metrics API services to add support for financial perspective mapping and HD PATE processing.

Financial perspectives mapping

The Convert perspective (POST /[v1][v2]/analyses/{analysisId}/map-perspective) enables clients to generate new analysis results based on an existing analysis by "mapping" (i.e. converting) the financial perspective used in the original analysis to a new financial perspective. The service adds a new MAP_PERSPECTIVE job to the workflow engine queue and provides a URI for tracking the status of the job.

The required analysisId path parameter identifies a “source” analysis, the analysis results on which the new analysis is based. The request body defines four attributes: an analysisName, sourcePerspective, newPerspective, and mapPerspectiveOption. If the optional analysisName attribute is undefined, the service generates a name for the new analysis by appending the string _PERSP to the name of the original analysis.

All other attributes are required. The sourcePerspective and newPerspective attributes specify the financial perspective used in the source analysis and the financial perspective used in the new analysis respectively.

Financial perspectives are identified by a two-character string. The client can call the Get perspectives service to retrieve the list of financial perspectives.

C0
Number of Total Casualties
C1
Number of Medical Only Injuries
C2
Number of Temporary Total Injuries
C3
Number of Permanent Partial-minor Injuries
C4
Number of Permanent Partial-major Injuries
C5
Number of Permanent Total Injuries
C6
Number of Fatalities
CG
Injury Level Casualties
CL
Client Loss
DC
Distance to Centroid
EL
Event Loss
FA
Facultative Reinsurance Loss
G1
Ground Up Loss - Primary Peril
G2
Ground Up Loss - Secondary Peril
GR
Gross Loss
GS
Ground Up Specified Loss
GU
Ground Up Loss
I0
Ground Up Loss - Indemnity
I1
Indemnity Losses - Medical Only
I2
Indemnity Losses - Temporary Total
I3
Indemnity Losses - Permanent Partial-minor
I4
Indemnity Losses - Permanent Partial-major
I5
Indemnity Losses - Permanent Total
I6
Indemnity Losses - Fatalities
IG
Injury Level Losses - Indemnity
L1
Losses from Medical Only Injuries
L2
Losses from Temporary Total Injuries
L3
Losses from Permanent Partial-minor Injuries
L4
Losses from Permanent Partial-major Injuries
L5
Losses from Permanent Total Injuries
L6
Losses from Fatalities
LG
Injury Level Losses
M0
Ground Up Loss - Medical
M1
Medical Losses - Medical only
M2
Medical Losses - Temporary Total
M3
Medical Losses - Permanent Partial-minor
M4
Medical Losses - Permanent Partial-major
M5
Medical Losses - Permanent Total
M6
Medical Losses - Fatalities
MG
Injury Level Losses - Medical
NL
Primary Insurer Net Loss
NP
Total Number of People Analyzed
OI
Other Insurer's Loss
OL
Over Limit Loss
PY
Payout Loss
QS
Quota Share Treaty Loss
RC
Net Loss Post Corporate Cat
RG
Reinsurance Gross Loss
RL
Net Loss Pre Cat
RN
Reinsurance Net Loss
RP
Net Loss Post Cat
SS
Surplus Share Treaty Loss
TE
Total Exposure
TG
* %Share
TN
* %Share * %Retent
TV
Total Value
TY
Treaty Loss
UC
Underlying Coverage
VA
Primary Underwriter Account View
VL
Location View
VP
Primary Insurance Portfolio View
VT
Treaty Underwriter View
VY
Policy View
WX
Working Excess Treaty Loss

Financial perspectives are understood to be upstream or downstream of one another. The position of perspectives relative to one another is an important factor in financial perspective mapping. Upstream perspectives are higher in the table than downstream perspectives.

Financial service mapping serves three distinct business scenarios depending on the mapping option (mapPerspectiveOption) specified. The mapPerspectiveOption attribute accepts one of three values: INCLUDE_DOWNSTREAM, DELETE_OTHER, and SELECT_ONLY.

• If INCLUDE_DOWNSTREAM is specified, the service maps the sourcePerspective to the newPerspective and copies the mapping to all downstream perspectives except reinsurance gross (RG) and reinsurance net (RN). The downstream perspectives (except RG and RN) return same results as the specified newPerspective.
• If DELETE_OTHER is specified, the service maps the sourcePerspective to the newPerspective and deletes records for all perspectives other than the newPerspective including the sourcePerspective. All perspectives other than the specified newPerspective return a value of 0.
• If SELECT_OTHER is specified, the service maps the sourcePerspective to newPerspective. All other downstream and upstream perspectives are unchanged.
On submission, the service returns a 202 Accepted status and a URI in the Location header that enables you to track the status of the job ({host}/v1/workflows/100000). On completion, the analysis is added to the Intelligent Risk Platform RDM.

HD PATE processing

The Analyze with PATE service (POST /[v1][v2]/analyses/{analysisId}/pate) enables clients to create and apply treaties to an existing analysis or analysis group, and view updated analysis results without the need to run a new analysis job. The service adds a new PATE job to the workflow engine queue and provides a URI for tracking the status of the job.

The updated service now supports PATE processing for HD analysis results and PLT-based HD analysis results (i.e. “simulated losses”; results converted from ELT to PLT). The service continues to support PATE processing for ELT results generated using DLM and ALM models with no changes.

For HD analysis results, the client may insert, update, or delete treaties applied to individual analyses. The analysisId path parameter identifies a specific HD analysis. One or more of these schema objects may be defined in the request body. The request body consists of an array of objects.

For PLT-based HD analysis results (simulated losses), the client may insert, update, or delete treaties applied to both individual analyses and to analysis groups. The analysisId path parameter may identify either a single analysis or an analysis group. One or more schema objects may be defined in the request body.

  • If the PATE processing job is applied to a specific analysis of simulated losses, the analysisId specified in the request body is identical with the value of the analysisId path parameter. The groupId attribute specified in the request body has a value of 0.
  • If the PATE processing job is applied to an analysis group of simulated loses -- a collection of multiple analyses, the value of groupId and analysisId attributes differ depending on whether the treaty is applied to the entire analysis group or to an analysis within to the analysis group. Where the treaty is applied to the analysis group— i.e. it is a “group-level treaty”, the groupId and analysisId values are identical. Both match the value of the analysisId path parameter. Where the treaty is applied to an underlying analysis—an analysis belonging to the analysis group, the value of the groupId is identical with the value of the path parameter (i.e. the ID of the analysis group), but the analysisId specified in the response body matches the value of the underlying analysis—the analysis to which the treaty is applied.
    The sample code shows a request to update the treaty applied at the group-level to an analysis group of PLT-based HD analyses (simulated losses). The value of the analysisId and groupId attributes are identical.

On submission, the service returns a 202 Accepted status and a URI in the Location header that enables you to track the status of the job ({env-url}/v1/workflows/100000). On completion, the analysis is added to the Intelligent Risk Platform RDM.

Get perspectives

The Get perspectives by analysis service (GET /[v1][v2]/analyses/{analysisId}/perspectives) service enables the client to retrieve financial perspectives for a specified analysis. The optional exposureType parameter enables the client to filter perspectives by exposure type. If unspecified, the service uses the default value of 0 and returns all exposure types.

Financial perspectives are understood to be upstream or downstream of one another. The position of perspectives relative to one another is an important factor in financial perspective mapping. For more information, see Map perspective by analysis.