Overview

The Import API defines a standard process for importing exposure data into the Intelligent Risk Platform using several different file formats.

The OED (Open Exposure Data) schema is an exposure database format defined by OASIS that is serves as an industry standard schema for Oasis LMF-based models.

OED Import enables you to convert data received from cedants in this format to an EDM.

Step 1: Prepare Exposure Data

The first step is to create one or more flat files of exposure data. These flat files define the account, location, reinsurance, and reinsurance scope data that you want to upload, import, and transform into EDM data.

Exposure data is defined as a tabular dataset.

Imported exposure data, financial data, and secondary modifiers may be defined four different flat files (in CSV or TXT file format):

Both CSV and TXT files are supported. Depending on the file type, you may create accountsFile.csv or accountsFile.txt.

Each column in the flat file contains data with exposure attribute values separated by means of a text delimiter: comma, semicolon, or tab. To ensure accurate interpretation of any numbers that use commas, Moody's recommends tab delimiters.

For example, an accountsFile in CSV format might include the following data:

FlexiAccTestCase    PortNumber  ACCOUNTNUMBER   POLICYNUM   PERILCOVERED    AccCurrency LayerParticipation  LayerLimit
acc1    acc1    acc1   Layer1     AA1    GBP    0.3    500000   500000
acc1    acc1    acc1   Layer2     AA1    GBP    0.3    100000000    1000000
acc10   acc10   acc10  Layer1     WSS    GBP    0.3    500000   500000
acc10   acc10   acc10  Layer2     WSS    GBP    0.3    100000000    1000000
acc18   acc18   acc18  Layer1     BB1    GBP    0.3    500000   500000
acc18   acc18   acc18  Layer2     BB1    GBP    0.3    100000000    1000000
acc25   acc25   acc25  Layer1     WTC    GBP    0.3    500000   500000
acc25   acc25   acc25  Layer2     WTC    GBP    0.3    100000000    1000000
acc96   acc96   acc96  Layer1     AA1    GBP    0.3    500000   500000
acc96   acc96   acc96  Layer2     AA1    GBP    0.3    1000000001000000

In Step 4 of this procedure, we will need to specify the delimiter value used to structure data within the uploaded CSV files.

📷

OED Import Templates

Moody's makes OED import templates for accounts, locations, and reinsurance data available for download in the ExposureIQ application.

Each OED template identifies appropriate tables. OED templates are available in both CSV and TXT format.
You can download import templates the Import panel in the ExposureIQ application.

Flat files have the following restraints:

• Maximum file size: 300MB
• Maximum number of accounts: 1.5 million records
• Maximum number of locations: 1.5 million records

Once you have the flat files of exposure data, you can create an import folder on Amazon S3 to which this data can be uploaded.

Step 2: Prepare Mapping File

The OED import workflow supports custom column mappings by means of a mappingsFile.

The Import API uses a mapping engine based on the OED 1.1.5 schema definition to map OED data to EDM data.

The import folder optionally accepts a mapping file in MFF format that defines column mappings between the uploaded OED exposure data files (accountsFile, locationsFile, reinsuranceInfoFile, reinsuranceScopeFile) and table columns in the EDM.

The optional mappingsFile defines column mappings between OED data (as defined in the uploaded accountsFile, locationsFile, reinsuranceInfoFile, reinsuranceScopeFile flat files) and columns in EDM tables. If the mappingsFile is uploaded to the import folder, the column mapping specified in the mappingsFile overwrite the default mappings used by the mapping engine.

During import, the Import API maps the exposure data, financial data, and secondary modifiers defined in the OED flat files to the corresponding EDM tables. The OED-to-EDM mapping engine supports the mapping of OED version 1.1.5 data only.

• The mapping engine does not validate the data stored in OED import files.
• The mapping engine may fail while mapping the data to EDM if the data includes invalid values or missing records.
• The mapping engine defines default mappings for construction codes, occupancy codes, and secondary modifiers that you cannot change.

📷

Recommendation

Moody's has tested the mapping engine with a variety of portfolios, but it is important that you test the engine on your portfolios and evaluate the mapped data before utilizing the tool for production workflows.