You are on page 1of 22

BDO Insurance Brokers, Inc.

(BDOI)
Requirements Specification Document
CLG Renewal
v2.0
Creation Date: October 2016

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.

Requirements Specification Document


CLG Renewal
Version 2.0

Document History
Version
0.01

Date

Author

September 20,
2016

Jeffrey
Oliveros

Description
Document
creation

Reviewed By

Approved By

Alfredo
Galang

Distribution List
Name

Role

Department/Unit

Please refer to sign-off sheet

Reference Documents
Document Name
Change Request CLG New Business and Renewal Business

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

Version

Date Updated

1.0

6/13/2016

Page 2 of 22

Requirements Specification Document


CLG Renewal
Version 1.0

TABLE OF CONTENTS
1.

2.

3.

2.
3.

Introduction.......................................................................................................................................... 4
1.1. Purpose...................................................................................................................................... 4
1.2. Audience.................................................................................................................................... 4
1.3. Scope......................................................................................................................................... 4
1.4. Definition of Terms and Acronyms.............................................................................................. 4
Overview.............................................................................................................................................. 5
2.1. System Objectives..................................................................................................................... 5
2.2. Functional Overview.................................................................................................................. 5
2.3. Process Schematic / Process Flow............................................................................................ 6
2.4. Interfaces with Users................................................................................................................. 8
Functional Description.......................................................................................................................... 8
3.1. RID1 Validation and uploading of files........................................................................................ 8
3.1.1. Features................................................................................................................................ 8
3.1.2. UI Wireframe....................................................................................................................... 14
3.1.3. Inputs and Outputs.............................................................................................................. 14
3.1.4. Reports Specification.......................................................................................................... 15
3.1.5. Business Requirements Mapping........................................................................................ 15
3.2. RID2 Updating of Pipeline module........................................................................................... 15
3.2.1. Features.............................................................................................................................. 15
3.2.2. UI Wireframe....................................................................................................................... 16
3.2.3. Inputs and Outputs.............................................................................................................. 16
3.2.4. Reports Specification.......................................................................................................... 16
3.2.5. Business Requirements Mapping........................................................................................ 16
3.3. RID 3 Generation of Expiry List, Sanitation and Disposition of records...................................16
3.3.1. Features.............................................................................................................................. 16
3.3.2. UI Wireframe....................................................................................................................... 18
3.3.3. Inputs and Outputs.............................................................................................................. 18
3.3.4. Reports Specification.......................................................................................................... 18
3.3.5. Business Requirements Mapping........................................................................................ 18
3.4. RID Viewing of records in the repositories...............................................................................18
3.4.1. Features.............................................................................................................................. 18
3.4.2. UI Wireframe....................................................................................................................... 19
3.4.3. Inputs and Outputs.............................................................................................................. 19
3.4.4. Reports Specification.......................................................................................................... 19
3.4.5. Business Requirements Mapping........................................................................................ 19
Risks, Issues, and Constraints........................................................................................................... 19
2.1. Design Constraints..................................................................................................................... 20
2.2. Hardware and Software Constraints...........................................................................................20
Assumptions and Dependencies........................................................................................................ 20

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

Page 3 of 22

Requirements Specification Document


CLG Renewal
Version 2.0

1. Introduction
This document list and explains the changes in the original requirements of CLG Renewal Business
uploading and sanitation module.
1.1. Purpose
The purpose of this document is to formalize amends to the original design and features of the CLG
Renewal uploading and sanitation module.
This document supersedes the following:
DOCUMENT NAME

DOCUMENT DATE

Requirements Specification Document CLG Renewal v1.0

8/19/2014

Requirements Specification Document CLG Renewal ADDENDUM v0.01

10/10/2015

1.2. Audience
This documents intended audiences are the project stakeholders and project participants from both
BDO Insurance, BDO IT Development Insurance.
1.3. Scope
This document covers the following sections:
SECTION NAME
Overview

PURPOSE

Risk, Issues, and


Constraints

Provides the system objective, functional overview, process flow, interfaces


with databases and users, and production environment in which the
system will operate.
Provides a detailed description of the system capabilities and
functionalities.
Provides a list of any known and potential risks, issues, and constraints
that would hinder or delay completion and delivery of the system.

