Import Exposure Data

Submit an MRI import job to the platform for processing

1435

Overview

Now that you have uploaded the account, location, and reinsurance resource files, and import mapping file to the storage bucket, you can run an import MRI job import that exposure data into an EDM.

The MRI import job fetches the account, location, and reinsurance data in the uploaded source files and using the uploaded import mapping file to ensure that related data is correlated and imported into the specified EDM.

Step 6.1: Run MRI import job

The Import exposures from file operation enables you to identify exposure data uploaded to storage bucket and import that data into the specified EDM using an MRI_IMPORT workflow job.

curl --request POST \
     --url https://{host}/riskmodeler/v1/imports \
     --header 'Accept: application/json' \
     --header 'Content-Type: application/json' \
     --header 'Accept-Language: en-US' \
     --header 'Authorization: XXXXXXXXXXXX'

All parameters are specified in the request body.

This operation may be used to initiate both MRI_IMPORT and ALM_IMPORT jobs. To define an MRI job, specify a value of MRI for the importType body parameter.

{
     "importType": "MRI",
     "bucketId": 35678,
     "dataSourceName": "myEDM",
     "delimiter": "TAB",
     "accountsFileId": 777777,
     "locationsFileId": 888888,
     "reinsuranceFileId": 999999,
     "mappingFileId": 555555,
     "currency": "USD",
     "portfolioId": 11,
}

Because we are defining an MRI job, you must specify the accountsFileId and locationsFileId body parameters as well as the bucketId, dataSourceNqme, and the delimiter parameters. We have also uploaded a reinsurance source file and a mapping file and will identify those files.

  • The importType parameter identifies the workflow job type. This operation may be used to initiate both MRI_Import and ALM_IMPORT jobs. Ensure that you specify MRI.
  • The bucketId identifies the ID number of storage bucket to which you have uploaded the accounts, locations, and reinsurance source files in Steps 2, 3, and 4.
  • The required dataSourceNqme specifies the name of EDM to which you wish to import the data.
  • The required delimiter parameter specifies the delimiter used to structure data in the account, location, and reinsurance source files.
  • The accountFileId, locationFileId, and reinsuranceFielId identify the account source file, location source file, and reinsurance source file respectively. The MRI process only works if both an accounts resource file and locations resource file are uploaded to the storage bucket. Consequently, the accountsFileId and locationsFileId must also be defined in MRI jobs.
  • The mappingFileId parameter specifies the ID number of an import mapping file. The import mapping file maps the columns in uploaded resource files to Risk Modeler database columns. The mapping file both defines the relationships between account, location and reinsurance data and between columns in the uploaded account, location, and reinsurance flat files and the corresponding columns in the EDM.
  • The currency parameter specifies a default value for the currency if the currency column for an imported exposure is undefined or blank. The value specified does not overwrite currency values in the source file themselves.
  • The portfolioId parameter specifies ID number of a portfolio. All uploaded accounts are associated with the specified portfolio. If null, the uploaded accounts are not associated with any portfolio. In Step 7, we will validate the MRI Import process by generating an portfolio-level exposure summary report that encompasses the accounts you have imported.
  • The locale parameter identifies the formatting convention that is assumed for imported dates and numbers. Depending on the option specified (en-US, en-GB, de-DE, fr-FR, dates may be interpreted as DD/MM/YYYY or MM/DD/YYYY, or numbers and decimals may use periods or commas as separators. If unspecified, American English (en-US) is assumed.

🍏

Deprecated

The geohaz body parameter is not supported in Risk Modeler.

If successful, returns a 202 Accepted response and adds an MRI_IMPORT to the workflow engine queue for processing. The Locations header returns a URL that will enable you to track the status of the job, using the Get Job Status operation and the ID number of the workflow job, e.g. /{host}/v1/workflows/451289.

Step 6.2: Track MRI import job status

The Get job status operation enables you track the status the MRI import job you just ran. The workflow ID is specified in the endpoint path.

curl --location --request GET 'https://{host}/riskmodler/v1/workflows/451289' \
     --header 'Authorization: XXXXXXXXXXXX'

A successful response returns the Workflow object, which provides detailed information about this workflow job including the submitTime, startTime, type, status.

When the job status is FINISHED, the exposure data will have been imported into the EDM.

{
  "id": 451289,
  "userName": "[email protected]",
  "status": "FINISHED",
  "submitTime": "2020-07-01T17:58:30.310Z",
  "startTime": "2020-07-01T17:58:33.608Z",
  "endTime": "2020-07-01T18:03:25.335Z",
  "name": "ACCOUNT",
  "type": "MRI_IMPORT",
  "jobs": [
    {
      "id": "c1469aad-4a36-4e75-9999-8daf3b0886a1",
      "taskId": 0,
      "workflowId": 451289,
      "status": "Succeeded",
      "submitTime": "2020-07-01T17:58:33.929Z",
      "createdAt": "2020-07-01T17:58:30.309Z",
      "name": "MRI_IMPORT",
      "input": {
        "name": "MRI_IMPORT"
      },
      "output": {
        "importSummary": "Imported 1 Accounts and 2 Locations"
      },
      "priorJobs": [],
      "percentComplete": 100
    }
  ],
  "summary": {
    "validationDownloadLink": "Not Available",
    "importSummary": "Imported 1 Accounts and 2 Locations",
    "expirationDate": "Not Available"
  },
  "progress": 100,
  "messages": []
}

Now, we will verify that the exposure data was added by generating an exposure summary report for the portfolio.