RSD All Market Segments - Personal Accident Insurance - v1

BDO Insurance Brokers, Inc.
(BDOI)
Requirements Specification Document
For uploading of Personal Accident Insurance
Version 0.01
Creation Date: January 2015
User of this document is responsible to use only the current version available on HQ and headMine.
The information contained in this document is not to be used for any purpose other than the purposes for which this document is
furnished by GENPACT, nor is this document (in whole or in part) to be reproduced or furnished to third parties or made public
without the prior express written permission of GENPACT.

Uploading requirements 03
Version 0.01
Document History
Version
Date
Author
0.01
January 28, 2015
Jeffrey Oliveros
Description of
Change
Document creation
Reviewed By
Approved
By
Conchita Valena
Reference Documents
Document Name
Version
Date Updated
BR Uploading for Individual Personal Accident Insurance of BBG

Consumer 2 for New Business
Requirements Specification Document for Pipeline Management,
Solicitation and Placement
3/17/2014
0.04
4/3/2014
Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)
Page 2 of 19

Version 0.01
TABLE OF CONTENTS
1. Process Schematic / Process Flow................................................................................................. 4
2. Functional Description.................................................................................................................... 6
2.1 RID 1 Uploading of Data to Staging.......................................................................................... 6
2.1.1 Features....................................................................................................................... 6
2.1.2 UI Wireframe................................................................................................................ 9
2.1.3 Inputs and Outputs..................................................................................................... 11
2.1.4 Reports Specification.................................................................................................12
2.1.5 Business Requirements Mapping...............................................................................12
2.2 RID 2 Uploading of Data from Staging to Pipeline..................................................................12
2.2.1 Features..................................................................................................................... 12
2.2.2 UI Wireframe.............................................................................................................. 16
2.2.3 Inputs and Outputs..................................................................................................... 16
2.2.4 Reports Specification.................................................................................................17
2.2.5 Business Requirements Mapping...............................................................................17
Page 3 of 19

Version 0.01
1. Process Schematic / Process Flow

UPLOADING OF DATA TO STAGING
BDOI
BROKER SYSTEM
Start
STAGING
C
D
Prepares file
containing list of
A
checked/validated
Personal Accident
Application form
Uploads file to the

Broker system
VALIDATION OF UPLOAD FILE - STAGING

BROKER SYSTEM
A
Validates completeness
and duplicate entries in
the upload file
N
Passed
criteria
?
Y
Page 4 of 19

Version 0.01
UPLOADING OF DATA TO PIPELINE

BROKER SYSTEM
B
Validates and matches data

from the upload file against
Pipeline records
N
Passed
criteria?
Generates
exception report file
Extract File
Y
Uploads data to the
Pipeline
Broker System
End
Page 5 of 19

Version 0.01
2. Functional Description
2.1 RID 1 Uploading of Data to Staging
This function provides a facility in the system that will validate and upload the data to Staging. Data
from the upload file consisting of verified and confirmed list of application for Personal Accident
Insurance will be copied to STAGING to check if these are compliant with the validation criteria prior
to uploading to the PIPELINE module of the Broker system.
2.1.1 Features
1. System facility to allow user to upload files. A module will be available to the user to
upload the list of verified and validated applicants for the Personal Accident Insurance.
Below are the contents of the upload file.
PERSONAL ACCIDENT
INSURANCE
Salutation
Name Suffix
Last Name
First Name
Middle Name
Gender 1
Email Address
Type of Address
No., Building, Street
Barangay
City/Municipality
Province
Contact Number
Contact Number Type
Assured Name
Account Type
Policy Currency
Policy Delivery
Insurance
Insurance Share
Premium Rate
Commission Rate
Inception Date
Expiry Date
Package or Non-Package
Package Name
Total Sum Insured
Occupation
Birthdate
Limit of Liability
Employer
Gender 2
Beneficiary 1
REMARKS
To be uploaded to the Client Administration
General Information tab
To be uploaded to the Client Administration

Contact Details tab
To be uploaded to the Account Management Basic

Information tab
To be uploaded to the Account Management Risk

Info tab
To be uploaded to the Account Management Risk

Details (Personal Accident Insurance)
Page 6 of 19

Version 0.01
Beneficiary Birthdate 1
Relationship with Assured 1
Beneficiary 2
Beneficiary 3
BDOI Account Officer
Date Referred
Business Origin
Sub Business Origin
To be uploaded to Account Management Other

