RSD ICBS v3

BDO Insurance Brokers, Inc.
(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.

ICBS
Version 0.01
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
Please refer to sign-off sheet
Reference Documents
Document Name
Powerpoint material presented to BDOI last April 10, 2014
Business Requirements ICBS Integration for Broker System
Classification: GENPACT Internal All rights reserved. Copyright (2008-2014)
Version
Date Updated
1.0
2
4/10/2014
9/25/2014
Systems Requirements Document

ICBS
Version 0.01
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........................................................................................................... 20
3.1.5 Business Requirements Mapping........................................................................................ 20
3.2 Uploading of data from Staging to ICBS repository....................................................................20
3.2.1 Features.............................................................................................................................. 21
3.2.2 UI Wireframe....................................................................................................................... 24
3.2.3 Inputs and Outputs............................................................................................................... 27
3.2.5 Business Requirements Mapping........................................................................................ 28
3.3 Matching and updating of CIF in the Pipeline module................................................................29
3.3.1.Features............................................................................................................................... 29
3.3.2.UI Wireframe........................................................................................................................ 32
3.3.4.Inputs and Outputs............................................................................................................... 32
3.3.5.Business Requirements Mapping........................................................................................ 32
4. RISKS, ISSUES, AND CONSTRAINTS................................................................................................. 33
4.1 DESIGN CONSTRAINTS........................................................................................................... 33
4.2 HARDWARE AND SOFTWARE CONSTRAINTS......................................................................33
5. ASSUMPTIONS AND DEPENDENCIES...............................................................................................33

ICBS Upload
Version 0.01
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. Outstanding loan, Customer Information Number) that will be used by the different
modules of the BDOI Broker System. 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
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 list of any known and potential risks, issues, and constraints that
may hinder or delay the completion and delivery of the system.
Assumptions and
Dependencies
Provides stipulations and factors that may affect the requirements stated in
this document.
Functional Description

ICBS Upload
Version 0.01
1.4
Definition of Terms and Acronyms

TERMS
DEFINITION
BDOI
Banco De Oro Insurance
CIF NO.
Customer Information File Number
ICBS
Integrated Computerized Banking System
ICBS File
Refer to list of records that have been extracted from the ICBS
PN No.
Promissory Note Number
RSD
Staging Repository
Repository of records where checking and validation in terms of data format

and structure will be performed by the system before these are uploaded to
the ICBS repository.
Repository of records that have been checked and validated in the Staging
repository.
Unit responsible for managing the bank data of BDO and its subsidiaries
ICBS Repository
ITO Data Center
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 to UPLOAD 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 with the system requirements. The next stage will be to UPLOAD THE VALIDATED DATA
FROM THE STAGING TO THE ICBS repository. These procedures will be performed by the BDO Data
Center authorized personnel.

ICBS Upload
Version 0.01
2.3 Process Schematic / Process Flow

VALIDATION OF UPLOAD FILES AND LOADING TO STAGING AND ICBS TABLE
ITO DATA CENTER
BROKER SYSTEM
Start
Arranges data according to

defined formats and structure.
Uploads files to the

Broker System
Checks if upload file is

compliant with the predefined
standards and format
Compliant?
Y
Staging
repository

ICBS Upload
Version 0.01
BROKER SYSTEM
A
Matches PN No, Customer Name from

Staging repository against PN No,
Customer Name and Date of Birth in the
ICBS repository
Matched?
Updates Loan Amount

Balance
and
Loan
Balance Date (of PN
No) in ICBS repository
ICBS repository
N
Same PN No. but different Customer
name?
Uploads record
ICBS repository
to
Matches PN No. and

Customer Name from
ICBS
repository
against PN No. and
Client Name (Last
Name, First Name
and Middle Name) in
Pipeline.
Y
Exception
List
End
End
Matched?
Y
Updates Loan Amount
Balance,
Loan
Balance Date, ICBS
Officer Code of the
record in the Pipeline

ICBS Upload
Version 0.01
CIF UPDATING PROCESS

BROKER SYSTEM
End
D
N
CIF No. in Pipeline
blank?
CIF No. differs but Client name (ICBS) =

Client name (Pipeline)?
CIF No. (ICBS) = CIF No. (Pipeline) but

