You are on page 1of 31

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.

Requirements Specification Document


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........................................................................................................... 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

Systems Requirements Document


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. 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

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

Systems Requirements Document


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

Requirements Specification Document

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.

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.

Systems Requirements Document


ICBS Upload
Version 0.01

2.3 Process Schematic / Process Flow


VALIDATION OF UPLOAD FILES AND LOADING TO STAGING AND ICBS TABLE
UPLOAD PROGRAM (ITO)

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
No
Compliant?
Yes

Staging
repository

Systems Requirements Document


ICBS Upload
Version 0.01

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

Systems Requirements Document


ICBS Upload
Version 0.01

PN NO./CIF MATCHING AND UPDATING PROCESS


BROKER SYSTEM
C

CIF No. in Pipeline


blank?

Yes

Copies CIF from


ICBS to CIF in
Pipeline

End

No
CIF in Broker = CIF in
ICBS?

No

Exception
List

Yes
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 will have a facility to upload the ICBS file manually in
case the scheduled uploading fails due to unforeseen events.
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

Systems Requirements Document


ICBS Upload
Version 0.01

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

Systems Requirements Document


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
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

Systems Requirements Document


ICBS Upload
Version 0.01

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/
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
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

Systems Requirements Document


ICBS Upload
Version 0.01

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
LEASING - 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

Systems Requirements Document


ICBS Upload
Version 0.01

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
Model Description
Model Year
Serial Number
Motor Number
Primary Color
FirstName
LastName
MiddleName
CIFname1
CIFname2
CIFname3
CIFname4
CIFname5
Employer Name
Employer Address
.
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

Systems Requirements Document


ICBS Upload
Version 0.01

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

Systems Requirements Document


ICBS Upload
Version 0.01

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

Systems Requirements Document


ICBS Upload
Version 0.01

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

Check for the data columns common to all market segment


Check the data column unique to a particular market segment. This should also
be included in the upload file.
Repeat the preceding steps for data columns unique to the other product codes.

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.

Systems Requirements Document


ICBS Upload
Version 0.01

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.

The specifications of the error file will be as follows:


CRITERIA
Format
Contents

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

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 filename convention will be


U20150330040000
4. Facility to upload ICBS file via MANUAL RUN. In the event that the scheduled uploading
of ICBS data FAILS due to unexpected errors, the user from the data center will have the
utility to upload the data manually. User will be prompted of the file that will be uploaded.
Refer to Figure 1 and 2 of this document.
5. System capability to generate error file for manual run. In the event that the MANUAL
RUN of data uploading FAILED, the system will generate an error file containing the error
message following the specifications mentioned in the section 3.1.1.4.
6. System capability to check 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 in the Broker system.
7. System validation if there are records in the Staging repository. The system will not
commence the uploading process if there are records remaining in the staging repository
caused by unforeseen errors. These should be disposed or removed before the incoming
ICBS file will be accepted by the system and uploaded to the Staging repository. Records

Systems Requirements Document


ICBS Upload
Version 0.01

that remained due to MATCHED PROMISSORY NOTE NUMBER (please refer to


3.2.1.1) will be deleted by the system since these are no longer needed and also to
accommodate incoming ICBS file that will be uploaded to the same repository. Please
note that uploading of ICBS data will be a recurring process. To enable succeeding
uploading of ICBS file, the Staging repository should not contain any data.

3.1.2 UI Wireframe
Figure 1

Figure 2

Systems Requirements Document


ICBS Upload
Version 0.01

3.1.3 Inputs and Outputs


DATA UPLOADING MENU
DATA
BEHAVIOR
ELEMENT
DATA
Executable
UPLOAD
button

FORMAT

REMARKS
Directs the system
administrator to the
DATA
UPLOADING
WINDOW.

DATA UPLOADING WINDOW


DATA
BEHAVIOR
ELEMENT
File
Display

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.

Directs the user