Information
2. System detection on the type and location of files to be uploaded. The system will detect
the type and location of files to be uploaded to the broker system through the UPLOAD
FILE MAINTENANCE TABLE in the BDOI Brokerage System.
FILE
Personal Accident
Insurance
Personal Accident
Insurance
STATUS
For uploading
Uploaded
LOCATION
\\BDOI\For uploading\Personal
Accident Insurance
\\BDOI\Uploaded\Personal Accident
Insurance
FILENAME
XY
XY
WHERE:
CODE
X
Y
VALUE
PAI = Personal Accident Insurance
Date (MMDDYYYY format)
FOR UPLOAD folder pertains to files that have not been uploaded to the system.
PROCESSED refers to files that have been uploaded to the system. Files that have been
processed will be automatically moved by the system from the FOR UPLOAD folder to the
PROCESSED folder.
The system will allow the user to upload files in MS OFFICE OR OPEN OFFICE FORMAT
provided that these complied with the system requirements. The system will disregard the
version release of these applications.
3. System detection on the files due for uploading. Based on the date indicated in the
filename of the upload files, the system will prompt the user regarding files that should be
uploaded. To illustrate:
Let us assume that there are several upload files in the predefined repository.
UPLOAD FILES
PAI01032015
PAI01052015
PAI01062015
PAI01092015
PAI01102015
If the system date is January 3, 2015,

user will be prompted of that upload file
Page 7 of 19

Version 0.01
PAI01032015 should be uploaded.

In the case of files that have not been uploaded based on the date corresponding to its
filename, the system will allow the user to upload these provided that the filename dates
are not beyond the current or system date. Let us presume that the current date is January
8, 2015. Based on the above example, the user will also be prompted of the following files
that are due for uploading.
UPLOAD FILES
PAI01032015
PAI01052015
PAI01062015
4. System facility to establish the type of extract file. Since the information that will be
extracted will differ depending on who is the target recipient of the file, a header code will
be placed in each extract file. As discussed in the main section of the RSD, there will be
centralized uploading module but the format of the extract and upload file will differ based
on the data per process per module that will be uploaded to the broker system.
Below is the proposed naming convention for the header code.
EXTRACT FILE
HEADER CODE
Personal Accident Insurance
XY
WHERE:
HEADER CODER
X
Y
DESCRIPTION
Date of upload (MMDDYYYY format)
The system will check the type of upload file based on the HEADER CODE. Each type of
file requires different uploading criteria.
5. System checking on the contents of the upload file. The system will validate if following
requirements have been met prior to uploading the data to the Pipeline module.
Page 8 of 19

Version 0.01
VALIDATION
ALL entries in the upload file
as listed in the section 2.1.1.1
Header Code
Format
Number of Records
CONDITION
o There should be no NULL values
o There should be no DUPLICATE CLIENT NAME
(LAST NAME, FIRST NAME AND MIDDLE NAME
that is EXACTLY THE SAME). To illustrate:
The upload file should INDICATE a header code based

on the prescribed format
The format should satisfy the standards defined in the
system to be considered as READABLE CONTENTS.
Otherwise, the system will reject the file. The list of
special characters allowed in the system and the
required data formats can be found in the RSD for
PIPELINE and the TECHNICAL DESIGN DOCUMENT
that will be prepared by GENPACT.
Validation of HASH TOTAL versus RECORD COUNT.
These two should yield the same value
If the above conditions are NOT SATISFIED, the system will REJECT the ENTIRE upload
File
6. System facility to prompt system message after records have been validated. In the event
that the file had been validated to be NOT valid for uploading, the user will be prompted of
a system message informing him that the file cannot be uploaded to the system. For files
that are valid for uploading, the system will not prompt a system message to the user
2.1.2
UI Wireframe
DATA UPLOADING MENU
Page 9 of 19

Version 0.01
DATA UPLOADING WINDOW
Page 10 of 19

Version 0.01
DATA VALIDATION RESULT MESSAGE
Page 11 of 19

Version 0.01
2.1.3
Inputs and Outputs
DATA UPLOADING MENU

DATA ELEMENT
Personal Accident
Insurance
BEHAVIOR
FORMAT
RANGE OF VALUES
Executable
button
REMARKS
Directs the user to
the DATA
UPLOADING
WINDOW
DATA UPLOADING WINDOW