Client name is not equal in Pipeline?
Y
Y
Updates CIF No. of
the
record
in
Pipeline
Exception
List
Exception
List
End
End
End
2.4 Interfaces with Users

The uploading of ICBS data to the Broker System will be managed by the BDO Data Center. The
operator from the Data Center may view the contents of the staging and ICBS repositories to check or
investigate data related problems that may have occurred during the uploading process through the
sequel server scripts. User from the data center can upload again the ICBS file in case after errors
have been corrected.
3. Functional Description
3.1
Uploading of ICBS data to the Staging Repository

This function provides a facility in the system that will upload and validate the compliance of the
ICBS files with the defined system data structure and format requirements before these are
uploaded to the ICBS repository. This process will ensure that only valid ICBS files are uploaded to
the system.

ICBS Upload
Version 0.01
3.1.1 Features
1. System facility to upload ICBS files. Personnel from ITO Data Center will have the
facility to upload the ICBS data to the STAGING repository. Uploading will be done at 10
PM DAILY subject to future changes by the concerned units. The system will check if the
ICBS upload file conforms to the required filename and location. Otherwise, user from
the data center will not be able to upload the ICBS file. The following are the different
ICBS files that will be uploaded to the Staging repository:
FILE
CLG Home
CLG Auto
Leasing Home
Leasing Auto
Combank
Corbank
FILENAME
ABCMMDDYYYYX
ABCMMDDYYYYX
ABCMMDDYYYYX
ABCMMDDYYYYX
ABCMMDDYYYYX
ABCMMDDYYYYX
WHERE:
CODE
A
B
C
MM
DD
YYYY
X
VALUE
BDOI
CLG = CLG, LEA = Leasing, COM = Combank, COR = Corbank
A = Auto, H = Home
01 to 12 (January to December)
1st to last day of the month
Year
01 -99
Below is the proposed location of ICBS files before and after uploading.
STATUS
For upload
LOCATION
\\BDOI\For upload\ICBS
Uploaded
\\BDOI\Uploaded\ICBS
Rejected
\\BDOI\Rejected\ICBS
DESCRIPTION
Location where files that will be
uploaded to the system will be placed by
the user.
Location of files after these has 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.
Locations of files that have not been
uploaded to the system due to noncompliance with the conditions prior to
uploading (e.g. Missing data columns,
Invalid file extension format).

ICBS Upload
Version 0.01
2. System checking on the uploading of file based on the date. To ensure that the contents
of the ICBS repository is based on latest transactions, the system will check if the ICBS
file (per file type) is the recent file extracted based on date incorporated in the filename.
There should be no other files with prior dates that have not been uploaded. To achieve
this, the system will keep logs of ICBS files that have been uploaded to the system.
Below is an illustrative explanation.
ICBS FILE
BDOICLGA0706201501
BDOICLGA0708201501
BDOICLGA0710201501
BDOICLGA0707201501
BDOICLGA0709201501
VALIDATION
First to be uploaded
Third to be uploaded
Last to be uploaded
Second to be uploaded
Fourth to be uploaded
In the above example, the user should not be allowed to upload BDOICLGA0710201501
ahead of the other files because this file contains the recent transactions being the last to
be extracted. Otherwise, the contents of the ICBS repository will not contain the recent
transactions from the ICBS source system.
3. 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
Last Principal Payment Amt

ICBS Upload
Version 0.01
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

ICBS Upload
Version 0.01
Park Description
Officer Code
AO Name
Collateral Code
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
Home Email
Business Email
Date of Birth/
Model Description
Model Year
Serial Number
Motor Number
Primary Color
FirstName
LastName
MiddleName
CIFname1
CIFname2
CIFname3
CIFname4
CIFname5
Employer Name
Employer Address
LEASING - HOME
Note Number
Short Name
Customer Name
Loan Type
Product Type
Product Description
Customer Number
Amount Financed
O/S Balance

ICBS Upload
Version 0.01
Branch Number
Branch Desc
Booking Date
Maturity Date
Park Branch
Park Description
Officer Code
AO Name
Collateral Code
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
Home Email/
Business Email
Date of Birth
REL Userfield
Appraised Value
Appraisal Date
House Name
House Number
Street/Subdivision
City/FirstName
LastName
MiddleName
CIFname1
CIFname2
CIFname3
CIFname4
CIFname5
Employer Name
Employer Address
LEASING - AUTO
Note Number
Short Name

