BUSINESS REQUIREMENT DOCUMENT-2019

AGENT PORTAL MANUAL

AGENT PORTAL MANUA VERSION 1.1 DATE PAGE NO:

BUSINESS REQUIREMENT DOCUMENT-2019

AGENT PORTAL MANUAL

A P M_ VERSION_ 1.1

BAMMU.K

Document type :

 draft

 to be validated

 validated

AGENT PORTAL MANUAL VERSION 1.1 DATE PAGE NO:

BUSINESS REQUIREMENT DOCUMENT-2019

DOCUMENT REFERENCE:

448015630.doc

 Document title : AGENT PORTAL MANUAL

 Subject
 Author
 Comments

PURPOSE OF THE DOCUMENT:

<The purpose of this document is to describe the application supplied to the user>

This document is the property of the <Org.agent portal manual>.It

may not be reproduced or communicated without the author's prior agreement.

1.DOCUMENT REVISION:

DOCUMENT VERSION DATE DRAFTER DESCRIPTION

TYPE NO.

AGENT PORTAL MANUAL VERSION 1.1 DATE PAGE NO:

BUSINESS REQUIREMENT DOCUMENT-2019
BUSINESS 1.0 17/9/2017 COEPD TEAM DRAFT VERSION
REQUIRED
DOCUMENT
BUSINESS 1.1 18/11/2019 BAMMU VALIDATION
REQUIRED VERSION
DOCUMENT
BUSINESS 1.2 20/11/2019 BAMMU CHANGE
REQUIRED REQUESTS
DOCUMENT

2.APPROVALS

ROLE NAME TITLE SIGNATURE DATE

PROJECT Mr.PAVAN Mr. 17/9/2017
SPONSOR
PROJECT Mr.PAVAN Mr. 18/11/2019
MANAGER
SYSTEM Mr.PAVAN Mr. 18/11/2019
ARCHITECT
DEVELOPMEN Mr.PAVAN Mr. 18/11/2019
T LEAD
QUALITY LEAD Mr.PAVAN Mr. 20/11/2019
CONTENT Mr.PAVAN Mr. 20/11/2019
LEAD
USER Mr.PAVAN Mr. 20/11/2019
EXPERIENCE
LEAD

3. TO BE APPROVED BY:

NAME OF THE USER,DEPARTMENT DATE

MR.PAVAN KUMAR 20/11/2019

PREPARED BY DATE

K.BAMMU 18/11/2019

AGENT PORTAL MANUAL VERSION 1.1 DATE PAGE NO:

BUSINESS REQUIREMENT DOCUMENT-2019

Name of user, department Date page no

Contents

1.Introduction ----------------------------------------------------------------------
1.1. Business Goals------------------------------------------------------------------

1.2. Business Objectives -----------------------------------------------------------

1.3. Business Rules ------------------------------------------------------------------

1.4. Background ----------------------------------------------------------------------

1.5. Project Objective ---------------------------------------------------------------

1..6. Project Scope --------------------------------------------------------------------

1.6.1. In Scope Functionality ------------------------------------------------------

1.6.2. Out Scope Functionality ----------------------------------------------------

2. RACI Chart for This Document --------------------------------------------------

Codes Used in RACI Chart -------------------------------------------------------------

3. Actors -----------------------------------------------------------------------------------
3.1. Workers -----------------------------------------------------------------------------

3.2. Business Actors ------------------------------------------------------------------------

3.3. Other Systems ----------------------------------------------------------------------

4. Assumptions ----------------------------------------------------------------------------

5. Constraints ---------------------------------------------------------------------------

6. Risks ----------------------------------------------------------------------------------------

7.Business process overview--------------------------------------------------------

7.1. Legacy System (AS-IS) ----------------------------------------------------------

AGENT PORTAL MANUAL VERSION 1.1 DATE PAGE NO:

BUSINESS REQUIREMENT DOCUMENT-2019

7.2. Proposed Recommendations (TO-BE)---------------------------------------

8. Use case diagram (Business Level) ---------------------------------------------