DATA ELEMENT
BEHAVIOR
File
Display
Location
Display
Select
Check box
Select All
Check box
Upload
Executable
button
Close
Executable
button
FORMAT
RANGE OF VALUES
REMARKS
Shows file for
uploading per
product type.
Shows location of
files for uploading.
If checked,
includes the file for
uploading.
If checked, selects
all file for
uploading. If
unchecked,
deselects all data
for uploading.
Uploads the file
selected by the
user to the system.
Closes the DATA
UPLOADING
WINDOW
Page 12 of 19

Version 0.01
DATA VALIDATION RESULT MESSAGE

DATA ELEMENT
BEHAVIOR
Message
Display
Ok
Executable
button
FORMAT
2.1.4
N/A
Reports Specification
2.1.5
Business Requirements Mapping

ITEM #
BRM-UP03-RID1-001
BRM-UP03-RID1-002
RANGE OF VALUES
REMARKS
Closes the
VALIDATION
RESULT
MESSAGE
WINDOW
BR REQUIREMENTS
FEATURES
The system should be able to

upload list containing clients
who availed of the Personal
Accident Insurance product
The
system
should
automatically show or prompt
the user regarding files to be
uploaded.
System facility to upload Personal

Accident Insurance upload file.
System facility to detect and

prompt the user due for uploading
based on the predefined location in
the system.
Page 13 of 19

Version 0.01
BRM-UP03-RID1-003
The system should be able to

validate if the upload file is valid
for uploading to the broker
system.
System facility to check if the

upload file conforms to the upload
criteria prior to uploading to the
Pipeline module.
2.2 RID 2 Uploading of Data from Staging to Pipeline

This function provides a facility in the system that will UPLOAD the data from the STAGING to the
PIPELINE MODULE of the Broker System. This stage presumes that the file have already confirmed
to be valid for uploading based on the validation procedure and criteria discussed in the preceding
section.
2.2.1 Features
1. System facility to validate predefined data. The following data from the Staging will be
CHECKED AND MATCHED by the system if EXISTING or PREDEFINED in the Pipeline.
If any of these are non-existent in the database, the system will REJECT the record and
include this in the EXCEPTION REPORT.
PERSONAL ACCIDENT INSURANCE
Salutation
Name Suffix
Gender 1
Type of Address
Province
Contact Number Type
Account Type
Policy Currency
Policy Delivery
Insurance
Package Name
Gender 2
BDOI Account Officer
Business Origin
Sub Business Origin
2. System facility to validate duplicate records. The system will for duplicate records from
STAGING and PIPELINE based on the following criteria.
STAGING
PIPELINE
Last Name + First

Name + Middle Name
and Birthdate
Last Name + First

Name + Middle
Name and Birthdate
Record is exactly
the same
RESULT
Last Name + First
Last Name + First
Record differs
ACTION
The system will
NOT CREATE a
Client
ID
and
Account
Reference
Number but will
upload the data
corresponding to
the record
The system will
Page 14 of 19

Version 0.01
Name + Middle Name

and Birthdate
Name + Middle
Name and Birthdate
create a Client ID
and
Account
Reference
Number
and
upload the data
corresponding to
the record.
3. System facility to upload data. Subject to the condition and validation mentioned in section
2.2.1.1 and 2.2.1.2, the system will UPLOAD the data below and UPDATE the Pipeline
information pertaining to the record that had been uploaded.
Page 15 of 19
DATA
ACTION
VALUE/SOURCE
Client ID
Client Type
Salutation
Name Suffix
Last Name
First Name
Middle Name
Gender 1
Email Address
Client
Classification
Type of Address
No., Building,
Street
Barangay
City/Municipality
Province
Region
Update
Update
Upload
Upload
Upload
Upload
Upload
Upload
Upload
Update
System Generated
Individual
From the upload file
Normal
Upload
Upload

Upload
Upload
Upload
Update

Based on the
Province indicated in
the upload file
Zip Code
Update
Country
Contact Number
Contact Number
Type
Account
Reference
Number
Assured Name
Update
Upload
Upload
Based on the
Province indicated in
the upload file
Philippines
Update
System Generated
Update
Pipeline Stage
Update
Pipeline Status
Update
Account Type
Transaction
Type
Policy Currency
Policy Delivery
Insurance
Insurance Share
Premium Rate
Commission
Rate
Line of
Insurance
Upload
Update
The same as Last