ICBS Upload
Version 0.01
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
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
Home Email
Business Email
Date of Birth
Model Description
Model Year
Serial Number
Motor Number
Primary Color
FirstName
LastName
MiddleName
CIFname1
CIFname2
CIFname3
CIFname4
CIFname5
Employer Name
Employer Address

ICBS Upload
Version 0.01
.
COMBANK
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
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
Home Email
Business Email
Date of Birth
REL Userfield
Appraised Value
Appraisal Date
House Name
House Number
Street
Subdivision
City
FirstName

ICBS Upload
Version 0.01
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
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
Home Email
Business Email
Date of Birth
REL Userfield

ICBS Upload
Version 0.01
Appraised Value
Appraisal Date
House Name
House Number
Street
Subdivision
City
FirstName
LastName
MiddleName
CIFname1
CIFname2
CIFname3
CIFname4
CIFname5
Employer Name
Employer Address
In the preceding list of data columns per ICBS file, there is no data field for LOAN
BALANCE DATE. This data column will be introduced or added as a new data field in the
Staging repository to capture the balance date based on the DATE OF THE UPLOAD
FILE. This information will be included when the system uploads the data from this
repository to the ICBS repository. The same information will be used to update the LOAN
BALANCE DATE in the Pipeline module of the Broker System.
4. System capability to generate error file for unsuccessful upload. In cases that errors will
occur during uploading, 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. INVALID DATA COLUMNS). The proposed filename of the
error file will be as follows:
WHERE:
FORMAT
X
Y
Z
A
DESCRIPTION
U = Unsuccessful
Filename of the file that was uploaded
Time file was generated HH:MM:SS format.
Date file was generated in YY-MM-DD format.
The specifications of the error file will be as follows:

CRITERIA
Format
Contents
DESCRIPTION
Text file
Status: 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 (HH:MM:SS)
User Id

ICBS Upload
Version 0.01
Occurrence
Records were not successfully uploaded to the staging or

ICBS repositories.
Manner of appending
Should not overwrite existing log file based on timestamp.
Location
\\BDOI\For Upload\ICBS\Unsuccessful
An example of a filename generated based on the above file naming convention will be
UBDOICLGA0706201507:00:0007072015
5. System capability to check the validity of the ICBS data in the Staging repository. Data
that was uploaded to the staging repository will undergo validation and data management
process before these are uploaded to the ICBS repository. This is to ensure that the data
that have been uploaded to the staging repository is in compliance with the data format
and structure of the ICBS repository of the Broker system.
3.1.2 UI Wireframe
DATA UPLOADING MENU

ICBS Upload
Version 0.01
DATA UPLOADING WINDOW
3.1.3 Inputs and Outputs

DATA UPLOADING MENU
DATA
BEHAVIOR
ELEMENT
DATA
Executable
UPLOAD/ICBS button
DATA
FORMAT
RANGE OF VALUES
REMARKS
Directs the system
administrator to the
DATA
UPLOADING
WINDOW.

ICBS Upload
Version 0.01
DATA UPLOADING WINDOW

DATA
BEHAVIOR
ELEMENT
File
Display
Alpha numeric
Refers to the
filename of the
ICBS data that
will be uploaded
Location
Display
Alpha numeric
Select
Check box
Select All
Check box
Upload
Executable
button
Close
Executable
button
Refers to the
location where
the ICBS file is
stored for
uploading.
Selects a
particular files for
uploading
Selects all files
for uploading
Uploads data to
the Staging
repository
Directs the user
back to the DATA
UPLOAD MENU
screen
FORMAT
RANGE OF
VALUES
REMARKS
3.1.4 Reports Specification

N/A
3.1.5 Business Requirements Mapping
ITEM #
BR REQUIREMENTS
BRM-ICBS-RID1-001
BRM-ICBS-RID1-002
User should be able to upload

ICBS file to the Staging
repository.
System should be able to
validate the ICBS upload file
before uploading to the Staging
repository.
FEATURES
System capability upload ICBS
file to the Staging repository.
System capability to validate
ICBS upload files and its contents
before uploading to Staging
repository.

ICBS Upload
Version 0.01
3.2
Uploading of data from Staging to ICBS repository

