Rating Management component naming conventions best practices

Guidewire recommends a number of naming best practices for Rating Management components. Naming conventions are intended to provide consistency, and make it easier to identify components by line of business and purpose.

Component names are not required to be unique, but the identifying code must be unique. For easy identification, Guidewire recommends that you use the same value for both component name and code.

Rating Management component	Naming convention	Example
Rate book	`PackageName` + `DescriptiveName`	`PAStandardCA` – Standard for Personal Auto in California
Rate routine	`PackageName` + `DescriptiveName` + `_rr`	`PAAssignDriver_rr`
Rate table	`PackageName` + `DescriptiveName` + `_VersionNumber`	`PACoverageBaseRate` `PACoverageBaseRate_v2`
Parameter set	`PackageName` + `DescriptiveName`	`PAVehicleStandardSet`

Package name

Follow these conventions for policy line package name:

Use capital letters, such as CP or PA for Commercial Property or Personal Auto policy lines, respectively.
If the rating component applies to all lines of business, use ALL.

Descriptive name

Follow these general naming conventions for DescriptiveName:

Use mixed case with the first letter of each word capitalized.
Do not use spaces.

Rate books

For DescriptiveName:

If you have multiple rate books per policy line, then add underwriting company, jurisdiction, or offering codes to differentiate the books.
It is not necessary to append the words book or rate book.

Rate routine

Append _rr to easily identify rate routine codes as distinct from rate table codes.

For DescriptiveName:

For a rate routine that calculates premium for a specific coverage, use the coverage code.
For example, a rate routine that calculates premium for Comprehensive coverage (PAComprehensiveCov is the code) on a Personal Auto policy can be named: PAComprehensiveCov_rr.
If a coverage has different rate routines that calculate premium for different types of risks, append the risk type to the rate routine names. To use fewer characters, you can abbreviate the risk type.
For example, a rate routine that calculates premium for Collision coverage for occasional drivers (abbreviate to OD) in a Personal Auto policy can be named: PACollisionOD_rr. The default rate routine for Collision coverage can be named: PACollision_rr.
If a rate routine applies to multiple coverages, then create a descriptive name. The name can be based on the covered object. Add the word Coverages at the end.
For example, a rate routine that calculates premium for certain coverages with a covered object of PersonalVehicle can be named: PAPersonalVehicleCoverages_rr.

Rate table

In DescriptiveName, do not include the word table. When doing a rate table lookup in a rate routine, PolicyCenter displays table: before the name.

Rate tables do not have a version field. However, you can copy a rate table and create the equivalent of a new version by including a version number in the name and code.

If you plan on versioning, then use a versioning identifier as a suffix. This can be a version number or additional information that helps you identify the version, such as _v2 or _ISO2015. You can choose to add a version number beginning with the second version.