User Requirement Specifications for “Product Name”

Document Control:
DOCUMENT IDENTIFICATION INFORMATION

Document No <Versioning of Document. (e.g. Version 1.0,Version 1.1,Version 1.2 )>

Document Name <Document Name should be short and consist of the main subject of
the document>
<The Product Name must be present>
Date Created <The date when document is created>
<This will be updated as per versioning>
<The date created should be same as request date of stake holders>
Web Prompt ID/Defect <For GC System: Web prompt ID will be mentioned>
management tool ID <For Non-GC Systems: DMT ID will be mentioned>
Created By <Name of BA (Author of BRD)>

Revision Control Information

Revision History
Version Release Date Change Description Requested By
1.0 <DD/MM/YYYY> <Base BRD> <User name requested for the
change>
1.1 <DD/MM/YYYY> <Major Change <User name requested for the
Description><MOM> change>
1.2 <DD/MM/YYYY> <Major Change <User name requested for the
description><MOM> change>

Document Review and Approval

Name Position/Role Signature Date

<This box should

only contain the <Date of sign
owner of off>
department>
<Senior Vice President/Process Delivery <DD/MM/YY
< JN Prasad>
and Quality > YY>

<System Name> Confidential Page 1 of 15

 User Requirement Specifications for “Product Name”

Table of Contents
1. Introduction............................................................................................................5
1.1. Background............................................................................................................5
1.2. Objectives...............................................................................................................5
1.3. Key definition.........................................................................................................5
1.4. Target Audience.....................................................................................................5
1.4.1. Users...............................................................................................................5
1.4.2. Beneficiaries...................................................................................................5
1.4.3. Other impacted parties...................................................................................5
1.5. Assumptions...........................................................................................................5
1.6. Dependencies.........................................................................................................5
1.7. Constraints..............................................................................................................6
2. Process Overview...................................................................................................6
2.1. Current Process......................................................................................................6
2.1.1. Process Diagram/ Description........................................................................6
2.1.1.1. New Policy /endorsement/Renewal...............................................................6
2.1.1.2. Limitations/ Challenges.................................................................................7
2.2. To Be Process Map................................................................................................7
3. Functional Requirements.......................................................................................8
3.1. Product Details.......................................................................................................8
3.1.1. Product Name.................................................................................................8
3.1.2. Product Code..................................................................................................8
<System generated>......................................................................................................8
3.1.3. UIN Number...................................................................................................8
3.1.4. List of Sub Products / Variants......................................................................8
3.2. Policy Term – Period.............................................................................................8
3.3. Policy Number series and Logic............................................................................8
3.4. Cover Group Items and their Categories................................................................8
3.5. Policy Sum Insured Determination........................................................................8
3.6. Major, Minor, Class, Peril, Sections, Risks, Covers, Tariff/Non-Tariff................9
3.7. Loading and Discounts...........................................................................................9
3.8. Clauses, Conditions, Warranties, Exclusions.........................................................9
3.9. Deductibles.............................................................................................................9
3.10. Plan Details/Risk Grid Details/Cover Grid Details/ Instalment Details............9
3.11. Approval Process...............................................................................................9
3.12. Business Rules and Impact on BRE Interface....................................................9
3.13. Underwriting and Rating....................................................................................9
3.13.1. UW Rules.......................................................................................................9
3.13.2. Rating Structure.............................................................................................9
3.14. Premium Computation Logic.............................................................................9
3.15. UW Master.........................................................................................................9
3.16. Quotation..........................................................................................................10
3.16.1. Quick Quote.................................................................................................10
3.16.2. Detailed Quote.............................................................................................10
3.17. Endorsements...................................................................................................10
3.17.1. Financial.......................................................................................................10
3.17.2. Non financial................................................................................................10

<System Name> Confidential Page 2 of 15

 User Requirement Specifications for “Product Name”

3.17.3. Cancellation and Refund..............................................................................10