9. Business Requirements -------------------------------------------------------------

10. Functional Requirements --------------------------------------------------------

11. Nonfunctional Requirements --------------------------------------------------

11.1. Performance Requirements --------------------------------------------------

11.2. Stress Requirements ------------------------------------------------------------

11.3. Response-Time Requirements --------------------------------------------------

11.4. Throughput Requirements -------------------------------------------------

11.5. Usability Requirements -------------------------------------------------------

11.6. Security Requirements ---------------------------------------------------------

11.7. Volume and Storage Requirements ----------------------------------------

12. Configuration Requirements ---------------------------------------------------

13. Compatibility Requirements -------------------------------------------------------

14. Reliability Requirements -----------------------------------------------------------

15. Backup/Recovery Requirements ------------------------------------------------

Back up requirement for the system is once every week on Saturday 12

AM – 3AM ----------------------------------------------------------------------------------

16. Training Requirements -------------------------------------------------------------

AGENT PORTAL MANUAL VERSION 1.1 DATE PAGE NO:

BUSINESS REQUIREMENT DOCUMENT-2019

INTRODUCTION:

1.1 BUSINESS RULES:

AGENT PORTAL

3. RACI CHART FOR THIS DOCUMENT:

The RACI chart identifies the persons who need to be contacted
whenever changes are made to this document. RACI stands for
responsible, accountable, consulted, and informed. These are the
main codes that appear in a RACI chart, used here to describe the

AGENT PORTAL MANUAL VERSION 1.1 DATE PAGE NO:

BUSINESS REQUIREMENT DOCUMENT-2019

roles played by team members and stakeholders in the production of

the Business Requirement Document (BRD). They are adapted from
charts used to assign roles and responsibilities during a project.

The following describes the full list of codes used in the table

3.1 CODES USED IN RACI CHART :

* Authorize Has ultimate signing authority for any changes to the
document.

R - Responsible Responsible for creating this document.

A - Accountable for accuracy of this document (for example, the

proje
ct manager )

C - Consulted Provides input (such as an interviewee)

.
I –Informed /Must Be Informed

3.2 RACI CHART:

AGENT PORTAL MANUAL VERSION 1.1 DATE PAGE NO:

BUSINESS REQUIREMENT DOCUMENT-2019

4.4.1 INTRODUCTION:

IN THE WEBSITE OF STAR HEALTH PRODUCTS

,WHERE VARIOUS FEATURES LIKE HEALTH INSURANCE,ACCIDENTAL
CARE,OVERSEAS TRAVEL,CLAIM CORNER AND TESTIMONIES,A NEW
PORTAL HAS BEEN ACTIVATED FOR AGENTS TO REGISTER AND LOG-
IN.

HERE,THE AGENT CAN GO THROUGH VARIOUS

DETAILS AND GET A REPORT GENERATED.IN THE BUSINESS
DETAILS A (PREMIUM REPORT,PRODUCT WISE,OFFICE WISE,FRESH
AND RENEWAL) CAN BE GEENERATED BY GIVING DATE FROM AND
DATE TO.

IN THE RENEWALS SESSION (POLICIES

RENEWAL,AND CANCELLATION RENEWAL) REPORT TYPE AS
RENEWED /NOT RENEWED CAN BE GENERATED.

IN COMMISSION SECTION COMMISION

DETAILS AND COMMISSION RECOVERY DETAILS PDF CAN BE
GENERATED

SIMILARLY,IN CLAIMS SESSION (INITIATE

CLAIMS,CLAIMS PAID STATEMENT,AND CLAIMS OUTSTANDING)
STATEMENTS OF PAID ,CLOSED AND REJECTED CLAIMS CAN BE
GENERATED.

THE AGENT CAN VIEW ALL DETAILS

REGARDING THESE STATEMENTS AND GET A DETAIL STRUCTURE OF
THE POLICIES AND STATMENTS,AND THERE BY GETTING A PRINTED
DOCUMENT .THIS HELPS THE AGENT TO KNOW AND GET A BETTER
UNDERSTANDING OF HIS ACTIONS AND ACTIVITIES.

