Generic schedule data model

To be able to add schedules to clauses in a line of business in Product Designer, you must extend the generic schedule data model. Generic schedules have a flexible data model. The generic schedule data model includes one set of entity types that have many columns. Predefined columns include StringCol1, StringCol2, TypeKeyCol1, PosIntCol1, and so forth. These columns are not inherently descriptive, but instead provide a generic way to store information. When configuring a new schedule, you use these generic columns and provide a description for them in the context of the schedule.

For example, Homeowners has an Exclude Y2K Computer Related And Other Electronic Problems scheduled coverage that includes:

  • Serial Number column that is stored in StringCol1
  • Description column that is stored in StringCol2
  • Date of Appraisal column that is stored in DateCol1
  • Property Damage Excluded column that is stored in BoolCol2

The generic schedule data model defines a schedule coverage, condition, or exclusion and a set of scheduled items.

The following data model displays the key entities related to schedules. In the base configuration, the Homeowners line contains examples of scheduled clauses that use generic schedules. You can implement scheduled clauses in other lines of business by extending the generic schedule data model to coverables in that line. See the Data Dictionary for a complete list of generic schedule entities and properties.


Generic schedule object model.

In the illustration above, XX is an abbreviation for the policy line. Coverable is a placeholder for the name of the coverable. Replace Cov with the clause type: Cov for coverage, Cond for condition, and Excl for exclusion.

Entities and classes relevant to generic schedules include:

  1. Coverable – The coverable, such as line, dwelling, vehicle, among others. Schedules can be associated with coverages that hang directly off those coverables (such as a dwelling or a vehicle).

    In Homeowners, this is HOPLine.

  2. XXCoverableScheduleCov– The scheduled clause object which implements the Schedule interface. The scheduled clause object is a clause entity for clauses that have schedules attached.

    An example in Homeowners is HOPLineScheduleCov, which is a subtype of HOPLineCov.

  3. XXCoverableScheduleCovImpl – This class performs actions such as creating, adding, or removing scheduled items. For example, HOPLinSchedulCovImpl.gs creates the HOPLineScheduleCov entity.

    The Schedule interface is implemented by AbstractScheduleImpl.gs. You extend this implementation class for each schedule you define.

    An example in Homeowners is HOPLineScheduleExclImpl.gs. This class extends the AbstractProductModelScheduleImpl interface and ultimately the Schedule class.

  4. XXCoverableScheduleCovItem – The scheduled item for schedules attached to clauses for XXCoverable.

    Examples:

    • Homeowners – HOPLineScheduleCovItem
    • General Liability – GLLineScheduleCovItem
  5. XXCoverableSchCovItemCov – Coverage associated with a scheduled item. Available only on a scheduled coverage item.

    Examples:

    • Homeowners – HOPLineSchCovItemCov
    • General Liability – GLLineSchCovItemCov
  6. CoverageTerm – For generic schedules with coverage terms, one or more coverage terms such as limits and deductibles. Those coverage terms are on the coverage associated with the scheduled item.