Name, First Name
and Middle Name.
System to
concatenate data
from the upload file.
System assigned
based on workflow.
System assigned
based on workflow.
New Business
Upload
Upload
Upload
Upload
Upload
Upload

Update
Product Type
Update
Type of Entry
Inception Date
Update
Upload
Based on the
package indicated in
the upload file
Personal Accident
Insurance
Individual
Expiry Date
Upload
Package or Non- Update
Package
Classification: GENPACT
Internal All rights reserved. Copyright(2008-2014)
Package
Convert To
Update
Placement
Package Name
Upload
DESTINATION
/LOCATION
Client Administration General
Requirements
Information
tabSpecification Document
Version 0.01
Client Administration Contact

Details tab
Account Management Basic

Information tab
Account Management Risk Info

tab
Page 16 of 19

Version 0.01
4. System facility to generate exception reports. In the event that records in the upload file
did not meet the criteria mentioned in 2.2.1.1, an exception report consisting of the same
data columns indicated in the uploaded file will be saved and generated by the system to a
predefined server directory. Below is the proposed repository of the exception report.
FILE
Personal Accident
Insurance
STATUS
Unmatched
LOCATION
\\BDOI\Unmatched\Personal
Accident Insurance\
FILENAME
XYZA
WHERE:
CODE
X
Y
Z
A
VALUE
Date of upload (MMDDYYYY format)
Timestamp (HH:MM:SS format)
E = Exception
User will be allowed to upload an exception file by adding a target date of upload and
placing the file to the predefined path mentioned in section 2.1.1.2 of this document.
Page 17 of 19

Version 0.01
5. System generation of display message after uploading. The system will prompt the user of
a message indicating that ALL records have been uploaded successfully and if there are
UNMATCHED records.
6. System display of history of uploaded files. User will be able to VIEW records of previous
files that have been uploaded to the system
2.2.2 UI Wireframe
DATA UPLOADING CONFIRMATION/UNMATCHED RECORD MESSAGE WINDOW
2.2.3 Inputs and Outputs

DATA UPLOADING CONFIRMATION/UNMATCHED RECORD MESSAGE WINDOW
DATA ELEMENT
BEHAVIOR
Message
Display
Close
Executable
button
FORMAT
RANGE OF
VALUES
REMARKS
Closes the DATA

UPLOADING
CONFIRMATION/UN
MATCHED RECORD
MESSAGE WINDOW
Page 18 of 19

Version 0.01
2.2.4 Reports Specification

N/A
2.2.5 Business Requirements Mapping

ITEM #
BRM-UP03-RID2-001
BRM-UP03-RID2-002
BR REQUIREMENTS
FEATURES
User should be able to

upload the data from the
staging to the Broker
System.
The system should be
able to match, validate
and update target data
fields versus source data
fields in the upload file.
Facility to allow the user to upload

the data from the staging to the
Broker System.
Facility to match, validate and

update target data fields versus
source data fields in the upload file.
Page 19 of 19

RSD All Market Segments - Personal Accident Insurance - v1

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

RSD All Market Segments - Personal Accident Insurance - v1

Uploaded by

Copyright:

Available Formats

BDO Insurance Brokers, Inc.

Requirements Specification Document

January 28, 2015

BR Uploading for Individual Personal Accident Insurance of BBG

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

1. Process Schematic / Process Flow

Uploads file to the

VALIDATION OF UPLOAD FILE - STAGING

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

UPLOADING OF DATA TO PIPELINE

Validates and matches data

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

To be uploaded to the Client Administration

To be uploaded to the Account Management Basic

To be uploaded to the Account Management Risk

To be uploaded to the Account Management Risk

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

To be uploaded to Account Management Other

If the system date is January 3, 2015,

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

PAI01032015 should be uploaded.

Personal Accident Insurance

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

The upload file should INDICATE a header code based

DATA UPLOADING MENU

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

DATA UPLOADING WINDOW

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

DATA VALIDATION RESULT MESSAGE

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

Inputs and Outputs

DATA UPLOADING MENU

DATA UPLOADING WINDOW

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

DATA VALIDATION RESULT MESSAGE

Business Requirements Mapping

The system should be able to

System facility to upload Personal

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

System facility to detect and

Requirements Specification Document

The system should be able to

System facility to check if the

2.2 RID 2 Uploading of Data from Staging to Pipeline

Last Name + First

Last Name + First

Last Name + First

Last Name + First

Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)

Requirements Specification Document

Name + Middle Name