Location object model

The following object model diagram displays some of the entities relating locations.

In PolicyCenter, you can create locations on the account level and the policy level. PolicyCenter stores location information on the account, and policies on that account can access it. The location object model is designed to handle revisioned fields. You can add fields to the AccountLocation entity and then configure whether those fields are revisioned at the policy level.

The AccountLocation entity is a subtype of the Address entity. You can add revisioned fields to the AccountLocation entity. In the default configuration, all fields in Address and AccountLocation are revisioned except for LocationName, LocationNum, and Phone.

Inside the box labeled PolicyPeriod Entities, the PolicyLocation entity has fields that are revisioned. These are marked as rev’d.

The PolicyLocation entity contains foreign keys to the AccountLocation and the PolicyPeriod entities. The PolicyLocation entity has a foreign key to the TaxLocation entity. You can add fields to the PolicyLocation entity. These fields are used only on a specific policy, not across policies.

Some of the subtypes of PolicyLine entity have associated location types. The subtypes have a foreign key, Location, that points to the PolicyLocation. The object model diagram shows the CommercialPropertyLine subtype.

In the default configuration, account location and policy locations are numbered separately. Because of this, both AccountLocation and PolicyLocation have their own LocationNum field which is not revisioned. For more information about location numbering, see Location numbering.