Insurance · Analytics ·

Technical steering — loss ratio

Steer your technical profitability: combined ratio, frequency and average cost of claims by product.

Illustrative preview of the SAP Analytics Cloud dashboard Technical steering — loss ratio for the Insurance industry: metrics Combined ratio, Loss ratio, Claim frequency, Average claim cost, analyzed by Product, Region, Segment.
Illustrative preview of a possible rendering in SAC. Brand colors and structure; synthetic figures.

KPIs included

  • Combined ratio
  • Loss ratio
  • Claim frequency
  • Average claim cost

Analysis dimensions

  • Product
  • Region
  • Segment

About this template

Steer your technical profitability: combined ratio, frequency and average cost of claims by product. Designed for teams in the Insurance industry, the model pre-wires 4 key metrics — including Combined ratio and Loss ratio — analyzable across 3 analysis axes (Product, Region, Segment). You start from an already-bounded base (units, aggregations and business labels defined) rather than a blank sheet.

After downloading, import Technical steering — loss ratio into SAC Modeler (Files → New Model → Import data from a file), map the 3 dimensions and 4 measures, then build your Story. The provided dataset contains 720 to 960 rows with realistic values for the Insurance industry, available as .xlsx (multi-sheet workbook), .csv (flat table) and .package (ZIP bundle with model.json, data.csv and README).

FAQ

What is the "Technical steering — loss ratio" template for?

It provides a ready-to-use SAC structure to drive analytics in the Insurance industry. The standard business KPIs and dimensions are already defined, saving you the modeling phase.

Which KPIs are included?

The template includes 4 metrics: Combined ratio, Loss ratio, Claim frequency, Average claim cost. Each is computed across the dimensions Product, Region, Segment.

How do I import it into SAP Analytics Cloud?

Download the .csv or .xlsx format, then in SAC: Files → New Model → Import data from a file. Map the columns (Dimensions then Measures), validate the types and build your Story. Allow 5 to 10 minutes for an operational model.