File Body

The body of the file follows the header section. Each record in the body represents a set of risks in a:

  • Given area (i.e., U.S. state or European country) or subarea (e.g. CRESTA zone)

  • Given peril covered for those risks (e.g. earthquake)

  • Given line of business (e.g. Homeowners for a U.S. ceding company)

It is very important that you include all the subareas in which the ceding company writes business. The coverages provided for in each record are:

  • B: Buildings only. In the US this includes coverages A and B

  • C: Contents only. In the US this includes coverage C

  • T: Time element only. In the US this includes coverage D

  • BC: Buildings and contents combined (i.e., the two coverages cannot be separated). In the US this includes coverages A, B and C

  • BCT: Buildings, contents, and time element combined (i.e., the three coverages cannot be separated) . In the US this includes coverages A, B, C and D

  • A: Automobiles only

  • W: Workers' Compensation or pandemic exposure

  • PD: Physical damage (Gulf of Mexico Offshore Platform only)

  • CROP: MPCI Agricultural and Crop Hail

For each record, you must provide data on at least one of the following:

  • No. of Risks

  • Sums-Insured Values

  • Premiums and Rates %

Note:

Files containing Market Shares must be created and imported separately..

Each record must have the following characteristics:

  • Each field must be assigned a value. If unknown, enter the digit 0 unless otherwise instructed below. It is very important that fields whose values are unknown are not skipped .

  • Individual fields must be separated by commas (as defined by the FIELD_SEPARATOR value in the header).

  • Individual records must be separated by a new line code, namely the ASCII CARRIAGE RETURN character followed by the ASCII LINE FEED character (as defined by the RECORD_SEPARATOR value in the header).

Finally, for every set of records for a given peril and a given LOB code, there must be a record for the area total. For example, if the file for a Belgian ceding company that provides Windstorm coverage contains nine records for Residential Building, one for each of the CRESTA zones, then the file must contain a 10th record for BELGIUM as a whole (i.e., areacode 11-000). If the file also contains records for, say, the Commercial LOB, then there should be a corresponding BELGIUM level (i.e., 11-000) record. These area total (i.e., country total and state total) records serve as check records to verify that the software reading the data is doing so correctly.

The fields in each record of a UNIUNICEDE/2 file are listed on the following pages.

Field

Name

Description

Notes

1

Area Tag

Identifies the area (i.e., country) and the subarea (e.g., county, ZIP Code, or CRESTA zone) in which the risks represented in this record are located.

The Area Tag value used must be consistent with the Area Tag Type.

2

Peril Codes

Identifies the peril covered for the risks in this record.

Note: The data in the fields that follow should represent this peril. Data for different perils should be reported separately in different records.

3

LOBCode

Identifies the line of business under which the risks covered in this record are reported.

The valid Line Of Business codes vary by country.

4

Coverage

Identifies the coverages included for the risks in this record. For example, if you are able to separate the sums-insured values for buildings, contents, and time element for a specific set of risks (i.e., risks for which the values in fields 1, 2, and 3 are identical) then you should enter the values as three separate records and in the three records you would provide the coverage code as B, C, and T, respectively. On the other hand, if you cannot separate the sums-insured for the three coverages, then you would enter all the values for that set of risks in a single record and set the coverage code as BCT.

A Buildings only. In the US this includes coverages A and B C Contents only. In the US this includes coverage C T Time element only. In the US this includes coverage D BC Buildings and contents combined i.e., the two coverages cannot be separated). In the US this includes coverages A, B and C BCT Buildings, contents, and time element combined (i.e., the three coverages cannot be separated) . In the US this includes coverages A, B, C and D. A Automobiles only

W Workers' Compensation or pandemic exposure

PD Physical damage (Gulf of Mexico Offshore Platform only)

CROP MPCI Agricultural and Crop Hail

5

NumRisks

This is the number of risks represented in this record.

This value must be entered in whole units (i.e., not in thousands or millions).

For records with W (Workers' Compensation) as the coverage code, this field represents the number of employees.

6

SumsIns

This is the total sums-insured value of the coverage (reported in field 4) for the risks represented in this record.

This value must be entered based on the DATA_UNITS and DATA_CURRENCY defined in the header.

For records with W (Workers' Compensation) as the coverage code, this field represents the payroll.

7

AvgDed

This is the average deductible for all the policies (for this peril) for the risks covered in this record.

This value must be entered based on the DATA_UNITS and DATA_CURRENCY defined in the header. If the policies for the risks in this record do not have any deductibles then enter the digit 0 (i.e., zero).

8

Prem

This is the total amount of written premium income from the policies (for this peril) for the risks covered in this record.

This value must be entered based on the DATA_UNITS and DATA_CURRENCY defined in the header. If the policies for the risks in this record do not cover any time element losses, enter the digit 0 (i.e., zero). If this record represents 5 risks, and two of the policies have a $75 premium and the other three policies have $200 premium, then the total amount of written premium is $750 (i.e., 2x$75 + 3x$200)

9

PremRate

This is the average premium rate per mil (‰), i.e., premium charged (for this peril) per 1000 units of sums-insured for the risks represented in this record.

This value must contain at least three decimal places.

10

SubareaName

This is the name of the area (i.e., country) or subarea. It should only be used if the DATA_LEVEL is 10 or 11.

This field improves the chances of detecting and fixing errors in the AreaTag field.

t - For countries other than the United States and Canada, Subarea Name is the eleventh field in the body of the file; field 10 is an unused place-holder.

Note:

In the HEADER, every line begins with an asterisk in the first character position. In the BODY, however, every line begins with the first value, i.e., there are no asterisks in the BODY. If a line in the body has an asterisk in the first character position, that line will be ignored