Assumptions and
Dependencies

Provides a list of factors that will affect the requirements stated in this
document.

Functional Description

1.4. Definition of Terms and Acronyms


TERMS

DEFINITION

BDOI

Banco De Oro Insurance

Pipeline

Contains list of Account records that are either In Process or Booked

PN No.

Promissory Note Number

Readable Contents

Format of the contents of the upload file that is recognized by the system for
processing.

Repository

Also known as Bucket. This refers to the table in the system database where
records will be uploaded based on the result of the matching and sanitation
process.

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

Page 4 of 22

Requirements Specification Document


CLG Renewal
Version 2.0

2.

Overview
2.1. System Objectives
The objective of the system is to provide a facility for the group of BDOI CLG - Renewal that will
update the Loan Amount Balance of the Account records and to determine expiring policies and
placing these in the appropriate system repositories for further processing.
2.2. Functional Overview
The CLG Loans (with Outstanding Balance and AO Code) and Loans Fully Paid Accounts files will
be uploaded to the Broker System. The system will match the Promissory note number and Product
type description contained in these files as against the same record in the Pipeline. If there is a
matched the system will update the Outstanding Balance field of the account record in the pipeline
based on the amount indicated in the files. After which, the system will determine those accounts
that will expire and will perform the sanitation process.

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

Page 5 of 22

Requirements Specification Document


CLG Renewal
Version 2.0

2.3. Process Schematic / Process Flow


VALIDATION AND UPLOADING OF FILES TO STAGING
BDOI CLG RENEWAL

BROKER SYSTEM

Validates data columns


Start
and data formats
Uploads CLG Loans (with
N Outstanding Balance and AO
Code)* and LoansData
Fullycolumns
Paid
and format are
Accounts
correct? entries
Y all required
and
entries are
present?
Checks
duplicate
and
Corrects CLG Loans
(with
mandatory
entries
Outstanding Balance and
Code) and Loans Fully Paid
Accounts

No duplicate
entries and all
mandatory
entries are
present?
Y

Staging
Staging table
table

* - Consist of multiple sheets (CLG Auto 1, CLG AUTO 2, CLG Business, CLG Home 1 and CLG Home 2)

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

Page 6 of 22

Requirements Specification Document


CLG Renewal
Version 2.0

UPDATING OF PIPELINE MODULE


A

Chooses account with status = In


Process or Booked

Matches PN Number and Product Type


description in the CLG Loans (with
Outstanding Balance and AO Code) and
Loans Fully Paid Accounts as against PN
Number and Product Type description in the
Pipeline module of the Broker system
N
Matched?

End

Y
Updates Loan Amount Balance, Loan
Balance Date and ICBS Officer Code in the
Pipeline module of the Broker System

Updated
Updated Pipeline
Pipeline
module
module

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

Page 7 of 22

Requirements Specification Document


CLG Renewal
Version 2.0

GENERATION OF EXPIRY LIST AND SANITATION OF RECORDS


BDOI CLG RENEWAL

BROKER SYSTEM

Performs
B data
sanitation
Generates expiry list in
Renewal module

Repositories
Repositories

End

2.4. Interfaces with Users


The uploading of CLG Loans (with Outstanding Balance and AO Code) and Loans Fully Paid
Accounts will be done through the Renewal module of the Broker System. Files will be stored in the
predefined location to be visible in the upload facility. Uploading of the files will be done manually by
BDOI on a monthly basis. User will be allowed to view the records that have been placed in the
appropriate repositories after the system has performed the sanitation process.

3.

Functional Description
3.1. RID1 Validation and uploading of files
This function provides a facility in the system that will validate the compliance of the upload files
(CLG Loans (with Outstanding Balance and Code) and Loans Fully Paid Accounts) with the
predefined standards and formats. The upload program will validate the format and contents of the
files to ensure that these comply with the system requirements.
3.1.1. Features
1. System facility to allow user to upload CLG Loans (with Outstanding Balance and AO
Code) and Loans Fully Paid Accounts. A module will be available to the user to upload
files. Access to this module will be controlled through the Access Control module of the
system.
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 Staging table. Below are the proposed
file naming convention and the location of the upload files prior and after uploading:

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