3.18. Reinstatement...................................................................................................10
3.19. Common Business Rules / validations applicable for all Products..................10
3.20. Escalation Matrix /Workflow...........................................................................10
3.21. Master Certificate and / or Individual..............................................................10
3.22. Software Interface / EDI Requirements...........................................................10
3.23. Quality Check...................................................................................................11
3.23.1. QC Process and Impact on IBM BPM Interface..........................................11
3.23.2. QC Points.....................................................................................................11
3.23.3. QA Audit Report..........................................................................................11
3.24. Accounts...........................................................................................................11
3.24.1. E-Franking....................................................................................................11
3.24.2. Shortfall........................................................................................................11
3.24.3. Reinsurance and RI Inward..........................................................................11
3.24.4. Changes in GL and Miscellaneous accounting............................................11
3.24.5. Changes in SAP............................................................................................11
3.24.6. Impact on SAP upload.................................................................................11
3.24.6.1. EOD..........................................................................................................11
3.24.6.2. EOM.........................................................................................................11
3.24.7. GST..............................................................................................................12
3.24.8. Commission..................................................................................................12
3.24.9. TDS..............................................................................................................12
3.24.10. Co- Insurance...........................................................................................12
3.24.11. Cheque Bounce........................................................................................12
3.24.12. Profit centre and cost centre mapping......................................................12
3.25. Claims..............................................................................................................13
3.25.1. Process Flow................................................................................................13
3.25.2. Claim registration.........................................................................................13
3.25.3. Claim Details................................................................................................13
3.25.4. Adjustor Appointment..................................................................................13
3.25.5. Adjustor Report submission.........................................................................13
3.25.6. Assessment Sheet.........................................................................................13
3.25.7. Process & Settlement (Product Specific).....................................................13
3.25.8. Litigation Registration.................................................................................13
3.25.9. Claim Reopen...............................................................................................13
3.25.10. Recovery Details......................................................................................13
3.25.11. Claim Approval Details............................................................................13
3.25.12. Claims Common functionalities...............................................................13
3.25.13. Impact on Claims interfaces including I-CAN.........................................13
3.26. Policy Renewal Process...................................................................................13
3.26.1. Logic for Policy Renewal.............................................................................13
3.26.2. Logic for Renewal notice generation...........................................................13
3.26.3. Renewal data search conditions...................................................................13
3.26.4. Renewal extracts file structure.....................................................................13
3.27. Generic Functionality.......................................................................................14
3.27.1. Impact on Customer master.........................................................................14
3.27.2. Impact on Producer/Dealer/DEU Master.....................................................14
3.27.3. Impact on Pace.............................................................................................14
3.27.4. Impact on POS Product Master....................................................................14
3.27.5. Impact on Risk Location Master..................................................................14

<System Name> Confidential Page 3 of 15

 User Requirement Specifications for “Product Name”

3.27.6. Impact on E-Mandate Master.......................................................................14

3.27.7. Impact on search Module.............................................................................14
3.27.8. Impact on Receipting...................................................................................14
4. Communication....................................................................................................14
4.1.1. Email............................................................................................................14
4.1.2. SMS..............................................................................................................14
4.1.3. Impact on CRM and Interfaces....................................................................14
5. Roles and Rights..................................................................................................14
6. Output Documents /CCM....................................................................................14
7. Reporting MIS......................................................................................................15
8. Non-Functional Requirements.............................................................................15
8.1.1. Volume & Performance Requirements........................................................15
8.1.2. Security Requirements.................................................................................15
8.1.3. Compliance Requirements...........................................................................15
8.1.4. Hardware......................................................................................................15
9. Annexure..............................................................................................................15
10. Open Items...........................................................................................................15

<System Name> Confidential Page 4 of 15

 User Requirement Specifications for “Product Name”

1. Introduction
<This should be the executive summary of the document>

1.1. Background
<Provide a short description of the application / software being specified and
its purpose, including relevant benefits, objectives, and goals. Relate the
software to corporate goals or business strategies. If a separate vision and
scope document is available, refer to it rather than duplicating its contents
here.>

1.2. Objectives
<Why this document is being created and why are the changes being done>

1.3. Key definition

<Abbreviation/glossary of terminology used in entire BRD>
Key word Definition

1.4. Target Audience

1.4.1.Users
 Product Tower
 Operations

1.4.2.Beneficiaries
 Product Tower
 Operations
 Claims

1.4.3.Other impacted parties

 Customer Services

1.5. Assumptions
<List any assumed factors (as opposed to known facts) that could affect the
requirements. The project could be affected if these assumptions are incorrect,
are not shared, or change>

1.6. Dependencies
<Identify any dependencies that can affect the requirements specified in this
BRD, such as software components that you intend to reuse from another
application.>

<System Name> Confidential Page 5 of 15

 User Requirement Specifications for “Product Name”