AGENT PORTAL MANUAL VERSION 1.1 DATE PAGE NO:

BUSINESS REQUIREMENT DOCUMENT-2019

4.2 BUSINESS GOAL :

TO ACHIEVE THE STAR HEALTH
PRODUCTS ORGANIZATION IN PROVIDING ONLINE HELP TO THE
AGENTS BY GIVING THE DETAILS AND GENERATING THE REPORTS BY
IMPLEMENTING THE NEW TECHNOLOGY SOLUTION TO EASYLY TRACK
THE STATUS FOR THE EASE OF THE AGENT AND ORGANIZATION

Need:
TO MINIMISE THE WORK OF THE STAFF
AND PROVIDE A DIRECT ACCESS TO THE AGENTS TO KNOW THEIR
STATUS AND DETAILS THERE BY INCREASE THE CUSTOMER BASE BY
IMPROVING THE COMMUNICATION SYSTEMS FOR A BETTER
UNDERSTANDING AND ACCESS TO THE REPORTS .

4.3 BUSINESS OBJECTIVE:

TO PROVIDE AN IT SOLUTION FOR STAR HEALTH
PRODUCTS IN THE AGENT PORTAL BY IMPROVING GOOD INTRACTIONS AND
COMMUNICATION FACILITIES BETWEEN CUSTOMER,AGENT AND
ADMINISTRATOR BY IMPLEMENTING THE FOLLOWING:

1. TO MINIMISE PROCESS TIME

2. GOOD COMMUNICATION WITH THE CUSTOMER VIA. AGENT DATABASE
3. CREATE AND MAINTAIN CUSTOMER DATABASE
4. ONLINE QUERIES
5. ONLINE STATUS AND DETAILS REGARDING BUSINESS
6. POLICIES RENEWAL AND CANCELLATION
7. COMMISSSIION AND RECOVERY DETAILS
8. CLAIMS INTIMATED ,OUTSTANDING OR PAID DETAILS
9. PROVIDE STATEMENTS
10.GENERATE REPORTS AND DETAILS IN PDF FORMAT
11.TRACKING THE STATUS DETAILS
12.PROVIDE GOOD CUSTOMER CARE ,AND AGENT SYSTEM

4.4 BUSINESS RULES

AGENT PORTAL MANUAL VERSION 1.1 DATE PAGE NO:

BUSINESS REQUIREMENT DOCUMENT-2019

4.5 BACKGROUND:
4.6 PROJECT OBJECTIVES:

5. PROJECT SCOPE:

TO PROVIDE AN IT SOLUTION TO MANAGE AND

EXECUTE IN THE AGENT PORTAL WITH FEATURES LIKE :

1. EFFECTIVE REPORT GENERATION SYSTEM

2. CLAIMS TO BE INTIMATED,OUTSTANDING,PAID,CLOSED AND

REJECTED

3. COMMISION DETAILS REGARDING RECOVERY AND DETAILS

4. RENEWALS OF POLICIES OR CANCELLATION

5. BUSINESS DETAILS OF PREMIUM REPORT GENERATED

6. TYPES OF REPORTS(PRODUCT WISE,OFFICE WISE,FRESH

RENEWED,PREMIUM)

5.1 IN SCOPE FUNTIONALITY:

1.BUSINESS DETAILS
2.RENEWAL DETAILS
3.COMMISSION DETAILS
4.CLAIM DETAILS
5.GENERATE PREMIUM REPORT
6.POLICY DETAILS
7. TYPES OF REPORTS
8. TRACK ONLINE STATUS
9.PAID,REJECTED AND OUTSTANDING CLAIMS
10.RECOVERY DETAILS
11.ALL KINDS OF REPORT GENERATION,GIVEN ONDATE FROM AND
DATE TO.
12.RETRIEVE STAMENTS FROM UPDATES

AGENT PORTAL MANUAL VERSION 1.1 DATE PAGE NO:

BUSINESS REQUIREMENT DOCUMENT-2019

13.VIEW CUSTOMER DATABASE