Page 8 of 22

Requirements Specification Document


CLG Renewal
Version 2.0

FILE
CLG Loans (with
Outstanding
Balance and AO
Code)

STATUS
For
uploading

LOCATION
\\BDOI\For
Upload\CLGRN\Outstanding

FILENAME
AMMDDYYYY

CLG Loans (with


Outstanding
Balance and AO
Code)
CLG Loans (with
Outstanding
Balance and AO
Code)
Loans Fully Paid
Accounts
Loans Fully Paid
Accounts
Loans Fully Paid
Accounts

Uploaded

\\BDOI\Uploaded\CLGRN\Outs
tanding

AMMDDYYYY

Rejected

\\BDOI\Rejected\CLGRN\Outst
anding

AMMDDYYYY

For
uploading
Uploaded

\\BDOI\For
Upload\CLGRN\Fully Paid
\\BDOI\Uploaded\CLGRN\
Fully Paid
\\BDOI\Rejected
Upload\CLGRN\Fully Paid

BMMDDYYYY

Rejected

BMMDDYYYY
BMMDDYYYY

Where:
CODE
A
B
MM
DD
YYYY

VALUE
CLG Loans (with Outstanding Balance and AO Code)
Loans Fully Paid Accounts
January to December
Last day of the month. Valid values are: 28th, 29th, 30th or 31st depending on
the month the file will be uploaded. Otherwise, the filename will be
considered as non-compliant and will be rejected by the system.
Year based on system date

To illustrate the above file naming convention, the filename of CLG Loans (with
Outstanding Balance and AO Code) that will be uploaded by the user for the month of
September will A09312016.
For Upload folder pertains to files that have not been uploaded to the system. Files that
have been processed will be automatically moved by the system from the FOR UPLOAD
folder to the Uploaded folder. In case all or one of the upload files is non-compliant with
the prescribed standards and format, these will not be processed by the system and will
be moved from the For Uploading folder to the Rejected folder.
The system will allow the user to upload files in Microsoft Office and Open Office format
provided that the files complied with the data and format 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. Below are illustrative examples:

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

Page 9 of 22

Requirements Specification Document


CLG Renewal
Version 2.0

The following files were stored in the predefined location (For upload) folder.
CLG LOANS
(with Outstanding Balance and AO Code)
A05302016
A06302016
A07302016
A08302016
A09302016

LOANS FULLY PAID ACCOUNTS


B05302016
B06302016
B07302016
B08302016
B09302016

If the system date is August 30, 2016, user will be prompted of the following files that
should be uploaded to the system:
CLG LOANS
(with Outstanding Balance and AO Code)
A05302016
A06302016
A07302016
A08302016

LOANS FULLY PAID ACCOUNTS


B05302016
B06302016
B07302016
B08302016

User will not be allowed to upload more than one (1) file per type in a month. Using the
above example, if A05302016 was uploaded in the morning of May 30, 2016, it can no
longer be uploaded in the afternoon or at any other time on the same date. Similarly, if
A05302016 (which was already uploaded on May 30, 2016) will be uploaded again on
June 1, 2016, the system will not be processed due to the one file per type limit per
month rule. User has to change the date in the filename and upload the file in the
succeeding months.
If in case of files were not uploaded based on the date corresponding to its filename and
were uploaded to a different month, the system will process that files provided that the
date of the files are not beyond the system date. To illustrate:
The following files were not uploaded.

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

Page 10 of 22

Requirements Specification Document


CLG Renewal
Version 2.0

CLG LOANS
(with Outstanding Balance and AO Code)
A05302016
A06302016
A07302016
A08302016
A09302016

LOANS FULLY PAID ACCOUNTS


B05302016
B06302016
B07302016
B08302016
B09302016

If the system date is July 30, 2016, only the following will be visible to the user for
uploading:
CLG LOANS
(with Outstanding Balance and AO Code)
A05302016
A06302016
A07302016

LOANS FULLY PAID ACCOUNTS


B05302016
B06302016
B07302016

The following files will not be prompted to the user because the dates in the filename are
beyond the system date.
CLG LOANS
(with Outstanding Balance and AO Code)
A08302016
A09302016

