Covered objects

Coverables have the following characteristics:

  • All covered objects are coverables.
  • Some policy entities are not coverables.
  • A coverable entity implements the CoverableDelegate interface.
  • A Coverable delegate encapsulates coverage behavior.

The term coverable refers to any covered object. For example, insurance terminology refers to a covered object, such as a house, as a coverable.

  • For liability, the insured is the coverable.
  • For liability coverages, PolicyCenter designates the policy line as the coverable to represent the insured.
  • For coverages that attach at a location, the location is a coverable. Do not use PolicyLocation as the coverable, but instead, create a separate coverable entity.

Other policy entities

Entities within a policy need not be coverables. For example, general liability stores rating basis information in location-based exposures. This exposure entity is not coverable. Scheduled equipment in the businessowners line is another example. To provide a coverage for set of scheduled items, attach a coverage to a building or location that contains an aggregate limit or deductible as a coverage term. Then create a scheduled item array on the building or location. You can use the stated values of scheduled items to determine a coverage limit. Unless you need separate declared limits or deductibles associated with each scheduled item, you need not attach a coverage to each item in the list. In cases where the set of scheduled items is covered by a single coverage limit, the scheduled item entity is not a coverable.