Detailed loss analysis

The Touchstone Extended Technical Preview loss engine includes several updates for the detailed loss analysis function.

Enhancements

We made the following improvements:

  • Enhanced the detailed loss analysis and loss modification analysis logs. Now the analysis log returns the errors/warnings, summary, and the remapped construction and occupancy codes.

  • Enhanced financial perspectives for accurately modeling step functions with building and contents policy terms including deductibles, layers, and sub-limits.

  • Updated the order of applying deductibles and limits: deductibles are applied before limits in a detailed loss analysis.

  • Enabled ability to save loss results by sub-perils when you perform a detailed loss analysis.

  • Enabled ability to export detailed loss results by sub-perils.

  • Enhanced performance of detailed loss analysis: use of an even number of cores in multiples of two in a detailed loss analysis.

  • Deprecated EnableCorrelation and ApplyDeductibleBeforeLimit APIs that allowed for manual inclusion of the correlation and deductible factors in a detailed loss analysis.

Enhanced the analysis log

The analysis log file now includes valuable information such as a detailed errors/warnings summary, construction and occupancy codes, and statistics of modeled exposures. Users can analyze the quality of the process (export, import, etc), find out missing data (such as event filters and unsupported construction or occupancy codes), or build a downstream programmatic process to troubleshoot errors. Now the existing GetFile method returns the log containing remapped construction and occupancy codes associated with a specific template.

Enhanced saving and viewing of loss results

You can save and export loss results by sub-perils for all Verisk models. We implemented additional loss analysis properties in the DetailedLossAnalysisOptions class.

Optimized performance

We replaced the HPC Scheduler compute resources type "nodes" with "cores" in the DetailedLossAnalysis class. Using cores as the resource unit enables Touchstone to reduce the likelihood of underused resources when running analyses.

To optimize memory usage, we recommend assigning cores in multiples of two and submitting API requests. To ensure backward compatibility in the updated engine, the API requests accept an odd number of Minimum or Maximum cores. Internally, the API mechanism rounds the odd number to an even number of cores. That is for a request with 1 core, the engine rounds up to 2 cores; and for all other odd numbers of cores, the engine rounds down to the nearest even number. Note that the Touchstone UI accepts only cores in multiples of two for all analyses. You should be prepared to use more cores for larger models, such as the Verisk Severe Thunderstorm Model for the United States. You may also want to account for additional space to leverage some of the new enhancements to the Touchstone Extended Technical Preview.

Enhanced deductibles

The loss engine applies deductibles first followed by sublimits. We implemented additional coverages, blanket deductibles, franchise (third-party) deductibles, attachment point deductibles, and layer deductibles to identify risks associated with exposures in different policy conditions. Refer to the API Reference posting to learn about the new exposure-level deductibles.