LOANS FULLY PAID ACCOUNTS


B08302016
B09302016

The system will only allow uploading of files on the current month for files pertaining to
the previous months. Files for the current month will only be processed on the
succeeding months.

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

Page 11 of 22

Requirements Specification Document


CLG Renewal
Version 2.0

CLG LOANS
(with
Outstanding
Balance and AO
Code)
A05302016
A06302016
A07302016
A08302016
A09302016

MONTH OF
PROCESSING

June onwards
July onwards
August onwards
September onwards
October onwards

LOANS FULLY
PAID ACCOUNTS

B05302016
B06302016
B07302016
B08302016
B09302016

MONTH OF
PROCESSING

June onwards
July onwards
August onwards
September onwards
October onwards

The system will automatically pair the upload files (CLG LOANS (with Outstanding
Balance and AO Code) and Loans Fully Paid Accounts.) per month based on the
filename. These will be marked as Selected. However, the user can remove the default
tick mark in the event that he does not want to upload one of the files. To illustrate:
CLG LOANS
(with Outstanding
Balance and AO Code)
A05302016
A06302016
A07302016
A08302016
A09302016

LOANS FULLY PAID


ACCOUNTS
B05302016
B06302016
B08302016
B09302016
B012302016

ACTION
Paired
Paired
Not paired
Not paired
Not paired

Based on the above examples, A05302016 was paired with B05302016 and A06302016
with B06302016 because both reflect the same month in its filename. The term paired
means that both files will be marked as Selected in the upload user interface.
4. System uploading of multiple sheets/tabs in a file. User will be allowed to upload the CLG
Loans (with Outstanding Balance and AO Code) consisting of several sheets listed as
follows: CLG Auto 1, CLG Auto 2, CLG Business, CLG Home 1 and CLG Home 2. The
system will check if the names of the sheets are based on the preceding. Otherwise, it
will not process the file. The file may contain all or some of the sheets listed.
Nonetheless, the system will not restrict the user from uploading the file if some of the

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

Page 12 of 22

Requirements Specification Document


CLG Renewal
Version 2.0

sheets were not included in the file.


5. System checking on duplicate contents of the CLG LOANS (with Outstanding Balance
and AO Code) and Loans Fully Paid Accounts. To ensure that the file does not contain
duplicate records, the system will validate the contents of the data columns in CLG
LOANS (with Outstanding Balance and AO Code) file (all sheets - CLG Auto 1, CLG Auto
2, CLG Business, CLG Home 1 and CLG Home 2) versus contents of the Loans Fully
Paid Accounts.
CLG LOANS (with Outstanding Balance and
AO Code)
PN Number
Product Description

LOANS FULLY PAID


PN Number
Product Type Description

The system will first check if duplicate records exist within the file. After which, it will
compare the contents of one file against the other.
If there are duplicate records, the system will reject all/entire files. User will have to
perform the necessary corrections to be able to upload the files.
The above validation will only be performed on the files that will be uploaded on the same
month. Duplicate contents in the files that will be uploaded in a different or succeeding
month will no longer be detected by the system.
6. System validation on the format of the contents of the upload files. The system will check
if the contents of the upload file comply with the requisites of the system. The format
should satisfy the standards defined in the system to be considered as READABLE
CONTENTS. Otherwise, the system will reject all/entire files. Examples of NONREADABLE contents are as follows:
CLG LOANS (with
Outstanding Balance
and AO Code)
PN Number
Product Description

NON-READABLE

LOANS FULLY
PAID

NON-READABLE

%%%kLL
3/3/78,YY#%

%%%kLL
3/3/78YY#%

O/S Bal. (LCYE)


Officer (AO Code)

AASSS
%^&*

PN Number
Product Type
Description
Posting Date

HJK()

The contents of the data field should correspond to the data type. If the data field is a
date, the contents should not contain letters or characters. This rule will apply to the other
data fields.

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

Page 13 of 22

Requirements Specification Document


CLG Renewal
Version 2.0

