All Risk Modeler cat modeling processes rely upon the quantity and quality of the exposure data in an Exposure Data Module (EDM). An EDM is both a cloud-based datastore and the leading data model for managing exposure data. The definition and maintenance of exposure data in a cloud-based EDM is a prerequisite for all catastrophe modeling workflows.
Intelligent Risk Platform offers several different methods for defining and updating exposure data. Once exposure data has been imported into the EDM, it is available for running analyses and for exchanging data with other RMS products.
Your options for importing exposure data are not mutually exclusive. You can use any combination of these methods to import and update exposure data in the EDM.
An exposure is an entity that represents a potential financial loss to risk holders. In Risk Modeler 2.0, exposures are modeled and managed as exposure objects that manifest an underlying schema. Exposure objects include portfolios, accounts, and locations.
The Risk Modeler offers distinct services for managing these exposure objects. For each exposure type, the API generally provides services that enable you to create, update, or delete an exposure. For step-by-step instructions on creating accounts and locations, see Exposure Objects.
The EDM defines the relationships between exposure objects. portfolios, accounts, locations, policies, and treaties. To better understand the relationships between these exposures and how the Risk Modeler API enables you to define and manage these relationships, see Understand Exposure Data.
The Manage exposures in batch service enables you to create, update, or delete large numbers of exposures using batch processing. Using this service, you can manage large numbers of portfolio, account, location, treaty, and policy exposures in a single request.
The fastest way to import large volumes of exposure data into an EDM is to upload exposure data using the multiple relational import (MRI) process.
MRI enables you to import exposures utilizes flat files of account, location, reinsurance exposure data. A flat file is a delimited text file that stores structured data in a plain text format. MRI leverages a separate mapping file to define the relationships between the account, location, and reinsurance exposures.
The MRI process requires multiple steps. For step-by-step instructions and tips for programmatically implementing an MRI-based process, see Multi-Relational Import.
The Risk Modeler File Storage API defines services that enable you to migrate entire EDMs to the Intelligent Risk Platform by uploading backups of EDM databases (saved as BAK files) to Amazon Simple Storage Service (Amazon S3).
For step-by-step instructions, see Import EDMs.
Congratulations! Now that you understand the options available to you for defining or importing exposures, you are ready to prepare exposure data for analysis.
Updated 7 months ago