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.)
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.
Portfolio object may be linked to multiple
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
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 services, see the Location API reference documentation.
A Location object may be defined by
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),
LocationTrDetail (terrorism), and
LocationWcDetails (worker's compensation) objects. The
Property objects are required.
To learn more about the Location resource and Location API services, see LocationV1.
A Policy object may be defined by
To learn more about the Policy resource and Policy API services, see PolicyV1.
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
To learn more about the Treaty resource and Treaty API services, see TreatyV1.
The Branch object specifies the name of the branch that underwrites the account.
To learn more about the Branch resource, see BranchV1.
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.
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 Database Schema on RMS Owl or the EDM Database Schema in the Risk Modeler Help Center. (You must have a Risk Modeler account to access.)
Updated 5 months ago
RMS offers several different methods for importing exposure data into the EDM.