Product model patterns

The product model consists of set of templates called patterns. PolicyCenter uses these patterns during policy transactions to generate specific instances of policies and policy objects. The product model provides a large number of patterns. The following patterns are the core patterns you use to start to define a new product. Most of the patterns contain the word “pattern” in their name. However, one exception is Product, which does not.

Pattern

Description

See

Product

Creates an instance of a product, which is a policy type available to an applicant in the Submission Manager screen in PolicyCenter. A product is a pattern that creates new policy instances. PolicyCenter lists each product on a separate row of the New Submissions screen. Each product pattern contains at least one PolicyLinePattern.

PolicyLinePattern

Creates an instance of a policy line for a specific line of business, such as businessowners or personal auto. Each policy line pattern contains any number of clause patterns. A clause pattern is a generic term that refers to a coverage pattern, exclusion pattern, or condition pattern.

CoveragePattern

Creates an instance of a coverage, which is a type of loss covered by a policy. A coverage pattern creates an instance of a coverage on a specific policy line.

ExclusionPattern

Creates an instance of an exclusion, which is a type of loss explicitly not covered by a policy line. An exclusion pattern creates an instance of an exclusion on a specific policy.

ConditonPattern

Creates an instance of a condition, which is a contractual obligation that is neither providing nor excluding coverage. A condition pattern creates an instance of a condition on a specific policy.

CoverageTermPattern

Creates an instance of a value that specifies the extent, degree, or attribute of coverage, exclusion, or condition. Coverage terms measure or further define a specific clause pattern. One example of a coverage term is a deductible.

ModifierPattern

Creates an instance of a modifier that affects the calculation of the policy premium.

Creating or modifying a line of business requires working with the product model with two different skill sets: programming skills and business domain skills. In some organizations, a single person performs all requires steps. In other organizations, software developers perform the programming steps while business analysts perform product model design steps. Guidewire provides separate tools for each aspect:

  • Guidewire Studio
    • Creates entities and defines their physical implementation in the PolicyCenter database
    • Defines business rules
    • Creates and modifies the PolicyCenter user interface
  • Guidewire Product Designer
    • Configures the product model patterns that define a line of business
    • Defines system tables that support the business logic needed by the line of business

Both tools can run on a single computer together with a development instance of PolicyCenter. Alternatively, Product Designer can run on a separate application server enabling multiple business analysts to edit the product mode at one time. The Product Designer Guide describes both installation scenarios.

Another part of a complete line of business is the set of forms that accompany each product. PolicyCenter can be integrated with a forms issuance system and each line of business can be configured to infer the forms required for each policy instance. For information about form patterns, see Policy form pattern administration for information about adding form patterns to products and policy lines.