Professional Documents
Culture Documents
(BDOI)
Requirements Specification Document
ICBS Upload to BDOI Broker System
v0.01
Creation Date: February 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.
Document History
Version
Date
0.01
February 23,
2015
Author
Jeffrey Oliveros
Description
Document creation
Reviewed By
Approved By
Conchita Valena
Distribution List
Name
Role
Department/Unit
Reference Documents
Document Name
Powerpoint material presented to BDOI last April 10, 2014
Business Requirements ICBS Integration for Broker System
Version
Date Updated
1.0
2
4/10/2014
9/25/2014
TABLE OF CONTENTS
1. INTRODUCTION..................................................................................................................................... 4
1.1 Purpose........................................................................................................................................ 4
1.2 Audience...................................................................................................................................... 4
1.3 Scope........................................................................................................................................... 4
1.4. Definition of Terms and Acronyms............................................................................................... 5
2. 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
3. FUNCTIONAL DESCRIPTION................................................................................................................ 8
3.1 Uploading of ICBS data to the Staging Repository.......................................................................8
3.1.1 Features................................................................................................................................. 9
3.1.2 UI Wireframe....................................................................................................................... 18
3.1.3 Inputs and Outputs.............................................................................................................. 19
3.1.4 Reports Specification........................................................................................................... 19
3.1.5 Business Requirements Mapping........................................................................................ 19
3.2 Uploading of data from Staging to ICBS repository....................................................................20
3.2.1 Features.............................................................................................................................. 20
3.2.2 UI Wireframe....................................................................................................................... 23
3.2.3 Inputs and Outputs............................................................................................................... 24
3.2.4 Reports Specification........................................................................................................... 25
3.2.5 Business Requirements Mapping........................................................................................ 25
3.3 Matching and updating of CIF in the Pipeline module................................................................26
3.3.1.Features............................................................................................................................... 26
3.3.2.UI Wireframe........................................................................................................................ 29
3.3.3 Reports Specification........................................................................................................... 29
3.3.4.Inputs and Outputs............................................................................................................... 29
3.3.5.Business Requirements Mapping........................................................................................ 29
4. RISKS, ISSUES, AND CONSTRAINTS................................................................................................. 29
4.1 DESIGN CONSTRAINTS........................................................................................................... 29
4.2 HARDWARE AND SOFTWARE CONSTRAINTS......................................................................29
5. ASSUMPTIONS AND DEPENDENCIES...............................................................................................30
1. Introduction
This document outlines the requirements needed to create a facility in the BDOI Broker System that
will upload the data from the Integrated Computerized Banking System. These data will serve as a source
of information (e.g. reference for outstanding loan, Customer Information Number) that will be used by the
different modules of the BDOI Broker System. Although, there are two stages in the uploading process,
the first is EXTRACTION of data from the source system which is the Integrated Computerized Banking
System and the second part is the UPLOADING of the extracted data to the BDOI Broker System, this
document will only cover the second stage. The extraction process will be discussed in another
requirements document.
1.1
Purpose
The Requirements Specification document presents the functions that will be provided to BDOI
for the uploading of data from the Integrated Computerized Banking System to the BDOI Brokerage
System. Customer approval of this document signifies acceptance of the contents and authorization to
proceed with the development phase.
This document is intended to establish the required functionalities, capture potential screen layouts,
and identify the environments in which the system will operate. However, based on design constraints
and other technical limitations, the actual functionalities and screen designs may differ from those
presented in this document.
1.2
Audience
This documents intended audiences are the project stakeholders and project participants from
both BDO Insurance, BDO IT Development - Insurance and GENPACT.
1.3
Scope
This document covers the following sections:
SECTION NAME
Overview
PURPOSE
Assumptions and
Dependencies
Provides a list of factors that will affect the requirements stated in this
document.
Functional Description
1.4
DEFINITION
BDOI
CIF NO.
ICBS
ICBS File
Refer to list of records that have been extracted from the ICBS
PN No.
RSD
Staging Repository
ICBS Repository
2. Overview
2.1 System Objectives
The objective of uploading the data from ICBS to the Broker system is for BDOI to have an
instant view of its clients that have existing loans with BDO bank that will serve as source of
information (e.g. such as reference to determine if policy is for renewal) for the different modules in the
system and business processes of BDOI .
2.2 Functional Overview
Extracted data from the ICBS (as mentioned in the preceding section, this process will covered by
a separate requirements document) will be uploaded to the BDOI Broker system. There will be two
parts; the first part will be the UPLOADING OF THE DATA TO A STAGING repository where system
validation and data management will be performed to ensure that the contents of the upload files are
valid and in accordance to the system requirements. The next stage will be to UPLOAD THE
VALIDATED FROM THE STAGING TO THE ICBS repository. These procedures will be performed by
the BDO Data Center personnel.
BROKER SYSTEM
Start
Staging
repository
BROKER SYSTEM
Checks if PN No. in
Staging is existing in the
ICBS repository
Existing?
No
Transfers records to
the ICBS repository
Yes
Matches PN No and client name
(Last Name, First Name and
Middle Name) from ICBS
repository against PN No. and
client name (Last Name, First
Name and Middle Name) in
Pipeline
Matched?
ICBS
repository
Yes
No
Same PN No but
different client name
Updates
Loan
Amount
Balance, Loan Balance
Date and ICBS Officer Code
of the Pipeline record (PN
No. matched the PN No. in
the ICBS table).
Yes
B
No
C
Yes
End
No
CIF in Broker = CIF in
ICBS?
No
Exception
List
Yes
End
uploaded to the ICBS repository. This process will ensure that only valid ICBS files are uploaded to
the system.
3.1.1 Features
1. System capability to check the DATA COLUMNS of ICBS upload file. The system will
validate the completeness of the data columns. In case some are not present, the
system will reject the ENTIRE upload file.
CLG HOME
Note Number
Short Name
Customer Name
Loan Type
Product Type
Product Description
Customer Number
Amount Financed
O/S Balance
Branch Number
Branch Desc
Booking Date
Maturity Date
Park Branch
Park Description
Officer Code
AO Name
Collateral Code
Collateral Description
Collateral Item Number
Short Collateral Desc
Collateral Description 1
Collateral Description 2
Collateral Description 3
Last Principal Payment Amt
Last Principal Payment Dt
Last Interest Payment Amt
Last Interest Payment Dt
Name Address Line 1
Name Address Line 2
Name Address Line 3
Name Address Line 4
Name Address Line 5
Name Address Line 6
Home Phone Number
Business Phone Number
Cellular Phone Number
Home Email
Business Email
Date of Birth
REL Userfield
Type of Building Design
Appraised Value
Appraisal Date
House Name
House Number
Street
Subdivision
City
FirstName
LastName
MiddleName
CIFname1
CIFname2
CIFname3
CIFname4
CIFname5
Employer Name
Employer Address
Projected O/S Balance
Projected O/S Balance Anniversary Date
CLG AUTO
Note Number
Short Name
Customer Name
Loan Type
Product Type
Product Description
Customer Number
Amount Financed
O/S Balance
Branch Number
Branch Desc
Booking Date
Maturity Date
Park Branch
Park Description
Officer Code
AO Name
Collateral Code
Collateral Description
Collateral Item Number
Short Collateral Desc
Collateral Description 1
Collateral Description 2
Collateral Description 3
Last Principal Payment Amt
Last Principal Payment Dt
Last Interest Payment Amt
Last Interest Payment Dt
Name Address Line 1
Name Address Line 2
Name Address Line 3
Park Description
Officer Code
AO Name
Collateral Code
Collateral Description
Collateral Item Number
Short Collateral Desc
Collateral Description 1
Collateral Description 2
Collateral Description 3
Last Principal Payment Amt
Last Principal Payment Dt
Last Interest Payment Amt
Last Interest Payment Dt
Name Address Line 1
Name Address Line 2
Name Address Line 3
Name Address Line 4
Name Address Line 5
Name Address Line 6
Home Phone Number
Business Phone Number
Cellular Phone Number
Home Email
Business Email
Date of Birth
REL Userfield
Type of Building Design
Appraised Value
Appraisal Date
House Name
House Number
Street
Subdivision
City
FirstName
LastName
MiddleName
CIFname1
CIFname2
CIFname3
CIFname4
CIFname5
Employer Name
Employer Address
CORBANK
Note Number
Short Name
Customer Name
Loan Type
Product Type
Product Description
Customer Number
Amount Financed
O/S Balance
Branch Number
Branch Desc
Booking Date
Maturity Date
Park Branch
Park Description
Officer Code
AO Name
Collateral Code
Collateral Description
Collateral Item Number
Short Collateral Desc
Collateral Description 1
Collateral Description 2
Collateral Description 3
Last Principal Payment Amt
Last Principal Payment Dt
Last Interest Payment Amt
Last Interest Payment Dt
Name Address Line 1
Name Address Line 2
Name Address Line 3
Name Address Line 4
Name Address Line 5
Name Address Line 6
Home Phone Number
Business Phone Number
Cellular Phone Number
Home Email
Business Email
Date of Birth
REL Userfield
Type of Building Design
Appraised Value
Appraisal Date
House Name
House Number
Street
Subdivision
City
FirstName
LastName
MiddleName
CIFname1
CIFname2
CIFname3
CIFname4
CIFname5
Employer Name
Employer Address
Since the above data columns per market segment (please note that all product
codes per market segment have the same data columns) will only be contained in one
ICBS file, the procedure for checking the completeness will be as follows:
o
o
o
To illustrate:
CLG HOME
Data column 1
Data column 2
Data column 3
Data column 4
CLG AUTO
Data column 1
Data column 2
CORBANK
Data column 1
Data column 2
COMBANK
Data column 1
Data column 2
Data column 4
In validating, data column 1 and 2 will be checked by the system since these are all
common to the four (4) market segments (CLG HOME, CLG AUTO, CORBANK and
COMBANK). Apart from these data columns, data columns 3 and 4 will also be validated
because these are unique to CLG HOME and CORBANK.
2. System capability to upload ICBS file. The system will automatically upload the ICBS
data to the STAGING repository. Uploading will start at 10 PM DAILY. The system will
check if the ICBS upload file conforms to the required filename and location. Otherwise,
the system will not commence the uploading process. Below is the proposed filename
and location of files before and after uploading the process:
FILE
ICBS
ICBS
STATUS
For uploading
Uploaded
LOCATION
\\BDOI\For Upload\ICBS
\\BDOI\Processed\ICBS
FILENAME
XMMDDYYYY
XMMDDYYYY
WHERE:
CODE
X
MM
DD
YYYY
VALUE
X = ICBS
01 to 12 (January to December)
1st to last day of the month
Year
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.
3. System capability to generate error file for unsuccessful scheduled run. In the event that
the SCHEDULED RUN of data extraction FAILED due to unforeseen events, the system
will GENERATE an error file (in XYZ format) containing the error message (e.g. DATA
UPLOADING FAILED) and the possible cause or causes of the errors. (e.g.
CORRUPTED FILE). The proposed filename of the error file will be as follows:
WHERE:
FORMAT
X
Y
Z
DESCRIPTION
U = Unsuccessful
Date file was generated in YY-MM-DD format.
Time file was generated HH:MM:SS format.
Occurrence
DESCRIPTION
Text file
Status: Successful or Unsuccessful
Remarks: Indicate error/s found (if unsuccessful)
Cause: Error that cause the upload process to fail (if
unsuccessful)
Date (MM/DD/YYYY)
Time stamp
User Id (this will appear only if uploading was done manually)
After records were not successfully uploaded to the staging or
ICBS repositories.
Manner of appending
Location
\\BDOI\For Upload\ICBS\Unsuccessful
3.1.2 UI Wireframe
Figure 1
Figure 2
FORMAT
REMARKS
Directs the system
administrator to the
DATA
UPLOADING
WINDOW.
FORMAT
Location
Display
Alpha numeric
Select
Check box
Select All
Upload
Check box
Executable
button
Executable
button
Close
RANGE OF VALUES
Alpha numeric
RANGE OF
VALUES
REMARKS
Refers to the
filename of the
ICBS data that is
uploaded through
scheduled run.
Refers to the
location where
the ICBS file is
stored for
uploading.
BRM-ICBS-RID1-003
3.2
FEATURES
System capability upload ICBS
file to the Staging repository.
System capability to validate
extracted data in the Staging
repository prior to uploading to the
ICBS repository.
System facility to allow user from
the data center to upload ICBS
file manually.
STAGING
100
200
ICBS
100
(Count
as of day
1)
VALIDATION
PROCEDURE
400
200
(count as
of day 2)
in 3.2.1.2. Records
will be deleted
afterwards.
100 records with no
duplicate will be
appended to the
ICBS repository.
100 records (from day
2) that have no
duplicate PN. No. will
undergo the
procedure in 3.2.1.2.
The same procedure
mentioned in the
preceding will be
repeated for the
succeeding uploads.
400
(count as
of day 3)
2. System capability to update records in the Pipeline based on the ICBS data. The system
will automatically update the following fields in the Pipeline based on the following
procedure:
DATA
Promissory
Note
ICBS
REPOSITORY
Equal
PIPELINE
Equal
Last Name
Equal
Equal
First Name
Equal
Equal
Middle Name
Equal
Equal
Promissory
Note
Not Equal
Not Equal
PROCEDURE
The system will match the
PROMISSORY
NOTE
NUMBER of a record in the
ICBS repository against
Pipeline.
If
there
is
MATCHED, the system will
compare the LAST NAME,
FIRST NAME and MIDDLE
NAME. If there is a
MATCHED, the system will
update the LOAN AMOUNT
BALANCE, LOAN BALANCE
DATE AND OFFICER CODE
in the Pipeline based on the
data
(LOAN
AMOUNT
BALANCE, LOAN BALANCE
DATE
AND
OFFICER
CODE) from the ICBS
repository.
The system will match the
PROMISSORY
NOTE
Last Name
Equal
Equal
First Name
Equal
Equal
Middle Name
Equal
Equal
3. System capability to generate an Exception List. The system will generate and Exception
list based on the following conditions:
PROCESS
Updating of LOAN
AMOUNT BALANCE,
LOAN BALANCE DATE
AND OFFICER CODE
in the Pipeline
Updating of CIF in
Pipeline
CONDITION
PROMISSORY NOTE NUMBER in ICBS repository IS NOT
EQUAL against PROMISSORY NOTE NUMBER in Pipeline
but LAST NAME, FIRST NAME and MIDDLE NAME in ICBS
repository IS EQUAL to the LAST NAME, FIRST NAME and
MIDDLE NAME in Pipeline.
PROMISSORY NOTE NUMBER in ICBS repository IS NOT
EQUAL against PROMISSORY NOTE NUMBER in Pipeline
but LAST NAME, FIRST NAME and MIDDLE NAME in ICBS
repository IS EQUAL to the LAST NAME, FIRST NAME and
MIDDLE NAME in Pipeline BUT
o There CIF is indicated in all or several CIF fields and
o There is discrepancy in all or some of the CIF data.
The system will automatically assign a filename (XYZ) and store the same to a
predefined directory based on the table below:
FORMAT
X
Y
Z
DESCRIPTION
E = Exception
Date file was generated in YY-MM-DD format.
Time file was generated HH:MM:SS format.
LOCATION
\\BDOI\For
Upload\ICBS\Exception
The contents of the Exception List will consist of the SAME DATA COLUMNS in the ICBS
repository where the records came from.
4. System capability to generate log file for SUCCESSFUL and UNSUCCESSFUL transfer
of data from the Staging to the ICBS repository. The system will assign a filename
(XYZ)for the log file and store to a predefined location based on the table below:
WHERE:
FORMAT
X
Y
Z
DESCRIPTION
S = Successful , U = Unsuccessful
Date file was generated in YY-MM-DD format.
Time file was generated HH:MM:SS format.
AND
STATUS
Successful uploading
Unsuccessful uploading
LOCATION
\\BDOI\For Upload\ICBS\Successful
\\BDOI\For Upload\ICBS\Unsuccessful
DESCRIPTION
Occurrence
Text file
Status: Successful or Unsuccessful
Remarks: Indicate error/s found (if unsuccessful)
Cause: Error that cause the upload process to fail (if
unsuccessful)
Date (MM/DD/YYYY)
Time stamp
User Id (this will appear only if uploading was done manually)
After records were not successfully uploaded to repositories
Manner of appending
5. System facility to view records in the ICBS repository. User will have a facility to view
records that have been uploaded to the repository. The parameters are listed in the table
below:
o
o
o
o
o
o
3.2.2
PARAMETERS
SUB-PARAMETERS
DATA
CLG - Home
CLG - Auto
Leasing - Home
Leasing - Auto
Combank
Corbank
UI Wireframe
Figure 3
Figure 4
3.2.3
FORMAT
RANGE OF VALUES
REMARKS
Directs the user to
the ICBS
REPOSITORY
WINDOW
Promissory
Note Number
Last Name
Data entry
Numeric
Data entry
Character
First Name
Clear All
Data entry
Executable
button
Character
Search
Executable
button
View
Executable
button
Close
Executable
button
RANGE OF VALUES
o
o
o
o
o
o
REMARKS
CLG - Home
CLG - Auto
Leasing - Home
Leasing - Auto
Combank
Corbank
Erases data
indicated in the
search parameters
Displays data
defined in the
search parameters.
Displays data
based on filtered
parameter.
Directs the user
back to the DATA
UPLOADING
MENU.
3.2.4
N/A
Reports Specification
3.2.5
BRM-ICBS-RID2-001
BRM-ICBS-RID2-002
3.3
FEATURES
System capability to transfer data
from staging to ICBS repository
System capability to generate log
files for successful and unsuccessful
transfer of data from staging to ICBS
repository.
Features
1. System capability to match and upload CIF Number from the ICBS repository against
record in the Pipeline. Below is the manner on how the system will match and update the
CIF number of records in the Pipeline module.
a. The system will check if PN No., Last Name, First Name and Middle Name from
ICBS repository matched the PN No., Last Name, First Name and Middle Name in
the Pipeline.
ICBS repository
CIF
1
2
3
Pipeline
CIF
PN
1111
222
333
PN
1111
4444
5555
LAST
NAME
Abacan
Buenviaje
Gomez
LAST
NAME
Abacan
Mendez
Gomez
FIRST NAME
Jerome
Martha
Liza
FIRST NAME
Jerome
Ana
Ana
MIDDLE NAME
Monteja
Sevilla
Ong
MIDDLE NAME
Monteja
Mondejar
Co
b. If there is a matched in the PN No., Last Name, First Name and Middle Name, the
system will copy the CIF No. from ICBS repository to the Pipeline.
ICBS repository
CIF
1
2
3
PN
1111
222
333
LAST
NAME
Abancan
Buenviaje
Gomez
FIRST NAME
MIDDLE NAME
Jerome
Martha
Liza
Monteja
Sevilla
Ong
LAST NAME
Abancan
Mendez
Gomez
FIRST NAME
Jerome
Ana
Ana
MIDDLE NAME
Monteja
Mondejar
Co
FIRST NAME
Jerome
Ana
Ana
MIDDLE NAME
Monteja
Mondejar
Co
Pipeline
CIF
PN
1111
4444
5555
If there are data indicated in the all or several CIF fields (there are currently five (5)
fields in the ICBS upload file) in the ICBS repository, below is the procedure on the
updating of CIF number:
o
o
c.
Validate and compare CIF data. If all are the same, the system will update
CIF field in the Pipeline;
If some or all of the CIF differs, the system will not update the CIF field in
Pipeline despite that there was a matched in the Promissory Note Number,
Last Name and Middle name. The system will generate and Exception List
(refer to section 3.2.1.3)
If there is no exact matched in the PN No., Last Name, First Name and Middle
Name, the system will not update the CIF Number field in the Pipeline module. If
there is an existing CIF Number data, the system will retain said data.
ICBS repository
CIF
1
2
3
PN
1111
4444
5555
Pipeline
CIF
PN
444
555
LAST
NAME
Abancan
Mendez
Gomez
LAST
NAME
Lao
Co
FIRST NAME
Jerome
Ana
Ana
FIRST NAME
Jerome
Martha
MIDDLE NAME
Monteja
Mondejar
Co
MIDDLE NAME
Sevilla
Ang
666
Mendez
Liza
Ong
d. If there is a matched in the PN No. but Last Name, First Name or Middle Name in
ICBS repository is different from the but Last Name, First Name or Middle Name in
the Pipeline, the system will not update the CIF Number in the Pipeline and will
generate and Exception list (refer to section 3.2.1.3)
ICBS repository
CIF
1
2
3
Pipeline
CIF
1
2
3
PN
1111
4444
5555
PN
1111
4444
5555
LAST
NAME
Abancan
Buenviaje
Gomez
LAST
NAME
Antolina
Mendez
Gomez
FIRST NAME
Jerome
Martha
Liza
FIRST NAME
Mark
Ana
Ana
MIDDLE NAME
Monteja
Sevilla
Ong
MIDDLE NAME
Sandejas
Mondejar
Co
e. If there is a matched in the Last Name, First Name or Middle Name but PN No. in
ICBS repository is different from the PN. No. in the Pipeline, the system will not
update the CIF Number in the Pipeline and will generate an exception list (refer to
section 3.2.1.3)
ICBS repository
CIF
1
2
3
Pipeline
CIF
1
2
3
PN
1111
4444
5555
PN
6666
4444
5555
LAST
NAME
Abancan
Buenviaje
Gomez
LAST
NAME
Abancan
Mendez
Gomez
FIRST NAME
Jerome
Martha
Liza
FIRST NAME
Jerome
Ana
Ana
MIDDLE NAME
Monteja
Sevilla
Ong
MIDDLE NAME
Monteja
Mondejar
Co
2. System capability to relate supplied CIF Number against client account in the Pipeline
module. The system will relate the CIF number of client name based on the following
procedure. This is in compliance with the information that will be provided to the
Customer Consolidator System, a BDO system used to come up with a single customer
profile from different customer data available to the bank.
a. The system will match the client id from the account information as against
records in the customer information in the Pipeline module.
Client Information
CIF
1
2
3
LAST NAME
Abancan
Buenviaje
Gomez
CIF
1
1
1
INVOICE
001
023
044
3456
7891
FIRST NAME
Jerome
Martha
Liza
MIDDLE NAME
Monteja
Sevilla
Ong
PN. NO.
1111
2346
5690
1257
9806
CLIENT ID
XXXX
CLIENT ID
XXXX
XXXX
XXXX
YYYY
ZZZZ
The report that will be submitted to ITD-Compliance for uploading to the Customer
Consolidator System will reflect that client JEROME MONTEJA ABCAN has three
(3) policy accounts in BDOI.
CIF
1
LAST NAME
Abancan
CIF
1
1
1
FIRST NAME
Jerome
INVOICE
001
023
044
MIDDLE NAME
Monteja
PN. NO.
1111
2346
5690
CLIENT ID
XXXX
CLIENT ID
XXXX
XXXX
XXXX
A consolidated list of BDOI clients with CIF number and their corresponding BDOI
transactions will be submitted to ITD Compliance for uploading to the Customer
Consolidator system. Complete data requirements and format required ITD
Compliance will be handled in a separate project.
3.1.2. UI Wireframe
N/A
3.1.3. Reports Specification
N/A
3.1.4. Inputs and Outputs
N/A
3.1.5.
FEATURES
BRM-ICBS-RID3-001
BRM-ICBS-RID3-002
Risk
DESCRIPTION
MITIGATION/RESOLUTION