1.7. Constraints
<Describe the constraints that can affect the requirements specified in this
BRD. These could constraints around the development or operating
environment>

2. Process Overview
2.1. Current Process
<Current process flow refers to the flow of work through the existing business
solution environment. The business processes or functions associated with the
current process flow are documented.>

2.1.1. Process Diagram/ Description

2.1.1.1. New Policy /endorsement/Renewal

<Process diagram and description of diagram>
<Sample format below>

<System Name> Confidential Page 6 of 15

 User Requirement Specifications for “Product Name”

2.1.1.2. Limitations/ Challenges

2.2. To Be Process Map

<To be process map refers to the flow of work through the business solution
environment as envisioned after the proposed software product is in
operation.>

2.2.1 Process Flow

2.2.1.1 New Policy/Endorsement/renewal
<Process diagram and description of diagram>
<Sample diagram below>

2.2.2 Process description

Sr Process Owner Description TAT

No
1 Login to Vakrangee Franchisee logs into Vakrangee Portal with his unique id and Password Day
Vakrangee Kendra and follows authentication process: 1
Portal Franchisee
 Selects ‘Insurance services’ and opts for ‘Tata AIG General
Insurance Co.’
 The above process will direct the application to TAGIC
portal

<System Name> Confidential Page 7 of 15

 User Requirement Specifications for “Product Name”

2 Selection of Franchisee After selecting the company name on, the Franchisee needs to select Day
Product the product which is offered to customer (Motor/ IPA) on TAGIC 1
portal

3 Franchisee enters customers personal details like name, contact no, Day
Creation of address etc and clicks on ‘Create Customer ID and proceed’ option. 1
Franchisee
Customer Customer ID gets generated

3. Functional Requirements
<Specify the sub functions or Use Cases necessary to comprehensively define
the fundamental actions that must take place within the software to accept
and process the inputs and to process and generate the outputs>

3.1. Product Details

3.1.1. Product Name

3.1.2. Product Code

<System generated>

3.1.3. UIN Number

3.1.4. List of Sub Products / Variants

<List down all the sub product and variant with sub product code and variant
code>

3.2. Policy Term – Period

<Annual
Long term
Risk Details>

3.3. Policy Number series and Logic

<Sample example below>

< Product code (4) +  Running number (10) +  Renewal counter (2) +
Endorsement counter (2) + Policy Plan code (2)>

3.4. Cover Group Items and their Categories

3.5. Policy Sum Insured Determination

<Sum insured calculation logic for sub product or product>

<System Name> Confidential Page 8 of 15

 User Requirement Specifications for “Product Name”

3.6. Major, Minor, Class, Peril, Sections, Risks, Covers, Tariff/Non-Tariff

3.7. Loading and Discounts

< Loading  is an additional cost built into the  insurance  policy to cover losses
which are higher than anticipated for the company arising from insuring a
person who is prone to a form of risk>

<E.G><Producer level discount><No claim bonus> < Cumulative Discounts on

Premiums>

3.8. Clauses, Conditions, Warranties, Exclusions

3.9. Deductibles

3.10. Plan Details/Risk Grid Details/Cover Grid Details/ Instalment

Details

3.11. Approval Process

3.12. Business Rules and Impact on BRE Interface

3.13. Underwriting and Rating

3.13.1. UW Rules
Refer

Decline

Accept Rules

3.13.2. Rating Structure

3.14. Premium Computation Logic

3.15. UW Master
<Product Specific Underwriting Masters - Front-end masters list along with
field specifications>

<System Name> Confidential Page 9 of 15

 User Requirement Specifications for “Product Name”

3.16. Quotation

3.16.1. Quick Quote

3.16.2. Detailed Quote

<Refer Standard SCREEN NAMES from the Library of UI>
<Quote level field specifications for Quick Quote and Detail Quote>

Field detail
Format.xlsx

3.17. Endorsements

3.17.1. Financial
<Type of financial endorsement with Logic>

3.17.2. Non financial

<Type of non-financial with rules>

3.17.3. Cancellation and Refund

<Cancellation and retention logic >
1. Short Rate
2. Pro rata
3. Nil refund
4. Full refund

<Refund and impact on Refund Automation System (RAS) >

3.18. Reinstatement

3.19. Common Business Rules / validations applicable for all Products

3.20. Escalation Matrix /Workflow

