Defining availability in lookup tables

An availability lookup table is a set rows. Each row defines a rule for whether or not the pattern is available. Availability lookup tables are available on the following patterns:
  • Conditions
  • Options
  • Coverages
  • Packages
  • Coverage terms
  • Products
  • Exclusions
  • Questions
  • Modifiers
  • Question sets
  • Offerings
  • Rate factors

    • Availability in all of these patterns can be based on date and jurisdiction. Product availability can also be based on industry code. Availability for all patterns except products can based on underwriting company and job type. You can extend availability tables with additional columns to handle other availability criteria.

    Availability lookup tables have columns that apply to the product. For example, navigate in Product Designer to Products > Businessowners > Availability. The lookup table for the businessowners product has the following columns:

    • StartEffectiveDate
    • EndEffectiveDate
    • Availability
    • State
    • JobType
    • IndustryCode

    While the lookup table for collision coverage on the commercial auto line has different columns. Navigate to Policy Lines > Commercial Auto Line > Coverages > Collision > Availability. This lookup table has the same columns as the previous table with a few differences. The collision coverage lookup table omits the IndustryCode column, and includes the following columns:

    • UWCompanyCode
    • PolicyType
    • VehicleType

    The columns in an availability table, such as start effective date, end effective date, and job type, are called dimensions. In addition, a column called Availability designates whether a pattern that matches the row is available or unavailable. When evaluating a pattern, PolicyCenter finds the row in the availability table that matches best, and then uses the state of the Availability cell in that row. The best matching row is the row that matches the most dimensions. If multiple rows match the same number of dimensions, the precedence of the dimensions determines the row that determines availability.

    Omitted dimensions are wildcards that match any value. If no rows match any defined dimension, the pattern is made unavailable.

    Important: Every availability lookup table must contain at least one row. Product Designer displays validation errors and refuses to commit your changes if it detects any availability tables that do not have at least one row. If you define an availability table without at least one row by, for example, using Studio to edit the XML file, the PolicyCenter server refuses to start.

    Using policy type to define pattern availability

    In certain policy lines, policy type defines pattern availability. After selecting policy type, pattern availability is further narrowed by the selected coverage form. For example, in homeowners, the policy type (dwelling, condominium, or rental) broadly defines pattern availability. The coverage form (HO2, HO3) further limits pattern availability.

    You can use the homeowners line of business as a model for defining policy types and coverage forms.

    Defining pattern as available on a job-by-job basis

    The JobType column specifies the policy transaction type on which to base availability. One use of this field is to make a coverage or other pattern available on a policy transaction basis. For example, you can make a pattern available for new business only. For more information, see Making a product model pattern available by policy transaction type.