Insure SIA

Siebel Insurance Guide
Version 8.1, Rev A June 2012
Copyright 2005, 2012 Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be errorfree. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are commercial computer software pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
Contents
Siebel Insurance Guide 1
Chapter 1: Chapter 2:
Whats New in This Release Overview of Siebel Finance

15 15
About Siebel Insurance
Siebel Insurance Functionality and Modules
Chapter 3:
Getting Started with Siebel Finance

19 20
About Applications Administration Tasks Renaming Siebel Account Objects Configuring Lists of Values Configuring Summary Views About Command Center 22 20 20 21
Adding Products and Product Lines
Command Center Configuration and Administration
22 22
Process of Configuring the Command Center Action Form
Defining the Command Center Business Object 23 Defining the Command Center Actions 25 Selecting the Command Center Responsibilities 27 Example of Configuring the Command Center Action Applet 27 Creating Global Commands for the Command Line Applet 29
Chapter 4:
Managing Companies
31 32 33 33
About Managing Companies About Company Hierarchies
Scenario for Managing Company Information Process of Managing Companies

Administrator Procedures 34 End-User Procedures 34
Setting Up Values for Companies Deleting Company Information
34 35
Siebel Insurance Guide Version 8.1, Rev A
Contents
Managing Competitor Information Verifying Coverage Team Members
36 36 38 39
Managing the Custom-Defined Relationship Types LOV Generating Company Hierarchies for Data Aggregation
Default Company Hierarchies 39 Dynamic Company Hierarchies 40
Adding Companies and Investors (End User) Creating Company Assessments (End User) Adding Company Applications (End User)
41 42 44
Viewing Company Hierarchies in Roll-Up Views (End User) 44 45 45 46
Adding Company Service Requests (End User) Managing Company Coverage Teams (End User) Viewing Company Summaries (End User) 46
Viewing Company Relationship Hierarchies (End User)
Chapter 5:
Managing Contacts
49 50 51 51
52
About Managing Contacts
Scenario for Adding a New Contact
Process of Managing Contacts (End User) Managing Contact Information (End User)
Adding Contacts 51 Creating Categories for Contact Information Creating Notes About Contacts 53 Managing Contact Referral Information 54
Creating Customer Assessments (End User) Setting the Customer Value Icon (End User) Viewing a Contact Summary (End User) 56
55 56 57
Viewing Contact Relationship Hierarchies (End User)
Chapter 6:
Managing Households
59 60 60
About Managing Households
Scenario for Managing Households Process of Managing Households Adding Households

4
60
Contents
Setting the Household Privacy Option Associating Contacts with Households Viewing Household Summaries 62
61 61 62
Using the Household Relationship Hierarchy
Chapter 7:
Managing Call Reports

65 66 67
About Managing Call Reports
Scenario for Managing Call Reports Process of Managing Call Reports

Viewing Call Report Charts
67 68 69 69 71 71 72 72
Activating the New Call Report Workflow Managing Call Report Templates Adding Call Reports (End User)
Creating Call Report Distribution Lists (End User) Setting the Call Report Privacy Flag (End User) Emailing and Printing Call Reports (End User)
Associating Action Items, Notes, and Attachments with Call Reports (End User)
Chapter 8:
Managing Group Pensions

75 75
About Managing Group Pensions Group Pension Sample Tasks

Scenario for Creating a Company 401(k) Plan 76 76 Process of Managing Group Pension Plans
Defining Group Pension Products Defining Group Pension Plans 78
77 80
Administering Group Pension Plans (End User)
Chapter 9:
Managing Auto Policies

85 85
5
About Managing Auto Policies
Scenario for Managing Auto Policies
Contents
Process of Managing Auto Policies

86
Adding Auto Coverages and Coverage Values Providing Quotes Adding Discounts 87 88 89 89 89 90
87
Adding Vehicles or Drivers to Policies Setting Up Payment Plans Adding Underwriting Information Ordering Underwriting Reports
Chapter 10: Managing Claims

About Managing Claims 92
93 Insurance Claims Terminology
Scenario for Opening and Managing a Claim for Property Loss Scenario for Opening and Managing a Claim for Auto Damage Process of Managing Claims 95
Administrator Procedures for Managing Claims 96 End-User Procedures for Managing Claims 96
94 94
About Siebel Insurance eService Claims Center Locators Activating the Workflow Processes Administering Reserve Codes Administering Loss Codes 99 101 102
102
97 97
Setting up Siebel Insurance eService Claims Center Locators 99
100
Administering Adjusters Financial Limits Administering the Employee Hierarchy
Example of Setting up the Employee Hierarchy
Integrating with the Insurance Services Office (ISO)
103
Setting the ISO System Preferences 103 Checking the ISO Run-Time Event 104 Checking the Validation Rules 104 Creating the Named Subsystem for the ISO Search Response Configuring the ISO Assigned Company ID 105
104
Integrating with the Office of Foreign Assets Control Checking the Policy Validity and Coverage (End User)
6 Siebel Insurance Guide Version 8.1, Rev A
105 106
Contents
Creating First Notices of Loss (End User)
106 107 108
Recording Details of Involved Parties (End User) Managing Claims Events (End User) 109 110
Recording Insured and Adverse Claimant Property Details (End User) Assigning a Claim to an Adjuster (End User) Creating an Activity Plan (End User) Assigning a Claim Element (End User) Adding an Appraisal (End User) 115 116 116 113 113 114
Checking a Claim Against the ISO Database (End User)
110
Assigning Claims to a Specialist Unit (End User) Attaching Claims Documentation (End User) Tracking Police and Fire Reports (End User) About Coverages and Reserves Creating a Reserve (End User) About Managing Reserves 119 122 124 125 124 Managing Reserves (End User) 117 117
Tracking Demands for Payment (End User) Creating an Invoice Record (End User) Generating a Payment Record (End User)
Tracking Payments Related to Invoices (End User) About Issuing a Settlement Payment (End User) Issuing a Settlement Payment (End User) Making a Bulk Payment (End User) 131 131
125 126
Viewing the Invoices and Claims for a Payment (End User) Managing Recovery Information (End User)
Using the Common Task Links 136
132
132 138
Creating a Recovery Payment Record (End User) Managing Fraud Information (End User)
Using the Common Task Links 141
138 142
About the Business Rules Processor and Claims Logic Claims Workflows 145
Contents
Chapter 11: Managing Life and Annuity Policies

About Managing Life and Annuity Policies Scenario for Life and Annuity Policies
149 151
150
Process of Managing Life and Annuity Policies
Defining Life or Annuity Insurance Products Defining Life or Annuity Insurance Coverages Administering Assessment Templates Providing Life and Annuities Quotes Ordering Underwriting Reports Adding a Beneficiary 154 155 156 Submitting Transaction Requests Viewing Value History Information Setting Up Payment Plans 156 154 152 153
152 152
Chapter 12: Managing Group Policies

About Group Policies 159 161 161 Scenario for Group Policies
Process of Managing Group Policies

Adding Group Insurance Products and Product Lines Adding Group Insurance Rate Bands 163 Defining Activity Plan Templates for Group Policies Defining Proposal Templates for Group Policies Adding Group Policy Records Importing Census Information 164 165 164
162 163
Adding Census Information in the Group Policies Screen Adding Employee Classes for Group Policies Designing Plans for Group Policies 168 168
166
How Enrollment Waiting Periods Affect the Start of Coverage Reconfiguring Customizable Products in Plan Design
8 Siebel Insurance Guide Version 8.1, Rev A
169
170
Contents
Generating Proposals for Group Policies Managing Underwriting Information Enrolling Members in Group Policies Adding Beneficiaries to Group Policies 171 Adding Eligible Members to Group Policies
171 172
173 174 174
Setting Up Payment Plans for Group Policies
Chapter 13: Managing Partners and Agencies

About Partners and Agencies 175 176 176 177 Scenario for Working with Partners and Agencies (Users) Process of Managing Partners and Agencies (Users) Adding New Partners Adding Agents 178 178 177
Setting Up Siebel Insurance eService Partners Locators Adding Information Associated with an Agent
Chapter 14: Managing Property Policies

About Property Policies 179 179 180 Scenario for Property Policies
Process of Managing Property Policies

Adding Property Types Providing Quotes 182
181 181
Adding Property Coverages and Coverage Limits Adding Underwriting Information Ordering Underwriting Reports Setting Up Payment Plans 184 184 182
Querying for Property Underwriting Information 183 183 Adding Scheduled Personal Property Additional Property Policies Views
183
Contents
Chapter 15: Managing PUL Policies

About PUL Policies 187 187 188 Scenario for PUL Policies
Providing PUL Policy Quotes
Chapter 16: Managing Billing Accounts

About Billing Accounts 189 189 190 Scenario for Billing Accounts
End-User Procedures 190
Process of Managing Billing Accounts Creating Billing Account Records 190
Associating Billing Accounts with Other Records
191
Chapter 17: Siebel Integration Messages

About the Siebel Financial Services Business Platform Siebel Insurance Integration Messages 194 193
Chapter 18: Business Services for Siebel Financial Services

About Siebel Business Services Disclosure Manager 202 203 200 200 About Siebel Financial Services Business Services VBC Cache and Instance Manager
Caching VBC Overview 203 Components 204 Stages of the Caching VBC Process Caching VBC Configuration 205 Purging the VBC Cache 206
204
Free Format Converter Data Validation Manager Business Rule Processor
208 209 210 211 212 215
Process of Defining Business Rule Processes
Creating and Managing Business Rule Processes Defining Properties for a Business Rule Process
About Business Rule Process Property Types 215
10
Contents
Defining Procedures for a Business Rule Process Fine-Tuning the Assignment Statement Handling Business Rules Processor Errors 227 229
219
Throwing Errors Within a Business Rules Process 230 Recovering from Errors Within a Business Rules Process
230
Using BRP Helper Business Services
231
FINS CAP Buscomp Data Loader Business Service 231 FINS CAP Buscomp Handler Business Service 236
Invoking the Business Rule Processor
242
243
Using eScript to Invoke the Business Rule Processor
Logging Business Rules Processor Debug Messages Requirements Manager 244
244
About Requirements Manager 245 Administering Requirements Manager 246 Creating Record Templates 246 Creating Requirement Templates 247 Using Requirements Manager 250 Creating Record Group Templates 250 Example of Using Requirements Manager for Record Group Templates
252
Customer Authentication Manager
254
Creating Customer Authentication Templates 254 Defining Customer Authentication Rules 256 Invoking Customer Authentication Manager 258
Using the Calculation Manager
259
262
Specifying Calculation Rules 259 Example of Using Embedded eScript for Mortgage Calculation Invoking Siebel Calculation Manager 265
Using the Customer Expectations Manager
265
Defining Customer Expectation Manager Rules 266 Invoking Customer Expectations Manager 268
Automating Approval Processing
269
Defining Approval Items and Approval Stages 269 Invoking FINS Approval UI Service from a Workflow 270 Approving or Declining Approval Stages (End User) 272
Automating the Display of Disclosure Documents

Setting Up Disclosures 273 About Disclosure Workflows 274 Activating Workflows 275
273
11
Contents
Invoking the Disclosure UI Service Business Service 276 Viewing Disclosures Associated with Contacts (End User) 276
SmartScript Integration with Workflow
276
277
Example of Integrating SmartScript with Workflow FINS Web Shopping Service Methods 279 FINS SmartScript Output Service Methods 279
Dynamic UI Business Service
279
280
Example of Creating a Dynamic Applet with the Dynamic UI Business Service Displaying Dynamic Applets in a Workflow 281 Creating a View Template for Dynamic Applets 282
FINS Application View Navigation
283
Business Service Methods 283 Business Service Behaviors 284 Business Service Administration 285 Example of FINS Application View Navigation Upgrade Note 286
285
Index
12
Whats New in This Release
Whats New in Siebel Insurance Guide, Version 8.1, Rev A

No new features have been added to this guide for this release. This guide has been updated to reflect only product name changes.
13
Whats New in This Release
14
Overview of Siebel Insurance
This chapter describes the modules of Siebel Insurance and their functionality. It includes the following topics: About Siebel Insurance on page 15 Siebel Insurance Functionality and Modules on page 15
About Siebel Insurance

Oracles Siebel Insurance includes various modules that you can mix and match according to your business needs. Siebel Insurance is built upon the Siebel Business Architecture, which includes Siebel Sales, Siebel Service, and Siebel Call Center applications. Like many other Siebel Business Applications, Siebel Insurance uses the Siebel Data Model, the Siebel Object Architecture, and the Siebel Application Server Architecture. NOTE: Siebel collection management functionality is available for use with Siebel Finance. For more information, see the collection management content in Siebel Automotive Guide.
Siebel Insurance Functionality and Modules

Siebel Insurance is an information management application designed to meet the needs of the insurance industry as they relate to sales, marketing, and customer service. Siebel Insurance provides the following functionality: Access to contact data for individuals, their households, their activities, their policies, and associated underwriting information Managing auto policies (including European auto policies), property insurance policies, PUL (personal umbrella liability) policies, life insurance policies and annuities, and group insurance policies, from quoting through issuance and maintenance Managing the claims process, including reporting and handling processes throughout the life cycle of a claim for both call center and mobile users Audit trail capabilities Managing agent and broker requirements, including licensing, continuing education and product training hours, and NASD registrations
15
Overview of Siebel Insurance Siebel Insurance Functionality and Modules
Total management of customer requests for action or information through the Service Request features Monitoring customer satisfaction using online surveys Access to solutions in a text-based retrieval system
NOTE: Some functionality requires the installation of optional product modules such as Siebel Briefings, Siebel SmartScript, and Siebel Configurator. Siebel Insurance includes the following modules: Call Reports. Siebel Call Reports are records of meetings and conversations with clients or other organizations and individuals. Financial institutions often require employees to generate call reports when they meet with customers. Service Requests. Siebel Service Requests is targeted at call center, field and branch service personnel, their managers, and their associates, and focuses on support for retail banking customers. Siebel Insurance allows agents to perform key service transactions, such as name or address changes, fulfilling requests for statement or check copies, performing fee reversals and funds transfers, initiating stop payments on checks, and tracking these requests to completion. Retirement/Pension Management. Siebel Retirement/Pension Management provides support for group pensions. It allows a user to manage private group pensions, including defined contribution plans, such as 401(k) plans and occupational pensions, and defined benefit plans. It is designed to meet the needs of sales and service professionals, managers, and pension administrators. The module allows users to define group pension plans, plan classes, plan eligibility rules, and plan funding vehicles. Siebel Retirement/Pension Management also provides eligible and enrolled participants tracking, participant contribution and investment allocation management, as well as a participant beneficiary management. Siebel Retirement/Pension Management includes the Securities module that provides for the set up and profiling of funding vehicles, such as mutual funds for pension plans. The plan administrators are provided with a picture of each mutual fund available for investment under the terms of the plan including literature about the fund, fund objectives, risk profile, and asset mix.
16
Rollup. Siebel Rollup provides a view of a client relationship in a single click, thereby eliminating the process to collect this information. Siebel Rollup offers four views of the relationship with a client - Activities, Opportunities, Coverage Team, and Contacts, that show the records for the selected client and for any hierarchical children. For example, the Contacts Rollup view displays contacts associated with the selected company, subsidiaries of the selected company and the regional offices. Executives, sales managers, or sales professionals are often looking for aggregate information across a corporate enterprise and the individuals who work there. For example, before the Global Relationship Manager visits the CEO at his client company, he might want to view a report of all the latest activities, and deals conducted with the client company or with any of the subsidiaries, divisions and offices of the client company. This information arms the Global Relationship Manager with a picture of the relationship between the client and his company, a tool for preparing for his important meeting.
NOTE: Optional modules from Siebel Business Applications can be used to provide enhanced functionality to support various business processes. For information about the optional modules, contact your Siebel sales representative.
List of Reports
To see a list of the preconfigured reports available for the data in a view, click Reports in the toolbar while in the view. The list specifies which reports are available as Oracle Business Intelligence Publisher reports. From the list you can access individual reports.
17
18
Getting Started with Siebel Insurance
This chapter lists the applications administration tasks specific to Siebel Insurance. Use this chapter in combination with Siebel Applications Administration Guide. This chapter includes the following topics: About Applications Administration Tasks on page 19 Renaming Siebel Account Objects on page 20 Configuring Lists of Values on page 20 Configuring Summary Views on page 20 Adding Products and Product Lines on page 21 About Command Center on page 22 Command Center Configuration and Administration on page 22 Process of Configuring the Command Center Action Form on page 22
About Applications Administration Tasks

Siebel Applications Administration Guide covers the setup tasks that are common to all Siebel Business Applications, such as using license keys, defining employees, and defining your companys structure. It also provides the information you must implement, configure, and monitor the Siebel sales, service, and marketing products and to perform data administration and document administration tasks. This guide assumes that you have already installed or completed the upgrade of Siebel Insurance. The Siebel database server installation creates a Siebel administrator account that can be used to perform the tasks described in this guide. For more information about this process, see the Siebel Installation Guide for the operating system you are using. CAUTION: Do not perform system administration functions on your local database using the Mobile Web Client. Although there is nothing to prevent you from doing this, it can have serious results, such as data conflicts, an overly large local database, or a large number of additional transactions to route.
19
Getting Started with Siebel Insurance Renaming Siebel Account Objects
Renaming Siebel Account Objects

In general, Siebel applications refer to companies as accounts. In the Financial Services industry, the term account has typically been synonymous with financial accounts, so historically the word company has been used in many places in Siebel Insurance. By default, Siebel Insurance installs using the term accounts. Users can change this term and use another description, such as Companies, Clients, or Customers. Users wishing to change this default must rename all Siebel Account objects prior to deployment. Make changes to the UI layer (for example, applet titles and control labels), rather than the Business Objects layer. For more information, see Siebel Database Upgrade Guide. NOTE: All of the chapters in this guide are written assuming you have renamed Siebel Account objects to Companies.
Configuring Lists of Values

In Siebel Insurance, modify the List of Values (LOV) in accordance with the terminology used by your financial institution. For example, the list of transaction types used in Siebel Insurance must match those used by your financial institution. For more information on configuring a LOV, see Siebel Applications Administration Guide. NOTE: This might impact certain forms and lists, which rely on the preconfigured values for correct operation.
Configuring Summary Views

In Siebel Insurance, summary views have been restructured. In the past, multiple summary views existed, typically one summary view for a particular type of user. For example, there were preconfigured summary views specifically for salespeople and customer service agents. This has been replaced by common summary views whose appearance can be configured by individual end users. Users can change the way a list appears in a summary view by using the controls in the top right corner of each list. The summary view controls, described in Table 1, allow users to manage what appears on the summary view.
Table 1. Button Hide Collapse Expand
Summary View Controls Description Temporarily hides a list or form from view. Collapses the list of records. If the list cannot be collapsed, the expand button appears instead of the collapse button. Expands the list of records. If the list cannot be expanded, the collapse button appears instead of the expand button.
20
Getting Started with Siebel Insurance Adding Products and Product Lines
Any changes made to a summary view layout are only visible to the current user and remain in effect until that user changes them again or reverts to the default layout. If users hide a list, they must click Edit Layout to restore it. For more information, see Editing a Summary View Layout.
Editing a Summary View Layout

Using the Edit Layout view, users can restore hidden lists, collapse or expand all lists, move lists or forms up or down on the page, or revert to the default layout. The edit layout buttons, described in Table 2, allow users to change the way a summary view appears and apply those changes to future sessions.
Table 2. Button Collapse Expand Move up
Edit Layout Buttons Description Collapses the list or form. Expands the list or form. Moves the list or form up on the home page. Moves the list or form down on the home page. Displays the list or form on the home page. Hides the list or form from view on the home page.
Move down Show Hide
For more information on available summary views, see Viewing a Contact Summary (End User) on page 56, Viewing Company Summaries (End User) on page 46, and Viewing Household Summaries on page 62.
Adding Products and Product Lines

Administrators must set up products, such as insurance products, in Siebel Insurance. After setting up a product, administrators can specify that it be included in a product line. They can also specify which product lines your company contracts agencies to sell or which ones the state licenses agencies to sell. Setting up products is discussed in detail in Siebel Product Administration Guide. However, this guide also explains some steps for adding products in the appropriate chapters. In those chapters, values for specific fields are given to help administrators set up products correctly. NOTE: Only those users with the required administrative responsibilities, such as Siebel administrators, can add products and information about product lines.
21
Getting Started with Siebel Insurance About Command Center
About Command Center

The command center allows you to launch a process, perform a task, or jump to a view. Command center actions are preconfigured by your system administrator in accordance with your companys business process requirements. For example, if the financial services agents at your company often have to jump to the financial accounts view for a contact, you could configure the command center to perform this action, saving them time and keystrokes. See Command Center Configuration and Administration on page 22 for information on how to configure the command center. Out of the box, the command center is only available from the Summary views on the Contacts and Companies screens.
Command Center Interface Types

There are two interface types for the command center: Action form Command line
Figure 1 shows the action form, a menu-driven interface guiding the end user through preconfigured choices in order to launch an action. The command line requires the end user to enter specific command line syntax to launch the action.
Figure 1.
Command Center Action Form
Command Center Configuration and Administration

Command Center configuration and administration must only be done by expert users accustomed to working with business services.
Process of Configuring the Command Center Action Form

To configure the appearance and function of the Command Center Action form you must:
22
Getting Started with Siebel Insurance Process of Configuring the Command Center Action Form
1 2
Define the business object where the Command Center Action form appears and what business component and fields are to be used. See Defining the Command Center Business Object. Define actions available for the business object, indicating for each combination of possible attribute values what action is taken (launch a business service or workflow, go to a view, and so on). See Defining the Command Center Actions. For actions defined as private, select the defined roles for which the actions will be available. See Selecting the Command Center Responsibilities.
An example configuration is included at Example of Configuring the Command Center Action Applet on page 27.
Defining the Command Center Business Object

The first step in configuring the Command Center Action form is to define the business object where the Command Center form appears, and what business component and fields are to be used. Out of the box, the Command Center forms appear on the Contact Summary and Company Summary views. This task is part of Process of Configuring the Command Center Action Form.
To define the business object 1 2

Navigate to Site Map, Administration - Command Center screen, and then the Defined Objects view. Create a new object definition record and complete the fields as follows: Parameters Any Business Object for which the forms have been defined. For example, Contact or Companies. The business component against which the Driving Field will be compared. For example, FINCORP Account. This must be a business component available on the view where the Command Center applets are visible (for example, Contact Summary view). Description This identifies the screen where the Command Center form is to appear.
Field Business Object
Source Business Component
The value of this field is constrained by the value of Business Object field. In turn, it is a constraint for the Driven Field.
23
Field Source Business Search Specification
Parameters A filter on the source business component. For example, Acct. Status = Open. Only Financial accounts with a status of Open will be available in the Command Center. A field name from the Source Business Component. The field name can be ascertained using Siebel Tools. Following the examples in the preceding field parameter descriptions, this could be the Financial Account name or ID.
Description Use this field to enter an optional filter criteria on the selected Business Component.
Driving Field
The value of this field is constrained by Source Business Component and Source Business Search Specification (if entered). The driving field is equivalent to Attribute 1.
Driving Field Label
Free text field, 20 character limit.
The text label exposed in the UI for Driving Field (Attribute 1). If blank, the label defaults to the Driving Field on the Command Center form. The text label for each of Attributes 2-4. If left blank, the attribute does not appear on the form.
Attribute 2,3,4 Label
Free text fields, 20 character limit.
24
Field Driving Field on Cmd Form Expression
Parameters Check box.
Description If checked, it exposes the Driving Field label on the Command Center form preceding the Command field. Use this field to constrain the available set of actions based on what the user has selected in the Driving Field. As each object definition can have multiple action definitions, the expression field is a way to limit the available actions based on a business component field. For example, if the user selects a checking account, investment based actions might not be appropriate. For example: IIF([Account Number] LIKE '1800*', Liability, Asset). That is, if the account number starts with 1800, it maps to action definitions in the Action Definition list that have the Attribute 1 Map field set to Liability. Otherwise, it is mapped to action definitions that have the Attribute 1 Map field set to Asset. If there is no need to constrain the actions, then any value suffices (for example, Contact - All).
Free text field.
Defining the Command Center Actions

After you define the business object, you define actions for each object. These actions indicate for each object a combination of possible attribute values what action is taken (launch a business service or workflow). The relationship is one-to-many. This task is part of Process of Configuring the Command Center Action Form on page 22.
To define actions for the Command Center applet 1

Navigate to Administration - Command Center screen, the Defined Objects view, and then select the Object Definition for which you wish to define actions.
25
Scroll down to the Action Definition list, create actions, and complete the fields as described in the following table. Parameters Check box. Description Indicates whether or not an entry in the Driving Field (Attribute 1) is required for the Command Center to return results. Works in concert with the Expression field of the Object Definition to determine the contents of the Command Center dropdown menus. Value lists for Attributes 2-4. The command line equivalent for the action. These commands are restricted to the Business Object with which they are associated. See also Creating Global Commands for the Command Line Applet on page 29.
Field Attribute 1 Required Attribute 1 Map
Free text.
Attribute 2-4 Command
Free text. Free text. Each entry must be unique, that is, you cannot use the same command for different actions.
Command Help Text
Free text.
The Help text for the command help feature when a question mark (?) is entered using the command line. This field is reserved for future use. You can expose it in some manner, if you choose, using a custom configuration.
Business Service
Free text. EX: FINS Goto View Service
The name of the Business Service to be run. The parameters for the Business service. The method for the selected Business service. If checked (true), then any roles selected for the action do not apply. If unchecked (false), then any roles selected do apply and visibility to actions are limited by the selected roles.
Business Service Context Business Service Method Public Flag
Free text. Free text. Check box.
Inactive
Check box.
This hides the defined action and attribute combination.
26
Selecting the Command Center Responsibilities

For each action, select the defined responsibilities for which the action will be available. The relationship between actions and responsibilities is one-to-many. This task is part of Process of Configuring the Command Center Action Form on page 22.
To select responsibilities for a Command Center action 1 2

Navigate to Administration - Command Center screen, the Defined Objects view, and then select the Action for which you wish to define responsibilities. Scroll down to the Responsibility list, create a new record, and select the responsibility. The responsibilities information appears as read-only in the Responsibility list. Selected responsibilities are only enforced if the Public Flag for the action is unchecked (false).
Example of Configuring the Command Center Action Applet

This topic gives an example of configuring the Action applet. You might use this feature differently, depending on your business model. NOTE: This example uses a view available only in Siebel Healthcare. Although it is not visible to Siebel Insurance users, the example is still useful to all Siebel Financial Services users to illustrate how to set up the Command Center. The Command Center is available on the Siebel Healthcare Member Summary view and can be configured to launch several key sales processes such as ordering a new ID card or changing a primary care physician. For more information on using the Member Summary Command Center when configured as in this example, see Siebel Healthcare Guide. The Command Center is set up using the Administration - Command Center view.
To configure the action applet to run the business service FINS Goto View 1
Navigate to FINS Command Center Admin Object view and create a new object definition record. Complete the fields as follows: Field Business Object Name Source Business Component Driving Field Driving Field Label Attribute 2 Label Value FINS Members FINS Members Last Name Name Area
27
Field Attribute 3 label Expression Driving Field On Cmd Form
Value Action RedundantExpression Checked
To set up a pop-up applet, in the Action Definition list create a new action record and complete the fields as follows: Field Attribute 2 Attribute 3 Command Business Service Business Service Context Value ID Card Requests Show History IDCSH SLM Save List Service 'Applet Mode', '6', 'Applet Name', 'FINS Service Request Order ID Popup Applet' NOTE: The applet in this example is only available in Siebel Healthcare. Siebel Insurance customers would select a suitable view and applet available in their respective applications. Business Service Method Public Flag LoadPopupApplet Checked
To set up a view navigation, in the Action Definition list create a new action record and complete the fields as follows: Field Attribute 2 Attribute 3 Command Business Service Business Service Context Value ID Card Requests Order New ID Card IDCOR FINS Goto View Service 'ViewName', 'FINS Member Benefits View', 'RowId', '[Current Src Rec Id]', 'AppletName', 'FINS Member Form Applet - short' NOTE: The view and applet in this example are only available in Siebel Healthcare. Siebel Insurance customers would select a suitable view and applet available in their respective applications.
28
Field Business Service Method Public Flag
Value GotoView Checked
Creating Global Commands for the Command Line Applet

Some users might prefer to use only the Command form. In this case, the only configuration required is to indicate the command line syntax and the associated business service and responsibility information. Use these global commands through the Command line form on whatever business object it appears.
To create global commands for the Command Line applet 1 2 3

Navigate to the Administration - Command Center screen, and then the Global Commands view. In the Global Commands list, create a command record, and complete the fields as described in Defining the Command Center Actions on page 25. For each Command, record select responsibilities as described in Selecting the Command Center Responsibilities on page 27.
29
30
Managing Companies
This chapter describes managing companies and accounts information. It includes the following topics: About Managing Companies on page 31 About Company Hierarchies on page 32 Scenario for Managing Company Information on page 33 Process of Managing Companies on page 33 Setting Up Values for Companies on page 34 Deleting Company Information on page 35 Managing Competitor Information on page 36 Verifying Coverage Team Members on page 36 Managing the Custom-Defined Relationship Types LOV on page 38 Generating Company Hierarchies for Data Aggregation on page 39 Adding Companies and Investors (End User) on page 41 Viewing Company Hierarchies in Roll-Up Views (End User) on page 42 Creating Company Assessments (End User) on page 44 Adding Company Applications (End User) on page 44 Adding Company Service Requests (End User) on page 45 Managing Company Coverage Teams (End User) on page 45 Viewing Company Summaries (End User) on page 46 Viewing Company Relationship Hierarchies (End User) on page 46
About Managing Companies

Within Siebel Insurance, the term companies refers to entities that are typically referred to as accounts in other Siebel applications. A company represents the relationship between your organization and companies or organizational entities (or structures) with which you do business. Use the Companies screen and its associated views to view company information and interactions. CAUTION: This chapter assumes you have renamed Siebel Account objects to Companies. By default, Siebel Insurance installs using the term Accounts. For more information on renaming Siebel Account objects, see Siebel Database Upgrade Guide.
31
Managing Companies About Company Hierarchies
In Siebel Insurance, the term investors refers to financial organizations such as mutual fund or money management institutions; investors are not contacts, rather they are companies that are identified as investors. In Siebel Financial Services, the investors functionality has migrated to the Companies screen. This chapter covers both regular company and investor procedures. Use the procedures in this chapter to perform the administrator tasks of controlling company information, generating company hierarchies, managing competitor information, verifying coverage team members, and managing custom-defined relationship types. End users use the Companies views to add new companies and investors, create company assessments, associate service requests with a company, update the coverage team, define relationships to other companies, contacts, and households, and view company summary information. In addition, end users can retrieve information about investors, including investors preferences, holdings, and transactions. You can save time and reduce keystrokes by using a workflow to automate steps that are repeatedly performed by end users. For more information, see Siebel Business Process Framework: Workflow Guide.
About Company Hierarchies

A company hierarchy is a group of companies that are organized by parent-child relationships. Siebel Industry Applications support displaying these company relationships in a hierarchical tree. The hierarchical tree is a visual representation of company hierarchy data that allows end users to view the relationships between companies. By viewing a company roll-up, users can see aggregated company information, including contacts, coverage teams, activities, and opportunities. When end users have access to a company, they can review the hierarchical structure for that company, its child divisions, and the contacts who work there. Company hierarchies are displayed in five subviews of the Companies screen: Relationship Hierarchy view Activity Roll-up Contact Roll-up Opportunity Roll-up Coverage Team Roll-up
Depending on your configuration, a company that does not have a parent-child relationship with another company might not appear in the roll-up views. For more information on company hierarchies, see Generating Company Hierarchies for Data Aggregation on page 39 and Viewing Company Hierarchies in Roll-Up Views (End User) on page 42.
32
Managing Companies Scenario for Managing Company Information
Scenario for Managing Company Information

This scenario features sample tasks performed by a sales representative in the insurance and healthcare industries. Your company might follow a different workflow according to its business requirements. In this scenario, end users are the sales representatives who manage company information. They enter information to: Add new companies to the database and create company assessments Associate applications and service requests with a company Manage company coverage teams View company summary information View relationships in a graphical manner
Sales Representative Tracks Company Information

A sales representative uses the Companies screen to capture and manage profile information about her business customer, such as contacts, organizational structure, management, and financial information. In addition to viewing market statistics and D&B reports. Using Siebel Insurance, she can capture and track information about a companys: Relationship with her organization, such as the coverage team, contract terms, sales and service information Preferred delivery channels, at both summary and detailed levels
She can also view details of competitors and create and access marketing and sales presentations. The sales representative can create a new company record or view and modify information about existing companies. For example, if the sales representative is preparing for a sales call, she can use the Companies screen to answer the following questions: What business is this company in? Who are the executives I must be calling on? What is this companys financial profile? What financial accounts and products does the company already own? What types of service issues has the company had?
Process of Managing Companies

This topic details sample tasks often performed by administrators and end-users when managing companies. Your company might follow a different process according to its business requirements.
33
Managing Companies Setting Up Values for Companies
Administrator Procedures
The following list shows tasks administrators typically perform to manage companies: Setting Up Values for Companies on page 34 Deleting Company Information on page 35 Managing Competitor Information on page 36 Verifying Coverage Team Members on page 36 Managing the Custom-Defined Relationship Types LOV on page 38 Generating Company Hierarchies for Data Aggregation on page 39
End-User Procedures
The following list shows tasks end users typically perform when managing companies: Adding Companies and Investors (End User) on page 41 Viewing Company Hierarchies in Roll-Up Views (End User) on page 42 Creating Company Assessments (End User) on page 44 Adding Company Applications (End User) on page 44 Adding Company Service Requests (End User) on page 45 Managing Company Coverage Teams (End User) on page 45 Viewing Company Summaries (End User) on page 46 Viewing Company Relationship Hierarchies (End User) on page 46
Setting Up Values for Companies

Administrators can create new industries and territories so that the appropriate selections are available to end users when they add companies. When a company is added to Siebel Insurance, the end user adding the company is responsible for indicating the industry to which the company belongs. Administrators are responsible for creating the industries that appear to end users.
Adding Industries
Use the following procedure to add an industry.
To add an industry 1
Navigate to the Administration - Data screen, then the Industries view.
34
Managing Companies Deleting Company Information
In the Industries list, add a record, and complete the necessary fields. Some fields are described in the following table. Field Language Code SIC Code Type Description Primary language of the classification used. Standard Industry Classification code as defined by the U.S. Department of Commerce. The classification used to describe the industry.
Companies are often associated with a territory. Administrators can create the territories that appear in the Territory field when end users add a company to Siebel Insurance.
Adding Territories
Use the following procedure to add a territory.
To add a territory 1 2
Navigate to the Administration - Assignment screen, then the Territories view. In the Territory List list, add a record, and complete the necessary fields.
Deleting Company Information

Deleting a company completely removes the company, as well as all activities related to the company, from Siebel CRM. Only delete a company record if you are certain that the company is no longer active. If end users are unsure whether or not a company is still active (and therefore must not be deleted), they have the option of removing themselves from the company team instead of deleting the record. As the Siebel administrator, you can make a company unavailable to all other users. First, you can assign yourself as the primary team member. Second, you remove all other employees from the companys team.
To make a company unavailable to all other users 1 2 3 4

Navigate to the Companies screen, then the Companies Administration view. In the Company list, drill down on the Name link. In the Company Team dialog box, locate the administrator, and click in the Primary field. In the Company Team dialog box, delete all other coverage team members and click OK. Only those users with access to the All Companies and All Companies Across Organizations views are able to see this company.
35
Managing Companies Managing Competitor Information
Managing Competitor Information

Effective sales and marketing requires that your employees have up-to-date and consistent information about the competition and their products. This topic describes how to administer information about competitors and competitive products within the Companies screen.
To indicate that a company is a competitor 1 2 3 4

Navigate to the Companies screen, then the Companies Administration view. In the Company list, add or select a company. In the Company form, click the show more button. Select the Competitor check box to add the company to the Competitors list. The company appears in the Competitors list. The Competitors list is available in the Competitors screen and related screens, such as Opportunities. NOTE: Nonadministrators can specify that a company is a competitor by selecting Competitor from the Type drop-down list. However, selecting Competitor from the Type drop-down list does not add the company to the Competitors list as seen on the Competitors screen, or in the Pick Competitors dialog box, which is accessible on related screens, such as Opportunities. When a company has been indicated as a competitor, you might want to add document files of comparative and competitive literature. For more information, see the chapter on literature administration in Siebel Applications Administration Guide.
Removing Records from the Competitors List

You cannot delete records that have been added to the Competitors list, since deleting them would also remove them from related screens, like Opportunities. For example, a company might have been a competitor for an opportunity last month. Even if the company is no longer a competitor, the competitor record must remain as part of the history of the opportunity. If you no longer want a record to appear in the Competitors list, deselect the Competitor check box. This removes the record from the Competitors screen without affecting other screens.
Verifying Coverage Team Members

If you are logged on as a Siebel administrator, you can search for companies that do not have any coverage team members. Managers can add or delete the members of a companys coverage team if they are the existing primary team member, or the primary team member is one of their direct reports. If you are logged in as an administrator, you can change the primary team designate for any company in the Company Administration view. (Navigate to the Companies screen, then the Companies Administration view.) NOTE: In Siebel Financial Services, the terms sales team and account team are equivalent to coverage team.
36
Managing Companies Verifying Coverage Team Members
The procedures that follow involve making selections in the Account Team field. If the Account Team field does not appear in your installation, you might reveal it using the Columns Displayed dialog box. NOTE: Usually, Assignment Manager resolves problems with coverage teams and owner assignment automatically. For more information on Assignment Manager, see Siebel Assignment Manager Administration Guide.
Searching for a Company without Coverage Team Members

Use the following procedure to search for a company without coverage team members.
To search for a company without any coverage team members 1 2

Navigate to the Companies screen, then the Companies Administration view. In the Companies list, define a new query where the Name field is: count( ) = 0
Execute the query. The query returns a list of all companies that do not have any coverage team members.
Adding and Deleting Members of the Coverage Team for a Company

Use the following procedure to add or delete members of the coverage team for a company.
To add or delete members of the coverage team for a company 1 2 3

Navigate to the Companies screen, then the Companies Administration view. In the Companies list, select a company, and click the More Info view tab. In the Account Team field, select an employee in the Coverage Team dialog box, and click Add or Remove.
Changing the Primary Coverage Team Member for a Company

Use the following procedure to change the primary coverage team member for a company.
To change the primary coverage team member for a company 1 2 3

Navigate to the Companies screen, then the Companies Administration view. In the Companies list, select a company, and click the More Info view tab. In the Account Team field, select the Primary field for the new primary coverage team member.
37
Managing Companies Managing the Custom-Defined Relationship Types LOV
Managing the Custom-Defined Relationship Types LOV

If you are logged in as the Siebel administrator, you can create and maintain a list of predefined custom-defined relationship types. A default list of values is provided with the application. These relationship types appear in the drop-down LOV for the Type field found on the Relationship Hierarchy views, in the Party Relationship applet.
To add a custom-defined relationship type 1 2

Navigate to the Administration - Data screen, then the List of Values view. In the List of Values list, create a New Query where Type equals PARTY_RELATIONSHIP_TYPE. At least six records will be returned, showing the existing list of values for custom-defined relationship type.
In the List of Values list, add a record, and complete the necessary fields. Some fields are described in the following table. Field Active Display Value Language Independent Code Language Name Order Parent LIC Translate Type Comments Determines whether the value is displayed to the end user in the Relationship drop-down list. Value as displayed in the Relationship drop-down list. Code used internally by the Siebel application. Language used for the list of values Display Value field. Numerical order in which a value is displayed within the Relationship drop-down list. Language-independent code of a parent list of values. It is used in hierarchical list of values. When checked, indicates that the list of values is part of a multilingual list of values (MLOV). The type of list of values. For this procedure, select PARTY_RELATIONSHIP_TYPE.
NOTE: You cannot delete LOV table entries. Use the Active check box to deactivate an LOV entry and thereby remove it from the Relationship drop-down list.
38
Managing Companies Generating Company Hierarchies for Data Aggregation
Generating Company Hierarchies for Data Aggregation

Data aggregation is available by using the Roll-up views, providing the administrator defined one or more hierarchies. The application administrator typically defines a default hierarchy by associating accounts with one another using the parent field on a company form, or the subaccount view for child accounts. Administrators can define Company hierarchies to display aggregated data across organizational structures, such as the activities, opportunities, contacts, and coverage teams. For example, the top node of the hierarchy contains activities for the organization, the subsidiaries below the organization, the departments at the subsidiaries, and contacts working at any level of the tree. As the end users move up and down the tree, they see more or less data rolled up to the selected level. By default, only companies that are part of a relationship hierarchy can display roll-up data. You can modify the application to display roll-up data for companies which are not part of a hierarchy.
To configure display of roll-up data for companies not in a hierarchy

Using Siebel Tools, set the DynHierachry user property of the Dynamic Hierarchy Direct Relationship business component to LoadAllAccounts
For more information on setting user properties, see Configuring Siebel Business Applications. Siebel Global Accounts is the module that provides this aggregation functionality. For more on global accounts, see Siebel Applications Administration Guide. The application administrator can define two types of hierarchies for data aggregation: Default hierarchy for all end users, see Default Company Hierarchies on page 39 Specific hierarchies that are used only by certain end users, see Dynamic Company Hierarchies on page 40
Default Company Hierarchies

The application administrator sets up a default company hierarchy one time, during the initial application setup. The default hierarchy is available to all end users who are not tied to a specific hierarchy, and who have been granted view access to the companies represented in the hierarchy. It is the administrators responsibility to give end users access to Company views. For more information, see Siebel Applications Administration Guide. When new companies are added, they are automatically added to the default hierarchy tree. The contacts, coverage teams, activities, and opportunities that are associated with the company are automatically displayed in the roll-up views. In the preconfigured application, using the Generate Hierarchy button adds only parent account and child companies to the hierarchy. Any company that does not have a child or parent is not displayed in the roll-up views. Use Siebel Tools to change the DynHierarchy LoadAllAccounts user property to alter this behavior.
39
Managing Companies Generating Company Hierarchies for Data Aggregation
You can set the DynHierarchy LoadAllAccounts user property on the Dynamic Hierarchy Direct Relationship business component to N or Y. When it is set to N, only parent and children appear in the generated hierarchy. When DynHierarchy LoadAllAccounts user property is set to Y, all companies are added to the generated hierarchy. For more information on setting user properties, see Siebel Developers Reference.
To generate a default company hierarchy 1 2

Navigate to the Companies screen, then the Global Companies Administration view. In the Company Hierarchies list, click Generate Hierarchy. The parent-child account relationships that have been defined in your application are registered for participation in the roll-up views. This process might take some time, depending on the quantity of account records that are in your existing environment. When the company hierarchy has been generated, a new record appears in the Company Hierarchies list. The Hierarchy Name field of the record contains the user ID of the administrator who generated the hierarchy and the time it was generated. If it is the only hierarchy record, the Default field is automatically checked. The companies that have been added for participation in the roll-up views appear in the Company Relationships list. NOTE: If no accounts are visible in the Company Relationships list, click the query button, step off the query, and click Go to refresh the view.
(Optional) Rename the company hierarchy and, if necessary, check the Default field. NOTE: If end users are using the application when you generate a hierarchy, they must log off and log on again to see the default hierarchy in the roll-up views.
Dynamic Company Hierarchies

In some cases, users work with particular companies within a large corporation, but not with others. In these instances, some end users do not need to or must not see aggregated data across the entire corporation. An administrator can define a custom hierarchical structure across which data can be aggregated. This defined structure, called a dynamic hierarchy, can be as simple or complex as needed and offers users the ability to aggregate data across the companies they are interested in seeing.
To create a dynamic company hierarchy of selected companies 1 2 3 4

Navigate to the Companies screen, then the Global Companies Administration view. In the Company Hierarchy list, and create a new record. Scroll down to the Company Relationships list, create a new record, and select company. All the accounts in the Company Relationship list belong to the new account hierarchy. To define parent and child relationships:
Select a company in the Company Relationship list that has no parent.
40
Managing Companies Adding Companies and Investors (End User)
In the Parent field, select a parent.
NOTE: Only companies entered in the Company Relationships list (Step 3) are available for selection in the parent field.
Repeat Step 4 for all companies that have no parents.
Associating Dynamic Hierarchies with an Organization

Use the following procedure to associate the dynamic hierarchy with an organization.
To associate the dynamic hierarchy with an organization 1 2 3

Navigate to the Administration - Group screen, then the Organizations view. Select the organization in the Organizations list. In the organization form, select the desired hierarchy in the Account Hierarchy field.
End users can only see the hierarchy with which their current positions primary organization is tied. It is the administrators responsibility to associate end users with positions, positions with organizations, and organizations with hierarchies. For more information, see Siebel Applications Administration Guide.
Adding Companies and Investors (End User)

When end users identify a possible lead, the lead can be added as a company. Users can then begin to add and track information about the company.
To add a company or investor 1 2 3

Navigate to the Companies screen, then the Companies List view. In the Companies form, click the show more button, add a record, and complete the necessary fields. To specify a privacy level, in the Privacy Option field select one of the following:

Opt-In. Sharing of nonpublic personal information is allowed without restrictions. Opt-Out - Affiliates. Sharing of nonpublic personal information with affiliates is not allowed. Opt-Out - Third Party. Sharing of nonpublic personal information with third parties is not allowed.
41
Managing Companies Viewing Company Hierarchies in Roll-Up Views (End User)
Opt-Out - All Parties. Sharing of nonpublic personal information with any affiliate or third party is not allowed.
United States law requires that financial institutions disclose their privacy policies regarding the sharing of non public personal information with third parties, and fair credit reporting, that impacts the sharing of non public personal information with affiliates. End users can specify a privacy level by making a selection from the Privacy Option field. The Privacy Option field is for registering the privacy level requested by the company; it does not impact record visibility in any way.
To identify the company as an investor, check the Investor box in the Company form.
Viewing Company Hierarchies in Roll-Up Views (End User)

End users can review the company and its parent organization, subsidiaries, contacts, opportunities and relationships to other entities using the graphical relationship hierarchy tree control. This control is available in the roll-up views. By drilling down on hypertext links on the hierarchy tree, end users can navigate to related views. NOTE: If the company has not been added to a hierarchy tied to the user's position's organization (either default hierarchy or dynamic hierarchy), the hierarchy tree is not visible to the end user. The following message appears: The selected record is not included as part of your defined hierarchy. If you feel this is in error, please contact your system administrator. The administrator is responsible for associating positions with organizations and an organization with a hierarchy. The Activities-Roll-up view shows all of the activities associated with the selected company and its children. End users can apply filters to the list to find specific activity records and save the filtered list. NOTE: If a company is not associated with any other organizations through the relationship hierarchy, then the roll-up views will not contain any data. A company must have a parent organization, or have children organizations, in order to display roll-up data.
To view aggregated activities for a company 1 2

Navigate to the Companies screen, then the Companies List view. Drill down on the desired company, and click the Activities-Roll-up view tab. The associated hierarchy appears on the right side of the screen. All activities associated with the company and all of its children appear in the Activities-Roll-up list. In the Activities-Roll-up List, you can:

Drill down on an activity type to navigate to the Activities screen, then the Attachments view. Drill down on a company name to navigate to the Companies screen, then the Contacts view.
NOTE: If you create an activity in the Activities screen and do not set the Company field, the activity will not appear in the Activities-Roll-up list.
42
Managing Companies Viewing Company Hierarchies in Roll-Up Views (End User)
Viewing the Aggregated Coverage Team for a Company

Use the following procedure to view the aggregated coverage team for a company.
To view the aggregated coverage team for a company 1 2

Navigate to the Companies screen, then the Companies List view. Drill down on a company, and click the Coverage Team-Roll-up view tab. The associated hierarchy appears on the right side of the screen. All coverage team members associated with the company and all of its subsidiaries appear in the Coverage Team-Roll-up list. In the Coverage Team-Roll-up list, you can:

Drill down on a last name to navigate to the Employees screen. Drill down on an email address to open a blank email message addressed to the team member who has that address.
Viewing the Aggregated Opportunities for a Company

Use the following procedure to view aggregated opportunities for a company.
To view aggregated opportunities for a company 1 2

Navigate to the Companies screen, then the Companies List view. Drill down on a company, and click the Opportunities-Roll-up view tab. The associated hierarchy appears on the right side of the screen. All opportunities associated with the company and all of its children appear in the Opportunities-Roll-up list. In the Opportunities-Roll-up list, you can:

Drill down on an opportunity name to navigate to the Opportunities screen. Drill down on a company name to navigate to the Companies screen, then the Contacts view.
Viewing an Aggregated List of Contacts for a Company

Use the following procedure to view an aggregated list of contacts for a company.
To view an aggregated list of contacts for a company 1 2

Navigate to the Companies screen, then the Companies List view. Drill down on a company, and click the Contact-Roll-up view tab. The associated hierarchy appears on the right side of the screen. All contacts associated with the company and all of its children appear in the Contacts-Roll-up list. In the Contacts-Roll-up list, you can:
Drill down on a last name to navigate to the Contacts screen.
43
Managing Companies Creating Company Assessments (End User)
Drill down on a company to navigate to the Companies screen, then the Contacts view. Drill down on an email address to open a blank email message addressed to the contact who has that address.
Creating Company Assessments (End User)

An assessment is a set of attributes used to assess the business potential or credit worthiness of a company. Company assessments can be used to compare companies to each other or against a model, or to learn about companies and sales situations. End users complete the company assessment by selecting the appropriate values for the different attributes.
To perform a company assessment 1 2 3 4

Navigate to the Companies screen, then the Companies List view. In the Companies list, drill down on the company for which the assessment is being performed. Click the Assessments view tab, and create a new record. In the Template Name field, select the appropriate template. Attribute records are automatically generated in the Assessment Attributes list.
In the Assessment Attributes list, make a selection in the Value field for each attribute.
NOTE: Administrators must create the assessment templates. See Siebel Applications Administration Guide for more information on how to create assessment templates.
Adding Company Applications (End User)

Applications are used for companies that want to apply for offered services or products. For example, a small business wants to apply for a business checking account. The end user handling the inquiry finds the company in the All Companies view, navigates to the Applications view, and creates an application record for this business checking account application.
To associate an application with a company 1 2 3

Navigate to the Companies screen, then the Companies List view. In the Companies list, drill down on the company to associate with an application. Click the Applications view tab, create a new record, and complete the necessary fields.
NOTE: Drill down on the Application Name link to enter more detailed application information.
44
Managing Companies Adding Company Service Requests (End User)
Adding Company Service Requests (End User)

A service request is a request from a company for information or assistance with a problem related to purchased products or services. When a customer calls about an existing service request, end users can find the service request and give status information to the caller in several ways. They can: Review the service request information Create an activity to record the customers call Update the service request with additional information from the customer Resolve the service request Assign the service request Transfer the caller to another service representative
If a call requires that an end user create a new service request, she can create one. Siebel Insurance automatically assigns a unique service request (SR) number to track the new service request throughout Siebel CRM.
To add a service request associated with a company 1 2 3 4

Navigate to the Companies screen, then the Companies List view. From the Show drop-down list, select All Companies. In the Companies list, drill down on the desired company. Click the Service Requests view tab, create a new record, and complete the necessary fields. The application automatically assigns a service request number (SR#).
Managing Company Coverage Teams (End User)

A coverage team is the group of employees that are assigned to manage the relationship with a given company. The coverage team for a company is defined as all users who have access to the company in the My Companies view. NOTE: Similar coverage team functionality is also available for contacts. You can use the Contact Coverage Team view (Navigate to the Contacts screen, then the Coverage Team view) to manage the contact coverage team. End users can use the company coverage team functionality available in Siebel Insurance to: Record and display employees covering a company within a single company record Specify and review the nature of the employee's relationship with each covered company, defined as the Coverage Role and Attributes list
45
Managing Companies Viewing Company Summaries (End User)
To add a member to a coverage team 1 2 3 4

Navigate to the Companies screen, then the Companies List view. In the Companies list, drill down on the desired company. Click the Coverage Team view tab, create a new record, and select an employee. If known, select the employees coverage role using the drop-down list in the Coverage Role field. NOTE: The Siebel administrator maintains the Coverage Role LOV in the List of Values screen under the Type field value type FINS_COVERAGE_ROLE_TYPE. Navigate to the Administration Data screen, then the List of Values view, to access the List of Values screen.
If desired, scroll down to the Categories and Securities view tabs and select values defining the coverage relationship between the employee and the company; you can select one or more attributes. The application adds the employee to the coverage team with a defined relationship. The company will appear in the employees My Companies view.
Viewing Company Summaries (End User)

The Company Summary view provides a comprehensive view of a company in an editable format. This view displays basic company information, financial accounts, call reports, logged alerts, and contacts associated with a company.
To view company summary information 1 2 3

Navigate to the Companies screen, then the Companies List view. In the Companies list, drill down on the desired company. Click the Summary view tab.
For more information on editing summary view information, see Configuring Summary Views on page 20.
Viewing Company Relationship Hierarchies (End User)

End users use the Relationship Hierarchy view to identify and capture key relationships for a company. This view features a graphical tree that provides a visual representation of a companys relationships. The tree shows the natural hierarchy of a companys parent-child relationships to entities such as companies, subsidiaries, divisions, contacts, and coverage relationships with employees, as well as custom-defined relationships.
46
Managing Companies Viewing Company Relationship Hierarchies (End User)
Custom-defined relationships are dynamic associations between the company and any contact, organization, household, or employee. End users can record custom-defined relationships between any two entities in the adjacent Party Relationships list. NOTE: The Relationship Hierarchy view is also available on the Contacts, Employee (read only) and Households screens. For more information, see Viewing Contact Relationship Hierarchies (End User) on page 57 and Using the Household Relationship Hierarchy on page 62.
To establish a natural parent-subsidiary relationship between two companies 1 2 3 4 5 6

Navigate to the Companies screen, then the Companies List view. In the Companies list, drill down on the company to be established as the subsidiary. Click the More Info view tab. In the Parent field, select the parent company. Repeat Step 2 through Step 4 to set up companies, subsidiaries, branches, and departments as needed for your deployment. Click the Relationship Hierarchy view tab. The new parent-subsidiary relationship is shown in the Relationship Hierarchy explorer in the lower-left corner of the screen.
Creating a Custom-Defined Relationship

Use the following procedure to create a custom-defined relationship.
To create a custom-defined relationship 1 2 3

Navigate to the Companies screen, then the Companies List view. In the Companies list, drill down on the company for which you want to create a custom-defined relationship. Click the Relationship Hierarchy view tab.
47
Managing Companies Viewing Company Relationship Hierarchies (End User)
In the Party Relationship list, add a record, and complete the necessary fields. Some fields are described in the following table. Field Relationship Comments Categorizes the relationship between the company and another entity. Field has an LOV for custom-defined Relationship values. Predefined values include Reports To, Spouse, Child, Lawyer, Board Member, Primary Contact (Backup), Admin Assistant, Competitor, Referral, Service Provider, Investor, Wealth Management Rep, Related Subsidiary, Bank Attorney, Trustee Attorney, and Debtor Attorney. This LOV can be modified by the Siebel administrator. For more information, see Managing the Custom-Defined Relationship Types LOV on page 38. Start Date End Date If the custom-defined relationship falls: Type Between the Start and End Dates, the custom-defined relationship appears in the tree. Outside the range, the custom-defined relationship does not appear to the user. The user can enter a start or end date, or both.
Use this field to determine the type of entity with which you wish to establish a relationship. Defaults to Contact. Other values include Household, Organization, and Employee. The value in this field is based on the Type field. For example, if Type equals Contact, then clicking the select button in the Value field displays the Select Contact dialog box.
Value
The newly defined relationship appears in the Relationship Hierarchy explorer.
48
Managing Contacts
This chapter describes how to manage contacts. It includes the following topics: About Managing Contacts on page 49 Scenario for Adding a New Contact on page 50 Process of Managing Contacts (End User) on page 51 Managing Contact Information (End User) on page 51 Creating Customer Assessments (End User) on page 55 Setting the Customer Value Icon (End User) on page 56 Viewing a Contact Summary (End User) on page 56 Viewing Contact Relationship Hierarchies (End User) on page 57
About Managing Contacts

Contacts are entities or individuals with whom the company does business with or with whom it expects to do business with in the future. Contacts includes employees of other companies, independent consultants, vendors, or personal acquaintances. Contacts can belong to only one company, but they can be part of many opportunities, including opportunities that do not involve their companies. Within Siebel Insurance, contacts are presented in a single view of the customer and your relationship with the customer. CAUTION: This chapter assumes you have renamed Siebel Account objects to Companies. By default, Siebel Insurance installs using the term Accounts. For more information on renaming Siebel Account objects, see Siebel Database Upgrade Guide. End users can: Enter and track information about contacts, which includes products bought, details of signed agreements or contracts, and products previously recommended to the customer. Document marketing campaigns and details of each customers response. Maintain a history of service requests, insurance claims, and product applications that the customer has made in the past. Analyze a customers financial health as well as a customers needs.
49
Managing Contacts Scenario for Adding a New Contact
The Contacts screen provides an alternative view of data that is available in other screens. Many tasks that can be performed in the Contacts views can also be performed in other screens. For example, users can create activities for a contact either in the Contact Activities view, or they can go to the My Activities view to enter a new activity, and then associate it with the contact. For more information on basic contact functionality and administration, see Siebel Applications Administration Guide. You can save time and reduce keystrokes by using a workflow to automate steps that are repeatedly performed by end users. For more information, see Siebel Business Process Framework: Workflow Guide.
Scenario for Adding a New Contact

This scenario features sample tasks performed by a sales representative in the insurance industry. Your company might follow a different workflow according to its business requirements.
Sales Representative Adds a New Contact

At a conference, a new account representative meets a potential customer. The potential customer gives the new account representative his business card and informs her that he had recently moved to the area and works for a medium sized software company. The new account representative returns to her office and enters her new acquaintance into Siebel Insurance as a new contact. She can also enter his company information and associate the company with the contact. In the Relationship Hierarchy view, she can enter the relationships for this contact, including all companies he is associated with, the contact's business partners, lawyer, his family members, and other influential relationships. As the creator of this new contact record, she is automatically added to the coverage team as the primary representative for the customer. If necessary, she can also add the small business manager and other product experts to the coverage team so they can see this new contact in their My Contacts view. As the customer is looking for personal and business services, the account representative can create separate opportunity records in Siebel Insurance associated with the contact. In the opportunity records, she records the products and services the customer is interested in as well as other followup activities to serve the customer's needs. In the scenario, end users are the new account representatives who manage company information in the field. They enter information to: Add a new contact and associate him/her with companies Use the Relationship view to enter all the contact's influential relationships Add other account representatives to the coverage team Create new opportunities associated with the contact Create follow-up activities and assign them to the right representatives to close the potential opportunities
50
Managing Contacts Process of Managing Contacts (End User)
Process of Managing Contacts (End User)

This topic details sample tasks often performed by administrators and end-users when managing contacts. Your company might follow a different process according to its business requirements. The following list shows tasks end users typically perform when managing contacts: Managing Contact Information (End User) on page 51 Creating Customer Assessments (End User) on page 55 Setting the Customer Value Icon (End User) on page 56 Viewing a Contact Summary (End User) on page 56 Viewing Contact Relationship Hierarchies (End User) on page 57
Managing Contact Information (End User)

Contacts are entities or individuals with whom the company currently does business with or with whom it expects to do business with in the future. End users manage contact information by: Adding new contacts. See Adding Contacts on page 51. Creating contact categories and notes. See Creating Categories for Contact Information on page 52 and Creating Notes About Contacts on page 53. Managing contact referral information. See Managing Contact Referral Information on page 54.
Adding Contacts
When end users meet someone in the course of business, they add a contact record for that individual to track pertinent personal information and possible potential future business. NOTE: The Personal Contacts List is different from the Contacts Lists because it is designed for contacts not associated with a company. Therefore, in the Personal Contacts List, adding a company to a record does not also add it to the My Contacts view, All Contacts view, and so on. End users must add business contacts in one of the Contacts List views proper. They must create, review, and manage activities for their personal contacts only in the Activities view of the Personal Contacts List view, not in the other Contacts views.
To add a contact 1 2
Navigate to the Contacts screen, then the Contacts List view. In the Contacts form, click the show more button, add a record, and complete the necessary fields.
51
Managing Contacts Managing Contact Information (End User)
To specify a privacy level, drill down on the contact name link, scroll down to the Privacy Option field, and select one of the following:

Opt-In. Sharing of nonpublic personal information is allowed without restrictions. Opt-Out - Affiliates. Sharing of nonpublic personal information with affiliates is not allowed. Opt-Out - Third Party. Sharing of nonpublic personal information with third parties is not allowed. Opt-Out - All Parties. Sharing of nonpublic personal information with any affiliate or third party is not allowed.
United States law requires that financial institutions disclose their privacy policies regarding the sharing of nonpublic personal information with third parties, and fair credit reporting, that impacts the sharing of nonpublic personal information with affiliates. End users can specify a privacy level by making a selection from the Privacy Option field. The Privacy Option field is for registering the privacy level requested by the contact; it does not impact record visibility in any way.
Associating a Contact with a Company

Use the following procedure to associate a contact with a company.
To associate a contact with a company 1 2 3 4

Navigate to the Contacts screen, then the Contacts List view. In the Contacts list, drill down on the desired contact. Click the More Info view tab. In the Account Name field, select a record from the list of available companies. The application automatically associates the company with the contact and populates the address with the default company address information.
5 6
To change the address, click the select button in the Address Line field, and select an address. To specify an address as the contacts primary address, click the Primary field. NOTE: The primary address in the Contact Addresses dialog box appears in the address fields on the More Info form.
In the Time Zone field, select the contacts time zone.
Creating Categories for Contact Information

If the default Contacts list and More Info form do not contain fields to track the type of information that end users must track, they can add additional categories. A manager might have set up a list of values from which users can select.
52
To add a category to a contact 1 2 3 4 5 6

Navigate to the Contacts screen, then the Contacts List view. In the Contacts form, query for the desired contact. Drill down on the Last Name link, click the Categories view tab, and create a new record. In the Categories list, select a category from the list of values or create a new category. Complete the necessary fields. Create additional categories by repeating Step 4 through Step 5.
Creating Notes About Contacts

As end users work with contacts, they learn things they might want to remember. Often these tidbits of information are best stored as notes. Users can create notes that everyone with access to the contact record can see, or they can create notes that only they can see.
To create a note regarding a contact 1 2

Navigate to the Contacts screen, then the Contacts List view. In the Contacts list, drill down on the desired contact. NOTE: If the contact does not exist, add it. For more information, see Adding Contacts on page 51.
3 4
Click the Notes view tab. From the link bar, select one of the following:

Public Notes. Notes that others can see. Private Notes. Notes that only their creators can see.
In the Notes list, add a record and complete the necessary fields. NOTE: You can perform a spell check in Private Notes, but not in Public Notes. Some fields are described in the following table. Field Created Type Description Comments Automatically populates with a date and timestamp. Default value is Note. Select alternate value to categorize the type of note. Text field for the content of the note.
53
Managing Contact Referral Information

The Referrals view tab allows end users to enter referral information associated with contacts. Referrals are potential opportunities. In the Referrals tab view, end users can record both referrals they give to their contacts, as well as referrals received from a contact.
To create a new contact for a referral 1 2 3

On the Contacts screen, create contacts. For more information, see Adding Contacts on page 51. Associate those contacts with the new company. For more information, see To associate a contact with a company on page 52. On Referrals view tab, select the Contact from the Pick Contact dialog box associated with this field.
Entering a Referral Received from a Contact

Use the following procedure to enter a referral received from a contact.
To enter a referral received from a contact 1 2 3 4

Navigate to the Contacts screen, then the Contacts List view. In the Contacts list, drill down on the desired contact. Click the Referrals view tab. From the drop-down list, select Referral From This Contact. NOTE: View all referrals from the contact by selecting Referrals From This Contact in the dropdown list.
In the form, add a record, and complete the necessary fields. Some fields are described in the following table. Field Company Last Name Comments Select an existing company or create a new one. The company selected represents the potential opportunity for your organization. Select a contact to associate with the referral company, as selected in the Company field; if you entered a Company, the list of Contacts is restricted to those associated with the selected company. Select the employee who made the referral.
Referred By
Creating a Referral to a Contact

Use the following procedure to create a referral to a contact.
54
Managing Contacts Creating Customer Assessments (End User)
To create a referral to a contact 1 2 3 4 5

Navigate to the Contacts screen, then the Contacts List view. In the Contacts list, drill down on the desired contact. Click the Referrals view tab. Scroll down to the Referrals to This Contact list, and from the drop-down list, select Referrals To This Contact. In the list, add a record, and complete the necessary fields. Some fields are described in the following table. Field Disposition Company Comments The status of the referral. Select an existing company or create a new one. The company selected represents the potential opportunity for your service provider. Select a contact to associate with the referral company, as selected in the Company field; if you entered a Company, the list of Contacts is restricted to those associated with the selected company. Select the employee from your organization who made the referral.
Last Name
Referred By
Creating Customer Assessments (End User)

The Contacts Assessments view can help end users qualify contacts. Contact assessments are created in the Contacts Assessments view. NOTE: A similar assessment functionality is available for companies. For more information, see Creating Company Assessments (End User) on page 44. A customer assessment evaluates a contact based on defined criteria. Each assessment template has a group of assessment attributes that make up the different measurement points of the assessment. A Siebel administrator can create new templates and add or modify assessment attributes. For more information on assessment templates and how to define and manage them, see Siebel Applications Administration Guide.
To create a customer assessment 1 2 3

Navigate to the Contacts screen, then the Contacts List view. In the Contacts list, drill down on the contact for whom the assessment will be added. Click the Assessments view tab, and create a new record.
55
Managing Contacts Setting the Customer Value Icon (End User)
In the Template Name field, select the desired template. Assessment attributes, as defined for the template, are automatically created in the Assessment Attributes list.
Scroll down to the Assessment Attributes list, and where possible, select a value for each attribute by clicking the select button in the Value field.
Setting the Customer Value Icon (End User)

In addition to the customer value assessment tool described in Creating Customer Assessments (End User) on page 55, there is an alternative customer value measurement device in Siebel Insurance. The customer value icon is a series of five stars visible on the contact form. The number of stars activated indicates the perceived value of the contact.
To adjust the customer value stars

From the Contacts screen, then the More Info view, adjust the value in the Tier field.
Viewing a Contact Summary (End User)

The Contact Summary view provides a comprehensive view of a contacts relationship with an end users organization in an editable format. This view displays the customers contact information, financial accounts, applications, alerts, campaigns targeted at the customer, and service requests and opportunities associated with the customer. The Customer Value stars on the Contact form indicates the customers value to the organization. For more information, see Setting the Customer Value Icon (End User) on page 56.
To view contact summary information 1 2 3

Navigate to the Contacts screen, then the Contacts List view. In the Contacts list, drill down on a contact. Click the Summary view tab.
For more information on editing summary view information, see Configuring Summary Views on page 20.
56
Managing Contacts Viewing Contact Relationship Hierarchies (End User)
Viewing Contact Relationship Hierarchies (End User)

A contacts relationships are those of influence. End users might have a contact who relies heavily on the opinions of others when making purchasing or other decisions. If so, they might want to keep track of the relationships between a contact having purchasing authority and those who might influence his purchasing decisions. End users use the Contacts Relationship Hierarchy view to identify and capture key relationships for a contact. This view features a graphical tree that provides a visual representation of a contacts relationships. The tree displays both the natural hierarchy of a contacts parent-child relationships to entities such as companies and households, as well as custom-defined relationships. Custom-defined relationships are dynamic associations between the contact and any other contact, organization, or household. End users can record custom-defined relationships between any two entities in the adjacent Party Relationships list. NOTE: The Relationship Hierarchy view is also available on the Companies and Households screens. For more information, see Viewing Company Relationship Hierarchies (End User) on page 46 and Using the Household Relationship Hierarchy on page 62.
To view a contacts relationship hierarchy 1 2 3

Navigate to the Contacts screen, then the Contacts List view. In the Contacts list, drill down on the contact for whom you want to view a relationship hierarchy. Click the Relationship Hierarchy view tab. The Contacts Relationship Hierarchy view appears.
Defining a Relationship Between Contacts

Use the following procedure to define a relationship between contacts.
To define a relationship between contacts 1 2

Navigate to the Contacts screen, then the Contacts List view. In the Contacts list, drill down on the contact for whom you want to describe relationships; if the contact does not exist, add it. For more information on adding contacts, see Adding Contacts on page 51.
Click the Relationship Hierarchy view tab.
57
Managing Contacts Viewing Contact Relationship Hierarchies (End User)
In the Party Relationship list, add a record, and complete the necessary fields. Some fields are described in the following table. Field Relationship Comments Categorizes the relationship between the contacts. The field has an LOV for Custom Defined Relationship values. Predefined values include Reports To, Spouse, Child, Lawyer, Board Member, Primary Contact (Backup), Admin Assistant, Competitor, Referral, Service Provider, Investor, Wealth Management Rep, Related Subsidiary, Bank Attorney, Trustee Attorney, and Debtor Attorney. The Siebel administrator can modify this LOV. For more information, see Configuring Lists of Values on page 20. Type Value Defaults to Contact. Other values include Household, Organization, and Employee. Identifies the other member of the relationship. The values are constrained by the Type field selection. For example, if Type equals Contact, then clicking the select button displays the Select Contact dialog box.
The newly defined relationship is expressed in the Relationship Hierarchy explorer.
58
Managing Households
This chapter describes how to manage households. It includes the following topics: About Managing Households on page 59 Scenario for Managing Households on page 60 Process of Managing Households on page 60 Adding Households on page 60 Setting the Household Privacy Option on page 61 Associating Contacts with Households on page 61 Viewing Household Summaries on page 62 Using the Household Relationship Hierarchy on page 62
About Managing Households

A household is a group of contacts generally sharing a common link or association. Households provide valuable segmentation information on the household as a whole, as well as a summary of information about the household member contacts. Users can use the Households screen for identifying and capturing demographic information about a household. They can also use the Households screen to review customers financial accounts, products, and contact information associated with that household. This information allows them to assess customers data. CAUTION: This chapter assumes you have renamed Siebel Account objects to Companies. By default, Siebel Insurance installs using the term Accounts. For more information on renaming Siebel Account objects, see Siebel Database Upgrade Guide. Grouping all of a customers accounts by household allows a service provider to identify a clients real value to the organization and seek opportunities to cross-sell and up-sell additional products and services to them, such as homeowners insurance and loans for childrens education. In addition, the ability to view all of a customer's financial accounts and related portfolio information by household allows an organization to view the households overall financial position. By following the procedures described in this chapter, users can enter, manage, and review information about household members (contacts), accounts, policies, underwriting reports, claims, opportunities, activities, service requests, and relationship hierarchies. NOTE: Many of the views are read-only, because they provide a summary of information about household contacts. The only editable views are Contacts and Relationship Hierarchy. The Households screen and associated views that appear in Siebel Insurance share much of the functionality found in Siebel Business Applications. This chapter focuses on the household functionality that is unique to Siebel Insurance. For more information on basic household functionality, see Siebel Applications Administration Guide.
59
Managing Households Scenario for Managing Households
Scenario for Managing Households

These scenarios are examples of workflows performed by sales representatives and their managers in the insurance and healthcare industries. Your company might follow a different workflow according to its business requirements. Household information supports sales and service decisions for segmentation and cross-selling. It also provides background information for the finance and insurance industries about a household and all of its contacts. A sales representative uses the Household screen for identifying and capturing demographic and relationship information about the household, and for reviewing policies and products associated with that household. From the Households screen, the sales representative creates a new household for a new customer. He then adds contacts to the household. Some weeks later, the sales representative wants to review household information. He navigates to the My Households view, and then selects the Insurance Summary view to review a list of contacts, service requests, policies and quotes, and claims associated with a household. In this scenario, end users are the sales representatives who manage household information in the field. They enter and review information to: Add a household Add a contact to a household View household summary information View household relationships View household policies
Process of Managing Households

This topic details sample tasks often performed by end-users when managing households. Your company might follow a different process according to its business requirements. Adding Households on page 60 Setting the Household Privacy Option on page 61 Associating Contacts with Households on page 61 Viewing Household Summaries on page 62 Using the Household Relationship Hierarchy on page 62
Adding Households
End users can collect and manage information about a customers household. Households are added from the Households screen. For detailed information on how to add a household see Siebel Applications Administration Guide.
60
Managing Households Setting the Household Privacy Option
Setting the Household Privacy Option

United States law requires that financial institutions disclose their privacy policies regarding the sharing of nonpublic personal information with third parties, and fair credit reporting, that impacts the sharing of nonpublic personal information with affiliates. End users can specify a privacy level by making a selection from the Privacy Option field. The Privacy Option field is for registering the privacy level requested by the household; it does not impact record visibility in any way.
To set the privacy option for a household 1 2

Navigate to the Households screen, then the List view. To specify a privacy level, scroll down to the Privacy Option field and select one of the following:

Opt-In. Sharing of nonpublic personal information is allowed without restrictions. Opt-Out - Affiliates. Sharing of nonpublic personal information with affiliates is not allowed. Opt-Out - Third Party. Sharing of nonpublic personal information with third parties is not allowed. Opt-Out - All Parties. Sharing of nonpublic personal information with any affiliate or third party is not allowed.
Associating Contacts with Households

Contacts are persons associated with a household. End users can specify one person in the household as the head of household and then identify the others as spouse, child, or dependent parent.
To add a contact to a household 1 2 3 4

Navigate to the Households screen, then the List view. In the Households list, drill down on the household to which the contacts will be added. Click the Contacts view tab. In the Contacts list, click Add, and do one of the following:

Select an existing contact and click OK. Perform a query to choose an existing contact. Select New to add a new contact. The contact is associated with the household.
NOTE: In the Households screen, a contacts address is his or her residential or personal address. In the Contacts screen, a contacts address is his or her work address. Household addresses can only be selected from among residential addresses.
61
Managing Households Viewing Household Summaries
Viewing Household Summaries

The Household Summary view provides a comprehensive view of the households relationship with an end users organization in an editable format. This view displays basic information about the household, contacts, financial accounts, and past or pending service requests.
To view household summary information 1 2

Navigate to the Households screen, then the List view. In the Households list, drill down on the household, and click the Summary view tab.
Using the Household Relationship Hierarchy

End users use the Household Relationship Hierarchy view to identify and capture key relationships for a household. This view features a graphical tree that provides a visual representation of a households relationships, which includes its natural relationships to the household contacts as well as custom-defined, dynamic relationships. Users can create custom-defined relationships between a household and any contact or organization. End users can record custom-defined relationships between any two entities in the adjacent Party Relationships list. NOTE: The Relationship Hierarchy view is also available on the Contacts and Companies screens. For more information, see Viewing Contact Relationship Hierarchies (End User) on page 57 and Viewing Company Relationship Hierarchies (End User) on page 46.
To create a custom-defined relationship 1 2 3

Navigate to the Households screen, then the List view. In the Households list, drill down on the household for which you wish to define relationships. Click the Relationship Hierarchy view tab, and in the Party Relationship list, add a record.
62
Managing Households Using the Household Relationship Hierarchy
Complete the necessary fields. Some fields are described in the following table.
.
Field Relationship
Comments The value in this field categorizes the relationship between the household and the other entity. The field has an LOV for custom-defined Relationship values. Predefined values include Reports To, Spouse, Child, Lawyer, Board Member, Primary Contact (Backup), Admin Assistant, Competitor, Referral, Service Provider, Investor, Wealth Management Rep, Related Subsidiary, Bank Attorney, Trustee Attorney, and Debtor Attorney. This LOV can be modified by the Siebel administrator. For more information, see Configuring Lists of Values on page 20. The value in this field determines the type of entity with which you wish to establish a relationship. Defaults to Contact. Other values include Household, Organization, and Employee. The value in this field is based on the Type field. For example, if Type equals Contact, then clicking the select button in Value field displays the Select Contact dialog box.
Type
Value
The newly defined relationship appears in the Relationship Hierarchy explorer.
63
Managing Households Using the Household Relationship Hierarchy
64
Managing Call Reports
This chapter describes how to manage call reports. It includes the following topics: About Managing Call Reports on page 65 Scenario for Managing Call Reports on page 66 Process of Managing Call Reports on page 67 Viewing Call Report Charts on page 67 Activating the New Call Report Workflow on page 68 Managing Call Report Templates on page 69 Adding Call Reports (End User) on page 69 Creating Call Report Distribution Lists (End User) on page 71 Associating Action Items, Notes, and Attachments with Call Reports (End User) on page 71 Setting the Call Report Privacy Flag (End User) on page 72 Emailing and Printing Call Reports (End User) on page 72
About Managing Call Reports

Call reports are records of meetings and other conversations with clients, organizations, and individuals. Call reports are often required of employees because they: Are a means for new relationship managers to learn about the client and its history with the organization. Allow senior managers and product specialists associated with a certain client to keep up with the developments in the client relationship, even if they do not meet with the client on a regular basis. Provide a record of important and informal agreements. In the event that a failed financing transaction results in legal proceedings, these reports are an important component of the legal process.
Administrators use these procedures to view a chart of call reports and manage call report templates. End users use the Call Reports screen to add a new call report, create a call report distribution list, designate a report as private, and email or print call reports. Siebel Insurance can provide notification of new call reports to designated individuals. For more information, see Siebel Business Process Framework: Workflow Guide.
65
Managing Call Reports Scenario for Managing Call Reports
You can generate reports that are specific to Siebel Insurance. While you are in a view, click Reports in the toolbar to see a list of the available preconfigured reports for the data in that view. From the list you can access individual reports. For more information about reports, including how to customize, enhance, and create Siebel reports, see Siebel Reports Guide.
Scenario for Managing Call Reports

This scenario features sample tasks performed by an insurance agent and his manager. The scenario outlined in this topic is based on the business requirements of the insurance industry. Your company might follow a different workflow according to its business requirements. After returning to the office following a successful meeting with the client, an insurance agent loads Siebel Insurance to complete his call report. The agent navigates back to his calendar and marks the meeting as Done. He then navigates to the Call Reports screen and enters a new call report to document the meeting. In the Report Detail view, he types a brief log of the meeting and adds the names of contacts and employees who participated. Upon completing his report, the insurance agent turns to the action items that resulted from the meeting. First, he must send an email to a fellow employee to tell her about the meeting. He uses the Email Report button on the Call Report form to accomplish this task. Next, he remembers that he promised to include the client on the invitation list for the upcoming Charity Ball, so he adds an action item on the Call Reports Action Items view tab. He does this by clicking Add Action Items on the Call Report form. After he enters his action item, along with several others, he assigns them to members of his team for follow-up. The insurance agents boss is also a member of the client team. When she arrives in the office the next day and loads Siebel Insurance, she reviews the new call reports on the Call Reports screen, reading about the meeting details and notes. In this scenario, managers or Siebel administrators can use Siebel Insurance to view graphical representations of their call reports, and perform volume analysis of their own calls, their teams calls, or all call reports. The end users are insurance agents who create call reports to record their meetings and activities. They enter information to: Create new call reports Create call report distribution lists Create call report action items Attach related documents Specify a call report as private Review and add additional notes or comments Email or print call reports
66
Managing Call Reports Process of Managing Call Reports
Process of Managing Call Reports

This topic details sample tasks often performed by administrators and end-users when managing call reports. Your company might follow a different process according to its business requirements.
The following list shows tasks administrators typically perform to manage call reports: Viewing Call Report Charts on page 67 Activating the New Call Report Workflow on page 68 Managing Call Report Templates on page 69
End-User Procedures
The following list shows tasks end users typically perform when managing call reports: Adding Call Reports (End User) on page 69 Creating Call Report Distribution Lists (End User) on page 71 Associating Action Items, Notes, and Attachments with Call Reports (End User) on page 71 Setting the Call Report Privacy Flag (End User) on page 72 Emailing and Printing Call Reports (End User) on page 72
Viewing Call Report Charts

As a manager or Siebel administrator, you can use the Call Report Charts view for call volume analysis of your own calls, your teams calls, or all call reports in Siebel Insurance. Use this view to analyze call volume and call types by employee and by customer, in order to determine which clients are receiving the most service.
To view a chart for your call reports 1 2

Navigate to the Call Reports screen, then the Call Report List view. From the visibility filter, select one of the following:

My Call Reports My Teams Call Reports All Call Reports
The view selected returns an appropriate set of call report records to be analyzed.
67
Managing Call Reports Activating the New Call Report Workflow
Click the Charts link on the link bar. The chart reflects only those call report records in the current query; that is, those records listed in the Call Reports list preceding the chart.
From the lower Show drop-down list, select one of the following chart types: Chart Call Type Analysis Call Volume Analysis Call Volume by Employee Company Calling Analysis Employee Calling Analysis Comments A breakdown of all selected call reports by Call Type. Charts the number of calls each month, quarter, or year. Charts the number of calls each month, quarter, or year, employee. Charts the number of calls for each company. Charts the number of calls for each company, by employee.
NOTE: Place your cursor over any chart segment to reveal additional information about that segment. Click a segment to drill down and refocus on just the call reports in that segment.
Activating the New Call Report Workflow

When activated, the New Call Report Workflow allows end users to create call report records automatically from the Contacts, Companies, Activities, and Opportunities screens. After the administrator activates the New Call Report Workflow, the New Call Report icon appears in the upperleft corner of those screens for end users.
To activate the New Call Report Workflow 1 2 3

Navigate to the Administration - Business Process screen, then the Workflow Deployment view. In the Repository Workflow Processes list, query for the New Call Report Workflow record. Click the Activate button at the top of the list to activate this workflow process. When activated, the definition is written to the run-time tables and appears in the Active Workflow Processes view. To use the New Call Report feature after it is activated, end users can do one of the following: Click the icon Choose File, Auto, and then the Call Report from the application-level menu Use the short cut key Alt+P
NOTE: The New Call Report Workflow uses the Data Transfer Utility business service to transfer fields from one view to another. For information on the Data Transfer Utilities business service, see Siebel Order Management Infrastructure Guide. The current Data Map Objects used for the New Call Report in the Data Transfer Utility business service include: New Call Report - Account, New Call Report Activity, New Call Report - Contact, and New Call Report - Opportunity.
68
Managing Call Reports Managing Call Report Templates
Managing Call Report Templates

You can email call reports. Emailed call reports, like other communications in Siebel Business Applications, use templates to automatically format information in a message sent as an email. When you email a call report, Siebel Insurance uses the Call Report Email template to populate the email message. For more information on configuring communication templates, see Siebel CTI Administration Guide.
To view or change the call report email template 1 2 3

Navigate to the Administration - Communications screen, then the All Templates view. In the Templates list, query for the template named Call Report Email. Review or change the call report in the Call Report Email form.
Siebel Insurance provides additional syntax for customizing message templates, offering a way to embed multi-value fields within the body of the message templates. As an example of this syntax, examine the template text for the Call Report Email template.
Adding Call Reports (End User)

End users add call reports to create a record of meetings and other conversations with clients, organizations, and individuals.
To add a call report 1

Navigate to the Call Reports screen, then the Call Report List view.
69
Managing Call Reports Adding Call Reports (End User)
In the Call Report form, add a record and complete the necessary fields. Some fields are described in the following table. Field Associated Activity Comments The activity that is the subject of the call report; each call report can have only one associated activity. Selection of the associated activity is governed by the following constraints if those fields are populated: Contacts Same Company ID Same Primary Opportunity ID Same Primary Contact ID
Enter the participating contacts who were at the meeting. Designate a primary contact if desired, otherwise the first contact selected becomes the default primary contact. Entries appear in the Report Detail view and on the printed Call Report. A summary description of the call report; enter a more detailed report in the Report Detail view. List additional employees from your organization who must receive the Call Report, but must not appear on the list of participants. The call report creator and all Employee Participants are automatically placed on the distribution list. List employees from your organization who participated in the call. Entries appear in the Report Detail view and on the printed Call Report. The call report creator is automatically listed as a participant. Associate an opportunity with the call report. You can view all call reports associated with any given opportunity from the Opportunities screen. The LOV type for this field is FINCORP_CALLRPT_CONTACT_TYPE.
Description Distribution
Employees
Opportunity Type
NOTE: In the Call Reports list, the New flag is a calculated field and appears checked for five days after the creation of a call report. Your systems administrator can change this setting.
3 4
In the Call Reports list, drill down on the Description link to navigate to the Report Detail view. In the Employees and Contact lists, enter detailed information about the call. Information you enter here appears in emailed or printed call reports.
70
Managing Call Reports Creating Call Report Distribution Lists (End User)
Creating Call Report Distribution Lists (End User)

A distribution list is the list of contacts who must know what is happening with a particular client. Usually, it is the coverage team for the client, plus any additional employee participants. The application automatically places the call report creator and each employee participant on the distribution list. For other employees, such as the coverage team, to receive a call report, end users must manually add them to the distribution list. When end users use the call report Email Report feature, the distribution list controls who receives the report. The call report Print Report function and the Send Email function, both available through the application-level File menu (F9), are not affected by the distribution list.
To create a distribution list 1 2 3

Navigate to the Call Reports screen, then the Call Report List view. In the Call Reports list, drill down on the call report for which you want to create a distribution list. In the Distribution field, select one or more employees to add to the distribution list. The selected name or names are added to the distribution list.
Associating Action Items, Notes, and Attachments with Call Reports (End User)
After an end user has added a call report, an end user can associate the call report with action items, notes, and attachments. NOTE: Call report attachments, like the attachments for other activities, are stored in the S_ACTIVITY_ATT table.
To associate action items, notes, and attachments 1 2 3

Navigate to the Call Reports screen, then the Call Report List view. In the Call Reports list, drill down on the desired call report. To add notes or action items to the call report, in the Call Report form click the appropriate view tab:

Notes. Adds notes or comments. Action Items. Adds an action item.
To attach external documents to a call report, click the Attachments view tab, and choose a file or select a URL.
71
Managing Call Reports Setting the Call Report Privacy Flag (End User)
Setting the Call Report Privacy Flag (End User)

Certain call reports might contain sensitive or confidential information about a given company or opportunity. Users can designate certain calls as private by clicking the Private check box in the call report form or list. After a call report is marked as private, only those employees on the employees list can access it.
To set a privacy flag 1 2

Navigate to the Call Reports screen, then the Call Report List view. In the Call Reports list, select the desired call report, and click the Private field. The call report is now categorized as private. Only the employees on the employees list can access it.
Emailing and Printing Call Reports (End User)

You can email or print call reports for distribution and record keeping. First, submit a call report and then email or print the report.
To submit a call report 1 2 3

Navigate to the Call Reports screen, then the Call Report List view. In the Call Reports list, select the call report to submit. In the Call Report form, select Submitted from the drop-down list.
Emailing or Printing a Call Report

Use the following procedure to email or print a call report.
To email or print a call report 1 2

Navigate to the Call Reports screen, then the Call Report List view. In the Call Reports list, drill down on the call report to email or print.
72
Managing Call Reports Emailing and Printing Call Reports (End User)
In the Call Report form, do one of the following: To... Email the report. Click... Email Report. The report is automatically emailed to everyone on the distribution list. Print the report. The toolbar Reports icon. In the Reports dialog box, select Summary or Detail and click Run.
73
Managing Call Reports Emailing and Printing Call Reports (End User)
74
Managing Group Pensions
This chapter describes how to manage group pensions. It includes the following topics: About Managing Group Pensions on page 75 Scenario for Creating a Company 401(k) Plan on page 75 Group Pension Sample Tasks on page 76 Process of Managing Group Pension Plans on page 76 Defining Group Pension Products on page 77 Defining Group Pension Plans on page 78 Administering Group Pension Plans (End User) on page 80
About Managing Group Pensions

Siebel Insurance provides support for group pensions and is designed to meet the needs of sales and service professionals, managers, and pension administrators. End users can use the Group Pensions screen to manage private group pensions, which includes defined contribution plans, such as 401(k) plans and occupational group pensions, and defined benefit plans. Use these procedures to define group pension plans, plan classes, plan eligibility rules, and plan funding vehicles. Once a group pension plan is defined, users can track eligible and enrolled participants, participant contribution and investment allocations, and participant beneficiary information. You can save time and reduce keystrokes by using a workflow to automate steps that are repeatedly performed by end users. For more information, see Siebel Business Process Framework: Workflow Guide.
Scenario for Creating a Company 401(k) Plan

The following business scenario features sample tasks performed by a pension administrator. Your company might follow a different workflow according to its business requirements. Product Administration view to define a new group pension product and investment options for plan participants. She then creates a new 401(k) retirement plan and enters all the basic plan information. In this instance, she defines one class, enters the plan eligibility rules, and specifies the key contacts for the plan.
75
Managing Group Pensions Group Pension Sample Tasks
A week later, the administrator updates information for the 401(k) retirement plan participants. First, she imports a list of eligible participants. Then, she enrolls 10 new participants, specifying each employees contribution amount, the employer match, and the selected fund allocations. In this scenario, the end user is a pension administrator who uses the Group Pensions screen to: Define a group pension product and specify pension plan investment options Define a group pension plan, including participant classes, eligibility rules, and key group pension plan contacts Add eligible plan members Enroll group pension plan participants and record participant beneficiary information
Group Pension Sample Tasks

Figure 2 illustrates sample tasks that end users typically perform when managing group pensions.
Figure 2.
Group Pension Sample Tasks
Process of Managing Group Pension Plans

This topic details sample tasks often performed by administrators and end-users when managing group pension plans. Your company might follow a different process according to its business requirements.
76
Managing Group Pensions Defining Group Pension Products
The following list shows tasks administrators typically perform to manage group pension plans: Defining Group Pension Products on page 77 Defining Group Pension Plans on page 78
End-User Procedures
The following list shows a task end users typically perform when managing group pension plans: Administering Group Pension Plans (End User) on page 80
Defining Group Pension Products

Before end users create an actual group pension plan, the product administrator must first define a group pension product and specify investment options for plan participants.
To define a group pension product 1 2

Navigate to the Administration - Product screen, then the Products view. Click the New and Release button and do the following:

In the Name field, enter a name for this group pension product. In the Finance Product Type field, select Retirement from the drop down list. In Products form, select Pension from the Sub Type drop down list.
3 4
Drill down on the name, and on the link bar, click the Group Pensions Product Administration. In the Funding Vehicles list, create a new record and complete the fields.
Defining Funding Vehicles for a Group Pension Product

Use the following procedure to define funding vehicles for a group pension product.
To define funding vehicles for a group pension product 1 2 3 4 5

Navigate to the Group Pensions screen, then the Group Pensions Administration List view. In the Product list, select a group pension product. In the Funding Vehicles list, add a record, and complete the necessary fields. In the Name field, select the funds and investments available on this plan. In the Effective Date field, specify the date this plan will become available within the system.
77
Managing Group Pensions Defining Group Pension Plans
Once users have defined a group pension product and funding vehicles, the next step is to create a group pension plan for an account (see Defining Group Pension Plans).
Defining Group Pension Plans

To define a group pension plan, end users must perform the following steps: Define a group pension plan. Specify plan rules. End users use the Rules view tab to define the types of rules that govern the selected group pension plan. Define participant classes. End users define different groups of plan participants in the Classes view tab. Record key plan contacts. End users use the Contacts view tab to define key contacts associated with the selected plan. These contacts are not plan participants, but consist of key individuals associated with the selected plan such as a plan administrator, trustee, or investment committee member. Enter billing information. End users use the Bill To view tab to specify high-level payment information, such as payment frequency and a billing address.
To define a group pension plan 1 2

Navigate to the Group Pensions screen, then the Group Pensions List view. In the lower form, add a record and complete the necessary fields. Some fields are described in the following table. Field Plan Sponsor Comments A company or account that has a group pension plan associated with it or a company or account that provides a group pension for a group of people. For more information on adding additional companies, see Adding Companies and Investors (End User) on page 41. The group pension product defined in the Group Pension Product Administration view.
Name
78
Managing Group Pensions Defining Group Pension Plans
Field Type
Comments The type of group pension plan. Options include: Defined Benefit. Group pension plan that defines the amount of the benefit a plan participant will receive upon retirement. Defined Contribution. Group pension plan that describes the plan sponsor's annual contribution to the plan on behalf of each plan participant.
Sub Type
Further defines the type of group pension plan being created. Available values are based on the Type field selection. If the Type is: Defined Benefit, available options include Final Salary and Average Salary. Defined Contribution, available options include 401(k), 403(b), Group Occupational Pension, Group Personal Pension, and Group Stakeholder Pension (UK-specific).
Specifying Plan Rules

Use the following procedure to specify plan rules.
To specify plan rules 1 2 3 4

Navigate to the Group Pensions screen. In the Group Pensions list, select a group pension plan, and drill down on the plan # link. Click the Rules view tab. In the Rules form, complete the necessary fields.
Defining Participant Classes for Plan Participants

Use the following procedure to define participant classes for plan participants.
To define participant classes for plan participants 1 2 3 4 5

Navigate to the Group Pensions screen. In the Group Pensions list, select a group pension plan, and drill down on the plan # link. Click the Classes view tab. In the Classes list, add a record and complete the necessary fields. If this is an employer-sponsored plan, enter the appropriate percentage in the Employer Match% field.
79
Managing Group Pensions Administering Group Pension Plans (End User)
Recording Key Group Pension Plan Contacts

Use the following procedure to record key group pension plan contacts.
To record key group pension plan contacts 1 2 3 4 5

Navigate to the Group Pensions screen. In the Group Pensions list, select a group pension plan, and drill down on the plan # link. Click the Contacts view tab. In the Contact list, add a record and complete the necessary fields. In the Contact Role field, select one of the following:

Administrator Investment Committee Trustee
Entering Billing Information

Use the following procedure to enter billing information.
To enter billing information 1 2 3 4 5

Navigate to the Group Pensions screen. In the Group Pensions list, select a group pension plan and drill down on the plan # link. Click the Bill To view tab. In the Pay Plans list, create the appropriate number of pay plans by adding a record for each plan and completing the necessary fields. Scroll down to the lower applet and enter the required information to complete the payment information.
Administering Group Pension Plans (End User)

End users administer group pension plans by performing the following tasks: View available plan funds and investments. End users view which funds and investments are available within a specific group pension plan in the Funding Vehicles view tab. Add eligible plan members. End users can track individuals who are eligible to participate in a group pension plan in the Eligible Members view tab.
80
Create service requests to track plan administration. End users can use the Service Requests view tab to track general plan administration activities, which includes account value inquiries, changes in participant contributions, and updates to participant contact information. Users can also use this view to track changes to the features and benefits of a specific plan. Enroll group pension plan participants. End users enroll new group pension plan participants in the Participants view tab. Record beneficiary information. End users record beneficiary information for plan participants in the Beneficiary view tab. Create activities and notes associated with a group pension plan.
For more information on defining funding vehicles, see Defining Group Pension Products on page 77.
To view the funds and investments available within a group pension plan 1 2 3
Navigate to the Group Pensions screen, then the Group Pension List view. In the Group Pensions list, select a group pension plan, and drill down on the plan # link. Click the Funding Vehicles view tab.
Adding Eligible Plan Memebers

Use the following procedure to add eligible plan members.
To add eligible plan members 1 2 3 4

Navigate to the Group Pensions screen, then the Group Pension List view. In the Group Pensions list, select a group pension plan, and drill down on the plan # link. Click the Eligible Members view tab. In the Participants list, add a record and complete the necessary fields.
Creating a Service Request Associated with a Group Pension Plan

Use the following procedure to create a service request associated with a group pension plan.
To create a service request associated with a group pension plan 1 2 3 4 5

Navigate to the Group Pensions screen, then the Group Pension List view. In the Group Pensions list, select a group pension plan, and drill down on the plan # link. Click the Service Requests view tab. In the Service Requests list, add a record and complete the necessary fields. To add further information about the service request, drill down on the SR # link.
81
Enrolling New Participants in a Group Pension Plan

Use the following procedure to enroll new participants in a group pension plan.
To enroll new participants in a group pension plan 1 2 3 4

Navigate to the Group Pensions screen, then the Group Pension List view. In the Group Pensions list, select a group pension plan, and drill down on the plan # link. Click the Participants view tab. In the Participants list, add a record and complete the necessary fields. NOTE: In order for Siebel Insurance to automatically populate the Employer Match % field in the Participants view tab, you must enter a value in the Class field.
In the Allocations form, add a record for each fund or investment option. Select the appropriate funds and investments options from the Pick Funding Vehicle list.
Recording Participant Beneficiary Information

Use the following procedure to record participant beneficiary information.
To record participant beneficiary information 1 2 3 4 5

Navigate to the Group Pensions screen, then the Group Pension List view. In the Group Pensions list, select a group pension plan, and drill down on the plan # link. Click the Beneficiary view tab. In the Participants list, select a participant. In the Beneficiary list, add a record and complete the necessary fields. NOTE: Make sure all the values entered in the % field equal 100%. For more information on adding participants, see Defining Group Pension Plans on page 78.
Creating an Activity Associated with a Group Pension Plan

Use the following procedure to create an activity associated with a group pension plan.
To create an activity associated with a group pension plan 1 2 3 4

Navigate to the Group Pensions screen, then the Group Pension List view. In the Group Pensions list, select a group pension plan, and drill down on the plan # link. Click the Activities view tab. In the Activities list, add a record and complete the necessary fields.
82
Creating a Note Associated with a Group Pension Plan

Use the following procedure to create a note associated with a group pension plan.
To create a note associated with a group pension plan 1 2 3 4

Navigate to the Group Pensions screen, then the Group Pension List view. In the Group Pensions list, select a group pension plan, and drill down on the plan # link. Click the Notes view tab. In the Notes list, add a record and complete the necessary fields.
83
84
Managing Auto Policies
This chapter describes how to manange auto polices. It includes the following topics: About Managing Auto Policies on page 85 Scenario for Managing Auto Policies on page 85 Process of Managing Auto Policies on page 86 Adding Auto Coverages and Coverage Values on page 87 Providing Quotes on page 87 Adding Discounts on page 88 Adding Vehicles or Drivers to Policies on page 89 Setting Up Payment Plans on page 89 Adding Underwriting Information on page 89 Ordering Underwriting Reports on page 90
About Managing Auto Policies

In Siebel Insurance, a quote is a policy that has not been issued. An automobile insurance policy quote has one or more insured drivers, one or more insured vehicles, and one set of coverages for those vehicles and drivers. Each variation of these rating and risk evaluation (underwriting) variables is represented in Siebel Insurance by a separate quote. Because a new quote is generated for each combination of variables that a customer inquires about, multiple quotes typically are generated for customers before they choose and purchase a policy. The Auto Policies screen allows end users to create and manage automobile insurance policies. End users can issue a quote for a new policy or for a change in an existing policy. Administrators can add auto coverage and coverage values in the Insurance Administration views. For more information on views common to all policy screens, see Common Policy Views on page 160.
Scenario for Managing Auto Policies

This scenario features sample tasks performed by a licensed sales representative. Your company might follow a different workflow according to its business requirements. In this scenario, a licensed sales representative for an auto insurance company is on the phone with a prospective customer.
85
Managing Auto Policies Process of Managing Auto Policies
She uses the Quick Quote view to prompt the customer for enough information to provide an initial quote. Then, she adds underwriting information and runs an underwriting report to obtain the rest of the information she needs. Next, she enters information about vehicle coverages and value. Then she adds adjustments for policy discounts and feeds the revised data into the external rating calculator to view the resulting premiums. She gives the prospect a verbal quote and ends the conversation. The next day, she receives an email message that the prospect has called back and will probably purchase a policy, but requires a new quote with a $250 deductible instead of $100. During the second call, the prospect confirms the intent to purchase the quoted policy. The quote now needs to be prepared for eventual contract issuance. This includes collecting information about any parties that hold liens against the insured vehicles and determining billing and payment arrangements. The sales representative follows the procedures implemented by her company to submit the policy for issuance and billing. In this scenario, end users are the sales representatives who manage auto policy information. They enter information to: Provide auto insurance policy quotes Add underwriting information Order underwriting reports Add the appropriate discounts Add vehicles or drivers to a policy Set up payment plans
Process of Managing Auto Policies

This section details sample tasks often performed by administrators and end-users when managing auto policies. Your company might follow a different process according to its business requirements.
The following administrator procedure is described in this section: Adding Auto Coverages and Coverage Values on page 87
NOTE: Only those users with the required administrative responsibilities, such as Siebel administrators, can change entries in the Insurance Administration screen.
End-User Procedures
The following list shows a task end users typically perform when managing auto policies: Providing Quotes on page 87
86
Managing Auto Policies Adding Auto Coverages and Coverage Values
Adding Underwriting Information on page 89 Ordering Underwriting Reports on page 90 Adding Discounts on page 88 Adding Vehicles or Drivers to Policies on page 89 Setting Up Payment Plans on page 89
Adding Auto Coverages and Coverage Values

The Administration - Insurance view allows you to add and make changes to auto coverages, driver coverages, and auto coverage values. You can use the existing fields to define the default limits and deductibles of auto coverages, or you can add more fields using Siebel Tools. For more information, see Configuring Siebel Business Applications.
To add an auto coverage and coverage value 1 2

Navigate to the Site Map, Administration - Insurance, then Auto Coverages. In the Coverage Administration list, add a record and complete the necessary fields. NOTE: If you leave the Vehicle Type field as null, the coverage can be used for driver coverage. If you select Private passenger vehicle in the Vehicle Type field, the coverage can be used for auto coverage.
3 4
Scroll down to the Coverage Values list. In the Coverage Value list, add a record and complete the necessary fields.
Providing Quotes
In Siebel Insurance, a quote is a policy that has not been issued. End users can provide a quote for a new policy or for a change to an existing policy. The Quick Quote view provides a faster way to gather basic policy and rating information. The information collected through the Quick Quote view represents the minimum rating information needed to create an initial premium estimate.
To provide an auto insurance policy quote 1 2 3 4 5 6

Navigate to the Auto Policies screen. Create a new policy, or select an existing policy, and drill down on the policy #. Click the Quick Quote view tab. In the Vehicles list, add a record and complete the necessary fields. In the Drivers list, add a record. In the Add Drivers dialog box, perform one of the following tasks:
87
Managing Auto Policies Adding Discounts
To choose an existing record, select a record and click OK. To add a new record, click New and complete the fields.
NOTE: When you add a driver with a Primary designation, the application automatically populates the Primary field in the Policy/Quote form.
Click the Rate Model view tab. Coverages might be defaulted to a standard set (through configuration) or manipulated through the Rate Model view to further refine the quote. You can collect additional data to aid in the underwriting and administration of the quote.
In the Vehicle Coverages list, add a record and select coverages and values. NOTE: You can manually add premium amounts or configure your Siebel application to add a Rate button that activates the software program your company uses to rate policies.
End users can view a summary of all vehicles, coverages, and premiums associated with a policy in the Multi Vehicle Rate Model view tab. The information that appears on this view is a different presentation of information entered in the Rate Model view.
Viewing a Summary of All Vehicles, Coverages, and Premiums Associated with a Policy
Use the following procedure to view a summary of all vehicles, coverages, and premiums associated with a policy.
To view a summary of all vehicles, coverages, and premiums associated with a policy 1 2 3
Navigate to the Auto Policies screen. In the Policies/Quotes list, drill down on the desired policy. Click the Multi Vehicle Rate Model view tab.

Click Next Vehicle Set to view additional vehicles that do not display. Click Prior Vehicle Set to return the previous view.
Adding Discounts
After end users create a quote or policy, they can add policy, driver, and vehicle discounts to the policy.
To add a discount 1 2 3 4
Navigate to the Auto Policies screen. In the Policies/Quotes list, drill down on the desired policy. Click the Discounts view tab. In the appropriate list, add a record and complete the necessary fields:
88
Managing Auto Policies Adding Vehicles or Drivers to Policies
Policy Discounts. To add policy discounts such as long-term customer discounts. Driver Discounts. To add driver discounts such as good driver discounts. Vehicle Discounts. To add vehicle discounts such as anti-theft discounts.
Adding Vehicles or Drivers to Policies

End users can add vehicles or drivers to existing policies.
To add a vehicle or driver to a policy 1 2 3 4 5

Navigate to the Auto Policies screen. In the Policies/Quotes list, drill down on the desired policy. Click the Quick Quote view tab. To add a driver, scroll down to the Drivers list, add a record, and complete the necessary fields. To add a vehicle, scroll down to the Vehicles list, add a record, and complete the necessary fields.
Setting Up Payment Plans

End users can set up payment plans, including details about payment methods, for auto insurance policies.
To set up a payment plan for an auto policy 1 2 3 4

Navigate to the Auto Policies screen. In the Policies/Quotes list, drill down on the desired policy. Click the Payment Plans view tab. In the Payment Plans list, add a record and complete the necessary fields.
Adding Underwriting Information

After end users provide a quote or accept an application for an auto policy, they can add information for use in ordering underwriting reports for the drivers and vehicles associated with the policy.
To add underwriting information 1 2 3

Navigate to the Auto Policies screen. In the Policies/Quotes list, drill down on the desired policy. Click the appropriate view tab:
89
Managing Auto Policies Ordering Underwriting Reports
Underwriting. To query for prior insurance history and to add prior insurance history, prior claims, or residence information. Accidents/Violations. Use the Accidents/Violations list to add information about each drivers accidents and violations. NOTE: The lists and forms that appear depend on the type of vehicle you select.
Add a record in the selected list or form and complete the necessary fields.
Ordering Underwriting Reports

After end users add the necessary policy, driver, or vehicle information, they can order underwriting reports for a policy. Examples of underwriting reports are motor vehicle, credit bureau, or loss history reports.
To order an underwriting report 1 2 3 4 5

Navigate to the Auto Policies screen. In the Policies/Quotes list, drill down on the desired policy. Click the Underwriting Reports view tab. In the Underwriting Reports list, add a record and complete the necessary fields. Use the procedures developed by your company to submit the order. NOTE: You can configure your Siebel application to add an Order button that activates the software program your company uses to submit orders for underwriting reports.
90
10 Managing Claims
This chapter is about managing claims in Siebel Insurance. It contains the following topics: About Managing Claims on page 92 Scenario for Opening and Managing a Claim for Property Loss on page 94 Scenario for Opening and Managing a Claim for Auto Damage on page 94 Process of Managing Claims on page 95 About Siebel Insurance eService Claims Center Locators on page 97 Setting up Siebel Insurance eService Claims Center Locators on page 97 Activating the Workflow Processes on page 99 Administering Reserve Codes on page 99 Administering Loss Codes on page 100 Administering Adjusters Financial Limits on page 101 Administering the Employee Hierarchy on page 102 Integrating with the Insurance Services Office (ISO) on page 103 Integrating with the Office of Foreign Assets Control on page 105 Checking the Policy Validity and Coverage (End User) on page 106 Creating First Notices of Loss (End User) on page 106 Recording Details of Involved Parties (End User) on page 107 Recording Insured and Adverse Claimant Property Details (End User) on page 108 Managing Claims Events (End User) on page 109 Assigning a Claim to an Adjuster (End User) on page 110 Checking a Claim Against the ISO Database (End User) on page 110 Creating an Activity Plan (End User) on page 113 Assigning a Claim Element (End User) on page 113 Assigning Claims to a Specialist Unit (End User) on page 114 Adding an Appraisal (End User) on page 115 Attaching Claims Documentation (End User) on page 116 Tracking Police and Fire Reports (End User) on page 116 About Coverages and Reserves on page 117 Creating a Reserve (End User) on page 117
91
Managing Claims About Managing Claims
About Managing Reserves on page 119 Managing Reserves (End User) on page 122 Tracking Demands for Payment (End User) on page 124 Creating an Invoice Record (End User) on page 124 Generating a Payment Record (End User) on page 125 Tracking Payments Related to Invoices (End User) on page 125 About Issuing a Settlement Payment (End User) on page 126 Issuing a Settlement Payment (End User) on page 131 Making a Bulk Payment (End User) on page 131 Viewing the Invoices and Claims for a Payment (End User) on page 132 Managing Recovery Information (End User) on page 132 Creating a Recovery Payment Record (End User) on page 138 Managing Fraud Information (End User) on page 138 About the Business Rules Processor and Claims Logic on page 142 Claims Workflows on page 145
About Managing Claims

Siebel Personal Lines Claims allows agents, call center representatives, and claims adjusters to capture notice of loss information, to view claim information and activities, and to link claims to customer and policy information. Incident and claim information is used across multiple business units including claims, policy servicing, sales, and underwriting, presenting an integrated view of the customer. Claims management is an important part of service interactions with insurance companies. Therefore, Siebel claims management can be integrated with other software components, such as legacy claims management systems, to provide an integrated solution. End users can use the Claims screen to open and track claims, as well as to track service requests and other activities associated with claims. The overall process of managing a claim might involve the following: Claims intake and First Notice of Loss (FNOL). A call center agent creates a First Notice of Loss, records the necessary details from the policy holder, and then assigns the claim to a claims adjuster. Review and assignment. A claims adjuster reviews the claim and assigns parts of the claim to other people or third parties. For example, the adjuster can assign an appraiser to appraise the damage, or can assign claim elements to third-party vendors, such as glass vendors. Reserve and adjustment. The claims adjuster creates a reserve with which the claim payment will be made.
92
Managing Claims About Managing Claims
Settlement. The adjuster makes the necessary payment to the policy holder to settle the claim. Special unit investigation. Throughout the claims process, an adjuster can assign the claim to a special unit, such as a subrogation or fraud unit. An investigator in the special unit then processes the claim.
Insurance Claims Terminology

The following definitions are useful in understanding Siebel Claims: Appraisal. A survey to determine a property's insurable value, or the amount of a loss. Arbitration. The procedure in which an insurance company and the insured or a vendor agree to settle a claims dispute by accepting a decision made by a third party. Bodily injury liability coverage. The portion of an auto insurance policy that covers the injuries that the policyholder causes to someone else. Catastrophe. A single incident or a series of closely related incidents causing severe, insured property losses, totaling more than a given amount, which is currently $25 million. Comprehensive coverage. The portion of an auto insurance policy that covers damage to the policyholder's car not involving a collision with another car (including damage from fire, explosions, earthquakes, floods, and riots), and theft. Deductible. The amount of loss paid by the policy holder. Either a specified dollar amount, a percentage of the claim amount, or a specified amount of time that must elapse before benefits are paid. First-party coverage. Coverage for the policyholder's own property or person. In no-fault auto insurance, first-party coverage pays for the cost of injuries. In no-fault states with the broadest coverage, the personal injury protection (PIP) part of the policy pays for medical care, lost income, funeral expenses and, where the injured person is not able to provide services such as child care, for substitute services. Fraud. Intentional lying or concealment by policyholders to obtain payment of an insurance claim that would otherwise not be paid, or lying or misrepresentation by the insurance company managers, employees, agents, and brokers for financial gain. Loss costs. The portion of an insurance rate used to cover claims and the costs of adjusting claims. Insurance companies typically determine their rates by estimating their future loss costs and adding a provision for expenses, profit, and contingencies. No fault insurance. An auto insurance system that both requires drivers to carry insurance for their own protection, and which places limitations on their ability to sue other drivers for damages. Subrogation. The legal process by which an insurance company, after paying a loss, seeks to recover the amount of the loss from another party who is legally liable for it. Salvage. The damaged property an insurer takes over to reduce its loss after paying a claim. Insurers receive salvage rights over property on which they have paid claims, such as badly damaged cars.
93
Managing Claims Scenario for Opening and Managing a Claim for Property Loss
Scenario for Opening and Managing a Claim for Property Loss

This scenario features sample tasks performed by a claims representative. Your company might follow a different workflow according to its business requirements. A claims representative for a property insurance company is on the phone with a policy holder whose home was burgled. The claims representative must first check that the policy holder has a valid policy and that there is appropriate coverage. To report this first notice of loss, the representative opens a claims file in Siebel Insurance by navigating to the Claims screen and creating a new Claims record. The claims representative enters the loss date and selects a Policy effective at the time of loss. The representative then moves on to the Loss Description view to capture additional details about the burglary. Next, he creates a detailed list of the lost insured items in the Insured Property view. Then, he uses the Police And Fire Reports view to initiate an order for a policy report on the burglary. Because heirloom jewelry was among the property that was stolen, he goes to the Appraisals view to document the value of the stolen property. Finally, he documents the coverages for the lost items. During the next few weeks, he uses other views to track the adjustment process, including reserving and recoveries (subrogation or salvage). After the claim is settled, he adds payment details. In this scenario, the end users are claims representatives. They enter information to: Create a loss claim and record details about it Associate the loss with a contact Create a list, record the worth, and the coverages for the lost insured items Record any police or fire reports, if applicable Track the adjustment process and record payment details
Scenario for Opening and Managing a Claim for Auto Damage

This scenario features sample tasks performed by call center agents and claims adjusters. Your company might follow a different workflow according to its business requirements. A call center agent for an insurance company is on the phone with a policy holder whose car was damaged in a road traffic accident. The call center agent must first check that the policy holder has a valid policy and that there is appropriate coverage. To report the first notice of loss, the call center agent opens a claims file in Siebel Insurance by navigating to the Claims screen and creating a new Claims record. She enters the loss date and selects a policy that was effective at the time of the loss. She then moves to the Loss Description view to capture some details about the damage to the vehicle and whether there were injuries or fatalities.
94
Managing Claims Process of Managing Claims
The call center agent navigates to the Involved Parties view to capture the contact and account information. She then goes to the Insured Property view to capture more information about the damaged vehicle and the damage that occurred. The call center agent assigns the claim to an adjuster who then reviews the claim and assigns part of the claim to other people or third parties as necessary. As part of the evaluation, the adjuster navigates to the ISO Database Search view to check whether the policy holder has already made a claim for the same vehicle with another insurance company. The adjuster creates an activities plan based on the appropriate loss code in the Activities Plan view, then assigns an activity to a particular appraiser who appraises the damage. The adjuster creates claim elements and assigns them as necessary to third-party vendors, such as a repair shop to fix the damage, or a glass vendor to replace the car windshield. The next step is to set up a reserve, which is a set amount of money that the insurer puts aside to make a claims payment. The adjuster navigates to the Loss Details - Auto view and creates reserves for the coverages that apply to the policy. He then navigates to the Reserves view and opens the reserves. In due course, the adjuster receives the invoices associated with the claim and creates a record for each invoice in the Claims screen, then the Invoices view. In the Claims screen, then the Invoices view, he clicks the Generate Payment button to create a payment record for the invoices. The adjuster navigates to the Payments view and clicks the Submit Payment button to make the necessary payment and settle the claim. Throughout the claims process, an adjuster can assign the claim to a specialist unit such as a subrogation unit or a fraud unit. The specialist unit then processes the claim in their area. In this scenario, the end users are call center agents and claims adjusters. They enter information to: Check that the claimant has a valid policy with the appropriate coverage Create a loss claim and record details about it Associate the loss with a contact and account Record details about the damage to the vehicle Check whether the claimant has filed a similar claim with another insurance company Create an activities plan and assign activities to appraisers Assign claim elements to appropriate third-party vendors Create and open reserves Record invoice details Generate and submit payments
Process of Managing Claims

This topic details tasks performed by administrators and end users when managing claims. Your company might follow a different process according to its business requirements.
95
Managing Claims Process of Managing Claims
Administrator Procedures for Managing Claims

The following list shows tasks administrators typically perform to manage claims: Setting up Siebel Insurance eService Claims Center Locators on page 97 Administering Reserve Codes on page 99 Administering Loss Codes on page 100 Administering Adjusters Financial Limits on page 101 Administering the Employee Hierarchy on page 102 Integrating with the Insurance Services Office (ISO) on page 103 Integrating with the Office of Foreign Assets Control on page 105
End-User Procedures for Managing Claims

The following list shows tasks call center agents typically perform to create the First Notice of Loss (FNOL): Checking the Policy Validity and Coverage (End User) on page 106 Creating First Notices of Loss (End User) on page 106 Recording Details of Involved Parties (End User) on page 107 Recording Insured and Adverse Claimant Property Details (End User) on page 108 Managing Claims Events (End User) on page 109 Assigning a Claim to an Adjuster (End User) on page 110
The following list shows tasks claims adjusters typically perform to review and assign claims: Checking a Claim Against the ISO Database (End User) on page 110 Creating an Activity Plan (End User) on page 113 Assigning a Claim Element (End User) on page 113 Assigning Claims to a Specialist Unit (End User) on page 114 Adding an Appraisal (End User) on page 115 Attaching Claims Documentation (End User) on page 116 Tracking Police and Fire Reports (End User) on page 116
The following list shows tasks claims adjusters typically perform to create reserves and adjust claims: About Coverages and Reserves on page 117 Creating a Reserve (End User) on page 117 Managing Reserves (End User) on page 122
The following list shows tasks claims adjusters typically perform to settle claims:
96
Managing Claims About Siebel Insurance eService Claims Center Locators
Creating an Invoice Record (End User) on page 124 Generating a Payment Record (End User) on page 125 Tracking Payments Related to Invoices (End User) on page 125 About Issuing a Settlement Payment (End User) on page 126 Issuing a Settlement Payment (End User) on page 131 Making a Bulk Payment (End User) on page 131 Viewing the Invoices and Claims for a Payment (End User) on page 132
The following list shows tasks special unit investigators typically perform to investigate claims: Managing Recovery Information (End User) on page 132 Creating a Recovery Payment Record (End User) on page 138 Managing Fraud Information (End User) on page 138
About Siebel Insurance eService Claims Center Locators

The Contact Us applet on the Siebel Insurance eService home page has a Locate Nearby Claims Centers hyperlink. When users with the role of Insurance Member click this link, an applet opens in which they can perform a parametric search using location attributes that they select from dropdown lists. For more information on Siebel Insurance eService, see Siebel eService Administration Guide Addendum for Industry Applications.
Setting up Siebel Insurance eService Claims Center Locators

This task is a step in Process of Managing Claims on page 95. To set up Claims Centers Locator functionality, administrators must complete the following tasks: Import the geocode data for their region Enter claim center locations Assign longitudes and latitudes to claim center locations
Geocode Data
The geocode data is used to reference your region. Geocode data for the U.S. geographical region is included in every licensed copy of Siebel Insurance. For information on importing geocode data, see Siebel eService Administration Guide.
97
Managing Claims Setting up Siebel Insurance eService Claims Center Locators
Entering Claim Center Location

The claim center information is matched with locations entered by end users when they perform a search to locate a branch. Administrators can use the Sites screen to enter claim center location information.
To enter claim center location information 1 2 3

Navigate to the Site Map, Administration - Marketing, and then Sites. In the Sites list, add a record. In the Sites form:
a b c d 4 5
In the Name field, enter the name of this claim center. In the Type field, select Claim Center. In the Address field, enter the address for this claim center. Complete the necessary fields.
To add a service for a site, scroll down to the Site Services list, add a record and complete the necessary fields. To add hours of operation, add a record in the Hours Of Operation list, and complete the necessary fields.
Assign a Longitude and a Latitude

The Siebel Insurance Claim Center Locator searches for claim centers using latitude and longitude. If you do not know the latitude and longitude, leave those fields blank. If the City, State, Zip Code, and Country fields are correct, the latitude and longitude values are automatically generated when you save the record. NOTE: The latitude and longitude values will not generate if any one value in the City, State, Zip Code, or Country fields is incorrect. For example, if the ZIP Code is incorrect, you will receive an error message. To correct this problem, navigate to the Application Administration, ZIP Code Administration view and make sure the Geo values for that city, state, and ZIP Code combination has been loaded. For more information, see Siebel eService Administration Guide.
To add a new center to the Claim Center Locator 1 2 3 4

Navigate to the Site Map, Administration - Application, and then Branch Locator. In the More Info form, add a record and complete the necessary fields. In the Name field, enter a name for the branch. In the Division field, select a site. For more information on adding a site, see Entering Claim Center Location on page 98. When the record is saved, the application automatically populates the Latitude and Longitude fields.
98
Managing Claims Activating the Workflow Processes
Activating the Workflow Processes

Siebel Claims uses many workflows processes, which, for example, are activated when a user clicks a particular button such as the Submit Payment button. You must activate these workflow processes before the user can use Siebel Claims. For more information about the workflow processes, see Claims Workflows on page 145.
To activate the workflow processes 1 2

Navigate to the Administration - Business Process screen, then the Workflow Deployment view. In the Repository Workflow Processes list, use a query to find all processes where the Name field contains the word claims. NOTE: You can query on *Claims*.
Activate each workflow process that has a status of Inactive:
a b
Select the workflow process record. Click Activate.
The workflow processes are activated.
Administering Reserve Codes

You can define a reserve code for a particular reserve to determine how the reserve value is calculated. You can determine whether the reserve has a default value and whether that default value can be overridden. You use the reserve code in the Administration - Insurance screen, then the Loss Codes view as well as in the Loss Details - Auto, Loss Details - Property, and Reserves views in the Claims screen. This task is a step in Process of Managing Claims on page 95.
To add a reserve code 1

Navigate to the Administration - Insurance screen, then the Reserve Codes view.
99
Managing Claims Administering Loss Codes
In the Reserve Code Administration list, create a new record, and complete the fields. Some fields are described in the following table. Field Code Type Comments Enter a code. Select the type of reserve: Manual. The value is set at the time of creating the reserve code by the adjuster. Factor. The reserve has a default value. Calculated. The reserve value is computed in real-time by a business service. NOTE: The customer must develop this business service during implementation. Factor Value Allow Override? Enter the default value for a reserve of type Factor. The reserve will have this value when it is opened. Whether the adjuster can override a default reserve value.
Administering Loss Codes

You can define a loss code for a particular type of loss and associate a default activity plan template and default coverages with that loss code. You use the activity plan association in the Claims screen, then the Activity Plans view. When the user enters a loss code and clicks the Default Plan button, the default activity plan for the loss code is created. The default coverage association is used in the Claims screen, then the Loss Details - Auto and Loss Details - Property views to populate these views with default coverage data. From these views, the user can create appropriate reserves for each coverage. This task is a step in Process of Managing Claims on page 95.
To add a loss code 1 2

Navigate to the Administration - Insurance screen, then the Loss Codes view. In the Loss Code Administration list, create a new record, and complete the necessary fields. Some fields are described in the following table. Field Code Comments Enter a loss code.
100
Managing Claims Administering Adjusters Financial Limits
Field LOB Active?
Comments Select the line of business associated with the loss code: Auto or Property. Whether the loss code is active.
In the Activity Plans list, add a record for the default activity plan for the loss code, and complete the Template and Description fields. You must set up the activity plan in the Administration - Data screen, then the Activity Templates view.
In the Coverages list, add records for the required coverages, and complete the fields. The coverages created in this coverages list are used to recommend the reserves to open for the particular loss code. Some fields are described in the following table. Field Coverage Rate State Type Reserve Code Comments Select the coverage. Displays the rate state. Displays the type of coverage. Select the reserve code associated with the coverage.
Administering Adjusters Financial Limits

You can set financial limits for adjusters on both the reserves level and on the claims level. You can set reserve and payment limits for each reserve code, and you can also set total reserve and total payment limits for a claim for the employee. Reserve and payment limits are checked when the user clicks the Open Reserve button (in the Reserves view) and the Submit Payment button (in the Payments view) respectively. For more information, see Managing Reserves (End User) on page 122 and About Issuing a Settlement Payment (End User) on page 126. This task is a step in Process of Managing Claims on page 95.
To set the adjusters financial limits 1 2 3

Navigate to the Administration - User screen, then the Employees view. Select an employee record. In the Employees list, enter the required values for:
Total Reserves. The total reserve amount available to the employee for a claim.
10 1
Managing Claims Administering the Employee Hierarchy
Total Payments. The total payment amount available to the employee for a claim.
4 5
Click the Claims Reserve Limits view tab. For each reserve code, enter the required values for:

Reserve Limit. The maximum value of reserve available to the employee for this reserve type. Payment Limit. The maximum payment value available to the employee for this reserve type.
Administering the Employee Hierarchy

When an adjuster clicks the Open Reserve button (in the Reserves view) and the Submit Payment button (in the Payments view), Siebel Insurance checks the reserve or payment limit for the coverage as well as for the total claim. If the limit is not enough, the adjusters supervisor is prompted to approve the reserve or payment. It is therefore necessary to set the employee hierarchy to determine the supervisor for each adjuster. You set the employee hierarchy in the Administration Group screen, then the Position view. For more information, see Siebel Applications Administration Guide. NOTE: You must set the employee and supervisor as the primary for that position. This task is a step in Process of Managing Claims on page 95.
Example of Setting up the Employee Hierarchy

This topic gives one example of setting up the employee hierarchy for approval of claims payments or reserves. You might use this feature differently, depending on your business model. You have two employees Chacko and Chandra and you want to set up Chandra as the manager of Chacko using the positions Position1 and Position2. You must set up Position2 as the parent position of Parent1.
To set up the employee hierarchy 1 2 3 4

Navigate to the Administration Group screen, then the Position view. In the Parent Position field, set Position2 as the parent position of Position1. Select the record for Position1 and enter Chacko in the Last Name field. Select the record for Position2 and enter Chandra in the Last Name field. Now if Chacko is an adjuster, and he tries to open a reserve that is over his limit, it is sent for approval to Chandra.
102
Managing Claims Integrating with the Insurance Services Office (ISO)
Integrating with the Insurance Services Office (ISO)

The ISO ClaimSearch database is an insurance fraud detection system owned by the Insurance Services Office (ISO), an organization that operates only in the U.S. ISO is one of the largest private databases in the world. It contains detailed records of insurance premiums collected and losses paid from participating insurers. Insurance companies can become a member of ISO and they can send claims information to ISO to check whether similar claims have been filed with other insurance companies. End users use the ISO Database Search view to check whether a similar claim has been filed by the claimant with another insurance company. This task is a step in Process of Managing Claims on page 95. Before an insurance company can integrate with the ISO, it must be an ISO member and pay the associated fees. The steps involved in integrating with the ISO include: Setting the ISO System Preferences on page 103 Checking the ISO Run-Time Event on page 104 Checking the Validation Rules on page 104 Creating the Named Subsystem for the ISO Search Response on page 104 Configuring the ISO Assigned Company ID on page 105
Setting the ISO System Preferences

You must configure the System Preferences shown in Table 3 using the Administration Application screen. The values are available as seed data, but you must make sure that the ISO Connection Info, ISO CustLogInId, and ISO Pswd system preferences have the appropriate values assigned for the insurance provider.
Table 3.
ISO System Preferences System Preference Value Client Application Name. The is XML_TEST for ISO ClaimSearch US customers. Client Application Version. The value is 1.0 for ISO ClaimSearch U.S. customers. ISO Application URL. Customer Login ID. The ISO assigns a unique user ID to each customer. Clear text Password. The ISO assigns the password.
System Preference Name ISO ClientAppName ISO ClientAppVersion ISO Connection Info ISO CustLogInId ISO Pswd
10 3
Managing Claims Integrating with the Insurance Services Office (ISO)
For more information about setting system preferences, see the chapter that discusses ongoing administrative tasks in Siebel Applications Administration Guide.
Checking the ISO Run-Time Event

You must verify the configuration of the run-time event that invokes the ISO Search Request workflow. You do this through the Administration Runtime Events screen. Table 4 shows the data for the run-time event and the associated action set, ISO Integration. This data is available as seed data in the Siebel repository. Table 4. ISO Run-Time Event Data Object Type BusComp Object Name INS Claims ISO Search Event InvokeMethod Subevent EventMethod Submit Action Set Name ISO Integration
Sequence 1
Checking the Validation Rules

The Validation Rule Set named INS Claims ISO Integration Validation specifies the validation rules that need to be applied before an ISO search request is submitted. You can verify the configured rule set through the Administration Data Validation screen. The validation rule checks that some of the mandatory fields for the ISO search exist in the Claim record. The fields are Company Id, Policy Number, and Loss Date. The validation rule is available as seed data in the Siebel repository. This rule is invoked as one of the initial steps in the FINS Claims ISO Search Request Workflow. The administrator has to make sure that the validation rule is present in the system.
Creating the Named Subsystem for the ISO Search Response

The Siebel system administrator must create a Named Subsystem called ProcessISOResponse and configure it with the inbound workflow, FINS Claims ISO Search Response. This is required for handling the results sent back by ISO after an ISO Database Search request is submitted. For more information about creating a Named Subsystem, see Siebel System Administration Guide.
To create and configure the Named Subsystem 1 2

Start the Siebel Gateway Name Server and Siebel Server. At a DOS prompt start the Siebel Server Manager (srvrmgr) and verify that the Siebel Server is running.
104
Managing Claims Integrating with the Office of Foreign Assets Control
Enter the following Siebel Server Manager command: create named subsystem ProcessISOResponse for subsystem EAITransportDataHandlingSubsys with DispatchWorkflowProcess="FINS Claims ISO Search Response", DispatchMethod=RunProcess
4 5
Connect to the Gateway Name Server using nsbrowse, and verify that the Named Subsystem is created correctly. In the eai.cfg file in the \siebel\bin\w32ud\enu directory, add the following entry. [HTTP Services] ProcessISOResponse=ProcessISOResponse
6 7
Enable the EAI component group. Restart the Siebel Gateway Name Server and the Siebel Server.
Configuring the ISO Assigned Company ID

The ISO assigns unique company identifiers to member insurance companies. One company can have multiple IDs for different offices or divisions. The IDs are used during ISO database searches to check whether the company is an ISO member. The Siebel system administrator must associate the ISO-assigned company ID with the Internal Division to which a user who performs an ISO database search belongs.
To configure the ISO-assigned company ID 1 2 3 4

Navigate to the Administration Group screen, then the Internal Divisions view. Select the Internal Division to which the employee belongs, or create a new Internal Division record as required. In the Internal Division List applet, or Internal Division Entry applet, enter the ISO-assigned company ID in the Company ID field. Save the record.
Integrating with the Office of Foreign Assets Control

The Office of Foreign Assets Control (OFAC) administers and enforces economic sanctions programs primarily against countries and groups of individuals, such as terrorists and narcotics traffickers. Siebel Insurance allows you to check claims payees against a blacklist of individuals and organizations provided by OFAC. The blacklist is stored in the Siebel database and you must keep it up to date by importing data from an XML file, sdn.xml that you obtain from the OFAC site:
10 5
Managing Claims Checking the Policy Validity and Coverage (End User)
http://www.treasury.gov/offices/enforcement/ofac/sdn/sdn.xml. You can schedule the FINS Claims OFAC Data Import Process workflow on a monthly basis to process the XML file and import the OFAC data. The FINS Claims OFAC Data Import Process workflow has a process property for the Input File. You can set the default string of this process property to C:\TEMP\OFAC_SDN.xml, or whatever location you require. TIP: Run the workflow after work hours to update the Siebel data; this minimizes the performance impact. This task is a step in Process of Managing Claims on page 95.
Checking the Policy Validity and Coverage (End User)

When a call center agent receives a call about a claim, she must check that there is a valid policy associated with the claim and that there is appropriate coverage. This task is a step in Process of Managing Claims on page 95.
To check policy validity 1 2 3 4 5

Navigate to the Contacts screen. Search for the contact. Drill down on the contact. In the Summary view, select the appropriate policy. Drill down on the policy and check whether:

The contact has a valid policy. The contact has the right sort of coverage for the claim, for example, for an auto policy, the right coverage for driver and vehicle. Claims are already associated with the policy.
Creating First Notices of Loss (End User)

When end users create a first notice of loss, they add basic loss information and link a policy to the loss. This task is a step in Process of Managing Claims on page 95.
To create a first notice of loss 1

Navigate to the Claims screen.
106
Managing Claims Recording Details of Involved Parties (End User)
2 3 4 5
In the Claims list, add a record, and complete the necessary fields. Drill down on the Claim # hyperlink. Click the Loss Details, then the Loss Description view tab. In the Claim Loss Description form, complete the necessary fields.
Recording Details of Involved Parties (End User)

As part of the first notice of loss process, a call center agent must record details of all parties involved in the claim. An involved party can be a contact or an organization. In the Involved Parties view, end users can see the relationship of all accounts and contacts related to the claim. Each account and contact can have multiple roles. For example, a single party can be both the insured and the claimant; that is, insured with their own policy and a third party claimant on the other party's policy. As another example, a service provider can be the insured, claimant, or a witness. In both the Contacts and Accounts forms, the On Behalf field records details of names and endorsement roles for the purpose of making payments. Because of legal requirements, it is necessary to capture all names and relationship correctly. Table 5 shows some examples of endorsement roles.
Table 5.
Contact Details and Endorsement Roles Endorsement Role Attorney for Guardian of Claim Contacts Todd Smith and Lisa Myers Sandra Oh
Contact Payee Bill Franklin Lisa Powers
In the examples in the table, the insurance company is making a single claims payment to Bill Franklin who is the attorney for Todd Smith and Lisa Myers and to Lisa Powers who is a guardian of Sandra Oh. In the first example, the end user must: Create three contact names: Bill Franklin, Todd Smith, and Lisa Myers. In the record for Bill Franklin, select Todd Smith and Lisa Myers in the On Behalf field. Siebel Insurance concatenates the names in the On Behalf field.
When the adjuster later makes a payment in the Claims, Financials, and then the Payments view, he can select Bill Franklin as payee and Siebel Insurance will already have the information that Bill Franklin is the attorney on behalf of Todd Smith and Lisa Myers. This task is a step in Process of Managing Claims on page 95.
10 7
Managing Claims Recording Insured and Adverse Claimant Property Details (End User)
To associate an involved party with a loss 1 2 3 4

Navigate to the Claims screen. In the Claims list, drill down on the desired claim. Click the Loss Details, then the Involved Parties view tab. If the involved party is a person, add the required details for the contact.
a b 5
If required, enter information in the On Behalf field. If required, select Contact Detail, and enter detailed information for the contact.
If the involved party is an organization, scroll down to the Accounts form, and complete the necessary fields. If required, select Account Detail, and enter detailed information for the account.
Repeat Step 4 through Step 5 for each involved party that you want to add to the claim.
Recording Insured and Adverse Claimant Property Details (End User)

After they have created a claim, end users record details about the property involved in a claim using the following Claims views: Insured Property. Track details about the insured property in a claim. Adverse Claimant Property. Track details about claims or damages filed against the policy holder.
This task is a step in Process of Managing Claims on page 95.
To record insured property information 1 2 3 4 5

Navigate to the Claims screen. In the Claims list, drill down on the desired claim. Click the Loss Details, then the Insured Property view tab. In the Insured Property list, add a record for each insured property involved in the claim. In the Sequence # field, click the select button and select the insured property from the Pick Insured Property dialog box. The type of property selected in the Insured Property list determines whether the application displays the Insured Vehicle Detail form or Insured Property Detail form.
In the Claim Elements # field, select a claim element, if applicable. Many insurance companies break down claims into subcomponents called claim elements. By subdividing claims in this way, insurers can delegate the management of these subcomponents to specific groups within their company according to their business rules. For more information on claim elements, see Assigning a Claim Element (End User) on page 113.
108
Managing Claims Managing Claims Events (End User)
In the form that appears, complete the necessary fields.
Recording Adverse Claimant Property Information

Use the following procedure to record adverse claimant property information.
To record adverse claimant property information 1 2 3 4 5 6

Navigate to the Claims screen. In the Claims list, drill down on a claim. Click the Loss Details, then the Adverse Claimant Property view tab. In the Adverse Claimants list, add a record for each claimant. In the Adverse Claimant Property list, add a record for each property. In the Property Type field, select Auto or Property. The Property Type you select determines whether the application displays the Vehicle Detail or Property Detail form.
In the Claim Elements # field, select a claim element, if applicable. Many insurance companies break down claims into subcomponents called claim elements. By subdividing claims in this way, insurers can delegate the management of these subcomponents to specific groups within their company according to their business rules. For more information on claim elements, see Assigning a Claim Element (End User) on page 113.
In the form that appears, complete the necessary fields.
Managing Claims Events (End User)

There are several circumstances in which a group of claims are associated with one event: Catastrophic events. Events such as tornado or hurricane damage that result in claims under multiple policies. There can be multiple claims for one insured person under different policies. Single loss involving multiple lines of business. Events where a single loss involving an insured person is covered under two different policies; for example, an insured persons vehicle might be broken into and personal property stolen. In this case, the vehicle damage is covered under the auto policy, and the personal property is covered under the homeowner policy. A single incident occurs with the same loss date, description, and so on. Single loss involving multiple people from the same company. Events, where, for example, two people insured with the same company are involved in a traffic accident. This is a single loss involving two insured people, on two separate auto policies. In this case, there are two claims, but a single incident with the same loss date, description, and so on.
The ability to record event details in one place reduces data duplication and the time required to collect claim information. It also provides the ability to track major catastrophic events and incorporate the statistics into risk-rating processes.
10 9
Managing Claims Assigning a Claim to an Adjuster (End User)
End users use the Claims Events screen to record details of claims events and to associate claims with an event. This task is a step in Process of Managing Claims on page 95.
To record details of a claims event 1 2

Navigate to the Claims Events screen. In the Claims Events list, add a record, and complete the necessary fields.
Associating a Claim with a Claims Event

Use the following procedure to associate a claim with a claims event.
To associate a claim with a claims event 1 2 3

Navigate to the Claims Events screen. In the Claims Event list, select the event with which you want to associate the claim or group of claims. In the Claims list applet, add a record or click the Associate button to display a picklist of claims, and select the appropriate claims.
Assigning a Claim to an Adjuster (End User)

There are two ways to assign a claim to an adjuster.
1 2
By entering the adjuster name in the Team field in the Claims header form applet. By using Assignment Manager so that when the Call Center agent changes the status from Notice of loss to Open in the Status field in the Claims header form applet, it initiates an Assignment Manager function to assign the claim to an adjuster. NOTE: This Assignment Manager function is not provided out-of-the-box.
For more information about using Assignment Manager, see Siebel Assignment Manager Administration Guide. This task is a step in Process of Managing Claims on page 95.
Checking a Claim Against the ISO Database (End User)

The ISO ClaimSearch database is an insurance fraud detection system owned by the Insurance Services Office (ISO), a U.S. specific organization. This task is a step in Process of Managing Claims on page 95.
110
Managing Claims Checking a Claim Against the ISO Database (End User)
ISO is one of the largest private databases in the world and it contains detailed records of insurance premiums collected and losses paid from participating insurers. Insurance companies can become a member of ISO and they can send claims information to ISO to check whether similar claims have been filed with other insurance companies. ISO Database search currently handles only Auto (Insured and Adverse Claimant) and Property (Insured only) searches. End users use either the ISO Database Search view or the ISO Database Search Attachments view to check whether a similar claim has been filed by the claimant with another insurance company. The ISO Database Search view displays the search records and, in the Claim Matches list applet, any matching records for that search that are returned by ISO. The ISO Database Search Attachment view also displays the search records, and in the Attachments list applet, displays the actual search responses from ISO as XML data. Clicking the Attachment name opens the XML file in the default editor. The end user can also drill down to this view from the ISO Database Search view, through the Match Details field. The claim data that must be sent to ISO for a database search is shown in Table 6.
Table 6.
Required Data for ISO Database Search Data Required Report Type Insuring Company ID Policy Number Policy Type Claim Number Date of Loss Location of Loss State Loss Type Role in the Claim Business Name (for accounts) First Name (for contacts) Last Name (for contacts Address Information Line 1 City State
Claims and Losses For each claim submitted
For each involved party
For a casualty or third-party property damage loss For first-party property loss
Alleged Injuries or Property Damage Theft items
11 1
Managing Claims Checking a Claim Against the ISO Database (End User)
In the ISO Database Search view, the Report Type field specifies the type of search as follows: Initial Search. Used when a claim is sent to ISO for the first time. The ISO ClaimSearch system writes the claim data to its database and then searches the database for claims that belong to the same claimant. This report type is used only for a first-time search or for resubmitting an initial search that had errors. Replacement. Used to overwrite data sent in the initial search. The data is updated in the database and a new search is performed. To locate the initial claim in the database, the data must include the Insuring Company ID, Claim Number, Policy Number, and Date of Loss.
When the end user submits the search, the information displayed in the ISO database search list applet is shown in Table 7.
Table 7. Field Date
Information Displayed in the ISO Database Search List Applet Comments The date when the search request was submitted. The ID of the person who submitted the request. The status of the request: Pending. The request is being created. Acknowledged. The request has been received by ISO. Error. The search is completed and there are errors. Complete. The search is completed and there are no errors.
Requested by Status
# Matches Error Message
The number of matches returned. Any error messages returned. If the data sent is incomplete, or fields contain invalid data, an error is returned. A link that the end user can drill down on to see the details of matches.
Match Details
To check a claim against the ISO database 1 2 3 4

Navigate to the Claims screen. In the Claims list, drill down on the desired claim. Click the Reports / Documents, then the ISO Database Search view tab. Create a new record.
112
Managing Claims Creating an Activity Plan (End User)
In the Report Type field, select Initial Search or Replacement. NOTE: You can perform a replacement search only if at least one initial search has already been completed for the claim record.
Click Submit to send the claim data to ISO.
Creating an Activity Plan (End User)

An adjuster uses the Activity Plans view to manage the claims task to completion and assign activities to different individuals. When he clicks the Default Plans button, Siebel Insurance automatically creates an activity plan based on the loss code for the claim. One of the adjusters jobs is to assign a field appraiser to appraise damage. Assigning an appraiser can be complex because the customer schedule and appraiser schedule must be optimized. In the activity plan, the user can drill down on an activity of type Field Appraisal to go to the Activities, then the Schedule view. The user can also drill down on the Status field in the activity plan, and if the status value is Unscheduled, the user is taken to the Dispatch Board view, which allows complex appraisal scheduling. For more information about scheduling with the Dispatch Board, see Siebel Field Service Guide. This task is a step in Process of Managing Claims on page 95.
To create an activities plan 1 2 3 4

Navigate to the Claims screen. In the Claims list, drill down on the desired claim. Click the Diary Management, then the Activity Plans view tab. Click the Default Plans button. The default activities plan is created based on the loss code for the claim.
Assigning a Claim Element (End User)

Many insurance companies break down claims into subcomponents called claim elements. By subdividing claims in this way, insurers can delegate the management of these subcomponents to specific groups within their company according to their business rules. You can also create a claim element and assign it to a third party. For example, you can assign a claim element to a service provider, such as Auto service, who then does the repair. The third party can see the claim element through the Partner Portal. This task is a step in Process of Managing Claims on page 95.
To assign a claim element 1

Navigate to the Claims screen.
11 3
Managing Claims Assigning Claims to a Specialist Unit (End User)
2 3 4
In the Claims list, drill down on the desired claim. Click the Assignments view tab. In the Claim Elements list, create a new record.
Adding Claim Element Details

Use the following procedure to add claim element details.
To add claim element details 1 2 3

Navigate to the Claim Elements screen. In the Claim Elements list, drill down on the desired Line #. Select the appropriate view tab to add details specific to the currently selected claim elements. NOTE: The view tabs on the Claim Elements screen function identically to those on the Claims screen.
Assigning Claims to a Specialist Unit (End User)

The following buttons are available in the Claims List screen for evaluating the fraud and subrogation (that is, recovery) potential of a claim: Evaluate Subrogation Potential. Evaluates the subrogation potential of the claim. Evaluate SIU Potential. Evaluates the fraud potential of the claim. Details. Captures the claims combined score details.
During implementation, the customer can write a business service or enable the Analytics application to drive the logic behind these evaluation buttons. When the user clicks either the Evaluate Subrogation Potential or Evaluate SIU Potential button, Siebel Insurance takes the value from the Details button, which captures the claims combined score details, and performs the calculation that determines the value in the Subro Potential or Suspicious Claims indicator in the Claims form respectively. Each indicator has ten bars each representing 10% and colors are displayed in the bars according to the value in the field to the right of the bars, which can have a value from 0 through 1. The following buttons are available for assigning claims to appropriate specialist units: Notify SIU. Assigns the claim to the special investigation unit (SIU) Notify Subro. Assigns the claim to the subrogation unit
After the Assignment Manager assigns the claim, an Alert applet in the Home page displays details of the claim. The user can then drill down on the alert to go to either the SIU dashboard view or the Recovery dashboard view, as appropriate. NOTE: The Assignment Manager component must be running. To check that it is running, navigate to the Administration - Server Configuration, Servers, then Components screen, and check for Assignment Manager and Batch Assignment entries in the list.
114
Managing Claims Adding an Appraisal (End User)
For information about managing claims through the recovery process, see Managing Recovery Information (End User) on page 132. For information about managing suspicious claims through the investigative process, see Managing Fraud Information (End User) on page 138. This task is a step in Process of Managing Claims on page 95.
To assign a claim to a subrogation unit 1 2 3

Navigate to the MyClaims screen. Drill down on a claim. Select a record, and click the Notify Subro button. The claim is assigned to the subrogation unit.
Assigning a Claim to an SIU

Use the following procedure to assign a claim to an SIU.
To assign a claim to an SIU 1 2 3

Navigate to the MyClaims screen. Drill down on a claim. Select a record, and click the Notify SIU button. The claim is assigned to the SIU.
Adding an Appraisal (End User)

End users use the Appraisals view to record a property's insurable value, or the amount of a loss. A row in the view shows the total estimation value for all adjusters. End users can click the Check Reserves button to compare the total estimation value with the total reserve amount set for the claim. (The INS Reserve Estimation Check business service is invoked.) If the reserve value is less than the total estimation value for all adjusters, Siebel Insurance notifies the end user that the reserve value must be adjusted. This task is a step in Process of Managing Claims on page 95.
To add an appraisal 1 2 3
Navigate to the Claims screen. In the Claims list, drill down on a claim. Click the Reports/Documents, then the Appraisals view tab.
11 5
Managing Claims Attaching Claims Documentation (End User)
In the Appraisals form, add a record, and complete the necessary fields. Some fields are described in the following table. Field Type Property Appraised Amount Appraiser Type Appraiser Name Service Region Comments The type of appraisal. Values include: Automobile, Home, RV. The property being appraised. The amount of the appraisal. The type of appraiser: Adjuster or Body Shop. An employee chosen from a Select Appraiser applet. The service region applicable to the appraiser. This field is automatically prefilled when the appraiser name is selected.
Click Check Reserves to check that the total estimates do not exceed the available reserves.
Attaching Claims Documentation (End User)

Adjusters use the Claims screen, then the Attachments view to attach documents associated with a claim, for example: All Claims. Statements, photographs, scene diagrams, state statutes, payments, estimates. Auto Claims. Ticket disposition, uninsured: subrotech information. Property Claims. Proof of loss.
To attach claims documentation 1 2 3 4

Navigate to the Claims screen. In the Claims list, drill down on a claim. Click the Reports/Documents, then the Attachments view tab. In the Attachments list, create a new record, and complete the necessary fields.
Tracking Police and Fire Reports (End User)

End users can use the Police And Fire Reports view to collect and manage police and fire report information.
116
Managing Claims About Coverages and Reserves
To add police and fire report information 1 2 3 4

Navigate to the Claims screen. In the Claims list, drill down on a claim. Click the Reports/Documents, then the Police And Fire Reports view tab. In the Police/Fire Reports Detail list or form, add a record, and complete the necessary fields.
About Coverages and Reserves

When a customer purchases an insurance policy, the policy specifies which coverages are included in the policy. For example, for an auto policy there might be coverages for: towing and labor, rental car, collision, and bodily injury. Each of these coverages has an associated maximum amount covered and the deductible amount. An adjuster must open a reserve for each coverage that applies to a claim. A reserve is an amount of money made available for payments in respect of claims. For example, if the claimant was involved in a collision accident, the adjuster must open a reserve for collision coverages. If the claimant was injured, the adjuster must open a bodily injury reserve. The money that the insurance companies put aside cannot be used for anything else, therefore it is important to create the right amounts for reserves. This task is a step in Process of Managing Claims on page 95.
Creating a Reserve (End User)

A claims adjuster uses the Loss Details - Auto and Loss Details - Property views to make sure that the customer has the right policy and coverage for a claim and to create a reserve for each coverage. It is essential to capture policy information at the time that the claim is opened, because policy information might change over time. To do so, the end user must select the right policy for the customer in the Policy field in the Claims form header applet. In the case of the Loss Details - Auto view, the Driver, Vehicle and Coverages applets are then populated with the policy details. NOTE: There is also a Get Policy button in the form applet that is disabled by default. The customer can enable this button by writing an appropriate business service to get the policy information from their policy system to populate the policy information in the claim.
11 7
Managing Claims Creating a Reserve (End User)
Table 8 shows the information displayed in the Coverages applet.
Table 8. Field Coverage
Coverage Information in Loss Details Views Comments The name of the coverage, for example, collision, bodily injury and so on. The individual limit of the coverage. For example, for a bodily injury, the typical individual limit is $100,000, which means that the most the insurance company will pay for bodily injury for a particular person is only up to $100,000.
Individual Limit
Total Limit
The total limit for a particular coverage. For example, for bodily injury, the typical total limit is $300,000, which means that the most the insurance company will pay for bodily injury for this claim is $300,000, regardless of how many persons are involved.
Deductible Coverage Applies? Reserve Code Reserve Reserve Type
The amount of loss paid by the policy holder. A flag to indicate that a reserve is opened based on the loss code for the claim. The reserve code. The name of the reserve. The type of reserve, which specifies how the reserve is set. Manual. The value is set at the time of reserve creation by the adjuster. Factor. The reserve has a default value Calculated. The reserve value is computed in realtime by a business service.
Reserve Amount
The amount of the reserve.
For each coverage, the Coverage Applies flag indicates whether a reserve must be created for the coverage. For example if the claim is for a car collision accident, the Collision coverage is flagged so that a reserve is created for that coverage. Coverages are flagged as applicable according to the default coverages for the loss code. For more information about loss codes, see Administering Loss Codes on page 100.
118
Managing Claims About Managing Reserves
The adjuster clicks the Create Reserve button to create a reserve for all the coverages that have the Coverage Applies flag set. If you want to create a reserve from a coverage that does not have the Coverage Applies flag set, you can set the flag for that coverage and add the appropriate reserve code. Reserves are created according to the reserve code and reserve type that are associated with the coverage. For more information about reserve codes, see Administering Reserve Codes on page 99. After a reserve is created, it can be viewed in the Claims, Financials, and then the Reserves view, see Managing Reserves (End User) on page 122. This task is a step in Process of Managing Claims on page 95.
To create a reserve for an auto policy claim 1 2 3 4

Navigate to the Claims screen. In the Claims list, drill down on a claim. Click the Loss Details, then the Loss Details - Auto view tab. Select the required policy in the Policy field in the Claim form header applet. The policy information including details for Vehicles, Driver, and Coverages are copied into the view.
In the Coverages list, click the Create Reserve button.
About Managing Reserves

An adjuster uses the Claims, Financials, and then the Reserves view to: Open reserves Adjust reserves Delete a reserve created using the Create Reserve button in the Loss Details - Auto or Loss Details - Property view Create new reserves
Opening Reserves
To open a reserve, the adjuster enters the amount of reserve to open in the Reserve Amount field and clicks the Open Reserve button. Siebel Insurance then performs the following checks:
11 9
Reserve authority limit check. Siebel Insurance checks the user limit on a per reserve - per claims basis. For example, if adjuster A has a bodily injury limit of $20,000 and he would like to open bodily injury for contact 1 for $15,000 and bodily injury for contact 2 for $15,000, Siebel Insurance displays an error message since the $30,000 is more than the adjuster total bodily injury limit for the claims. The per reserve - per claim basis will apply at the supervisor level as well. That means if the claim goes to a supervisor, the amount will go against that supervisor limit even if he does not approve it. For example in, lets say B (As supervisor) limit for bodily injury reserve is only $25,000. In this case, B can not approve it and Siebel Insurance will send the claim to C (Bs supervisor). The next time A would like to open another bodily injury reserve, B cannot approve it anymore since the total bodily injury for the claim is already more than $30,000 and this is more than Bs bodily injury $25,00 limit. A supervisor can click one of the reserves in the Inbox list to open a reserve, as long as his or her own limits are not exceeded. On the reserve applet, the approver only sees that associated reserve record. To see all of the reserve records, the approver can use the query button to show all reserves. From the inbox, a supervisor can change the reserve status to either approve or reject. Once a supervisor has changed the status of an Inbox item, the associated reserve status is changed and the item is moved to the completed inbox. Because the approval history is tracked by inbox items, administrators must not delete completed inbox items. For more information about using the Inbox, see Siebel Applications Administration Guide. The reserve authority limit check Split limit check. Siebel Insurance checks the individual policy limit and the total policy limit fields and does some comparison. If the reserve amount set for a contact or an account is more than the individual limit, Siebel Insurance displays an error message. Also, if the reserve amount set for a particular coverage is more than the total limit, Siebel Insurance displays an error message. For example, a Bodily Injury coverage can have a $100,000 individual limit and $300,000 total limit. Siebel Insurance checks that the reserve amount to be opened for each individual or account for the Bodily Injury reserve is no more than $100,000 and that the total reserves amount for bodily injury reserves for all individuals or accounts is no more than $300,000.
After the checks are performed, The Outstanding Reserve field is updated with the amount that was entered in the Reserve Amount field. For more information about financial limits for adjusters, see Administering Adjusters Financial Limits on page 101. Table 9 shows the fields in the Reserves applet.
Table 9. Field Status
Reserve Fields Comments The status of the reserve. If the reserve status is Open, the reserve record is read only and the only way an adjuster can modify this record is by clicking the Reserve Adjustment button.
Reserve Code Reserve
The code of the reserve. The name of the reserve.
120
Table 9. Field
Reserve Fields Comments The reserve amount. The adjuster can enter the amount of reserve in this field. If the reserve type is Factor, this field is automatically prefilled. The type of the reserve such as Factor, Manual, or Calculated. The date the reserve is opened. The date the reserve is closed. The amount of reserve outstanding at a particular time. The value of this field is automatically decreased every time an adjuster makes an indemnity payment. The last name of the contact for which the reserve is opened. The first name of the contact for which the reserve is opened. The name of the account in which the reserve is opened. A reserve can only be opened for either a contact or account and cannot be opened for both.
Reserve Amount
Reserve Type Reserve Open Reserve Closed Outstanding Reserve Last Name First Name Account
Individual limit
The individual limit for a particular reserve for a particular contact or account. The individual limits for reserves of the same reserve code must be the same. If, for example, you have two bodily injury reserves of the same code, one for person A, and you specify an individual limit of $100,000 and on the other bodily injury for person B you specify an individual limit of $150,000, Siebel Insurance displays an error message.
Total Limit
The total limit for a particular reserve. The total limits for reserves of the same reserve code must be the same.
Deductible
The deductible for the reserve. The deductibles for reserves of the same reserve code must be the same.
Adjuster
The name of the adjuster to which this particular reserve is assigned. Different reserves can be assigned to different adjusters and only the assigned adjuster can open that particular reserve, therefore it is necessary to enter the adjuster name.
12 1
Managing Claims Managing Reserves (End User)
Table 9. Field Approver
Reserve Fields Comments The approver name. Siebel Insurance automatically populates the approver name with the adjusters supervisor name. For information about how the employee hierarchy is set to determine the supervisor for each adjuster, see Administering the Employee Hierarchy on page 102. The supervisor can then go to the Inbox screen, drill down on the claims that need approval, and select the claim to open the reserve. The supervisor can change the status to either approve or reject. Once the status of the inbox is changed, items move to the completed inbox. If this supervisor does not have enough reserve limit, Siebel Insurance fills in the supervisors supervisor name in the Approver field. Siebel Insurance then notifies that supervisor to go to the Inbox screen to approve the reserve.
Insured property Total payment
The insured property. The total amount of payment that has been made using this reserve.
Adjusting a Reserve
After a reserve is opened, the user can adjust only the reserve amount by selecting the reserve record and clicking the Reserve Adjustment button. The user can then change the reserve amount and reopen the reserve. The adjuster can make the adjustment even after the reserve is used to make payment. When the adjuster makes a payment of type Indemnity, the value of the Outstanding Reserve field is decreased by the amount of the payment. If the Outstanding Reserve amount is 0, the adjuster cannot use this reserve to make other indemnity payments. If the adjuster wants to make indemnity payments, he must adjust the reserve amount by clicking the Reserve Adjustment button and entering the new reserve amount in the Reserve amount field. Siebel Insurance then updates the Reserve Outstanding field. Only the adjuster that is assigned to a reserve can open or adjust that reserve. An adjuster can assign a reserve to a different adjuster by changing the Adjuster field in the Reserves view.
Managing Reserves (End User)

After a reserve is created, an adjuster can open and adjust the reserve. You can also create new reserves and delete existing reserves. This task is a step in Process of Managing Claims on page 95.
122
Managing Claims Managing Reserves (End User)
To open a reserve 1 2 3 4 5 6
Navigate to the Claims screen. In the Claims list, drill down on a claim. Click the Financials, then the Reserves view tab. In the Reserves list, select the required record. Enter the required amount in the Reserve Amount field. Click Open Reserve.
Adjusting a Reserve
Use the following procedure to adjust a reserve.
To adjust a reserve 1 2 3 4 5 6 7
Navigate to the Claims screen. In the Claims list, drill down on a claim. Click the Financials, then the Reserves view tab. In the Reserves list, select the required record. Click Reserve Adjustment. Enter the required amount in the Reserve Amount field. Click Open Reserve.
Creating a New Reserve

Use the following procedure to create a new reserve.
To create a new reserve 1 2 3 4

Navigate to the Claims screen. In the Claims list, drill down on a claim. Click the Financials, then the Reserves view tab. In the Reserves list, create a new record and complete the necessary fields. For information about the fields in a reserve, see Table 9.
Deleting a Reserve
Use the following procedure to delete a reserve.
12 3
Managing Claims Tracking Demands for Payment (End User)
To delete a reserve 1 2 3 4 5
Navigate to the Claims screen. In the Claims list, drill down on a claim. Click the Financials, then the Reserves view tab. In the Reserves list, select the required record. Click Delete.
Tracking Demands for Payment (End User)

End users use the Bills view to record demands for payment associated with a claim. NOTE: The Bills view was used in versions prior to Siebel Insurance 8.0. In Siebel Insurance 8.0, you can use either the Bills view or the Invoices view to capture information about bills. This task is a step in Process of Managing Claims on page 95.
To record demands for payment 1 2 3 4

Navigate to the Claims screen. In the Claims list, drill down on a claim. Click the Financials, then the Bills view tab. In the Bills list, add a record, and complete the necessary fields. For more information on claim elements, see Assigning a Claim Element (End User) on page 113.
In the Attachments list, attach an electronic version or image of the bill.
Creating an Invoice Record (End User)

An adjuster uses the Claims, then the Invoices view to create a record of bills and invoices received from the claimant and third parties in respect of a claim. The view is also used to associate invoices with claims. If the adjuster wants to add additional line items for the invoice, or to attach an invoice image and note, the adjuster can drill down on the invoice number to go to the Invoices Screen. For information about using the Invoices screen, see Siebel Communications Guide. This task is a step in Process of Managing Claims on page 95.
To create invoice records 1 2

Navigate to the Claims, then the Invoices view. In the Invoices list, add a new record, and complete the necessary fields.
124
Managing Claims Generating a Payment Record (End User)
3 4 5 6
Drill down on the invoice to go to the Invoices screen. (Optional) In the Line Items list, add line items for the invoice. (Optional) In the Attachments list, attach an electronic version or image of the invoice. (Optional) In the Notes list, add any notes for the invoice.
Generating a Payment Record (End User)

An adjuster can use the Claims screen, then the Invoices view to create a record of invoices received from the claimant and third parties in respect of a claim, and to generate a payment record for invoices. When the adjuster clicks the Generate Payment button, Siebel Insurance creates a payment record for one invoice or multiple invoice records. NOTE: A similar view is in the Claims Element screen. This task is a step in Process of Managing Claims on page 95.
To generate a payment record 1 2 3 4 5

Navigate to the Claims screen. In the Claims list, drill down on a claim. Click the Financials, then the Invoices view tab. In the Invoices list add records and complete the necessary fields. Click Generate Payment.
Tracking Payments Related to Invoices (End User)

Adjusters can use the Invoices, then the Claim Payments view to track all of the payments for invoices. This task is a step in Process of Managing Claims on page 95.
To view the payments for an invoice 1 2 3

Navigate to the Invoices screen. In the Invoices list, drill down on an invoice. Click the Claim Payments view tab.
12 5
Managing Claims About Issuing a Settlement Payment (End User)
About Issuing a Settlement Payment (End User)

End users use the Financials, then the Payments view tab to issue a settlement payment. This task is a step in Process of Managing Claims on page 95. A payment can be associated with a single or multiple reserves. For example, an adjuster can make a payment of $10,000, and this payment can be drawn from a collision reserve and a towing-andlabor reserve. NOTE: End users can associate a payment with reserves only if the payment type is indemnity. For other payment types, the Reserves list applet is a read-only applet. Table 10 shows the fields in the Payment list applet.
Table 10. Field
Payment List Applet Fields Comments The system-generated payment number. The code of the payment. Values include: After Full Payment, Full Payment, and Partial Payment The type of payment. Values include: SIU Expenses, Subrogation Expenses, Expenses, Indemnity Payment, Loss, and Loss - Supplemental. The method of payment. Values include: Check, Cash, Cashier Check, Third Party, Payroll Deposit. The name of the contact to whom payment is made. The name of the company to which payment is made. The amount of the payment. Whether the payment represents a cash settlement. The claim element associated with the payment. The claim element coverage. The invoice associated with the payment. The date the payment is issued. The number of the check issued for payment. The name of the adjuster making the payment.
Payment # Payment Code Payment Type
Payment Method Payee Vendor Payee Amount Cash Settlement Claim Element # Claim Element Coverage Invoice # Issued Check # Paid By
126
Table 10. Field
Payment List Applet Fields Comments The status of the payment. Pending. The default status and the status when the validation fails. On-Hold OFAC. The status when the OFAC check fails. On-Hold Limit. The status when the authority limit check fails. Approved Limit. The status when the supervisor approves. Rejected. The status when the supervisor rejects the payment. Payment Generated. The status when all the checks are good and the payment goes through. Void. The status when the payment is voided. Bulk Payment. The status when the payment is made through bulk payment.
Payment Status
From Date To Date Adjuster Approver
For medical claim or bodily injury bills, the from date for the customers stay in hospital. For medical claim or bodily injury bills, the to date for the customers stay in hospital. Read only field populated with the login ID of the payment creator. Read only field populated when the payment enters the approval process.
Table 11 shows the fields in the Reserve list applet.
Table 11. Field
Reserve List Applet Fields Comments The code of the reserve. The name of the reserve. The reserve amount. The amount of reserve outstanding at a particular time. The value of this field is automatically decreased every time an adjuster makes an indemnity payment.
Reserve Code Reserve Reserve Amount Outstanding Reserve
12 7
Table 11. Field
Reserve List Applet Fields Comments The amount of the reserve that will be applied to the selected payment. The deductible for the reserve. Whether the deductible has been applied to the payment. The individual limit for a particular reserve for a particular contact or account. The total limit for a particular reserve. The name of the contact for which the reserve is opened. The last name of the contact for which the reserve is opened. The name of the account in which the reserve is opened. A reserve can only be opened for either a contact or account and cannot be opened for both.
Reserve Applied to Payment Deductible Apply Deductible? Individual limit Total Limit Last Name First Name Account
Reserve Open Reserve Closed Total Payment Status
The date the reserve is opened. The date the reserve is closed. The total amount of payment that has been made using this reserve. The status of the reserve.
When the user clicks the Submit Payment button, the following checks are performed:
Check whether some of the fields are entered correctly. Siebel Insurance checks:
a b c d e 2
That the Date From field is not null, and that it is before the date in the Date To field. That the Date To field is not null, and that it is later than the date in the Date From field. That the Payment Amount field is not 0. That the Payment Status field is pending. Only a payment with status Pending is evaluated when the user clicks the Submit Payment button. Whether the Mail To Flag is set for the Payee or Vendor Payee field. There must be only one payee among both the contact payees and the vendor payees that have the Mail Payment Flag checked.
Check whether the contact payee or account payee is in the OFAC database. Siebel Insurance checks whether the contact or account is in the OFAC database. If the payee or vendor payee is in the OFAC database, Siebel Insurance suspends the payment and changes the status of the payment to On Hold OFAC. For more information, see Checking a Claim Against the ISO Database (End User) on page 110.
128
Check whether the per-coverage deductible has been applied to the payment amount. Siebel Insurance checks whether the deductible flag in the Reserve list applet is checked. This step is only applicable if the payment is associated with a reserve (that is, a payment of type Indemnity payment). If the deductible flag is not checked, Siebel Insurance displays a message prompting the adjuster to reduce the amount in the Reserve applied toward payment field by the deductible amount. When the flag is set to true, the deductible flag field becomes a read-only field and it applies to the reserve. So, the next time the adjuster associates the reserve to another payment, the deductible flag remains checked. Check whether the payment amount is equal to the total of reserve applied to payment . Siebel Insurance checks whether the Total reserve applied toward payment field in the Reserve list applet is the same amount as in the Payment amount field in the Payment list applet. If the value is not the same, Siebel Insurance displays an error message prompting the user to adjust the amount to make it the same. Check whether the reserve applied to payment is equal or less than outstanding reserve. Siebel Insurance checks whether there is enough outstanding reserve to make the payment. If there is not enough reserve left to make the payment, Siebel Insurance displays a message to adjust the Reserve Applied to Payment field in the Reserve list applet to be less or equal to the Outstanding Reserve field in the Reserve list applet.
12 9
Check if the payment authority limit is correct. Siebel Insurance checks whether the adjuster has enough payment limit to make this payment. The adjuster has a payment limit on the coverage level as well as on the total claim level (see Administering Adjusters Financial Limits on page 101). For every payment made by this adjuster, Siebel Insurance keeps track of how much payment has been made on the coverage level and on the claim level. Siebel Insurance then compares this with the adjuster payment limit for each coverage and for the claim. For example: Adjuster A has a bodily injury payment limit of $10,000, collision payment limit of $5,000, and a total indemnity payment limit of $20,000. If the adjuster receives an invoice, say for $12,000, and he wants to draw from the collision and bodily injury reserves to make this payment, the most he can pay from the bodily injury reserve is $10,000, and the most he can draw from the collision reserve is $5000. If he tries to pay more than his payment limit, Siebel Insurance displays a message and sends notification to the supervisor for approval. Siebel Insurance keeps track of how much the user has paid from a particular limit. Suppose on this $12,000 payment, the user draws $10,000 from the bodily injury reserve and $2,000 from the collision reserve. The next time he wants to make a payment, he can not make a payment from bodily injury reserve without Siebel Insurance notifying his supervisor for approval, because he has already used up to his payment limit on bodily injury reserves. Siebel Insurance keeps track of the adjuster payment limit on the per reserve - per claim level. For example, adjuster A might have a bodily injury payment limit of $10,000. Suppose he wants to make a payment, and wants to draw $6,000 from the bodily injury reserve 1 for Mary and $6,000 from bodily injury reserve 2 for Todd. In this case, Siebel Insurance displays an error message since the total of bodily injury payments is more than the adjuster As $10,000 limit. The per reserve - per claim basis will apply on the supervisor level as well. If the adjuster does not have enough payment limit, Siebel Insurance creates an Inbox item for the supervisors approval. The supervisor can then go to the Inbox screen to approve the payment. The supervisor can drill down on the Inbox item to view the payment details. To see all of the payment records, the supervisor can use the query button. He can then return to the Inbox view and approve or reject the Inbox item. When the supervisor approves the payment, the payment status goes to Payment Generated. If the supervisor's limit is not enough, another Inbox item is created for the supervisor's supervisor. However, if the supervisor rejects the Inbox item, the payment status goes to Rejected. For more information about using the Inbox, see Siebel Applications Administration Guide.
Updating the reserve outstanding amount if all the above checks are passed. Siebel Insurance reduces the Outstanding Reserve field by the amount of payment made. For example, suppose an adjuster sets a $2,000 collision reserve for the claim, and the collision reserve has a $500 deductible. If the adjuster receives a bill from a glass vendor for $1,000, the adjuster applies the deductible for the collision reserve and pays the $500 from the $2,000 collision reserve. After he makes the payment, the outstanding reserve becomes $1,500. The adjuster can then use this $1,500 outstanding reserve to pay another bill related to collision coverage.
For more information about the financial limits for adjusters, see Administering Adjusters Financial Limits on page 101. If the adjuster makes a mistake, the adjuster can select the Void button to reverse the transaction. When the user select the Void button, Siebel Insurance adds the payment amount back into the outstanding reserve amount. Furthermore, the user can modify the payment and reserve record accordingly.
130
Managing Claims Issuing a Settlement Payment (End User)
Issuing a Settlement Payment (End User)

An adjuster issues a payment to settle a claim. This task is a step in Process of Managing Claims on page 95.
To issue a settlement payment 1 2 3 4 5

Navigate to the Claims screen. In the Claims list, drill down on a claim. Click the Financials, then the Payments view tab. (Optional) If the payment type is Indemnity, in the Reserves list, associate one or more reserves with the payment. In the Payments list, add a record and complete the necessary fields. NOTE: You can configure your Siebel application to connect to the system your company uses to produce a draft or check to pay the claim. For more information, see Siebel Integration Messages on page 193.
Making a Bulk Payment (End User)

Insurance companies usually have a relationship with vendors such as car rental companies where the insurance company can make one large payment in a particular period, for example, every two weeks, or every month. For such bulk payments, Siebel Insurance allows the adjuster to query all the payments for the vendor, sum the payments, and generate one payment for the vendor. To use the bulk payment capability, the user must first set the relevant account for bulk payment. This task is a step in Process of Managing Claims on page 95.
To set an account for bulk payment 1 2 3 4

Navigate to the Accounts screen Drill down on an account. Click the Profiles, then the Customer Profiles view tab. In the Pricing and Purchasing Information section of the form, select the Bulk Pay check box. Bulk payment can now be used for the account.
Making Bulk Payments

Use the following procedure to make a bulk payment.
13 1
Managing Claims Viewing the Invoices and Claims for a Payment (End User)
To make a bulk payment 1 2 3

Navigate to the Payments screen, then the Insurance Payments view. Click the Generate Bulk Payment button. In the Payments query box, select the appropriate Account, and select a From Date and To Date. Siebel Insurance queries all payment record for the vendor for the specified period and generates a payment record for the vendor. The payments associated with that particular bulk payment are displayed in the Payment screen, Insurance Payment, and then the Bulk Payment view. NOTE: For the query to work properly, make sure that the Issued field in the Claims, then the Payment view contains the payment issue date.
Viewing the Invoices and Claims for a Payment (End User)

Adjusters can use the Payments, then the Insurance Payments view to display all of the invoices and claims associated with a particular payment. This task is a step in Process of Managing Claims on page 95.
To view the invoices and claims for a payment 1 2

Navigate to the Payments screen, then the Insurance Payments view. Drill down on a payment. The invoices and claims for the payment are displayed.
Managing Recovery Information (End User)

End users use the Claims screen, then the Recoveries view to record and track information regarding subrogation and salvage activities. This task is a step in Process of Managing Claims on page 95. Subrogration refers to sections of a property insurance or liability insurance policies that give the insurer the right to take legal action against the third party who is responsible for the loss. For example, a customers car might be hit by another car and instead of waiting for the other car owners insurance to pay, the customer files a claim with his insurance company. The insurance company pays for the damage but contacts the other insurance company to get reimbursement for the payment. The process of getting reimbursement from the other insurance company is an example of subrogation. Salvage occurs when the insurer takes ownership of the damaged property after the claim has been settled. An adjuster can assign a claim to a subrogation unit if required. One or more investigators can then use the Recoveries dashboard to manage the subrogation activities and to recovery money from the third party.
132
Managing Claims Managing Recovery Information (End User)
A claim can be assigned to various investigators, for example, to arbitration or litigation specialists, or to people handling collection and salvage. Table 12 shows the primary fields in the Recovery dashboard.
Table 12. Field
Recovery Dashboard Fields Comments Indicates whether the claim has been referred to subrogation. Identifies how the case was referred to subrogation: System. The case was referred automatically due to the subrogation potential score. Manual - adjuster. An adjuster referred the case manually. Manual - Reassignment. The case was reassigned.
Subro Referral Referral Source
Assignment Date Closed Date Subro Potential
Displays the time and date on which the subrogation file was opened. Displays the time and date on which the subrogation file was closed. Displays the combined subrogation potential score. This field is updated by the Evaluate Subrogation Potential button in the Claims List applet.
Overall Fault % Status
Displays the theory of liability value for the claim. This field is set through the Update Theory of Liability task. Select the status of the subrogation case. Values include: Assigned, Accepted, Initial Review, Negotiations, Decision Pending, Closed, and Re-opened. Select the final status of the subrogation case after processing. Values include: Partial Recovery, Full Recovery, Collections Handoff, Arbitration Handoff, Litigation Handoff, and Abandoned.
Disposition
13 3
Table 13 shows the fields in the dashboard that display the key financial information.
Table 13. Field
Recovery Dashboard Key Financials Fields Comments Displays the total of payments made on the claim to date. This field is updated by the Recalculate Payment task. NOTE: The value in this field comes from the Claims, then the Payment view for payments with a type other than Subrogation Expense or SIU Expense.
Total Claim Payment
Total Expenses
Displays the total subrogation expenses incurred to date. This field is updated by the Update Expenses task. NOTE: The value in this field comes from the Claims, then the Payment view for payments with a type of Subrogation Expense.
Recovery Potential
Displays the recovery potential for the claim. The default value is (Theory of Liability % * Total Claim Payment), that is the theory of liability percentage multiplied by the total claim payment amount. This field is updated by the Update Recovery potential task.
Table 14 shows the fields in the dashboard used for arbitration or litigation referrals.
Table 14. Field
Recovery Dashboard Arbitration/Litigation Referral Fields Comments Indicates whether the claim is assigned to a litigation or arbitration specialist. Displays the date and time when the case was assigned to arbitration or litigation for further pursuit. Select the arbitration board or the external counsel handling the case. If the organization is a business unit, it is added to the claims Service Provider list with a role of Subro Arb./Lit. Provider. Enter the settlement amount for the subrogation case.
Arb./Lit. Referral Assignment Date
Counsel/Arb. Board
Settlement Amount
134
Table 14. Field Status
Recovery Dashboard Arbitration/Litigation Referral Fields Comments Select the status of the arbitration or litigation process. Values include: Assigned, Accepted, Initial Review, Filed Arbitration, Under Litigation Internal, Under Litigation - External, Decision Pending, Closed, and Re-opened.
Disposition
Select the final status of the arbitration or litigation case. Values include: Settled - Full Recovery, Settled - Partial Recovery, Collections Handoff, and Abandoned.
Table 15 shows the fields in the dashboard that display the final outcome of the recovery processing
Table 15. Field
Recovery Dashboard Outcome Fields Comments Enter the total recovery amount on the claim. Select the debt schedule for the subrogation recovery. Values include Installments and Single Payment. Displays the deductible return amount for the subrogation case. This field is updated by the Calculate Deductible Return task.
Recovery Amount Debt Schedule Deductible Return
Table 16 shows the fields in the dashboard used for collections referrals.
Table 16. Field
Recovery Dashboard Collections Referral Fields Comments Indicates whether the claim has been assigned to collections. Displays the date and time when the case was assigned to collection for further pursuit. Select the collection agency handling the case. If the organizations is a business unit, it is added to the claims Service Provider list with a role of Subrogation Collection Agency. The collection amount for the subrogation case.
Collections Referral Assignment Date Collection Agency
Collection Amount
13 5
Table 16. Field
Recovery Dashboard Collections Referral Fields Comments Select the status of the collection process. Values include: Assigned, Accepted, Negotiating, Closed, and Re-opened. Select the final status of the collection process. Values include: Full Recovery, Partial Recovery, and Abandoned.
Collection Status
Disposition
Table 17 shows the fields in the dashboard used for salvage processing.
Table 17. Field
Recovery Dashboard Salvage Potential Fields Comments Indicates whether salvage potential has been notified. Enter the date recovery took place. Enter the amount salvaged.
Notify Salvage Recovered Date Amount Recovered
Using the Common Task Links

In the Recovery dashboard, task links allow the user to update information in the dashboard or to reassign the case to a different person.
136
Table 18 shows the tasks in the recovery dashboard.
Table 18. Action
Tasks in the Recovery Dashboard Description Checks the state statutes. During implementation, the customer can extend the business service for this task to implement statute of limitations logic specific to the states in which they operate.
Check State Statutes
Update Theory of Liability
Displays a dialog box with the following fields: New Theory of Liability %. Enter a new value with which to update the Overall Fault % field in the dashboard. Reason for Change. Enter the reason for adjusting the theory of liability to create a new note of type Subro Liability Assessment with the text you enter. Update Recovery Potential flag. Select this check box to update the Subro Potential field with the calculated value (New Theory of Liability % * Total Claim Payment Amount).
Update Recovery Potential
Displays a dialog box with the following fields: New Recovery Potential Amount. Enter a new value with which to update the Subro Potential field in the dashboard. Reason for Change. Enter the reason for changing the recovery potential to create a new note of type Subro Recovery Potential with the text you enter.
Recalculate Payment Update Expenses Calculate Deductible Return
Recalculates the total claim payment and updates the Total Claims Payment in the dashboard. Recalculates the total subrogation expenses and updates the Total Expenses field in the dashboard. Calculates the amount of the deductible that must be returned to the insured party and updates the Deductible Return field in the dashboard. Updates the Notify Salvage flag. Displays a dialog box with the following fields: Assign To. Select the User ID of the person to whom you want to assign the claim. Leave the field blank if you require Assignment Manager to assign the claim automatically. Reason for Reassignment. Enter the reason for reassigning the case to create a new note of type Subro Reassignment with the text you enter.
Notify Salvage Reassign Claim
13 7
Managing Claims Creating a Recovery Payment Record (End User)
Table 18. Action
Tasks in the Recovery Dashboard Description Displays a dialog box with the following fields: Assign To. Select the User ID of the person to which you want to assign the claim. Leave the field blank if you require Assignment Manager to assign the claim automatically. Referral Notes. Enter any referral notes to create a new note of type Subro Litigation Referral with the text you enter.
Refer to Arbitration / Litigation
Refer to Collections
Displays a dialog box with the following fields: Assign To. Select the User ID of the person to which you want to assign the claim. Leave the field blank if you require Assignment Manager to assign the claim automatically. Referral Notes. Enter any referral notes to create a new note of type Subro Collection Referral with the text you enter.
Creating a Recovery Payment Record (End User)

A subrogation or SIU specialist uses the Financials, then the Recoveries view to create a record of invoices related to recoveries from third parties. This view is used to capture recoveries payment as well as to keep track of invoices that you send to third parties to collect the money. It is similar to the Claims screen, then the Invoices view but has a filter to show only invoices and payments related to the SIU and subrogation unit. This task is a step in Process of Managing Claims on page 95.
To create recovery payment records 1 2 3 4

Navigate to the Claims screen. In the Claims list, drill down on a claim. Click the Financials, then the Recoveries view tab. In the Invoices list, add records, and complete the necessary fields.
Managing Fraud Information (End User)

End users use the Claims screen, then the SIU Dashboard view to record and track information regarding fraudulent claims. This task is a step in Process of Managing Claims on page 95.
138
Managing Claims Managing Fraud Information (End User)
Cases of fraud relating to claims are usually handled by a special investigation unit (SIU). An adjuster can assign a claim to a SIU if he thinks there is fraud involved in the claims. One or more investigators in the SIU can then use the Claims screen - SIU Dashboard view to manage the fraudrelated activities. A claim can be assigned to various investigators, for example, to arbitration or litigation specialists. Table 19 shows the primary fields in the SIU dashboard.
Table 19. Field
SIU Dashboard Fields Comments Indicates whether the claim has been referred to the SIU. Identifies how the case was referred to the SIU: System. The case was referred automatically due to the suspicious claim score. Manual - adjuster. An adjuster referred the case manually. Manual - Reassignment. The case was reassigned.
SIU Referral Referral Source
SIU Assignment Date SIU Closed Date Stop Payment Suspicious Claim Score Prob. of Resolution SIU Status SIU Disposition
Displays the time and date on which the claim was assigned to the SIU. Displays the time and date on which the SIU file was closed. Indicates whether the payment is on hold. Displays the combined fraud potential score. Displays the probability of resolution value for the claim. This field is set through the Update Probability of Resolution task. Select the status of the fraud case. Values include: Assigned, Accepted, Initial Review, Negotiations, Decision Pending, Closed, and Re-opened. Select the final status of the fraud case after processing is complete. The values include: Abandoned, Deny, Litigate, Negotiated, Pay.
13 9
Table 20 shows the fields in the dashboard that display the key financial information.
Table 20. Field
SIU Dashboard Key Financials Comments Displays the total of payments made on the claim to date. This field is updated by the Recalculate Payment task. NOTE: The value in this field comes from the Claims, then the Payment view for payments with a type other than Subrogation Expense or SIU Expense.
Total Claim Payment
Total Expenses
Displays the total SIU expenses incurred to date. This field is updated by the Update SIU Expenses task. NOTE: The value in this field comes from the Claims, then the Payment view for payments with a type of SIU Expense.
Recovery Potential
Displays the recovery potential for the claim. The default value is (Prob. of Resolution % * Total Claim Payment). This field is updated by the Update Recovery Potential task.
Table 21 shows the fields in the dashboard that display the final outcome of SIU investigation.
Table 21. Field
SIU Dashboard Outcome Fields Comments Displays the total outstanding reserve amount for the claim. This field is updated by the Recalculate Conservation task.
Conservation Amount
Recovery Amount Debt Schedule
Enter the total recovery amount for the claim. Select the debt schedule for the fraud recovery. The values are: Installments and Single Payment.
Table 22 shows the fields in the dashboard used for arbitration or litigation referrals.
Table 22. Field
SIU Dashboard Litigation Referral Fields Comments Indicates whether the claim is assigned to a litigation or arbitration specialist. Displays the date and time when the case was assigned to litigation for further pursuit.
Litigation Referral Assignment Date
140
Table 22. Field
SIU Dashboard Litigation Referral Fields Comments Select the organization; that is, the external counsel handling the case. If the organization is a business unit, the organization is added to the claims Service Provider list with a role of Fraud/Lit. Provider. Enter the minimum and maximum settlement amounts for the fraud case.
Outside Counsel
Settlement Range
Using the Common Task Links

In the SIU dashboard, task links allow the user to update information in the dashboard or to reassign the case to a different person. Table 23 shows tasks in the SIU dashboard.
Table 23. Action
Tasks in SIU Dashboard Description Recalculates the total claim payment and updates the Total Claim Payments field in the dashboard. Recalculates the total SIU expenses and updates the Total Expenses field in the dashboard. Displays a dialog box with the following fields: New Recovery Potential Amount. Enter a new value with which to update the Recovery Potential field in the dashboard. Reason for Change. Enter the reason for changing the recovery potential to create a new note of type Fraud Recovery Potential with the text you enter.
Recalculate Payment Update SIU Expenses Update Recovery Potential
Update Probability of Resolution
Displays a dialog box with the following fields: New Theory of Liability %. Enter a new value with which to update the Prob. of Resolution field in the dashboard. Reason for Change. Enter the reason for adjusting the theory of liability to create a new note of type SIU Liability Assessment with the text you enter. Update Recovery Potential flag. Select this check box to update the Recovery Potential field with the calculated value (New Theory of Liability % * Total Claim Payment Amount).
Recalculate Conservation
Recalculates the conservation amount and updates the Conservation Amount field in the dashboard.
14 1
Managing Claims About the Business Rules Processor and Claims Logic
Table 23. Action
Tasks in SIU Dashboard Description Goes to the National Insurance Crime Bureau (NICB) Web site to allow you to enter information for investigation by NICB. The NICB is a nonprofit organization that analyzes and investigates insurance fraud cases.
http://www.nicb.org
Reassign Claim
Displays a dialog box with the following fields: Assign To. Select the User ID of the person to which you want to assign the claim. Leave the field blank if you require Assignment Manager to assign the claim automatically. Reason for Reassignment. Enter the reason for reassigning the case to create a new note of type SIU Reassignment with the text you enter.
Refer to Arbitration / Litigation
Displays a dialog box with the following fields: Assign To. Select the User ID of the person to which to assign the claim, or leave the field blank if you require Assignment Manager to assign automatically. Referral Notes. Enter any referral notes to create a new note of type SIU Litigation Referral with the text you enter.
About the Business Rules Processor and Claims Logic

Much of the logic for Siebel Insurance is implemented using the Business Rules Processor (BRP) business service. The BRP is appropriate for business logic that can be modified, and you can modify claims business logic without deploying a new SRF. Because BRP is a business service, it can be called from workflow processes. For more information about using the BRP, see Business Rule Processor on page 210. Table 24 shows the BRP business rules processes for claims.
Table 24.
BRP Business Rules Processes for Claims Description Calculates the Subrogation Real Time score. Used In Evaluate Subrogation Potential button in MyClaims view Field that drives the subrogation indicator in MyClaims view
BRP Name FINS Claims Evaluate Subrogation Potential FINS Claims Calculate Combined Score
Calculates the Subrogation Combined score.
142
Table 24.
BRP Business Rules Processes for Claims Description Calculates the combined Fraud Potential score based on the Real time Rule score, Real time Predictive Model score, and Batch Predictive Model score. Evaluates the Fraud Potential score. Compares the Total Estimation amount with the Total Reserve amount. Performs the authority limit check before the reserve is opened. Performs checks on the limits for reserve claims. Calculates the SIU Total Expenses. Calculates the Conservation Amount. Used In Field that drives the fraud indicator in MyClaims view Evaluate SIU Potential button in MyClaims view Claims, then the Appraisals view Open Reserve button in Claims, then the Reserves view Open Reserve button in Claims, then the Reserves view Task link in SIU dashboard view Task link in SIU dashboard view Task link in SIU dashboard view Task link in SIU dashboard view Task link in Recovery view Task link in Recovery view Task link in Recovery view Notify Salvage flag in Recovery view Task link in Recovery view
BRP Name FINS Claims Calculate Fraud Score
FINS Claims Evaluate Fraud Potential FINS Claims Reserve Estimation Check BRP FINS Claims Authority Limit Check FINS Claims Split Limit Check FINS Claims Calculate SIU Expenses FINS Claims Calculate Total Conservation Amount FINS Claims Calculate Total Payment Amount FINS Claims Create Fraud Case Assignment Alert FINS Claims Calculate Subrogation Expenses FINS Claims Calculate Deductible Return FINS Claims Create Subrogation Case Assignment Alert FINS Claims Set Notify Salvage FINS Claims Subrogation Reassignment
Calculates the Total Claim Payments amount.
Creates an alert for a fraud case assignment.
Calculates the Subrogation Total Expenses. Calculates the Subrogation Deductible Return amount. Creates a subrogation case assignment alert.
Sets the Notify Salvage flag. Reassigns the claim to a subrogation specialist.
14 3
Table 24.
BRP Business Rules Processes for Claims Description Updates the subrogation fields for Recovery Potential or Update Theory of Liability tasks. Performs the Claims fraud Arbitration Litigation assignment. Reassigns the claim to a fraud specialist. Updates business component fields when the Update Recovery Potential or Update Probability Of Resolution link is clicked. Assigns the claim to a subrogation arbitration or litigation unit. Used In Task link in Recovery view Task link in Recovery view Task link in SIU dashboard view Task link in SIU dashboard view Task link in Recovery view
BRP Name FINS Claims Subrogation Update BC Fields FINS Claims Fraud Litigation Assignment FINS Claims SIU Reassignment FINS Claims Fraud Update BC Fields FINS Claims Subrogation Arbitration Litigation Assignment FINS Claims Subrogation Collections Assignment FINS Claims Subrogation Check State Statutes FINS Claims Assign SIU Opportunity FINS Claims Assign Subrogation Opportunity FINS Claims Invoke Assignment Manager FINS Claims Check OFAC Status For Contact Payees FINS Claims Check OFAC Status For Vendor Payees FINS Claims Payment Update Reserves
Assigns the claim to a subrogation collections unit.
Task link in Recovery view
Checks the State Statutes.
Task link in Recovery view Notify SIU button in MyClaims view Notify Subro button in MyClaims view All assignment buttons and assignment links. Submit Payment button in Claims, then the Payments view Submit Payment button in Claims, then the Payments view Submit Payment button in Claims, then the Payments view
Assigns the claims to the SIU unit when the user clicks the Notify SIU button. Assigns the claims to the subrogation unit when the user clicks the Notify Subro button. Invokes the Assignment Manager component. Checks and updates the OFAC-related fields for the Contact payees during the Submit Payment processing. Checks and updates the OFAC-related fields for the Vendor payees during the Submit Payment processing. Updates the Reserve fields during the Submit Payment processing.
144
Managing Claims Claims Workflows
Table 24.
BRP Business Rules Processes for Claims Description Validates the Reserve fields during the Submit Payment processing. Changes the Status from Pending - Open to Open when a user clicks the Reserve Adjustment button. Adds the Reserve position to the Claim team. Used In Submit Payment button in Claims, then the Payments view Reserve Adjustment button in Claims, then the Reserves view Open Reserve button in Claims, then the Reserves view Claims, then the Reserves view
BRP Name FINS Claims Payment Validate Reserves FINS Claims Reserve Adjustment FINS Claims Add Reserve Position to Claim Team FINS Claims Manual Override Flag
Sets the Manual Override flag. If the reserve is of type Factor and the Allow Override flag is set, and if the reserve amount is changed, the Manual Override flag is set to true. Cancels the submitted payment.
FINS Claims Void Payment Reserves Process FINS Claims Apply Deductible For Reserve
Void payment button in Claims, then the Payments view Apply Deductibles flag in Claims, then the Payments view
Applies the deductible flag for the reserve across payments.
Claims Workflows
Siebel Claims uses many workflows processes, which, for example, are activated when a user clicks a particular button, such as the Submit Payment button in the Payments view. Table 25 shows the workflows for Siebel Claims.
Table 25.
Workflows for Siebel Claims Description Adds an adjuster position to a claim. For each adjuster for the current reserve, it checks if the position is part of the claim team, and if not, it adds the position to the claim team. Calls the FINS Claims Evaluate Fraud Potential and FINS Claims Calculate Fraud Score BRPs and displays a popup message. Used In Adjuster field in the Claims, then the Reserves view
Workflow Name FINS Claims Add Reserve Position to Claim Team
FINS Claims Call Evaluate SIU Potential Process
Evaluate SIU Potential button in MyClaims view
14 5
Table 25.
Workflows for Siebel Claims Description Calls the FINS Claims Evaluate Subrogation Potential and FINS Claims Calculate Combined Score BRPs to initialize the realtime rule score and calculate the subrogation combined score. Creates a new revision of the policy and returns the new policy ID. Sends a search request to the ISO database. Updates Siebel Insurance with the results from the ISO database search. Imports the OFAC XML data to the Siebel database. Opens the reserve for a claim. Used In Evaluate Subrogation Potential button in MyClaims view
Workflow Name FINS Claims Call Evaluate Subrogation Potential Process
FINS Claims Get Policy Details Process FINS Claims ISO Search Request FINS Claims ISO Search Response FINS Claims OFAC Data Import Process FINS Claims Open Reserve Process FINS Claims Payment Create Activity Alert Sub Process FINS Claims Payment Validation Sub Process FINS Claims Approval Manager Process FINS Claims Payments Create Payments Process FINS Claims Payments Inbox Action SubProcess FINS Claims Payments Inbox Drilldown Process FINS Claims Payments Inbox GotoView SubProcess
Get Policy button in Claims, then the Loss Details -Auto view Submit button in ISO Database Search view Submit button in ISO Database Search view Submit Payment button in Claims, then the Payments view Open Reserve button in Claims, then the Reserves view Submit Payment button in Claims, then the Payments view Submit Payment button in Claims, then the Payments view Submit Payment button in Claims, then the Payments view Generate Payment button in Claims, then the Invoices view Inbox screen for payment approval Inbox screen for payment approval Inbox screen for payment approval
Creates an activity of type Alert, and assigns it to the subrogation or fraud unit. Validates the payment record (Submit Payment Validation Ruleset) and also checks that it is not a duplicate payment. Checks whether the Inbox item is approved. If so, updates the proper Status value in the original request. Creates the bundled Payment record based on the selected invoice records. Checks whether additional approvals are required when a user approves an Inbox item. Fetches the proper payment when the user clicks on the Inbox item and invokes a view navigation subprocess. Navigates to the Claim Payments view with the given payment information.
146
Table 25.
Workflows for Siebel Claims Description Checks whether the Inbox item is approved. If so, updates the proper Status value in the original request. Navigates to the Claims Payments view. Used In Inbox screen for payment approval Submit Payment button in Claims, then the Payments view Submit Payment button in Claims, then the Payments view Submit Payment button in Claims, then the Payments view Submit Payment button in Claims, then the Payments view Submit Payment button in Claims, then the Payments view Submit Payment button in Claims, then the Payments view Void button in Claims, then the Payments view
Workflow Name FINS Claims Payments Status Update SubProcess FINS Claims Payments Query Payments GotoView SubProcess FINS Claims Submit Payment Check Draft Authority Limits SubProcess FINS Claims Submit Payment Check OFAC Status SubProcess FINS Claims Submit Payment Process FINS Claims Submit Payment Updated Reserves FINS Claims Submit Payment Validate Reserves SubProcess FINS Claims Void Payment Process
Checks whether the payment limits for the user are exceeded. If so, sends the item to the appropriate supervisors Inbox for approval. Checks the imported OFAC data for the payee. Invokes the main submit payment process.
Updates the Claims Reserve totals during the processing of a claims payment. Checks to verify that there is enough reserve in the Claims Reserve totals before allowing the workflow to process a claims payment. Cancels a payment that was generated successfully during the Submit Payment process. Sets the payment status to void and reverses the reserve outstanding made during the Submit Payment process. Also, creates an activity for the logged in user indicating that a payment has been cancelled.
14 7
148
11 Managing Life and Annuity Policies

This chapter is about working with life and annuity policies in Siebel Insurance. It includes the following topics: About Managing Life and Annuity Policies on page 149 Scenario for Life and Annuity Policies on page 150 Process of Managing Life and Annuity Policies on page 151 Defining Life or Annuity Insurance Products on page 152 Defining Life or Annuity Insurance Coverages on page 152 Administering Assessment Templates on page 152 Providing Life and Annuities Quotes on page 153 Ordering Underwriting Reports on page 154 Adding a Beneficiary on page 154 Submitting Transaction Requests on page 155 Viewing Value History Information on page 156 Setting Up Payment Plans on page 156
About Managing Life and Annuity Policies

The Life & Annuities screen allows users to create and manage a variety of individual life insurance and annuity policies. Administrators can set up life and annuity plans in the Insurance Administration screen. Table 26 lists some common individual life insurance and annuity products.
Table 26. Product Term Life
Life and Annuities Products Description Insures a life for a specified period of time. If the insured dies during the term, a benefit is paid. If the policy is not renewed and the insured dies after the term, no benefit is paid. Often referred to as permanent insurance because it provides a death benefit and a savings feature. The insurance accumulates a cash value, and the policy owner can generally borrow up to 95% of the cash value of the policy.
Whole Life
14 9
Managing Life and Annuity Policies Scenario for Life and Annuity Policies
Table 26. Product
Life and Annuities Products Description A form of whole life insurance in which the face amount and the cash value fluctuate according to the investment performance of a separate account fund. The policy holder can choose how a portion of the premium is invested. An insurance policy characterized by flexible premiums and cash values. Universal Life policies do not allow the policy holder to choose how premiums are invested. A form of annuity in which the rate of interest on the annuity account value is guaranteed (fixed) for a specific period. A form of annuity in which the rate of return on the account value fluctuates according to the investment performance of a separate account fund. The annuity owner can choose how to invest a portion of the premium. A policy that allows you to accumulate funds that will be payable in a lump sum at a future date. The money accumulates tax-free. If the insured dies before the pay-off date, the full face value of the policy is paid to the beneficiaries.
Variable Life
Universal Life
Fixed Annuity Variable Annuity
Endowment and Annuity
For more information on views common to all policy screens, see Common Policy Views on page 160.
Scenario for Life and Annuity Policies

This scenario features sample tasks performed by a Siebel administrator and a licensed sales representative. Your company might follow a different workflow according to its business requirements. In this scenario, a Siebel administrator defines life and annuity coverages and creates assessment templates. A licensed sales representative for a life insurance company is on the phone with a prospective customer who has called to request a quote for Variable Life insurance. She searches for the contact in Siebel Insurance and finds that the customer is part of an existing household. She adds a new life quote as well as data about the type of policy and the proposed insured. Next, she fills out a rating questionnaire for the prospect and creates an underwriting report. Then, she adds information about coverages and amounts. After that, she adds beneficiaries, and then sets up a payment plan with a bill-to address. After the data has been collected, she submits it to an external rating engine to determine the premium. She gives the prospect a verbal quote for the policy and the customer agrees to purchase it. Then, she follows the procedures implemented by her company to submit the policy application for underwriting. After the policy is issued, she can submit loan, transfer, withdrawal, and surrender requests. End users are the sales representatives who manage customer requests. They enter information to: Generate a life insurance or annuity quote
150
Managing Life and Annuity Policies Process of Managing Life and Annuity Policies
Add underwriting information or order an underwriting quote Add a beneficiary Set up a payment plan and add a bill-to-address Submits the policy application for underwriting
Process of Managing Life and Annuity Policies

This section details sample tasks often performed by administrators and end-users when managing life and annuity policies. Your company might follow a different process according to its business requirements.
The administration tables of Siebel Insurance store definitions of important insurance constructs such as coverages and coverage options information. These tables can be used to define a flexible set of insurance administrative data. Within the base product, the administrative tables are used to define life insurance coverages and limits. The administration tables for Life & Annuities are in the Administration - Insurance screens Life & Annuity Coverages view. The following list shows tasks administrators typically perform to manage life and annuity policies: Defining Life or Annuity Insurance Products on page 152 Defining Life or Annuity Insurance Coverages on page 152 Administering Assessment Templates on page 152
NOTE: Only administrators can change entries in the Administration - Insurance screen.
End-User Procedures
The following list shows tasks end users typically perform when managing life and annuity policies: Providing Life and Annuities Quotes on page 153 Ordering Underwriting Reports on page 154 Adding a Beneficiary on page 154 Submitting Transaction Requests on page 155 Viewing Value History Information on page 156 Setting Up Payment Plans on page 156
15 1
Managing Life and Annuity Policies Defining Life or Annuity Insurance Products
Defining Life or Annuity Insurance Products

As an administrator, you can add products to the Siebel database and add the product to a product line, if applicable. This section describes the procedure for setting up products in general terms. For more information about defining products, see Siebel Product Administration Guide.
To add an insurance product 1 2

Navigate to the Site Map, Administration - Product, and then the Products view. In the Product form, add a record, and complete the necessary fields.
In the Category field, select Life & Annuity.
Defining Life or Annuity Insurance Coverages

After defining life and annuity products, you might need to add coverages.
To define a life or annuity coverage 1 2

Navigate to the Site Map, Administration - Insurance, and then Life & Annuity Coverages. In the Life & Annuity Coverages list, add a record and complete the necessary fields. You have defined the coverage type and levels for a life or annuity insurance product.
3 4
In the Coverage Options list, add a record and type a coverage option. Repeat Step 3 for each coverage option you want to add.
Administering Assessment Templates

There are three types of assessment templates that are administered by sales administrators: Rating Reinstatement Underwriting
Each template is a collection of questions designed to obtain information needed to rate, reinstate, or underwrite a policy. They are all administered in the Sales Assistant Administration screens Sales Assessment Templates view. For more information, see Siebel Applications Administration Guide.
To administer an assessment template 1

Navigate to the Site Map, Administration - Data, and then Sales Assessment Templates.
152
Managing Life and Annuity Policies Providing Life and Annuities Quotes
In the Assessment Templates list, add a record.

In the Type field, select Life & Annuity. Complete the remaining fields.
In the Assessment Attributes list, add a record and complete the necessary fields.
In the Name field, specify a question, such as Have you used any form of nicotine products in the last 12 months?.
For each assessment attribute entered, in the Attribute Values list, add a record and complete the necessary fields.
a b
In the Value field, add a possible answer (such as Yes or No) to the question defined in the Assessment Attributes list. In the Score field, add a numeric value that represents how important that answer is to the assessment. NOTE: You need to add one record for each potential answer to the question created in the Assessment Attributes list. For example, if a question requires a yes or no answer, you will need two Attribute Values records, one with a value of Yes and one with a value of No.
Providing Life and Annuities Quotes

In Siebel Insurance, a quote is a policy that has not been issued. End users can provide a quote for a new policy or for a change to an existing policy. For a life insurance quote, users need to specify coverage information in the Coverages view tab. After the data has been collected, users can submit it to an external rating engine or illustration system to determine an initial premium, future account value, future annuity payments, or other calculations. Coverages might be defaulted to a standard set (through configuration) or manipulated through the Questionnaire and Coverages views to further refine the quote. Users can collect additional data to aid in the underwriting and administration of the quote.
To generate a life insurance or an annuity quote 1 2

Navigate to the Life & Annuities, then the Life Policy List view. In the Policies/Quote list, add a record and complete the necessary fields.

To request a life insurance quote, in the Contract Type drop-down list, select Life Quote. For an annuity quote, in the Contract Type drop-down list, select Annuity Quote.
NOTE: Additional fields are available in the More Info view tab.
3 4
Drill down on the Policy # hyperlink. Click the Participants view tab and scroll down to the Contacts list.
In the Contacts list, add a new record for each new participant.
15 3
Managing Life and Annuity Policies Ordering Underwriting Reports
In the new record, complete the fields. CAUTION: Make sure you select the Named check box for each Contact that will be covered under the policy. If you do not check this box, the Contact will not appear in the Questionnaire view.
c 5 6 7
Repeat Step 4 for each participant to add to the policy.
For all quotes, click the Questionnaire view tab. In the Insured/Annuitant list, select a record. Scroll down to the Questionnaire Templates list and add a new record.
a b c 8 9
In the Template Name field, click the select button. In the Select Assessment Template dialog box, in the Template Name field, select the desired template and click OK. Step off the record to save the record and select the saved record. The questions appear in the Questionnaire list.
In the Questionnaire list, complete the value field for each question. For a life insurance quote, click the Coverages view tab.
10 In the Coverages list, add a record and complete the necessary fields.

After end users add the necessary underwriting information, they can order underwriting reports for a policy.
To order an underwriting report 1 2 3 4 5

Navigate to the Life & Annuities screen. In the Policies/Annuities list, select a policy. Click the Underwriting Reports view tab. In the Underwriting Reports list, add a record and complete the necessary fields Follow the procedures defined by your company to submit orders for underwriting reports.
Adding a Beneficiary
End users can add or make changes to policy beneficiaries.
To add a beneficiary 1 2
Navigate to the Life & Annuities screen. In the Policies/Quotes list, drill down on a policy.
154
Managing Life and Annuity Policies Submitting Transaction Requests
Click the Beneficiaries view tab and review the three view links:

Beneficiary Class. To add or change classes of individuals, such as all my children. Individual Beneficiary. To add or change beneficiaries. Organizations. To add or change organizations.
4 5 6
Click the appropriate view link. In the Coverage Component list, select the desired record. Scroll down to the lower list, add a record and complete the necessary fields.
Submitting Transaction Requests

End users can submit transaction requests for: Loans Transfer of funds Withdrawal or surrender of funds
To submit a loan request 1 2 3 4 5 6

Navigate to the Life & Annuities screen. In the Policies/Quotes list, drill down on a policy. Click the Transaction Request view tab. From the Transaction Requests view link list, select Loans. In the Loans list, add a record and complete the necessary fields. Follow the procedures defined by your company to submit requests for loans.
Submitting a Transfer Request

Use the following procedure to submit a transfer request.
To submit a transfer request 1 2 3 4 5 6

Navigate to the Life & Annuities screen. In the Policies/Quotes list, drill down on a policy. Click the Transaction Request view tab. From the Transaction Requests view link list, select Transfers. In the Transfers list, add a record and complete the necessary fields Follow the procedures defined by your company to submit requests for transfers.
15 5
Managing Life and Annuity Policies Viewing Value History Information
Submitting a Withdrawal or Surrender Request

Use the following procedure to submit a withdrawal or surrender request.
To submit a withdrawal or surrender request 1 2 3 4 5 6

Navigate to the Life & Annuities screen. In the Policies/Annuities list, select a policy. Click the Transaction Request view tab. From the Transaction Requests view link list, select Withdrawals & Surrenders. In the Withdrawals & Surrender list, add a record and complete the necessary fields Follow the procedures defined by your company to submit requests for withdrawals or surrenders.
Viewing Value History Information

End users can use the Value History view to display cash values. Usually, this requires integration of Siebel Insurance with a policy administration system. For more information, see Siebel Integration Messages on page 193.
To display value history 1 2 3 4

Navigate to the Life & Annuities screen. In the Policies/Quotes list, drill down on a policy. Click the Policy Values view tab. Select the Value History view link. NOTE: Choose the Value History Chart view link to see value history data in chart format.

End users can set up payment plans and payment method details for life insurance and annuity policies.
To set up a payment plan 1 2 3

Navigate to the Life & Annuities screen. In the Policies/Quotes list, drill down on a policy. Click the Payment Plans view tab.
156
Managing Life and Annuity Policies Setting Up Payment Plans
In the Payment Plans list, add a record and complete the necessary fields. NOTE: The payment method you choose determines the type of list that appears. For example, if you select Electronic Funds Transfer as a payment method, the Payroll Deduction Plan/ Electronic Funds Transfer Details form appears after you save the record.
15 7
Managing Life and Annuity Policies Setting Up Payment Plans
158
12 Managing Group Policies

This chapter describes how to manage group policies. It includes the following topics: About Group Policies on page 159 Scenario for Group Policies on page 161 Process of Managing Group Policies on page 161 Adding Group Insurance Products and Product Lines on page 162 Adding Group Insurance Rate Bands on page 163 Defining Activity Plan Templates for Group Policies on page 163 Defining Proposal Templates for Group Policies on page 164 Adding Group Policy Records on page 164 Importing Census Information on page 165 Adding Census Information in the Group Policies Screen on page 166 Adding Employee Classes for Group Policies on page 168 Designing Plans for Group Policies on page 168 How Enrollment Waiting Periods Affect the Start of Coverage on page 169 Reconfiguring Customizable Products in Plan Design on page 170 Generating Proposals for Group Policies on page 171 Managing Underwriting Information on page 171 Adding Eligible Members to Group Policies on page 172 Enrolling Members in Group Policies on page 173 Adding Beneficiaries to Group Policies on page 174 Setting Up Payment Plans for Group Policies on page 174
About Group Policies

Group policies are insurance policies sold to a group on behalf of its members. The group is the insured party and can be an employer purchasing insurance for its employees, a group of employers who are purchasing insurance together, or an association or club purchasing insurance for its members. Each group policy can offer many products. Group insurance products include group life, supplemental group life, group disability, group health, vision, and dental.
15 9
Managing Group Policies About Group Policies
Some group policies, especially those for larger groups, offer different products to different employee classes of group members. Examples of employee classes are salaried employees and hourly employees. Group members have the option to accept coverage that is available for their class. Group members who accept coverage are enrolled in the policy and are considered the primary member of the policy. Enrolled members are usually referred to as members (for health insurance) or policyholders (for other kinds of insurance). Primary members can choose products for themselves and for family members or dependents. Usually, different products are available for primary members and for other policy members. The Group Policies screen allows users to manage group insurance. Specifically, it allows end users to generate proposals, create policies and quotes, add employee classes, design plans, enroll members, and provide service for the policy. NOTE: In order to generate proposals from the Group Policies screen, you must purchase the Siebel Proposals & Presentations module.
Common Policy Views

Table 27 describes views common to all policy screens.
Table 27. View Tab Summary
Common Policy Screen Views Description Displays a summary of key data associated with a policy in a single view. Applicable to auto and property policies. Allows users to select coverages and limits for an individual policy. Displays claims recorded for an individual policy. Allows for the creation and retrieval of quotes prepared for a customer associated with an individual quote or policy. Proposals would normally show up in the quote process, but not later. Allows users to collect and manage underwriting information associated with an application. These reports are sometimes ordered during the application process and sometimes after an application is submitted. Allows users to collect and manage documents associated with an application. Applicable to auto and property policies. Allows users to collect and manage information describing other parties who have an interest in insured property. Examples include a loss payee for an automobile loan or a mortgagee on real property.
Rate Model Claims Proposals
Underwriting Reports Documents Third Parties
For more information on other insurance policy views, see Chapter 9, Managing Auto Policies, Chapter 11, Managing Life and Annuity Policies, Chapter 14, Managing Property Policies, and Chapter 15, Managing PUL Policies.
160
Managing Group Policies Scenario for Group Policies
Scenario for Group Policies

This scenario features sample tasks performed by a licensed sales representative. Your company might follow a different workflow according to its business requirements. In this scenario, a licensed sales representative for an insurance company is on the phone with an insurance agent. The insurance broker has called on behalf of a prospective customer who wants to offer insurance to its employees at group rates. In Siebel Insurance, the sales representative adds a policy record for the company, which automatically assigns a unique policy number to the company. Then he imports census information for the company using the electronic file he received from the broker (alternatively, the broker might import the census himself through the Siebel Agent Portal). Next, he sets up employee classes, and adds a plan design by adding products for the policy. The plan design information and census data can be sent to the insurance companys rating engine to generate a quote for this policy. Next, he uses a template to generate a proposal, which he then sends to the prospect. Two weeks later, he receives an email message from the broker indicating that the prospect has called back and will probably purchase a policy, but requires a revised proposal. He selects a group insurance plan according to the needs of the prospect. Next, he schedules an activity as a reminder to return the call with the revised premium information. The prospect accepts the revised proposal. Now the sales representative needs to complete the procedures necessary to issue a policy. This includes collecting information about group members and about billing and payment preferences. He follows the procedures implemented by his company to submit the policy for issuance and billing.
Process of Managing Group Policies

This topic details sample tasks often performed by administrators and end-users when managing group policies. Your company might follow a different process according to its business requirements.
The following list shows tasks administrators typically perform to manage group policies: Adding Group Insurance Products and Product Lines on page 162 Adding Group Insurance Rate Bands on page 163 Defining Activity Plan Templates for Group Policies on page 163 Defining Proposal Templates for Group Policies on page 164
NOTE: Only those with Siebel administrator responsibilities can change entries in the Insurance Administration and Product Administration screens.
16 1
Managing Group Policies Adding Group Insurance Products and Product Lines
End-User Procedures
The following list shows tasks end users typically perform when managing call group policies: Adding Group Policy Records on page 164 Importing Census Information on page 165 Adding Census Information in the Group Policies Screen on page 166 Adding Employee Classes for Group Policies on page 168 Designing Plans for Group Policies on page 168 Reconfiguring Customizable Products in Plan Design on page 170 Generating Proposals for Group Policies on page 171 Managing Underwriting Information on page 171 Adding Eligible Members to Group Policies on page 172 Enrolling Members in Group Policies on page 173 Adding Beneficiaries to Group Policies on page 174 Setting Up Payment Plans for Group Policies on page 174
Adding Group Insurance Products and Product Lines

As an administrator, you can add products to the Siebel database. This section describes the procedure for setting up products and product lines in general terms. You can also specify that a product line is one that your company contracts agencies to sell, or that the state licenses agencies to sell, or both. For more information about adding product and product lines, see Siebel Product Administration Guide and Siebel Applications Administration Guide.
To add a group insurance product 1 2 3 4 5

Set up the product class structure, including product class attributes. Add the products in the Product Administration screen and associate them with the appropriate class. In the Category field in the Products form, select Group Insurance. Include the product in a product line. Specify a product line type:
a b
162
From the application-level menu, choose View, Site Map, Application Administration, and then Product Lines. In the Product Line list, select one or both of the following fields:
Managing Group Policies Adding Group Insurance Rate Bands
Contracting. To specify that the product line is one that your company contracts agencies to sell. This product line will appear to end users as a choice in the Lines of Business dialog box in the Partners, Contracts view tab. Licensing. To specify that the product line is one that agencies can be granted a state license to sell. This product line will appear to end users as a choice in the Lines of Business dialog box in the Partners, Licenses & Appointments view tab.
A check box appears in the middle of the field.
c 6
Click in a blank check box to select the product line type or click the X in a check box to clear it.
Set up the Customization Product by defining configuration rules and specifying the user interface. For more information, see the section on creating customizable products in Siebel Product Administration Guide.
Adding Group Insurance Rate Bands

After you add a product in the Product Administration screen, you can use the Insurance Administration screen to associate a rate band with a product. A rate band is pricing information about the deductible, the premium, and the payroll deduction for each insurance product.
To add a rate band 1 2 3

From the application-level menu, choose View, Site Map, Insurance Administration, and then Health and Group Products. In the Products list, select a product. In the Rate Bands list, add a record and complete the necessary fields.
Defining Activity Plan Templates for Group Policies

Activity Plan Templates allow you to create and manage activities related to group policies. You define templates using the Administration - Data screen Activity Templates and Activity Template Details views.
To create an activity plan template 1 2 3 4 5

Navigate to the Site Map, Administration - Data, and then Activity Templates. In the Activity Plan Templates list, add a record. In the Name field, type a name for the template. In the Type field, choose FINS Group Policy. Complete the remaining necessary fields.
16 3
Managing Group Policies Defining Proposal Templates for Group Policies
For more information, see Siebel Applications Administration Guide.
Creating Activities for the Template

Use the following procedure to create activities for the template.
To create activities for the template 1 2 3 4 5 6

Navigate to the Site Map, Administration - Data, and then Activity Templates. In the Activity Plan Templates list, select a template. Click the Activity Template Details view tab. In the Activity Template Details list, add a record. Complete the necessary fields for each activity assigned to the template. From the drop-down list, choose an activity type. NOTE: Repeat Step 2 through Step 6 to add activities to the template.
Save the activity.
Defining Proposal Templates for Group Policies

Proposal Templates with a particular definition allow you to create and manage proposals related to group policies. You define templates using the Administration - Document screen Proposal Templates view.
To create an proposal template for group policies 1 2 3 4 5

Navigate to Site Map, Administration - Document, and then Proposal Templates. In the Proposal Templates list, add a record. In the Name field, type a name for the template. In the Category field, select Insurance Proposal. Complete the remaining necessary fields.
For more information, see Siebel Applications Administration Guide.
Adding Group Policy Records

Adding a group policy record is the first step in generating a policy proposal or issuing a group policy. After end users add a policy record, they must set up employee classes, add a policy plan design, and generate a policy proposal. If the customer accepts the proposal, they add eligible members, enroll members who elect coverage under the plan, and set up policy payment plans.
164
Managing Group Policies Importing Census Information
To add a policy record 1 2

Navigate to the Group Policies screen. In the Policies/Quotes list, add a record and complete the necessary fields.
Importing Census Information

Insurance companies often receive group insurance census information from external sources. For example, an insurance broker collects this data and provides it to the insurance company as a comma separated text file. End users can use the Group Policies Census view to import the census data into Siebel Insurance. NOTE: Census data can also be imported from the Companies Census view. Both detailed and segmented census data can be imported for each census. Usually, either only detailed or segmented census information is added for a company. However, both types of census information can be added. Census data can also be imported by the originators, such as insurance brokers or employer groups, using Siebel Agent Portal or Siebel Group Portal. For more information about these two products, see Siebel Partner Relationship Management Administration Guide. Census data can also be entered manually. See Adding Census Information in the Group Policies Screen on page 166.
To import detailed census data 1 2 3 4 5 6

Navigate to the Group Policies screen. In the Policies/Quotes list, drill down on a policy. Click the Census view tab. Click New to create a new census record and complete the fields. In the Census list, from the view link list, select Detailed Census. Scroll down to the Employee list and click Import.
16 5
Managing Group Policies Adding Census Information in the Group Policies Screen
In the Import dialog box, locate the file from which to import data and set the remaining parameters. Some parameters are described in the following table. Parameter Input Format Input Source Conflict Resolution Description Select either comma separated text or tab delimited text file type. Select Auto Mapping. Choose how to handle data conflicts. Defaults to Overwrite Existing Record.
The field mappings appear in a dialog box showing how each import field maps to the Siebel field. By default fields with matching labels are mapped to each other.
To add or change a field mapping:
a b c 9 a b c
Highlight the field in the Import Field list Highlight the field to map to in the Siebel Field list Click Update Mapping
To remove an existing field mapping: Highlight the field in the Import Field list Highlight <ignore this field> to disregard the import field Click Update Mapping
10 Click Next.
Importing Segmented Census Data

The census data is imported into the Siebel application and appears in the Employee List.
To import segmented census data

Follow the steps in Importing Census Information on page 165 except select Segmented Census in Step 5. The census data is imported and appears in the Employee Count list.
Adding Census Information in the Group Policies Screen

End users can add census information for companies that request a quote or proposal for a group insurance policy. To add census information, end users must:
166
Managing Group Policies Adding Census Information in the Group Policies Screen
1 2 3
Add a policy in the Group Policies screen Add census information using the instructions in the procedures in this topic. Associate the census with the policy using the instructions in the Associating a Census with a Policy on page 167 procedure.
Census data can also be automatically imported. See Importing Census Information on page 165.
To add census information 1 2 3 4

Navigate to the Group Policies screen. In the Policies/Quotes list, drill down on a policy. Click the Census view tab. In the Census list, from the view link list, select Segmented Census or Detailed Census.

Segmented Census. Add information for groups of employees. Detailed Census. Add information for individual employees.
NOTE: Usually, either only detailed or segmented information is added for a single census. However, information can be added for both.
5 6
In the Census list, add a record and complete the necessary fields. For a Segmented Census:

Scroll down to the Employee Count list. In the Employee Count list, add a record and complete the necessary fields.
For a Detailed Census:

Scroll down to the Employee List list. In the Employee List list, add a record and complete the necessary fields.
Associating a Census with a Policy

Use the procedure below to associate a census with a policy.
To associate a census with a policy 1 2 3

Navigate to the Group Policies screen. In the Policies/Quotes list, select a policy. In the Policy Census field of the Policies/Quotes form, click the select button. The Pick Group Census dialog box appears, showing each census available for that policy.
In the Pick Group Census dialog box, select a census and click OK.
16 7
Managing Group Policies Adding Employee Classes for Group Policies
Adding Employee Classes for Group Policies

Some group policies, especially those for larger groups, offer different products to different employee classes of group members. Examples of employee classes are salaried employees and hourly employees. Each employee class offers a unique combination of products, product options, and product rates. Users can use the Classes view to add or make changes to employee classes.
To add an employee class 1 2 3 4

Navigate to the Group Policies screen. In the Policies/Quotes list, select a policy. Click the Classes view tab. In the Classes list, add a record and complete the necessary fields.
Designing Plans for Group Policies

End users can design plans for group polices by adding information about products, product classes, and rate bands. A rate band is pricing information about the deductible, the premium, and the payroll deduction for each insurance product. The following lists are available in the Plan Design view: Product Attributes. This view contains the Plan Design Product list and the Attributes list. Use the Plan Design Product list to associate a product with the policy that appears in the Group Policy form. Use the Attributes list to view attribute information and change attribute values. Product Classes. This view contains the Plan Design Product list and the Classes list. Use the Classes list to select employee classes that you want to associate with the selected product. Product Class Matrix. This view contains the Plan Design Product Class Matrix list. In this list, you associate an employee class with the selected product. Product Class Rate Bands. This view contains the Plan Design Product Class Rate Band list. Use this list to associate a rate band with the selected product/class.
To add a plan design 1 2

Navigate to the Group Policies screen. In the Policies/Quotes list, drill down on a group policy.
168
Managing Group Policies How Enrollment Waiting Periods Affect the Start of Coverage
Click the Plan Design view tab. The Plan Design Product list appears, showing the selected policy. NOTE: If you need to add a product, in the Plan Design Products list, click New and complete the fields.
4 5 6
From the view link list, select Product Attributes and scroll down to the Attributes list. In the Attributes list, change the appropriate information. From the view link list, select Product Classes and scroll down to the Classes list.
a b c
In the Classes list, click New to associate an employee class with the selected product. In the Class Name field, click the select button. In the Pick Class dialog box, select an employee class from the Class Name field and click OK.
NOTE: Only employee classes available for the selected product appear in the Pick Class dialog box. You can add employee classes to the list in this dialog box by using Adding Employee Classes for Group Policies on page 168.
7 8
From the view link list, select Product Class Matrix.
a a b c d
In the Product Class Matrix list, check the appropriate product column for each class.
From the view link list, select Product Class Rate Bands. In the Product Class list, select a record with the appropriate product and class and scroll down to the Rate Bands list. In the Rate Bands list, click New to associate a rate band with the selected product and class. In the Rate Bands field, click the select button. In the Pick Product Rate Bands dialog box, select a Rate Band and click OK.
NOTE: Only available rate bands for the selected product appear in the Pick Product Rate Bands dialog box. Rate Bands are created in the Administration - Insurance, then the Health and Group Products view. For more information about how to add Rate Bands, see Adding Group Insurance Rate Bands on page 163. To generate a proposal for this plan, see Generating Proposals for Group Policies on page 171.
How Enrollment Waiting Periods Affect the Start of Coverage

You can control how Siebel Insurance calculates the start of coverage by defining the enrollment waiting period in the Group Policies screen. When you add a Plan Design (see Designing Plans for Group Policies on page 168), you define Product Classes that you then associate with a specific product. In the Classes list you can specify the Waiting Period, that is the number of days that must pass prior to the start of coverage. The actual start of coverage appears in the Effective Date field in the Group Policies, Enrollment view. The Waiting Period you specify in the Plan Design, Classes list directly impacts this Effective Date.
16 9
Managing Group Policies Reconfiguring Customizable Products in Plan Design
By default, Siebel Insurance has the following defined rules: If a Waiting Period is specified, the Effective Date is set to the number of waiting days from todays date. If a Waiting Period is not specified, the application checks today's date. If that date is before the 15th of the month, the Effective Date is set to the first of the month. If that date is after the 15th of the month, the Effective Date is set to the first of the following month.
When a user enrolls a new member in the Group Policy, Enrollment view, the Effective Date field defaults to a value based on these two rules and the application sets the Status field to Waiting. The FINS Member Enrollment Rules Workflow enforces these rules. Users can invoke this workflow by submitting a repeating component job request that repeats every 24 hours in batch mode. It checks the Effective Date of existing enrollment records and updates the Status from Waiting to Active if: The Effective Date of a record is less than or equal to todays date The Status is still set to Waiting
For more information on component job requests, see Siebel System Administration Guide.
Reconfiguring Customizable Products in Plan Design

End users can dynamically reconfigure customizable products by using the Customize Plan button in the Product Attributes list. The Customize Plan button is only available if Siebel Configurator was installed and the selected product was created as a customizable product in Siebel Configurator. For more information, see the chapters about customizable products in the Siebel Product Administration Guide.
To dynamically reconfigure customizable products in plan design 1 2 3 4 5

Navigate to the Group Policies screen. In the Policies/Quotes list, drill down on a group policy. Click the Plan Design view tab. Select the Product Attributes view link. In the Product list, click Customize Plan. A configuration session launches and a selection page appears. The changes made in the configuration session are reflected in the line items in the Attributes list.
170
Managing Group Policies Generating Proposals for Group Policies
Generating Proposals for Group Policies

A proposal is a written quote for a policy. Before generating a proposal, end users must add the policy, set up classes, and add the policy plan design. Usually, the last step in adding the plan design is to activate the software program your company uses to rate policies. For more information, see Designing Plans for Group Policies on page 168. Proposals are built off of pre-defined templates. For more information on creating proposal templates, see the chapter on proposals in Siebel Applications Administration Guide. NOTE: Only those with Siebel administrator responsibilities can create or change proposal templates from the Administration - Document screen.
To generate a proposal 1 2 3 4 5 6
Navigate to the Group Policies screen. In the Policies/Quotes list, drill down on a policy. Click the Proposals view tab. In the Proposals list, add a record. In the new record, select the appropriate template. Click Generate Draft.
Managing Underwriting Information

End users can use the Underwriting Reports view tabs on the Group Policies screen to collect and manage underwriting information.

Navigate to the Group Policies screen. In the Policies/Quotes list, drill down on a policy. Click the Underwriting Reports view tab.
17 1
Managing Group Policies Adding Eligible Members to Group Policies
In the Underwriting Reports list, attach the information and complete the necessary fields. Some fields are described in the following table. Field Type Status Comments Type of underwriting report or information being requested. Status of the current report. Valid options include: Ordered Received Requested Received Submitted
Date automatically generated by the application when a new record is created. Date the underwriting report was received.
Viewing Historical Underwriting Information

Use the procedure below to view historical underwriting information.
To view historical underwriting information 1 2 3

Navigate to the Group Policies screen. Click the Group History view tab. From the view link list in the Group History list, select a type of underwriting information:

Rates Prior Insurance History Premium/Claim History Large Claimant History
Adding Eligible Members to Group Policies

After a customer accepts a group policy plan, end users can add or make changes to eligible members. Eligible members can accept or decline group policy coverages. Members who accept coverage can be enrolled in the plan.
To add an eligible member 1 2

Navigate to the Group Policies screen. In the Policies/Quotes list, drill down on the policy.
172
Managing Group Policies Enrolling Members in Group Policies
3 4 5
Click the Eligible Members view tab. In the Primary Members list, add a record. In the Add Members dialog box, select an existing record, or add a record and complete the necessary fields. NOTE: During implementation, you will import the eligible members from the final census. For more information, see Importing Census Information on page 165.
Enrolling Members in Group Policies

Group members who accept coverage are enrolled in the policy and are considered the primary member of the policy. End users use the Enrollment view to enroll eligible members, including the primary member and dependents, who accept coverage in the plan.
To enroll a member 1 2 3 4
Navigate to the Group Policies screen. In the Policies/Quotes list, drill down on the policy. Click the Enrollment view tab. In the Primary Members list, select the primary member to enroll and scroll down to the Member Products list.
a b 5
In the Member Products list, add a record and complete the necessary fields. Repeat Step 4 for each product you would like to add for this primary member.
All the products related to this primary members enrollment are added. Scroll down to the Insured Members list.
a b c d
In the Insured Members list, click New to enroll the primary member and the dependents. In the Last Name field, click the select button. In the Pick Contacts dialog box, select the primary member that you would like to associate with the selected product and click OK. In the Insured Members list, complete the remaining fields. NOTE: Add dependent members in the Pick Contacts dialog box by clicking on the New button and completing the fields.
Repeat Step 4 and Step 5 for each member you would like to enroll.
When you finish, all enrolled members, including the primary member, appear in the Insured Members list.
17 3
Managing Group Policies Adding Beneficiaries to Group Policies
Adding Beneficiaries to Group Policies

Some group policies, such as group life insurance policies, require that members designate one or more policy beneficiaries. End users can use the Member Beneficiary view to add or make changes to group policy beneficiaries.
To add a beneficiary 1 2 3 4 5 6
Navigate to the Group Policies screen. In the Policies/Quotes list, drill down on the policy. Click the Member Beneficiary view tab. In the Member Life Products list, select a primary member record. Scroll down to the Insured Members list and select a member for whom to add a beneficiary. In the Beneficiary list, add a record and complete the necessary fields.
Setting Up Payment Plans for Group Policies

End users can set up payment plans, including details about payment methods, for group insurance policies.
To set up a payment plan for a group policy 1 2 3 4 5

Navigate to the Group Policies screen. In the Policies/Quotes list, drill down on the policy. Click the Payment Plans view tab. In the Pay Plans list, add a record and complete the necessary fields. Scroll down to the Payment Details form and update the statement information.
a b
In the Last Name field, click the select button. In the Pick Contact dialog box, select a name and click OK.
174
13 Managing Partners and Agencies

This chapter describes how to manage partners and agencies. It includes the following topics: About Partners and Agencies on page 175 Scenario for Working with Partners and Agencies (Users) on page 176 Process of Managing Partners and Agencies (Users) on page 176 Adding New Partners on page 177 Setting Up Siebel Insurance eService Partners Locators on page 177 Adding Agents on page 178 Adding Information Associated with an Agent on page 178
About Partners and Agencies

Siebel Insurance allows you to manage partners and agencies. Partners include service providers, aggregators, and insurance agencies. Agencies are organizations that act on behalf of insurance companies to sell insurance policies. Agents and brokers are the licensed sales representatives who sell the insurance policies. For many insurance companies, agencies are often the most important type of partner.
Tracking partner information is important because for many insurance, partners such as banks, agencies, and brokerages often function as a primary revenue channel. NOTE: Adding partners on the Partners screen only allows you to track and monitor partner information. If you want to share data with a partner, the partner must be upgraded to a Siebel Organization. To perform this and other Partner administration tasks, you use the Administration Partner screen. For more information, see Siebel Partner Relationship Management Administration Guide. End users use the Agents screen for insurance-related procedures such as: Adding agents Viewing agent information Creating service requests or activities for agents Tracking information about contracts, licenses, appointments, registration, errors and omissions, policies, and quotes
NOTE: Under the Party Model, where contacts include all persons, individuals added in the Agents business component are also members of the Contacts business component. Agents are a special subset of contacts who are engaged in the sales of Financial Services products.
17 5
Managing Partners and Agencies Scenario for Working with Partners and Agencies (Users)
Scenario for Working with Partners and Agencies (Users)

These scenarios feature sample tasks performed by insurance company employees. Your company might follow a different workflow according to its business requirements. In these scenarios, the end users are company employees who manage information in the field. They enter information to: Create a partner Add a contact that represents an agency Add new agents View information about existing agents Track agent information about contracts, licenses, appointments, registration status, errors and omissions, policies, and quotes Create service requests or activities for agents
Employee Adds a New Agency

In this scenario, an insurance company uses independent agencies as one of the channels for distribution of its insurance products. An employee for this insurance company needs to add a newly appointed agency to represent his companys products to consumers. His company has verified the qualifications of the agency, so he adds information about the agent. Then, he adds a new Partners record and adds information about the agencys errors and omissions coverage. Next, he navigates to the Licenses & Appointments view to record information about the agencys license. Finally, he adds a contact with the agency.
Company Signs a New Agent

An insurance company signs a new agent. A licensing and contracting coordinator for the company receives an interoffice mail containing the required paperwork. She enters the agents contact, license, appointment, and contract information into Siebel Insurance. Six months later, the agent moves to a new office. He forwards his new address and phone number to the sales representative who is his main contact at the insurance company. The sales representative locates the agent in Siebel Insurance and updates his address and phone number.
Process of Managing Partners and Agencies (Users)

This section details sample tasks often performed by end-users when managing partners and agencies. Your company might follow a different process according to its business requirements.
176
Managing Partners and Agencies Adding New Partners
The following list shows tasks end users typically perform when managing partners and agencies: Adding New Partners on page 177 Setting Up Siebel Insurance eService Partners Locators on page 177 Adding Agents on page 178 Adding Information Associated with an Agent on page 178
Adding New Partners

End users can create new partner records and make changes to existing service provider information.
To create a partner 1 2 3
Navigate to Partners, then the Partner List view. In the Partners form, add a record, and complete the necessary fields. In the Partner Type field, select the appropriate type; if this partner is a service provider, select Service Provider.
Setting Up Siebel Insurance eService Partners Locators

The Contact Us applet on the Siebel Insurance eService home page has a Locate Nearby Partners hyperlink. When users with the role of Insurance Member click this link, an applet opens in which they can perform a parametric search using location attributes that they select from drop-down lists. Users set up the records used in these searches in Siebel Insurance. For more information on Siebel Insurance eService, see Siebel eService Administration Guide Addendum for Industry Applications.
To set up a Partner Locator 1 2 3

Navigate to the Site Map, Partners, Partners List, and then the Locations view. In the Partners form, query for the desired partner. In the Locations list, add a record for each partner address and complete the necessary fields. When the record is saved, the application automatically populates the Latitude and Longitude fields. NOTE: The latitude and longitude values will not generate if any one value in the City, State, Zip Code, or Country fields is incorrect. For example, if the ZIP Code is incorrect, you will receive an error message. To correct this problem, navigate to the Application Administration, ZIP Code Administration view and make sure the Geo values for that city, state, and ZIP Code combination has been loaded. For more information, see Siebel eService Administration Guide.
17 7
Managing Partners and Agencies Adding Agents
Adding Agents
Agents are the licensed sales representatives who sell insurance policies. Adding an agent is the first step in managing procedures related to the agent.
To add an agent 1 2
Navigate to the Agents screen. In the Agents list, add a record and complete the necessary fields.
a b c
In the Partner field, click the select button. In the Partners dialog box, select a record and click OK, or click New to add a new partner. If adding a new partner, complete the fields.
NOTE: To add or change the columns displayed in the list, click the lists menu button and choose Columns Displayed.
Adding Information Associated with an Agent

Using the view tabs on the Agents screen, end users can track additional information related to agents including information about contracts, licenses and appointments, errors and omissions, National Association of Securities Dealers (NASD) registration, and policies and quotes.
To add additional information about an agent 1 2

Navigate to the Agents screen. In the Agents list, drill down on the desired agent and click the appropriate view tab from the following list:

Contracts. To add information about the agents contracts. Licenses and Appointments. To add information about licenses the agent holds. Errors and Omissions. To add information about the agents errors and omissions. Registration. To add information about the agents registration status. Policies/Quotes. To view policies and quotes for the agent.
In the selected view list, add a record and complete the necessary fields.
178
14 Managing Property Policies

This chapter describes how to manage property policies. It includes the following topics: About Property Policies on page 179 Scenario for Property Policies on page 179 Process of Managing Property Policies on page 180 Adding Property Types on page 181 Adding Property Coverages and Coverage Limits on page 181 Providing Quotes on page 182 Adding Underwriting Information on page 182 Querying for Property Underwriting Information on page 183 Ordering Underwriting Reports on page 183 Adding Scheduled Personal Property on page 183 Setting Up Payment Plans on page 184 Additional Property Policies Views on page 184
About Property Policies

Terminology for property insurance policies varies among insurance companies. For example, the same type of insurance could be referred to as fire insurance, homeowners insurance, home insurance, or property insurance. Using the procedures given in this chapter, you will be able to perform the administrator tasks of adding property types, property coverage, and coverage limits in the Insurance Administration views. End users, usually service and licensed sales representatives, use the Property Policies screen to create and manage property insurance policies. Specifically, they can generate quotes for a new policy or for a change in an existing policy, add underwriting information, order underwriting reports, add scheduled personal property to the system, and setting up a payment plan. For more information on views common to all policy screens, see Common Policy Views on page 160.
Scenario for Property Policies

This scenario features sample tasks performed by an administrator and a licensed sales representative. Your company might follow a different workflow according to its business requirements. In this scenario, a Siebel administrator adds property types, coverages, and coverage limits for his companys property policies.
17 9
Managing Property Policies Process of Managing Property Policies
A licensed sales representative for a property insurance company is on the phone with a customer buying a first home. The customer wants to switch from a renters policy to a homeowners policy. Using the fields on the Quick Quote view as a guide, the sales representative asks the customer a series of questions in order to gather enough information to provide an initial quote. Next, she adds more underwriting information, orders underwriting reports to request additional information, and adds scheduled personal property. After the data has been collected, she submits it to an external She gives the customer a verbal quote and ends the conversation. Two weeks later, the sales representative receives another call from the customer. The offer was rejected for the property she quoted a premium for, but an offer on another house was accepted. She adjusts the coverages and limits accordingly, and then gives the customer the revised premium information. The customer confirms an intent to purchase the quoted policy. The quote now needs to be prepared for eventual contract issuance. This includes collecting information about any parties that hold liens and mortgages against the insured property and billing and payment arrangements. Then the sales representative follows the procedures implemented by her company to submit the policy for issuance and billing. In this scenario, end users are sales representatives who service customers. They enter information to: Provide quotes Add underwriting information Order an underwriting report Add scheduled personal property to the system Set up a payment plan
Process of Managing Property Policies

This section details sample tasks often performed by administrators and end-users when managing property policies. Your company might follow a different process according to its business requirements.
The following list shows tasks administrators typically perform to manage property policies: Adding Property Types on page 181 Adding Property Coverages and Coverage Limits on page 181
NOTE: Only those with the required administrative responsibilities, such as Siebel administrators, can change entries in the Insurance Administration views.
180
Managing Property Policies Adding Property Types
End-User Procedures
The following list shows tasks end users typically perform when managing property policies: Providing Quotes on page 182 Adding Underwriting Information on page 182 Querying for Property Underwriting Information on page 183 Ordering Underwriting Reports on page 183 Adding Scheduled Personal Property on page 183 Setting Up Payment Plans on page 184 Additional Property Policies Views on page 184
Adding Property Types

The Insurance Administration view allows you to add and make changes to property types. You can use the existing fields to define the default values of property types, or you can add more fields using Siebel Tools. For more information, see Configuring Siebel Business Applications.
To add a property type 1 2

Navigate to the Site Map, Administration - Insurance, and then the Property Types. In the Property Type Administration list, add a record and complete the necessary fields.
Adding Property Coverages and Coverage Limits

The Property Coverage Administration view allows you to add and make changes to property coverages and property coverage limits. You can use the existing fields to define the default values of property coverages, or you can add more fields using Siebel Tools. For more information, see Configuring Siebel Business Applications.
To add a property coverage 1 2

Navigate to the Site Map, Administration - Insurance, and then the Property Coverages. In the Property Coverage Administration list, add a record and complete the necessary fields.
Adding a Property Coverage Limit

Use the following procedure to add a property coverage.
18 1
Managing Property Policies Providing Quotes
To add a property coverage limit 1 2 3 4

Navigate to the Site Map, Administration - Insurance, and then the Property Coverages. In the Property Coverage Administration list, select a record. Scroll down to the Coverage Limit list, and add a record. In the Limit field, type a coverage limit and complete the remaining fields.
Providing Quotes
In Siebel Insurance, a quote is a policy that has not been issued. End users can provide a quote for a new policy or for a change to an existing policy. The Quick Quote view provides a way to gather basic policy and rating information. The information collected through the Quick Quote view represents the minimum rating information needed to create an initial premium calculation.
To provide a property insurance policy quote 1 2 3 4 5

Navigate to the Property Policies screen. In the Policies/Quotes list, drill down on a policy. Click the Quick Quote view tab. In the Property Types list, add a record and complete the necessary fields. Scroll down to the Dwelling Rating form and complete the fields. NOTE: Coverages might be defaulted to a standard set (through configuration) or manipulated through the Rate Model view to further refine the quote. You can collect additional data to aid in the underwriting and administration of the quote.
Adding Underwriting Information

After end users provide a quote for a property policy, they can add additional information for underwriting.

Navigate to the Property Policies screen. In the Policies/Quotes list, drill down on a policy. Click one of the following view tabs and add a record.

Property Underwriting. To add property-related information. Outbuilding Underwriting. To add information related to outbuildings such as detached garages. Coverage Underwriting. To add other underwriting information, such as earthquake, farm, and brush hazard.
182
Managing Property Policies Querying for Property Underwriting Information
In the new record, complete the fields.
Querying for Property Underwriting Information

End users can also query for property type and dwelling underwriting information.
To query for underwriting information 1 2 3 4 5

Navigate to the Property Policies screen. In the Policies/Quotes list, drill down on a policy. Click the Property Underwriting view tab. In the Property Type list, click Query to search for property type and dwelling underwriting information. Select the query criteria and click Go.

After end users add the necessary policy information, they can order underwriting reports for a policy. Examples of underwriting reports are motor vehicle, credit bureau, or loss history reports.
To order an underwriting report 1 2 3 4

Navigate to the Property Policies screen. In the Policies/Quotes list, drill down on a policy. Click the Underwriting Reports view tab. In the Underwriting Reports list, add a record and complete the necessary fields. NOTE: You can configure your application to activate the software program your company uses to submit orders for underwriting reports.
Adding Scheduled Personal Property

End users can add scheduled personal property, such as jewelry, coins, and fine art, to a property insurance policy.
To add scheduled personal property 1 2

Navigate to the Property Policies screen. In the Policies/Quotes list, drill down on the policy.
18 3
Managing Property Policies Setting Up Payment Plans
3 4
Click the Quick Quote view tab. In the Property Types list, add a record and complete the necessary fields. NOTE: When you select a personal property value in the Type drop-down list, the Scheduled Property Rating form appears.
5 6 7 8 9
Scroll down to the Scheduled Property Rating form and complete the fields. Click the SPP Detail view tab. In the Property Type list, select a type and scroll down to the SPP Items list. In the SPP Items list, add a record and complete the necessary fields. Repeat Step 4 through Step 8 for each scheduled property item you want to add.

End users can set up payment plans, including details about payment methods, for property insurance policies.
To set up a payment plan for a property policy 1 2 3 4

Navigate to the Property Policies screen. In the Policies/Quotes list, drill down on the policy. Click the Payment Plans view tab. In the Payment Plans list, add a record and complete the necessary fields.
Additional Property Policies Views

Table 28 describes additional views that are unique to the Property Policies screen. Table 28. View Tab Coverage Underwriting Replacement Cost Additional Property Policy Screen Views Description Records additional details regarding optional property policy coverages. Replacement cost is an estimate of what it would cost to rebuild a real property structure. A replacement cost estimate is the basis of determining the amount of dwelling coverage that must be applied to a policy covering real property structures. This view captures a detailed description of property to be insured from which a replacement cost estimation can be made.
184
Managing Property Policies Additional Property Policies Views
Table 28. View Tab
Additional Property Policy Screen Views Description Displays the details of a replacement cost estimate. Replacement cost data is often obtained from an external system. For more information on integrating with external systems, see Siebel Integration Messages on page 193. Records a detailed description of watercraft and associated equipment. Records operator information for watercraft operators on a policy. Displays a summary of all scheduled personal property items. For more information, see Adding Scheduled Personal Property on page 183. Records details of accident and violation history for boat operators.
Replacement Cost Summary
Boat Detail Boat Operator All SPP Items Accident Violation
18 5
Managing Property Policies Additional Property Policies Views
186
15 Managing PUL Policies

This chapter describes managing PUL policies. Itincludes the following topics: About PUL Policies on page 187 Scenario for PUL Policies on page 187 Providing PUL Policy Quotes on page 188
About PUL Policies

PUL Policies are a specialized type of insurance policy. Rather than provide financial protection for real property, a PUL policy provides an umbrella of liability coverage that is above that provided by a policyholders other insurance policies. A PUL policy requires the collection of information about the property that is covered by the contract, plus information about the policies that provide the basic liability coverage for those pieces of property. Within a PUL policy, the policies that provide the basic liability coverage are termed underlying policies. The PUL policy provides for liability coverage that exceeds the liability coverage provided by the underlying policies. The PUL (personal umbrella liability) Policies views are used by service and licensed sales representatives to create and manage PUL insurance policies, including issuing quotes for a new policy or for a change in an existing policy. For more information on views common to all policy screens, see Common Policy Views on page 160.
Scenario for PUL Policies

This scenario features sample tasks performed by a licensed sales representative. Your company might follow a different workflow according to its business requirements. In this scenario, a licensed sales representative for a PUL insurance company is on the phone with a customer who has a homeowners policy with your company. Using the fields on the Quick Quote view as a guide, the sales representative asks the customer a series of questions in order to gather enough information to provide an initial quote. Because this is a PUL quote, he collects vehicle information, property (residence) information, watercraft information, and underlying policy information. Underlying policies are those whose liability coverage is extended by the PUL policy. After the data has been collected, he submits it to an external rating calculator to determine the premium. Then, he gives the customer a verbal quote, and the customer indicates an intention to purchase the policy. The quote now needs to be prepared for eventual contract issuance. This includes collecting detailed information about the insured vehicles, boats, or property and any underlying policies and billing and payment arrangements.
18 7
Managing PUL Policies Providing PUL Policy Quotes
Then, he follows the procedures implemented by his company to submit the policy for issuance and billing. In this scenario, end users are licensed sales representatives who service customers. They enter information to: Provide quotes Collect underwriting, rating, and underlying policy information about vehicles, properties, and watercraft
Providing PUL Policy Quotes

In Siebel Insurance, a quote is a policy that has not been issued. End users can generate a quote for a new policy or for a change to an existing policy. The Quick Quote view provides a way to gather basic policy and rating information. The information collected through the Quick Quote view represents the minimum rating information needed to create an initial premium calculation.
To generate a PUL insurance policy quote 1 2 3 4 5 6

Navigate to the PUL Policies screen. In the Policies/Quotes list, add a record and complete the necessary fields. In the Policies/Quotes list, drill down on the policy. Click the Quick Quote view tab. In the Quick Quote form, complete the necessary fields. Collect underwriting, rating, and underlying policy information about vehicles, properties, and watercraft using the following PUL Policies view tabs:

Vehicles Property Watercraft Underlying Policies
After collecting the data, you can submit it to an external rating engine to determine the premium. In the application, you can add information to help underwrite and administer the quote. You can use the Rating form to manipulate the Rating factors and further refine the quote. NOTE: You can configure your Siebel application to add a Rate button that activates the software program your company uses to rate policies.
188
16 Managing Billing Accounts

This chapter describes how to manage billing accounts. It includes the following topics: About Billing Accounts on page 189 Scenario for Billing Accounts on page 189 Process of Managing Billing Accounts on page 190 Creating Billing Account Records on page 190 Associating Billing Accounts with Other Records on page 191
About Billing Accounts

To handle the payment of policy premiums, insurance companies use something called a billing account. A billing account is a construct that is used to handle the billing and payment activities associated with one or many insurance policies. The policy premiums are billed and collected through the billing account. This allows insurance companies to give users the flexibility to pay their premiums through a single bill, even though they might have several policies. Siebel Insurance provides flexibility for companies to handle billing-oriented transactions in various ways. Although billing accounts are a popular method within the industry, many companies handle billing on a single policy basis and many use a blend of billing account and single policy billing. Using the procedures given in this chapter, end users will be able to use the Billing Accounts screen to add a billing account, associate a billing account with a policy, contact, or company, and add a service request to a billing account.
Scenario for Billing Accounts

This scenario features sample tasks performed by an insurance agent. Your company might follow a different workflow according to its business requirements. An insurance agent creates a new billing account to manage the various policies held by one of her customers. First, she associates the policies and certain contacts with the billing account. In this context, a contact can be someone who is responsible for paying the bills associated with an account or someone associated with the billing account, such as the secondary insured on a policy. Later, the insurance agent receives a call from one of her contacts. The contact has a problem with his latest bill. The insurance agent logs a service request against the customers billing account.
18 9
Managing Billing Accounts Process of Managing Billing Accounts
Process of Managing Billing Accounts

This section details sample tasks often performed by end-users when managing billing accounts. Your company might follow a different process according to its business requirements.
End-User Procedures
The following list shows tasks end users typically perform when managing billing accounts: Creating Billing Account Records on page 190 Associating Billing Accounts with Other Records on page 191
Creating Billing Account Records

End users can add a new billing account record from any Billing Accounts view, including the Contacts screen, the Companies screen, the Service Requests screen, or the Billing Accounts screen.
To add a billing account 1 2

Navigate to the Billing Accounts screen. Add a new record and complete the necessary fields. Some fields are described in the following table. Field Account # Comments Automatically generated by the application. You can configure Siebel Insurance to assign a billing account number based on your companys standards and conventions. Set to the current date. Set to New. The type of billing account. Select: Single Policy if you will associate only one policy with the billing account. Multiple Policy if you will associate more than one policy with the billing account.
Effective Date Status Type
190
Managing Billing Accounts Associating Billing Accounts with Other Records
Associating Billing Accounts with Other Records

Billing accounts can be associated with policies, contacts, companies, service requests, and households. End users can make the associations directly from the Billing Accounts screen, the Contacts Billing Accounts view, or the Companies Billing Accounts views. Billing accounts can only be associated with households through an implicit relationship with a contact. That is, a billing account must be associated with a contact who is a member of a household in order for the billing account to be associated with the household. This relationship is then visible in the Households Billing Accounts view.
To associate a billing account with a policy 1 2 3 4

Navigate to the Billing Accounts screen. In the Billing Account list, drill down on the billing account for which to associate a policy. Click the Policies view tab. In the Policies list, add a record. The Add Policy dialog box appears.
Do one of the following:

If the policy already exists, select the policy in the Add Policy dialog box. If the policy does not yet exist, click New to create a new policy.
The Add Policy dialog box closes and a record is added to the Policies list.
Complete the necessary fields. The policy is now associated with the billing account. NOTE: The billing account type determines how many policies must be associated. If the type is Single Policy, then only one policy must be associated.
Associating a Billing Account with a Contract or a Company

Use the following procedure to associate a billing account with a contract or a company.
To associate a billing account with a contact or a company 1 2 3 4

Navigate to the Billing Accounts screen. In the Billing Account list, drill down on the billing account with which to associate a contact or a company. Click the Contacts view tab. Do one of the following:
19 1
Managing Billing Accounts Associating Billing Accounts with Other Records
In the Contacts list, click New and either select or add a contact in the Add Contact dialog box. In the Organizations list, click New and either select or add a company in the Add Companies dialog box.
The selected contact or company is now associated with the billing account.
Adding a Service Request to a Billing Account

Use the following procedure to add a service request to a billing account.
To add a service request to a billing account 1 2 3 4

Navigate to the Billing Accounts screen. In the Billing Account list, drill down on the billing account to associate with a service request. Click the Service Requests view tab. In the Service Requests list, add a record and complete the necessary fields.
192
17 Siebel Integration Messages

This chapter describes Siebel integration messages. It includes the following topics: About the Siebel Financial Services Business Platform on page 193 Siebel Insurance Integration Messages on page 194
About the Siebel Financial Services Business Platform

The Siebel Financial Services Business platform combines a set of tools, technologies, and prebuilt functional integration components to facilitate application integration. This set of products is referred to as Siebel Financial Services Business Application Integration (EAI). Siebel Financial Services EAI is an EAI solution built on top of Siebel EAI offered by Oracle. Siebel Financial Services EAI provides an integration solution using industry XML standards. These standards have been adopted by the industry and extended by middleware companies such as IBM MQSFSE. Siebel Financial Services EAI is designed as a set of interfaces that interact with each other and with other components within the Siebel application. These interfaces: Allow configurable messages within Siebel Tools for exchanging information using the various industry XML standards. Expose internal Siebel Objects to external applications. Take advantage of prebuilt adapters and enterprise connectors, and are compatible with thirdparty adapters and connectors. Allow prebuilt XML connectors for Siebel applications. Allow for comprehensive data transformation. Allow extension for customized XML connectors by providing the Siebel Industry XML Connector Factory API.
For more information on Siebel EAI, see Siebel Financial Services Enterprise Application Integration Guide and Overview: Siebel Enterprise Application Integration.
19 3
Siebel Integration Messages Siebel Insurance Integration Messages
Siebel Insurance Integration Messages

Siebel Insurance includes a number of integration messages designed to support key business processes for the insurance industry. Table 29 describes these messages by defining the message type, the message purpose, the target application, and where you can find more information about it.
Table 29. Type ACORD
Siebel Insurance Integration Messages Message Dwelling Valuation Inquiry Request Target Application Replacement Cost Estimation System Description A message submitting details of a dwelling on a home policy in order to request for dwelling values. For information, see Siebel Financial Services Connector for ACORD P&C and Surety Guide.
ACORD
Dwelling Valuation Inquiry Response
Replacement Cost Estimation System
The response message to a home policy request for dwelling values. For information, see Siebel Financial Services Connector for ACORD P&C and Surety Guide.
ACORD
Home Policy Add Request
Policy Administration System
A request message to create a new home policy. For information, see Siebel Financial Services Connector for ACORD P&C and Surety Guide.
ACORD
Home Policy Add Response
The response message to a request for the creation of a new home policy. For information, see Siebel Financial Services Connector for ACORD P&C and Surety Guide.
ACORD
Home Policy Quote Inquiry Request
Rating Engine
A message submitting details of a home policy rate quote. For information, see Siebel Financial Services Connector for ACORD P&C and Surety Guide.
ACORD
Home Policy Quote Inquiry Response
Rating Engine
The response message to a request for a home policy quote. For information, see Siebel Financial Services Connector for ACORD P&C and Surety Guide.
194
Table 29. Type ACORD
Siebel Insurance Integration Messages Message Personal Auto Policy Add Request Target Application Policy Administration System Description A request message to create a new personal auto policy. For information, see Siebel Financial Services Connector for ACORD P&C and Surety Guide.
ACORD
Personal Auto Policy Add Response
The response message to a request to create a new personal auto policy. For information, see Siebel Financial Services Connector for ACORD P&C and Surety Guide.
ACORD
Personal Auto Policy Quote Inquiry Request
Rating Engine
A message submitting details of a personal auto policy request for a rate quote. For information, see Siebel Financial Services Connector for ACORD P&C and Surety Guide.
ACORD
Personal Auto Policy Quote Inquiry Response
Rating Engine
The response message to a request for a personal auto policy quote. For information, see Siebel Financial Services Connector for ACORD P&C and Surety Guide.
ASI
Create Life Policy Record
A message to create a new life insurance policy. For information, see Siebel Application Services Interface Reference.
ASI
Inquiry MIB Report
Medical Insurance Bureau
A message to request a Medical Insurance Bureau report. For information, see Siebel Application Services Interface Reference.
ASI
Notice of Loss
Claims Administration System
A message to create a claim record with initial loss information. For information, see Siebel Application Services Interface Reference.
19 5
Table 29. Type ASI
Siebel Insurance Integration Messages Message Payment Information Target Application Claims Accounting System Description A message to submit a claim payment. For information, see Siebel Application Services Interface Reference.
ASI
Request ParaMed Result
Medical Examination Service Provider
A message to request for the result of a physical examination for a life insurance applicant. For information, see Siebel Application Services Interface Reference.
IAA
Add Party Request; Add Party Response
Party Administration System
A message to add contact information. For information, see Siebel Financial Services Connector for IAA-XML Guide.
IAA
Delete Party Request; Delete Party Response
A message to delete a contact. For information, see Siebel Financial Services Connector for IAA-XML Guide. A message to query for a contact. For information, see Siebel Financial Services Connector for IAA-XML Guide. A message to update contact information. For information, see Siebel Financial Services Connector for IAA-XML Guide.
IAA
Find Party Request; Find Party Response
IAA
Modify Party Request; Modify Party Response
196
Table 29. Type IAA
Siebel Insurance Integration Messages Message Submit Application Request; Submit Application Response Target Application Policy Administration System Description A message to submit an insurance policy application. For information, see Siebel Financial Services Connector for IAA-XML Guide. Policy Administration System A message to inquire about the status of an insurance policy application. For more information, see Siebel Financial Services Connector for IAA-XML Guide.
IAA
Inquiry Financial Services Agreements Request; Inquiry Financial Services Agreements Response
19 7
198
18 Business Services for Siebel Financial Services

This chapter describes the business services for Siebel Financial Services. It includes the following topics: About Siebel Business Services on page 200 About Siebel Financial Services Business Services on page 200 Disclosure Manager on page 202 VBC Cache and Instance Manager on page 203 Free Format Converter on page 208 Data Validation Manager on page 209 Business Rule Processor on page 210 Process of Defining Business Rule Processes on page 211 Creating and Managing Business Rule Processes on page 212 Defining Properties for a Business Rule Process on page 215 Defining Procedures for a Business Rule Process on page 219 Fine-Tuning the Assignment Statement on page 227 Handling Business Rules Processor Errors on page 229 Using BRP Helper Business Services on page 231 Invoking the Business Rule Processor on page 242 Logging Business Rules Processor Debug Messages on page 244 Requirements Manager on page 244 Customer Authentication Manager on page 254 Using the Calculation Manager on page 259 Using the Customer Expectations Manager on page 265 Automating Approval Processing on page 269 Automating the Display of Disclosure Documents on page 273 SmartScript Integration with Workflow on page 276 Dynamic UI Business Service on page 279 FINS Application View Navigation on page 283
19 9
Business Services for Siebel Financial Services About Siebel Business Services
About Siebel Business Services

A business service is an object that simplifies the use of a specific set of functionality. Business services are not tied to specific objects, but rather operate or act upon objects to achieve a particular goal. You can use business services to execute predefined or custom actions in a workflow process. For more information on: Business services, see Overview: Siebel Enterprise Application Integration Workflows, see Siebel Business Process Framework: Workflow Guide
About Siebel Financial Services Business Services

Siebel Financial Services introduces a number of business services that fulfill a specific need in an end-to-end business process. The overall goal with these business services is to reduce the custom scripting that customers do during implementation. These business services benefit Siebel Financial Services customers in the following ways: Increased efficiency and consistency with automation Rapid deployment of functionalityless programming, and immediately deployable; SRF changes are not required Better performance than scripting Ease of maintenanceability for a business analyst to maintain rules
For example, the Data Validation business service allows customers to define data validation rules in an administration view that users trigger in run time. This significantly reduces the amount of custom scripting that would otherwise be required. Other business services, such as the Disclosure and Approval business services, bring similar benefits to customers' disclosure and approval business processes.
200
Business Services for Siebel Financial Services About Siebel Financial Services Business Services
Table 30 lists the business services available in Siebel Financial Services.
Table 30.
Siebel Financial Services Business Services Business Applications Regulatory compliance, sales process compliance. Policy exception approvals, underwriting. Cache data from external applications in Siebel for display. Comma-delimited and other free-format message creation. Embed Q&A style processes as part of a workflow process. Auto-creation, prefilling. Conditional logic, data integrity control. Application closings, service case resolution. Transaction level security, regulatory compliance. Lead scoring, payment calculations, prioritization. Customer services expectations, fulfillment expectations. Definition and execution of complex, frequently changing business logic. Functionality Present literature specific to products; logs presentation for compliance. Determines necessary approval sources and routes to inbox. Cache VBC data throughout user's session and use Siebel Workflow to query external data sources. EAI Business Service to convert Siebel data to nonXML formats. Launch SmartScript sessions within a workflow process. Pass information from SmartScript back into the workflow process for downstream processing. Copies data from one Siebel BO/BC/Field to another BO/BC/Field. Performs data validation across business component fields. Determines requirements and next steps for transaction completion. Situation specific customer authentication data collection and logging. Performs arithmetic functions and if/then/ else calculations in background or through UI. Calculates expected and promise dates, and sets priorities, based on item type and customer value. Higher performance and more scalable than scripting. Can change business logic without a new SRF. Flexible - supports procedure, loops, if-then-else, switch-case constructs.
Business Service Disclosure Manager
Approval Manager VBC Cache and Instance Manager Free Format Converter
Workflow - SmartScript Integration
Data Transfer Utilities (DTU) Data Validation Manager Requirements Manager Customer Authentication Manager Using the Calculation Manager Using the Customer Expectations Manager Business Rule Processor
20 1
Business Services for Siebel Financial Services Disclosure Manager
Table 30.
Siebel Financial Services Business Services Business Applications Create read-only view that can be changed without the need to recompile and redeploy a Siebel Repository File (SRF). View navigation. Functionality Create and render views containing a single read-only applet in the Siebel Financial Services application.
Business Service Dynamic UI Business Service
Guides users through a series of views based on administration data.
CAUTION: As with other specialized code, use only the specialized business services that are documented in Siebel documentation. The use of undocumented services is not supported and can lead to unwanted and unpredictable results.
Disclosure Manager
The Disclosure Manager business service is used to present literature specific to financial products, and to log the presentation of disclosure statements. Disclosure processing is implemented by invoking the FINS Disclosure workflow from Siebel Script or Siebel Workflow. Disclosure documents are associated with specific products by the administrator.
FINS Disclosure UI Service Methods

The FINS Disclosure UI Service business service provides the following two methods: SetupDisclosure. This method is used to save the current active view information for navigating back after displaying the disclosure(s). GotoView. This method is used to navigate to a view whose context was saved during the SetupDisclosure method call. This method does not take any parameters.
SetupDisclosure Input User Properties

Table 31 lists the input user properties for the SetupDisclosure method.
Table 31.
SetupDisclosure Input User Properties Description This is the Contact row ID. This is the disclosure name. Predefault Value N N
Parameter Name ContactId DisclosureName
202
Business Services for Siebel Financial Services VBC Cache and Instance Manager
Table 31.
SetupDisclosure Input User Properties Description This is the Product row ID. This is a Boolean flag. If the value is set to true then disclosures must be displayed. Predefault Value N
Parameter Name ProductId ShowAlways
SetupDisclosure Output User Properties

Table 32 lists the output user properties for the SetupDisclosure method.
Table 32.
SetupDisclosure Output User Properties Description This is the Disclosure row ID. This is a Boolean flag. If the value is set to true, then it implies that the current active version of the disclosure has not been displayed. The value will be N if ShowAlways is set in the input property set. Predefault Value N N
Parameter Name DisclosureId bDone
VBC Cache and Instance Manager

Integrating external systems with Siebel data in real time is a common business requirement. A standard approach is to use Virtual Business Components (VBC) with a substantial amount of scripting. This approach, however, often has associated performance and scalability concerns. The Caching VBC was originally developed to address integration with external billing systems, and the design requires a minimal amount of scripting. These features, however, can be extended and applied to a broad set of integration challenges beyond billing.
Caching VBC Overview

The Caching VBC enhances the existing CSSBCVRec VBC class and works in conjunction with the SIA Billing Extern Service business service. Although the name of this business service implies that it is billing specific, it is a generic service without any industry specific functionality. Features of the Caching VBC include: Caching of response data, allowing navigation between records in a parent BC without generating duplicate requests in the child VBC Ability to have a VBC be the parent of another VBC child within a single business object Forced refresh of already cached data Ability to generate integration object instances without using the EAI Siebel Adapter business service
20 3
Integration with workflow process that can take advantage of any existing integration flow that uses Application Service Interfaces (ASIs), Web Services, or connector technology
Possible limitations to consider: Read-only behavior Only available as part of the Siebel Industry Applications (SIA) product Queries are not supported. Only an active field of an active business component has its value prefilled properly by the request integration object. The business service references only the top-level from the top-level integration component when creating the request message to populate predefault fields.
Components
Figure 3 shows the components to implement the Caching VBC.
Figure 3.
Caching VBC Components
Stages of the Caching VBC Process

The caching VBC process uses the following process flow.
1 2
The Caching VBC invokes the named service when queried. User properties on the VBC identify:

Whether or not to enable caching The service name to invoke (SIA Billing Extern Service) The integration object name to be passed to the service as an input parameter The workflow process name to be passed to the service as an input parameter
3 4 5
When the VBC is executed, the VBC calls the business service and passes it the integration object name and workflow process name. The business service instantiates the named integration object and populates it with values in the currently active business object without using the EAI Siebel Adapter. The business service passes the integration object instance to the SiebelMessage workflow process property and invokes the workflow process.
204
The workflow process handles any integration tasks, including communicating with the external system. It receives data from the external system and populates a hierarchical process property that matches the field structure of the VBC.
7 8
The workflow process completes. The business service reads the hierarchical output process property from the workflow process property named VBC Output and compares it with the fields in the VBC. Where matching field names are encountered, the value in the output process property is copied to the VBC. Field names that do not match are ignored and do not generate an error.
Caching VBC Configuration

Base the VBC on the CSSFABCVRec class. Table 33 lists the user properties VBC uses for its configuration.
Table 33.
User Properties for VBC Configuration Valid Names Yes or No Description Yes enables the caching of records retrieved by the VBC. No disables caching.
User Property Name Enable Caching
Outgoing Integration Object Name ProcessName
An integration object name
Name of the integration object to be passed to the business service. Name of the workflow process to be passed to the business service. Name of the business service to be invoked when the VBC is executed.
A workflow process
Service Name
A business service
You must also configure the fields for your business component. No other scripting is necessary to invoke the service or the workflow. The VBC uses a special field called Vid. This field is an internally generated unique identifier. It is not necessary to create this field in your VBC. However, if you do create this field in your VBC, do not modify this value. Treat this field as a system field. You can create link specifications between parent business components and this VBC, and between this VBC and any child VBC. Any field can be a link specification.
20 5
Purging the VBC Cache

Purge the VBC cache by configuring a button to invoke method RefreshVBCCache. Table 34 lists the consequences if Enable Caching is set to Yes or No.
Table 34. If...
Consequences of Setting Enable Caching Then... The VBC purges cached values and forces a query of the external system. The RefreshVBCCache method has no effect.
Enable Caching is set to Y. Enable Caching is set to N.
Business Service Configuration

Base the business services specified in the Service Name parameter of the VBC on the CSSFAExternalService class, and have a method named query defined. You do not need to specify any input arguments to this method or configure any user properties. In this way, you can reuse this business service.
Integration Object Configuration

Use the integration object specified as the Outgoing Integration Object Name user property of the VBC to communicate record data between the business service and the workflow process. This integration object is non standard because it does not need to have an integration component for all the parent business components in the business object hierarchy. For example, if your business object hierarchy consists of Contact and the VBC as a child of Contact, you do not need to include a Contact integration component as the parent integration component in your integration object. The reason for this is that this integration object is never used by the EAI Siebel Adapter. Therefore, you do not need to include the complete business component hierarchy in the integration object. The integration object uses the PREDEFAULT user property (Table 35) on integration component fields to identify those fields that must be prefilled with data from the active business components:
Table 35.
PREDEFAULT User Property Valid Values [Business Component Name.Field Name] For example, [Contact.Primary Personal Postal Code] Description Identifies the source business component field that the Business Services uses to prefill the integration component field.
Integration Component Field User Property PREDEFAULT
206
After the workflow process completes, values in the integration component fields that have matching names in the VBC are copied back to the VBC. If the integration object has fields that do not match the VBC, then those fields are ignored and no error is produced.
Workflow Configuration
The workflow process specified as the ProcessName user property of the VBC is used to identify which workflow process the business service must invoke after instantiating the named integration object. Table 36 lists the two process properties that must be configured for this process to communicate with the business service.
Table 36.
Workflow Process Properties Type Integration Object Description The input of the workflow process. This is passed in by the business service. Contains the integration object instance of the integration object identified with the Outgoing Integration Object Name user property on the VBC. This integration object instance contains data for integration component fields that have the PREDEFAULT user property set as described in the Integration Object Configuration section of this document.
Process Property Name SiebelMessage
VBC Output
Hierarchy
The output from the workflow process. This is returned to the business service. Contains the integration object instance of the result of querying the external system that is to be returned to the business service for inserting into the VBC.
20 7
Business Services for Siebel Financial Services Free Format Converter
The SiebelMessage process property contains the query parameter for the external system. The workflow process transforms this data to a format understood by the external system, then uses a transport to send the request and receive the response from the business service. Finally, it must transform the response data back to a format that matches the VBC fields. This transformed response data must be stored in the VBC Output process property so that the calling business service can map it back to the VBC.
Free Format Converter

This topic describes how to leverage the FINS EAI Free Format Hier Converter business service to convert a Siebel property set into a UTF-8 based text file structure for downloading. Out of the box, the FINS EAI Free Format Hier Converter business service is used in the FINS eBanking Account Download Outbound workflow to enable the creation of flat file, tag-based data stream for download. The business service follows the same model as the EAI XML converter, but provides flexibility for manipulating the output data stream and header information. If the output format that you want is XML-based, use EAI XML Converter, XML Hierarchy Converter, or other XML related converter Business Service that Oracle provides. If the file format is not XMLbased, use FINS EAI Free Format Hier Converter.
FINS EAI Free Format Hier Converter Methods

The FINS EAI Free Format Hier Converter business service provides two methods for creating text data streams: PropSetToPlainText PropSetToRawText
The difference between these two methods is that the PropSetToRawText method has the DiffBeginEndTag, EscCharSupport, and NewLineAfterNode user properties predefaulted. And in the PropSetToPlainText method, the following parameters are preset: DiffBeginEndTag = N EscCharSupport = N NewLineAfterNode = Y
PropSetToPlainText and PropSetToRawText User Properties

Table 37 lists the user properties for the PropSetToPlainText and PropSetToRawText methods.
Table 37.
User Properties Description A text value for the left boundary of the begin tag. A text value for the right boundary of the begin tag. Predefault Value < >
Parameter Name BeginTagLeft BeginTagRight
208
Business Services for Siebel Financial Services Data Validation Manager
Table 37.
User Properties Description Y or N If there are different tags for the begin and end tag, then for XML, they are the same. Use , as the separator to set it differently. For example, if this is set to Y, and the XML tag of any component is A,B, then the begin tag is A and end tag is B. Predefault Value N
Parameter Name DiffBeginEndTag
EndTagLeft EndTagRight EscCharSupport
A text value for the left boundary of the end tag. A text value for the right boundary of the end tag. Y or N Yes supports escape characters such as \n and \r.
< > Y
NewLineAfterNode
Y or N Yes prints a new-line character after each element.
PrintAggregateEndTag
Y or N Yes prints end tag for aggregate nodes.
PrintElementEndTag
Y or N Yes prints end tag for element nodes (element that has no child).
PrintEndTagBeforeChild
Y or N Yes prints the end tag before print out the first child.
PrintTagBound
Y or N Yes prints the tag boundaries.
XMLHierarchy
The IntObj instance that is parsed into the BusSvc.
Data Validation Manager

Many companies are governed by various regulatory agencies, as well as internal processes and procedures, to verify the quality and accuracy of their transactions. Data validation can involve many types of transactions, which includes orders, applications, claims, and various other service requests. Data validation is a key component of almost every business process in Financial Services. The Data Validation Manager business service can validate business component data based on a set of rules.
20 9
Business Services for Siebel Financial Services Business Rule Processor
In the case of a rule violation, a custom error message appears or a user-defined error code is returned. The validation rules are defined using the Siebel Query Language and can be conveniently constructed using the Personalization Business Rules Designer. The business service centralizes the creation and management of data validation rules without requiring Siebel Tools configuration, and does not require the deployment of a new SRF. The Data Validation Manager business service significantly reduces the need for custom scripts, decreasing implementation costs and increasing application performance. The Data Validation Manager features include: Search automatically for the proper rule set to execute based on active business objects and views. Write validation rules based on fields from multiple business components. Apply a validation rule to a set of child business component records to see if a violation occurs from one or more records. Invoke specific actions to be performed as a result of a validation. Write validation rules that operate on dynamic data supplied at run time without that data being from the business component field. Automatic logging of data validation events.
Some example business rules that can be enforced by the Data Validation Manager business service are: In an insurance company, claim adjusters are required to enter a closed date whenever they close a claim. If the adjuster tries to close a claim without a closed date, he is prompted with an appropriate error message and the claim record is not committed to the database. In a retail bank, different data validation rules are required for each of dozens of different service request types. When a customer service representative creates a new service request, the Data Validation manager identifies the appropriate validation rule set for the specific type of service request and executes the data validation rules of that rule set. At a health insurance company, customer service representatives use activity plans and activities to track service requests. All activities must be closed before the service request can be closed. When the CSR closes the SR, the DVM loops through all associated activities making sure the status of each activity is closed. If any are still open, the SR cannot be closed.
For more information about Data Validation Manager, see Siebel Order Management Infrastructure Guide.
Business Rule Processor

The Business Rule Processor (BRP) business service is a general-purpose, highly-scalable business logic execution engine. The business logic is defined from within the Siebel client administration user interface, reducing the need to hard-code the logic into the Siebel Repository file. This supports scenarios in which there are constant changes to the business rules. The BRP can define and execute highly complex business logic.
210
Business Services for Siebel Financial Services Process of Defining Business Rule Processes
You can invoke the BRP by a run-time event, workflow, or Siebel script. This is described in Invoking the Business Rule Processor on page 242. The Business Rule Processor features include: Business logic administration through the application user interface. Appropriate for complex business logic; supports procedure, loops, if-then-else and switch-case constructs. Appropriate for business logic that changes frequently. You can modify business logic without deploying a new SRF. Query, read, and write access to business components. Error handling. Support logging at multiple levels for easy testing and debugging. Can potentially replace large amounts of custom scripts.
The BRP executes business rule processes. A business rule process is constructed much like a computer program or a Siebel workflow. A process consists of procedures. Procedures are made of steps. Steps, in turn, contain statements. A statement is a conceptual line of code. BRP configuration and administration must only be done by expert users accustomed to working with business services. TIP: Before you begin to create a business rule process, carefully consider and plan the required steps for it.
Process of Defining Business Rule Processes

Defining business rules processes involves the following procedures:
1 2 3
About Business Rule Process Property Types on page 215 Defining Procedures for a Business Rule Process on page 219 Using BRP Helper Business Services on page 231
21 1
Business Services for Siebel Financial Services Creating and Managing Business Rule Processes
Figure 4 presents an overview of defining business rule processes.
Figure 4.
Business Rule Processor Design Diagram
Creating and Managing Business Rule Processes

This topic describes how to create and manage business rule processes.
212
About Business Rule Processes

A BRP process is uniquely identified by its name. A process name must begin with a letter. It can contain alphanumeric, space, underscore, and hyphen. The name cannot contain other special characters like @ or !. NOTE: BRP names are case sensitive and limited to 75 characters. TIP: It is important to establish a naming convention before you engage in the development of BRP processes.
About Defining Business Rule Processes

You define business rule processes from the Business Rule Processor screen. You can either revise an existing process or create a new one. A business rule process is made up of procedures and properties. A BRP process can have one of three statuses: In progress. You can modify only a process in the In-progress status Active. An Active status indicates that the process definition is released for execution Inactive. An Inactive process indicates that the process is in no longer in use and has been retired
NOTE: The process status indicates its edit disposition rather than its current run-time execution status. Additionally, all BRP process definitions are cached in the object manager across all login sessions to improve scalability. Hence, if any modifications are made to the process definitions, then they are not available to the run-time sessions until the cache is refreshed. It is recommended that you put in place procedures to promote BRP processes from development to production, and establish controls on how to refresh the cache. You can import and export business rule processes. This makes migrating process definitions across development and production environments easier. The process is saved as an XML file for importing and exporting purposes. This step is part of Process of Defining Business Rule Processes on page 211.
To create a business rule process 1 2

Navigate to the Business Rule Processor screen. Create a new record.
Revising an Existing Business Rule Process

You can also revise an existing business rule process.
To revise an existing business rule process 1

Navigate to the Business Rule Processor screen.
21 3
In the Processes list, select a business rule process of status Active or Inactive and click Revise. Clicking Revise changes the status of the process to In Progress.
Make the appropriate changes to the process.
Activating a Business Rule Process

You can also activate a business rule process.
To activate a business rule process 1 2 3

Navigate to the Business Rule Processor screen. In the Processes list, select the business rule process you wish to activate. Click the Activate button. Clicking Activate changes the Status from In Progress to Active and makes the record read-only.
Click the Refresh Cache button. This clears the OM cache and creates a new copy of the process definitions. Any process that is executing when the cache is cleared is allowed to complete. However, the new process definition is available to all processes that start right after the button is clicked. NOTE: Take care while using this feature. Refresh Cache clears the cache for all BRP process definitions. Hence, any processes that are In-progress or Inactive are lost from the cache.
Exporting a Business Rule Process

You can export an existing business rule process.
To export a business rule process 1 2 3 4

Navigate to the Business Rule Processor screen. In the Processes list, select the process you wish to export and click the More Info view tab. In the Processes form, click the Export Process button. Follow the on-screen prompts to save the rule set as an XML file.
Importing a Business Rule Process

Once you follow the procedure to export a business rule process, follow this procedure to import the business rule process.
To import a business rule process 1 2

Navigate to the Business Rule Processor screen. Click the More Info view tab.
214
Business Services for Siebel Financial Services Defining Properties for a Business Rule Process
3 4
In the Processes form, click the Import Process button. In the Workflow Process Import dialog box, locate the file you wish to import and click Import. The imported process appears with a status of In Progress.
To activate the imported process, select it in the Processes list and click Activate. Clicking Activate changes the rule set Status to Active and makes the record read-only. NOTE: If the process already exists, the process status must be In progress to allow the import. View imported processes by performing a query/go operation to refresh the Processes list.
Defining Properties for a Business Rule Process

Properties are: Variables that are used either to facilitate flow of data in and out of a process or to store information temporarily for the life of the process. Either global process properties or local procedure properties. Global properties are available for all procedures that are associated with the business rule process.
The property name: Must begin with a letter. Can contain alphanumeric, spaces, underscore, and hyphen. Cannot contain other special characters such as an ampersand (@) or exclamation mark (!). Are case sensitive and limited to 75 characters.
NOTE: If a procedure defines a local property with the same name as a global property, the local property takes precedence over the global property within the scope of that procedure. This step is part of Process of Defining Business Rule Processes on page 211.
About Business Rule Process Property Types

You can categorize properties into two classes: Simple property types. Scalar properties such as an integer, string, or date. Complex property types. Nonscalar properties such as property sets, vectors, and Siebel Business Component references.
At run time, you can pass values for global properties to the BRP business service as an input argument. This run-time value overwrites the initial value definition, if any, on the property. TIP: Use an appropriate prefix, such as global_, local_, or l_ to designate local and global properties.
21 5
Complex properties except ProperySet and Vector cannot be passed as inputs to a BRP process. Table 38 describes the complex types in further detail.
Table 38. Type BusComp
Complex Property Types Description This data type stores a reference to a Siebel Business Component (BC) and is used in conjunction with the FINS CAP Buscomp Handler business service. See Using BRP Helper Business Services on page 231. BusComp is used within BRP process as a stand-alone BC, without the context of Business Object (BO). Hence, you have to explicitly query the BusComp with the correct key values to establish a context.
Property Set
Property sets are collections of properties used for storing data. They might have child property sets assigned to them to form a hierarchical data structure. See Siebel Object Interfaces Reference. The Property Set itself can contain child property sets. This is particularly convenient to store array-like data. For example, to store multiple contacts and their properties such as Name, Phone Number, and Date of Birth. Each contact is stored as a child property set of Contacts. At the leaf, the property map stores data as a name-value pair. A property set cannot be instantiated with an assignment. Property sets are always instantiated using a business service, such as FINS CAP Buscomp Data Loader Service. See Using BRP Helper Business Services on page 231.
216
Table 38. Type Vector
Complex Property Types Description Vectors are special-formatted Property Sets, where each nonleaf node stores a unique key as its value. NOTE: The vector root node type for a BRP process is always SEBLFACapVector. A vector cannot be instantiated with an assignment. Vectors are always instantiated using an business service, such as FINS CAP Buscomp Data Loader Service. See Using BRP Helper Business Services on page 231. The following diagram shows a ProductRate vector that has 2 levels - Region & Product name. At the leaf level the vector stores the rate and the balance as key value pairs.
21 7
Table 38. Type
Complex Property Types Description Vector Reference is a reference to a property set, vector or a child property set. Once defined, you can use Vector Reference as a vector or propertyset. When the referenced object is reset, the dependent reference is automatically set to NULL. This property set is particularly useful when accessing data on the child property sets. There are two ways to make a child Property Set reference: childPropertySetRef = parentPropertySet[strkeyValue] childPropertySetRef = parentPropertySet(nIndex)
Vector Reference
About Using Parentheses Round parentheses ( ) are used to retrieve a child Property Set by index. NOTE: The index starts at 0. Square parentheses [ ] are used to get a child Property Set by value. NOTE: Accessing by value is only valid for Vectors. Only literals or property names can be used within [ ] or ( ). Expressions cannot be used within. TIP: To use expressions within [ ] or ( ), assign these to a simple property type and use the simple property within [ ] or ( ). You can use square and round parentheses in combination. Example: grandchildPropertySetRef = parentPropertySet(2)["California"] In the preceding notion, parentPropertySet itself can be a reference. In other words, a reference and a property set are used interchangeably for data access. Retrieve leaf properties by using square parentheses [ ]. Example: ProductRate = productRate[productId][domain]["Annual Fee"] The following procedure describes how to define a property for use in a business rule process.
To define a property for a business rule process 1

Navigate to the Business Rule Processor screen and select a process for which you want to create global variables.
218
Business Services for Siebel Financial Services Defining Procedures for a Business Rule Process
Click the Properties view tab and create a new property completing the fields as necessary. Some fields are described in the following table. Field Sequence Data Type Comments Identifies the numeric sequence of this property. The application initializes properties in numerical order based on this number. The data type for the property. The value can be one of the following. Simple types: String Integer Number Date Boolean
Complex types: Value Property Set Vector Vector Reference BusComp
Initial value of the property. Initial values can be set only for Simple property types.
Output
Select this check box to make property an output argument and is used to pass information out of the business service. which has no output arguments of its own. This flag does not apply to Complex property types except ProperySet and Vector.
Defining Procedures for a Business Rule Process

Procedures are collections of steps. When a procedure is executed, each step in the procedure is executed in sequence. One of the procedures is designated at the process level as the entry procedure. This procedure is executed when the process is executed. Within the entry procedure, other procedures are invoked by additional procedure statements.
21 9
Each procedure is uniquely identified by its name. The name must begin with a letter. It can contain alphanumeric, spaces, underscores, and hyphens. It cannot contain other special characters such as an ampersand (@), exclamation mark (!), or percent sign (%). Procedure names are case sensitive. A procedure can have its own local properties. These properties can only be accessed within the procedure where they are defined. If a local property has the same name as a global property, the local property takes precedence over the global property. NOTE: Business rule processes are not permitted to use recursion. If you define a recursion, then you will receive an error message that recursion is not allowed. This step is part of Process of Defining Business Rule Processes on page 211.
To define a procedure for a business rule process procedure 1 2 3

Navigate to the Business Rule Processor screen and select a process. Click the Procedures view tab, and create a new procedure. In the Properties list, create new records to define local variables for the procedure. The fields for a local variable are equivalent to those of a global variable. The fields are described in The following procedure describes how to define a property for use in a business rule process. on page 218. NOTE: Properties defined for a procedure are local variables accessible only to the parent procedure. You can define global variables in the Business Rule Processor Properties view. See Using BRP Helper Business Services on page 231.
Defining a Step for a Business Rule Process Procedure

You must define the steps that make up a business rule process procedure.
To define a step for a business rule process procedure 1

Navigate to the Business Rule Processor screen, select a process and a procedure.
220
Navigate to the Steps list and create a new record to define each step for the procedure. Some of the fields are described in the following table. Field Sequence Step Type Comments The numerical order in which the steps are executed. There are three types of steps: Statement Step. Contains one or more child statements that are executed if and when the statement step is executed. Business Service Step. Invokes a Siebel business service. Business Service Step provides a way to extend the capabilities of BRP beyond its out-of-box features. For instance, you could code custom functionality in an eScript and then wrapped as a Siebel Business Service. You could invoke this Business Service within the Business Service step and exchange arguments between the script and the BRP process. Switch Step. Contains switch criterion and a switch block for each criteria. The switch block is like a statement step and contains one or more child statements. TIP: Use the switch step if a variable is a bounded variable. From a performance and maintenance standpoint, a switch step is better than multiple conditional statement steps. Inactive Comment A check box to activate or inactivate a given step. A free text field used to document the step. TIP: Make sure that each step has appropriate comments for ongoing maintenance of BRP process definitions.
Drill down on the Step Type and proceed to one of the following steps, depending on the step type.

Statement Step on page 221 Business Service Step on page 226 Switch Step on page 227
Statement Step For a statement step:
22 1
Complete the fields in the Statement Steps form, some of which are described in the following table. Field Condition Comments A Siebel Query Language expression evaluated to be TRUE or FALSE. If the expression is evaluated to be TRUE, then the statement step is executed. If the field is not specified, then the statement step executes every time it is encountered. Example: [SomeIntegerVariable] < 0 Loop If checked, the statement step iterates over and over as long as the Condition is evaluated to TRUE. If neither Condition nor Loop is asserted, then the statement step is executed one time, unconditionally. The looping is counted and compared with the maximum allowed Loop Count in order to avoid infinite looping. By default, this number is set to 1000, however, you can overwrite this value by defining the system preference FINS CAP Max Iteration. If the iteration number exceeds the maximum, an error is thrown. Refer to Handling Business Rules Processor Errors on page 229 for more information on handling errors. TIP: Construct a Fornext loop, by defining a local variable and then either incrementing or decrementing that variable in a statement. On the condition, check if the local variable has reached its limit.
Add one or more records to the Statements list, defining the statements of the statement step. Some of the field are described in the following table. Statement Type Assignment. Evaluates the expression and assigns the resulting value to the property listed in the Value field. Procedure. Invokes another procedure defined inside the BRP process. Value Name of a local, global, and system properties previously defined for the business rule process. Name of a defined procedure which is part of the business rule process. Expression A Siebel Query Language expression. Example
Null and readonly.
222
Statement Type PropertySet Value. Retrieves a property value from a property set or child property set, as defined by Expression. This property value is placed into the variable defined by Value.
Value Name of a local, global, and system properties previously defined for the business rule process.
Expression A property set value retrieve expression. The expression must begin with a variable of type property set, vector set reference, or vector. Each index can be either a variable of type integer or number, or numeric literal. No Siebel calculation expressions can be involved. EX: PropSet[AnIntege r][SomeName] PropSet(2)[Som eName] No Siebel calculation expressions can be involved.
Example Consider a Property Set called productRate that contains banking product information organized by Region and Product Name. Retrieve the Annual Fee property from the Property Set and assign this to a local property named l_Rate, by setting: Value = l_Rate Expression = productRate["West"] ["Checking"]["Annual Fee"]
PropertySet Set Value. Assigns a value to a property set property value.
A property set value retrieve expression. If the stated property name value does not exist, a new name/ value pair is created.
Name of a local or global property. If the property is not a string, it is internally converted to a string first by BRP.
Set the Annual Fee property on the Property Set productRate, by setting: Value = productRate["West"] ["Checking"]["Annual Fee"] Expression = l_Rate
22 3
Statement Type PropertySet Reference. Creates a reference to a vector or property set. If the referenced object is a vector, the reference acts as a vector. Otherwise, the reference acts as a property set. Creates an alias to a subset of a property set.
Value A local or global property of type Vector Reference.
Expression The expression must begin with a variable of type property set, vector set reference, or vector. Each index can be either a scalar property or a string or numeric literal. No Siebel calculation expressions can be involved.
Example Create a new Property Set Reference to all the products in the "East" region from the productRate Property Set, and assign this to a local variable l_east_prod, by setting: Value = l_east_prod Expression = productRate["East"]
PropertySet Sum. Retrieves an aggregation value from a vector or property set.
A local, global property. The property must be of data type number or integer.
A property set value retrieve expression. This expression differs from other property set retrieval expressions in that one of the indexes must be a wild card, indicating summing of all indices of that node. This is done by using an empty set of parenthesis. If the child property set, or the property does not exist, the return value is set to null.
Calculate the sum of balances under the Savings product across all regions from the productRate Property Set, and assign this to a local variable l_savings_bal, by setting: Value = l_savings_bal Expression = producetrate[] ["Savings"]["Balance"]
224
Statement Type PropertySet Childcount. Retrieves the number of child property sets.
Value A local, global property. Property must be of data type integer or number.
Expression A property set reference retrieve expression. If the property set does not have a child property set, the return value is 0. If the property set does not exist, the return value is -1. The latter is a useful approach to determine if a property set, or a reference is null. The expression follows property set retrieval syntax, but in the following specialized format: PropertySet [Upper Bound Field Name] [Lower Bound Field Name][Return Value Field Name] [InputProperty] The Upper Bound Field Name, Lower Bound Field Name, and Return Value Field Name must be a string literal or a BRP string property. The InputPropety must be the name of a BRP numeric property used to do the lookup.
Example Calculate the number of products available in the west region from the productRate Property Set, and assign this to a local variable l_west_count, by setting: Value = l_west_count Expression = producetRate["West"]
Table Lookup. Look-up a value based on ranges. The look up table is stored as a specialized property set. The property set consists of child property sets, and the child property sets contain three properties corresponding to Lower Bound, Upper Bound, and Value. At run time, for any input value, BRP looks up the child property set and locates the leaf whose lower Bound is smaller than the input value, but whose Upper Bound is bigger than the input value, and returns the Value property.
A local, global scalar property.
Consider a TaxRateTable vector, where High, Low, and Rate fields define the Upper Bound, Lower Bound, and Return Value. Lookup the effective tax rate for a person given the Total Income and assign this to a local variable l_tax_rate, by setting: Value: l_tax_rate Expression: TaxRateTable["High"] ["Low"]["Rate"] [dMyTotalIncome]
22 5
Business Service Step For a business service step:
In the Business Service Step form, complete the fields as described in the following table. Field Business Service Comments The name of the business service to invoke. In particular for BRP, there are two helper business services that you are likely to use for data access: FINS CAP Buscomp Data Loader Service and FINS CAP Buscomp Handler. For more information on these two business services, see Using BRP Helper Business Services on page 231. Method BusComp The business service method to use. A reference to a Buscomp Property Type. This field is used only in conjunction with the two BRP helper business services, FINS CAP Buscomp Data Loader and FINS CAP Buscomp Handler. See Using BRP Helper Business Services on page 231.
In the Arguments list, define required input and output arguments for the business service invoked. Some of the fields required are described in the following table. Field Direction Name Comments Type of argument: Input, Output, or Input/Output. The argument name. Use the pick list to select the name for registered business services. Picking the argument name automatically sets the direction. Type The mechanics of passing values to the Business Service. Select from one of three values: Literal. For Input and Input/Output arguments, the literal string in the value field is passed as an input to the Business Service method. For output arguments, this selection is invalid. Property. For Input and Input/Output arguments, the value of the local or global property is passed as an input to the Business Service method. For output arguments, the return value is populated into the local or global property. Expression. For Input and Input/Output arguments, the expression in the Value field is evaluated and is passed as an input to the Business Service method. For output arguments, this selection is invalid.
226
Business Services for Siebel Financial Services Fine-Tuning the Assignment Statement
Field Value
Comments Contains different values depending on the argument type: Literal. Contains the string value. Expression. Contains the Siebel query expression. Property. Disabled.
Property
Local or global property. This field is disabled for Literal or Expression type arguments.
Switch Step For a switch step:
a b
In the Switch Steps form, enter the switch criteria, a Siebel Query Language Expression that evaluates to be a string. In the Switch Blocks list, create records and complete the fields as described in the following table. Field Value Comments A string value used to compare with the switch step criterion value. If they are the same, the switch block is executed, which, in turn, executes the child statements belonging to the switch block. Default If checked, the switch block acts as the default switch block. It is executed if no match is found for the switch step criteria. At any point, you can disengage only one Switch Block as the default block.
In the Statements list, enter one or more statements. See Statement Step on page 221 for details on creating statements.
Fine-Tuning the Assignment Statement

You can use two fields available at the statement level to fine-tune the performance of Assignment Statements: Cache Flag Light Parser Flag
For most cases, it is recommended to leave these fields at their default values. It is only necessary to consider changing these values if performance is deemed poor.
22 7
Business Services for Siebel Financial Services Fine-Tuning the Assignment Statement
About the Light Parser Flag

Within your Siebel application, calculation expressions are evaluated using Siebel Query Language Parser. This parser could be performance and resource intensive if the expressions are simple numeric. However, to improve performance, BRP includes a high-performance light parser, which is used solely to evaluate numeric expressions. In most cases, the light parser works many times faster than the Siebel Query Language for simple numeric. The following examples are numeric expressions that can be handled by the light parser: 12 + 8 + [A]* [B] 5 + (12 + [A]* ([B] + [C]))
The following examples are considered complex and cannot be handled by the light parser: IIf ([A] > [B], 0, 1) [A] IS NULL LN (10)
When the Light Parser flag is checked, BRP attempts to use the light parser to parse and evaluate the expression. If this fails, BRP resorts to Siebel Query Language engine to parse the expression. By default, Light Parser Flag is checked. TIP: If the Light Parser flag is checked, but the expression is not a simple expression, the BRP logs an entry in the log file at run time if the Siebel log level is informational or higher. Use these log entries to help you fine-tune assignment statements. See Logging Business Rules Processor Debug Messages on page 244 for more information.
228
Business Services for Siebel Financial Services Handling Business Rules Processor Errors
About the Cache Flag

Table 39 shows the options if the Cache flag is checked or unchecked. It is recommended that you leave this flag at its default value, that is, checked. NOTE: The Cache flag is only meaningful when the expression is not handled by a light parser.
Table 39. If...
Cache Flag Options Then... Only one single parse tree is established for the expression within the object manager, irrespective of the number of open sessions. Therefore, when all sessions share the same parse tree, the memory footprint is reduced, however an overhead for context switch is assumed.
The Cache flag is checked.
The flag is not checked.
Each session has its own parse tree for the expression. There will be no context switch, but the memory footprint is increased.
Handling Business Rules Processor Errors

BRP offers a mechanism to handle errors that includes two key features: Throwing Errors Within a Business Rules Process on page 230 Recovering from Errors Within a Business Rules Process on page 230
22 9
Business Services for Siebel Financial Services Handling Business Rules Processor Errors
Throwing Errors Within a Business Rules Process

The BRP process definition includes three global system properties to throw errors and provide some meaningful information when a run-time error occurs. These properties are presented in Table 40.
Table 40.
Global System Properties for Errors Type String Description Alphanumeric error code. This property contains an empty string when there is no error.
Property Name System_ErrorCode
System_ErrorMessage System_ErrorSource
String String
Descriptive error message. Current context of the error.
After each statement, step, or procedure is executed, the BRP processor checks if System_ErrorCode is an empty string. There are two ways to set System_ErrorCode: Manually (Expected Error Conditions). An explicit assignment statement sets a nonempty string to System_ErrorCode. Automatically (Unexpected System Error Conditions). The BRP Processor detects a system error such as failure to invoke a business service, or failure to evaluate a Siebel query language expression, and sets System_ErrorCode to a Siebel error code.
When System_ErrorCode is non empty, an error occurs and the BRP processor uses the following syntax to automatically set the error source to the full context of the current execution unit: Statement Seq (Block Seq) Step Seq Procedure Name where, Seq represents the sequence number of the Statement, Block, or Step. NOTE: Block is optional and occurs only inside a switch step. The three output global properties System_ErrorCode, System_ErrorMessage, and System_ErrorSource are returned back to the calling process.
Recovering from Errors Within a Business Rules Process

For every BRP process, a procedure can be nominated as the error procedure at the process level. If defined, when an error condition occurs, this procedure is automatically invoked to handle the error. On completion of the error procedure, System_ErrorCode property is rechecked. If it is empty, the execution continues from the point where the error was originally thrown. If the error code is still populated, the process does not necessarily end, but rather follows an error bubbling process.
230
Business Services for Siebel Financial Services Using BRP Helper Business Services
For example, if an error encounters in Statement 10 Step 5 Procedure Main, the error procedure is first executed with System_ErrorSource to be 'Statement 10 Step 5 Procedure Main'. If the error is not handled, the error bubbles one level higher, to Step 5 Procedure Main. The error procedure is then re-executed with System_ErrorSouce to be 'Step 5 Procedure Main'. If error is handled there, the next step following Step 5 is executed. Otherwise, the error bubbles to Procedure Main. The whole bubbling process continues until it reaches the process level, with System_ErrorSource to be Process myProcessName. If the error is not handled at the process level, the process ends with an error. It is important that the error procedure be thoroughly tested. If an execution error occurs within the error procedure, the error procedure will not be recursively invoked; the error procedure will end with an error. TIP: Use a Switch block within the error procedure to check for known error codes.
Using BRP Helper Business Services

In Siebel Financial Services, there are two helper business services that are used as business service steps within the BRP. They are both used to facilitate data access with a business rule process. The two business services are: FINS CAP Buscomp Data Loader Business Service. The FINS Buscomp Data Loader is used to load data for prop sets. FINS CAP Buscomp Handler Business Service. This business service takes the results of calculations done within the BRP and then either creates new business component records, updates existing business component records, or queries on calculation results.
FINS CAP Buscomp Data Loader Business Service

Use this business service to load data from a Siebel business component into a Siebel property set. Additionally, once this data is loaded into a property set, it can be cached and shared across all login sessions. This business service exposes three methods: LoadData ClearCache NewVector
23 1
About LoadData Method

Use the LoadData method to load business component data into a property set. The property set follows the vector format. Table 41 describes the input and output parameters for this method. NOTE: Default the Search Spec, Sort Spec, Hierarchical Key, Key Field, Value Field, and Aggregate field arguments by defining these as user properties on the source business component. Pre-fix the BC user property with FINS Data Loader to identify these fields. For example, define the default search spec as the Buscomp user property: FINS Data Loader Search Spec.
Table 41.
LoadData Method Parameters Direction Input Input Description The name of a Siebel BC. If true, the resulting vector is cached within the OM. Further requests to load data from the same business component are handled through the cache. Cached data is retrieved based on the business component name. If a second retrieval request uses different search spec, fields, format, and so on, release the original cached data first.
Parameter Name BusComp IsCachedData
Search Spec
Input
The search spec applied to the business component when loading data. Since the FINS CAP Data Loader Service works outside the context of a business object, the search spec must include the appropriate user key fields.
Hierarchical Key [n]
Input
Hierarchical keys define the hierarchy within the vector. These keys identify the unique key at each level. Specify multiple hierarchical keys by defining [n] = 1, 2, 3 n Refer to the ProductRate vector illustrated under Defining Properties for a Business Rule Process on page 215. In the ProductRate vector, Region and Product fields represent the hierarchical keys.
232
Table 41.
LoadData Method Parameters Direction Input Description The sort specification applied to the business component when loading data. It is important to match the Sort Spec and the hierarchical keys when creating the vector. When a business component is accessed through the FINS CAP Buscomp Data Loader Service, sorting controls the shape of the parent/child tree structure. Records are processed sequentially and are aware of only the last parent node key. When children nodes are added to a parent node, they continue to be added until a new value is retrieved for the hierarchical key. When a new key value is discovered, a new parent node is immediate created, and children are assembled under that parent. This process continues until all records are collected. If a key equal to a previously processed node is retrieved after a different node key has been processed, a new node is produced rather than adding to the original.
Parameter Name Sort Spec
Field [n]
Input
The name of Buscomp fields whose values are retrieved as the leaf propertyset properties. The property name is the field name, and the property value is the field value. [n]=1,2, This represents one approach to how Buscomp fields can be retrieved. See Example of LoadData Method Using Field [n] on page 234.
Key Field & Value Field
Input
Used to retrieve data as Key/value pair and store as a property in the leaf propertyset. The field value of the Key Field is the name of the property and the value of Value Field is stored as the value of the property. This is an alternative approach to Field [n] to retrieve data. See Example of LoadData Method Using Key Field and Value Field on page 235. Duplicate Key/Value pairs are not allowed. If duplicates are found when the vector is created, the new entry replaces the old entry.
23 3
Table 41.
LoadData Method Parameters Direction Input Description Fields that are aggregated if duplicates occur. Multiple aggregate fields can be specified by defining [n] = 1, 2, 3 n This parameter is useful with the Key Field/Value Field data retrieval approach. For example, a contact can have multiple income records with different types. If the Aggregate Field is defined, the data loader service automatically sums the income and stores this as a single income key/value pair.
Parameter Name Aggregate Field[n]
Vector
Output
The resultant vector output.
Example of LoadData Method Using Field [n]

Golden Gate Bank defines its product rates in the Buscomp Financial Product. Table 42 shows fields in the Buscomp and some sample data.
Table 42. Region West West West East
Example of LoadData Method Using Field [n] Product Checking Saving N Market Checking Balance 10000 29000 87560 40000 Rate 0.2 2.1 2.5 0.24
Table 43 shows the arguments used to retrieve the data and store it in a format as defined by the ProductRate Vector sample diagram shown in Vector type.
Table 43.
ProductRate Vector Sample Value Financial Product Y Region Product Region, Product
Input Argument Name Buscomp IsCachedData Hierarchial 1 Hierarchial 2 Sort Spec
234
Table 43.
ProductRate Vector Sample Value Balance Rate
Input Argument Name Field 1 Field 2
The data is stored into a vector named productRateVector. Then, the rate of the Checking product in the East region can be retrieved as: productRateVector["East"]["Checking"]["Rate"] using a PropertySet Value statement.
Example of LoadData Method Using Key Field and Value Field

Golden Gate Bank decides to implement its product rates using a different schema. Instead of one record for one product as shown in Example of LoadData Method Using Field [n] on page 234, they would like to store the data using name-value pairs for each product. The advantage of this approach is that they can add new attributes without schema changes. Table 44 shows the data that is stored in the Financial Product Attribute business component.
Table 44. Region West West West East
Financial Product Attribute business component data Product Checking Checking Savings Savings Attribute Name Balance Rate Balance Rate Attribute Value 10000 0.2 29000 2.1
Table 45 shows the arguments used to retrieve the data and store it in a format as defined by the ProductRate Vector sample diagram shown in Vector type.
Table 45.
ProductRate Vector sample Value Financial Product Attribute Y Region Product Region, Product
Input Argument Name Buscomp IsCachedData Hierarchical Key 1 Hierarchical Key 2 Sort Spec
23 5
Table 45.
ProductRate Vector sample Value Attribute Name Attribute Value
Input Argument Name Key Field Value Field
About ClearCache Method

Use this method to create an empty Vector or PropertySet. There is one output argument, Vector. In BRP, PropertySets and Vectors are uninitialized before they are populated by a business service method, for example, the data loader LoadData method. You can use the NewVector method to generate an empty PropertySet/Vector.
FINS CAP Buscomp Handler Business Service

FINS CAP Buscomp Handler Business Service provides the ability perform data operations such as query, update, and insert within the context of a business rules process. NOTE: The business component is established without the context of the business object. Pay special care to identify the user keys for each record when inserting and setting values. Additionally, the normal Siebel error handling resulting from the business object context is not enforced. FINS CAP Buscomp Handler Business Service provides the following five methods: Query NextRecord GetFieldValue SetFieldValue InsertRecord
All of these methods need a BusComp variable to be defined under the business service step definition. See Business Service Step on page 226 for details on defining a business service step.
236
About Query Method

Use this method to retrieve data from a Siebel business component into a BRP BusComp property. The query uses ForwardBackward cursor mode. For more information on cursor mode, see Siebel Object Interfaces Reference. Table 46 describes the input and output parameters for this method.
Table 46.
Query Method Parameters Direction Input Description The name of the fields that must be included in the query. List each field individually in a sequence. Any field that you must use with the GetFieldValue and SetFieldValue methods, must be activated prior to using these. There are no limits to the number of fields that can be activated, however, care must be taken since this affects performance of the query.
Parameter Name ActivateFieldName(1,2,3n)
BusCompName SearchSpec
Input Input
The Name of the business component from which the data is to be retrieved. The search specification applied to the business component when retrieving data. This is a regular Siebel Query Language expression. Since the business service operates without a context of business object, the search spec must include the appropriate user keys when the query is used for an update.
SearchSpecFieldName(1,2,3 n)
Input
Search Spec Field Name/Value pair is an alternative way to set search spec on a field. For example, SearchSpecFieldName1=Application Flag, SearchSpecFieldValue1=Y, then this is the equivalent of setting SearchSpec to be: [Application Flag] = Y
SearchSpecFieldValue(1,2,3 n)
Input
23 7
Table 46.
Query Method Parameters Direction Input Output Description The sort specification applied to the business component when querying data. The status of the query operation. Status can have one of two values: Succeeded. Indicates that the query returned atleast one business component record. Failed. Indicates that either the query returned no business component records or the query failed due to a system error.
Parameter Name SortSpec Status
Following any data operation, use the Status field to check for error conditions and take appropriate actions. See Handling Business Rules Processor Errors on page 229 for information on error handling. Figure 5 shows the use of Query method to retrieve data from the FINS Health Provider business component.
Figure 5.
Using Query Method to Retrieve Data
238
About GetFieldValue Method

Use this method to get a value of a Business Component field into a local or global property. Table 47 describes the input and output parameters for this method.
Table 47.
GetFieldValue Method Parameters Direction Input Input Description The Name of the business component from which the data is to be retrieved. Name of the fields to be retrieved. This field must be activated prior to retrieval. See Table 46 on page 237.
Parameter Name BusCompName FieldName(1,2,3n)
FieldValue(1,2,3n)
Output
The output property into which the field values are written. This is always of type property. FieldName and FieldValue must be defined in pairs. That is, for each FieldName defined, define a FieldValue as well.
Status
Output
The status of the GetFieldValue operation. The status can have one of two values: Succeeded. Indicates that the query returned atleast one business component record. Failed. Indicates that either the query returned no business component records or the query failed due to a system error.
Following any data operation, use the Status field to check for error conditions and take appropriate actions. See Handling Business Rules Processor Errors on page 229 for information on error handling.
23 9
About SetFieldValue Method

Use this method to set a value of a business component field. Table 48 describes the input and output parameters for this method.
Table 48.
SetFieldValue Method Parameters Direction Input Input Description The name of a business component where the field to be updated is located. The name of the fields to be updated. This field must be activated prior to fetching. See About Query Method on page 237.
FieldValue(1,2,3n)
Input
The new value for the field. FieldName and FieldValue must be defined in pairs. That is, for each FieldName defined, a FieldValue must be defined as well.
Status
Output
The status of the SetFieldValue operation. Status can have one of 2 values: Succeeded. Indicates that the operation succeeded. Failed. Indicates that the operation failed.
Use the status field to check for error conditions and throw appropriate errors. See Handling Business Rules Processor Errors on page 229 for information on error handling.
About InsertRecord Method

Use this method to insert a record into a Business Component. Table 49 describes the input and output parameters for this method.
Table 49.
InsertRecord Method Parameters Direction Input Input Description The name of a business component to which a record is to be inserted. The name of the fields to be included in the insert.
240
Table 49.
InsertRecord Method Parameters Direction Input Description The value for the field. FieldName and FieldValue must be defined in pairs. That is, for each FieldName defined, a FieldValue must be defined as well.
Parameter Name FieldValue(1,2,3n)
Status
Output
The status of the InsertRecord operation. Status can have one of 2 values: Succeeded. Indicates that the operation succeeded. Failed. Indicates that the operation failed.
About NextRecord Method

Use the NextRecord method to advance to the next record in a list of business component records. Table 50 describes the input and output parameters for this method.
Table 50.
NextRecord Method Parameters Direction Input Output Description The name of a business component. The status of the NextRecord operation. Status can have one of 2 values: Succeeded. Indicates that the operation succeeded. Failed. Indicates that either the end record has reached or the operation failed with a system error.
Parameter Name BusCompName Status
24 1
Business Services for Siebel Financial Services Invoking the Business Rule Processor
Invoking the Business Rule Processor

A business rule process can be invoked from a workflow or Siebel script. While the processor cannot be directly invoked from a run-time event, it can be invoked from a workflow that is triggered by a runtime event. For all three of these invocation methods, you can prepopulate global variables through the input arguments of the BRP. Input argument names must match the global variables you define. For an example of how to invoke the BRP from a run-time event or a workflow, see the process for Data Validation Manager in Siebel Order Management Infrastructure Guide. For information on invoking the BRP from with eScript, see Using eScript to Invoke the Business Rule Processor on page 243. NOTE: Within each session, BRP Processor creates a copy of the BRP executable objects. The executable objects belong only to a single login session and are not shared. These executable objects are cached within a login session. Release processes either explicitly or implicitly when the open session is closed. The FINS CAP Processor Service Business Services exposes three methods. Table 51 describes these methods.
Table 51.
FINS CAP Processor Service Business Services Methods Input Arguments System_ProcessName - The name of a calculation process. Output Arguments None.
Method - Description LoadProcess - The named calculation process definition is loaded, and an executable instance of the process is instantiated in the current Web session. RunProcess - This method executes the named process. If the process definition has not been loaded, the processor loads the definition first. Whenever a BRP process is executed, the processor checks if the current process definition cached in the OM instance. If not, the processor instantiates the process definition into the OM instance. ReleaseProcess - This method releases the named process executable in the current Web session. This does not affect other open Web sessions.
System_ProcessName - The name of a calculation process.
System_ErrorCode System_ErrorMessage System_ErrorSource Return Codes. See Handling Business Rules Processor Errors on page 229.
System_ProcessName - The name of a calculation process.
None.
242
Business Services for Siebel Financial Services Invoking the Business Rule Processor
Using eScript to Invoke the Business Rule Processor

The following is an illustration of how to invoke the BRP using eScript.
Example of Loading the BRP Business Service

This example provides a sample eScript that loads a BRP process definition. var psIn = TheApplication().NewPropertySet(); var psOut = TheApplication().NewPropertySet(); var bs = TheApplication().GetService("FINS CAP Processor Service"); psIn.SetProperty ("System_ProcessName", "MyBRPProcessName"); bs.InvokeMethod("LoadProcess", psIn, psOut)
Example of Running the BRP Business Service

This example provides a sample eScript that executes a BRP process definition. The script also shows how to pass an input argument (g_AssetId) to a BRP process. function WebApplet_PreInvokeMethod (MethodName) { if (MethodName == "InvokeMyBRP") { var psinputs = TheApplication().NewPropertySet(); var psoutputs = TheApplication().NewPropertySet(); var oBusObj = TheApplication().ActiveBusObject(); var oBusComp = oBusObj.GetBusComp("FINS Group Policy"); var sAssetId = oBusComp.GetFieldValue("Id"); psinputs.SetProperty ("g_AssetId", sAssetId); psinputs.SetProperty ("System_ProcessName", "MyBRPProcessName"); var obs = TheApplication().GetService("FINS CAP Processor Service"); obs.InvokeMethod ("RunProcess",psinputs, psoutputs); return (CancelOperation); } return (ContinueOperation); }
24 3
Business Services for Siebel Financial Services Logging Business Rules Processor Debug Messages
Logging Business Rules Processor Debug Messages

BRP provides different levels of execution logging in the form of trace files to facilitate debugging a process. Currently, there are two levels of BRP logging. These levels are detailed in Table 52.
Table 52. Level 4 5
BRP Levels of Execution Logging Severity Detail Debug BRP Implementation Log the execution and initialization path of the BRP process without details. Log execution details. Under this level of logging, the values of local and global properties are logged as a part of the assignment statements. TIP: To check the value of a variable, use a dummy assignment step.
The BRP log level is set with the environment parameter SIEBEL_FACAP_LOG_EVENTS. BRP logging is written to the Siebel object manager log file. In order to enable BRP logging, the Siebel log level must also be informational or higher. For a mobile client, set the workstation system environment parameter SIEBEL_LOG_EVENTS = 3. The SIEBEL_LOG_EVENTS can be set from Server Administration. Refer to Siebel System Administration Guide for more information. In BRP logs, each local property is appended with its procedure name. For example, if a local property was defined as local_dMyIncome in Procedure Main, within the log file, this property would be identified as Main@local_dMyIncome. CAUTION: BRP log files can grow quickly. In general, the logs must be enabled only for administrators to do debugging.
Requirements Manager
The topic is about the Requirements Manager business service and includes the following topics: About Requirements Manager on page 245 Administering Requirements Manager on page 246 Creating Record Templates on page 246 Creating Requirement Templates on page 247 Using Requirements Manager on page 250 Creating Record Group Templates on page 250
244
Business Services for Siebel Financial Services Requirements Manager
Example of Using Requirements Manager for Record Group Templates on page 252
About Requirements Manager

The Requirements Manager is a business service that automatically generates activities, customer submissions, and workflows required at predetermined steps in the business process. For example, a loan applicant might be required to submit proof of employment, account statements, and other documents. The Requirements Manager allows a business analyst to specify conditions under which certain documents would be required in order to move the application process forward. The business service is invoked at a predetermined point during the application process to generate the appropriate follow-up activities for customer submissions. The Requirements Manager can be applied to a wide variety of usage scenarios including service processes such as the auto-creation of a fund transfer service request. Some examples of Requirements Manager scenarios are: Life Insurance. A life insurance policy might require a trailing document (a physical exam), an activity (such as an interview with an underwriter), and several forms to complete. If the product type = life insurance for instance, this set of requirements might be selected. However, an exclusion rule might be present to eliminate the need for the underwriter interview if the policy was for less than $100,000. Mortgage Application. A mortgage application might require several documents, several disclosures, two annual tax returns (documents), an appraisal (activities), and a credit check (workflows) to complete. This set of requirements might be run for every mortgage, but there might be an exclusion rule such that if the loan-to-value is less than 50%, the tax returns are not required.
The Closing Requirement view is preconfigured in the Applications and Life & Annuities screens. You can use this to view the output of the Requirement Manager business service, for requirement templates defined on the FINS Application, and FINS Life Policy business objects respectively.
Key Features of Requirements Manager

The Requirements Manager business service provides the following key features: Define multiple requirement templates that supports version control Provide support for conditional expression in each requirement template Define record templates that can insert records into any Siebel business object and component Invoke predefined workflows automatically to support the processes
About Invoking Requirements Manager

Requirement Manager is invoked the same as any other business service; through a workflow, runtime event, or script. At the time of execution, the service evaluates the various templates from which to execute, and executes each requirement where the exclusion rule evaluates to false.
24 5
Administering Requirements Manager

Administering the Requirements Manager business service involves the following steps:
1 2
Creating Record Templates on page 246 Creating Requirement Templates on page 247
Optionally, you can create record group templates in order to aggregate other record group template and record templates. See Creating Record Group Templates on page 250.
Creating Record Templates

The Record template is used to define templates that work in a specific business object/ component. It also defines the fields that automatically populate the template in that business object/component. Upon execution, the business service generates a record in the business object/business component and populates the fields according to the specified template.
To create a record template 1 2

Navigate to the Administration - Record Template screen, and then the Record Template view. In the Record Template list, create a new record, and complete the fields. Some of the fields are described in the following table. Field Template Name Display Name Business Object Description Name for the record template. The display name of the template as seen in the UI. The business object for the template to be enabled. For example, to auto populate a record in the Applications or Life & Annuities screen, you must select FINS Application or FINS Life Policy business objects, respectively. Business Component Business Component on the selected business object. The Record Template Administration view is preconfigured so you can specify the prefill of two applets in the Closing Requirements view: activities and documents. For example, to prefill the record in one of these two applets, you must select Action or INS Policy Document, or FINS Application Mortgage Trailing Documents business component.
246
In the Fields list, create a new record and complete the fields. Some of the fields are described in the following table. Field Sequence # Field Name Pre-Default Value Description Sequence number for the fields. The field name in the specified business component. The prefilled value for the field. NOTE: You can put conditional statements on this field. Business Component Read-only field of the business component name.
In the Related Record Template list, create a new record and complete the fields. The Related Record Template applet is used to specify child and grandchild of record templates. Upon execution, the business service inserts a record as specified in the parent record template, as well as all records specified in child and grandchild templates.
Creating Requirement Templates

The Requirement Template is used to aggregate several record templates. The record template specified in Creating Record Templates on page 246 only inserts one record in the business object/ business component. Insert multiple records in different business objects/components, by aggregating multiple record templates in a single requirement template. Additionally, in a requirement template, you can specify a workflow to invoke.
To create a requirement template 1 2

Navigate to the Administration - Requirement Template screen, and then the Workflows view. In the Requirement Template list, create a new record and complete the fields. Some of the fields are described in the following table. Field Template Name Display Name Business Object Description Name for the requirement template. The display name of the template as seen in the UI. The business object for the template to be enabled. For example, to pick the template name in Applications or Life & Annuities screen, you must select FINS Application or FINS Life Policy business objects, respectively.
24 7
Field Business Component
Description Business Component on the selected business object. For example, to be able to pick the template name in the Applications or Life & Annuities screen, you must select Opportunity or FINS Life Policy business components, respectively.
Condition
A valid Siebel query language expression. If this conditional expression evaluates to True then the rules under the rule-set would be evaluated. TIP: Use the expression builder to test the validity of conditional expressions.
Version
The version number of the template. NOTE: When you select the Revise button, the Siebel application automatically versions the template.
Status Start Date
Status of the template with values: active, pending active, inactive, outdated, and in progress. Start date for the template. You can specify a date in the future, and when activated, the status of the template changes to Pending Active. The application automatically changes the status to Active on the specified date and time, and executes the appropriate version of the template.
End Date
End date for the template. The application sets the status of the template to Outdated once the specified end date arrives.
In the Workflow list, create a new record and complete the fields. Some fields are described in the following table. Field Sequence # Workflow Name Description Sequence number for the workflow. Name of the workflow that is enabled for the business object/ business component specified in the requirement template. NOTE: The workflow called here must be deployed and active. Please see Siebel Business Process Framework: Workflow Guide for further information. Exclusion Rules A valid Siebel query language expression. If this conditional expression evaluates to True, then the workflow is excluded.
248
Field Execute Immediately
Description A flag to automatically execute the workflow when the requirement template is executed. This field must be empty to execute the workflow manually. See Using Requirements Manager on page 250 for information on executing the workflow manually.
Workflow Context
A text field passed as process properties to the workflow. The format of this field must be in the form of comma delimited, Name-Value pairs. For example: State, CA, Source BusComp, FINS Life Policy Where State and Source BusComp are property names, and CA and FINS Life Policy are property values, respectively.
Business Component
Read-only field similar to the business component specified in the requirement template applet. Identifies the business component on which the exclusion rules are evaluated.
4 5
Click the Record Template view tab. In the Record Template list, create new record, and complete the fields in the list. Some fields are described in the following table. Field Template Name Exclusion Rule Expectation Set Description Select the template you want to associate with the requirement template. A valid Siebel query language expression. If this conditional expression evaluates to True, then the record template is excluded. A flag to automatically invoke the Customer Expectations Manager. NOTE: The Customer Expectations Manager must be previously set for this to work. Please see Using the Customer Expectations Manager on page 265 for more information. Auto-Assign A flag to automatically invoke the Siebel Assignment Manager. NOTE: Assignment Manager must be previously set for this to work. Please see Siebel Assignment Manager Administration Guide for more information.
6 7 8
In the Requirement Template list, click Activate. (Optional) To revise the requirement template, click Revise. (Optional) To deactivate a requirement template, click Deactivate.
24 9
Using Requirements Manager

Use the Closing Requirement view, enabled in the Applications and Life & Annuities screens, to view the output of the Requirement Manager business service, for requirement templates defined on the FINS Application, and FINS Life Policy business objects respectively. However, through configuration, the Requirements Manager can be invoked from any screen. When invoked, the business service automatically prefills the target list or form with records as defined in the Administration - Requirement Template screen.
To invoke Requirements Manager 1

Navigate to either:

Applications screen, Application List view, and then the Closing Requirements view Life & Annuities screen, Life Policy List view, and then the Closing Requirements view
2 3 4
In the Templates list, create a new record. Select the template name as defined in Creating Requirement Templates on page 247. In the Templates list, click Execute. Requirements Manager prefills Activities, Workflow, and Documents lists based on the records specified in the Administration - Requirement Template screen.
Complete the fields in the Activities, Workflow, and Documents lists.
NOTE: If the workflow is not set to run automatically, you can set the workflow manually by clicking Execute in the Workflow list.
Creating Record Group Templates

The Record Group Template is used to define a template that works in a specific business object/ component. The Record Group Template is used to aggregate other record group template and record templates. A record group template is based on the business component relationship defined in the business object layer. You can use the record group template to recursively execute interrelated business components, and generate data in a particular business component. A record group template can include other related record group templates and related record templates. When the business service executes a record group template, it automatically, recursively executes any other related record template or related record group template defined. Creating a Record Group Template involves the following steps:
1 2 3
Creating Record Group Templates Creating Related Record Group Templates Creating Related Record Templates
For an example of setting up a record group template, see Example of Using Requirements Manager for Record Group Templates on page 252.
250
To create a record group template 1 2

Navigate to the Administration - Record Template screen, and then the Record Group Template view. In the Record Group Template list, create a new record and complete the fields. Some fields are described in the following table. Field Template Name Display Name Business Object Business Component Description Name for the record group template. The display name of the template as seen in the UI. The business object for the template. The business component on the selected business object.
In the Related Record Template list, create a new record and complete the fields. You can use the Related Record Template list to specify a child of the record group template. Upon execution, the business service inserts a record in the business component on which the record template is defined, for the corresponding parent record. Field Template Name Exclusion Rules Description Name of the child template record. A valid Siebel query language expression. If this conditional expression evaluates to True, then the related record template is excluded. A field indicating the number of times the record template must be executed within the context of the parent record group template. By default this is set to 1. Read-only field. Identifies the business component on which the exclusion rules are evaluated.
Repeat Expression
Business Component
In the Related Record Group Template list, create a new record, and complete the fields. You can use the Related Record Group Template list to specify the child record group template. Upon execution, the business service executes the business component on which this record group template is defined, within the context of the corresponding parent record group template. Field Template Name Description Name of the related record group template.
25 1
Field Exclusion Rules
Description A valid Siebel query language expression. If this conditional expression evaluates to True, then the related record template is excluded. Read-only field. Identifies the business component on which the exclusion rules are evaluated.
Business Component
Example of Using Requirements Manager for Record Group Templates

This topic provides an example of configuring record group templates for automatically generating vehicle coverages. Record group templates can be used to automatically generate default coverage for vehicles in an auto policy.
To setup auto coverage 1 2

Navigate to the Administration - Insurance screen, and then the Auto Coverages view. For each auto coverage in the Coverage Administration list, in the Coverage Values list, check the default flag for one of the values.
Configuring a Record Group Template for Generating Vehicle Coverages

Once you have set up auto coverage, in this example you next configure a record group template for generating vehicle coverages.
To configure a record group template for generating vehicle coverages 1 2

Navigate to the Administration - Record Template screen, and then the Record Template view. Create a new record in the Record Template list, and enter the values as shown in the following table. Field Template Name Display Name Business Object Business Component Value INS Vehicle Default Coverage Auto Default Coverages INS Policy INS Vehicle Default Coverage
252
Leave the Fields list empty. The predefault values set for the fields in this business component in Siebel Tools will be considered during execution.
Click the Record Group Template link bar, create a new record in the Record Group Template list, and enter the values as shown in the following table. Field Template Name Display Name Business Object Business Component Condition Value INS Vehicle Available Coverage Value Template INS Vehicle Available Coverage Value Template INS Policy INS Vehicle Available Coverage Value [Default]='Y'
5 6
In the Related Record Template list, create a new record and pick the record template defined in Step 2. Create another new record in the Record Group Template list, and enter the values as shown in the following table. Field Template Name Display Name Business Object Business Component Value INS Vehicle Template Default Vehicle Coverage Template INS Policy INS Vehicle
In the Related Record Group Template list, create a new record and pick the record group template defined in Step 2.
Creating a New Auto Policy

Once you have configured a record group template for generating vehicle coverages you can create the new auto policy.
To create a new auto policy 1 2

Navigate to Auto Policies screen and create a new policy. Drill down on the Policy # record to navigate to the Quick Quote view and create the following records:
a b
In the Vehicles list, create new vehicles In the Drivers list, create new driver records
25 3
Business Services for Siebel Financial Services Customer Authentication Manager
Click the Rate Model view tab. The vehicles list displays the vehicles created in the previous step.
Select a vehicle record and click Default Coverages. The Select Templates to Run dialog box appears, and displays the template defined in Step 6 after evaluating any conditional expressions defined.
In the dialog box, click Execute. Default Vehicle Coverages are automatically created in the Vehicle Coverage list for the selected vehicle record. These default coverages correspond to the default coverages selected in the Administration - Insurance views in Step 2.
Customer Authentication Manager

Financial service institutions require customer authentication before a financial transaction can take place. Furthermore, authentication becomes important as privacy and security regulations have become common in the retail banking, and also make their way into insurance and healthcare businesses. Typically, a bank might enforce tiered authentication policies that require a basic validation for transactions up to certain limit, and require more rigorous transaction-based authentication for transactions over the limit. In certain cases, for customers who perform regular high-value transactions, the bank might use token validation, common ones being RSA tokens, or scratch lists. Customer Authentication Manager is a utility that can be used to implement a secure and auditable customer authentication during a sales or service process. You can use the Customer Authentication Manager to prompt customer service representatives to authenticate a caller before providing any service. It provides the following key features: Ability to define multiple authentication templates using fields from the contact profile Rules-based, context sensitive invocation of authentication template Access from the global toolbar Audit trail of past authentication events; facilitates quick and accurate conflict resolutions Ability to define success and failure workflows to take appropriate actions
Administering Customer Authentication Manager business service involves the following steps:
1 2
Creating Customer Authentication Templates on page 254 (Optional) Defining Customer Authentication Rules on page 256
Creating Customer Authentication Templates

Customer authentication templates define the credentials used for authentication and the actions that follow a successful or a failed authentication attempt.
254
To create a customer authentication template 1 2

Navigate to the Administration - Application screen, and then the Authentication Template view. In the Templates list, create a new record, and complete the fields. Some fields are described in the following table. Field Name Description Success Workflow Comments Name for the authentication template. Description for the template. Invoke this Siebel workflow if the authentication is successful. The workflow called here must be deployed and active. The fields used for authentication are passed as process properties to this workflow. TIP: Use the success workflow to log the status of the authentication for audit purposes. Failure Workflow Invoke this Siebel workflow if the authentication failed. The workflow called here must be deployed and active. The fields used for authentication are passed as process properties to this workflow. Default If flagged as default, this template is used as the default template. The default template is invoked if all rules defined in the Authentication Rules fail. Only one template can be flagged as default. Alternate Template Defines an alternate template to use for authentication if the caller fails to authenticate using the current template. The alternate template is invoked by clicking the alternate button on the authentication pop up window.
In the Credentials list, create a new record, and complete the fields. Some fields are described in the following table. Field Business Object Comments Business Object for the credential field. In the current Siebel release, the Contact business object is the only business object that is available for use. Hence, this field is predefaulted and read-only. Business Component Business Component reference for the credentials field. The business component used here must be a valid business component on the Contact business object.
25 5
Field Field Name
Comments Name of the business component field. Only single value fields are supported; multi-value fields are not supported and might cause system instability if used.
Display Name Search Specification
The display name for the business component field. This specifies the label for the field at run time. For any one-to-many contact business component, the search specification provides the criteria to narrow selection to a single record. Flag indicates that the field must be verified for the authentication to be successful. If a required field is not confirmed at run time, the authentication fails. Defaults to No.
Required Flag
Defining Customer Authentication Rules

Customer authentication rules define the logic to select an authentication template. When the authentication manager is invoked, the business service steps through each rule for all applicable rule-sets to find a rule that evaluates to true. The template defined against this rule is used for authentication. If no rules are defined, or if none of the rules succeed, the default template, if defined, is used for authentication.
To create a customer authentication rule 1

Navigate to the Administration - Application screen, and then the Authentication Administration view.
256
In the Rule Sets list, create a new record, and complete the fields. Some of the fields are described in the following table. Field Name Description Business Object Business Component Conditional Expression Comments Name for the authentication rule set. Description for the rule set. Business Object context for evaluating the rules. Business Component context for the conditional expression and rules evaluation. A valid Siebel query language expression. If this conditional expression evaluates to True, then the rules under the rule-set are evaluated. TIP: Use the expression builder to test the validity of conditional expressions. Active Flag Flag to activate or inactivate a rule-set. The field predefaults to Inactive. NOTE: If the conditional expression is not used, there must be only one rule-set for each business object or business component defined. If there are multiple rule-sets for the same business object or business component, and a conditional expression is not defined, then the sequence of examination is undefined.
In the Rules applet, create a new record, and complete the fields. Some of the fields are described in the following table. Field Sequence Business Component Comments Sequence number for rule evaluation. Business component reference for the expression evaluation. This field predefaults to the BC on the rule-set definition, and is a read-only field. Inclusion Expression Siebel query language expression that specifies the rule. If this conditional expression evaluates to True, then the template associated with the rule is selected; further evaluation of the rules is aborted. TIP: Use the expression builder to test the validity of Inclusion expressions. Template Name The authentication template to use if the rule succeeds.
25 7
Invoking Customer Authentication Manager

Customer Authentication Manager is available preconfigured on the Contact, Members, and Providers screens. However, using Siebel Workflow, you can invoke the Customer Authentication Manager from any screen that contains a Contact, Member, or Provider business component.
To authenticate a contact 1 2 3 4
Navigate to the Contacts List view. Select the contact to authenticate and click the Authentication Manager icon on the toolbar. The Siebel Authentication Manager dialog box appears. Check the Confirmed checkbox for each field listed. Do one of the following: To... Authenticate. Click... Authenticate. If all required fields are confirmed, the authentication succeeds. Use an alternate template. Alternate. If an alternate template is defined, it appears. Cancel authentication. Cancel.
NOTE: When Authentication Manager is invoked, if a matching template is not identified, an error message appears.
Configuring Customer Authentication Manager to Handle More Fields

By default Customer Authentication Manager is configured to handle only a maximum of three fields. To use more than three fields in Customer Authentication Manager, you must add more virtual fields to the authentication business component, and expose them through the appropriate applet.
To configure Authentication Manager to handle more fields 1 2

Log in to Siebel tools. Navigate to the FINS Authentication Manager UI business component. The following fields are defined for the business component:

Field0, Field1 and Field2 Required Flag0, Required Flag1, and Required Flag2
258
Business Services for Siebel Financial Services Using the Calculation Manager
Ten confirmed flag fields
3 4 5 6 7 8 9
Define a new field called, Field3. Define a new field called, Required Flag3. Add a new confirmed flag field if you have more than 10 authentication fields. Navigate to the FINS Authentication Manager Popup Form Applet. Go to applet Control, and add the new fields: Field3, Required Flag3. Add a confirmed flag field if you have more than five authentication fields. (The applet already contains five confirmed flag fields). Add the fields and corresponding labels to the applet templates.
10 Compile the changes into the SRF.
Using the Calculation Manager

The Siebel Calculation Manager is designed to allow financial services institutions to declaratively define and execute simple to moderately complex calculations within their Siebel application. It is implemented as a business service that accepts input parameters for calculation, and the results are available as output parameters. The Calculation Manager is tightly integrated into the Siebel application architecture and can use Siebel Business component fields for input or output. The business service facilitates specification of embedded calculation by business analysts. Some examples of how Siebel Calculation Manager could be used: Loan Payment Schedule. The term, amount, and interest rate of a consumer installment loan are captured in a Siebel Application. Calculation Manager is invoked to generate a schedule of the amounts due, split by principle and interest for each month of the term. The user evaluates the schedule, runs several what-if scenarios with different loan amounts, and then exports the schedule to an excel spreadsheet. Currency Conversion. A user wants to know the value of $100,000 in Japanese yen at the current exchange rate. Calculation Manager is invoked, and an input dialog box is presented. The current exchange rate has been prefilled into the dialog box. The user enters 100,000 as an input, and clicks Calculate to see the result. The results are not saved. Early Withdrawal Penalty Calculation. A customer wants to remove money from a retirement account he holds, but there is a penalty involved. The calculation of the penalty is complex, and has been entered into the Siebel application as eScript. Upon invoking the Calculation Manager, the Siebel application pulls in the variables necessary for the penalty calculation and runs the eScript. The result is saved in the Siebel business component.
Specifying Calculation Rules

Calculations are entered as calculation rules in a list, similar to how validation rules or Siebel personalization rules are administered.
25 9
Calculation rules are specified in three stages:
1 2 3
Specify a calculation rule-set. Specify variables used in the calculation. Specify calculation details.
To specify a calculation rule-set 1 2

Navigate to the Administration - Application screen, and then the Calculation Manager view. In the Rule Sets list, create a new record, and complete the fields. Some fields are described in the following table. Field Name Comments Business Object Array Output Business Component Active Flag Script Flag Type Applet Title Comments Calculation rule set name. Rule-set names are language independent. Rule set description. Business object context for evaluating the rules. Business component context for writing the output of an array calculation, such as Amortization table calculation. Flag to activate the calculation rule set. By default a calculation rule set is inactive. Flag to indicate that the calculation rule is specified as a script, rather than declarative rules. List of values that provide the ability to categorize rules for easier administration. Title for the pop-up applet that appears when the calculation manager is invoked in the interactive mode.
Specifying Variables
After specifying a calculation rule-set, you must specify variables.
To specify variables 1 2
Navigate to the Administration - Application screen, and then the Calculation Manager view. Select a Rule Set for which you want to specify variables.
260
in the Variables list, create a new record and complete the fields. Some fields are described in the following table. Field Sequence Number Name Comments Sequence number for the variable specification. The variables on the pop-up applet appear in the sequence specified. Internal name for the variable used when specifying the calculation rule. Variable names can contain a maximum of 35 characters and cannot include spaces or arithmetic operators. Display Format Display format for the variable. Example, $###.## Display Name Type Business Component BC Field Name Label for the variable when presented to the user. Type of variable. Values are Input, Output, or Output Array. Business component context for the variable. Business Component field name. If the variable is an: Optional Input variable, the run-time value of the business component field name is assigned to this variable. Output variable, the value calculated for the variable is written into the business component field name.
Optional variables are variables not critical to the calculation, but might be specified to alter the calculation. This flag defaults to No.
Default Value Testing Value Suppress Display Variable Include
Default value for the variable in the calculations. This value appears in the dialog box for the variable. Value for the variable when the Calculation Manager is invoked in the simulator. Flag to indicate that the variable is hidden, and not displayed when calculation manager is invoked in the interactive mode. Include the variable in the script generation.
Specifying Calculation Details

After specifying variables, you can specify calculation details.
26 1
To specify calculation details 1 2 3

Navigate to the Administration - Application screen, and then the Calculation Manager view. Select a Rule Set for which you want to specify calculation details. In the Rules list, create a new record, and complete the fields. Some fields are described in the following table. Field Sequence Number Expression Comments Sequence number for the rule execution. Calculation expression. The expression is guided by the following: Operator Support. All basic arithmetic operators, including exponents, are supported (+,-,*,/,^). Nested quantities (that is parentheses) are also supported. Simple Calculations. Simple calculations, such as a+b=c, are defined in a single row. Compound Calculations. Multiple rows of calculations specified in a single Template. This enables multiple variables to be calculated independently, and then used in subsequent calculations. For-Next Logic. Simple looping enables the generation of arrays. Use a For statement and a Next statement to accomplish looping. Example:

row 1: For N=1 to Period, row 2: [calculation] row3: Next N
For-Next loops might be nested. If-Then-Else Logic. Simple If-Then-Else logic is supported declaratively. As in the case of For-Next, If-Then-Else statements appear on multiple rows of the calculation set. Nesting of If-Than-Else statements is supported.
Example of Using Embedded eScript for Mortgage Calculation

For compound calculations, embedded eScript is a more appropriate mechanism. The following is an example of a mortgage calculation using eScript: var var var var Amount= 0; NumPeriods= 0; Rate= 0; InterestPaid = new Array;
262
var var var var var var var
Payment = new Array; Period = new Array; PrincipleBalance = new Array; PrinciplePaid = new Array; PeriodPayment = 0; TotalInterest = 0; TotalPayment = 0;
function GetInput (Inputs) { with(Inputs) { var temp; temp = GetProperty(Amount); if (temp.length!=0) Amount= ToNumber(temp); temp = GetProperty("NumPeriods"); if (temp.length!=0) NumPeriods= ToNumber(temp); temp = GetProperty("Rate"); if (temp.length!=0) Rate= ToNumber(temp); } } function Main() { Period[0] = 0; InterestPaid[0] = 0; PrinciplePaid[0] = 0; Payment[0] =0; PrincipleBalance[0] = Amount; Rate = Rate /1200; PeriodPayment = Amount / (1.00/Rate - (1.00/Rate)/Math.pow((1.00+Rate), NumPeriods)); for(var i=1; i<=NumPeriods-1; i++) { Period[i] = i; InterestPaid[i] = PrincipleBalance[i-1]*Rate; Payment[i] = PeriodPayment; PrinciplePaid[i] = Payment[i]-InterestPaid[i]; PrincipleBalance[i] = PrincipleBalance[i-1] - PrinciplePaid[i]; }
26 3
TotalPayment = NumPeriods * PeriodPayment; TotalInterest = TotalPayment - Amount; } function Service_PreInvokeMethod (MethodName, Inputs, Outputs) { GetInput(Inputs); Main(); SetOutput(Outputs); return( CancelOperation ); } function SetOutput (Outputs) { Outputs.SetType("Result"); var psArray = TheApplication().NewPropertySet(); psArray.SetType("Array"); var len = InterestPaid.length; for(var j=0; j<=len-1; j++) { var psArrayElement = TheApplication().NewPropertySet(); psArrayElement.SetProperty("InterestPaid",InterestPaid[j]); psArrayElement.SetProperty("Payment",Payment[j]); psArrayElement.SetProperty("Period",Period[j]); psArrayElement.SetProperty("PrincipleBalance",PrincipleBalance[j]); psArrayElement.SetProperty("PrinciplePaid",PrinciplePaid[j]); psArray.AddChild(psArrayElement); } Outputs.AddChild(psArray); var psPeriodPayment= TheApplication().NewPropertySet(); psPeriodPayment.SetProperty("PeriodPayment",PeriodPayment); Outputs.AddChild(psPeriodPayment); var psTotalInterest= TheApplication().NewPropertySet(); psTotalInterest.SetProperty("TotalInterest",TotalInterest); Outputs.AddChild(psTotalInterest); var psTotalPayment= TheApplication().NewPropertySet(); psTotalPayment.SetProperty("TotalPayment",TotalPayment); Outputs.AddChild(psTotalPayment); }
264
Business Services for Siebel Financial Services Using the Customer Expectations Manager
Invoking Siebel Calculation Manager

Siebel Calculation Manager is invoked from within a Siebel workflow and can be triggered using a mini-button on an applet. Use a business service step to invoke Siebel Calculation Manager in a workflow. Using the FINS Calculation Engine Business Service and the Calculate business service method, set the input arguments as described in Table 53. There are no output arguments for this business service.
Table 53. Name
Input Arguments to Invoke Calculation Manager Type Literal Literal Process Property Literal Literal Literal Comments Calculation Rule name Primary Business Component name Typically the Object Id of the Workflow Y or N Child Business Component name Child Business Component row id
Rule Expression Name Primary BC Name Primary BC Rowid Save To BC Child BC Name (Optional) Child BC RowIdn (Optional)
When invoked interactively, the calculation manager displays a pop-up dialog box with the input and output arguments. Perform the calculation by entering all input arguments and clicking the Calculate button. A second pop-up dialog box appears with the calculated values. Finish the calculation by clicking the Cancel button.
Using the Customer Expectations Manager

Managing customer expectations around the length of time it takes to complete their requests is crucial in maintaining customer satisfaction. Although many financial transactions complete in seconds, a number of key relationshipenhancing tasks require lead time of one or more days to complete. For example: Bank check deposits might not be available for immediate withdrawal and are subject to clearing. Credit and insurance applications typically undergo an underwriting process where the application is evaluated for its creditworthiness, risk profile, and other factors that go into approval and pricing. Fast turnaround is a competitive differentiator. Healthcare service complaints and grievances are handled through a structured review and appeals process. In many jurisdictions, the processing of the complaints and grievances must meet regulatory standards.
26 5
The Siebel Customer Expectations Manager (CEM) provides the ability to use historical estimates of task completion times to aid the customer service representative in setting expectations for service completion. It is most useful in situations where a standardized process is being executed, and there is a need to estimate the expected completion date. Siebel CEM has the following two key features: Ability for an administrator to input the factors governing the time to complete task. A run-time engine that sets Due Date and Expected Close Date for the enabled objects.
NOTE: For CEM compared to Agreements/Entitlement Metrics, it is possible to establish an agreement for an account that includes entitlements mandating the completion of Service Requests within specified entitlement metrics. When these are setup, and the user navigates to the Service screen, they see a Verify button. Clicking this button invokes the calculation of an Agent Committed Time. The entitlement metrics calculate a contracted due date. In contrast, CEM calculates an estimated completion time or due date based on how long a process historically takes to complete. In cases where a service agreement is in place, the contracted dates take precedence.
Defining Customer Expectation Manager Rules

The CEM administration screen holds the historical estimates for task completion times and the rules for selecting an appropriate line. When CEM is invoked, the business service steps through each rule for all applicable rule-sets to find a rule that evaluates to true. The estimates defined against this rule are used for calculation of expected times.
To create a CEM rule 1

Navigate to the Administration - Application screen, and then the Customer Expectations Manager view.
266
In the Rule Sets Applet, create a new record, and complete the fields. Some fields are described in the following table. Field Name Business Object Business Component Conditional Expression Comments CEM rule set name. Business object context for evaluating the rules. Business component context for the conditional expression and rules evaluation. A valid Siebel query language expression. If this conditional expression evaluates to True, then the rules under the rule-set would be evaluated. TIP: Use the expression builder to test the validity of conditional expressions. Active Flag Flag to activate or inactivate a rule-set. The field predefaults to Inactive. NOTE: If the conditional expression is not used, there must be only one rule-set for each business object/business component defined. If there are multiple rule-sets for the same BO/BC, and a conditional expression is not defined, then the sequence of examination is random.
In the Rules list, create a new record, and complete the fields. Some fields are described in the following table. Field Sequence Business Component Comments Sequence number for rule evaluation. Business component reference for the expression evaluation. This field predefaults to the BC on the rule-set definition and is a read-only field. Conditional Expression Siebel query language expression that specifies the rule. If this conditional expression evaluates to True, then the estimates associated with the rule is selected; further evaluation of the rules is aborted. TIP: Use the expression builder to test the validity of Inclusion expressions. Name Unique name for the rule. Used to improve performance of the rule-set search during execution. Internally, a user key is constructed on the name field.
26 7
Field Schedule
Comments Schedule to use for calculating the expected completion times for the task. Schedules govern the working hours, holidays, and downtime. If selected, the start time for the task is calculated using the schedule. Schedules are administered by navigating to the Administration Service screen, and then the Schedules view. Refer to Siebel Field Service Guide for details on schedule administration.
Use Employee Schedule Unit Preparation Time Expected Time Slack Time Auxiliary Field
If flagged, the employee schedule is used to calculate the start time. Employee schedule override the default schedule. Unit of measure for the preparation, expected and slack times. Valid units: Minutes, Hours, or Days. Queue time for the task. Expected time to complete the task. Time buffer to allow for deviations from the expected completion time. (Optional) Specify Business Component field-value pairs. The specified fields are updated with the values based upon the rule selected. Example: "Priority","0-ASAP"
Invoking Customer Expectations Manager

In the current version of Siebel Financial Services, CEM is enabled for the Service Request object.
To invoke CEM 1
Click the Calculate Dates button on the Service Request form. The CEM business service is invoked, and based on the administrative setup a pop-up dialog box appears with the expected completion dates for the service request. Closing the dialog box, the expected completion times are written into the current service request.
Click the show more button on the Service Request form to view the expected completion times in the Internal Tracking - Expected Times section.
268
Business Services for Siebel Financial Services Automating Approval Processing
Automating Approval Processing

In Siebel Insurance, administrators can define a number of approval levels without the need for programming, scripting, or configuring. You can define both basic or multiple step approval processing levels based on the needs of your organization. You can invoke approval processing from a workflow or a run-time event. Automating an approval process involves the following steps: Administrator defines approval items and approval stages. For more information, see Defining Approval Items and Approval Stages on page 269. Administrator invokes approval processing. For more information, see Invoking FINS Approval UI Service from a Workflow on page 270. End users approve or decline an approval stage. For more information, see Approving or Declining Approval Stages (End User) on page 272.
Defining Approval Items and Approval Stages

An administrator defines the approval process by creating approval items and approval stages in the Approval Admin view.
To define approval items and stages 1 2 3

Navigate to the Administration - Application screen, and then the Approval Admin view. In the Approval Item list, add a record and enter a name in the Approval Item field. In the Approval Flow Type field, select one of the following:
Sequential. Indicates this Approval Item is distributed to approvers one after another in the sequence specified in the Approval Stage. The application routes the Approval Item to the next approver only if the current approver approves the request. If any approver in the approval chain declines the request, the Approval Item is rejected and no further routing is conducted. Parallel. Indicates this Approval Item is distributed to all approvers simultaneously for approval. The Approval Item is rejected if at least one approver declines the approval request.
Once you have defined an Approval Item, the next step is to define the appropriate approval stages. The Approval Item and Approval Stage lists have a parent-child relationship.
26 9
In the Approval Stage list, add a record for each approval stage and complete the necessary fields. Some fields are described in the following table. Field Sequence # Comments Identifies the numeric sequence of this Approval Stage in the current Approval Item. The application executes Approval Stages in numerical order based on this number. Specifies whether the approver is a position or an employee. Indicates the login name tied to this Approval Stage. Relevant only if Approval Type is Employee. Indicates the position tied to this Approval Stage. Relevant only if Approval Type is Position.
Approval Type Owner Login Name Owner Position
End users use the My Approval Inbox view to approve an approval item. For more information, see Approving or Declining Approval Stages (End User) on page 272.
Invoking FINS Approval UI Service from a Workflow

Invoke FINS Approval UI Service from a workflow by creating a workflow process in Siebel Tools containing the following steps: Start. Initiates the process instance. When the conditions have been met, the application initiates the process instance. See Configuring the Start Step on page 271 for details. Business Service. A step in a process in which an automated call is made to the FINS Approval UI Service. A workflow process definition can have one or more business service steps. See Configuring the Business Service Step on page 272 for details. End. A step in a process that specifies when a process instance is finished.
In order for your workflow to execute correctly, the Start and Business Service steps must meet the minimum requirements described in the referenced topics. For more information on workflows, see Siebel Business Process Framework: Workflow Guide.
270
Configuring the Start Step

Table 54 details some of the start step parameters for the workflow process.
Table 54. Field Event
Parameters for Start Step Comments The specific event that happens to the object. The set of available events is different for different object types. Example Use the WriteRecord business component event if you want to trigger the approval process after the record is written to the database. Use the WriteRecordNew business component event if you want to trigger the approval process after a new record is written to the database.
Event Object
The name of the application, business component, or applet to which the event occurs. The type of object to which the event occurs. This can be an application, business component, or applet. The name of the Next step branch. The name of the branch must be unique or you cannot import or export the workflow process.
Contact
Event Object Type
BusComp
Name
Next Step Type
The name of the step that follows when conditions are met. The type of branch.
Picklist of existing process steps. The value can be one of the following: Condition. This value indicates that a condition is defined for the branch. Default. This value indicates that if nothing else is satisfied, then this branch is followed. Additionally, if this value is used, any conditions defined for the branch are ignored.
27 1
Configuring the Business Service Step

Table 55 details some of the business service step parameters for the workflow process. Table 55. Field Business Service Method Parameters for Business Service Step Value FINS Approval UI Service Create Approval Stage
Table 56 details the input arguments for the workflow process. Table 56. Input Arguments for Business Service Step Property Name Object Id Approval Item Name Requesting Buscomp Comments Row Id of the object (for example, a Service Request) that needs approval processing. Name of the Approval Item defined in the Approval Admin view. Name of the business component object (for example, a Service Request) that needs approval processing.
Input Argument Approval Item ID Approval Item Name Requesting Buscomp
Approving or Declining Approval Stages (End User)

End users approve approval items in the My Approval Inbox view. Users can view approval items by login name or position. For more information on setting up approval processing, see Defining Approval Items and Approval Stages on page 269.
To approve or decline an approval stage 1 2

Navigate to the My Approval Inbox screen. Select one of the following views:

My Approvals. Displays all approval items associated with the users login name. My Position Approvals. Displays all approval items associated the current users position.
3 4
To view additional details about an approval item, drill down on the Approval Identifier link. In that Status field, select Approve or Decline. Once you select a status, the application populates the Approval By and Approval Date field and sets the record to read-only.
272
Business Services for Siebel Financial Services Automating the Display of Disclosure Documents
Automating the Display of Disclosure Documents

Disclosure processing allows companies to comply with internal company policies and external regulations. These policies and regulations require they display disclosure statements or external documents to users, and then record whether or not they have read and understood them. Implementing the automatic display of disclosure documents involves the following steps: Set up a disclosure by associating it with a product and literature. For more information, see Setting Up Disclosures on page 273. Activate the appropriate workflows. For more information, see About Disclosure Workflows on page 274. Invoke the Disclosure UI Service business service. For more information, see Invoking the Disclosure UI Service Business Service on page 276. View a disclosure history. For more information, see Viewing Disclosures Associated with Contacts (End User) on page 276.
Setting Up Disclosures
To implement disclosure processing, you must associate each disclosure with a product and then, if applicable, with the appropriate document.
To associate a disclosure with a product 1 2 3 4

Navigate to the Administration - Product screen, and then the Disclosure view. In the Product form, query for the product. In the Disclosure list, add a new record, and complete the necessary fields. To activate a disclosure, select it in the Disclosure list, and click Activate. Clicking Activate, changes the Status from In Progress to Active and makes the record read-only.
Revising an Existing Disclosure

If necessary, you can revise an existing disclosure.
To revise an existing disclosure 1 2

Navigate to the Administration - Product screen, and then the Disclosure view. In the Product form, query for the product.
27 3
In the Disclosure list, select the disclosure to be revised, and click Revise. Clicking Revise creates a new version of the disclosure and sets its status to In Progress.
Make the appropriate changes to the new disclosure, and click Activate. Clicking Activate, changes the Status from In Progress to Active and makes the record read-only. The prior version of the disclosure still appears, but displays a Status of Outdated.
To associate literature with a disclosure, add a new record in the Literatures list, and complete the necessary fields.
For more information on loading literature into Siebel Insurance, see the sharing literature discussion in Siebel Applications Administration Guide.
About Disclosure Workflows

Siebel Insurance includes three workflows that help manage the display of disclosure documents and disclosure event logging. Table 57 describes each workflow.
Table 57.
Disclosure Workflow Processes Comments The FINS Disclosure Workflow process accomplishes the following tasks:
Workflow Process FINS Disclosure
Invokes the Setup method of the Disclosure UI Service business service. Invoking this method sets up the appropriate disclosure documents based on the selected product. Calls the FINS Disclosure Goto File View subprocess. This subprocess navigates users to the Disclosure Documents list, where they can review all the disclosure documents pertaining to the selected product. This subprocess also navigates users back to the previous view after they accept or decline the disclosure. This final navigation step is accomplished by invoking the View Back method of the Disclosure UI Service. Calls the FINS Disclosure Create Activity Sub Workflow subprocess. If the user accepts the disclosures, the workflow calls the FINS Disclosure Create Activity Sub Workflow subprocess to log the disclosure activity.
274
Table 57.
Disclosure Workflow Processes Comments This subprocess navigates users to the Disclosure Documents list, where they can review all the disclosure documents pertaining to the selected product. This subprocess also navigates users back to the previous view after they accept or decline the disclosure. This final navigation step is accomplished by invoking the View Back method of the Disclosure UI Service. If the user accepts the disclosures, this sub process logs the disclosure activity.
Workflow Process FINS Disclosure Goto File View
FINS Disclosure Create Activity Sub
Before you can display disclosure documents, you must: Deploy the workflow processes using Siebel Tools. For more information, see Siebel Business Process Framework: Workflow Guide. Activate the workflow processes described in Table 57. For more information, see Activating Workflows on page 275. Invoke the Disclosure UI Service business service. For more information, see Invoking the Disclosure UI Service Business Service on page 276.
Activating Workflows
Use the following procedure to activate the workflows used to display disclosure documents.
To activate the workflows used to display disclosure documents 1 2

Navigate to the Administration - Business Process screen, and then the Workflow Deployment view. In the Repository Workflow Processes list, use a query to find all processes where the Name field contains the word Disclosure. NOTE: You can query on *Disclosure*.
Activate each workflow process shown in Table 57 on page 274, that has a status of Inactive.
a b 4 a b
Select the workflow process record. Click Activate.
To verify that the Status is Active for each process: In the lower Active Workflow Processes list, query again for Name = *Disclosure*. For each process, check that Deployment Status = Active.
27 5
Business Services for Siebel Financial Services SmartScript Integration with Workflow
Invoking the Disclosure UI Service Business Service

You can invoke the Disclosure UI Service from a workflow. This topic describes some of the possible steps you can include to enable this invocation. You might want to modify and expand on this procedure to accommodate more complex business requirements. The workflow process you create must contain the following steps: Start. Initiates the process instance. When the conditions have been met, the application initiates the process instance. Sub Process. Calls the FINS Disclosure Workflow. When creating this step, you must populate the following inputs:

Contact Id. The Row Id of the contact who places the order of the product. Disclosure Name. The name of the Disclosure that relates to the product. Product Id. The Row Id of the product that the customer has ordered.
End. A step in a process that specifies when a process instance is finished.
For more information on workflows, see Siebel Business Process Framework: Workflow Guide.
Viewing Disclosures Associated with Contacts (End User)

All end users can view disclosures associated with a specific contact on the Contacts Disclosures view. This view is read-only and displays the: Disclosure name Date the disclosure was presented to the user Date the user acknowledged the disclosure Date the user accepted the disclosure
For more information on setting up disclosure processing, see Automating the Display of Disclosure Documents on page 273.
To view a disclosure history 1 2 3

Navigate to the Contacts screen, and then the Contacts List view. In the Contacts list, drill down on the contact. Click the Disclosures view tab.
SmartScript Integration with Workflow

You can invoke a SmartScript from a workflow process and pass parameters from the SmartScript to the workflow process. These business services support SmartScript integration with workflow:
276
FINS Web Shopping Service. For methods, see FINS Web Shopping Service Methods on page 279.
FINS SmartScript Output Service. For methods, see FINS SmartScript Output Service Methods on page 279.
NOTE: In order to completely understand the concepts in this topic, familiarity with SmartScript is required. For more information, see Siebel SmartScript Administration Guide. For a detailed explanation about how to integrate SmartScript with Workflow, see Example of Integrating SmartScript with Workflow on page 277.
Example of Integrating SmartScript with Workflow

The scenario outlined in this topic is an example of how to insert a SmartScript in a workflow process. After the SmartScript ends, the workflow proceeds to the next step in the workflow process. Your company might follow a different workflow that fits its business requirements. In this scenario, you are designing a SmartScript that allows customers to complete a loan application online. After the loan application is complete, your workflow verifies the customers address in an external system.
To configure SmartScript integration with Workflow 1

In the SmartScript, create Save User Parameters for the parameters you want to pass to the workflow. For more information on SmartScript user parameters, see Siebel SmartScript Administration Guide. Create a Business Service step for your workflow, using the FINS Web Shopping Service business service, and enter the input arguments described in Table 58 on page 279. Create a subprocess to invoke the SmartScript using the workflow User Interact step. The subprocess is based on the SmartScript Player business object and has three steps: a start step, a user interact step, and an end step.
2 3
In the user interact step, set the view name to FINS SmartScript Player View (App).
27 7
In the Next Steps applet, add two conditions, entering the information listed in the following tables:
Entries for Record 1 (first condition): Field Branch Name Type Next Step Event Object Type Event Event Object Subevent Entries for Record 2 (second condition): Field Branch Name Type Next Step Event Object Type Event Event Object Subevent Entry Finish Condition End Applet Invoke Method Smart Script Player Applet (FINS eSales App) FinishScript Entry Cancel Condition End Applet Invoke Method Smart Script Player Applet (FINS eSales App) CancelScript
Add a Business Service step using the FINS SmartScript Output Service business service. Enter the output arguments described in Table 59 on page 279.
Now you might either end your workflow process or include additional steps, depending on your companys business requirements. The SmartScript is integrated in your workflow process.
278
Business Services for Siebel Financial Services Dynamic UI Business Service
FINS Web Shopping Service Methods

The FINS Web Shopping Service business service methods are described in Table 58.
Table 58. Method
FINS Web Shopping Service Methods Description / Arguments Input Arguments: Script Name (Required): The name of the SmartScript you want to invoke. SSUserParameter# (Required): A SmartScript user parameter between 1 and 20. For example, SSUserParameter1. The value for the input argument must be the exact name of the user parameter specified in the SmartScript, whose value must be passed into the workflow process at the conclusion of the SmartScript.
SetSmartScriptName
FINS SmartScript Output Service Methods

The FINS SmartScript Output Service business service methods are described in Table 59.
Table 59. Method SetOutput
FINS SmartScript Output Service Methods Description / Arguments Reads the SmartScript user parameters and outputs them as workflow properties: Output Arguments: The name of the user parameter. Specifies the SmartScript user parameters as output arguments, and passes the value of the user parameters back to the workflow process when the SmartScript ends. These output arguments can be mapped to process properties. SmartScript Result Action: Returns the action users take to end the SmartScript. Possible values are Finish or Cancel.
Dynamic UI Business Service

This business service and associated administration views allow you to create and render views containing a single read-only applet in the Siebel Financial Services application. These views and applets, called dynamic applets, allow business analysts and developers to make frequent changes to the user interface without the need to recompile and redeploy a Siebel Repository File (SRF).
27 9
The following topics are included in this topic: Example of Creating a Dynamic Applet with the Dynamic UI Business Service Displaying Dynamic Applets in a Workflow
Example of Creating a Dynamic Applet with the Dynamic UI Business Service

The scenario outlined in this topic is an example of a Dynamic UI Service in a workflow process. Your company might follow a different workflow that fits its business requirements. You would like to set up your companys user interface to dynamically display read-only views at run time, based on user input. For example, a customer requests a quote for an auto insurance policy. The policy includes the option to cover additional drivers. After the customer enters additional driver information, the workflow process uses a Dynamic UI applet to display a read-only list of the additional drivers for review. Customers can review the list, then select an option to continue the process. To set up a similar user interface for your business, follow the instructions that follow.
To create a dynamic applet 1 2

Navigate to the Administration - Finance screen, and then the Dynamic Applet Administration view. In the Dynamic Applet list, click New, then enter the view alias and view name. The view alias must be a unique name. The view name is a picklist of the views defined in the Template Definition view.
3 4
Step off the record. The Applet Instance list automatically displays the name of the applet template defined for this view. In the Applet Instance list, enter the applet title, business object name, and business component name. The business object and business component determine the fields to display for this applet.
If you want to set up a default search specification, enter:

Business component field. Specifies the field on which to base your search. Default. Specifies a default value for which you want to search.
In the Field Control list, add a new record for each field you want to display. Each field control is displayed as a read-only text box with a text label. For each record, enter:

Display Sequence number. Indicates the display order for the field. For list applets, the order is left to right. For form applets, the order is left to right and top to bottom. Field name. The business component field whose value you want to display. Caption. The display label for the field.
280
In the Button Control list, add a new record for each button you want to display. Enter the sequence number, caption, and method for each button.

Display Sequence. Indicates the display order for the button, from left to right. Caption. The display label for the button. Method. The method invoked when the button is clicked. The method name must begin with FrameEventMethod. For example, FrameEventMethodContinue.
Displaying Dynamic Applets in a Workflow

Workflows can invoke a dynamic applet as part of a process defined for a product application. This feature allows an application administrator to establish applet instances without requiring recompilation and redeployment of individual applets.
To integrate the dynamic applet in a workflow 1 2 3 4

Create a subprocess based on the FINS Dynamic UI business object. Add a Dynamic UI Service business service step and invoke the Set View Name method described in Table 60 on page 282. (Optional) Add a second Dynamic UI Service business service step and invoke the AddRecord method described in Table 60 on page 282. Add a User Interact step to display the dynamic applet.
a b
For the view property of the User Interact step, enter the view template name defined in Step 2 of Example of Creating a Dynamic Applet with the Dynamic UI Business Service. For each button that might be clicked in the dynamic applet, add entries into the Next Steps list applet of the User Interact step. The following is an example of such an entry: Entry Continue Button Condition End Applet InvokeMethod FINS Dynamic UI List Applet FrameEventMethodContinue
Field Branch Name Type Next Step Event Object Type Event Event Object Subevent
28 1
The Dynamic UI Service business service methods are described in Table 60.
Table 60. Method
Dynamic UI Service Methods Description and Arguments Input Arguments: View Alias (Required): The view alias defined in Step 2 of Example of Creating a Dynamic Applet with the Dynamic UI Business Service.
Set View Name
AddRecord (Optional)
Overrides the default search specification value. Input Arguments: Business Component Name (Required): The name of the source business component. Object ID (Required): The row ID of the business component.
Creating a View Template for Dynamic Applets

Creating a view template involves first creating views and applets based on specialized applet classes within Siebel Tools. These views and applets contain placeholder fields. Placeholder fields are applet controls that are not mapped to any particular business component. The views and applets then form the basis of view templates and applet templates. You can use a single view and applet template to create any number of dynamic applets. Two templates are provided as part of seed data: a view template containing a list applet template, and a view template containing a form applet template. The view templates are named as follows: FINS Dynamic UI Form view. A view template that contains a form applet template. FINS Dynamic UI view. A view template that contains a list applet template.
For more information about creating views and templates within Siebel Tools, see Using Siebel Tools. When creating dynamic applets in Siebel Tools, note the considerations listed as follows. (Use of the word applet in the following bulleted list refers to applets created in Siebel Tools.) When setting applet class, use:

CSSFrameListFADynamicUI for list applets CSSFrameFADynamicUI for form applets
If using a preconfigured business component, the applet business component must be FINS Dynamic UI.
282
Business Services for Siebel Financial Services FINS Application View Navigation
If you create your own Virtual Business Component (VBC) in Siebel Tools, the business class must be CSSBCVDynamicUI. Dynamic Applet supports 20 fields and five currency codes (that is, five types of currency value). In your new VBC, all field names must start with the prefix Field and a number value, (for example, Field0..., Field19). All currency code fields must start with the prefix Currency Code and a number value, (for example, Currency Code0..., Currency Code4).
It is recommended that applets based on the same VBC have their corresponding views use a different business object.
Once the views and applets have been created in Siebel Tools, in order to define them as view templates and applet templates, they must be added to the Template Definition view.
To add views and applets to the Template Definition view 1 2 3

Navigate to the Administration - Finance screen, Dynamic Applet Administration view, and then the Template Definition view. In the Template Definition list, click New, and then enter the view name. In the Applet Template Definition list, click New, and then enter the applet name.

The FINS Application View Navigation Service guides users through a series of views based on administration data. The view list is dynamically generated according to the products associated with the current record. It replaces the Next/Previous button functionality, known as the FINS Application Workflow, in previous releases. The following topics are presented in this topic: Business Service Methods on page 283 Business Service Behaviors on page 284 Business Service Administration on page 285 Example of FINS Application View Navigation on page 285 Upgrade Note on page 286
Business Service Methods

The business service has two methods: GetNextViewName. Gets the next view name without view navigation. GotoNextView. Navigates to the next view.
28 3
Table 61 describes the arguments for these methods.
Table 61. Name BusComp
FINS Application View Navigation Service Arguments Type Required Optional Optional Optional Output Description The master business component through the view navigation. Forward or Backward. Default is Forward. Product Id value. The field in the business component that is used to retrieved Product Ids. 0: success 1: EOF 2: BOF 3: Error
Navigation Direction Product Id Product Id Field Status
Next View Name FINS View Navigation Mgr Admin BC
Output Optional
Name of the Next View. Name of the admin business component.
Business Service Behaviors

The FINS Application View Navigation Service is constrained by the following behaviors: The business service can be invoked from any screen. The navigation is limited to the views in the current screen that are accessible to the current login. For example, if there is a product that is associated with views in both the Contact and Opportunity screens, and the invocation occurs inside the Contact screen, views in the Opportunity screen are ignored. Furthermore, the views that the current login do not have access to are also ignored. A view in the view list that is left by clicking the Next button, is treated as a visited view. At any point in the view navigation, if a next view request is triggered and there are views ahead of the current views not marked as visited, the service navigates to the skipped views. During the navigation sequence, do not change the master business component record row ID. Otherwise, all the views will be treated as unvisited after the record change.
284
Business Service Administration

The FINS Application View Navigation Service is administered through the Administration - Product screen.
To administer the FINS Application View Navigation business service 1 2 3 4 5

Navigate to the Administration - Product screen, and then the Products view. In the Products list, query for the product, and drill down on the product name link. Click the More Info view tab. In the More Info form, click the Application Workflow view link. Create new records to associate views and their sequence to the product.
NOTE: You can associate views from any screen with a product. If you specify views with a gap in the sequence on two different products and add both those products to, for example, an Application, you navigate based on sequence number and not on product. For example, if you specify: View V1 with sequence 1 and view V2 with sequence 3 on product A And then also specify view V3 with sequence 2 and view V4 with sequence 4 on product B And then proceed to add both these products to an Application
The navigation sequence will be V1, V3, V2, V4.
Example of FINS Application View Navigation

The FINS Application View Navigation Service is used in Siebel Insurance on the Application screen, where the Application form contains Previous and Next buttons. The invocation on the Application screen uses Applet Named Method, a feature of frame classes derived from CSSSWEFrameBase and CSSSWEFrameListBase. The applet User Property has the following name/value pairs: Named Method 1: GotoPreView 'INVOKESVC', 'FINS Application View Navigation Service', 'GotoNextView', '"BusComp'", "'Opportunity'", "'Navigation Direction'", "'Backward'", "'Product Id Field'", "'Opportunity Product Id'"
Named Method 1: GotoNextView 'INVOKESVC', 'FINS Application View Navigation Service', 'GotoNextView', "'BusComp'", "'Opportunity'", "'Navigation Direction'", "'Forward'", "'Product Id Field'", "'Opportunity Product Id'"
28 5
The Next and Previous buttons are mapped to methods as follows: Previous Next GotoPreView GotoNextView
Upgrade Note
In previous releases, the function provided by the FINS Application View Navigation business service was available through NextView and PrevView methods in CSSSWEFrameFINApplication. These methods are no longer supported since Siebel Insurance 7.7. If you have upgraded to Siebel Insurance 7.8 from a release prior to Siebel 7.7, the Next and Previous buttons must be reconfigured following the example provided in Example of FINS Application View Navigation on page 285.
286
Index
Symbols
35
A
accounts Financial Services, as used in 20 action items associating with call reports 71 activities group pension plan, creating activity associated with 82 viewing aggregated activities for a company 42 activity plan templates group policies, creating activities for the template 164 group policies, creating for 163 agencies agents, adding 178 business scenario, company signs new agent 176 business scenario, employee adds a new agency 176 defined 175 information, adding information associated with an agent 178 new partners, adding 177 annuities administrative tables 151 assessment template, administering 152 beneficiary, adding 154 business scenario 150 insurance product, adding 152 life or annuity coverage, defining 152 loan request, submitting 155 payment plan, setting up 156 policies, table of 149 quote, generating 153 transfer request, submitting 155 underwriting report, ordering 154 value history information, viewing 156 withdrawal or surrender request, submitting 156 applets Command Center applet, configuring example 27 Command Center applet, defining actions 25
Command Line applet, creating global commands for 29 applications associating company applications with a company 44 Applications Administration Guide, about task setup 19 approval stage, approving or declining 272 assessment template, administering 152 assessments company assessments, about creating 44 company assessments, performing 44 Assignment Manager about using to resolve coverage team problems 37 Assignment Statements, fine tuning about 227 Cache flag, about 229 Light Parser flag, about 228 attachments associating with call reports 71 auto policies auto insurance policy quote, providing 87 business scenarios 85 coverages, adding 87 discounts, adding 88 drivers, adding to policies 89 payment plan, setting up 89 underwriting information, adding 89 underwriting report, ordering 90 vehicles, adding to policies 89 vehicles, coverages, and premiums, viewing associated with policy 88 automating approval processing about 269 approval items and stages, defining 269 FINS Approval UI Service, invoking from a workflow 270
B
beneficiaries adding to group policies 174 beneficiary adding a beneficiary 154 beneficiary information recording for participant 82 billing
28 7
Index C
entering billing information group pensions 80 billing accounts about 189 billing account records, adding or modifying 190 business scenario 189 contact or company, associating billing account with 191 policy, associating a billing account with 191 service request, adding to a billing account 192 BRP See Business Rule Processor Business Rule Process creating and managing 212 defining 211 defining properties 215 errors 229, 230 exporting 214 FINS CAP Buscomp Data Loader Business Service 231 FINS CAP Buscomp Handler Business Service 236 helper business services, about using 231 importing 214 procedures, defining 219, 220 property types 215 revising existing 213 Business Rule Processor about 210 activating 214 debug messages, logging 244 invoking, about 242 business services about 200 approval items and stages, defining 269 approval stage, approving or declining 272 Assignment Statements, fine tuning 227 automating approval processing 269 Cache flag, about 229 calculation details, specifying 262 Calculation Manager 259, 265 calculation rule set. specifying 259 customer authentication 254 Customer Authentication Manager 254, 258 Customer Expectations Manager 265, 266, 268 Data Validation Manager, about 209 definition of 200 disclosure documents, activating workflows used to display 275 disclosure history, viewing associated with contacts 276
disclosure processing, automating display 273 Disclosure UI Service, about invoking from workflow 276 disclosure workflow processes (table) 274 disclosures, associating with a product 273 dynamic applet, creating with Dynamic UI business service example 280 dynamic applet, displaying in a workflow 281 Dynamic UI business service, about 279 Dynamic UI Service methods 283 embedded script for mortgage calculation example 262 existing disclosure, revising 273 FINS Application View Navigation Service 283, 284, 285, 286 FINS Application View Navigation Service, methods 283 FINS Approval UI Service, invoking from a workflow 270 FINS CAP Buscomp Data Loader Business Service 231 FINS CAP Buscomp Handler Business Service 236 FINS SmartScript Output Service methods 279 FINS Web Shopping Service methods 279 Free Format Converter 208 Light Parser flag, about 228 Record Group templates, creating 250 record templates, creating 246 requirement templates, creating 247 Requirements Manager 245 SmartScript, about invoking from a workflow 276 Template Definition view, adding views and applets 283 variables, specifying 260 VBC cache and Instance Manager 203 view template, about creating for dynamic applets 282
C
Cache flag, about 229 Calculation Expectations Manager 266 about 265 invoking 268 Calculation Manager about and examples 259 calculation details, specifying 262 calculation rule set, specifying 259 embedded script for mortgage calculation example 262
288
Index C
variables, specifying 260 Calculation Manager, invoking 265 call report email templates viewing or changing 69 call reports action items, notes, and attachments, associating with 71 business scenario 66 call report charts, viewing 67 call report distribution list, creating 71 call report email templates, viewing or changing 69 call report privacy flag, setting 72 call report, adding 69 Data Transfer Utility, about using 68 defined and about 65 emailing and printing 72 New Call Report Workflow, activating 68 categories creating contact information for 52 census data census information, adding 166 detailed census data, importing 165 segmented census data, importing 166 claim elements defined 109 claimant property information, recording adverse 109 claims 116 activity plan, creating 113 adjusters financial limits, administering 101 appraisals, adding 115 assigning claim to adjuster 110 bulk payments 131 business rules processor 142 business scenario 94 claim elements 113 claimant property information, recording adverse 109 Claims Center Locators, about setting up 97 Claims Center Locators, assigning longitude and latitude 98 Claims Center Locators, assigning new claim center 98 Claims Center Locators, entering claim center information 98 coverages, about 117 employee hierarchy, administering 102 events 109 events, creating 110 first notice of loss, creating 106 fraud information, managing 138 Insurance Services Office, integrating with 103
insured property information, recording 108 invoice records, creating 124 ISO database, checking a claim against 110 loss codes, administering 100 loss, associating an involved party with 108 Office of Foreign Assets Control, integrating with 105 payment record, generating 125 payment, issuing settlement 131 payment, tracking demands for 124 police and fire reports, tracking 116 policy validity, checking 106 recovery information, managing 132 reserve codes, administering 99 reserves, about 117 reserves, adjusting 122 reserves, creating 122 reserves, deleting 122 reserves, managing 119 reserves, opening 122 settlement payments, issuing 126 specialist unit, assigning claims to 114 workflow processes 99 workflows 145 ClearCache method, about 236 Collapse button Edit Layout view 21 summary view control, about 20 command center about and interface types 22 configuration and administration, about 22 Command Center Action form Command Center action, selecting responsibilities 27 Command Center business object, defining 23 process of configuring appearance and functions 22 Command Center applet configuring example 27 defining actions 25 Command Center business object, defining 23 Command Line applet, creating for global commands 29 companies about 31 aggregated activities viewing for a company 42 aggregated coverage team, viewing 43 aggregated list of contacts, viewing 43 aggregated opportunities, viewing 43 billing account, associating with 191 business scenario, sales representative tracks
28 9
Index D
company information 33 company applications, associating with a company 44 company assessments, about creating 44 company assessments, performing 44 company coverage team, adding a member 46 company coverage teams, about managing 45 company hierarchies, about 32 company hierarchies, default 39 company information, making unavailable to users, deleting 35 company or investor, adding 41 company summaries, viewing 46 competitor designation, changing 36 competitor, indicating a company is a competitor 36 coverage team members, about verifying 36 coverage team members, adding or deleting 37 coverage team members, search for a company without 37 custom-defined relationship type, about managing 38 custom-defined relationship type, adding 38 custom-defined relationship, creating 47 data aggregation, about generating company hierarchies for 39 default company hierarchy, generating 40 dynamic company hierarchy, creating 40 industry, adding 34 parent-subsidiary relationship, establishing 46 primary coverage team members, changing 37 service requests, adding associated with a company 45 territory, adding 35 values, about setting up 34 company hierarchies aggregated activities, viewing for a company 42 aggregated coverage team, viewing 43 aggregated list of contacts, viewing 43 aggregated opportunities, viewing 43 data aggregation, generating for 39 default company hierarchies 39 default company hierarchy, generating 40 dynamic company hierarchy, creating 40 company relationship hierarchies custom-defined relationship, creating 47 viewing 46 company summaries, viewing 46
competitor company, indicating as a competitor 36 designation, changing competitor designation 36 contacts adding 51 billing account, associating with 191 business scenario, sales representative adds a new contact 50 categories, creating for contact information 52 company, associating a contact with a company 52 contact relationship hierarchies, viewing 57 contact summary, viewing 56 customer assessments, about creating 55 customer assessments, creating 55 customer value stars. adjusting 56 defined 49 disclosure history, viewing associated with contacts 276 financial plans, creating 58 group pension plan contacts, recording 80 household, adding to a 61 households, associating with 61 managing contact information, about 51 notes, creating about contacts 53 referral, creating to a contact 55 referral, entering a referral received from a contact 54 relationship between contacts, defining 57 coverage teams company coverage team, adding a member 46 company coverage teams, about managing 45 customer assessments creating 55 creating, about 55 customer value stars, adjusting 56 Customer Authentication Manager 256, 258 about 254 customer authentication templates, creating 254 customer value stars, adjusting 56 customizable products reconfiguring in plan design 170 Customize Plan button, using 170
D
data aggregation company hierarchies, default 39 company hierarchies, generating for data
290
Index E
aggregation 39 default company hierarchy, generating 40 dynamic company hierarchy, creating 40 Data Transfer Utilities about using 68 Data Validation Manager, about 209 disclosure documents automating display, about 273 contacts, viewing disclosure history 276 Disclosure UI Service, invoking from workflow 276 disclosure workflow processes (table) 274 disclosures, associating with a product 273 existing disclosure, revising 273 workflows, activating used to display disclosure documents 275 Disclosure UI Service, invoking from a workflow 276 discounts auto policies, adding 88 distribution list about creating 71 documentation, attaching 116 Drivers, adding to auto policies 89 dynamic applets See Dynamic UI business service dynamic company hierarchy, creating 40 Dynamic UI business service about 279 dynamic applet, creating with Dynamic UI business service example 280 dynamic applet, displaying in a workflow 281 Dynamic UI Service methods 283 Template Definition view, adding views and applets 283 view template, about creating for dynamic applets 282
Process 230 Expand button Edit Layout view 21 summary view control, about 20
F
facility locator, adding facilities 98 financial plans, creating 58 FINS Application View Navigation Service about 283 administering 285 business service behaviors 283, 284 business service methods 283 example 285 upgrade note 286 FINS Approval UI Service business service step, configuring 272 start step, configuring 271 workflow, about invoking 270 FINS CAP Buscomp Data Loader Business Service about 231 ClearCache method, about 236 LoadData method example using field [n] 234 LoadData method example using Key and Value fields 235 LoadData method, about 232 FINS CAP Buscomp Handler Business Service about 236 GetFieldValue method, about 239 InsertRecord method, about 240 NextRecord method, about 241 query method, about 237 SetFieldValue method, about 240 FINS EAI Free Format Converter about 208 methods 208 user properties 208 FINS Group Policy Member benefits business component enrollment waiting period, about rules 169 FINS SmartScript Output Service methods 279 FINS Web Shopping Service methods 279 fire reports, tracking 116 Free Format Converter about 208 methods 208 user properties 208 funds group pension plan, viewing available within plan 81
E
Edit Layout view, using and buttons 21 email templates viewing or changing call report email templates 69 employees adding employee classes for group policies 168 enrolling members in group policies 173 enrollment waiting periods coverage, impacting on the start of 169 errors Business Rules Process, throwing errors within 229 recovering from errors within a Business Rules
29 1
Index G
G
geocode data, about 97 GetFieldValue method, about 239 global commands, creating for the Command Line applet 29 group pensions activity, creating associating with a plan 82 administering group pension plans, list of tasks 80 billing information, entering 80 business scenario 75 eligible plan members, adding 81 funding vehicles, defining for a group pension product 77 funds and investments available within plan, viewing 81 group pension plan contacts, recording 80 group pension plan, defining 78 group pension plans, process of defining 78 group pension product, defining 77 managing, about 75 new participants, enrolling in plan 82 note, creating associated with a plan 83 participant beneficiary information, recording 82 participant classes, defining for plan participants 79 plan rules, specifying 79 service request, creating associated with plan 81 tasks, samples performed when managing group pensions (diagram) 76 group policies activity plan templates, creating 163 activity plan templates, creating activities for the template 164 beneficiaries, adding 174 business scenario 161 census data, importing 165 census information, adding 166 customizable products, reconfiguring in plan design 170 defined 159 employee classes, adding for group policies 168 enrollment waiting periods, impact start of coverage 169 group insurance products, adding 162 group policy record, adding 164 members, adding eligible members 172 members, enrolling members 173 payment plans, setting up 174 plans, adding for group policies 168
policy screens, views common to all 160 proposal templates, creating 164 proposals, generating for group policies 171 rate bands, adding 163 segmented census data, importing 166 underwriting information, adding 171 underwriting information, viewing 172
H
Hide button Edit Layout view 21 summary view control, about 20 households business scenario 60 contact, adding to a household 61 contacts, associating with households 61 defined 59 household summary, viewing 62 privacy option, setting 61 relationship hierarchy, about viewing 62
I
importing census data 165 segmented census data 166 InsertRecord method, about 240 Instance Manager and VBC Cache about 203 caching VBC configuration 205 components 204 features and limitations 203 purging the VBC cache 206 stages of caching process 204 insurance policy, associating with billing account 191 Insurance Services Office 103 insurance, group policies about 159 activity plan templates, creating 163 activity plan templates, creating activities for the template 164 beneficiaries, adding 174 business scenario 161 census data, importing 165 census information, adding 166 customizable products, reconfiguring in plan design 170 employee classes, adding for group policies 168 enrollment waiting periods, impact start of coverage 169 group insurance products, adding 162 group policy record, adding 164
292
Index L
members, adding eligible members 172 members, enrolling 173 payment plans, setting up 174 plans, adding for group policies 168 policy screens, views common to all 160 proposal templates, creating 164 proposals, generating for group policies 171 rate bands, adding 163 segmented census data, importing 166 underwriting information, adding 171 underwriting information, viewing 172 insurance. See auto policies; life insurance; PUL policies integration integration messages 194 investments viewing available within group pension plan 81 investors about 31 investor, adding 41 involved parties loss, associating with 108 ISO ClaimSearch database 110
first notice, creating 106 involved party, associating with 108 loss report adverse claimant property 109 associating involved party 107 creating first notice 106 insured property 108 issuing settlement payment 131 police and fire reports 116 salvage and subrogation 132
M
members beneficiaries, adding to group policies 174 eligible members, adding 172 enrolling members 173 Mobile Web Client, about performing administrative functions on local db 19 Move down button, Edit Layout view 21 Move up button, Edit Layout view 21
N
National Association of Security Dealers (NASD) registration tracking 178 New Call Report Workflow activating 68 Data Transfer Utility, about using to modify 68 NextRecord method, about 241 notes call reports, associating with 71 creating about contacts 53 group pension plan, creating associated with plan 83
L
latitude and longitude assigning 98 life insurance administrative tables 151 assessment template, administering 152 beneficiary, adding 154 business scenario 150 insurance product, adding 152 life or annuity coverage, defining 152 loan request, submitting 155 payment plan, setting up 156 policies, table of 149 quote, generating 153 transfer request, submitting 155 underwriting report, ordering 154 value history information, viewing 156 withdrawal or surrender request, submitting 156 Light Parser flag, about 228 List of Values, configuring 20 LoadData method about and parameters 232 ClearCache method, about 236 example using field [n] 234 example using Key and Values fields 235 loan request, submitting 155 loss
O
Office of Foreign Assets Control 105
P
parent-subsidiary relationship establishing 46 partners agents, adding 178 business scenario, company signs new agent 176 business scenario, employee adds a new agency 176 defined 175 information, adding information associated with an agent 178
29 3
Index Q
new partners, adding 177 sharing data with partner, about enabling 175 payments auto policy payment plan, setting up 89 claims, tracking demands for 124 payment plan, setting up 156 payment plan, setting up for group policies 174 property policy, setting up payment plan 184 settlement, issuing 131 pensions See group pensions personal umbrella liability. See PUL policies plans customizable products, reconfiguring in plan design 170 group policies, adding for 168 payment plans, setting up for group plans 174 police reports, tracking 116 policy screens, common views 160 privacy flags setting the call report privacy flag 72 privacy option, setting 61 products customizable products, reconfiguring in plan design 170 property coverage adding property coverage 181 property coverage limit, adding 182 property information recording 108 recording adverse claimant 109 property insurance policy, providing a quote 182 property policies Accident Violation view tab, about 185 All SPP Items view tab, about 185 Boat Details view tab, about 185 Boat Operator view tab, about 185 business scenario 179 payment plan, setting up 184 property coverage limit, adding 182 property coverage, adding 181 property insurance policy quote, providing a 182 property types, adding 181 property underwriting information, querying for 183 Replacement Cost Summary view tab, about 185 Replacement Cost view tab, about 184 scheduled personal property, adding 183
underwriting information, adding 182 underwriting report, ordering 183 proposal templates creating for group policies 164 proposals group policies, about generating for 159 group policies. generating for 171 PUL policies about 187 business scenario 187 PUL insurance policy quote, generating 188 Rate button, about adding 188
Q
querying for property underwriting information 183 quotes auto insurance policy quote, providing 87 life insurance or annuity, generating quote 153 property insurance policy, providing a quote 182 PUL insurance policy quote, generating 188
R
rate bands plans, adding for group policies 168 rate band, adding* 163 Rate button, about adding 188 rate policies, adding Rate button 188 Record Group templates creating 250 Requirements Manager, example of using for Record Group templates 252 record templates, creating 246 referral information referral, creating to a contact 55 referral, entering a referral received from a contact 54 relationship hierarchy contact, about viewing 57 contacts, defining a relationship between contacts 57 household relationship hierarchy, about viewing 62 relationship types, custom defined managing, about 38 managing, adding 38 requirement templates, creating 247 Requirements Manager about and scenarios 245 example of using for Record Group templates 252
294
Index S
invoking Requirements Manager 250 Record Group templates, creating 250 record templates, creating 246 requirement templates, creating 247 roll-up views aggregated activities, viewing for a company 42 aggregated coverage team, viewing 43 aggregated opportunities, viewing 43
S
salvage and subrogation, recording details 132 scheduled personal property, adding 183 service requests adding associated with company 45 billing account, adding to 192 group pension plan, creating associating with 81 SetFieldValue method, about 240 settlement, issuing payment 131 Show button, Edit Layout view 21 Siebel Calculation Expectations Manager, about 265 Siebel Calculation Manager See Calculation Manager SmartScript FINS SmartScript Output Service methods 279 FINS Web Shopping Service methods 279 integrating with workflow example 277 workflow, about invoking from 276 summary information viewing a household summary 62 summary views configuring, about 20 layout, editing 21 surrender request, submitting 156
activity plan templates, creating for group policies 163 call report email templates, viewing or changing 69 customer authentication templates, creating 254 Dynamic UI Service methods 283 proposal templates, creating for group policies 164 Record Group templates, creating 250 record templates, creating 246 requirement templates, creating 247 Template Definition view, adding views and applets 283 view template, about creating for dynamic applets 282 transfer request, submitting 155
U
umbrella policies. See PUL policies underwriting auto policies report, ordering 90 auto policy underwriting information, adding 89 information, adding 182 property underwriting information, querying for 183 report, ordering (life and annuities) 154 report, ordering (property policies) 183 underwriting information adding 171 viewing 172
V
value history information, viewing 156 VBC Cache and Instance Manager about 203 caching VBC configuration 205 components 204 features and limitations 203 purging the VBC cache 206 stages of caching process 204 Vehicles, adding to auto policies 89 view template dynamic applets, about creating for 282 Dynamic UI Service methods 283 Template Definition view, adding views and applets 283
T
team members coverage team members, about verifying 36 coverage team members, adding or deleting 37 coverage team members, searching for a company without 37 primary coverage team members, changing 37 Template Definition view, adding views and applets 283 templates activity plan templates, creating activities for group policies 164
W
wealth management industry about access to households aggregated holdings 60
29 5
Index W
withdrawal request, submitting 156 workflows disclosure documents, activating (table) 275 Disclosure UI Service, invoking from a workflow 276 disclosure workflow processes (table) 274 dynamic applets, displaying in a
workflow 281 FINS Approval UI Service, invoking from a workflow 270 SmartScript, about invoking from a workflow 276 SmartScript, integrating with workflow example 277
296

Insure SIA

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Insure SIA

Uploaded by

Copyright:

Available Formats

Siebel Insurance Guide

Version 8.1, Rev A June 2012

Siebel Insurance Guide 1

Whats New in This Release Overview of Siebel Finance

About Siebel Insurance

Siebel Insurance Functionality and Modules

Getting Started with Siebel Finance

Adding Products and Product Lines

Command Center Configuration and Administration

Process of Configuring the Command Center Action Form

About Managing Companies About Company Hierarchies

Scenario for Managing Company Information Process of Managing Companies

Setting Up Values for Companies Deleting Company Information

Siebel Insurance Guide Version 8.1, Rev A

Managing Competitor Information Verifying Coverage Team Members

Viewing Company Hierarchies in Roll-Up Views (End User) 44 45 45 46

Viewing Company Relationship Hierarchies (End User)

About Managing Contacts

Scenario for Adding a New Contact

Viewing Contact Relationship Hierarchies (End User)

About Managing Households

Scenario for Managing Households Process of Managing Households Adding Households

Siebel Insurance Guide Version 8.1, Rev A

Using the Household Relationship Hierarchy

Managing Call Reports

About Managing Call Reports

Scenario for Managing Call Reports Process of Managing Call Reports

Viewing Call Report Charts

Managing Group Pensions

About Managing Group Pensions Group Pension Sample Tasks

Defining Group Pension Products Defining Group Pension Plans 78

Administering Group Pension Plans (End User)

Managing Auto Policies

About Managing Auto Policies

Scenario for Managing Auto Policies

Siebel Insurance Guide Version 8.1, Rev A

Process of Managing Auto Policies

Chapter 10: Managing Claims

Setting up Siebel Insurance eService Claims Center Locators 99

Administering Adjusters Financial Limits Administering the Employee Hierarchy

Example of Setting up the Employee Hierarchy

Integrating with the Insurance Services Office (ISO)

Creating First Notices of Loss (End User)

106 107 108

Checking a Claim Against the ISO Database (End User)

Siebel Insurance Guide Version 8.1, Rev A

Chapter 11: Managing Life and Annuity Policies

Process of Managing Life and Annuity Policies

Chapter 12: Managing Group Policies

Process of Managing Group Policies

173 174 174

Setting Up Payment Plans for Group Policies

Chapter 13: Managing Partners and Agencies

Chapter 14: Managing Property Policies

Process of Managing Property Policies

Adding Property Types Providing Quotes 182

Siebel Insurance Guide Version 8.1, Rev A

Chapter 15: Managing PUL Policies

Providing PUL Policy Quotes

Chapter 16: Managing Billing Accounts

Process of Managing Billing Accounts Creating Billing Account Records 190

Associating Billing Accounts with Other Records

Chapter 17: Siebel Integration Messages