Categories are central to how programs are rated in Oracle Insbridge.  Every component of a rating program - inputs, tables, algorithms, and outputs - are assigned a category.  


A category is used to define a logical grouping of iterative data.  For example... If you are developing a rating program for the Personal Auto line of business, you are going to have at least Driver, Vehicle, and Accident/Violation categories.  Each of these categories represent a grouping of data that is repeatable on any given policy.


Insbridge uses categories to iterate the logic you define.  Continuing with the Personal Auto example, you may need a table lookup for a discount factor that can be different for every driver on the policy.  In this case, you would create a table and assign the table to the Driver category.  During rating, your table lookup will execute for every driver on the policy.


If you're having trouble defining categories for the line of business you are rating, ask yourself these questions:

  1. What inputs and outputs are repeatable?  It's important to look at both the inputs and outputs when determining what categories are needed.  Integration and rating complexity can both be impacted by this.
  2. What rating logic is repeatable?  Categories can be used to avoid duplicating logic, so use this to your advantage.  You may uncover additional categories outside of just what's needed for inputs/outputs.
  3. How do the categories relate to each other?  Insbridge allows you to setup parent/child relationships with categories.  You must be aware of how data is shared across categories for efficiency purposes.