Intelligence

Calamìta

Insurance exposure, analysed event by event.

When an earthquake or a flood happens, you need to know which policies fall inside the affected area and what insured value they represent.

Real-time NatCat exposure analysis · INGV seismic data · hydrogeological and weather events · geolocated portfolio

Ask for a demo How it works

Live event · policies in the affected area

Real-time updatethe exposure map updates as event data arrives

INGV sourceseismic data updated in real time

Geospatial analysisgeospatial engines and parametric models

Claimsone shared map for assessing exposure and handling claims

Illustrative diagram of the impact area around the epicentre and of the geolocated policies in the portfolio.

The context

After an event, rebuilding the exposure takes time.

After an earthquake or a flood, the insurer has to estimate how many policies fall inside the affected area and what insured value is involved. If the data is scattered or not geolocated, rebuilding that picture takes time — and different departments can end up with different answers.

The first decisions come before the full picture

In the first hours you have to assess the policies involved, organise the loss adjusters and brief whoever handles reserves and communications. An exposure picture that only arrives days later makes all of that late.

Addresses without coordinates

Incomplete addresses, inconsistent formats and postcodes used as the only geographic reference make it hard to match policies to the affected area.

Departments working on different data

Risk management, claims and reinsurance can be working from different extracts and different criteria. Without a shared base, a consistent view of the exposure is hard to assemble.

Accumulations that stay hidden

Without a geographic reading of the portfolio it is hard to see in advance where exposure concentrates against the natural hazards being considered.

How it works

From the event to the policies that may be involved.

Calamìta takes in the event data, estimates the impact area and compares it with the policy coordinates. The result is a map of the potential exposure, showing the locations involved and where they concentrate.

The sequence

From the event to the exposure assessment.

The event data feeds the analysis: the affected area is estimated and compared with the geolocated portfolio. As the sources update, so does the exposure map.

Event

Event data acquired

For seismic events: magnitude, depth and coordinates. For hydrogeological ones: the warnings and the areas they cover.

Affected area

The impact area is estimated

Geospatial models estimate how far the event reaches and map the intensity bands around its origin.

Portfolio

Policies are matched against the area

Policy coordinates are compared with the estimated impact area. The result is the list of locations that may be involved, grouped by intensity band.

Assessment

What the operational decisions need

Risk management and claims read the same exposure picture: the locations involved, where they concentrate, and what is needed to set priorities.

Inside the product

One map, three ways of working.

The same information read by three departments with different needs: assessing exposure, handling claims, and watching portfolio concentration.

What the portfolio is exposed to

Shows the policies involved, the sums insured and the reserves, by intensity band, line of business and area.

Exposure by intensity band
Where the portfolio concentrates
History of events and their exposures

Exposure view

Which locations need attention first

The policies that may be involved are ordered by event intensity and exposure value, which gives a basis for setting priorities and assigning loss adjusters.

Locations ranked by intensity and exposure value
Support for planning contact with the policyholders involved
Claims received compared with locations potentially involved

Claims view

Where the portfolio concentrates

Reading the portfolio geographically shows where policies concentrate, and lets that be compared with the hazard levels being considered.

Concentration maps by area
Scenarios based on historical or hypothetical events
Analysis to support the conversation with reinsurance

Concentration view

What it brings together

Event data and portfolio, on the same map.

Type of event	Data source	What the analysis gives
Earthquakes	Italian national seismic network (INGV)	Intensity bands and the policies falling inside them
Floods	Hydrogeological warnings and bulletins	Affected areas and the policies that may be involved
Hail and other weather events	Weather data and warnings	Affected areas and portfolio concentrations
Policy data	Policy records matched to geographic coordinates	The reference for comparing the event area with the policies

The sources are agreed at set-up, according to the lines of business and the geographies in the portfolio.

Frequently asked questions

The questions we are asked
most about Calamìta.

Any other questions?

Geocoding can be handled as a first step: addresses are normalised and matched to coordinates. The quality of the starting data affects the precision of the analysis, so the coverage has to be checked and the addresses that cannot be geocoded reliably identified.

The processing scope, the access arrangements and where the data sits are agreed at set-up with the IT and privacy functions. Calamìta uses policy data to compare it with public event information; how that happens depends on the architecture agreed with the insurer.

No. Calamìta analyses the portfolio’s potential exposure to an event and identifies the policies that might be involved. It is not an actuarial pricing model and it does not estimate actual loss: it supports the operational assessment of the event.

They represent potential exposure, not assessed loss. The result depends on what is known about the event, on the models used and on how precise the policy coordinates are. It is a starting point for deciding which locations to look at, to be updated and compared with what the claims process finds.

The results of the analysis can be integrated into the company data platform built with frAIme and queried in plain language through Tequery. How the data is integrated and shared is agreed according to the architecture and the systems already in place.

Keep exploring

The other Add Value products

Intelligence · Banking

Tequery

Lets you query databases in plain language and check the SQL generated behind every answer.

Intelligence · Raw materials

PriceSense

Reads news and market data to estimate price movements and raw-material availability, with an analyst validating the result.

Data · Cloud and AI

frAIme

Integrates different data sources into a cloud-native data fabric, leaving the information in its systems of record and making it available to AI applications.

Intelligence · Mainframe

OptiMIPS

Analyses mainframe consumption and attributes it to the applications, to find where resources can be optimised.

Intelligence · Procurement

TSV

Categorises indirect spend with AI and makes it searchable by category and supplier.

Software · Modernisation

L2M

Core applications, modernised and verified against real data.

Intelligence · AI adoption

Officina AI

Finding where artificial intelligence can create value in business processes.

Know the exposure, before and after the event.

Ask for a demo Read an insurance case study