In Diamond, Tiering allows for the transferring of policies across tiers or company / state / lines of business both through a "Manual" underwriting process and an "Automatic" underwriting process. Before using this process:
Authorities: There are two (2) authorities listed in those available in the Policy Processing group users must have:
Company / Tiering - Overall: This grants authority to access the Tier button on the Policy Control toolbar and have the system retrieve the configurable underwriting project that was set up for the version of the policy.
Company / LOB Tiering - Allow Manual: This gives the same authority as "Company / Tiering - Overall," but it also displays a screen that prompts the user for a company / state / line of business to be selected.
Diamond System Editor: The system setting, "Display Tiering," in the Policy folder must be set to "True" (Enabled). This displays the Tiering button on the Policy toolbar.
For "Manual" Tiering, if the user has the "Company / Tiering - Allow Manual" authority, a screen is displayed that prompts for a company / state / line of business to be selected. For "Automatic" Tiering, if the user leaves the Company combo box blank and then selects the Okay button OR does not have the "Company / Tiering - Allow Manual" authority, Diamond performs "Automatic" Tiering.
For "Automatic" Tiering, the system automatically retrieves the configurable underwriting project that was set up for this version of the policy. It looks at the policy and determines what Tier the policy should be placed in. In other words, what company / state / line of business it should be rated with. With this version, the only thing that changes is the company, but it is possible to change the other two (2) options: state and line of business. (Note: This is not recommended unless in very special cases.)
In either case, if the configurable underwriting engine returns a company / state / line of business (i.e., "Automatic") or, if the user selects them (i.e., "Manual), the new version is then determined. It is different from the original version, and the policy is then copied over to a new quote, giving it a new version. If the version_id stays the same but the ratingversion_id, addformsversion_id or the underwritingversion_id changed, they will be updated in the original policy and a new image will not be created since no new coverages were added or deleted.
A policy can be "automatically" tiered when doing a Rewrite Full transaction. When selecting "Automatic Tiering" as the transaction reason, the system first rewrites a "New" business policy in the original version. Then, the configurable underwriting engine is retrieved, which returns the company / state / line of business it should be moved to. If a new version_id results from the new company / state / line of business, then a quote is created from the rewritten policy. Its version is changed to the calculated version for the company / state / line of business chosen.
Policies can also be "automatically" tiered when doing a Cancel Rewrite transaction. When selecting "Automatic Tiering" as the transaction reason, the original policy is canceled and a rewritten "New" business policy is done using the original version. Next, the configurable underwriting engine is retrieved to return the company / state / line of business it should be moved to. If a new version_id results from the new company / state / line of business, the quote is created from the rewritten policy. Its version is changed to the calculated version for the company / state / line of business chosen.