Traditional Life Policy Addition Collaboration Overview

IBM(R) WebSphere(R) Business Integration Collaboration for Traditional Life Policy Addition is utilized for a typical life insurance scenario where a client wants to request a new life insurance policy. The end user provides the details for the request. When the request is received, this collaboration allows the financial institution to quickly process and respond to the user request for a new policy.

Business rules

The following business rules apply to the Traditional Life Policy Addition business process:

System assumptions

Like the other WebSphere Business Integration for Insurance collaboration templates, Traditional Life Policy Addition utilizes the IBM WebSphere Interchange Server. WebSphere Business Integration connectors are used to connect to other applications that participate in the collaboration.

The following applications are also assumed to participate in the Traditional Life Policy Addition collaboration:

This collaboration object uses a Pub/Sub engine to post responses.

The system features that are expected to execute the collaboration object, including IBM WebSphere Business Integration connectors, are shown in the following diagram:

 AddTraditionalLifePolicy system assumptions diagram

Use Case

This process demonstrates a typical life insurance scenario where a client wants to request the creation of a new life policy. The process begins when the client uses a browser to provide the data required to request a new life policy, and is completed when verification of the policy has been published to all interested systems.

Actors

The Traditional Life Policy Addition use case has a single actor, the requester of a new life policy. The client does not have an existing life policy with the insurance provider but wants to request that one be created.

Use case flow

The following tables describe the main course and the alternate courses that may be followed in the Traditional Life Policy Addition use case:

Main course
# Activity by the actor System activity Reference
M1 Client submits a request  to add a traditional life policy. Receives client information  
M2   Retrieves client information 1
M3   Submits life policy application information 2
M4   Retrieves policy information 3
M5   Publishes a response message to client with policy information or notice of request failure  
Alternate course
# Activity by the actor System activity Reference
1   Submitted client information does not match information on record M5
2   Submitted life policy application information is not able to be processed M5
3   Submitted policy information does not match information on record M5

The following activity diagram illustrates the Traditional Life Policy Addition use case:

Activity diagram for AddTraditionalLifePolicy use case

Business examples

The following business examples show situations where the Traditional Life Policy Addition use case is realized.

New life policy requested with accurate client data

  1. A client wishes to open a new life policy.
  2. The client submits the request for a new life policy, using a Web browser to enter their current user and policy application information.
  3. The client information is retrieved by the insurance provider's system.
  4. The policy application information is submitted along with the relevant client data.
  5. A response message is quickly returned to the client's system, providing the information for the policy that was created.

New life policy requested with incorrect client data

  1. A client wishes to open a new life policy.
  2. The client submits the request for a new life policy, using a Web browser to inadvertently enter incorrect user and policy application information.
  3. The client information cannot be retrieved by the insurance provider's system.
  4. A response message is quickly returned to the client's system, indicating that the client data cannot be found in the insurance provider's records.
  5. The client contacts the insurance provider and the reason for the non-match is quickly determined.

Copyright IBM Corp. 2002, 2003