5.2 OUT SCOPE FUNTIONALITY:

OUT OF SCOPE
1.PRODUCT WISE REPORTS,OFFICE REPORTS,FRESH AND RENEWAL
REPORTS
2.CANCELLED REPORTS POLICIES
3.COMMISSION RECOVERY DETAILS
4.CLAIM PAID STATEMENT
5.CLAIM OUTSTANDING
6. THIRD PARTY ASSISTANCE
7.BUSINESS PROCESSING SYSTEM IN AGENT PORTAL.

5.3 ASSUMPTIONS:

1. AGENT PORTAL HAS GOT ALL CUSTOMER DATABESE IN LEGACY

SYSTEM

2. ONLY REGISTED AGENTS CAN LOG-IN AND ACCESS THE PORTAL

3. BACK OFFICE ADMINISTRATORS ARE WELL AWARE OF DATABASE

SECURITY SYSTEM TO SAFE HANDLE DATABASE

4. AGENTS WELL AWARE OF INTERNET AND USAGE OF PORTAL FOR

THEIR ACTIVITY

5.4 CONSTRAINS:
1. STATUS AND DETAILS OF THE CUSTOMER CAN BE TRACKED ONLY IF
THE BACK OFFICE UPDATES THE DATA

2. ONLY AGENT CAN LOG-IN AND VIEW THE CUSTOMER POLICIES AND
CLAIMS IN THE AGENT PORTAL

AGENT PORTAL MANUAL VERSION 1.1 DATE PAGE NO:

BUSINESS REQUIREMENT DOCUMENT-2019

3. AGENT WITH SPECIFIED RESOURCE ONLY CAN ACESS CUSTOMER

DATA

6.RISK ANALYSIS:
IN THIS SECTION OF THE BRD,RISKS ARE DESCRIBED.A RISK IS
SOMETHING THAT COULD AFFECT THE SUCCESS OR FAILURE OF A
PROJECT.ANALYZE RISKS REGULARLY AS THE PROJECT PROGRESSES.WHILE EVERY
RISK MIGHT NOT BE AVOIDED ,BUT STILL CAN REDUCE THE RISK IMPACTS BY
PREPARING BEFOREHAND.FOR EACH RISK,NOTE THE LIKELIHOOD OF ITS
OCCURANCE,THE COST TO THE PROJECT IF IT OCCURS,AND THE STATERGY FOR
HANDLING THE RISKS.STATERGIES INCLUDE THE FOLLOWING:

 AVOID: DO SOMETHING TO ELIMINATE THE RISK

 MITIGATE: DO SOMETHING TO REDUCE THE DAMAGE IF RISK

MATERIALIZES

 TRANSFER: PASS THE RISK UP OR OUT TO ANOTHER ENTITY

 ACCEPT: DO NOTHING ABOUT THE RISK .ACCEPT THE CONSEQUENCE

TYPES RISKS LIKELI COST STATERGY

OF HOOD
RISKS
1. POSSIBILITY OF DATA TRANSFER:
6.1TE HACKING MEDIU PROJECT PROVIDE DATA HANDLING TO
CHNI 2. 3RD PARTY M COST OUTSOURCE FOR MIGITATION
ASSISTANCE TO AGENT PROCESS.
CAL TO ASSIST CUSTOMER
RISKS DATABASE
3.RESOURCE
ALLOCATION
4.DURING MITIGATION
CHANCES OF MISSING
EXISTING MANUAL
DATA
.

AGENT PORTAL MANUAL VERSION 1.1 DATE PAGE NO:

BUSINESS REQUIREMENT DOCUMENT-2019

1.HUMAN ERROR IN MIGITATE:

