Better data in, better answers out

Most exposure problems are data problems: a missing postcode, an implausible value, a schedule in the wrong format. Catching them as the data arrives is cheaper than finding them in a loss estimate.

  • Rules run on arrival
  • Named, owned corrections
  • Patterns, not just incidents

Fix the record, not the report.

A dense coastal city at night, photographed from orbitPhoto: NASA
Policy · schedule
ExposureHub Policy tab: a schedule of 1,000 locations with a map of the Massachusetts portfolio
Illustrative
6 of 8

fictional records flagged on arrival, each routed to its owner.

Most exposure problems are data problems. Catch them as the data arrives.

Catching them as the data arrives is cheaper than finding them in a loss estimate.

A missing postcode

The location cannot be placed.

An implausible value

A total insured value that is zero, or far too large.

The wrong format

A schedule that does not match your data model.

Found on arrival, not in the loss estimate

Switch a rule off. Fix a record. Watch the score.

Eight fictional records arrive. Each rule you leave on tests every record as it comes in; flagged ones go to an owner, and every correction is kept against the record.
RecordCountryPostcodeLat, longValue USD mConstruction
R-101US0100142.07, -72.6212.4Masonry
R-102USmissing42.38, -72.478.1Timber
R-103US0210842.36, -71.060Steel
R-104GBEC2N 2DB51.51, -0.0922missing
R-105GBM1 1AE3.14, -0.1114.2Masonry
R-106US1000140.75, -73.999,999Steel
R-107GBmissing53.48, -2.2431.5Masonry
R-108US9410537.79, -122.3917.3Timber
Illustrative: fictional records
Records passing every rule that is on
25%

6 flagged of 8

The rules, owned by your team
Audit trail

Route a flagged record to its owner and the correction is recorded here.

Missing, inconsistent or out-of-range is found in the fields.

This is the Policy tab's schedule: a postcode, coordinates, a geocoding type and a value on every row. These are the cells a rule looks at. The Data Quality tab sits next to it in the same navigation, with the Audit tab keeping the per-record history.

Policy · schedule
ExposureHub Policy tab: a schedule of 1,000 locations with a map of the Massachusetts portfolio
1
2
3
4

ExposureHUB demo environment · Policy tab · demo property schedule

Other people's data gets the same checks.

Satellite imagery, climate data and social media data give a more complete picture of risk, but only if they are right. Securely feeding them into a platform involves best practice in all six of these.
Data encryption
Access controls
Data validation
Data normalisation
Data monitoring
Vendor management

Three of them are the checks: validate, normalise, monitor.

Validate

Check third-party sources for inconsistencies or errors; this is critical to accuracy and completeness.

Normalise

Standardise sources so they are compatible with the platform's data model; the best providers convert data from many sources into a standard format aligned with its schema.

Monitor

Watch sources for changes or updates so the data stays accurate, secure, compliant and up to date, with alerts to tell users when something changes.

Ebix Europe, “Lloyd’s syndicate business plan bulletin: accelerating improved exposure management”

Five things the DQ Module does, as it describes them.

DQ Module, as described on the ExposureHub page on ebixrisk.com

Automated validation against configurable quality rules

Early detection of missing, inconsistent or out-of-range values

Trend analysis of recurring data quality patterns

Correction workflows with an audit trail per record

Supports regulatory compliance requirements

Modules behind it, and the next job.

Each solution is the platform's modules applied to one job. The next one picks up where this one ends.

Put data quality at source to work.

Book a walk-through built around your own classes of business and the questions your team asks of the book.