Risk Modeler, September 2022

The September release introduces marginal impact reporting and enhancements to the Export and Location operations.

Export API

The Export data module to file operation (POST /v2/exports) now enables you to specify whether period loss tables (PLTs) are exported to the RDM as PLTs or event loss tables (ELTs).

In previous releases, PLTs generated by an HD analysis could only be exported as ELTs because the RDM schema did not support PLTs. This Risk Modeler release updates the RDM to support a new plt schema that includes the rdm_port, rdm_treaty, and rdm_fac tables. Exporting PLTs enables you to preserve the effect of the temporal component on event losses.

When exporting results data using the ResultsExportInputV2 type workflow, the client can now specify whether PLTs are exported as PLTs or ELTs in the exportHdLossesAs body parameter:

{
    "analysisIds": [
        148368
    ],
    "rdmName": "GM_TC1_Export_Losses_PLT",
    "type": "ResultsExportInputV2",
    "exportType": "RDM",
    "createnew": true,
    "exportFormat": "BAK",
    "sqlVersion": "2019",
    "exportHdLossesAs": "PLT"
}

The parameter is optional. If unspecified, PLTs are automatically converted to ELTs when exported to an RDM.

Locations API

The Create location EQ peril operation (POST /v1/locations/{id}/locationeqdetail/{locationeqdetailid}) now accepts three new EQ peril attributes in the request body: soilPeriodMatch, groundwaterDepthMatch and groundSlopeMatch.

The Update location EQ peril operation (PUT /v1/locations/{id}/locationeqdetail/{locationeqdetailid}) now accepts three new EQ peril attributes in the request body: soilPeriodMatch, groundwaterDepthMatch and groundSlopeMatch.

The Get location EQ peril operation
(GET /v1/locations/{id}/locationeqdetail/{locationeqdetailid}) now returns three EQ peril attributes: soilPeriodMatch, groundwaterDepthMatch and groundSlopeMatch.

Metrics API

The Get marginal impact by analysis operation (POST /[v1]/analyses/{id}/marginal-impact) returns a marginal impact report that measures the effect of adding additional accounts to a portfolio as differential losses.

A marginal impact analysis calculates the difference between a portfolio-level analysis result (based on the "reference portfolio") with a new analysis that incorporates metrics from an account-level analysis result.

🚧

The current releases supports marginal impact analysis that calculates differential losses based on a single new account only.

The operation accepts a single {analysisId} path parameter that specifies a the ID number of a porfolio-level ELT analysis result. All other parameters are specified in the request body.

{
    "outputType": "Account",
    "currency": {
        "code": "USD",
        "scheme": "RMS",
        "vintage": "RL22",
        "asOfDate": "2022-06-01"
    },
    "marginalImpactAnalysisIds": [
         99999
    ],
    "jobName": "Job_Name_Marginal_Impact",
    "rateSchemes": [
        202,
        203
    ]
}

The currency, outputType, and jobName parameters are required.

• The outputType body parameter specifies the granularity of the marginal analysis report. One of Account or Policy. If Account, the report returns projected losses for all policies and locations
  grouped by peril. If Policy the report returns projected losses for all analyses grouped by policy.
• The currency body parameter.
• The marginalImpactAnalysisIds body parameter specifies an array of account-level analysis results identified by their ID number. In the current release, only a single analysis result is supported. For each analysis result, the operation returns differential losses that represent the difference between reference portfolio metrics with those of the updated portfolio that includes the account metrics.
• The jobName body parameter identifies the name of the workflow job. These jobs belong to the MARGINAL_IMPACT workflow type.
• The optional rateScheme body parameter specifies an array of event rate scheme IDs to be used in metric calculations. If specified, overrides the event rate schemes used in the original analyses.

📘

Role-based Permissions

To perform this operation the principal must belong to a group that has been assigned the Cat Analyst, Portfolio Manager, or Risk Analyst role.