This function provides a facility in the system that will upload data that have been validated in the
Staging to the ICBS repository. Necessary data validation in terms of format and structure has been
performed by the system at this stage.
3.2.1 Features
1. System facility to upload data from Staging to ICBS repository. Data that have been
validated by the system to be compliant with the data format and requirements will be
uploaded to the ICBS repository of the Broker system. Below are the rules on the
uploading of data:
To illustrate:
CONDITION
PROCEDURE
NO DUPLICATE PN NO AND
CUSTOMER NAME ( LAST
NAME, MIDDLE NAME AND
FIRST NAME) in the ICBS
repository
Data will be uploaded/appended to the ICBS

repository
WITH DUPLICATE PN NO AND

CUSTOMER NAME ( LAST
NAME, MIDDLE NAME AND
FIRST NAME) in the ICBS
repository
LOAN BALANCE AND LOAN BALANCE DATE of

the same record will be updated in the ICBS
repository. The Loan Balance will be taken from the
upload file while the Loan balance date will be
based on the date of the upload file.
UNIQUE PN NO. BUT

DUPLICATE CUSTOMER NAME
(LAST NAME, MIDDLE NAME
AND FIRST NAME) in the ICBS
repository
Data will not be uploaded. Record will be included

in the exception report that will be generated by the
system.
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
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 again a MATCHED, the system
will update the LOAN AMOUNT
BALANCE, LOAN BALANCE DATE
AND OFFICER CODE in the Pipeline
based on the information from the

ICBS Upload
Version 0.01
ICBS repository.
Promissory
Note
The
system
will
match
the
PROMISSORY NOTE NUMBER of a
record in the ICBS repository against
Last Name
Not Equal
Not Equal Pipeline. If there is a MATCHED, the
First Name
Not Equal
Not Equal system will compare the LAST NAME,
FIRST NAME and MIDDLE NAME. If
Middle Name
Not Equal
Not Equal there is NO MATCHED, the system will
generate an exception report.
3. System capability to generate an Exception report. The system will generate the report
per process based on the following conditions:
PROCESS
Uploading of records
from the Staging to the
ICBS repository
Updating of LOAN
AMOUNT BALANCE,
LOAN BALANCE DATE
AND OFFICER CODE
in the Pipeline
Updating of CIF in
Pipeline
Equal
Equal
CONDITION
PN NO. is unique in both Staging and ICBS repository BUT
DUPLICATE CUSTOMER NAME (LAST NAME, MIDDLE
NAME AND FIRST NAME) in the Staging and ICBS
repository.
PROMISSORY NOTE NUMBER in ICBS repository IS
EQUAL to the PROMISSORY NOTE NUMBER in Pipeline
but CUSTOMER NAME (LAST NAME, FIRST NAME and
MIDDLE NAME) in ICBS repository IS NOT EQUAL to the
LAST NAME, FIRST NAME and MIDDLE NAME in Pipeline.
PROMISSORY NOTE NUMBER in ICBS repository IS NOT
EQUAL to the PROMISSORY NOTE NUMBER in Pipeline
but CUSTOMER NAME (LAST NAME, FIRST NAME and
MIDDLE NAME) in ICBS repository IS EQUAL to the LAST
NAME, FIRST NAME and MIDDLE NAME in Pipeline.
The system will automatically assign a filename (XYZ) and store the Exception report to a
predefined directory based on the table below:
FORMAT
X
Y
Z
A
DESCRIPTION
E = Exception
Filename of the file that was uploaded
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. An example of a filename generated based on
the above file naming convention will be EBDOICLGA0706201507:00:0007072015
4. System capability to generate message regarding status of the uploading. The user will
be prompted of the following system message depending on the outcome of the
uploading process:

ICBS Upload
Version 0.01
UPLOAD STATUS
Successful
o
o
o
Unsuccessful (entire o
file was rejected by the o
system)
With Exceptions (File o

was accepted by the o
system. However, the
contents were partially
uploaded. Others were o
not uploaded due to
errors detected by the
system).
o
CONTENTS
File uploaded
Status of the
upload;
Number of
records
uploaded
Filename;
Reason/s
for
the
unsuccessful
uploading (e.g.
incorrect data
columns)
PROPOSED MESSAGE CONTENTS