back to the DATA
UPLOAD MENU
screen

Systems Requirements Document


ICBS Upload
Version 0.01

3.1.4 Reports Specification


N/A
3.1.5 Business Requirements Mapping
ITEM #
BR REQUIREMENTS
BRM-ICBS-RID1-001
BRM-ICBS-RID1-002

BRM-ICBS-RID1-003

3.2

System 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 ICBS
repository.
User from the data center
should be able to upload ICBS
file manually in case the
scheduled run of upload file
fails.

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.

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 and arranged by the system to comply with the data format and requirements
will be uploaded to the ICBS repository in the Broker system. Data will be appended to
the ICBS repository; existing data that have been previously uploaded will not be
superseded. The system will check if the PROMISSORY NOTE NUMBER in the Staging
repository EXISTS in the ICBS repository. If YES, record will not be uploaded. The
system will perform the procedure mentioned in the section 3.2.1.2. Otherwise, the
system will transfer/append the record (with no duplicate PN. No.) to the ICBS repository.
To illustrate:
DAY

STAGING

100

200

ICBS

100
(Count
as of day
1)

VALIDATION

PROCEDURE

100 records have been


uploaded
from
the
staging repository.
100 records with o 100 records will not
PN. NO = PN NO
be
in
ICBS
transferred/appended
repository.
to ICBS repository
The other 100
records with no
duplicate PN. NO. will
be appended. This
will undergo
procedure mentioned

Systems Requirements Document


ICBS Upload
Version 0.01

400

200
(count as
of day 2)

200 records with o


PN. NO = PN NO
in
ICBS
repository
o

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

Systems Requirements Document


ICBS Upload
Version 0.01

Last Name

Equal

Equal

First Name

Equal

Equal

Middle Name

Equal

Equal

NUMBER of a record in the


ICBS repository against
Pipeline. If there is NO
MATCHED, the system will
compare the LAST NAME,
FIRST NAME and MIDDLE
NAME.
If
there
is
MATCHED, the system will
generate and exception list.

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

Systems Requirements Document


ICBS Upload
Version 0.01

The contents of the log file will be as follows:


CRITERIA
Format
Contents

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

Should not overwrite existing log file based on timestamp.

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

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

UI Wireframe

Figure 3

Systems Requirements Document


ICBS Upload
Version 0.01

Figure 4

Systems Requirements Document


ICBS Upload
Version 0.01

3.2.3

Inputs and Outputs

DATA UPLOADING MENU


DATA
BEHAVIOR
ELEMENT
View ICBS
Executable
Repository
button

FORMAT

RANGE OF VALUES

REMARKS
Directs the user to
the ICBS
REPOSITORY
WINDOW

Systems Requirements Document


ICBS Upload
Version 0.01

ICBS REPOSITORY WINDOW


DATA
BEHAVIOR
FORMAT
ELEMENT
Market
Dropdown
Segment

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.

Systems Requirements Document


ICBS Upload
Version 0.01

3.2.4
N/A

Reports Specification

3.2.5

Business Requirements Mapping


ITEM #
BR REQUIREMENTS

BRM-ICBS-RID2-001
BRM-ICBS-RID2-002

3.3

System should be able to


transfer data from staging to
ICBS repository
System should be able to
generate log files after data
from staging have been
transferred
to
ICBS
repository.

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.

Matching and updating of CIF in the Pipeline module


This function provides a facility in the system that 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
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

Systems Requirements Document


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

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

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

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

Systems Requirements Document


ICBS Upload
Version 0.01

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.

Systems Requirements Document


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

3.1.5.

Business Requirements Mapping


ITEM #
BR REQUIREMENTS

FEATURES

Systems Requirements Document


ICBS Upload
Version 0.01

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
information
from
ICBS
repository
The system should be able to
relate supplied CIF number in
the Client Information against
record
in
the
Account
Information of the Pipeline
module (for data extraction).

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.