Insurance Industry Framework Implementation Guide

© Copyright 2008 Pegasystems Inc., Cambridge, MA
All rights reserved. This document describes products and services of Pegasystems Inc. It may contain trade secrets and proprietary information. The document and product are protected by copyright and distributed under licenses restricting their use, copying distribution, or transmittal in any form without prior written authorization of Pegasystems Inc. This document is current as of the date of publication only. Changes in the document may be made from time to time at the discretion of Pegasystems. This document remains the property of Pegasystems and must be returned to it upon request. This document does not imply any commitment to offer or deliver the products or services described. This document may include references to Pegasystems product features that have not been licensed by your company. If you have questions about whether a particular capability is included in your installation, please consult your Pegasystems service consultant. For Pegasystems trademarks and registered trademarks, all rights reserved. Other brand or product names are trademarks of their respective holders. Although Pegasystems Inc. strives for accuracy in its publications, any publication may contain inaccuracies or typographical errors. This document or Help System could contain technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Pegasystems Inc. may make improvements and/or changes in the information described herein at any time.

This document is the property of: Pegasystems Inc. 101 Main Street Cambridge, MA 02142-1590 (617) 374-9600, fax: (617) 374-9620 www.pega.com Insurance Industry Framework Document: Implementation Guide Software Version: 3.3 Updated: June 2008

Contents
Chapter 1: Before You Begin .............................................................................................. 1-1  What Is the Insurance Industry Framework? ................................................................... 1-2  Insurance Industry Framework ................................................................................. 1-3  Understanding the Insurance Product ............................................................................. 1-4  Insurance Products .................................................................................................. 1-4  Insurance Components ............................................................................................ 1-5  Your Framework and Process Commander .................................................................... 1-6  Who Should Read This Document? ................................................................................ 1-7  Education and Training ............................................................................................ 1-7  Other Information to Read ............................................................................................... 1-8  Chapter 2: Deploying the Framework ................................................................................. 2-1  Documenting Your Application ........................................................................................ 2-2  Creating a New RuleSet .................................................................................................. 2-4  Creating a RuleSet Version ............................................................................................. 2-5  Adding Your RuleSet to the Administrator’s Access Group ............................................. 2-6  Creating Your Top-Level Class ....................................................................................... 2-7  Copying the Work Class Group to Your Class Hierarchy ................................................ 2-8  Copying the Data-Admin-DB Table Instances ................................................................. 2-9  Setting Up Calendars .................................................................................................... 2-10  Setting Up Correspondence .......................................................................................... 2-11  Sample HTML and Template ................................................................................. 2-13  Printing and Faxing ....................................................................................................... 2-14  Setup Requirements Before Extending ......................................................................... 2-15  Chapter 3: What Is Already Set Up .................................................................................... 3-1  System Administrator Account ........................................................................................ 3-2  RuleSet Hierarchy ........................................................................................................... 3-3  Class Structure ................................................................................................................ 3-5  Class Inheritance ..................................................................................................... 3-5  Class Structure for Work Objects ............................................................................. 3-6  Data Classes ................................................................................................................... 3-7  Interface Classes............................................................................................................. 3-8  PegaIns-Interface-InsurancePolicy .......................................................................... 3-8  PegaIns-Interface-PolicyLink.................................................................................... 3-8  PegaIns-Interface-AgencyLOB................................................................................. 3-8 

iv

Insurance Industry Framework

PegaIns-Interface-Contact ....................................................................................... 3-8  PegaIns-Interface-Roles .......................................................................................... 3-9  Data-Admin-DB-Table .............................................................................................. 3-9  Work Object Naming Conventions ................................................................................ 3-10  Default Work Groups and Workbaskets ........................................................................ 3-11  Default Operators and Access Groups .......................................................................... 3-12  Predefined Access Roles and Privileges ....................................................................... 3-13  Predefined Work Parties ............................................................................................... 3-14  Correspondence Templates .......................................................................................... 3-15  Process Commander Templates ............................................................................ 3-15  Framework Templates ........................................................................................... 3-16  Sample Data to Test Use Cases ................................................................................... 3-17  Contact Search.............................................................................................................. 3-18  Policy Search ................................................................................................................ 3-22  Policy Search Implementation ................................................................................ 3-22  Search Types and Implementation Rules .............................................................. 3-23  Chapter 4: Extending the Framework ................................................................................. 4-1  Extending the Work Class Structure................................................................................ 4-2  Inheriting from the PegaIns-Work- class .................................................................. 4-3  Creating New Work Flows ........................................................................................ 4-6  Integrating with Systems of Record and Policy Administration systems .................. 4-7  Extending the Data Class Structure ................................................................................ 4-8  Inheriting from the PegaIns-Data- Class Structure ................................................... 4-9  Underwriting rules .................................................................................................. 4-11  Inheriting from the PegaIns-Interface- Class Structure .......................................... 4-12  Working with Insurance Work Objects........................................................................... 4-13  Application – New Business ................................................................................... 4-13  Understanding the Preconfigured Workflows ......................................................... 4-25  ChgPolicy – Endorsements .................................................................................... 4-28  Configuration of Products (Policies) ....................................................................... 4-37  Pricing Details ........................................................................................................ 4-40  Agencies and Agents .................................................................................................... 4-41  Agencies ................................................................................................................ 4-42  Agents .................................................................................................................... 4-42  Agent Profiles ......................................................................................................... 4-42  Associating Agencies to Policies ............................................................................ 4-43 

............................................. 6-5  Writing Policy Rules ................................................................................................................................................................................................................................................................................................................................................................................................................... 5-12  Variable Universal Life Pricing Model ... 7-1  ACORD Processing Flow and Architecture ............................ 5-4  Pricing activities in the PegaSP Class................................................................................................................................................................................... 6-1  Integrating Contact Data ...................... 5-18  Commercial Auto................................................................................................................ 5-8  Term Life Pricing Model .................................................................................................................................................................. 5-6  Business Policy Owner’s Product Pricing Model ....................................... 5-4  Pricing Activities in the Framework ........................... 6-4  Integrating Policy Data ................... A-1  ..... 5-2  Standard Pricing Rules......................................................................................................................................................... 7-2  ACORD Processing Rules ................................................................................................................................................................................................................................... 5-13  Automotive Pricing Model........... 7-11  Application Specific Rules ...... 7-19  Adding a New Product.................................................................. 5-20  Homeowners Pricing Model .... 6-2  Writing Contact Data Rules .................................................... 4-45  Matching Drivers to Vehicles ................ 6-8  Integrating Agent and Agency Data ......... 7-22  Appendix A: Database Tables .................................. 4-50  Chapter 5: Pricing Rules and Models .......................................................................................................................................................................................................................... 6-7  Searching Policy Rules ............................................................................................. 6-3  Searching Contact Data Rules ........................................................................................................................................ 7-13  Building Rule-Obj-XML rules ........... 6-2  Reading Contact Data Rules ....................................... 7-4  General Rules ........................................................................................ 7-20  Sample Messages .................. 7-5  Parsing Rules ............................................................................................................................................................................................. 5-21  Chapter 6: Interfacing with External Systems ...................... 6-9  Chapter 7: Processing ACORD XMLMessages........................................ 5-18  Personal Auto..................................................................Insurance Industry Framework v Sample Agent and Agency Data ..................... 6-5  Reading Policy Rules ...................................................................................................................................................................................................................................................................................................................................................................................................... 5-1  Pricing Overview .................................................................. 4-48  How the Framework Associates Drivers to Vehicles .......................................

..... A-26  Foreign Key Relationships .................................................................................................................................................................................................................... A-21  Referencing Tables and Columns ... A-8  Columns ................................................................................... A-23  Constraints ......................................... A-22  PA_BUSINESSUNIT_LINK ............................................................................................................................................................... A-14  Columns ........................ A-8  Constraints ...................................................................................................................................................................................................................................... A-12  Columns ................................... A-14  Constraints ............................................................. A-25  Constraints ............................ A-15  Foreign Key Relationships ................................ A-13  PA_ADDRESS ............................................... A-28  Columns ..... A-17  Referencing Tables and Columns ........................................ A-12  Constraints ....................................................................................................................................................................................................................................................................................................................................................... A-10  Foreign Key Relationships ...................................................... A-19  Columns ............................................................................. A-17  Columns ....................................vi Insurance Industry Framework Database Tables ............................................................................................. A-25  Columns ......................................... A-24  PA_COMMUNICATION_OPTIONS ........ A-3  Constraints ...................................................... A-27  PA_COMMUNICATION_TYPES ...... A-16  PA_ADDRESS_TYPE ..... A-7  IIF_POLICY_LINK ................... A-30  ....................... A-29  Foreign Key Relationships .................................. A-6  Large Object (LOB) Storage Attributes ....................................................................................................................................................................................................................................................................................................................................................................................... A-18  PA_BUSINESSUNIT ..................................................................................................................................................................................................................................................................................................................... A-17  Constraints ............................................................................................................................................................ A-11  IIF_AGENCY_LOB .......................................................................... A-7  Referencing Tables and Columns .............................................................................................................................................................................................................................. A-3  Columns .................................................................................................................................................................................................................................................................................................................... A-28  Constraints ................................................................................................................................................................................................................................................................. A-2  IIF_POLICY .................................................................................................. A-19  Constraints ..... A-23  Columns ..................................

.................................................. A-51  Referencing Tables and Columns ................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................. A-45  Columns ............................................................................... A-43  Constraints ................................................................................................................................................................. A-37  PA_CUSTOMER_TYPE ......................................................................................................... A-41  Constraints ........... A-42  Referencing Tables and Columns .............................................. A-50  Columns ............................................................ A-51  .......................................................................... A-38  Columns ............................................................................................................... A-31  Columns ................................................................................................... A-41  Columns ...................................................................................................................................... A-50  Constraints ........................................................................................... A-35  Constraints ..................................................................................... A-33  Foreign Key Relationships ........................................................................................................................... A-34  Referencing Tables and Columns ........Insurance Industry Framework vii PA_CONTACT ................................................................................................................................................................................................................................... A-34  PA_CONTACT_BUSINESSUNIT_LINK .................................................. A-45  Constraints ......................... A-47  Columns ............................................ A-43  Columns .......................................................................................................................................................................................................................................... A-44  PA_PRODUCT .......................................................... A-46  PA_PRODUCT_TYPE .................................. A-48  PA_ROLES ................................................................. A-36  Foreign Key Relationships ......................................... A-39  Referencing Tables and Columns .................................. A-31  Constraints .............. A-38  Constraints ............................................................................................................................................................................. A-42  PA_NOTES ......................................................................................................................................................................... A-35  Columns ........................................ A-47  Constraints ..................................................................................................................... A-40  PA_INDUSTRY .........................