3.21. Master Certificate and / or Individual

<Master/Open Policy level input field specification>
<Certificate level Input field specifications>

3.22. Software Interface / EDI Requirements

 List of all interfaces Required for the Product

<System Name> Confidential Page 10 of 15

 User Requirement Specifications for “Product Name”

 Interfaces file format for all above applicable interfaces

 Additional validations required for interfaces

 Validations which are not applicable for interfaces

 Online/Offline upload data format

EDI_Format_Sample
1.1

3.23. Quality Check

3.23.1. QC Process and Impact on IBM BPM Interface

3.23.2. QC Points

3.23.3. QA Audit Report

3.24. Accounts

3.24.1. E-Franking

3.24.2. Shortfall

3.24.3. Reinsurance and RI Inward

3.24.4. Changes in GL and Miscellaneous accounting

3.24.5. Changes in SAP

3.24.6. Impact on SAP upload

3.24.6.1. EOD
 EOD SAP Extract
 Advance premium Batch

3.24.6.2. EOM
 UEPR
 OSLR

<System Name> Confidential Page 11 of 15

 User Requirement Specifications for “Product Name”

3.24.7. GST
<Impact on certificate, Master Policy and Leaser>

3.24.8. Commission

3.24.9. TDS

3.24.10. Co- Insurance

3.24.11. Cheque Bounce

3.24.12. Profit centre and cost centre mapping

Mapping should be added in URS for below parameters:
a. Product code: 4 digit GC product code
b. Variant: If variant is there in product then provide display product code
c. UIN: If variant wise different UIN, provide both UIN for product
d. MMCP: For all applicable covers
e. Profit center: This will vary as per covers based on section, for Motor
products OD and TP section and for non motor products terrorism and non
terrorism product.
Sample attached

Sample profit centre

mapping.xlsx

<System Name> Confidential Page 12 of 15

 User Requirement Specifications for “Product Name”

3.25. Claims

3.25.1. Process Flow

3.25.2. Claim registration

3.25.3. Claim Details

3.25.4. Adjustor Appointment

3.25.5. Adjustor Report submission

3.25.6. Assessment Sheet

3.25.7. Process & Settlement (Product Specific)

3.25.8. Litigation Registration

3.25.9. Claim Reopen

3.25.10. Recovery Details

3.25.11. Claim Approval Details

3.25.12. Claims Common functionalities

3.25.13. Impact on Claims interfaces including I-CAN

3.26. Policy Renewal Process

3.26.1. Logic for Policy Renewal

3.26.2. Logic for Renewal notice generation

3.26.3. Renewal data search conditions

3.26.4. Renewal extracts file structure

<System Name> Confidential Page 13 of 15

 User Requirement Specifications for “Product Name”

3.27. Generic Functionality

3.27.1. Impact on Customer master

3.27.2. Impact on Producer/Dealer/DEU Master

3.27.3. Impact on Pace

3.27.4. Impact on POS Product Master

3.27.5. Impact on Risk Location Master

3.27.6. Impact on E-Mandate Master

3.27.7. Impact on search Module

3.27.8. Impact on Receipting

4. Communication
4.1.1. Email

4.1.2. SMS

4.1.3. Impact on CRM and Interfaces

5. Roles and Rights

Roles and Rights

V1.xls

6. Output Documents /CCM

< Worksheet, Proposal Form, Policy Schedule, Endorsement
Schedule, Policy Cancellation Letter, Renewal Notice>
<All applicable XML files for output documents>
< Attach templates of each product>
<Highlight the changes in attachment for reference>
<Impact on omnidocs>

<System Name> Confidential Page 14 of 15

 User Requirement Specifications for “Product Name”

7. Reporting MIS
<Impact on all existing reports, data hub, data lake to be confirmed with
IT/MIS Team>

8. Non-Functional Requirements
8.1.1. Volume & Performance Requirements

8.1.2. Security Requirements

8.1.3. Compliance Requirements

8.1.4. Hardware

9. Annexure

Serial
No Annexure Content
1. General Underwriting Annexure
2. Underwriting Annexure
3 QC Check Points
4 Output Documents

10.Open Items
<This is a dynamic list of the open requirements issues/items that
remain to be resolved, including TBDs, pending decisions, information
that is needed, conflicts awaiting resolution, and the like.>

<System Name> Confidential Page 15 of 15