7. Validation regarding the total number of records in the raw file versus those that have
been uploaded to the Staging repository. Raw file refers to the contents of the
excel/upload file that have been uploaded by the user. These will be compared to the
contents of the Staging repository to ensure that the data (after undergoing data
management procedure (e.g. concatenate)) have been completely accounted for. To
illustrate:
UPLOAD FILE
200
300
100

STAGING
200
150
120

ACTION
Upload
Reject
Reject

8. System detection on duplicate upload files. The system will record the file name of the
upload file to a registry table inside the database to ensure that no duplicate files will be
uploaded to the system.
DATE
06/30/2016
07/30/2016
08/30/2016

FILENAME
A05302016
A05302016
A05302016

REMARKS
Unique
Duplicate
Duplicate

9. System validation on the completeness and correctness of the data columns of the
upload files. The system will check if all the data columns are present in the file that will
be uploaded to the system. Below is the list of required data columns per type of file:
CLG LOANS (with
Outstanding Balance
and AO Code)
CLG Auto 1, CLG Auto
2, CLG Business, CLG
Home 1 and CLG Home
2

DATA COLUMNS
PN Number
Product Description
O/S Bal. (LCYE)
Officer (AO Code)

LOANS FULLY PAID


PN Number
Product Type Description
Posting Date

ENTRIES
Required
Required
Required
Required

ENTRIES
Required
Required
Required

10. System facility to check predefined data. The system will check if the following values in
the upload files are exist in the Broker System. Otherwise, the system will reject the
entire.

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

Page 14 of 22

Requirements Specification Document


CLG Renewal
Version 2.0

CLG LOANS (with Outstanding


Balance and AO Code)
Product Description
Officer (AO Code)

LOANS FULLY PAID


Product Type Description

11. System facility to generate an exception log. In the event that records in the upload file
did not meet the criteria listed in the preceding a log file will be generated by the system.
The exception report will adapt the exact format of the correct /standard upload file and
will consist of records that are non-compliant with the required standards and format.
The log file will be generated and saved by the system to a predefined server directory.
Below is the proposed repository and filename of the exception report:
FILE
CLG Loans (with
Outstanding
Balance and AO
Code)

LOCATION
\\BDOI\For
Upload\CLGRN\Outstanding\Exception

FILENAME
AMMDDYYYYEC

Loans Fully Paid


Accounts

\\BDOI\Rejected Upload\CLGRN\Fully
Paid\Exception

BMMDDYYYYEC

Where:
CODE
A
B
MM
DD
YYYY
E
C

VALUE
CLG Loans (with Outstanding Balance and AO Code)
Loans Fully Paid Accounts
January to December
Day of the month file as uploaded
Year based on system date
Exception
001 to 100

12. System generation of display message after the CLG LOANS (with Outstanding Balance
and AO Code) and Loans Fully Paid Accounts. The system will prompt a display
message to the user informing that the upload of files had been completed.
3.1.2. UI Wireframe
Screen layouts will be provided in the next release of this document

3.1.3. Inputs and Outputs


UPLOADING OF FILES WINDOW

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

Page 15 of 22

Requirements Specification Document


CLG Renewal
Version 2.0

DATA ELEMENT

BEHAVIOR

FORMAT

Filename

Display

Varchar

File Location

Display

Varchar

Select

Tick box

Upload and
Match Files

Executable
button

Close

Executable
button

RANGE OF
VALUES

REMARKS
The system will
display the filename of
the upload file. Upload
files will be arranged
based on filename.
The system will
display the
location/path of the
upload file.
This will be
automatically ticked by
the system if two files
reflects that same
month in there
filename.
The system will upload
the file to the system.
The system will close
the upload window
screen.

CCOMPLETED UPLOAD DISPLAY MESSAGE

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

Page 16 of 22

Requirements Specification Document


CLG Renewal
Version 2.0

DATA ELEMENT

BEHAVIOR

Message

Display

OK

Executable
button

FORMAT

RANGE OF
VALUES

Varchar

REMARKS
The message that will appear
reflects the number of
records that have been
saved from the SL file to the
PIPELINE. Example: 500
records have been saved in
the PIPELINE.
The system will close the
display message.

3.1.4. Reports Specification


N/A
3.1.5. Business Requirements Mapping
ITEM #
BRM-RN-RID1-001

BRM-RN-RID1-002
BRM-RN-RID1-003