200
records
from
BDOICLGA0706201501have
been
successfully uploaded to the ICBS
repository.*
Filename;
Number of
record
uploaded;
Number of
records that
were not
uploaded;
Exceptions in
the upload file
(e.g. PN No.
with duplicate
customer
name)
100
records
from
BDOICLGA0706201501
were
successfully uploaded to the ICBS
repository. 100 were not uploaded due to
Promissory Note Numbers with duplicate
Customer Name. Exception report was
generated
and
saved
to
\\BDOI\Exception\Personal
Accident
Insurance *
File BDOICLGA0706201501 cannot be

uploaded to the ICBS repository due to
incorrect data columns.*
* - Message will vary depending on the outcome of the upload process.

5. System capability to generate log files for SUCCESSFUL and UNSUCCESSFUL transfer
of data from the Staging to the ICBS repository. The system will assign a filename (XYZ)
and generate log files to a predefined location based on the table below:
WHERE:
FORMAT
X
Y
Z
A
DESCRIPTION
S = Successful , U = Unsuccessful
File that was uploaded

ICBS Upload
Version 0.01
AND
STATUS
Successful uploading
Unsuccessful uploading
LOCATION
\\BDOI\For Upload\ICBS\Successful
\\BDOI\For Upload\ICBS\Unsuccessful
The contents of the log file will be as follows:

CRITERIA
DESCRIPTION
Format
Text file. An example of a filename generated based on the

above
file
naming
convention
will
be
SBDOICLGA0706201507:00:0007072015
Contents
Occurrence
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
After records were not successfully uploaded to repositories
Manner of appending
Should not overwrite existing log file based on timestamp.
6. 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:
PARAMETERS
o
o
o
o
o
o
CLG - Home
CLG - Auto
Leasing - Home
Leasing - Auto
Combank
Corbank
SUB-PARAMETERS
DATA
User can search either

any of the following:
o PN Number
o Last Name
o First Name
Information that will be shown will

be based on the data columns for
o CLG Home
o CLG - Auto
o Leasing - Home
o Leasing - Auto
o Combank
o Corbank
7. System display of history of uploaded files. User will be able to VIEW records of files that
have been uploaded to the system. Below are the proposed parameter and data columns
that will be available to the user.
DATA
Parameter
Data columns
Format
DESCRIPTION
o By user
o Month
o Year
o Date (uploaded) From
o Date (uploaded) To
o Filename
o Date uploaded
o Uploaded by
o Total number of record
Open office or excel

ICBS Upload
Version 0.01
3.2.2
UI Wireframe
DATA UPLOADING CONFIRMATION MESSAGE
VIEW ICBS REPOSITORY MENU

ICBS Upload
Version 0.01
VIEW ICBS REPOSITORY PARAMETERS
VIEW UPLOADED FILES MENU

ICBS Upload
Version 0.01
VIEW UPLOADED FILES SCREEN

ICBS Upload
Version 0.01
3.2.3
Inputs and Outputs
DATA UPLOADING CONFIRMATION MESSAGE

DATA ELEMENT
BEHAVIOR
Message
Display
Close
Executable
button
FORMAT
RANGE OF
VALUES
REMARKS
Closes the DATA

UPLOADING
CONFIRMATION
MESSAGE.
VIEW ICBS REPOSITORY MENU

DATA ELEMENT
View ICBS
Repository
BEHAVIOR
FORMAT
Executable
button
VIEW ICBS REPOSITORY PARAMETERS
RANGE OF VALUES
REMARKS
Directs the user to
the ICBS
REPOSITORY
WINDOW

ICBS Upload
Version 0.01
DATA ELEMENT
ICBS File
BEHAVIOR
Dropdown
FORMAT
Promissory Note
Number
Last Name
Data entry
Numeric
Data entry
Character
First Name
Data entry
Character
Clear All
Executable
button
Search
Executable
button
View
Executable
button
Close
Executable
button
RANGE OF VALUES
o CLG - Home
o CLG - Auto
o Leasing - Home
o Leasing - Auto
o Combank
o Corbank
REMARKS
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.

ICBS Upload
Version 0.01
VIEW UPLOADED FILES MENU