viii Insurance Industry Framework .

) Some team members understand the application and technology architecture of the environment into which the Framework is to be deployed. and extend the Insurance Industry Framework (IIF) for initial development and production use. business processes. and activities.Chapter 1: Before You Begin This document describes how to install. claims. including interface requirements of related applications ■ . It assumes that: ■ ■ ■ ■ PegaRULES Process Commander (Process Commander) is already installed You have taken the appropriate training courses Some team members are PegaRULES Process Commander certified Some team members have business expertise at a detailed level in the application areas to be supported (such as insurance products. deploy. agreements.

common services. outline product specifications. ■ Integral to the Insurance Industry Framework is the capability for defining and managing new products configurations. and basic workflows and activities that span all lines of business and most of the insurance value chain. Starter Kits in three areas (Product Management. Pegasystems’ Product Configurator Solution Framework is used in conjunction with this Framework to provide this capability. and decreasing the time to gain Return On Investment (ROI). and screen flows that serve as best practice implementations. your own custom built applications. data mapping.. properties. and act as a model for each instantiation of the product as a specific agreement as “bought” by a customer. methods. leveraging the strengths of the Process Commander SmartBPM Suite to maximize reusability. By externalizing product rules from manual and legacy systems. rules can be more easily maintained by users. reducing the development time to create new applications.1-2 Insurance Industry Framework Implementation Guide What Is the Insurance Industry Framework? The Insurance Industry Framework provides a best practice implementation of basic insurance services to create insurance specific business applications. and structure work objects correctly. or some mix of both. the Insurance Industry Framework can also access external rules engines and existing core administration applications if expeditious to do so. mitigating project risk. These serve as starting points to extend the Framework and manage your specific business needs by means of Pegasystems provided Insurance Solution Frameworks. the business rules and calculations surrounding the sale and servicing activities. The Insurance Industry Framework has two components: ■ An insurance foundation that provides comprehensive partially attributed class structures. services. Acquiring and Retaining Business) that provide high-level work templates. . These product specifications define the structure and valid configurations of what maybe offered for sale in terms of insured objects. The Insurance Industry Framework can be the system of record for such rules and activities and these can then be leveraged in all insurance solutions that rely on detailed knowledge of the insurance product or resulting agreement. etc. coverages / benefits. as long as the basic product / agreement hierarchical structure is defined in the Insurance Industry Framework for each product type – since this is used to drive screen and workflows. However.

services. Enables circumstancing on date and jurisdiction on all relevant business rules and activities so that these are used as workflows and activities are executed.Before You Begin 1-3 Insurance Industry Framework The Insurance Industry Framework: ■ Provides a foundation that services a range of business process management applications including acquiring and retaining business (new business. . a quote maybe for a date in the future or past and be valid for 30 days during which time changes maybe made – the rules in effect for the desired start date must be correctly selected and used until the case is resolved and the data no longer required). agreements. and then to a ratified Agreement such as a Policy). Provides full support for the reuse of common product components. an agreement type work object may change from being a quote. workflows. and pricing). and more detail products rules if no other option is selected (such as calling other applications for services for licensing requirements. commonly found product structures. Provides best-practice sample definitions of insurance parties. Provides sample User Interfaces to enter basic product specifications. Please refer to your license agreement for the Insurance Industry Framework for restrictions on the use of these assets. Provides industry data and process models covering most insurance lines of business derived from IBM’s Insurance Application Architecture. endorsements. claims and product management Provides the ability to define Product Specifications used to create and maintain individual agreements including the state of the agreement. and activities. rating. (For example. and user interfaces. underwriting). to a full offer for Products and Services. ■ ■ ■ ■ ■ ■ Note: The Insurance Industry Foundation includes assets derived from IBM Insurance Application Architecture (IAA) models. to a Binder. (For example.

and uniquely deploy product (or service) specifications in a controlled and consistent manner. See the Product Configuration Framework Installation and Deployment Guide for more information about the Product Configuration Solution Framework. The amount of detail that resides in the Insurance Industry Framework as the system of record versus that held in other applications and called from Insurance Industry Framework varies for each unique implementation.1-4 Insurance Industry Framework Implementation Guide Understanding the Insurance Product An insurance product is created by defining both a product and its components. life. This combination also provides the capability to rapidly develop. is a prerequisite for product management. This Framework is included in the Insurance Industry Framework. components. services. Insurance Products Insurance products are specified as valid combinations of such things insured objects (property. Following is a short description of some sample Insurance products that have been created using a combination of the Product Configuration Framework rules and activities and the Insurance Foundation class and attribute structure. maintain.). and features. They are at the level at which the purchase agreement is made. investments. offers to purchase. and agreements for each sample product type. The Insurance Industry Framework also provides the associated work object class structure and specialized workflows necessary to produce quotes. subcomponents. provides specifications for some sample insurance products. locations. coverages and benefits. and terms and conditions that can be quoted and offered for purchase under a set of predetermined circumstances (who may buy / sell / dates). enables you to define products (saleable packages of insurance coverages / benefits and services) in terms of standard and optional packages. and is used to acquire and retain business product functionality. leveraging the imbedded Product Configuration Framework. An insurance product may be specified to be a packaging of other products. Pegasystems Product Configuration Solution Framework is a horizontal solution that when combined with the Insurance Industry Framework. etc. The Insurance Industry Framework. financial exposure. .

and workflows in the Insurance Industry Framework include: ■ ■ ■ ■ ■ ■ Personal Lines Auto Personal Lines Homeowners Commercial Lines BOP (Business Owner’s Package) Commercial Lines Auto Term Life Variable Universal Life Note: These products contain key components and attributes only. and speeds implementation of changing business needs. they do not represent complete product specifications. and modified if they are not identical. A “where-used” capability is provided to assist with maintenance and management of components that are shared or cloned. All components can be shared across products if they are truly identical. Insurance Components Components of the Insurance Product and derived quotation and agreements include: ■ ■ ■ ■ ■ ■ ■ ■ Jurisdictions Locations Insured objects (risk units) Coverages / benefits Risks Terms and conditions Investments Services and fees.Before You Begin 1-5 Examples of product specifications. Components may consist of other components (subcomponents). or copied. renamed. . reduces risk. This greatly increases productivity. class structures.

processing logic. as they supersede the Framework defaults. database. . making it specific to your organizational needs. The rules you modify when extending the Framework are at the top level. making use of underlying technology instead of reinventing process flows (Figure 1-1). You can use the Framework RuleSets as a starting point for extending the Framework. Process Commander Frameworks Showing Layers Because Pegasystems Frameworks all share the same underlying technology. configuration processes (such as creating accounts and copying rules) are identical to those in Process Commander. Figure 1-1. Process Commander Frameworks are layered. and functions — providing the base upon which Pegasystems Frameworks are built.1-6 Insurance Industry Framework Implementation Guide Your Framework and Process Commander PegaRULES Process Commander contains a rules engine. Additional flows and rules are contained in the Framework layer and support application-specific functions (such as contact management or customer service).

For more information about Pegasystems programs and schedules.asp.Before You Begin 1-7 Who Should Read This Document? Before you install. modifying. and extending the Framework. . and troubleshooting. visit us at http://pega. deploy.com/Services/EducationalServices/Education. security. Through hands-on. and extend your Framework. and taught by certified experts for those who would like additional training. These users are presumed to be experienced with system operations. Project Managers / Business Analysts — responsible for implementing a Framework solution that can be applied to specific business requirements. maintaining. The specific user roles addressed are the following: ■ Business Managers — responsible for evaluating the Framework solution and possess a general. System Architects / Application Developers — responsible for building. it is assumed you have attended the courses listed below for your specific user role. role-based training. and ensures compliance and continuous improvement across organizations. tuning. and ongoing operational functions of the Framework such as access. non-technical understanding of its features and capabilities. System and Database Administrators — responsible for the installation. ■ ■ ■ Education and Training Pegasystems Educational Services delivers in-depth programs that are designed. students receive critical knowledge from professionals skilled in the implementation of PegaRULES Process Commander solutions. delivered.

pega. . Technical notes.com. such as Microsoft Visio. a section of the Pegasystems Support Network located at pdn. application help and configuration how-tos and tips for using PegaRULES Process Commander are also available on the PDN.1-8 Insurance Industry Framework Implementation Guide Other Information to Read Process Commander and other framework documentation is available on the Pega Developer Network (PDN). consult the vendor documentation. For information on installing or working with third-party applications.

Note: For additional information about completing any of the forms. .Chapter 2 Deploying the Framework This chapter describes how to set up the RuleSet. RuleSet version. use the PegaRULES Process Commander Application Developer Help and the Pega Developer Network (PDN). and class structure to begin deployment of the Framework and to build your application while protecting the delivered Framework structure.

The Application menu provides access to information about your application.2-2 Insurance Industry Framework Implementation Guide Documenting Your Application Before you begin the deployment process. Complete the pop up dialog to control which rules are presented and which sections appear in the document. the section criteria includes: • All rules • Rules changed between identified dates • Highest version for each rule Which detailed chapters to include: • Decision logic • Integration • Rule inventory and update comments for each rule − − The short description from the rule form appears with each rule listed. making it easy for any developer to continue where you left off. it is important to understand what classes. rules. You can use the following: ■ Preflight — to evaluate the flow rules. . All PegaRULES Process Commander Frameworks include a self-documenting feature that enables you to develop and document your application simultaneously. Use the tools and reports described below along with this document to deploy. and extend the Framework. You can choose: ■ − Which summary chapters to include: • Application overview • Work class hierarchy • Process hierarchy and diagrams Which rules and versions. flow action rules. Document Button — to produce a Microsoft Word document listing all the rules associated with the selected application. understand what has been delivered. section rules and activities against the design and implementation principles known as SmartBuild guardrails. and flows already exist.

You can click a rule name to open the rule. Choose Flow Explorer for the flow. . Click the Process Slice icon. Lines connect the starter flows to the subflows. Open one of the flow rules. To begin: 1. 3. You can: ■ Check By Description? to view the short description text within the rectangle for each flow rule or leave the box unchecked to display the Flow Type key part. You can then create a list view report that shows the information you entered for each rule. As you extend your Framework.Deploying the Framework 2-3 ■ Inventory Button — to produce an interactive HTML report that lists all the rules associated with the application sorted by the Applies To class. The Flow Explorer is available from the Process Slice (Facility) on the Developer Portal. Subflows (called Branched To flows) are referenced by a Split-Join or Split-forEach shape appear to the right. Click the related rules toolbar button. It lets you display the starter flows and helps you to understand the relationships among the flow rules in the selected application. complete the Full Description and Usage fields on the History tab of each rule form. 2. Adjust the levels to determine how many levels are presented. 4. ■ You can also select the View > Rules option to run several different rule reports. Enter information in these fields that explains what the rule is for and how it is used. Starter flows (those that create new work objects) appear at the left of the display.

2-4

Insurance Industry Framework Implementation Guide

Creating a New RuleSet
The RuleSet you create lets you tailor your Framework to suit your production environment. RuleSets also provide security, version control, and the ability to move your application to a different Process Commander environment. Give your RuleSet a name that helps you manage and identify its contents. Your RuleSet name can be up to 255 characters long, must start with a letter, and should contain only letters, and digits. Use names that are short and easy to remember. The first part of the name should represent your company and the second part should represent the application content or purpose. For example, you might use your company’s stock ticker symbol and then add something representing the application purpose or its contents.

To create a new RuleSet:
1. Use the Class Explorer and select Rule- > RuleSet- > Name. A list of RuleSets appears. 2. Click New. The New form appears. Complete and Save the New form. The RuleSet form appears. 3. Complete the Security tab sections. 4. Go to the History tab and complete the Full Description and Usage fields. 5. Save the RuleSet.

Deploying the Framework

2-5

Creating a RuleSet Version
Each RuleSet has a version number that Process Commander uses (along with other criteria) when determining the correct business rule to apply in each situation as work is processed. Version numbers let you make changes without impacting the existing version. When you create a RuleSet, you must create the initial version number, 01-01-01, for that RuleSet. Use the required format of xx-yy-zz, where xx is the major version, yy is the minor release within that version, and zz is the interim, or update level within that release.

To create a RuleSet Version:
1. Use the Class Explorer and select Rule- > RuleSet- > Version. 2. Click New. The New form appears. Complete and Save the New form. The RuleSet Version form appears. 3. Complete the Security tab sections. 4. Go to the History tab and complete the Full Description and Usage fields. 5. Save the RuleSet version.

2-6

Insurance Industry Framework Implementation Guide

Adding Your RuleSet to the Administrator’s Access Group
Before users can access a new RuleSet, you must give them access by adding the RuleSet to each access group for the users who need it. Before doing so, you must add your custom RuleSet to the administrator access group (with which you logged in) so that you can work with the RuleSet and continue configuring your application. (See Chapter 3, “What is Already Set Up” for a list of the default access groups and users.)

To add your custom RuleSet to the administrator access group:
1. From the View menu, click Organization > Access Groups 2. Click the administrator access group for your application to display the rule. Figure 2-1 shows an example using the PegaInsure access group. The PegaInsurance application shown under Applications on the left specifies the RuleSets that you need for the Insurance Industry Framework.

Figure 2-1. Example Showing Administrator Access Groups 3. Insert a blank field at the top of the Production RuleSet list and enter the name of your RuleSet. 4. Go to the History tab and complete the Full Description and Usage fields. 5. Click Save. Log off and back in to access your RuleSet.

Deploying the Framework

2-7

Creating Your Top-Level Class
Your application uses a hierarchical class structure to define work objects so they can share common attributes and control rule resolution. A top-level class is the starting place for your class structure. For simplicity and clarity, use the same (or similar) names for the RuleSet and its top-level class. In many cases, you may find it useful to define the top-level class as the company name. For example, SampleCo- could be the top-level class name for the company SampleCo.

Naming conventions:
■ ■ ■ ■ Start names with a capital letter. Names are case sensitive. Alphanumeric characters are permitted. Significant letters should be uppercase for legibility.

To create a top-level class:
1. Use the Class Explorer and select Rule- > Obj- > Class. A list of classes appears. 2. Click New. The New form appears. Complete and Save the New form. The Class form appears. 3. Complete the Basic and History tabs. (Complete the Restrictions tab if you want to limit which other objects can reference this class.) 4. Click Save.

select Database > Clone Class Group. The first Direct Inheritance Wizard screen appears. and they must be unique across your organization (the application prevents you from creating a duplicate). To copy a class group to your class hierarchy: 1. 4. Many rules in your application reference the class data structure. The wizard creates a new set of classes (one of which corresponds to a class group) that matches the classes below a specified class.2-8 Insurance Industry Framework Implementation Guide Copying the Work Class Group to Your Class Hierarchy Optionally. 2. Complete the fields and click Next. you might want to copy your work class group from your Framework into your RuleSet to provide the data structure for various types of work in your application. 3. The Clone a Class Group link in the Database section of the Administration workspace starts the Direct Inheritance wizard. The third screen appears and displays a list of generated classes. Change the RuleSet name to your custom RuleSet name so the rules are created in your RuleSet. The second wizard screen (Class Mapping) appears. . 5. Class groups are the link between your class structure and the underlying database. On the Tools menu. Scroll down and click Next.

Repeat for the History-ClassName-Work instances. . Scroll down until you see the instance you want to copy. Repeat for the Index-ClassName-WorkParty instances. (You only need to replace the XX portion of the name with your name. 4.Deploying the Framework 2-9 Copying the Data-Admin-DB Table Instances Optionally. Click Save As to save the instance in your class. 7.) 5. 6.> DB. select Data. The Save As form appears. 2.> Admin. Repeat for each instance that you want to copy. Open the instance and click Save As. you can copy the Data-Admin-DB-Table instance from your Framework to your class hierarchy to specify the correct database tables for your new classes.> Table to display a list of tables. From the Rules By Type Explorer. 8. To copy the Data-Admin-DB-Table instances: 1. Change the Short Description to replace the ClassName with your Class Name when appropriate and click the Save icon. 3. Change the Class Name replacing what exists with your Class Name.

delete. you can add.2-10 Insurance Industry Framework Implementation Guide Setting Up Calendars The calendar identifies business days and the hours of operation on these days. Default Calendar for 2007 . The RuleSet record is Data-Admin-Calendar. Calendars affect the following activities: ■ ■ Case types that require a work date to be a business day Service Level Rules that measure goal and deadline times in business days As part of the deployment process. typically Saturday and Sunday. Figure 2-2 shows the 2007 calendar supplied with the product. Holidays and other non-work days. and update the calendar to reflect your operation’s open business days and local holidays. The default time zone is EST. are considered non-business days. Figure 2-2.

Deploying the Framework 2-11 Setting Up Correspondence The Insurance Industry Framework comes with a few predefined correspondence templates. The advantage of defining correspondence templates in separate rules is that one header or footer. The rules define various correspondence segments such as the header. or fax — is defined in the top-level correspondence rule when it is created. Figure 2-3. and body. Master templates are based on a top-level correspondence rule and can include other rules or references to other rules. Each segment (or stream) provides a piece of the HTML code needed to generate a complete piece of correspondence. Figure 2-3 shows a representative correspondence template structure. The correspondence type — whether e-mail. phone. footer. for example. mail. Standard Correspondence Template Elements . Some correspondence rules are called top-level rules (indicated on the Prompts tab of the rule form). can be used in many correspondence rules.

2-12

Insurance Industry Framework Implementation Guide

Because the correspondence is HTML based, it provides the opportunity to create a professional look and feel to letters, e-mails, and faxes that are sent to customers and banks. See Chapter 3 What is Already Set Up for a list of preconfigured correspondence templates and correspondence fragments. E-mails are generated through capabilities built into PegaRULES Process Commander. The routing, printing, and faxing of correspondence is handled by an interface to the PegaDISTRIBUTION Manager. However, it is not necessary to have PegaDISTRIBUTION Manager installed when updating and testing changes to the templates. Correspondence will be generated, attached to the case, and can be reviewed online in its printed form. It won’t print until the interface is active.

Tip: To copy and customize the templates in your RuleSet, maintain the
same Correspondence Rule name to avoid unnecessary updates to workflow elements that call specific templates. Add templates only when no alternative is available.

Deploying the Framework

2-13

Sample HTML and Template
Figure 2-4 shows and example of the underlying HTML for a correspondence template that is used to notify a claimant via Email.

Figure 2-4. Correspondence Template —Decision Letter to Claimant via Email

2-14

Insurance Industry Framework Implementation Guide

Printing and Faxing
PegaDISTRIBUTION MANAGER is a required companion product that works with the Insurance Industry Framework to activate printers and print servers to send correspondence in print, fax, or Rich Text Format (RTF) file modes. It can also print HTML files and their associated image files. Installed independently of the framework, it is designed to run on Microsoft Windows 2000 Professional or Server or Windows XP. To install and configure the PegaDISTRIBUTION MANAGER, refer to the PegaDISTRIBUTION MANAGER (IOS) for PegaRULES Installation and Configuration Guide.

Deploying the Framework

2-15

Setup Requirements Before Extending
Ensure you have set up the following before extending your Framework: Operators — Operator IDs define the type of users who work with the Framework and the application you build. Your Framework comes with a set of predefined operator IDs that you can use to create your own. Access Groups — Operators IDs specify an access group that determines options that portal users see, RuleSets they can access, classes of work that appear in their portal, default class group of rules that users work with, and access roles. Your Framework comes with a set of predefined access groups that you can use to create your own. Access Roles — An access role is defined as having certain class access rights. Users can have one or more access roles, which are listed in access groups.Your Framework comes with a set of predefined access roles that you can use to create your own. Privileges — A privilege allows users with a particular role to execute certain functions. Privileges are associated with access roles, not directly with users. If a user has the access role with which the privilege is associated, the user has the privilege. Privileges also play a role in routing work as users can only receive work items for which they have privileges. Configuration of these rules should happen on site to guarantee that the system behaves in a manner consistent with desired business practices.

Tip: Access-Role-Obj rules (of type Rule-Access-Role-Obj) associate
access roles with the classes to which they provide access and with any relevant privileges or access settings. When you create a new access role, you must associate it with the appropriate classes. When you associate an access role or privilege with a class, you not only associate the names of the rules, but you also specify the level of access a role or privilege has to a class or the conditions under which the role or privilege can access the class. This process allows for an extremely flexible and powerful way of defining class-based security.

The topics include: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ System Administrator Account RuleSet Hierarchy Data Classes Work Object Naming Conventions Default Work Groups and Workbaskets Default Operators and Access Groups Predefined Access Roles and Privileges Predefined Work Parties Correspondence Templates Sample Data for Testing Purposes Party Search .Chapter 3 What Is Already Set Up This chapter describes defaults and samples that are set up and ready for your use. It is expected that you will use these as a basis for extending the Insurance Foundation Framework.

com install .3-2 Insurance Industry Framework Implementation Guide System Administrator Account The Framework uses the following Operator ID as the default system administrator account. Note: Operator IDs are not case sensitive. Operator ID: Password: Administrator@insco. This Operator ID gives you access to all the insurance functions. You should change this password after logging in. but passwords are case sensitive.

custom. and components. while the rules towards the top control application functions. Piif — contains the data structures and properties defined in the IBM Insurance Application Architecture and used to define entities. The top-level class is named PegaApp-. and if the rule is not found moves to the next RuleSet. Figure 3-1 shows the RuleSet hierarchy with all the Framework layers. The RuleSet order is critical to rule resolution. PegaSP — contains the rules for creating a new product by configuring components. Used by the Framework to take advantage of the external database tables and the rules to support them. Process Commander begins with the top RuleSet in this list. site-specific rules have precedence over application-specific rules. The top-level class is named PegaSP. PegaApp – contains rules that are common to all frameworks. The four RuleSets at the bottom are standard in all applications and control the underlying Process Commander operations. RuleSet Hierarchy The Framework RuleSets include: ■ MyInsCo — contains the rules that implement examples or certain industry use cases. ■ ■ ■ ■ . but will likely be overwritten.What Is Already Set Up 3-3 RuleSet Hierarchy RuleSets are arranged hierarchically. eligibility. In this manner. with the more general rules at the bottom and more specific rules at the top. validation. The top-level class is named PegaIns-. The top-level class is named Piif-. To find the appropriate rule. These rules leverage PegaInsure. Figure 3-1. and display of the objects. pricing. features. products. PegaInsure— contains the insurance functional components with definitions that inherit from or override those found in the Piif layer.

and other basic rules engine operations ■ ■ ■ ■ .3-4 Insurance Industry Framework Implementation Guide The Process Commander RuleSets include: ■ Pega-AppDefinition — contains the rules for the set of application development tools and wizards designed to capture and tie business and project goals. including connectors and services Pega-WB — internal logic and facilities Pega-RULES — activities. Java generation. and use case requirements to action implementations Pega-ProCom — workflow support and portal facilities Pega-IntSvcs — system interface support. objectives. rule resolution.

These are models that you can follow by copying them into your own RuleSet. Use class names that do not include “Pega” as a prefix thereby preserving the namespace integrity of created rules.class that are available for your use.class tree. The primary examples in inheritance. Predefined Policy Component Classes . It is expected that they will be overridden at a higher level RuleSet when appropriate. involve the definition of Agreements (Policies) and their components. create a RuleSet that inherits from the PegaInsure RuleSet.What Is Already Set Up 3-5 Class Structure When developing class and property definitions for your applications. Class Inheritance This section describes how properties are inherited in the Framework. the Framework’s Piif classes and properties are configured as generically as possible. Parties are defined in the PegaIns-Data-Party. however. Use the Class Explorer to view a complete list of the classes defined in within the Framework.class and inherit from Data-Party. Component InsuredVehicle NamedDriver AutoCoverage InsuredPropertyLocation InsuredBuilding InsuredItem Liability InsuredRisk InsuredLife Used to Represent Vehicles in an auto policy Drivers in an auto policy Specific auto coverage options and features Locations in a BOP Policy Buildings in a BOP Policy Specified items in a BOP policy General liability in a BOP policy Specific Risk options and features Life insurance coverage Figure-3-2. Policies are defined within the PegaIns-Data-InsurancePolicy. Because different systems have different requirements. Figure-3-2 lists some of the predefined component classes in the PegaInsureData-PolCmp. Policy components are defined within the PegaIns-Data-PolCmp.class tree.

PegaIns-WorkPegaIns-Work-Application PegaIns-Work-Application-ComPegaIns-Work-Application-Com-Automotive PegaIns-Work-Application-Com-BOP PegaIns-Work-Application-IndivPegaIns-Work-Application-Indiv-TermLife PegaIns-Work-Application-Indiv-VarUnivLife PegaIns-Work-Application–Indiv-WholeLife PegaIns-Work-Application-PersPegaIns-Work-Application-Pers-Automotive PegaIns-Work-Application-Pers-Household PegaIns-Work-ChgPolicy PegaIns-Work-ChgPolicy-ComPegaIns-Work-ChgPolicy-IndivPegaIns-Work-ChgPolicy-PersPegaIns-Work-ChgPolicy-Pers-Automotive . Extension Tip The structure is intentionally incomplete as it is assumed you will expand for your site.3-6 Insurance Industry Framework Implementation Guide Class Structure for Work Objects Work object types defined in the Framework are: ■ Application (new business) ■ Change Policy The class structure to support these work types may have Line Of Business specific variants as shown below.

The data classes used in the Framework are listed below.What Is Already Set Up 3-7 Data Classes Data classes define the data structures for supporting information that the Framework uses to process work. The data classes that represent different types of policies are: ■ ■ ■ ■ ■ ■ ■ PegaIns-Data-InsurancePolicy-Commercial-Auto PegaIns-Data-InsurancePolicy-Commercial-BOP PegaIns-Data-InsurancePolicy-Individual-TermLife PegaIns-Data-InsurancePolicy-Individual-VarUnivLife PegaIns-Data-InsurancePolicy-Individual-WholeLife PegaIns-Data-InsurancePolicy-Personal-Automotive PegaIns-Data-InsurancePolicy-Personal-Household The data classes that represent components used in defining a policy are: ■ PegaIns-Data-PolCmp– and its subclasses for policy components The data classes that represent parties involved in an insurance agreement are: ■ ■ ■ ■ ■ PegaIns-Data-Party-Person PegaIns-Data-Party-Person-Agent PegaIns-Data-Party-OrgPegaIns-Data-Party-Org-Company PegaIns-Data-Party-Org-Agency .

such as the PA_CONTACT and PA_ADDRESS tables among others. The InsurancePolicy class does not inherit from Account. It contains sample contact data used in the Framework. PegaIns-Interface-Contact This class inherits from PegaApp-Interface-Contact. It also contains information to facilitate policy searches. It is linked to the agency by the AgencyCode. PegaApp does not have an InsurancePolicy class to inherit from. It contains sample data for each agencies Line Of Business. Similar to the Policy class. Consideration was given to inherit from the PegaApp’s Account class. The Interface classes described below are the concrete data classes used to persist insurance policy data. It also uses the same data model that PegaApp uses to represent a contact. and specified period of time.3-8 Insurance Industry Framework Implementation Guide Interface Classes The Insurance Industry Framework uses external database tables to store its data instances for an insurance policy. PegaIns-Interface-PolicyLink This class inherits from PegaApp-Interface. but an account and insurance policy have enough differences to warrant two different classes. PegaIns-Interface-InsurancePolicy This class Inherits from PegaApp-Interface. IIF_POLICY_LINK and IIF_AGENCY_LOB tables. This gives the ability for the expansion of the IIF to use the PegaApp-Interface-Account class in the future. PegaApp does not have a PolicyLink class to inherit from. An Agency is stored in the BusinessUnit table. PegaIns-Interface-AgencyLOB This class represents the Agency LOB data. More detailed information on these tables can be found in Chapter 6: Integrating with External Systems. The PolicyLink class contains information that links the policies with contacts via roles. storing the contact information in various database tables. Each instance in this class represents a line of business that an agency is licensed to sell in a given state. It uses a simplified data model to represent insurance policies. . The remaining policy information is stored in the IIF_POLICY.

What Is Already Set Up 3-9 PegaIns-Interface-Roles Inherits from PegaApp-Interface-Roles. The following table lists the interface classes and their instances in the Data-Admin-DB-Table class. It contains sample role data used in the Framework. Data-Admin-DB-Table Interface Instances . Data-Admin-DB-Table Each of the interface classes mentioned above have associated instances in the Data-Admin-DB-Table class to identify the database information for the associated table. such as Applicant and InsuredParty. More information about these database tables can be found in Chapter 6: Integrating with External Systems. Class PegaIns-Interface-InsurancePolicy PegaIns-Interface-PolicyLink PegaIns-Interface-AgencyLOB PegaIns-Interface-Contact PegaIns-Interface-Roles Database Table IIF_POLICY IIF_POLICY_LINK IIF_AGENCYLOB PA_CONTACT PA_ROLES Database Name Sample Sample Sample Sample Sample Figure 3-3.

■ Work objects capture and process information about an individual unit of work. and making your changes. a predefined model populates key property values (such as urgency) that directly affect the work object’s relative priority and placement in operator worklists.prefix. models are applied to all the embedded components in the product definitions before the data entry screens are generated.class into your RuleSet changing its class to apply to your own installation specific class structure.3-10 Insurance Industry Framework Implementation Guide Work Object Naming Conventions There are three primary types of work objects: basic work objects. work objects. As work objects progress towards resolution. Covers tightly coordinate processing of one or more distinct. Applications use basic work objects. Each work object has a unique ID that is computed by combining a systemassigned number and a prefix defined in a pyDefault Model rule. ■ ■ When your application initiates a work object. In the case of Insurance Applications for new business. Folders are not currently used. but not all. Work objects created by this Framework use the default W. may use covers or folders. You can change the prefix or create additional prefixes by copying the Rule-Obj-Model called pyDefault in the Work. covers. some. The system normally resolves a cover work object after all its component work objects are resolved. . core property values such as priority and status are continually updated to reflect the current stage of processing. but closely related. and folders.

What Is Already Set Up 3-11 Default Work Groups and Workbaskets Figure 3-4 lists the default workbaskets used in the Framework. Default Workbaskets Description Policy applications waiting for underwriting specific assignments Policy applications created from a message that have errors in processing Policy applications that have data entry in progress . The work group is named MyInsCo-NewBusiness. Workbasket UnderwriterQueue NewBusinessErrors PartialApplications Figure 3-4.

com TSmith@TomsInsAgency Access Group PegaInsureWorkUser PegaInsureUnderwriter PegaInsure PegaInsureWorkUser PegaInsureWorkManager PegaInsureACORD Portal Name WorkUser WorkUser DeveloperSP WorkUser IIFWorkManager DeveloperSP Figure 3-5.com Administrator@insco. All passwords are set to install.3-12 Insurance Industry Framework Implementation Guide Default Operators and Access Groups The Framework comes with sample operators and access groups (Figure 3-5).com UnderWriter@insco. Insurance Industry Framework Operators and Access Groups . Operator ID Broker@insco.

Rule-Access-Role-Obj instances have been added for WorkMgr4 and User4 giving them Read-Write access to the PegaIns-DataInsurancePolicy database table. Each of these roles has a corresponding rule in RuleAccess-Role-Obj where you can define specific privileges for each of these roles.What Is Already Set Up 3-13 Predefined Access Roles and Privileges Your Framework includes a set of predefined access roles. . These roles are defined as Rule-Access-Role-Name instances and are associated with an operator’s access group. In the Framework.

.3-14 Insurance Industry Framework Implementation Guide Predefined Work Parties The Framework defines work parties in a record called Rule-Obj-Workparty for the PegaIns-Work.types and references the following party roles: ■ ■ ■ ■ ■ ■ ■ ■ Applicant Broker Originator Underwriter Beneficiary AuthorizedParty Interested Agent Note: When the product is commercial. the party classes are defined to reflect that difference. and are changed to -party-org instead of -party-person.

Mail. Fax. and you will need to copy them to your RuleSet to modify them to meet your requirements. Process Commander Templates Figure 3-6 lists templates that are not used in the Framework workflows but are part of Process Commander and are available for your use. Fax. Mail.What Is Already Set Up 3-15 Correspondence Templates The Framework comes with a number of sample correspondence templates and fragments. PhoneText Email. Mail Email Email Email Email Email. Mail Email Email. Figure 3-6 and Figure 3-7 list the templates that come with Process Commander and the Framework. mail Email Email Email Email. Fax. Mail. PhoneText Email Email. If you decide to use any of these templates. Mail. remember that they are samples. fax. Template AcknowledgeSample DeadlineTimeReminder Details ExternalAcknowledgeSample ExternalRequest ExternalRequestBrief ExternalSample Footer GoalTimeReminder Header LateTimeReminder NewAssignment NotifyReopen PromptSample QuestionAboutItem ResolutionDetails ResolutionSample Type Email. Fragments are defined as instances of Rule-Corr-Fragment and are used in compiling correspondence templates. Fax. PhoneText Email. Templates are defined as instances of Rule-Obj-Corr. Mail Email. Fax. PhoneText Purpose Internal acknowledgement of a work object Notification that a work object has passed its deadline Details of a work object External acknowledgement of a work object Request for information about a work object assigned to an external user Assignment of a work object to an external user Correspondence with external party regarding a work object Signature for correspondence Notification that a work object has passed its goal time Salutation for correspondence Notification that a work object is late Notification of a new assignment on a worklist Notification that a work object has been reopened Prompt for user input Request for more information about a work object Resolution details for a work object Notification that a work object has been resolved Figure 3-6. Fax. Fax. Process Commander Correspondence Templates .

copy them to your RuleSet to modify them to meet your requirements.3-16 Insurance Industry Framework Implementation Guide Framework Templates Figure 3-7 lists templates that are used in the Framework workflows. Framework Correspondence Templates . These are samples and if you decide to use any of these templates. Template NewPolicy PolicyBinder ExternalRequest Type Email Email Email Purpose Acknowledge creation of the new policy The binder for the new policy External request to adjusters Figure 3-7.

or contact. This sample party.data is stored in external database tables provided by the PegaApp layer. Table Name IIF_POLICY IIF_POLICY_LINK Description Primary table to store insurance policy information Stores relationships between insurance policies. The Framework also provides sample data for policies and endorsements to those policies (policy transactions) which is also stored in external database tables. contact and business unit associations Primary table to store information about contacts. The Framework uses sample data to represent its party data.What Is Already Set Up 3-17 Sample Data to Test Use Cases Sample data is provided for testing purposes. For a complete list of all database tables shipped with the Framework. Framework Sample Data Tables . ie a Master Agent and its Agencies IIF_AGENCYLOB PA_ROLES PA_CONTACT PA_ADDRESS PA_COMMUNICATION_OPTIONS PA_BUSINESS_UNIT PA_CONTACT_BUSINESUNIT_LINK PA_BUSINESSUNIT_LINK Figure 3-8. Figure 3-8 lists the tables that contain sample data used by the Framework. including agencies Stores relationships between a contact and a business unit Stores relationships between business units. including agents Stores address information about contacts and business units Stores communication information about contacts and business units Stores information about business units. contacts and the roles the contacts have in the policy Stores Agency Line Of Business information Stores role information for policy. see Appendix A: Database Tables.

This table is followed by processing details for the key rules in the search process. Contact Search Rules .3-18 Insurance Industry Framework Implementation Guide Contact Search The contact search functionality is implemented in the Framework using the searching capability provided in the PegaApp software layer. RuleType Flow FlowAction Flow FlowAction FlowAction Flow Activity Activity Activity Activity Activity Activity Activity Activity Activity Activity Activity Class PegaIns-Work PegaApp-WorkPegaApp-WorkPegaApp-WorkPegaApp-WorkPegaIns-WorkPegaIns-Work PegaApp-WorkPegaApp-WorkPegaApp-WorkPegaApp-WorkPegaIns-Work PegaIns-Work PegaIns-Work PegaApp-WorkPegaIns-Work PegaIns-Work Rule IIFAppContactSearch AppFindContact AppGetContact AppSelectContact AppFindBusinessUnit AppGetBusinessUnit IIFAppGetContactDetails AppReadContactInfo AppListAddressesForContact AppCommOptionsForContact AppGetContactBUAssociations IIFCreateContactParty IIFMapPartyDetails IIFAppGetBusinessUnitDetails AppReadBusinessUnitInfo IIFCreateBusinessUnitParty IIFMapBusinessUnitPartyDetail s Description Flow to handle contact search functionality specific to the Framework Enter search criteria and execute search Handles list of contacts resulting from search Selects a contact from the list provided Enter search criteria and execute search Handles list of business units from search Gets contact details for selected contact Reads contact information Gets addresses for contact Gets communications options for contact Gets associations between contacts and business units Creates the appropriate pyWorkParty page in the work object Maps data from the contact search data into the work object Gets business unit details for selected item Gets business unit info from database Creates the appropriate pyWorkParty page in the work object Maps data from the business unit search data into the work object Figure 3-9. The rules provided in PegaApp that implement contact searching have been extended and modified to fit the specific Framework requirements For more information on these rules see Chapter 6: Integrating With External Systems. Figure 3-9 lists the rules involved in executing a contact search.

it calls the IIFAppGetContactDetails activity to retrieve the contact data Then. All other flows do not set this parameter. This is set to True in the Commercial product NB flows.AppFindContact flow action to enter the search criteria and present a list of contacts that fit the search criteria When one contact is selected.that calls the AppAddContactFromSearch flow to handle adding a new contact . PartyRole.AppFindContact to validate and setup search criteria PegaApp-Work-. This PartyRole parameter signifies the role that this contact has in the insurance policy.AppFindContact HTML to set up the display for entering search criteria Calls the post activity PegaIns-Work. Claimant. exits PegaApp-Work. ■ This flow: – – – Uses the PegaApp-Work. AppGetContact Flow This flow: – – Calls the AppSelectContact flow action to handle the contact search. It accepts two parameters: ■ BUSearch – True if this should search for a BusinessUnit.IIFAppContactSearch Flow This flow handles searching for both a business unit and a person contact. etc. Calls the AppAddContactStart flow action. ie. The default value is False. It is used to map the contact data into the correct pyWorkParty page group for this role. InsuredParty.What Is Already Set Up 3-19 PegaIns-Work. Specifies the role that this contact is being searched for. AppFindContact Flow Action This flow action: – – Executes PegaApp-Work.

IIFCreateContactParty Activity This activity: – – Creates the pyWorkParty instance using the RoleName input parameter as the value of the PageGroup index Calls IIFMapPartyDetails to map the data from the selected Contact into the work object PegaIns-Work. AppSelectContact Flow Action This flow action calls PreActivity PegaApp-Work-.3-20 Insurance Industry Framework Implementation Guide PegaApp-Work-.AppReadContactList that executes the SQL that generates the list of contacts PegaIns-Work.IIFAppGetContactDetails Activity This activity: – Uses an input parameter of Role Name and executes a number of steps to gather the details for the contact that was selected from the list of contacts.AppCallAppReadContactList which calls PegaApp-Interface-Contact.IIFAppGetBusinessUnitDetails Activity This activity: – Uses an input parameter of Role Name and executes a number of steps to gather the details for the business unit that was selected from the previously displayed list of business units Uses activities provided with PegaApp to retrieve the business unit data from the various database tables Calls IIFCreateBusinessUnitParty to create the work party – – . Uses activities provided with PegaApp to retrieve the contact data from the various database tables and reconstitute the data into the PegaInsInterface-Contact class Calls IIFCreateContactParty to create the work party – – PegaIns-Work.

What Is Already Set Up 3-21 PegaIns-Work.IIFCreateBusinessUnitParty Activity This activity: – – Creates the pyWorkParty instance using the RoleName input parameter as the value of the PageGroup index Calls IIFMapBusinessUnitPartyDetails to map the data from the selected BusinessUnit into the work object PegaIns-Work. RoleName.IIFMapPartyDetails Activity This activity maps data from the AppContact page on the clipboard that was populated by the PegaApp contact search rules to the pyWorkParty page specified by the input parameter. .

and Policy Type PolicyID – exact match of PolicyID PolicyID – listing all policy transactions These searches are described on the following pages which also include details about how they are implemented in the Framework. include a JSP tag that references a ListView that is configured as a Selectable ListView 3. policy searches are implemented by using a Selectable ListView. Effective Date. Policy searches are initiated from a flow action that specifies an HTMLSection to display on the HTML tab. Policies can be searched by: ■ ■ ■ ■ ■ Contact Contact and Role Contact. On the HTML tab of the Section. check the ‘Embedded’ box On the Content tab: – – – Specify the properties to be returned Specify “Key Of A Row” as pzInsKey In the Report Source area: • • Specify a custom getContent activity in the Activity Name field Specify the clipboard page for the results in the Content Page Name field On the Selectable tab: . In addition to using the standard configuration for a list view.3-22 Insurance Industry Framework Implementation Guide Policy Search The Framework provides the ability to search for policies in a number of different ways. Setting Up Selectable ListViews The following steps describe how to set up a Selectable ListView. the following Framework configuration was implemented to configure the ListView as a ‘selectable’ list view: On the Fields tab. 1. Policy Search Implementation Since the user will select a policy from a list of policies. 2.

Figure 3-10 lists the rules used to implement a selectable list view for this search type followed by specific implementation details for each rule in the list. Create a custom getContent activity in the Embed-ListParams class to create the list of policies. If the policyholder is a BusinessUnit (for Commercial Lines). Search Types and Implementation Rules Policy Search By Policyholder The policy search by policyholder lists all policies for a given policyholder. For example. A custom activity is needed here because the search needs to be executed against the IIF_POLICY_LINK table and the underlying SQL includes a join between two database tables. . then the search filters the list of policies further by the AuthorizedParty for the BusinessUnit. where one will be selected to be processed by the flow. Create the SQL needed to execute the desired search. see Application Developer Help or the PDN. Extension Tip: For details about setting up a List View and more information about the use and configuration of Selectable List Views.What Is Already Set Up 3-23 – Check the “Enable Selection of Rows” box For framework purposes the options are set as: ■ ■ ■ Mode: Single Select Copy To: Page Name: pyWorkPage – specifying the properties for the selected policy you want to put on the clipboard for reference later 4. three policies will appear in the list. if Peter Roberts has an Auto Insurance Policy and two Life Insurance Policies. This search is currently being used in the ChgPolicy flow to display the list of policies for a given policyholder. 5.

PolicyListForPolicyholder HTML-Section This Section is in the PegaIns-Work class making it available for all work types. On the HTML tab of this section.ListPoliciesForPolicyholder ListView Specify a custom getContent activity. SQL to get policies from db table.InsPickPolicy FlowAction On the HTML tab of the flow action. PegaIns-Work. Policy Search by Policyholder Rules PegaIns-Work-ChgPolicy. getContentPoliciesForPolicyholder.3-24 Insurance Industry Framework Implementation Guide Rule Type Flow Action HTMLSection ListView Class PegaIns-WorkChgPolicy PegaIns-Work Rule InsPickPolicy Description Flow action to display list of policies Defines HTML used to display list of policies Selectable list view to display list of policies and allows one to be selected Executes an RDB-List to run SQL to retrieve policies SQL to get policies from db table. include directives to execute a list view as follows: <pega:listView name="ListPoliciesForPolicyholder" className="PegaInsInterface-InsurancePolicy" header="false" /> PegaIns-Interface-InsurancePolicy. to get the list of policies from the Policy and PolicyLink tables. PolicyListForPolicyholder PegaInsInterfaceInsurancePolicy EmbedListParams PegaInsInterfaceInsurancePolicy PegaInsInterfaceInsurancePolicy ListPoliciesForPolicyholder Activity getContentPoliciesForPolicyholder ConnectSQL ConnectSQL IIFGetPolicyListForPolicyholder IIFGetPolicyListForPolicyholderAndA uthorizedParty Figure 3-10. . reference the HTML-Section named PolicyListForPolicyholder.

Policy Search By Policyholder.getContentPoliciesForPolicyholder Activity This activity sets . effective date and policy type lists all policies for a given policyholder and policy type where the search date falls between the TransactionEffectiveDate and TransactionEndDate. PegaIns-Interface-InsurancePolicy. the latest transaction is returned. . This search currently is not used in the framework. It is provided as functionality that can be used or extended in your implementation.IIFGetPolicyListForPolicyholder Connect-SQL This SQL rule currently only exists for an Oracle database. It executes a SQL statement to return information for a list of policies for the PartyID specified on the QueryParams page on the clipboard. it executes the IIFGetPolicyListForPolicyholderAndAuthorizedParty SQL. Effective Date and Policy Type The policy search by policyholder. If it is a ‘C’ it executes the IIFGetPolicyListForPolicyholder SQL. the latest transaction is returned. It executes a SQL statement to return information for a list of policies for the PartyID and AuthorizedParty specified on the QueryParams page on the clipboard. Figure 3-11 lists the rules used to implement a selectable list view for this search type followed by specific implementation details for each rule in the list. It then executes an RDB-List to call depending on whether the policyholder has a party type of ‘B’ (BusinessUnit) or ‘C’ (Contact). Otherwise.IIFGetPolicyListForPolicyholderAndAuthorizedParty Connect-SQL This SQL rule only exists for an Oracle database.What Is Already Set Up 3-25 Embed-ListParams. If more than one policy transaction exists for any given policy. If more than one policy transaction exists for any given policy.PartyID on QueryParams page for the SQL statement to use as search criteria. PegaIns-InterfaceInsurancePolicy.

Policy Search By Policyholder-Effective Date and Policy Type Rules PegaIns-Work. Embed-ListParams. getContentPoliciesForPolicyholder_Date_PolicyType.ListPoliciesForPolicyholder_Date_PolicyType ListView This rule specifies a custom getContent activity.PartyID on QueryParams page for the SQL to use as search criteria.getContentPoliciesForPolicyholder_Date_PolicyType Activity This activity sets .3-26 Insurance Industry Framework Implementation Guide Rule Type HTML-Section Class PegaIns-Work Rule PolicyListForPolicyholder_Date_ Type ListPoliciesForPolicyholder_Date_ PolicyType Description Defines HTML used to display list of policies Selectable list view to display list of policies and allows one to be selected Executes an RDBList to run SQL to retrieve policies SQL to get policies from db table ListView PegaInsInterfaceInsurancePolicy EmbedListParams PegaInsInterfaceInsurancePolicy Activity getContentPoliciesForPolicyholder_ Date_PolicyType IIFGetPolicyListForPolicyholder_ Date_PolicyType Connect-SQL Figure 3-11. . to get the list of policies from the Policy and PolicyLink tables. include directives to execute a list view as follows: <pega:listView name="ListPoliciesForPolicyholder_Date_PolicyType" className="PegaIns-Interface-InsurancePolicy" header="false" /> PegaIns-InterfaceInsurancePolicy. It should be called from the flow action that you set up to execute this search. It then executes an RDB-List to call the IIFGetPolicyListForPolicyholder_Date_PolicyType SQL.PolicyListForPolicyholder HTML-Section This Section is in the PegaIns-Work class so it is available for all work types. On the HTML tab of this section.

search again Flow Action PegaIns-Work PolicyNotFound Figure 3-12. Policy Search by PolicyID This search is executed in the ChgPolicy flow to find the policy directly by the policy id instead of going through the contact search and choose a policy from the list of policies presented. It provides the ability to find the policy by an exact match on the policy id. It is generated by the ListView rule PegaIns-Interface-Contact-PolicyRoleSummary . It displays a field to enter the policy id which is used in the subsequent flow to get the policy. . Policy Search by Contact and Role Type This search lists all policies where a given contact has any role. Figure 3-12 lists the rules used to implement the Policy Search by ID functionality.ListPoliciesByContactAndRole. and SearchDate properties on the QueryParams page of the clipboard.IIFGetPolicyListForPolicyholder_Date_PolicyType Connect-SQL This SQL rule currently only exists for an Oracle database.What Is Already Set Up 3-27 PegaIns-InterfaceInsurancePolicy. It is initiated by the FindPolicyByID flow action that is defined in the IIFAppContactSearchFlow.FindPolicyByID FlowAction This flow action is called from the IIFAppContactSearch flow. Policy search by Policy Id rules PegaIns-Work. It can be found in the Data Reports section of the Monitor Activity screen. PolicyType. It executes a SQL statement to return information for a list of policies that meet the search criteria specified in the PartyID. Rule Type Flow Action Flow Activity Class PegaIns-Work PegaIns-Work PegaIns-Work Rule FindPolicyByID FindPolicyByID GetCurrentPolicyKeys Description Flow action to enter PolicyID Controls process of policy search by policy id Reads the database to get the keys for the last transaction for this policy Handles Policy not found.

ModNumber.ListPolicyTransactions. If the policy id is not found. Policy Transaction Search Type This search lists all transactions for a given PolicyID. PegaIns-Work. TransactionProcessDate. PegaIns-Work. If the policy id is found. It can be found in the Data Reports section of the Monitor Activity screen. . TransactionEffectiveDate.PolicyNotFound FlowAction Displays that the policy is not found and allows the user to search again.3-28 Insurance Industry Framework Implementation Guide PegaIns-Work. it returns to the calling flow for continued processing. The actual retrieval of the policy data happens in the SelectPolicy flow. GetCurrentPolicyKeys. it displays the PolicyNotFound flow action. It is generated by the ListView rule PegaIns-Interface-PolicyLink. The keys it returns are PolicyID.GetCurrentPolicyKeys Activity This activity executes an RDB-List calling the GetLatestPolicy Rule-Connect-SQL rule to get the keys for the last transaction for this policy in the IIF_POLICY table. using the keys determined in this flow. to retrieve the policy keys for the latest transaction for this policy id.FindPolicyByID Flow This flow first calls the activity.

extend and work with the following components of the Framework: ■ ■ ■ ■ ■ ■ Work Classes Data Classes Interface Classes Work Objects Agencies and Agents Matching of Drivers and Vehicles .Chapter 4 Extending the Framework This chapter contains information to help you understand.

Figure 4-1 shows the work class structure as it exists when the Framework is installed.4-2 Insurance Industry Framework Implementation Guide Extending the Work Class Structure This section describes the work class structure shipped with the Framework and how it can be extended to meet your organization’s requirements. Figure 4-1. Industry Framework Work Class Structure .

class The Framework’s PegaIns-Work class hierarchy inherits from Work.through the PegaSP-Work.— Commercial lines Indiv.and PegaApp-Work classes. The PegaIns-Work class hierarchy is organized by three work type classes: ■ PegaIns-Work-Application Supports NewBusiness (NB) and Quote processing Contains the rules that are common to all types of Application (or NB) processing. ■ ■ ■ Com.Extending the Framework 4-3 Inheriting from the PegaIns-Work. there are subclasses for the following lines of business. This structure is designed to provide access to both Product Configurator and PegaApp rules and functionality. Most of the flows and subflows are found in this class with a few of them extended into a lower class for modified processing PegaIns-Work-ChgPolicy Supports Endorsement processing Contains the rules that are common to all types of policy change processing − − ■ − − Within each work type class.— Personal lines . Figure 4-2 shows the structure in the Class Explorer.— Individual lines Pers.

Work Class Subclasses in Class Explorer Within each class for a line of business. In the Framework. . Figure 4-3 shows the lines of business structure in the Class Explorer.4-4 Insurance Industry Framework Implementation Guide Figure 4-2. these product groups are associated with the product groups defined in the Product Configurator Framework. BOP (Business Owners Policy). These subclasses can be specialized further to provide support for additional subtypes of these product groups. there are subclasses for product groups such as Automotive. and TermLife.

you have access to all the rules provided in the framework that support basic Insurance Processes. using the standard Process Commander Clone a Class Group wizard. Do not make changes to the PegaIns-Work class structure or rules. PegaIns-Work. Extension Tip: When extending the work class. Lines of Business Subclass Structure in Class Explorer By setting up your class structure in a similar way and inheriting from the PegaIns-Work class hierarchy. In addition. you have the start of a framework that can be used to build out the class structure that meets your requirements.Extending the Framework 4-5 Figure 4-3. you should clone the class defining the work pool. extend and override them in your own class structure. . Instead.

If you set up subclasses to specialize the Product Group (for example: adding RetailStore) you can change the work object class to the lower subclass once you have created the work object at the product group class. NewWork flows exist in the subclass for the particular product group. . This provides the option to create a work object for each product group that appears in the Process gadget of the Run menu.4-6 Insurance Industry Framework Implementation Guide An example of an extended work class structure for New Business processing with a Retail Store type of Business Owners Policy is shown in Figure 4-4. Example of Extended New Business Work Structure Creating New Work Flows In the Framework. Figure 4-4. for example: Business Owners or Homeowners.

the insurance policy information is stored external to Process Commander either in database tables or in other external systems of record. For more information about integrating with other systems. There are a number of integration rules that need to be extended and modified to access these systems appropriately.Extending the Framework 4-7 Integrating with Systems of Record and Policy Administration systems When the Framework is deployed. see Chapter 6: Integrating with External Systems. .

4-8 Insurance Industry Framework Implementation Guide Extending the Data Class Structure This section describes the data class structure shipped with the Framework and how it should be extended to meet your organization’s requirements. Figure 4-5 shows the data structure as it exists when the Framework is installed. Figure 4-5 Insurance Industry Framework Data Class Structure .

The Process Commander party classes are subclassed.Class Structure The PegaIns-Data. These classes provide many of the common elements required to create Products and their associated Policies. The PegaIns-Data-PolCmp classes typically aggregate multiple Piif classes to provide more generic objects than using Piif alone.Extending the Framework 4-9 Inheriting from the PegaIns-Data. The Piif class. The structure also can inherit from the PegaIns-Data-PolCmp classes. you can leverage the Piif class by having your data classes directly inherit from the corresponding Piif class and then making customizations as necessary to meet your business need. with each new class directly inheriting from their Piif equivalent. The structure is based on the Interface Design Model of the IBM Insurance Application Architecture (IAA) version 2006TR with one exception — the Framework also leverages Process Commander’s extensive Party classes and associated rules.000 properties that can be used to represent the data aspects of insurance products.class structure is set up to inherit from the Piif class structure to provide access to the many properties provided in Piif. . and its children provide the foundation data structures of the Framework. Piif contains over 550 classes. This provides direct access to both Process Commander and Piif party properties. and life-cycle processing. As you customize the Framework to meet the needs of your own environment. agreements. and over 2.

class structures provide data classes for the following: ■ InsurancePolicy Class that represents a general insurance policy. Subclasses defined here inherit from the Piif class structure to take advantage of the many Insurance properties provided by IAA – IBM’s Insurance Application Architecture. Contains subclasses that represent lines of business and product groups similar to the class structure in PegaIns-Work-. It is specialized by its subclasses.4-10 Insurance Industry Framework Implementation Guide The PegaIns. These classes are used when defining product and component rules in the Product Configurator Framework. PolCmp Contains a number of subclasses that represent components in a product. . Party Contains classes that define parties used in the IIF − − ■ − ■ − Figure 4-6 shows an example of inheritance from the PegaIns-DataInsurancePolicy class hierarchy.

Extending the Framework 4-11 Figure 4-6. the component subclasses are subclassed further to provide additional specialization. In this example. the additional subclass specialization allows for this. For example. The PolCmp classes contain many of the underwriting rules. In this case the AutoCoverage class would be subclassed as: ■ ■ PegaIns-Data-PolCmp-AutoCoverage-Com-Auto PegaIns-Data-PolCmp-AutoCoverage-Pers-Auto . the AutoCoverage rules may be different between Commercial Auto and Personal Auto. In the case where the underwriting rules are common to the lines of business. Example of Extended Data Class Structure Underwriting rules Figure 4-7 shows an example of inheritance from the PegaIns-Data-PolCmp class.

The interface classes that are included in the Framework are: ■ ■ ■ ■ ■ ■ PegaIns-Interface-Contact PegaIns-Interface-Contact-PolicyRoleSummary PegaIns-Interface-InsurancePolicy PegaIns-Interface-PolicyLink PegaIns-Interface-AgencyLOB PegaIns-Interface-Roles .4-12 Insurance Industry Framework Implementation Guide Figure 4-7. you can leverage the existing rules set up to facilitate data access.classes contains classes that are used to build interfaces and API’s to external systems. By inheriting from these classes.Class Structure The PegaIns-Interface. Example of Inheritance from PolComp Class Inheriting from the PegaIns-Interface.

and ‘processing the work type’. ‘entering data for the work type’. or other operational issues best handled outside of existing systems. the Framework can be used as the system of record. such as manually priced policies. In these cases. Each flow is controlled by a main flow that calls the appropriate subflows for the work type. The system of record may or may not be an existing system. Application – New Business Applications for insurance after being entered and successfully processed result in the issuance of insurance policies. The flows for each work type are discussed on the following pages. The actual document production is assumed to be handled externally. In the Framework. examples are provided showing how the Product Configuration Framework can be used to drive the processing of Manually Priced policies. the Framework acts as an integrator. Although. in most cases the system of record will be external to the Framework.Extending the Framework 4-13 Working with Insurance Work Objects The Framework includes the following work objects: ■ ■ Applications (new business ) Service – Change Policy (endorsements) Work objects are intended to be at the front-end of processing or to link to back end systems such as Policy Administration or Document Management. They follow the basic structure of ‘entering party data’. . binding other systems together and managing exceptional cases not handled elsewhere. The flow structure for each work type is similar.

layer. Bind and Issue steps involved in processing an Application. Underwrite. Each NewWork flow (Figure 4-8) calls the Application Main flow (Figure 4-9) that is common to all product groups. the NewWork flows for Applications exist in the subclass for the particular product group. This is configured for demonstration purposes. The following figures show the preconfigured flows shipped with the Framework that comprise the New Business process. Figure 4-8. During implementation you must create your own set of classes that have their own activities that preempt those in the PegaIns. As previously mentioned. Personal Auto NewWork Flow . for example: Personal Auto or Homeowners. The Application flows have been built to show the Quote.4-14 Insurance Industry Framework Implementation Guide Extension Tip: The Framework writes the policy image to an external database table defined for the PegaIns-Interface-InsurancePolicy class.

ApplicationMain Flow The EnterPartyData subflow (Figure 4-10) that is specific to Applications collects the party data for the Applicant. .Extending the Framework 4-15 Figure 4-9. The party data is entered through the contact search functionality.

The flow calls the PopulateAgentData activity to handle this process. The IIFAppContactSearch subflow is common to all work types in the Framework and lives in the PegaIns-Work class. the data is moved into the pyWorkParty page group for the “Applicant”.4-16 Insurance Industry Framework Implementation Guide Figure 4-10. so that when the contact is selected. If this work is being executed by an agent. the Agent work party is populated with the Agent’s information from the AgentProfile page on the clipboard. EnterPartyData Subflow The IIFAppContactSearch subflow (Figure 4-11) is called with a flow parameter of “Applicant”. .

IIFAppContactSearch Subflow The ProductSelection subflow for Applications (Figure 4-12) handles the process of producing a list of products to select from and setting up the policy with the product selected. .Extending the Framework 4-17 Figure 4-11.

. ProductSelection Subflow The EnterApplicationData flow (Figure 4-13) handles the process of entering the detailed data for the policy. It then presents the entered data for confirmation from the customer.4-18 Insurance Industry Framework Implementation Guide Figure 4-12.

It calls the ApplicationQuote subflow (Figure 4-15) that handles producing a Quote and sending it to the customer for acceptance. . Binding and Issuing the Application. it then spins off the BackOffice flow (Figure 4-16) that handles the processes of Underwriting. If the customer accepts the quote.Extending the Framework 4-19 Figure 4-13. EnterApplicationData flow The ProcessApplication flow (Figure 4-14) handles the steps needed to process the application once all the data has been entered and validated.

4-20 Insurance Industry Framework Implementation Guide Figure 4-14. ProcessApplication Flow .

ApplicationQuote Subflow .Extending the Framework 4-21 Figure 4-15.

4-22 Insurance Industry Framework Implementation Guide Figure 4-16. BackOffice flow .

Figure 4-17. ApplicationUnderWrite Subflow . The back office functions include Underwrite (Figure 4-17).Extending the Framework 4-23 The BackOffice flow needs to be called via a spin-off flow shape to allow the back office functions to be handled via the Framework even when the application was handled by another system or framework application such as CPM for Insurance.Bind Policy (Figure 4-18). and Issue Policy (Figure 4-19) which are each handled by subflows.

IssuePolicy Subflow .4-24 Insurance Industry Framework Implementation Guide Figure 4-18. BindPolicy Subflow Figure 4-19.

When an Application flow is initiated. the WorkParties rule is found in the class PegaIns-WorkApplication-Pers-. After the contact data is entered. a list of available products displays in a selection list. Figure 4-20 lists the Work. This list is created from the products that are defined in the Product Configuration layer for the product group associated with the work object. and product group. A NewWork flow exists in each of the lowest level work classes defining the product groups. For example. the work classes for Applications processing are specialized by Line of Business (LOB). which is defined in the Product Configuration Framework layer. Examples of product groups are Auto and Business Owners Policy (BOP) for Commercial LOB and Auto and Homeowners for Personal LOB. users are taken through the Contact Search functionality. such as Commercial or Personal. These work parties are defined in the Rule-Obj-WorkParties rule at the class level for the line of business that is chosen.classes containing rules that filter the information.Extending the Framework 4-25 Understanding the Preconfigured Workflows In this release of the Framework. data is collected for the appropriate work parties. To facilitate entering party data. if ‘Personal Lines’ is chosen for the line of business. The product group is a concrete work class under the class of the current work pool. There is an Application flow for each of the product groups. Each product group can have many products defined for them in the Product Configurator. Figure 4-21 shows an example of the filtering during the entry of a Commercial Lines application. .

4-26 Insurance Industry Framework Implementation Guide Figure 4-20. Business and Product Filtering Figure 4-21. Product Filtering .

and to confirm or reenter the same. EnterApplicationData Flow If the Product Configuration Framework drives the process. Figure 4-22. The detail screens presented to the user depend on the product selected. there are actions that allow users to select a different product within the same Line of Business.Extending the Framework 4-27 The Entry process for applications may be driven by the Product Configuration Framework or may be custom crafted for Policy Administration system resident products. . Figure 4-22 shows the flow used to enter application data. to enter details for the selected product.

The framework includes flows that process InSequence Endorsements and can be extended to support Out-of-Sequence endorsements. The ChgPolicy NewWork flow (Figure 4-23) is the main flow that controls the required processing steps by calling the appropriate subflows.4-28 Insurance Industry Framework Implementation Guide ChgPolicy – Endorsements The ChgPolicy work type and flows handle the processing of Endorsements (or Mid-Term Adjustments). Figure 4-23. The following figures show the preconfigured flows shipped with the Framework that comprise the ChgPolicy process. ChgPolicy NewWork Flow .

The IIFAppContactSearch subflow is common to all work types in the Framework and lives in the PegaIns-Work class.Extending the Framework 4-29 The EnterPartyData subflow (Figure 4-24) that is specific to ChgPolicy collects the party data for the Policyholder. the Agent work party is populated with the Agent’s information from the AgentProfile page on the clipboard. Figure 4-24. The party data is entered through the contact search functionality. If this work is being executed by an agent. The flow calls the PopulateAgentData activity to handle this process. The IIFAppContactSearch subflow is called with a flow parameter of “Policyholder”. so when the contact is selected. ChgPolicy EnterPartyData Subflow . the data is moved into the pyWorkParty page group for the “Policyholder”.

Figure 4-25. If you are executing this flow in a CPMINS implementation. ChgPolicy SelectPolicy Flow . the policy data is already retrieved. Similarly. then the policy list is bypassed and control goes directly to FetchPolicyData. if the policy is present (the policyid is not blank). bypassing this part of the flow.4-30 Insurance Industry Framework Implementation Guide The next step is to select a policy to apply the change. The SelectPolicy flow (Figure 4-25) handles the steps needed to display a list of policies for the Policyholder and gathers the policy data for the policy that is selected from the list.

ChgPolicy PerformEndorsement Flow The EnterEndorsementData flow (Figure 4-27) displays the data for the policy that was selected and allows the data to be modified. . Figure 4-26.Extending the Framework 4-31 The PerformEndorsement flow (Figure 4-26) handles the entering and processing of the endorsement data.

the current premium and the change in premium that is a result of the changes made to the policy. A Premium Summary area is shown to identify the new premium. . a new price is calculated.4-32 Insurance Industry Framework Implementation Guide Figure 4-27. ChgPolicy EnterEndorsementData Flow After modifications are made. Figure 4-28 shows this Premium Summary on the confirmation screen.

it then spins off the BackOffice subflow (Figure 4-31) to handle the processes of Underwriting. control is then sent to the ProcessPolicyChanges flow (Figure 4-29).Extending the Framework 4-33 Figure 4-28. gives a list of previous endorsements for this policy in a pop-up window. . there are two buttons at the top of the screen as seen in Figure 4-28. which is the basis for this endorsement. Binding and Issuing the Endorsement. The second button. View Endorsement History. One can click on any of these to see the policy details for this endorsement. the first button. ChgPolicy Confirm Product Details Screen On the ChgPolicy screens. After the desired changes have been made to the policy and confirmed. This flow first calls the ReQuote subflow (Figure 4-30) to handle the Re-Quote process and sends it to the customer for acceptance. If the customer accepts the re-quote. shows the policy details for the current version of the policy. When clicked. View Endorsement Basis.

ChgPolicy ProcessPolicyChanges Flow .4-34 Insurance Industry Framework Implementation Guide Figure 4-29.

Extending the Framework 4-35 Figure 4-30. ChgPolicy ReQuote Subflow .

ChgPolicy BackOffice Subflow .4-36 Insurance Industry Framework Implementation Guide Figure 4-31.

components represent Insured Objects and Coverage Options.classes as the “entry process class”. In the Framework. The Piif classes were created from IAA’s Interface Design Model (IDM) and contain a multitude of properties that can be used to assemble insurance objects. class structures have been created to represent Products and Product Components. These classes should inherit from Piif classes. The Products are grouped by Lines of Business. . Classes Based on the IAA Model Rule-PegaSP-Product records are defined with the classes listed in Figure 4-32 as the “applies to” class with corresponding work. Products represent Insurance Policies which are composed of “components” (and sub-components nested to an arbitrary level). Figure 4-32. and “features”.Extending the Framework 4-37 Configuration of Products (Policies) The Product Configuration Framework included in the Insurance Industry Framework allows administrators to define products “as they may be sold”. The Product Components are more generally grouped and are based on classes defined in the PegaIns-Data-PolCmp class. Figure 4-32 shows the structure of the classes based on this model. In the Insurance Framework.

Product Explorer For Commercial Lines – BusinessOwnersPolicy Tree .4-38 Insurance Industry Framework Implementation Guide Figure 4-33 shows the products (Insurance Policies) available for the Commercial Lines as displayed by the system’s Product Explorer. Figure 4-33. The Product Explorer is available from the Edit menu on the task bar located at the top of the workspace.

Figure 4-34.Extending the Framework 4-39 Figure 4-34 shows an example of the product component definition for the BusinessOwnersPolicy shown in the Product Explorer in Figure 4-33. Product Definition for BusinessOwnersPolicy .

This is a post-processing activity that executes validations and calculates prices after policy data entry. you will have to create component class specific calculation routines and insert them into this process.4-40 Insurance Industry Framework Implementation Guide Pricing Details IAA assumes that there will always be an “exposureAmount” property related to insurance policies or insurance policy components. a PegaInsWork-Application specific version of the ActionFinalCheck activity is provided. pricing is directly related to the exposureAmount property. That way. Figure 4-35 shows how pricing details appear to an online user. Therefore. The PegaIns-. Figure 4-35. User View of Pricing Details . See Chapter 5 — Pricing Rules and Models for more details on the pricing functionality in the framework.Figure_Exposure activity was added to loop through all components and all features and calculates a component instance’s exposureAmount as the sum of all the exposureAmount values in its selected features. Pricing for the BOM policy example follows this model. Extension Tip: If the final amount is not a simple sum.

The typical insurance policy is linked with one Agency. Each line of business may have a different effective date for processing and commission percentage. Agencies generate new business and process requests for servicing existing business.Extending the Framework 4-41 Agencies and Agents An Agency acts as an intermediary between an insured and carrier. This licensing information is a key piece of information to be linked to the Agency. An Agent is an employee of the Agency. An Agency may process multiple lines of business for the carrier. The Agent is the central point of contact with the insured and the carrier. Figure 4-36. There is a license that must be obtained to write a line of business in each state. Agency-Agent Relationship . The relationship is illustrated in Figure 4-36. A Master Agency Code is used as a method for aggregating all of the Agency data.

When the operator is an agent. This data is used in later processing.ApplicationProfileSetup Activity This activity is invoked when the operator signs onto the system. The relationship between them is stored in the PA_BUSINESSUNIT_LINK table. The Agency LOB data is stored in a new table IIF_AGENCY_LOB. This relationship is stored in the PA_CONTACT_BUSINESSUNIT_LINK table.4-42 Insurance Industry Framework Implementation Guide Agencies Master Agencies and Agencies are stored in the PA_BUSINESSUNIT table. an AgentProfile is created at the time the operator signs onto the system. The following rules are involved in creating the AgentProfile: Code-Security. It is overridden in the PegaInsure ruleset with one line that is added to call the BuildAgentProfile activity. The keys to the AgencyLOB table are: AgencyCode. EffectiveDate Agents Agents are stored in the PA_CONTACT table. LicensedState. Agent Profiles An operator on the system can be either an agent or a representative of the carrier performing work on behalf of the agent. See Chapter 6 and Appendix A for more information on this table. . LineOfBusiness. The AgentProfile contains the agent and agency data for this agent. The link between the operator and agent is in the AgentProfile decision table. Each agency also can have many agents working for it.

AgentProfile Decision Table Associating Agencies to Policies Agency data is stored in the policy as an embedded page of the class. This page contains agent and agency information for the operator.Extending the Framework 4-43 PegaIns-Data-AgentProfile. Figure 4-37. It looks the operator up in the AgentProfile decision table to get the AgentCode (contact id) and AgencyCode (business unit id) for this operator. When a new policy is created in the New Business flow.AgentProfile Decision Table This table (Figure 4-37) maps the operator to an agent code (contact id) and an agency code (business unit id). This property is displayed in a new DisplayAgency section whenever the policy is displayed. The agent and agency data are then read from the PA_CONTACT table and the PA_BUSINESSUNIT table using these values as keys. this agency data is populated in one of two ways. A new AgencyData property is created in the PegaIns-Data-InsurancePolicy class for this embedded page. If the operator is an agent. then his AgentProfile exists on the clipboard. PegaIns-Data-Party-Org-Agency. TSmith@TomsInsAgency. The decision table that is shipped contains information for this operator. The framework is shipped with a sample agent that has an associated operator record. 1.BuildAgentProfile Activity This activity is responsible for creating the AgentProfile page on the clipboard. PegaIns-Data-AgentProfile. The agency data is copied to the AgencyData page property in the policy .

This is used to set the AgencyData property when the operator is an agent and the AgentProfile page exists on the clipboard. AgencyDisplay Section PegaIns-Work-Application. If the operator is not an agent. PegaIns-Data-Party-Org-Agency. 2.InitializeNewPolicyData Activity This activity is called when a new policy is created in the new business process to set initial data. this activity is called to retrieve the agency data from the database and populate the AgencyData embedded page in the policy.GetAgencyData Activity This activity is called from an OnChange event defined on the AgencyCode property in the AgencyDisplay section. the AgencyData display on the screen is updateable and the operator selects an agency to assign to the policy. When a value is put into the AgencyCode field. . Figure 4-38.4-44 Insurance Industry Framework Implementation Guide which is displayed read-only in the policy information area of the screen. This information is required. The agent data is copied to the ‘Agent’ work party in all new work objects he creates.

510 Maple St.Extending the Framework 4-45 Sample Agent and Agency Data The framework is shipped with sample agency and agent data. This sample data is described in the following tables: Master Agencies AgencyCode ABC MAINEAG SMITHINS Name ABC Brokers Maine Agency Smith Insurance Agency Address 123 Main St 543 Main St. City Alexandria Adjuntas Boston State NY ME MA Agencies Agency Code TOMSINS 1000 1001 2007 2008 MasterAgency Smith Insurance Agency ABCBrokers ABCBrokers Maine Agency Maine Agency Name Toms Insurance Agency ABC Brokers Faifax Agency Maine Agency Jones Agency Address 1420 Newton St 123 Main St 562 Main St 543 Main St 571 Main St City Needham Alexandria Alexandria Adjuntas Charlotte Amalie State MA NY NY ME ME Agency Lines of Business Agency Code TOMSINS TOMSINS LOB Personal Auto Personal Auto State MA NH Effective Date 10/9/07 10/9/07 Expiration Date 12/31/99 12/31/99 Commission % 15 15 .

4-46 Insurance Industry Framework Implementation Guide Agency Code TOMSINS TOMSINS TOMSINS 1000 1000 1000 1000 1000 1001 1001 1001 1001 1001 2007 2007 2007 2007 2007 2008 2008 2008 2008 2008 LOB Homeowners Commercial Auto Life Personal Auto Homeowners BOP Commercial Auto Life Personal Auto Homeowners BOP Commercial Auto Life Personal Auto Homeowners BOP Commercial Auto Life Personal Auto Homeowners BOP Commercial Auto Life State MA MA MA MA MA MA MA MA MA MA MA MA MA MA MA MA MA MA MA MA MA MA MA Effective Date 10/9/07 10/9/07 10/9/07 1/1/07 1/1/06 1/1/05 1/1/07 1/1/07 1/1/07 1/1/06 1/1/05 1/1/07 1/1/07 1/1/07 1/1/06 1/1/05 1/1/07 1/1/07 1/1/07 1/1/06 1/1/05 1/1/07 1/1/07 Expiration Date 12/31/99 12/31/99 12/31/99 12/31/99 12/31/99 12/31/99 12/31/99 12/31/99 12/31/99 12/31/99 12/31/99 12/31/99 12/31/99 12/31/99 12/31/99 12/31/99 12/31/99 12/31/99 12/31/99 12/31/99 12/31/99 12/31/99 12/31/99 Commission % 8 10 8 10 15 15 10 8 10 15 15 10 8 10 15 15 10 8 10 15 15 10 8 .

Extending the Framework 4-47 Agents AgentId CONTA-100 CONTA-110 CONTA-120 CONTA-130 CONTA-140 CONTA-150 Name Tom Smith Joan Smith Ethan Frome Pat Kenzie Jacob Larson Jim Jones Agency Toms Insurance Agency Toms Insurance Agency ABC Brokers Fairfax Agency Maine Agency Jones Agency .

) and the vehicle (using age. and the combined vehicle-driver risk value for each is derived. the process requires associating (matching) drivers to vehicles so that consideration of the risk involved for each vehicle is appropriate for the driver. Once the vehicles and drivers have been associated. and so on. etc. Next.4-48 Insurance Industry Framework Implementation Guide Matching Drivers to Vehicles When determining the premium for an automobile policy. See Chapter 5: Pricing Rules and Models of this document for information about pricing models used in the Framework. coverage. the lower the risk of loss expected. and the algorithms used for aggregating the total risk and discount may vary greatly. theft risk.) are rated separately. The risk assessment is based on the primary driver for the vehicle. The rating of vehicles and drivers is numeric — the lower the value. The vehicles and drivers are associated using a method described in the section below or some other method. Pricing is different for each company. the process moves to calculating the price. driving record. This can involve quantity and multi line discounts. the combined derived risk is determined. repair cost. Processing follows the logic below: ■ ■ The driver (using age. ■ ■ . college.

Associate the driver with this vehicle. the driver is not permitted to drive the vehicle under any circumstances as they would be uninsured. ■ Method 4 – Highest Pairing with Exclusion The exclusion method is where a driver is explicitly excluded from driving a specific vehicle. . the customer is allowed to specify certain other associations such as their oldest vehicle is driven by their teenager. Pre-associated pairs are removed from the first iteration through vehicle list and the rest of the process uses Method 1. However. while their newer or more expensive car is driven by an older adult. the list of drivers is reused starting from the beginning of the list. In addition to specifying the primary driver of a vehicle. Some approaches are related to the corporate policy for the carriers while others are legally mandated. the lists are ordered from highest to lowest. It allows the customer to specify the primary driver of a given vehicle.Extending the Framework 4-49 Driver/Vehicle Association Methods There are a number of methods that can be used to make the association between drivers and vehicles. ■ Method 3 – Highest Pairing with Specification This method is an addition to the process defined in Method 1. look for the driver with the highest rating who is not associated with any vehicle. Common methods are: ■ Method 1 – Customer specification In this method the driver-vehicle pairs are defined by the customer.to limit how negative a consideration a company can make. The driver and vehicle are both still in consideration for all possible matches. ■ Method 2 – Highest Pairings Following the rating of the drivers and vehicles. If there are vehicles remaining after matching all available drivers. Iterating through the list of vehicles from highest to lowest rated.

etc. the customer specifies the principal driver of each vehicle in the NamedDriver property.4-50 Insurance Industry Framework Implementation Guide This association method is implemented to mitigate a situation like having a newly licensed 16 year old and a brand new high performance exotic sports car in the same household. The PegaIns-Data-InsurancePolicy VehiclesToDrivers property has a data type of page group in the PegaIns-Data-VehiclesToDrivers class. By storing the information here. the VehiclesToDrivers property structure resembles the sample in Figure 4-39 indicating that the Driver specified in the second element of the NamedDriver . it is readily available at the time the pricing activities are invoked and eliminates the need for the pricing activities to traverse the product structure to find the associated driver information. The PegaIns-Data-VehiclesToDrivers class contains the following properties: ■ ■ ■ DriverIndex — contains the integer values for the NamedDriver that is assigned to the vehicle DriverAgeCategory — is populated with a rating information for the specific driver DriverRecordCategory — is populated with rating information for the specific driver In a scenario where there are two vehicles and two drivers. Vehicle3. When entering information. The value for the page group index is Vehicle1. How the Framework Associates Drivers to Vehicles The PersonalAuto sample product in the Framework uses Method1 to associate its vehicles and drivers. Vehicle2. the vehicle to driver associations are determined in the beginning of the pricing process and stored in the VehiclesToDrivers property located in the PegaIns-DataInsurancePolicy class. Because of the complexity of the product data structure and how it represents components with a series of embedded pages.

is executed as the first step in the pricing activity that walks through the named driver array and populates the VehiclesToDrivers page group. PegaIns-Data-InsurancePolicy-PersonalAutomotive. Once the VehiclesToDrivers property is populated. Sample Property Structure for Two Vehicles and Drivers This property is populated at the beginning of the pricing process. The activity. There is one data element for each driver but not necessarily for each vehicle. . there would be only two elements in the VehiclesToDrivers page group. it is available for use in the pricing activities that calculate a price for a given vehicle. In a case where there are 3 vehicles and only 2 drivers.MapVehiclesToDrivers.Extending the Framework 4-51 pagelist is matched with the vehicle specified in the first element of the InsuredVehicle pagelist and so on: VehiclesToDrivers Property Vehicle1 Properties Driver Index DriverAgeCatgory DriverRecordCategory Driver Index DriverAgeCatgory DriverRecordCategory Value 2 Low Good 1 High Good Vehicle2 Figure 4-39.

CalculateBodilyInjury contains the steps to calculate the driver rating that it utilizes. 3. . Override the logic to rate the drivers and vehicles. For example. 2. Add properties to the VehiclesToDrivers class that are needed to meet additional pricing requirements. Override the PegaIns-Data-InsurancePolicy-PersonalAutomotive.MapVehiclesToDrivers activity to implement different mapping algorithms for matching drivers to vehicles.4-52 Insurance Industry Framework Implementation Guide How to Extend the Matching Drivers to Vehicles Functionality There are three configuration points in the Framework where the matching functionality can be extended: 1. This logic is implemented in the pricing activity for a given auto coverage component. the activity PegaIns-Data-PolCmpAutoCoverage.

It includes the following topics: ■ ■ ■ ■ ■ ■ ■ Pricing Overview Standard Pricing Rules Business Owners Policy Pricing Model Term Life Pricing Model Variable Universal Life Pricing Model Automotive Pricing Model Homeowners Pricing Model .Chapter 5 Pricing Rules and Models This chapter describes how pricing is set up in the Insurance Industry Framework and provides information about developing your own pricing models.

5-2 Insurance Industry Framework Implementation Guide Pricing Overview Pricing calculations are used to calculate the premiums for coverages included in an insurance policy and for the policy itself. rather than declaratively with Process Commander’s declarative network. is a good example that shows how to walk down the Product Configurator product structure on the clipboard. called from the EnterProductData flow action. See the Product Configuration Frameworks documentation for a more detailed description of this functionality. any of these pricing activities can be overridden or extended. The activity RunCalculations. called from RunCalculations. used to initiate the pricing process. To replace the entire pricing functionality. ActionFinalCheck. The logic loops through the product tree and calls the pricing activity defined in each component rule from the bottom up. It uses many embedded pages to calculate prices for components and subcomponents and roll those prices up product hierarchy. The pricing calculations are implemented procedurally using activities. These pricing algorithms are very specific to the product examples shipped with the framework and are in themselves examples of how pricing can be implemented. Extension Tip: When extending the framework to meet individual business pricing needs. is invoked from a step in the post processing activity. the ActionFinalCheck activity should be overridden. references are made to the Product Configuration layer and its rules. . Because the Insurance Industry Framework uses the Product Configuration Framework to represent an insurance policy and its coverages. It is expected that you will replace the Framework’s pricing activities with activities that meet the pricing requirements of your business. The activities used to calculate the price for a given product and its components are specified in the Product Configuration product and component rules. The CalculateProductPrice activity.

needs to be able to have a pricing calculation applied to it. therefore. The algorithms used in calculating the price for the example products that are included in the Framework. This allows a pricing activity to be specified in the component rule for any given coverage.Pricing Rules and Models 5-3 One of the requirements across all insurance products is that each coverage have a premium associated with it and. In order to meet this requirement. are described on the following pages for each example product. all coverages are implemented as components in the Product Configuration Framework layer (as compared to features). . The Personal Auto pricing rules show an example of how to use circumstancing to handle pricing rules that vary by state. along with the activities that implement them.

The rate and adjustment percentages are determined in decision tables that belong to the class of the component that is referencing it.5-4 Insurance Industry Framework Implementation Guide Standard Pricing Rules There are a number of standard pricing rules provided in both the Product Configurator and Insurance Industry Frameworks. The pricing activities provided in the Product Configurator Framework are found in the PegaSP class. calculate taxes and apply discounts at all levels of the product structure. The greater the deductible . There are activities that calculate the price using a decision table. For example. or by expressions. which is the amount of risk that the insurance company carries. You can explore these rules to become more familiar with them. The pricing rules provided by the Insurance Industry Framework implement a general pricing algorithm specifically for coverages. a decision tree. The exposureAmount. The pricing activities provided in the Framework implement both general algorithms that apply to all types of coverages and specific algorithms that are used by the example products provided in the framework. The Product Configurator pricing rules are generic and provide the ability to connect the product and its components and subcomponents in calculating the price. only those used in the Insurance Framework are discussed here. Pricing Activities in the Framework General Pricing Activities for Coverages The price of a coverage is calculated by the general algorithm: exposureAmount * a rate * an adjustment. is calculated by the InsuredValue (sometimes called CoveredAmount) less any DeductibleAmount. The rate decision tables are based on the DeductibleAmount. the price of a product is the sum of all the component prices.

The values in each table are specific to the type of component and the component class: The decision table for the rate is named SpecifiedItemRate.exposureAmount = InsuredValue – DeductibleAmount The Rate and Adjustment values are determined from decision tables that are passed in as parameters. This table exists in the class of the component the price is being calculated for.CalculatePrice. Rate Tables There are a number of sample rate tables included in the framework.CalculatePrice Activity Input parameters: Rate table Adjustment table This activity is a standard CalculatePrice activity that follows a basic calculation to determine a premium for a coverage. This CalculatePrice activity is sometimes extended in the class of the associated component.Pricing Rules and Models 5-5 amount. PegaIns-Data-PolCmp-. . coverage premium = exposureAmount * Rate * Adjustments . The InsuredValue and DeductibleAmount values are specified by the customer at data entry. the less risk is given to the carrier. The adjustment decision tables are based on the exposureAmount of the coverage. The general pricing activity that implements this algorithm and can be used for all coverages is PegaIns-Data-PolCmp. which is reflected in the rate tables.

.TotalexposureAmount property.DeductableAmount <= 500 the rate is .5-6 Insurance Industry Framework Implementation Guide In the PegaIns-Data-PolCmp-BuildingCoverageBenefit class the table is based on deductible amount: If . Explore the PegaSP class for a full listing of the pricing activities available.000 then the adjustment is .000.000 then the adjustment is .000. it applies the discount (passed in as a parameter) to the product price and cascades this discount down to the component and subcomponents by calling the DiscountProdAndComps activity.0025 Else the rate is .exposureAmount values into the product .SPPrice values into the product .0027 Else if .000 then the adjustment is .DeductableAmount <= 5000 the rate is . Then.003 Else if .DeductableAmount <= 1000 the rate is .1 Else If exposureAmount >= 1.SPPrice property and the . The discount is passed as a parameter. 1.000. 2.000 and < 5.15 Else the adjustment is 1. It first calls ProductSumOfCompPrices that loops through all the components and subcomponents and sums up the . Pricing activities in the PegaSP Class The PegaSP pricing activities used by the Framework are described here.12 Else If exposureAmount >= 5.002 The decision table for the adjustment is named SpecifiedItemAdjustment: If exposureAmount < 1.000. ProdSumcomponentsWithDiscount Activity This activity sums all the component and subcomponent prices into the product price and then applies a discount to the product and subcomponent prices.

The DiscountProdAndComps activity then applies the discount to all components and subcomponents by iteratively calling DiscountComponentPrice. and DiscountProductPrice.SPPrice by the discount supplied by the parameter and puts result into property . .exposureAmount in the .Pricing Rules and Models 5-7 3.SPPrice in the optionData page into the . DiscountSubcomponentPrice.SPAdjustedPrice.SPPrice property for the product. The DiscountProdAndComps activity first applies any discount to the product price by calling DiscountProductPrice which uses following logic: − − Multiplies the value in .optionData page into the TotalexposureAmount property and . The following sections describe the specific pricing algorithms used by the sample products provided in the Framework. It loops through the first level of components in the product and sums up the . ProductSumOfCompPrices Activity This activity sums the prices for the first level of components under a product and rolls them up into the total price for the product.

and can have multiple buildings defined for it.5-8 Insurance Industry Framework Implementation Guide Business Policy Owner’s Product Pricing Model The Business Owners Policy (BOP) product and component structure is a representation of a BOP policy and the coverages it can contain. Content Coverage. BOP Product and Component Structure The price calculations for a Business Owner’s Policy are: BOP price = (sum of all Location premiums + GeneralLiability Premium) * 10% discount Location Price = BusinessInterruption Premium + sum of all Building Premiums + ContentCoverage premium BusinessInterruption Premium = uses the standard PegaIns-DataPolCmp-. Figure 5-1 illustrates the product and component structure displayed by the Product Explorer. Each building has coverages as well as the Content Coverage component has various coverages. Building Premium. Each property location is defined to have Business Interruption coverage. Each property location has a postal address.CalculatePrice activity using the BusinessContinuationRate rate table. Content Coverages and SpecifiedItem premium = sum of their sub-component prices . Each policy can have a number of property locations. Figure 5-1. The BOP product also has a General Liability component with its coverages.

Each of these coverages uses the general PegaIns-Data-PolCmp-.DeductableAmount <= 5000 the rate is .0027 Else if .DeductableAmount <= 500 the rate is . Fraud nd SexHarassment Fraud and SexHarassment coverages also use the general PegaIns-DataPolCmp-. content coverage and specified item components. They are defined in the PegaIns-Data-PolCmp-BuildingCoverageBenefit class and have the same pricing algorithm as the coverages in the Homeowners Policy.DeductableAmount <= 1000 the rate is . are defined for the buildings. No adjustment is applied to the price calculation for these coverages. Figure 5-2 lists the pricing activities called for each of the Business Owner Policy components .CalculatePrice activity referencing the General Liability Rate table and General Liability Adjustment Table.Pricing Rules and Models 5-9 The basic coverages.003 Else if . Theft. In the PegaIns-Data-PolCmp-BuildingCoverageBenefit class the rate table is based on deductible amount: If .CalculatePrice activity (described in the General Pricing Activities for Coverages section) and the SpecifiedItemRate table in the PegaIns-Data-PolCmpBuildingCoverageBenefit class.002 The calculation for the premium is: GeneralLiability Premium = sum of its Subcomponent prices.0025 Else the rate is . Fire and Flood.

5-10 Insurance Industry Framework Implementation Guide Product/Component BOP Product Location BusinessInterruption Building TheftCoverage FireCoverage FloodCoverage ContentCoverage TheftCoverage FireCoverage FloodCoverage SpecifiedItem TheftCoverage FireCoverage FloodCoverage GeneralLiability Fraud SexHarassment Pricing Activity PegaSP.ProdSumComponentsWith Discount (passing a discount parameter of 10%) PricePlusSumOfSubcomponentPrices CalculatePrice PricePlusSumOfSubcomponentPrices CalculatePrice CalculatePrice CalculatePrice SumOfSubcomponentPrices CalculatePrice CalculatePrice CalculatePrice PricePlusSumOfSubcomponentPrices CalculatePrice CalculatePrice CalculatePrice PricePlusSumOfSubcomponentPrices CalculatePrice CalculatePrice Figure 5-2. Business Owners Policy Pricing Activities .

CoverageAmount > 10. The rate is determined by a decision table called ContentRateTable that is passed in as a parameter from the component rule: If the .000 then the rate is .CoverageAmount > 20. The total price of the subcomponents is then summed up by looping through them and totaling the . .CoverageAmount property that is populated from data entry. It determines the Content Coverage Price by multiplying the value insured amount by a rate.CoverageAmount * rate.01 The Content Coverage Price is then calculated as the . This total subcomponent price is then added to the Content Coverage Price and the result is stored in the .SPPrice property for the Content Coverage component.Pricing Rules and Models 5-11 PricePlusSumOfSubcomponentPrices Activity This activity first determines the Content Coverage Price and then rolls up the subcomponent prices into the total price for the Content Coverage.000 then the rate is . The value insured amount is in the .02 Else if the .SPPrice for each subcomponent.025 Else the rate is .

05 40 and 49 the rate is .CoveredAmount entered on the screen by this rate.1 Else the rate is .TermLifeRates. It determines a rate based on the age of the insured person. Term Life Pricing Components PricingByAgeAndDecisionTable This activity is in the PegaIns-Data-PolCmp-InsuredLife class and is used only in calculating the TermLife price. Term Life Product Structure The pricing calculation used to calculate a TermLife premium is: TermLife price = CoverageAmount * TermLifeRate (based on age of insured) The pricing activities used here are specific to the TermLife product and do not use the generic CalculatePrice activity.11 . The decision table it uses is PegaIns-Data-PolCmpInsuredLife.06 50 and 65 the rate is . It then multiplies the .5-12 Insurance Industry Framework Implementation Guide Term Life Pricing Model The Term Life example product currently contains only one component named TermLife. Figure 5-4 lists the TermLife components and pricing activities. This activitiy is referenced in the TermLife component rule. Its product structure is defined in the Product Explorer as: Figure 5-3.ProductSumOfCompPrices PricingByAgeAndDecisionTable Figure 5-4. Component TermLife Product (product) TermLife (component) Pricing Activity PegaSP. The decision logic is: If the age of the insured is between 20 and 39 the rate is .

009) + (SpousalRiderAmount * .009) + 200 The pricing activities used here are specific to the VUL product and do not use the generic CalculatePrice activity. BasicPolicyInformation Price = InvestmentGoal * . Figure 5-6 lists the pricing activities that are called for each of the VUL components: .Pricing Rules and Models 5-13 Variable Universal Life Pricing Model The Variable Universal Life (VUL) example product that is provided in the framework currently contains only three components. BasicDemographicInformation Price = CoveredAmount * rate based on age and smoker * rate based on frequency of payments. Variable Universal Life Product Structure The price calculation for a VUL policy is: VUL price = Price for BasicDemographicInformation + Price for BasicPolicyInformation + Price for RiderInformation. The product structure is defined in the Product Explorer as: Figure 5-5.00094 * rate based on frequency of payments RiderInformation Price = (ChildRiderAmount * .

Frequency Discouont Table . Payment Fequency 1 2 4 12 Other Rate .5-14 Insurance Industry Framework Implementation Guide Component VUL Product (product BasicDemographicInformation BasicPolicyInformation RiderInformation Pricing Activity PegaSP.1 . Figure 5-7 shows the relationship between the payment frequency value and the discount rate. It calculates the price using two rates: 1. Variable Universal Life Pricing Activities BasicDemographicInformation Activity This activity is in the PegaIns-Data-PolCmp-InsuredLife class and used only in calculating the BasicDemographicInformation price. PaymentFrequencyRate uses the VarUnivLifeFrequenceDiscount table and the payment frequency entered on the screen.ProductSumOfCompPrices BasicDemographicInformation BasicPolicyInformation BasicRiderInformation Figure 5-6. It is referenced in the BasicDemographicInformation component rule.05 .03 0 0 Figure 5-7.

00686 .3 Smoker Rate .0090 .00146 .00107 .00094 .0090 .CoveredAmount that is entered on the screen by these rates using the following formula: BasicDemographicInformation Price = (CoveredAmount * TermRate) * (1 – PaymentFrequencyRate) BasicPolicyInformation Activity This activity is in the PegaIns-Data-PolCmp-InsuredLife class and used only in calculating the BasicPolicyInformation price.00184 . It is referenced in the BasicPolicyInformation component rule.00102 .00113 .00637 .00119 . Age and Smoker and NonSmoker Decision Values It then multiplies the . TermRate is set by the values set in the VarUnivLifeBasicDemoData table and the age of the insured (Figure 5-8).00126 .2 Non-Smoker Rate .3 Figure 5-8.00323 .00166 .Pricing Rules and Models 5-15 2. It calculates the price using two rates: .00283 . Age of Insured <=25 <=30 <=35 <=40 <=45 <=50 <=60 <=70 Default Else .01327 .

LengthOfCoverageRate is set based on the VarUnivLifeBasicPolicyData table and a hard coded LengthOfCoverage value of 35.00094 .00090 . PaymentFrequencyRate – uses the VarUnivLifeFrequenceDiscount table and the payment frequency entered on the screen.3 Figure 5-9 Age and Smoker Rate Table It then multiplies the value of the .00323 .00686 . Figure 5-9 lists the rates for the ages of the insured.InvestmentGoal property entered on the screen by these rates using the following formula: BasicPolicyInformation Price = (InvestmentGoal * LengthOfCoverageRate) * (1 – PaymentFrequencyRate) . 2.00166 .00119 .00090 . AgeOfInsured <=25 <=30 <=35 <=40 <=45 <=50 <=60 <=70 Default Smoker Rate .00102 .5-16 Insurance Industry Framework Implementation Guide 1.

Pricing Rules and Models 5-17 BasicRiderInformation Activity This activity is in the PegaIns-Data-PolCmp-InsuredLife class and is used only in calculating the BasicRiderInformation price.009) + (SpousalRider * . It calculates the price using hard coded rates and the .SpousalRider values that are entered on the screen in the following calculation: RiderInformation Price = ((ChildRider * .ChildRider and .009) + 200) . It is referenced in the RiderInformation component rule.

Figure 5-10.5-18 Insurance Industry Framework Implementation Guide Automotive Pricing Model Personal Auto The Personal Auto Product structure contains both vehicles and named drivers. Personal Auto Product Structure The pricing calculations for the Personal Auto are: ■ ■ ■ Personal Auto Premium = sum of Garaging Location Premiums Garaging Location Premium = sum of Covered Vehicle Premiums Covered Vehicle Premiums = sum of coverage premiums Coverage Premiums are calculated by activities specific to the coverage listed in Figure 5-11: . Each vehicle has the coverages shown below in the product structure displayed by the Product Explorer. The Vehicles are subcomponents of the GaragingLocations components.

BodilyInjuryFromUnderInsuredAuto OptionalBodoilyInjuryToOthers. . The BodilyInjury coverages and DamageToOthersProperty use the driving record information for the driver that is assigned to the vehicle that the coverage is being calculated for. These pricing activities first determine the particular driver in the Named Driver component that is assigned to the vehicle. BodilyInjuryFromUninsuredAuto PersonalInjuryProtection DamageToOthersProperty MedicalPaymentsPerPerson. the ProductOptionsPage.Pricing Rules and Models 5-19 Component BodilyInjuryToOthers. This information is stored in the DriverToVehicle page group in the top level page for the policy. TowingAndLabor Collision LimitedCollison Figure 5-11. Automobile Specific Coverage Activities Pricing Activity CalculateBodilyInjuryPrice CalculateBodilyInjuryPrice CalculatePersInjProtPrice CalculateDamangeToOthersPropertyPrice CalculatePrice using GeneralAutoRate decision table CalculatePrice using GeneralAutoRate decision table CalculateCollisionPrice CalculateLimitedCollisionPrice Some of the coverage premium calculations have a more complicated algorithm than the basic exposureAmount * rate * adjustment that is implemented with Calculate Price. Comprehensive SubstituteTransportationl. The pricing activity looks at this page group to find the index into the OptionData page list in the NamedDriver component for the assigned driver pricing information.

. Figure 5-12. ignoring any data references to the Named Driver driving record information. except that they do not have the NamedDriver component as seen in the product structure display from the Product Explorer (Figure 5-12).5-20 Insurance Industry Framework Implementation Guide Commercial Auto The Commercial Automotive products are similar to the Personal Auto. Commercial Auto Product Structure The pricing activities are the same activities used for the Covered Vehicle components.

A building for a homeowners policy is defined in IAA as a dwelling. Each building can have content coverage and specified items. This property location has a postal address. with its components and subcomponents. DwellingPremium = (FireCoveragePremium + FloodCoveragePremium + LossOfUseCoveragePremium + ContentCoveragePremium) ContentCoveragePremium = (TheftCoveragePremium + FireCoveragePremium + FloodCoveragePremium + SpecifiedItemPremium) and so on. for a homeowners policy is shown in the ProductExplorer (Figure 5-13). which is a building intended for humans to reside in. Each property can have more than one building defined for it.Pricing Rules and Models 5-21 Homeowners Pricing Model Each policy is written for a single property location. fire and flood coverages apply to all levels of components in the policy. The theft. HomePropertyLocation premium = sum of all Dwelling premiums. . Figure 5-13 Homeowner Product Strructure The pricing calculations for Homeowners are: HomeOwners premium = sum of all HomePropertyLocation premiums. The product structure.

.DeductableAmount <= 5000 the rate is . Each coverage uses the general PegaIns-Data-PolCmp-. As described above.5-22 Insurance Industry Framework Implementation Guide The four basic coverages provided in the Homeowners Framework product are: ■ ■ ■ ■ TheftCoverage FloodCoverage FireCoverage LossOfUseCoverage All are of the class PegaIns-Data-PolCmp-BuildingCoverageBenefit.DeductableAmount <= 500 the rate is . No adjustment is applied to the price calculation for these coverages.DeductableAmount <= 1000 the rate is .CalculatePrice activity (described above) using the SpecifiedItemRate table in the PegaIns-DataPolCmp-BuildingCoverageBenefit class. In the PegaIns-Data-PolCmp-BuildingCoverageBenefit class the rate table is based on deductible amount: If . the premium is calculated for each of the basic coverages.003 Else if .0025 Else the rate is .0027 Else if . ContentCoverage and SpecifiedItem components. and then these premiums are summed up and rolled up the hierarchy to determine a premium price for each of the components in the product.002 These four coverages are included in the Dwelling.

In other cases. the insurance system built in Process Commander will be the system of record where the data is stored in database tables external to the Framework. an external system of record stores the policy information when the Framework is deployed. The Insurance Industry Framework comes with sample integration rules that you can extend in your RuleSet or use as models for creating new integration rules. This means that Party data and Policy data must be recorded and retrieved from other systems. The following sections discuss these integration functions: ■ ■ ■ Integrating Contact Data Integrating Policy Data Integrating Agent and Agency Data . searching for contact or policy data.Chapter 6 Integrating with External Systems This chapter describes how to integrate with other systems to either push or pull data. or reading in the policy data. In most cases. There are a number of integration activities that perform specific functions such as writing out policy data.

While the Framework uses the functionality and rules provided in the PegaApp layer to handle Contact information. The contact search rules are discussed in the corresponding section. write and search the Framework’s contact information. . also referred to as Party Data.6-2 Insurance Industry Framework Implementation Guide Integrating Contact Data Contact Data. is stored as instances of the PegaIns-Interface-Contact class. it uses a subset of these rules to read. They read the contact data by calling a corresponding Connect-SQL rule that is listed in the table under the activity rule. RuleType Activity Connect-SQL Activity Connect-SQL Activity Connect-SQL Activity Connect-SQL Activity Class PegaApp-Interface-Contact PegaApp-Interface-Contact PegaApp-Interface-Contact PegaApp-Interface-Contact PegaApp-Interface-Contact PegaApp-Interface-Contact PegaApp-Interface-BusinessUnit PegaApp-Interface-BusinessUnit PegaIns-Work RuleName AppReadContactInfo AppGetContactInfo AppListAddressesForContact AppListAddressesForContact AppCommOptionsForContact AppListCommOptionsForContact AppListBUsForContact AppListBUsForContact IIFMapPartyDetails Figure 6-1 Reading Contact Rules The activities listed in Figure 6-1 are used in the contact search flow to read the contact data once a particular contact has been selected and the ContactID is known. There are three groups of integration rules provided for handling policy data: ■ ■ ■ Reading Contact Data Rules Writing Contact Data Rules Searching Contact Data Rules Reading Contact Data Rules Contact data is always read through the contact search functionality. The rules listed in Figure 6-1 are the rules that are specific to reading the contact data that you may need to modify when integrating with your contact database table.

The PegaIns-Work.IIFAppContactSearch flow. Each called activity executes the Connect.SQL rule listed directly below the activity in Figure 6-2 to write the data to the database table.Integrating with External Systems 6-3 These activities are called from the PegaIns-Work. RuleType Activity Activity Connect-SQL Activity Connect-SQL Activity Connect-SQL Class PegaApp-Work PegaApp-Interface-Contact PegaApp-Interface-Contact PegaApp-Interface-Contact PegaApp-Interface-Contact PegaApp-Interface-Contact PegaApp-Interface-Contact RuleName AppSaveContactRecordDetails AppSaveContactRecordDetails AppSaveQuickContactDetails AppSaveNewAddressTypeForContact AppSaveNewAddressTypeForContact AppSaveNewCommOptsTypeForContact AppSaveNewCommOptnTypeForContact Figure 6-2. Writing Contact Data Rules The Framework uses the rules listed in Figure 6-2 to add new contact data to the contact table. It calls each of the other activities listed in the table.IIFMapPartyDetails activity maps the data from the contact page on the clipboard into the work object.AppSaveContactRecordDetails Activity This activity is the controlling activity that writes out the contact data. See Chapter 3: What Is Already Setup for more details about this flow and these activities. .IIFAppGetContactDetails activity which is called from the PegaIns-Work. Writing Contact Data Rules PegaApp-Work. These integration rules will require modification if changes are made to the contact storage.

the rules listed in Figure 6-1 handle reading the contact that is selected. RuleType Activity Connect-SQL Class PegaApp-Interface-Account PegaApp-Interface-Contact RuleName AppReadContactList AppListByContactID Figure 6-3. See Chapter 3: What Is Already Setup for details about the Contact Search functionality.AppReadContactList Acitivity This activity generates a list of contacts by running the Connect-SQL AppListByContactID to execute the search. Searching Contact Data Rules PegaApp-Interfrace-Account. . When the search is executed and the list of contacts is displayed.6-4 Insurance Industry Framework Implementation Guide Searching Contact Data Rules The rules listed in Figure 6-3 are used to implement the Contact Data Search.

PolicyID property.ProductOptionData. Writing Policy Rules PegaIns-Work.WritePolicy Activity Writing the policy is handled by the WritePolicy activity. The Framework emulates this by saving images of the Product selections in PegaIns-InterfaceInsurancePolicy with a unique key generated and inserted in the . but it must be recorded and returned to Process Commander so that work items contain the key data. The unique key may be generated external to Process Commander. This activity does the following: ■ Maps the insurance policy data from the embedded data page in the work object.ProductData. PegaIns-Interface-InsurancePolicy Calls SetExposedColumns to set the values of the columns that are exposed in the table Copies work parties to PartiesToAgreement and handles the roles Calls Obj-Save to save the instance of this PegaIns-InterfaceInsurancePolicy class to the database ■ ■ ■ . to the policy interface class. pyWorkPage. There are three groups of integration rules provided for handling policy data: ■ ■ ■ Writing Policy Rules Reading Policy Rules Searching Policy Rules Writing Policy Rules Figure 6-4 lists the integration rules that may need to be modified to write to a new policy table: RuleType Activity Activity Declare-Index Class PegaIns-Work PegaIns-Interface-InsurancePolicy PegaIns-Interface-InsurancePolicy RuleName WritePolicy SetExposedColumns PolicyLink Figure 6-4.Integrating with External Systems 6-5 Integrating Policy Data The Application and ChgPolicy flows write policy data.

the IssuePolicy activity is applied to both the PegaIns-Work-Application and PegaInsWork-ChgPolicy classes. PolicyLink Rule Declare Index The Rule-Declare-Index instance (Figure 6-5) automatically populates the policy link table. The PegaIns-InterfaceInsurancePolicy.SetExposedColumns activity handles the setting of these columns. Because the processing to issue a policy is different for New Business or Policy Change. SetExposedColumns Activity Policy data is written out by Process Commander as a blob.6-6 Insurance Industry Framework Implementation Guide The WritePolicy activity is called from the IssuePolicy activity. PegaIns-Interface-InsurancePolicy. PolicyLink Declare Index Rule . Figure 6-5. with a set of exposed columns to facilitate policy searching. PegaIns-Interface-InsurancePolicy.

ReadingPolicy Rules PegaIns-Work. Any specialized processing for a given work type is done in the PostFetchPolicyData activity. FetchPolicyData Activity This activity: ■ Reads policy data from the PegaIns-Interface-InsurancePolicy class using the Obj-Open method Maps the data to the work object in the embedded page of the class PegaIns-Data-InsurancePolicy Calls PostFetchPolicyData for any additional processing that may be needed ■ ■ This activity is in the PegaIns-Work class because it implements common functionality to read policy data across all types of work.Integrating with External Systems 6-7 Reading Policy Rules Figure 6-6 lists the integration rules that may need to be modified when reading from a new policy table. For example. PostFetchPolicyData Activity Additional logic for reading a policy is needed in the ChgPolicy flow. the TransactionEffectiveDate is blanked out to be ready to be filled in from the screen when executing the ChgPolicy flow. PegaIns-Work-ChgPolicy. RuleType Activity Activity Class PegaIns-Work PegaIns-Work-ChgPolicy RuleName FetchPolicyData PostFetchPolicyData Figure 6-6. .

6-8 Insurance Industry Framework Implementation Guide Searching Policy Rules Figure 6-7 lists the integration rules that may need to be modified to search a new policy database table. RuleType Connect-SQL Connect-SQL Connect-SQL ListView ListView ListView ListView Class PegaIns-Interface-InsurancePolicy PegaIns-Interface-InsurancePolicy PegaIns-Interface-InsurancePolicy PegaIns-Interface-InsurancePolicy PegaIns-Interface-InsurancePolicy PegaIns-Interface-ContactPolicyRoleSummary PegaIns-Interface-PolicyLink RuleName IIFGetPolicyListForPolicyholder IIFGetPolicyListForPolicyholder_Date_D ate_PolicyType IIFGetPolicyListForPolicyholderAndAuth orizedParty ListPoliciesForPolicyholder ListPoliciesForPolicyholder_Date_Policy Type ListPoliciesByContactAndRole ListPolicyTransactions Figure 6-7. SearchPolicy Rules .

The following table (Figure 6-8) lists the integration rules that may need to be modified when accessing the agency lob data.BuildAgentProfile Activity This activity creates the AgentProfile page on the clipboard.Integrating with External Systems 6-9 Integrating Agent and Agency Data In the framework. Assigning an agency to a policy during the New Business flow. Part of the agency data is information about the Lines of Business that an agency can write. Part of the key to this table is the AgencyCode which links it to an agency. The information above on integrating contact data can be applied to the integration of agent data. . It gets the agent and agency data from the contact and business unit tables respectively using the activites mentioned above. The agency data for a particular policy is ultimately stored as an embedded page in the policy. agent data is stored as contacts in the PA_CONTACT table and agency data is stored in the PA_BUSINESSUNIT table. It then calls an RDB-List that executes IIFGetAgencyLOBs to get the agency line of business data from the database. This data is stored in the IIF_AGENCY_LOB table. An AgencyProfile is created filling in agent and agency data for the operator. There are two integration points where the AgencyLOB data is accessed: Creating the AgencyProfile for an operator that is an agent. AgencyLOB integration rules PegaIns-Data-AgentProfile. the agency data is manually assigned to the policy. RuleType Activity Activity Connect-SQL Class PegaIns-Data-AgentProfile PegaIns-Data-Party-Org-Agency PegaIns-Data-AgencyLOB RuleName BuildAgentProfile GetAgencyData IIFGetAgencyLOBs Figure 6-8. The agents and agencies are linked together through the PA_CONTACT_BUSINESSUNIT_LINK table. When an operator is filling out a New Business application ‘On Behalf Of’ an agent.

IIFGetAgencyLOBs Connect-SQL This rule contains SQL that will need to be replaced with the correct SQL to get your agency line of business data. When the AgencyCode is populated. this activity retrieves the agency data for that AgencyCode. Agency Line of Business data is retrieved by calling an RDB-List that executes IIFGetAgencyLOBs PegaIns-Data-AgencyLOB. The data is retrieved in two steps: 1.6-10 Insurance Industry Framework Implementation Guide PegaIns-Data-Party-Org-Agency.GetAgencyData Activity This activity is called when an agency is manually assigned to a policy in the New Business flow. . Agency data is retrieved from the business_unit table using the data in the AgencyCode property 2.

Topics covered are: ■ ■ ■ ■ ■ ACORD processing flow and architecture ACORD processing rules Building XML rules Adding a new product Sample Messages .Chapter 7 Processing ACORD XML Messages The chapter describes the design and processing flow for ACORD XML inbound and outbound messages that pass data between insurance institutions and other entities and the Insurance Industry Framework.

7-2 Insurance Industry Framework Implementation Guide ACORD Processing Flow and Architecture The Framework is designed to receive and process both incoming and outgoing ACORD XML messages. When installed. It integrates with external systems through a SOAP Service. . For this purpose. a separate RuleSet called PegaInsACORD has been defined. the framework set up to: ■ ■ ■ ■ ■ Receive an inbound ACORD XML message from an external system through a SOAP service Parse and map the data from the message to a work object page on the clipboard Execute a flow that processes the data and calculates the premium and creates a work object Map the data from the work object page on the clipboard to the XML outbound response message Send an outbound XML message to an external system using the SOAP service in ACORD standard format A diagram of the inbound and outbound message process is shown in Figure 7-1.

Processing ACORD XML Messages 7-3 Figure 7-1. Insurance Framework ACORD Message Processing Diagram .

7-4 Insurance Industry Framework Implementation Guide ACORD Processing Rules This section describes the rules that are used to process messages. A table is provided for each rule that outlines the: ■ ■ ■ ■ Rule type Name of the Applies To class Description of its role in the processing of the message Modifications needed to extend the rule for deployment . All rules are defined in PegaInsACORD ruleset. Some of these can be used directly when a new product is defined while others need to be copied and modified in their respective work class in order to add a new product to the ACORD Design.

GetACORD SOAP Service Rule Type Applies To Package Description Rule-Service-SOAP PegaIns-Work MyCoInsureACORD Called when the external system tries to connect to the Framework using the SOAP service. It creates a page called requestpage on the clipboard and copies the inbound XML onto that page. the ProcessACORDMessage activity is called in PegaIns-Work-Application to process the message.Processing ACORD XML Messages 7-5 General Rules General rules are the rules in the ACORD message process configuration that are reusable in any of products that you may add when extending the Framework. None Modifications Needed Note: The GetACORD Soap Service rule is included with the Framework and can be used for the processing of all products. It then calls the ProcessAcordMessage activity in the respective work class for the message. The general rules are placed in parent classes. Following that. It initiates the ProcessAcordMessage SOAP activity in the PegaIns-WorkApplication class that determines the message type then gets the respective work class for the ACORD message (for example: PegaInsWork-Application-Pers-Automotive). .

Append the tag name to the local variable msgTags in the java step (Instructions to append the string are provided in the java step). In the SetWorkPageClass decision table. the ProcessACORDMessage activity of the work class (Depending on the input message type) is called to continue the parsing. Depending on the status message. Using ProductSelection decision table. the ProcessACORDMessage flow creates the response message. the message type is set to the pyLabel property. It finds the message type and calls ProductSelection and SetWorkPageClass decision tables to set the pyWorkPage class and pyLabel. Finally. Modifications Needed . Include the tag name of the message type (like PersAutoPolicyQuoteInqRq (for PersonalAuto) and HomePolicyQuoteInqRq for HomeOwner) in the Java step of the activity. This is the main activity in the ACORD design. Next. the flow will be executed.7-6 Insurance Industry Framework Implementation Guide ProcessACORDMessage Activity Rule Type Applies To Package Description Rule-Obj-Activity PegaIns-Work-Application MyCoInsureACORD Called from the SOAP service to process the ACORD message. the pyLabel is passed as the input property and returns the respective work class of the product. If any errors found during the validation of the message or processing the message then it sets the task status to errorsfound. calculates the premium and handles the errors.

Need to include pyLabel and the work class for the respective product in this rule. Modifications Needed SetWorkPageClass Decision Table Rule Type Applies To Description Rule-Declare-DecisionTable PegaIns-Work-Application Sets the work class to a local property depending on pyLabel. Append the pyLabel and the respective work class for the product. Append the tag name and the respective product name for the product. Include the message type tag and the product name for the respective tag in this rule. Modifications Needed .Processing ACORD XML Messages 7-7 ProductSelection Decision Table Rule Type Applies To Description Rule-Declare-DecisionTable PegaIns-Work-Application Sets the product name to the pyLabel property depending on the input message type. It will set the work class dynamically depending upon the input message type.

None Modifications Needed . handles errors and creates the appropriate response messages. Respective price calculation activities will be called from the product.7-8 Insurance Industry Framework Implementation Guide ProcessACORDMessage Flow Rule Type Applies To Description Rule-Obj-Flow PegaIns-Work-Application Calls the activities for price calculation. and premium is calculated None Modifications Needed CreateACORDResponse Activity Rule Type Applies To Description Rule-Obj-Activity PegaIns-Work-Application Calls the (Rule-Obj-Xml) QuoteResponse instance for the work class of the product to set the outbound ACORD message on the clipboard page.

create the Obj-XML rules based on tthe clipboard structure (see the QuoteResponse instance for the personal auto product).Processing ACORD XML Messages 7-9 QuoteResponse XML Rule Type Applies To Description Rule-Obj-XML PegaIns-Work-Application-Pers-Automotive Gets the data from clipboard properties. It calls the (Rule-Obj-Xml) QuoteErrorResponse of particular work class of the product to set the outbound ACORD message on to the clipboard page to send the error response data. None Modifications Needed . Modifications Needed CreateACORDErrorResponse Activity Rule Type Applies To Description Rule-Obj-Activity PegaIns-Work-Application If there are any errors while processing the message. In order to set the clipboard property values. creates an XML message and sets the message to a string property on the clipboard. this activity is invoked. Save this rule into the work class and modify the code accordingly. This rule incorporates some other Rule-Obj-XML rules.

In order to get the clipboard property values. create the Obj-XML rules according to the clipboard structure (See the QuoteResponse instance for the personal auto product). creates an XML message and sets the message to a string property on the clipboard. Modifications Needed . This rule can be invoked if there are any error messages on the clipboard pages. Save this rule into the work class and modify the code accordingly.7-10 Insurance Industry Framework Implementation Guide QuoteErrorResponse XML Rule Type Applies To Description Rule-OBJ-XML PegaIns-Work-Application-Pers-Automotive Gets the data from the clipboard properties.

Processing ACORD XML Messages 7-11 Parsing Rules These general rules parse the incoming ACORD message and place it on the clipboard.Parse-XML PegaIns-Data-ACORD-SignonRq Parses the Sign on related data from the inbound message onto the clipboard page SignOnRq None ParseApplicant Activity Rule Type Applies To Description Rule-OBJ-Activity PegaIns-Work-Application Gets the chunk of xml from the original xml and calls the parsing rules to map the applicant details onto the clipboard structure. This rule is a generalized rule. Modifications Needed None . therefore. this can be reusable in all the products. It gets the chunk of xml from the original message for the InsuredOrPrincipal tag and stores the value in a value list. SignonRq Parse XML Rule Type Applies To Description Modifications Needed Rule.

7-12 Insurance Industry Framework Implementation Guide ApplicantInfo Parse XML Rule Type Applies To Description Modifications Needed Rule-Parse-XML Data-Party Parses the applicant information onto the clipboard structure. It also gets the chunk of xml from the original message for Producer tag and stores the value in a value list. None Modifications Needed MapBroker Parse XML Rule Type Applies To Description Modifications Needed Rule-Parse-XML Data-Party Parses the Broker information onto the clipboard structure. if provided with the chunk of xml None ParseBroker Activity Rule Type Applies To Description Rule-Obj-Activity PegaIns-Work-Application Gets the chunk of xml from original xml and then calls the parsing rules to map the Broker (producer) details on to the clipboard structure. if provided with the chunk of xml None .

these rules should be copied to the work class of the particular application and modified to meet your processing needs. Modify the steps according to the product. This activity calls SetupProductData of PegaSPWork. Save this rule into the product work class. Rules need to be modified/created in this activity according to the product design. Save this rule into each product class. the rule referenced here is for the PegaIns-Work-ApplicationPers-Automotive product). A Work object is created by calling the AddWork activity.Processing ACORD XML Messages 7-13 Application Specific Rules The following rules are application-specific. Modifications Needed . The examples in this section are instances of the rules used to process the personal auto product. the ParseMessage activity in the respective work class of the product is called to parse the message. After that.to create the clipboard structure of the application. ProcessACORDMessage Activity Rule Type Applies To Description Rule-Obj-Activity PegaIns-Work-Application-Pers-Automotive This rule belongs to the work class of the product (For example. When a product is added to the Framework.

Modifications Needed AcordProductOptionData Parse XML Rule Type Applies To Description Modifications Needed Rule-Parse-XML PegaIns-Work-Application-Pers-Automotive Maps the product option data (like plannedenddate and inceptiondate) onto the clipboard page. All the parsing mechanisms related to the product are implemented in this activity. Save this rule into the product work class. It calls subsequent activities. Different Parse-XML rules need to be created according to the clipboard structure of the product. Modify the steps according to the product design and clipboard structure of the product. Save this rule into the product work class. browsing the clipboard structure to parse the inbound XML on to the clipboard properties. Modify properties according to the product design and clipboard structure of the product.7-14 Insurance Industry Framework Implementation Guide ParseMessage Activity Rule Type Applies To Description Rule-Obj-Activity PegaIns-Work-Application-Pers-Automotive This activity is defined in the work class of the product (eg: PegaIns-Work-Application-Pers-Automotive). .

If required can be used in the commercial auto product. ParseAcordGaragingLocations Activity Rule Type Applies To Description Modifications Needed Rule-Obj-Activity Embed-PegaSP-ProductComponents This rule is specified for use in the personal auto product. Used in only personal auto. These rules provide good examples to work from when implementing new products but are not be useful for any other product by simply saving them into another work class. .Processing ACORD XML Messages 7-15 Note: The following activity and parsing rules support the clipboard structure for processing the personal auto product.

ParseAcordCoveredVehicles Activity Rule Type Applies To Description Rule-Obj-Activity Embed-PegaSP-ProductComponents This rule is specified for use in the personal auto product. And finally calls the ParseAcordInsuredVehicleData activity for each option data page Used in only personal auto. If required can be used in the commercial auto product. this activity will be called. If the value list has more than one value then it will call InsertSubPage activity of PegaSP-Work. Used in only personal auto.7-16 Insurance Industry Framework Implementation Guide ParseAcordInsuredPropertyLocation Activity Rule Type Applies To Description Modifications Needed Rule-Obj-Activity PegaIns-Data-PolCmp-InsuredPropertyLocation This rule is specified for use in the personal auto product. For each component (CoveredVehicles) page. If required can be used in the commercial auto product. This activity gets the chunk of xml for <persVeh> tag and appends the values to the value list on the clipboard. For each optiondata page (Location) this activity is called. Modifications Needed .to create one more option data page.

If required can be used in the commercial auto product. For each Optiondata page (for vehicles) this activity will be called. If required can be used in the commercial auto product. if provided with the chunk of xml for vehicle data. Modifications Needed VehicleInfo Parse XML Rule Type Applies To Description Modifications Needed Rule-Parse-XML PegaIns-Data-PolCmp-InsuredVehicle This parse xml will map the vehicle details onto the clipboard structure. Used in only personal auto. It will map the vehicle info on to the clipboard as well. This activity gets the chunk of xml for each coverage tag in the input XML and appends it to the CoverageList on the clipboard. .Processing ACORD XML Messages 7-17 ParseAcordInsuredVehicleData Rule Type Applies To Description Rule-Obj-Activity PegaIns-Data-PolCmp-InsuredVehicle This rule is specified for use by the personal auto product. Used in only personal auto.

It is called for each element in the coverage list.7-18 Insurance Industry Framework Implementation Guide ParseAcordCoverages Activity Rule Type Applies To Description Rule-Obj-Activity PegaIns-Data-PolCmp-InsuredVehicle Maps the coverage details on to the clipboard structure. Used in only personal auto. It determines the coverage code of and based on coverage code it maps the values on to the clipboard structure. If required can be used in the commercial auto product. Modifications Needed .

it is necessary to add a When rule for each tag to validate if the value of property is blank before including the tag into the message.Processing ACORD XML Messages 7-19 Building Rule-Obj-XML rules This section describes how the Rule-Obj-XML rules used in the process should be designed and configured as well as how to include and validate the optional tags into a message. For a better understanding of this type of configuration. refer to the QuoteResponse XML rule created for the Personal Auto Product. Sample of Rule Incorporating XML and JSP Features . ■ Figure 7-2. JSP tags and other Obj-XML rules into an ObjXML rule. Figure 7-2 provides a visual example of how to include When rules. ■ There are many optional tags that may or may not be included in an outbound message. and embedded into the other XML rules. According to ACORD standards. an optional tag should not appear in the message if it does not contain a value (if the value of tag is blank). Note: Rule-Obj-XML rules should be built using JSP tags instead of the HTML directives option. To comply with that standard. All Rule-Obj-XML rules should be based on the clipboard structure.

Step 4. Create sample inbound XML for the product if it is not available. Step 3. Step 1. The ACORD help file is a good reference to use to help create the sample messages. Create/Save the ParseMessage activity in the respective work class of the ACORD message and call it in the ProcessAcordMessage of the work class. This activity will bundle all the Parsing rules for the product . Update the java step (Desc: Set the tag for inbound message here) in the ProcessACORDMessage activity in the PegaIns-Work-Application class. Step 2.7-20 Insurance Industry Framework Implementation Guide Adding a New Product This section describes the design and configuration steps to follow when ACORD messages for a new product is introduced. This is used to find the message type. Update the ProductSelection and SetWorkPageClass Decision tables of PegaIns-Work-Application class to include product name and the work class for the new product. Step 5. Create/Save the ProcessAcordMessage activity in the respective work class of the ACORD message (For example: PegaIns-Work-Application-PersAutomotive). Append the product tag to the local variable msgTags (See PersAutoPolicyQuoteInqRq and HomePolicyQuoteInqRq for examples). Customize the activity to populate the required product to the clipboard. Follow the instructions mentioned in the java step to append the tag.

Call the AddWork activity from the ProcessAcordMessage activity to create the work object. When there are repeating elements (eg: <PersVeh>) in the message. Step 9. Step 8. See QuoteResponse and QuoteErrorResponse in the Personal Auto Product for reference. For that. Create the Rule-Parse-XML and the activities to call these Rule-Parse-XML rules by hand to map the request data from the message to the clipboard.Work.InsertSubPage activity is used.Processing ACORD XML Messages 7-21 Step 6. for each value in the value list InsertSubPage activity is called and corresponding component is added to the clipboard. Use JSP tags instead of using the HTML. These Parse-XML rules will be bundled in ParseMessage activity. add a When condition to not to include the tag in outbound message if the value is blank. You will get an idea by looking into the Personal Auto product. . same number of corresponding components should be created in the Clipboard. Then. Chunk xml which contains the repeating group of the main xml message is taken to a value list property (See the ParseAcordCoveredVehicles activity in EmbedPegaSP-Component class for reference) using the GetXMLElementbyTag Rule-Utility-Function. These rules should be created according to the clipboard structure and all rules should be embedded into the QuoteResponse XML rule of the work class of the product. the PegaSP. After that. Create QuoteResponse and QuoteErrorResponse Rule-Obj-Xml’s in the respective work class of the product. − For each tag that needs to be included in the outbound message. Rule-Parse-XML rules specific to each product must be created and called them in the ParseMessage activity. All the parsing rules should be created by looking into clipboard structure. Step 7. do the following: − Create the Rule-Obj-XML rules by hand to map the response data from the product’s work page on the clipboard to the xml message.

The message samples are available for: ■ Inbound Request Messages Personal Auto Quote Home Policy Quote Outbound Response Messages Personal Auto Quote Home Policy Quote − − ■ − − .7-22 Insurance Industry Framework Implementation Guide Sample Messages Sample inbound and outbound XML message formats are included in the installation media.

You can use these sample database tables as a starting point for integration or for demonstrating the system environment. The following information.Appendix A Database Tables The Insurance Industry Framework comes with a robust set of industry standard sample data that simulates the processing environment. where applicable. This appendix includes a list of those database tables that are installed with the Framework. is included for each database: ■ ■ ■ ■ ■ ■ Description of the database List of Columns with data type and size Constraints Large object (LOB) storage attributes Foreign key references not defined in the database Referencing tables and columns .

foreign keys. The Insurance Industry Framework follows a universal approach and uses lowercase characters. List of Tables in the Insurance Industry Framework . about column structures. Tables and lists beginning on page A-3 provide details. Tables fall into two categories: ■ ■ The IIF (Insurance Industry Framework) database tables that are specific to the framework and contain Insurance specific data. and referencing tables for each of the tables listed in Figure A-1. Note: In Oracle. all table data and column headings appear in uppercase characters. constraints. IIF_Tables IIF_POLICY IIF_AGENCY_LOB PA_ Tables PA_ADDRESS PA_ADDRESS_TYPE PA_BUSINESSUNIT PA_BUSINESSUNIT_LINK PA_COMMUNICATION_OPTIONS PA_COMMUNICATION_TYPES PA_CONTACT_BUSINESSUNIT_LINK PA_CUSTOMER_TYPE PA_INDUSTRY PA_NOTES PA_PRODUCT PA_PRODUCT_TYPE IIF_POLICY_LINK Figure A-1. The PA (PegaApp) tables that contain party information about Contacts.A-2 Insurance Industry Framework Implementation Guide Database Tables Figure A-1 lists the tables in the database structure. LOB storage. but correct SQL is in lowercase. where applicable.

Database Tables A-3 IIF_POLICY This table stores policy specific information. Replace calls to this table with calls to your external database tables or the interface to the system of record for your policy data. Columns Name PXCREATEDATETIME PXCREATEOPNAME PXCREATEOPERATOR PXCREATESYSTEMID PXINSNAME PXOBJCLASS PXUPDATEDATETIME PXUPDATEOPNAME PXUPDATEOPERATOR PXUPDATESYSTEMID PYLABEL PZINSKEY POLICYID MODNUMBER TRANSACTIONEFFECTIVEDATE TRANSACTIONPROCESSDATE TRANSACTIONENDDATE Datatype DATE VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 DATE VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 NUMBER DATE DATE DATE Size 7 128 128 32 128 96 7 128 128 32 64 255 20 3 7 7 7 0 Scale Nulls? Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No No No No No Yes Dflt .

A-4 Insurance Industry Framework Implementation Guide Name POLICYEFFECTIVEDATE POLICYENDDATE POLICY_DESCRIPTION POLICYSTATUS ACCOUNTPACKAGE ACCOUNTTYPE ACTIVE ADDEDBY ADDRESSFROMDATE ADDRESSLASTCHANGEDATE ADDRESSLINE1 ADDRESSLINE2 ADDRESSLINE3 ADDRESSLINE4 ADDRESSLINE5 ADDRESSTODATE ADDRESSUPDATECOUNTER APPLICATIONTYPE BUSINESSPHONE BUSINESSUNITID CELLPHONE CITY CONTACTID COUNTRYCODE Datatype DATE DATE VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 DATE DATE VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 DATE NUMBER VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 Size 7 7 50 20 20 20 5 50 7 7 36 36 36 36 36 7 3 20 20 20 17 20 20 20 Scale Nulls? Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Dflt 0 Yes Yes Yes Yes Yes Yes Yes Yes 0 .

Database Tables A-5 Name CUSTOMERVALUE DATEADDED DATEDELETED DATEUPDATED DELETEDBY EMAIL FAX FIRSTNAME HOMEPHONE LASTNAME MIDDLENAME PRODUCTID ROLEDESCRIPTION SECURITYANSWER SECURITYQUESTION SPECIALINSTRUCTIONS STATECODE STATEMENTCUTDATE UPDATEDBY ZIPCODE PZPVSTREAM POLICYTYPE Figure A-2. IIF_POLICY Table Columns Datatype VARCHAR2 DATE DATE DATE VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 BLOB VARCHAR2 Size 20 7 7 7 50 50 20 20 17 50 20 32 20 50 100 100 2 2 50 12 Scale Nulls? Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Dflt 20 Yes .

A-6 Insurance Industry Framework Implementation Guide Constraints Constraint Name Type Disable Referenced Schema Referenced Table Cascade On Delete Check Condition Deferrable? No Validate? Initially Deferred? RELY (Do Not Enforce)? No No No No No SYS_C0014541 PRIMARY No Figure A-3. IIF_POLICY Table Constraints Constraint Column Details Table Columns POLICYID MODNUMBER TRANSACTIONEFFECTIVEDATE TRANSACTIONPROCESSDATE Constraint SYS_C0014541 Referenced Column Figure A-4. IIF_POLICY Constraint Column Details .

IIF_POLICY Referencing Tables and Columns Referencing Table IIF_POLICY_LINK Referencing Column POLICYID MODNUMBER TRANSACTIONEFFECTIVEDATE TRANSACTIONPROCESSDATE . IIF_POLICY Table LOB Attributes Referencing Tables and Columns Column POLICYID MODNUMBER TRANSACTIONEFFECTIVEDATE TRANSACTIONPROCESSDATE Figure A-6.Database Tables A-7 Large Object (LOB) Storage Attributes Table Column Tablespace: Enable Lob Storage in Row Number of blocks accessed at one time (CHUNK): Space used for new version (PCTVERSION): Lob Cache: Generate full redo for LOB data pages(LOGGING) PZPVSTREAM USERS Yes 16384 Bytes 10 % Off Yes Figure A-5.

a policy id and the role that the contact or business unit has with the policy Columns Name PXCREATEDATETIME PXCREATEOPNAME PXCREATEOPERATOR PXCREATESYSTEMID PXINDEXCOUNT PXINDEXPURPOSE PXINSINDEXEDCLASS PXINSINDEXEDKEY PXINSNAME PXOBJCLASS PXPRIVILEGECLASS PXPRIVILEGENAME PXUPDATEDATETIME PXUPDATEOPNAME PXUPDATEOPERATOR PXUPDATESYSTEMID PYLABEL PZINSKEY Datatype DATE VARCHAR2 VARCHAR2 VARCHAR2 NUMBER VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 DATE VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 Size 7 128 128 32 18 32 96 255 128 96 64 256 7 128 128 32 64 255 0 Scale Nulls? Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Dflt .A-8 Insurance Industry Framework Implementation Guide IIF_POLICY_LINK This table maintains the relationship between a contact or business unit.

IIF_POLICY_LINK Table Columns .Database Tables A-9 PARTYTYPE PARTYID ROLETYPE TRANSACTIONEFFECTIVEDATE TRANSACTIONPROCESSDATE TRANSACTIONENDDATE POLICYTYPE POLICYID MODNUMBER ACTIVE POLICYSTATUS VARCHAR2 VARCHAR2 VARCHAR2 DATE DATE DATE VARCHAR2 VARCHAR2 NUMBER VARCHAR2 VARCHAR2 1 128 5 7 7 7 20 20 3 5 20 0 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Figure A-7.

IIF_POLICY_LINK Table Constraints Constraint Column Details Table Columns PZINSKEY Constraint POLICYLINK_INDEX_PK Referenced Columns Figure A-9. IIF_POLICY_LINK Constraint Column Details .A-10 Insurance Industry Framework Implementation Guide Constraints Constraint Name Type Disable Referenced Schema Referenced Table Cascade On Delete Check Condition Deferrable? No Validate? Initially Deferred? RELY (Do Not Enforce)? No No No No No POLICYLINK_INDEX_PK PRIMARY No Figure A-8.

IIF_POLICY_LINK Foreign Key Relationships .Database Tables A-11 Foreign Key Relationships Column POLICYID MODNUMBER TRANSACTIONEFFECTIVEDATE TRANSACTIONPROCESSDATE PARTY ID ROLETYPE Referencing Table IIF_POLICY Referencing Column POLICYID MODNUMBER TRANSACTIONEFFECTIVEDATE TRANSACTIONPROCESSDATE CONTACTID ROLETYPE PA-CONTACT PA_ROLES Figure A-10.

Columns Name AGENCYCODE LINEOFBUSINESS LOBEFFECTIVEDATE LOBEXPIRATIONDATE LICENSEDSTATE COMMISSIONPERCENTAGE Datatype VARCHAR2 VARCHAR2 DATE DATE VARCHAR2 VARCHAR2 Size 20 30 7 7 2 3 Scale Nulls? No No No Yes No Yes Dflt Figure A-11.A-12 Insurance Industry Framework Implementation Guide IIF_AGENCY_LOB This table stores the line of business information that an agency is licenses to write in a given state for a stated period of time. IIF_AGENCY_LOB Table Columns .

IIF_AGENCY_LOB Table Constraints Constraint Column Details Table Columns AGENCYCODE LINEOFBUSINESS LOBEFFECTIVEDATE LICENSEDSTATE Constraint SYS_C0017441 Referenced Columns Figure A-13.Database Tables A-13 Constraints Constraint Name Type Disable Referenced Schema Referenced Table Cascade On Delete Check Condition Deferrable? No Validate? Initially Deferred? RELY (Do Not Enforce)? No No No No No SYS_C0017441 PRIMARY No Figure A-12. IIF_AGENCY_LOB Constraint Column Details .

A-14 Insurance Industry Framework Implementation Guide PA_ADDRESS This table stores address information about contacts and business units. Replace calls to this table with calls to your data tables. Columns Name OWNERID ADDRESSID ADDRESSTYPE ADDRESSLINE1 ADDRESSLINE2 ADDRESSLINE3 ADDRESSLINE4 ADDRESSLINE5 CITY STATECODE ZIPCODE COUNTRYCODE DATEFROM DATETO PRIMARYADDRESS NOTES ACTIVE DATEADDED Datatype VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 DATE DATE VARCHAR2 VARCHAR2 VARCHAR2 DATE Size 12 1 4 36 36 36 36 36 20 2 10 12 7 7 5 255 5 7 Scale Nulls? No No No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Dflt .

PA_ADDRESS Table Constraints . PA_ADDRESS Table Columns Constraints Constraint Name Type Disable Referenced Schema Referenced Table Cascade On Delete Check Condition Deferrable? No Validate? Initially Deferred? RELY (Do Not Enforce)? No No No No No SYS_C0013127 PRIMARY No Figure A-15.Database Tables A-15 Name ADDEDBY DATEUPDATED UPDATEDBY DATEDELETED DELETEDBY Datatype VARCHAR2 DATE VARCHAR2 DATE VARCHAR2 Size 50 7 50 7 50 Scale Nulls? Yes Yes Yes Yes Yes Dflt Figure A-14.

A-16 Insurance Industry Framework Implementation Guide Constraint Column Details Table Columns OWNERID ADDRESSID ADDRESSTYPE DATEADDED Constraint SYS_C0013127 Referenced Columns Figure A-16. PA_ADDRESS Foreign Key Relationships . PA_ADDRESS Constraint Column Details Foreign Key Relationships Column OWNERID OWNERID OWNERID Referencing Table PA_CONTACT PA_BUSINESSUNIT PA_ADDRESS_TYPE Referencing Column CONTACTID BUSINESSUNITID BUSINESSUNITID Figure A-17.

Database Tables A-17 PA_ADDRESS_TYPE This table stores the valid address types (for example. Replace the sample entries in this table with address types valid for your configuration. HOME or BILLING) used within the system.PA_ADDRESS_TYPE Table Columns Constraints Constraint Name Type Disable Referenced Schema Referenced Table Cascade On Delete Check Condition Deferrable? No Validate? Initially Deferred? RELY (Do Not Enforce)? No No No No No SYS_C0013128 PRIMARY No Figure A-19. PA_ADDRESS_TYPE Table Constraints . Columns Name ADDRESSTYPE ADDRESSTYPEDESCRIPTION ADDRESSOUTLOOKCODE Datatype VARCHAR2 VARCHAR2 VARCHAR2 Size 4 36 40 Scale Nulls? No No Yes Dflt Figure A-18 .

A-18 Insurance Industry Framework Implementation Guide Constraint Column Details Table Columns ADDRESSTYPE Constraint SYS_C0013128 Referenced Columns Figure A-20. PA_ADDRESS_TYPE Constraint Column Details Referencing Tables and Columns Column ADDRESSTYPE Referencing Table PA_ADDRESS Referencing Column ADDRESSTYPE Figure A-21. PA_ADDRESS_TYPE Referencing Tables and Columns .

Columns Name BUSINESSUNITID BUSINESSUNITNAME CUSTOMERTYPE PARENT INDUSTRYCODE PRIORITYTYPE ACTIVE TAXID WEBSITE CUSTOMERLOGO REFERENCE TERRITORY CUSTOMEREMPLOYEE PRIMARYADDRESS PRIMARYCONTACT CUSTOMERSATISFACTION BUSINESSDESCRIPTION DIVISION Datatype VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 Size 20 50 15 12 15 36 5 12 50 50 1 12 12 5 10 20 255 30 Scale Nulls? No No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Dflt .Database Tables A-19 PA_BUSINESSUNIT This table stores information about business units. Replace calls to this table with calls to your data tables.

A-20 Insurance Industry Framework Implementation Guide Name INTERNALREFERENCE DATEADDED ADDEDBY DATEUPDATED UPDATEDBY DATEDELETED DELETEDBY PIN PRIORITYNOTE STATUS Datatype VARCHAR2 DATE VARCHAR2 DATE VARCHAR2 DATE VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 Size 30 7 50 7 50 7 50 30 255 30 Scale Nulls? Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Dflt Figure A-22. PA_BUSINESSUNIT Table Columns .

PA_BUSINESSUNIT Constraint Column Details . PA_BUSINESSUNIT Table Constraints Constraint Column Details Column BUSINESSUNITID CUSTOMERTYPE INDUSTRYCODE Constraint SYS_C0013137 SYS_C0013138 SYS_C0013139 Referenced Column ADDRESSTYPE CUSTOMERTYPE INDUSTRYCODE Figure A-24.Database Tables A-21 Constraints Constraint Name Type Disable Referenced Schema Referenced Table Cascade On Delete Check Condition Deferrable? No Validate? Initially Deferred? RELY (Do Not Enforce)? No No No No No No No No No No No No No SYS_C0013137 PRIMARY No SYS_C0013138 FOREIGN No FRM5102 PA_CUSTOMER_TYPE No SYS_C0013139 FOREIGN No FRM5102 PA_INDUSTRY No Figure A-23.

PA_BUSINESSUNIT Referencing Tables and Columns .A-22 Insurance Industry Framework Implementation Guide Referencing Tables and Columns Column BUSINESSUNITID BUSINESSUNITID Referencing Table PA_CONTACT_BUSINESSUNIT_LINK PA_ADDRESS Referencing Column BUSINESSUNITID OWNERID Figure A-25.

Database Tables A-23 PA_BUSINESSUNIT_LINK This table stores business-to-business relationships. PA_BUSINESSUNIT_LINK Table Columns . Columns Name BUSINESSUNIT1 BUSINESSUNIT2 TYPE DESCRIPTION ROLETYPE MEMO DATEADDED ADDEDBY DATEUPDATED UPDATEDBY DATEDELETED DELETEDBY ACTIVE Datatype VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 DATE VARCHAR2 DATE VARCHAR2 DATE VARCHAR2 VARCHAR2 Size 20 20 50 100 5 255 7 50 7 50 7 50 5 Scale Nulls? No No No Yes Yes Yes No Yes Yes Yes Yes Yes Yes Dflt Figure A-26. For example. it shows that Acme Technology is a subsidiary of Acme Software.

A-24 Insurance Industry Framework Implementation Guide Constraints Constraint Name Type Disable Referenced Schema Referenced Table Cascade On Delete Check Condition Deferrable? No Validate? Initially Deferred? RELY (Do Not Enforce)? No No No No No No No No No SYS_C0013140 PRIMARY No SYS_C0013141 FOREIGN No FRM5102 PA_BUSINESSUNIT No Figure A-27. PA_BUSINESSUNIT_LINK Constraint Column Details . PA_BUSINESSUNIT_LINK Table Constraints Constraint Column Details Column BUSINESSUNIT1 BUSINESSUNIT2 TYPE DATADDED BUSINESSUNIT1 Constraint SYS_C0013140 Referenced Column ADDRESSTYPE SYS_C0013141 BUSINESSUNITID Figure A-28.

Replace calls to this table with calls to your data tables. PA_COMMUNICATION_OPTIONS Table Columns .Database Tables A-25 PA_COMMUNICATION_OPTIONS This table stores communication information for contacts and business units. Columns Name OWNERID COMMUNICATIONID COMMUNICATIONTYPE ADDRESSTYPE PRIMARYCOMMUNICATION CONTACTSTRING NOTES ACTIVE DATEADDED ADDEDBY DATEUPDATED UPDATEDBY DATEDELETED DELETEDBY DATEFROM DATETO Datatype VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 DATE VARCHAR2 DATE VARCHAR2 DATE VARCHAR2 DATE DATE Size 12 1 10 10 5 255 50 5 7 50 7 50 7 50 7 7 Scale Nulls? No No No Yes Yes Yes Yes Yes No Yes Yes Yes Yes Yes Yes Yes Dflt Figure A-29.

PA_CMMUNICATION_OPTIONS Constraint Column Details .A-26 Insurance Industry Framework Implementation Guide Constraints Constraint Name Type Disable Referenced Schema Referenced Table Cascade On Delete Check Condition Deferrable? No Validate? Initially Deferred? RELY (Do Not Enforce)? No No No No No SYS_C0013129 PRIMARY No Figure A-30. PA_COMMUNICATION_OPTIONS Table Constraints Constraint Column Details Column BUSINESSUNITID COMMUNICATIONID COMMUNICATIONTYPE DATEADDED Constraint SYS_C0013129 Referenced Column Figure A-31.

Database Tables A-27 Foreign Key Relationships Column OWNERID COMMUNICATIONTYPE Referencing Table PA_CONTACT PA_COMMUNICATION_TYPES Referencing Column CONTACTID TYPE Figure A-32. PA_COMMUNICATION_OPTIONS Foreign Key Relationships .

A-28 Insurance Industry Framework Implementation Guide PA_COMMUNICATION_TYPES This table stores the valid communication types (for example. Replace the sample entries in this table with communication types valid for your configuration. HOME-EMAIL or HOME-PHONE) used within the system. Columns Name TYPE DESCRIPTION CATEGORY CLASS Datatype VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 Size 10 25 1 10 Scale Nulls? No Yes Yes Yes Figure A-33. PA_COMMUNICATION_TYPES Table Columns .

PA_COMMUNICATION_TYPES Constraint Column Details . PA_COMMUNICATION_TYPES Table Constraints Constraint Column Details Column TYPE Constraint SYS_C0013130 Referenced Column Figure A-35.Database Tables A-29 Constraints Constraint Name Type Disable Referenced Schema Referenced Table Cascade On Delete Check Condition Deferrable? No Validate? Initially Deferred? RELY (Do Not Enforce)? No No No No No SYS_C0013130 PRIMARY No Figure A-34.

A-30 Insurance Industry Framework Implementation Guide Foreign Key Relationships Column TYPE Referencing Table PA_COMMUNIATION_OPTIONS Referencing Column COMMUNICATIONTYPE Figure A-36. PA_COMMUNICATION_OPTIONS Foreign Key Relationships .

Database Tables A-31 PA_CONTACT This table is a sample table that stores information about contacts. Replace calls to this table with calls to your data tables. Columns Name CONTACTID CUSTOMERTYPE SOCIALSECURITYNUMBER LASTNAME FIRSTNAME MIDDLENAME SALUTATION SUFFIX SHORTNAME DATEOFBIRTH DATEOFDEATH MARITALSTATUS LANGUAGE PIN MOTHERMAIDENNAME TERRITORYID PRIORITYTYPE ACTIVE WEBPRIVILEGES LOGINS Datatype VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 DATE DATE VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 NUMBER Size 12 15 9 50 36 36 12 5 20 7 7 10 18 30 50 12 36 5 1 10 0 Scale Nulls? No Yes Yes No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No 0 Dflt .

PA_CONTACT Table Columns .A-32 Insurance Industry Framework Implementation Guide Name BADLOGINS DATEOFLASTLOGIN NICKNAME BUSINESSAFFILIATION DATEADDED ADDEDBY DATEUPDATED UPDATEDBY DATEDELETED DELETEDBY GENDER SECURITYQUESTION SECURITYANSWER COMMUNICATIONPREFERENCE PRIORITYNOTE CUSTOMERVALUE BESTTIMETOCALL NOMARKETINGBYMAIL NOMARKETINGBYPHONE NOMARKETINGBYEMAIL COMPANY OCCUPATION Datatype NUMBER DATE VARCHAR2 VARCHAR2 DATE VARCHAR2 DATE VARCHAR2 DATE VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 Size 10 7 26 12 7 50 7 50 7 50 1 100 50 10 255 30 20 5 5 5 50 50 Scale 0 Nulls? No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Dflt 0 Figure A-37.

Database Tables A-33 Constraints Constraint Name Type Disable Referenced Schema Referenced Table Cascade On Delete Check Condition Deferrable? No Validate? Initially Deferred? RELY (Do Not Enforce)? No No No No No SYS_C0013131 PRIMARY No Figure A-38. PA_CONTACT Constraint Column Details .PA_CONTACT Table Constraints Constraint Column Details Table Columns CONTACTID Constraint SYS_C0013131 Referenced Columns Figure A-39.

PA_CONTACT Foreign Key Relationships Referencing Tables and Columns Column CONTACTID CONTACTID CONTACTID CONTACTID Referencing Table PA_ADDRESS PA_CONTACT_BUSINESSUNIT_LINK IIF_POLICY_LINK PA_COMMUNICATIONS_OPTIONS Referencing Column OWNERID CONTACTID PARTYID OWNERID Figure A-41. PA_CONTACT Referencing Tables and Columns .A-34 Insurance Industry Framework Implementation Guide Foreign Key Relationships Column CUSTOMERTYPE Referencing Table PA_CUSTOMER_TYPE Referencing Column CUSTOMERTYPE Figure A-40.

Columns Name CONTACTID BUSINESSUNITID TYPE PRIMARYASSOCIATION ROLETYPE NOTES ACTIVE DATEADDED ADDEDBY DATEUPDATED UPDATEDBY DATEDELETED DELETEDBY Datatype VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 DATE VARCHAR2 DATE VARCHAR2 DATE VARCHAR2 Size 12 20 50 1 5 255 5 7 50 7 50 7 50 Scale Nulls? No No No Yes Yes Yes Yes No Yes Yes Yes Yes Yes Dflt Figure A-42.Database Tables A-35 PA_CONTACT_BUSINESSUNIT_LINK This table stores contact-to-business relationships. For example. PA_CONTACT_BUSINESSUNIT_LINK Database Columns . Jeff Buten is associated with Buten Bearings as an authorized party.

PA_CONTAC_BUSINESSUNIT_LINK Table Constraints Constraint Column Details Table Columns CONTACTID BUSINESSUNITID TYPE DATEADDED Constraint SYS_C0013134 Referenced Columns Figure A-44.A-36 Insurance Industry Framework Implementation Guide Constraints Constraint Name Type Disable Referenced Schema Referenced Table Cascade On Delete Check Condition Deferrable? No Validate? Initially Deferred? RELY (Do Not Enforce)? No No No No No SYS_C0013134 PRIMARY No Figure A-43. PA_CONTACT_BUSINESSUNIT_LINK Constraint Column Details .

Database Tables

A-37

Foreign Key Relationships
Column CONTACTID BUSINESSUNITID Referencing Table PA_CONTACT PA_BUSINESS_UNIT Referencing Column CONTACTID BUSINESSUNITID

Figure A-45. PA_CONTACT_BUSINESSUNIT_LINK Foreign Key Relationships

A-38

Insurance Industry Framework Implementation Guide

PA_CUSTOMER_TYPE
This table stores the information used to describe the business unit as a particular type of customer. Examples of customer type values are Fortune 500, Small Business, and Partnership.

Columns
Name CUSTOMERTYPE CUSTOMERTYPEDESCRIPTION DATEADDED ADDEDBY DATEUPDATED UPDATEDBY DATEDELETED DELETEDBY ACTIVE Datatype VARCHAR2 VARCHAR2 DATE VARCHAR2 DATE VARCHAR2 DATE VARCHAR2 VARCHAR2 Size 15 100 7 50 7 50 7 50 5 Scale Nulls? No Yes Yes Yes Yes Yes Yes Yes Yes Dflt

Figure A-46. PA_CUSTOMER_TYPE Table Columns

Database Tables

A-39

Constraints
Constraint Name Type Disable Referenced Schema Referenced Table Cascade On Delete Check Condition Deferrable? No Validate? Initially Deferred? RELY (Do Not Enforce)? No No No No No SYS C0013132 PRIMARY No

Figure A-47. PA_CUSTOMER_TYPE Table Constraints

Constraint Column Details
Table Columns CUSTOMERTYPE MODNUMBER TRANSACTIONEFFECTIVEDATE TRANSACTIONPROCESSDATE Constraint SYS_C0013132 Referenced Columns

Figure A-48. PA_CUSTOMER_TYPE Constraint Column Details

A-40

Insurance Industry Framework Implementation Guide

Referencing Tables and Columns
Column CUSTOMERTYPE CUSTOMERTYPE Referencing Table PA_CONTACT PA_BUSINESSUNIT Referencing Column CUSTOMERTYPE CUSTOMERTYPE

Figure A-49. PA_CUSTOMER_TYPE Referencing Tables and Columns

Examples of industry values are Healthcare. Columns Name INDUSTRYCODE INDUSTRYDESCRIPTION ACTIVE DATEADDED ADDEDBY DATEUPDATED UPDATEDBY DATEDELETED DELETEDBY Datatype VARCHAR2 VARCHAR2 VARCHAR2 DATE VARCHAR2 DATE VARCHAR2 DATE VARCHAR2 Size 15 36 5 7 50 7 50 7 50 Scale Nulls? No Yes Yes Yes Yes Yes Yes Yes Yes Dflt Figure A-50. Insurance. PA_INDUSTRY Table Columns . and Technology.Database Tables A-41 PA_INDUSTRY This table stores information that describes the industry in which a business operates.

PA_INDUSTRY Table Constraints Constraint Column Details Table Columns INDUSTRYCODE Constraint SYS_C0013133 Referenced Columns Figure A-52. PA_INDUSTRY Referencing Tables and Columns . PA_INDUSTRY Constraint Column Details Referencing Tables and Columns Column INDUSTRYCODE Referencing Table PA_BUSINESSUNIT Referencing Column INDUSTRYCODE Figure A-53.A-42 Insurance Industry Framework Implementation Guide Constraints Constraint Name Type Disable Referenced Schema Referenced Table Cascade On Delete Check Condition Deferrable? No Validate? Initially Deferred? RELY (Do Not Enforce)? No No No No No SYS C0013133 PRIMARY No Figure A-51.

Database Tables

A-43

PA_NOTES
This table stores ad-hoc notes that are added to contact or policy records. It is provided with the PegaApp layer, but currently is not used by the Insurance Framework.

Columns
Name NOTEID NOTEDATE ACCOUNTNUMBER BUSINESSUNITID CONTACTID LABEL NOTES TAKENBYID OPPORTUNITYID TYPE Datatype NUMBER DATE VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 Size 10 7 20 12 12 50 1000 32 12 10 Scale 0 Nulls? No No Yes Yes Yes Yes Yes Yes Yes Yes Dflt

Figure A-54. PA_NOTES Table Columns

A-44

Insurance Industry Framework Implementation Guide

Constraints
Constraint Name Type Disable Referenced Schema Referenced Table Cascade On Delete Check Condition Deferrable? No Validate? Initially Deferred? RELY (Do Not Enforce)? No No No No No SYS C0013135 PRIMARY No

Figure A-55. PA_NOTES Table Constraints

Constraint Column Details
Table Columns NOTEID Constraint SYS_C0013135 Referenced Columns

Figure A-56. PA_NOTES Constraint Column Details

Database Tables

A-45

PA_PRODUCT
This table stores product information. It is provided in the PegaApp layer and is not currently used in the Insurance Framework.

Columns
Name ACTIVE PRODUCTCOST PRODUCTDESCRIPTION PRODUCTID PRODUCTLISTPRICE PRODUCTNAME PRODUCTTYPE PXCREATEDATETIME PXCREATEOPNAME PXCREATEOPERATOR PXCREATESYSTEMID PXINSNAME PXOBJCLASS PXUPDATEDATETIME PXUPDATEOPNAME PXUPDATEOPERATOR PXUPDATESYSTEMID PYLABEL Datatype VARCHAR2 NUMBER VARCHAR2 VARCHAR2 NUMBER VARCHAR2 VARCHAR2 DATE VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 DATE VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 Size 5 19 100 32 19 64 15 7 128 128 32 128 96 7 128 128 32 64 2 2 Scale Nulls? Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Dflt

A-46

Insurance Industry Framework Implementation Guide

Name PZINSKEY PZPVSTREAM

Datatype VARCHAR2 BLOB

Size 255

Scale

Nulls? No Yes

Dflt

Figure A-57. PA_PRODUCT Table Columns

Constraints
Constraint Name Type Disable Referenced Schema Referenced Table Cascade On Delete Check Condition Deferrable? No Validate? Initially Deferred? RELY (Do Not Enforce)? No No No No No PR_PRODUCT_PK PRIMARY No

Figure A-58. PA_PRODUCT Table Constraints

Constraint Column Details
Table Columns PZINSKEY Constraint PA_PRODUCT_PK Referenced Columns

Figure A-59. PA_PRODUCT Constraint Column Details

Columns Name ACCOUNTCLASS ACTIVE OPPORTUNITYCLASS PRODUCTTYPE PRODUCTTYPEDESCRIPTION SPECIALPRODUCTID PXCREATEDATETIME PXCREATEOPNAME PXCREATEOPERATOR PXCREATESYSTEMID PXINSNAME PXOBJCLASS PXUPDATEDATETIME PXUPDATEOPNAME Datatype VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 DATE VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 DATE VARCHAR2 Size 64 5 64 15 50 12 7 128 128 32 128 96 7 128 Scale Nulls? Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Dflt .Database Tables A-47 PA_PRODUCT_TYPE This table stores information about the product type. It is provided in the PegaApp layer and is currently not used by the Insurance Framework.

A-48 Insurance Industry Framework Implementation Guide Name PXUPDATEOPERATOR PXUPDATESYSTEMID PYLABEL PZINSKEY PZPVSTREAM Datatype VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 BLOB Size 128 32 64 255 Scale Nulls? Yes Yes Yes No Yes Dflt Figure A-60. PA_PRODUCT_TYPE Table Constraints . PA_PRODUCT_TYPE Table Columns Constraints Constraint Name Type Disable Referenced Schema Referenced Table Cascade On Delete Check Condition Deferrable? No Validate? Initially Deferred? RELY (Do Not Enforce)? No No No No No PA_PRODUCT_TYPE_PK PRIMARY No Figure A-61.

Database Tables A-49 Constraint Column Details Table Columns PZINSKEY Constraint PA_PRODUCT_TYPE_PK Referenced Columns Figure A-62. PA_PRODUCT_TYPE Constraint Column Details .

Columns Name ROLETYPE PARTYTYPE APPLICATION ROLEDESCRIPTION DATEADDED ADDEDBY DATEUPDATED UPDATEDBY DATEDELETED DELETEDBY Datatype VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 DATE VARCHAR2 DATE VARCHAR2 DATE VARCHAR2 Size 5 1 10 36 7 50 7 50 7 50 Scale Nulls? No Yes Yes Yes Yes Yes Yes Yes Yes Yes Dflt Figure A-63. contact. contact. PA_ROLES Table Columns . and business unit associations.A-50 Insurance Industry Framework Implementation Guide PA_ROLES This table stores roles for policy. Add your own affiliations for account. Some workflows use the role type to determine processing steps. and business unit links.

PA_ROLES Constraint Column Details Referencing Tables and Columns Column ROLETYPE Referencing Table IIF_POLICY_LINK Referencing Column ROLETYPE Figure A-66.Database Tables A-51 Constraints Constraint Name Type Disable Referenced Schema Referenced Table Cascade On Delete Check Condition Deferrable? No Validate? Initially Deferred? RELY (Do Not Enforce)? No No No No No SYS_C0013126 PRIMARY No Figure A-64. PA_ROLES Table Constraints Constraint Column Details Table Columns ROLETYPE Constraint SYS_C0013126 Referenced Columns Figure A-65. PA_ROLES Referencing Tables and Columns .

Master your semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master your semester with Scribd & The New York Times

Cancel anytime.