BRM-RN-RID1-004

BR REQUIREMENTS

FEATURES

User should be able to upload the


CLG LOANS (with Outstanding
Balance and AO Code) and Loans
Fully Paid Accounts.
The system should be able to
detect and validate if the upload
file is valid for uploading to staging.
The system should be able to
detect duplicate contents of the
upload files.

System detection on the location of


files.

The system should be able to


detect if a duplicate file is uploaded
to the system

System detection on the validity of


upload files.
System detection on the duplicate
contents of the CLG LOANS (with
Outstanding Balance and AO
Code) and Loans Fully Paid
Accounts.
System detection on duplicate files.

3.2. RID2 Updating of Pipeline module


This function provides a facility in the system that update records in the Pipeline module based on
the CLG LOANS (with Outstanding Balance and AO Code) and Loan Fully Paid Accounts that were

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

Page 17 of 22

Requirements Specification Document


CLG Renewal
Version 2.0

uploaded to the Staging table.


3.2.1. Features
1. System detection of account records in the Pipeline that will be updated. The system will
check accounts in the Pipeline module whose account status is In Process or Booked.
After records have been selected, the system will match the PN. Number of the account
record in the Pipeline as against the PN Number in the Staging table (which came from
the CLG LOANS (with Outstanding Balance and AO Code) and Loans Fully Paid Accounts
that were uploaded). If there is a matched, the following data fields in the Pipeline module
will be updated:
DATA FIELDS
Loan Amount Balance

Loan Balance Date

CASE
PN Number in the Pipeline =
PN number in the CLG
LOANS (with Outstanding
Balance and AO Code).
PN Number in the Pipeline =
PN number in the Loans
Fully Paid Accounts
PN Number in the Pipeline =
PN number in the CLG
LOANS (with Outstanding
Balance and AO Code).
PN Number in the Pipeline =
PN number in the Loans
Fully Paid Accounts

ICBS Officer

VALUE
Amount indicated in the data
column O/S Bal. (LCYE)

0
Date of the upload

Date indicated in the data


column Posting date
Officer (AO Code)

3.2.2. UI Wireframe
Screen layouts will be provided in the next release of this document
3.2.3.
N/A

Inputs and Outputs

3.2.4.
N/A

Reports Specification

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

Page 18 of 22

Requirements Specification Document


CLG Renewal
Version 2.0

3.2.5.

Business Requirements Mapping


ITEM #
BR REQUIREMENTS

BRM-RN-RID2-001

The system should be able to


update accounts records in the
Pipeline based on the upload
files

FEATURES
System selection of records based
on the account status (In Progress
or Booked) and matching by PN
Number in the Pipeline versus PN
Number in the upload files.

3.3. RID 3 Generation of Expiry List, Sanitation and Disposition of records


This function allows the user to generate list of expiring accounts from the Broker System that will be
included in the sanitation process which will eventually be placed in the various repositories
depending the sanitation rules that have been satisfied.
3.3.1. Features
1. System facility to allow the user to generate list of expiring accounts. Generation of the
list will be done through the Renewal module of the Broker System. User will be allowed
to generate that list based on the following filters: Market Segment, Product Line, Market
Segment and Product Line or All (all records regardless of the Market Segment and/or
Product Line will be included in the generation). The system will check if the EXPIRY
DATE of the insurance policies found in the Pipeline is within 120 days reckoned from
current or system date.
2. System facility to perform data sanitation and populate the repositories. The system will
create records in the repositories below as follows:
REPOSITORIES
For Renewal Matched

CONDITIONS

RMU

Expiring accounts with outstanding balance and


not AO Code is not RMU
Expiring accounts with PN Number that did not
match the PN Number in the CLG LOANS (with
Outstanding Balance and AO Code) or Loans Fully
Paid Accounts.
Expiring account with AO Code = RMU

Loans Fully Paid

Expiring Accounts with zero (0) balance

For Renewal Unmatched

Data retention in the above repositories will be one (1) year. After which, the system will
automatically delete the records. The one year period will be from the current date
counted backwards. To illustrate:
CURRENT DATE

ONE YEAR PERIOD

05/13/2016

05/13/2015

07/29/2017