6.2 ENTERING DATA AND LOW TRAININ PROVIDE SCHEDULE UPDATE ON
USAGE OF SOFTWARE G COST OPERATING AND NEED BASED
2. AGENT ADOPTION TO TRAINING
SKILL
THE NEW AGENT
RISKS PORTAL IN THE
EXISTING SYSTEM
1.LOOSING CUSTOMER MITIGATION:
6.3 DATABASE DUE TO MEDIU INSTANT CUSTOMERS SHOULD BE INTIMA
IMPROPER UPDATE BY M UPDATE AND THE AGENT MUST GET ALL T
THE 3RD PARTY UPDATES AUTOMATICALLY.
2. EXISTING CUTOMERS S AND
BUSI NOT ACTIVE IN NEW THROUG TRANSFER:WITH TIMELINE THI
NESS AGENT PORTAL DUT TO H ACESS ACTIVITY CAN BE OUT SOUCEDE
RISKS LACK OF AWARENESS TO THE
AGENT
AVOID:PLAN STRUCTURAL WALK
6.4 PROVIDE VALID HIGH SOFTWA THROUGHS WITH THE
LOG IN ,CONTACT RE STAKEHOLDERS.REVIEW AGAIN
BEFORE CODING BEGINS..
NUMERS,PAN UPDATIO
REQU NUMBERS,PASSWO N,VALID
IREME RD,PDF FORMAT CREDEN
NT FOR OUTPUT TIALS
RISKS GENERATION,AND
STATEMENTS ALL
POLICIES
CLAIMS,AND
REPORTS,GENERAT
ED AND UPDATED

6.5 HIGH ACCEPT:

CHAN
GE
REQU
IREME
NT
RISKS

AGENT PORTAL MANUAL VERSION 1.1 DATE PAGE NO:

BUSINESS REQUIREMENT DOCUMENT-2019

Contents

PURPOSE OF THE DOCUMENT 1

DOCUMENT HISTORY 2
DISTRIBUTION 2
VALIDATION 2
1. ICONS USED IN THE MANUEL 4
2. PRESENTATION OF THE SOLUTION 4
2.1 Brief description 4
2.2 Descriptives Icons 4
2.3 Project players 4
2.4 Support 5
2.5 Referenced Documentation 5
2.6 History of the Solution 5
3. CONNECTING TO THE APPLICATION 6
3.1 Address 6
3.2 Authentication 6
4. STRUCTURING OF THE APPLICATION 6
4.1 Layout 6
4.2 Menus 7
4.3 Icons / Shortcuts 7
4.4 Functionalities 7
4.4.1 Functionalities Presented/Described 7
4.4.2 Functionalities not Presented/not Described 7

5. FUNCTION XXX / SCREEN XXX 7

5.1 Screenshot 7
5.2 Descriptions of fields, content 8
5.3 Description of actions 8
5.4 Sequence of screens 8
6. FUNCTION XXX / SCREEN XXX 8
6.1 Screenshot 8
6.2 Descriptions of fields, content 8
6.3 Description of actions 8
6.4 Sequence of screens 9
7. APPENDICES 9
7.1 Appendix 1 9

AGENT PORTAL MANUAL VERSION 1.1 DATE PAGE NO:

BUSINESS REQUIREMENT DOCUMENT-2019
7.2 Appendix 2 9

1. ICONS USED IN THE MANUEL

Throughout this document, the pictograms below are used to underline points or important
notions

Important information

Good to know - Tricks

Risk in front of a parameter setting or of a specific action

Action to be avoided

Mandatory action

Sensitive or difficult procedure. To take into account necessarily