DATA ELEMENT
View uploaded files
BEHAVIOR
FORMAT
RANGE OF
VALUES
Executable
button
REMARKS
Directs the user to the
VIEW UPLOADED
FILES SCREEN
VIEW UPLOADED FILES SCREEN

DATA ELEMENT
BEHAVIOR
FORMAT
RANGE OF
VALUES
Per user
All user
User
Dropdown
Month
Dropdown
January to
December
Year
Dropdown
Year (e.g. 2015,

2016, 2017, etc.)
Date (uploaded)
From
Date (uploaded) To
Data entry
MM/DD/YYYY
Data entry
MM/DD/YYYY
Clear All
Executable
button
View
Executable
button
Close
Executable
button
3.2.4
N/A
Reports Specification
REMARKS
Shows users that
have access to
upload files.
Limited to one
month per viewing
Limited to one year
Clears parameters
indicated by the
user.
Display data based
on parameters
defined by the
user.
Closes the VIEW
UPLOAD FILES
SCREEN.

ICBS Upload
Version 0.01
3.2.5
Business Requirements Mapping

ITEM #
BR REQUIREMENTS
BRM-ICBS-RID2-001
BRM-ICBS-RID2-002
BRM-ICBS-RID2-003
BRM-ICBS-RID2-004
3.3

transfer data from staging to
ICBS repository
generate log files after data
from staging have been
transferred
to
ICBS
repository.
update the Loan Amount
Balance, Balance Date and
Office Code in the Pipeline
based on the ICBS data that
have been uploaded.
User should be able to view
files that have been uploaded
to the system.
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.
System capability to automatically
update the Loan Amount Balance,
Balance Date and Office Code in the
Pipeline based on the ICBS data that
have been uploaded.
Facility to allow the user to view files
that have been uploaded to the
system.
Matching and updating of CIF in the Pipeline module

This function provides a facility in the system that will match and update CIF Number in the Broker
System based on the information available in the ICBS repository.
3.1.1.
Features
1. System capability to match and upload CIF Number from the ICBS repository against CIF
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. To illustrate:
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

ICBS Upload
Version 0.01
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
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
Pipeline (Populated CIF field)

CIF
PN
LAST NAME
1
1111
Abancan
4444
Mendez
5555
Gomez
FIRST NAME
Jerome
Ana
Ana
MIDDLE NAME
Monteja
Mondejar
Co
Pipeline
CIF
c.
PN
PN
1111
4444
5555
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 (in the Pipeline), the system will retain said
data.
ICBS repository
CIF
1
2
3
PN
1111
4444
5555
Pipeline
CIF
PN
444
555
666
LAST
NAME
Abancan
Mendez
Gomez
LAST
NAME
Lao
Co
Mendez
FIRST NAME
Jerome
Ana
Ana
FIRST NAME
Jerome
Martha
Liza
MIDDLE NAME
Monteja
Mondejar
Co
MIDDLE NAME
Sevilla
Ang
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. An
exception report will be generated by the system containing the discrepancies (refer
to section 3.2.1.3).
ICBS repository
CIF
1
PN
1111
LAST
NAME
Abancan
FIRST NAME
Jerome
MIDDLE NAME
Monteja

ICBS Upload
Version 0.01
2
3
Pipeline
CIF
1
2
3
ICBS repository
CIF
1
2
3
Pipeline
CIF
1
2
3
4444
5555
PN
1111
4444
5555
PN
1111
4444
5555
PN
6666
4444
5555
Buenviaje
Gomez
LAST
NAME
Antolina
Mendez
Gomez
LAST
NAME
Abancan
Buenviaje
Gomez
LAST
NAME
Abancan
Mendez
Gomez
Martha
Liza
FIRST NAME
Mark
Ana
Ana
FIRST NAME
Jerome
Martha
Liza
FIRST NAME
Jerome
Ana
Ana
Sevilla
Ong
MIDDLE NAME
Sandejas
Mondejar
Co
MIDDLE NAME
Monteja
Sevilla
Ong
MIDDLE NAME
Monteja
Mondejar
Co
e. If one client record contains several accounts with PN. No and during matching, any
of the accounts falls into the exceptions mentioned in the preceding sections, an
exception report (refer to section 3.2.1.3) will be generated containing the
discrepancies notwithstanding that some of the accounts with PN No. matched the
records in the ICBS repository.
ICBS repository
CIF
1
1
1
Pipeline
CIF
1
1
3
PN
1111
4444
5555
PN
1111
4444
5555
LAST
NAME
Abancan
Buenviaje
Gomez
LAST
NAME
Abancan
Buenviaje
Gomez
FIRST NAME
Jerome
Martha
Liza
FIRST NAME
Jerome
Martha
Liza
MIDDLE NAME
Monteja
Sevilla
Ong
MIDDLE NAME
Monteja
Sevilla
Ong
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.

