Understand Exposure Data
Manage the migration of EDM and RDM data
Overview
An exposure is a collection of account and location data that represent entities that may be affected by catastrophic events.
All exposure data is stored and managed in an Exposure Data Module (EDM), which defines the relationships between portfolios, accounts, locations, policies, and treaties. Every exposure object is created in reference to a specific exposure (data source) or to an object that belongs to that exposure.
The Risk Modeler API enables you to model or analyze exposures at the account or portfolio level. That is, assess the risk of account exposures (the locations belonging to an account) or assess the risk of portfolio exposures (all account exposures belonging to a portfolio.)
Portfolio
A portfolio is a collection of accounts. Risk Modeler analyzes a portfolio of accounts as a unit and produces portfolio-level results. An account may or may not belong to a portfolio.
A Portfolio
object may be linked to multiple Account
, Location
, Policy
, and Treaty
objects.
To learn more about the Portfolio resource and Portfolio API resources, see PortfolioV2 and PortfolioV1.
Account
An account defines a contract between a buyer (the cedant) and a seller (the underwriter) that transfers risk from the contract buyer to the contract seller in exchange for some premium. The account links those parties to policies that define the terms of their contract, treaties, and to one or more locations that represent exposures insured by those policies. To learn more about the Account resource and Account API calls, see the Accounts API reference documentation.
An Account object may be defined by Branch
, Cedant
, Producer
, and Underwriter
objects.
To learn more about the Portfolio resource and Portfolio API resources, see AccountV1 and AccountV2.
Location
A location is a building, property, business, or other asset that may be damaged by events. Every location is tied to a specific account. To learn more about the Location resource and Location API resources, see the Location API reference documentation.
A Location object may be defined by Address
, BuildingAttribute
, LocationCoverage
, LocationDetail
, and Property objects among others. Of special note are the “peril detail objects”, which specify the vulnerability of a location to different types of peril. Peril detail objects include LocationBiDetail
(business interruption), LocationEqDetail
(earthquake), LocationWsDetail
(windstorm), LocationtoDetail
(terrorism), LocationFlDetail
(flood), LocationFrDetail
(fire), LocationTrDetail
(terrorism), and LocationWcDetails
(worker's compensation) objects. The Address
and Property
objects are required.
To learn more about the Location resource and Location API resources, see LocationV1.
Policy
A Policy object may be defined by PolicyConditions
, PolicyCoverage
, and ReinsuranceCessation
objects.
To learn more about the Policy resource, see PolicyV1.
Treaty
A treaty defines a reinsurance contract between an underwriter and a primary insurer that applies to a collection of related exposures. Under the terms of the treaty, the primary insurer (for example, a cedant) transfers risk to the underwriter in exchange for a premium and the reinsurer assumes financial responsibility for that risk. Treaties may be applied to accounts, locations, policies, and portfolios.
The Treaty object may be defined by the Cedant
, LineOfBusiness
, and Producer
objects.
To learn more about the Treaty resource and Treaty API resources, see TreatyV1.
Branch
The Branch object specifies the name of the branch that underwrites the account.
To learn more about the Branch resource, see BranchV1.
Cedant
The Cedant object specifies a risk-holding party (insurer/reinsurer) that is transferring a portion of its risk to another risk-holding party (reinsurer/retrocessionaire). A Cedant
object may be defined within an Account or a Treaty object.
To learn more about the Cedant resource, see CedantV1.
Producer
The Producer object specifies the name and ID number of an agent or brokerage firm that produced the policy. A Producer object may be defined within an Account or a Treaty object.
To learn more about the Producer resource, see ProducerV1.
To learn more about Risk Modeler exposure objects, see the RiskLink® and RiskBrowser®18 and Risk Modeler™ 2.0 Database Schema on RMS Customer Support. You must have a Risk Modeler account to access.
Updated over 1 year ago