Actions reserved for the …. < Adapt the vocabulary according to the
application (administrator, manager, etc. >

Actions reserved for the … < Adapt the vocabulary according to the
application (user, publisher, etc. >

2. PRESENTATION OF THE SOLUTION

2.1 BRIEF DESCRIPTION

<Give an outline description here>

2.2 DESCRIPTIVES ICONS

<Add if necessary, a table listing the specific signalling system to the application (icons,
buttons and associated actions).
Delete section so useless. >

2.3 PROJECT PLAYERS

<List all the players impacted by the project/solution here:

 Owner of the application

AGENT PORTAL MANUAL VERSION 1.1 DATE PAGE NO:

BUSINESS REQUIREMENT DOCUMENT-2019
 Owner of the data
…
>

2.4 SUPPORT

<List what is needed for a support request here:

 Telephone
 E-mail
 Dedicated application
 …

Describe how to track the progress of the request in order to avoid excessive telephoning>

2.5 REFERENCED DOCUMENTATION

<Some documentation may be useful to the user in helping them understand how application-
related modules work.
List them here if applicable.
>

2.6 HISTORY OF THE SOLUTION

<Give the background here to the various stages in developing the solution from a user
viewpoint.>

AGENT PORTAL MANUAL VERSION 1.1 DATE PAGE NO:

BUSINESS REQUIREMENT DOCUMENT-2019

3. CONNECTING TO THE APPLICATION

3.1 ADDRESS

You must connect to the application using the following address:

<Insert the application's URL here>

3.2 AUTHENTICATION

<Indicate here what information must be given by the user to log on: login AD, surname first
name, e-mail address etc
Insert a screenshot of the authentication page.

Explain and show a screenshot of the page refusing unauthorised access. >

4. STRUCTURING OF THE APPLICATION

4.1 LAYOUT

<For a web application describe the structuring of the pages if they follow the same pattern.
An example is given below.>

Icons / Shorcuts

Processing area

AGENT PORTAL MANUAL VERSION 1.1 DATE PAGE NO:

BUSINESS REQUIREMENT DOCUMENT-2019

4.2 MENUS

<List the menus, shown in tree-structure >

4.3 ICONS / SHORTCUTS

<Show each icon or shortcut, together with a description. >

4.4 FUNCTIONALITIES

4.4.1 FUNCTIONALITIES PRESENTED/DESCRIBED

<List here all the functionalities that will be described in the document.
You could group together a number of similar functions or functionalities linked within a
workflow for example. These groupings should be shown here to give the user the map they
need to read the document. >

4.4.2 FUNCTIONALITIES NOT PRESENTED/NOT DESCRIBED

<List here all the functionalities that will not be described in the document.

It is not necessary to present all the functionalities of an application:

 because it is already described elsewhere: you could insert a link or reference etc
 because the functionality is unimportant
 …

>

5. FUNCTION XXX / SCREEN XXX

<Description of the functionality >

5.1 SCREENSHOT

<Not absolutely necessary but often very useful, with arrowed explanations, and boxing or
circling of different fields for user input or presentation>

AGENT PORTAL MANUAL VERSION 1.1 DATE PAGE NO:

BUSINESS REQUIREMENT DOCUMENT-2019

5.2 DESCRIPTIONS OF FIELDS, CONTENT

<Show the fields, particularly the mandatory fields, and/or the input masks which are
checked
Show the colour codes if there are any.
Show the lists and explain their content
…>

5.3 DESCRIPTION OF ACTIONS

<Explain the actions possible for the given screen, and the consequences, without
reproducing the functional specifications.
Nevertheless it may prove useful, if not necessary, to reiterate a business rule or
management rule.>

5.4 SEQUENCE OF SCREENS

<If necessary show the sequence of screens.>

6. FUNCTION XXX / SCREEN XXX

<Description of the functionality >

6.1 SCREENSHOT

<Not absolutely necessary but often very useful, with arrowed explanations, and boxing or
circling of different fields for user input or presentation>

6.2 DESCRIPTIONS OF FIELDS, CONTENT

<Show the fields, particularly the mandatory fields, and/or the input masks which are
checked
Show the colour codes if there are any.
Show the lists and explain their content
…>

6.3 DESCRIPTION OF ACTIONS

<Explain the actions possible for the given screen, and the consequences, without
reproducing the functional specifications.

AGENT PORTAL MANUAL VERSION 1.1 DATE PAGE NO:

BUSINESS REQUIREMENT DOCUMENT-2019
Nevertheless it may prove useful, if not necessary, to reiterate a business rule or
management rule.>

6.4 SEQUENCE OF SCREENS

<If necessary show the sequence of screens.>

7. APPENDICES

7.1 APPENDIX 1

<Give here any additional information that could make the functional specifications easier to
understand.>

7.2 APPENDIX 2

End of document

AGENT PORTAL MANUAL VERSION 1.1 DATE PAGE NO: