Field Mappings

You must have a valid mapping set for each set of files that you want to import. The mapping set determines how the data is validated and where it is saved in the database. For example, if you indicate that a field in your import file contains AIR construction codes, the import validation process alerts you if any values in that field do not appear to be valid construction codes. If you have used custom values in an import field, you can then map the custom values to valid AIR values using the Value Mapping settings.

 

AIR ImportExpress does not import fields that are not mapped to valid Touchstone fields. This provides you with an easy way of omitting custom or proprietary data fields that do not affect catastrophe modeling.

After selecting a policy type, a mapping set, and the source files in the Mapping Set and File Selection area of the Import & Mapping Data tab on AIR ImportExpress, click Edit Mappings to map the fields in your CSV import files to the corresponding Touchstone fields. The changes you make are saved in the mapping set.

 

When you select the source files for import, AIR ImportExpress automatically attempts to map fields in the files to acceptable Touchstone fields. This function is called "automapping."

Workers' compensation records contain the same information as property records, except for information about replacement values and limits. Instead, you map the number of employees, annual payroll, percent of shifts, annual payroll, average annual wage, and medical costs to valid Touchstone fields.

To edit field mappings:

1.     In the Mapping Set and File Selection area on the Import & Mapping Data tab of AIR ImportExpress, select the policy type, mapping set, and data to import.

2.     Click Edit Mappings.

The Field Mapping window includes a tab for each type of data that you selected. A status icon on each tab indicates whether the tab is filled out or requires further action .

 

The Contracts tab, Locations tab, and Reinsurance tab contain sub-tabs for field mapping and defaults. The Step Function tab contains a tab for field mapping.

3.     Select the Field Mapping tab that corresponds to each of the file types to import—contracts, locations, reinsurance, and/or step function.

The tabs that appear depend on the policy type. The Mapped Fields grid initially displays the fields in the source files that AIR ImportExpress was able to automap. If you map fields manually, the Mapped Fields field displays the total number of fields that were automapped or manually mapped. The first row of the Mapped Fields grid contains the column headings in your source data. The second row contains the valid Touchstone fields. The remaining rows contain data from the first 10 import records.

4.     To map your data to valid Touchstone fields, select the appropriate Touchstone field from the list below the column heading for each import column containing data that you want to import.

For example, if your data includes an "InsuredName" column, select "Insured Name" from the list below the "InsuredName" import column heading. Each tab includes a list of required fields that must be included in the import file for a successful import. In addition, an asterisk (*) next to a Touchstone field identifies a required field. If you already mapped a required field, a green check mark appears to the left of the field. Warning triangles identify additional required Touchstone fields that you must map.

5.     When you select the Locations tab, in the # Terms field, select the number of coverage term sets that exist for the locations that you want to import.

  When a location includes multiple sets of coverage terms, the terms are repeated in the Field Mapping grid. The field label identifies the term set. For example, "Deductible Type 2" indicates that this is the Deductible Type field in the second set of terms and "Deductible Type 3" identifies the field in the third set of terms.

6.     As you edit the settings on each tab, click Apply to save the field mappings.

7.     When you finish setting field mappings, click OK to save the field mappings and close the Field Mapping window.

After editing the field mappings, you can configure any necessary value mappings.

 
  • See the Using Geocoding in Touchstone document on the AIR Client Portal for information about the minimum location information requirements for geocoding exposures.

  • If your exposure data includes columns for both CountryISO and CountryCL2 codes, make sure that you map only one of these fields. Otherwise, the mapping set will be invalid, and the import will fail.

 


© 2020 AIR Worldwide. All rights reserved.

Touchstone 7.0 Updated September 03, 2020