ICBS Upload
Version 0.01
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

ICBS Upload
Version 0.01
3.1.5.
Business Requirements Mapping

ITEM #
BR REQUIREMENTS
BRM-ICBS-RID3-001
BRM-ICBS-RID3-002
4. Risks, Issues, and Constraints

FUNCTIONAL
TYPE
AREA
RID 1
Risk
The system should be able to

update CIF field in the Pipeline
module based on the CIF
information
from
ICBS
repository
The system should be able to
relate or attach supplied CIF
number
in
the
Client
Information against record in
the Account Information of the
Pipeline module.
FEATURES
System capability that will update
CIF field based on validation
procedures.
System capability to relate supplied
CIF number in the Client Information
against record in the Account
Information of the Pipeline module
(for data extraction).
DESCRIPTION
MITIGATION/RESOLUTION
Erroneous data or those not

recognized by the Pipeline
module may be included and
uploaded in the ICBS table.
Data are validated based on the

acceptable and recognized values
in the Staging table.
4.1 Design Constraints

The design of the upload facility is highly dependent on the structure and format of the ICBS file. Any
changes to this file will impact the workability of the upload facility.
4.2 Hardware and Software Constraints
The performance of the uploading process is highly dependent on the specification of the data
server, number of records from ICBS table and frequency of uploading. The
5. Assumptions and Dependencies
o The accuracy of the matching process is highly dependent on the completeness and correctness
of the ICBS upload files.
o Correctness, completeness and accuracy of the contents and compliance to the format and
contents of data columns in the upload file will be handled by ICBS source system.
Duplicate records in the upload files will be handled by the ICBS source system.

RSD ICBS v3

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

RSD ICBS v3

Caricato da

Copyright:

Formati disponibili

BDO Insurance Brokers, Inc.

Requirements Specification Document

Please refer to sign-off sheet

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

Systems Requirements Document

Systems Requirements Document

Risk, Issues, and

Provides the system objective, functional overview, process flow,

Systems Requirements Document

Definition of Terms and Acronyms

Banco De Oro Insurance

Customer Information File Number

Integrated Computerized Banking System

Promissory Note Number

Requirements Specification Document

Repository of records where checking and validation in terms of data format

Systems Requirements Document

2.3 Process Schematic / Process Flow

Arranges data according to

Uploads files to the

Checks if upload file is

Systems Requirements Document

Matches PN No, Customer Name from

Updates Loan Amount

Matches PN No. and

Systems Requirements Document

CIF UPDATING PROCESS

CIF No. differs but Client name (ICBS) =

CIF No. (ICBS) = CIF No. (Pipeline) but

2.4 Interfaces with Users

Uploading of ICBS data to the Staging Repository

Systems Requirements Document

Systems Requirements Document

Systems Requirements Document

Last Principal Payment Dt

Systems Requirements Document

Systems Requirements Document

Systems Requirements Document

Systems Requirements Document

Systems Requirements Document

Systems Requirements Document

The specifications of the error file will be as follows:

Systems Requirements Document

Records were not successfully uploaded to the staging or

Should not overwrite existing log file based on timestamp.

Systems Requirements Document

DATA UPLOADING WINDOW

3.1.3 Inputs and Outputs

Systems Requirements Document

DATA UPLOADING WINDOW

3.1.4 Reports Specification

User should be able to upload

Systems Requirements Document

Uploading of data from Staging to ICBS repository

Data will be uploaded/appended to the ICBS

WITH DUPLICATE PN NO AND

LOAN BALANCE AND LOAN BALANCE DATE of

UNIQUE PN NO. BUT

Data will not be uploaded. Record will be included

Systems Requirements Document

Systems Requirements Document

With Exceptions (File o

PROPOSED MESSAGE CONTENTS