07/29/2016

09//01/2018

09//01/2017

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

Page 19 of 22

Requirements Specification Document


CLG Renewal
Version 2.0

Data that will arise from the subsequent uploading will not supersede prior data
regardless if they have exactly the same values. To illustrate:
PRIOR UPLOADING
Record 1

SUBSEQUENT
UPLOADING
Record 1

TOTAL RECORDS
Record 1

Record 1

Record 1

Record 1

Record 1

Record 1

Record 1

Record 2

Record 2

Record 2

Record 2

Record 2

Record 2
Record 1
Record 1
Record 1
Record 2
Record 2

3. System facility to mark records in the repository. User will be allowed to indicate the
following status of records in the repository as follows:
REPOSITORIES
For Renewal
Matched
For Renewal
Unmatched

STATUS
Renew as is
Renew as is

IMPACT
All accounts in the repositories
marked as Renew as is will be
queued for Renewal Letter
Generation.

3.3.2. UI Wireframe
Screen layouts will be provided in the next release of this document
3.3.3. Inputs and Outputs
N/A
3.3.4. Reports Specification
N/A
3.3.5. Business Requirements Mapping
ITEM #
BRM-RN-RID3-001

BRM-RN-RID3-002

BR REQUIREMENTS
User should be able to
generate list of expiring
accounts based on defined
filters.
System should be able to
sanitized records based on

FEATURES
System facility to allow user to
generate list of expiring accounts
based on defined filters.
System facility that will sanitized
records based on defined rules and

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

Page 20 of 22

Requirements Specification Document


CLG Renewal
Version 2.0

predefined rules.

placing the records to appropriate


repositories.

3.4. RID Viewing of records in the repositories


This facility will allow the user to view contents of the repositories
3.4.1. Features
1. System facility to view and print contents of the repositories. User will be allowed to view
and print the contents of the following repositories:
REPOSITORIES

ACTION

FILTER

For Renewal Matched

View and Print

PN Number, Product Type, Officer Code

For Renewal Unmatched

View and Print

PN Number, Product Type, Officer Code

RMU

View and Print

PN Number, Product Type, Officer Code

Loans Fully Paid

View and Print

PN Number, Product Type

3.4.2. UI Wireframe
Screen layouts will be provided in the next release of this document
3.4.3. Inputs and Outputs
N/A
3.4.4. Reports Specification
N/A
3.4.5. Business Requirements Mapping
ITEM #
BR REQUIREMENTS
BRM-RN-RID4-001

2.

User should be able to view


and print contents of the
repositories

FEATURES
System facility to allow the user to
view and print contents of the
repositories

Risks, Issues, and Constraints


FUNCTIONAL
AREA
RID 1

TYPE
Risk

DESCRIPTION

MITIGATION/RESOLUTION

Filename and location of


upload files have not been
properly complied with the
user.

BDOI to ensure prescribed format


and standards have been properly
communicated to the Insurance
Company and to update the latter
of any changes in the upload
template
System will validate format of the

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

Page 21 of 22

Requirements Specification Document


CLG Renewal
Version 2.0

upload file.
RID 2

Constraints

Accuracy and completeness of


the matching process will
depend on the completeness
and correctness of the data in
upload files and Broker
system.

BDOI to call the attention of the


system owners for any data that
have
been
mishandled
as
evidenced by the extracted files.

RID 3

Risk

Data from the upload file may


not be aligned with the data
fields in the Pipeline module.

BDOI to discuss and ensure that


data fields and formats are
aligned with the requirements and
design of the Pipeline module

2.1. Design Constraints


The design of the matching and upload facility is highly dependent on the format and contents of the
upload files. Any changes on the upload file will impact the workability of the upload facility
2.2. Hardware and Software Constraints
The performance of the sanitation process is highly dependent on the specification of the data
server, workstation and the number of records that needs to be uploaded to the Pipeline module.
3.

Assumptions and Dependencies


o The contents of the CLG LOANS (with Outstanding Balance and AO Code) and Loans Fully
Paid Accounts. are complete and correct.
o The accuracy of the matching process is highly dependent on the completeness and
correctness upload files and the data in the Pipeline module.

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

Page 22 of 22