RSD Leasing - v1.0

BDO Insurance Brokers, Inc.
(BDOI)
Requirements Specification Document
BDOI Leasing
v1.0
Creation Date: April 2014
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.

BDOI Leasing
Version 1.0
Document History
Version
Date
Author
Description
0.01
April 24, 2014
Jeffrey
Oliveros
Document creation
1.0
August 5, 2014
Jeffrey
Oliveros
Baselined/Approved
RSD
Reviewed By
Conchita
Valena
Approved By
BDOI
Distribution List
Name
Role
Department/Unit
Please refer to sign-off sheet
Reference Documents
Document Name
BDOI Business Requirements for BDOI Leasing
Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)
Version
Date Updated
1.0
4/3/2014
Page 2 of 27

BDOI Leasing
Version 1.0
TABLE OF CONTENTS
1.
2.
3.
4.
5.
6.
Introduction.......................................................................................................................................... 4
1.1.
Purpose................................................................................................................................. 4
1.2.
Audience............................................................................................................................... 4
1.3.
Scope.................................................................................................................................... 4
1.4.
Definition of Terms and Acronyms......................................................................................... 5
Overview.............................................................................................................................................. 5
2.1.
System Objectives................................................................................................................ 5
2.2.
Functional Overview.............................................................................................................. 5
2.3.
Process Schematic / Process Flow.......................................................................................6
2.4.
Interfaces with Users............................................................................................................. 9
Functional Description.......................................................................................................................... 9
3.1.
RID1 Validation and uploading of files to staging tables........................................................9
3.1.1. Features................................................................................................................................ 9
3.1.2. UI Wireframe....................................................................................................................... 11
3.1.3. Inputs and Outputs.............................................................................................................. 11
3.1.4. Reports Specification.......................................................................................................... 12
3.1.5.
Business Requirements Mapping........................................................................................ 12
3.2.
RID2 Matching and uploading to repositories......................................................................12
3.2.1. Features.............................................................................................................................. 12
3.2.2. UI Wireframe....................................................................................................................... 18
3.2.5. Business Requirements Mapping........................................................................................ 19
3.3.
RID3 Viewing and transfer of records to other repository/Pipeline......................................19
3.3.1. Features.............................................................................................................................. 19
3.3.2. UI Wireframe....................................................................................................................... 20
3.4.
RID4 Other Requirements................................................................................................... 22
3.4.1. Features.............................................................................................................................. 22
3.4.2. Reports specification........................................................................................................... 22
Risks, Issues, and Constraints........................................................................................................... 24
4.1. Design Constraints..................................................................................................................... 24
4.2. Hardware and Software Constraints...........................................................................................24
Assumptions and Dependencies........................................................................................................ 24
APPENDIX......................................................................................................................................... 25
6.1.Business Rules............................................................................................................................ 25
6.2. Access Matrix............................................................................................................................. 25
Page 3 of 27

BDOI Leasing
Version 1.0
1. Introduction
This document outlines the requirements needed to create a facility within the BDOI Brokerage system
that will allow BDOI Leasing to check and monitor if all leased and mortgage properties under BDOI
Leasing and Finance Incorporation have been insured.
1.1. Purpose
The Requirements Specification document presents the functions that will be provided to BDOI for the
uploading of accounts from the Finance Product Management System and Integrated Computerized
Banking System based on the Business Requirements document submitted to GENPACT. Customer
approval of this document signifies acceptance of the content and authorization to proceed with the
development of the system.
It should be clearly noted that this document is meant to demonstrate the desired functionality, capture
potential screen layouts, and identify the environments in which the system must operate. However,
based on design constraints and other technical limitations, the delivered functionality and screen
designs may differ somewhat from the formats presented in this document.
The purpose of this document is to clearly demonstrate GENPACT understands the business
requirements submitted by BDOI and to serve as basis for the design and development of the module.
1.2. Audience
This documents intended audiences are the project stakeholders and project participants from both
BDOI and GENPACT. It is written to demonstrate the GENPACTs due diligence and understanding of
the functional requirements.
1.3. Scope
This document covers the following sections:
SECTION NAME
Overview
Functional Description
Risk, Issues, and
Constraints
Assumptions and
Dependencies
Appendix
PURPOSE
Provides the system objective, functional overview, process flow,
interfaces with databases and users, and production environment in
which the project will be installed and maintained
Provides a detailed description of the system architecture. Include
architecture diagrams, data structure diagrams, or other similar
information as required.
Provides a list of any known risks, issues, and constraints that would
hinder, delay, or cause serious system delivery impacts to the project.
Provides a list of the factors that affect the requirements stated in the
RSD. These factors are any changes to the design constraints that
can affect the requirements.
This section may include the business rules, report and file format,
and other attachment that may be used as a reference in further
understanding the contents of some of the sections of the RSD.
Page 4 of 27

BDOI Leasing
Version 1.0
1.4. Definition of Terms and Acronyms

TERMS
2.
DEFINITION
BDOLF
BDO Leasing and Finance
BDOI
Banco De Oro Insurance
BDOLFI
BDO Leasing and Finance Incorporation
FPMS
Finance Product Management System
ICBS
Integrated Computerized Banking System
IMD
Insurance Monitoring Database
PN No.
Promissory Note Number
Repository
Also know as Bucket in the system database where records from the FPMS
and ICBS will be saved based on the result of the matching process
RSD
Staging table
Repository of uploaded contents from the FPMS and ICBS prior to matching
and uploading to different repositories.
Overview
2.1. System Objectives
Currently, insurance coverage of properties leased or mortgaged under BDOI Leasing and Finance
are checked and monitored manually using an IMD which is created in excel file. Details of new
leases or mortgages by clients are encoded in this database. The objective of the new facility is to
allow BDOI-Leasing to upload information from the FPMS and ICBS to the BDOI Brokerage System
to check and monitor if properties that have been leased and mortgaged are insured through BDOI
or directly through the Insurance Company.
2.2. Functional Overview
Data from the FPMS and ICBS source systems will be uploaded to the brokerage system.
Information indicated on these files will be matched against the data in the Pipeline (Submitted
Policy and Booked Accounts) to check if properties rendered by clients of BDOLF as collateral have
been insured.
Page 5 of 27

BDOI Leasing
Version 1.0
2.3. Process Schematic / Process Flow

VALIDATION OF UPLOAD FILES AND LOADING TO STAGING TABLES
EXTRACTION
PROGRAM
BDOI LEASING
BROKERAGE SYSTEM
Arranges
dataor
Start FPMS
Uploads
to defined
according
ICBS
formats and
computes for hash
total of records
Executes
scheduled
extraction
MATCHING AND UPLOADING TO REPOSITORIES
and loads B
FPMS and
BROKERAGE SYSTEM
ICBS data to
Hash total
predefined
= Record
location
count?
Y
Staging
Staging tables
tables
Page 6 of 27

BDOI Leasing
Version 1.0
Checks required
data columns and
mandatory entries
Complete?
Y
Matches FPMS/ICBS with
the Submitted Policy and
Booked Accounts
(Pipeline)
Discrepancy in
unit description
and client
name?
Matched?
N
Insurance
Required?
Y
Y
N
C
VIEW AND TRANSFER OF RECORDS FROM/TO REPOSITORY/PIPELINE

BDOI LEASING
BROKERAGE SYSTEM
Page 7 of 27

BDOI Leasing
Version 1.0
Except for the

MATCHED
ACCOUNTS,
Matched
Matched Accounts
Accountsmoves
record
Uninsured
List
Uninsuredfrom/to
List other
repository/Pipeline
No
No Insurance
Insurance Required
Required List
List
N
Move to
Pipeline?
Y
Pipeline
Pipeline
End
2.4. Interfaces with Users

The uploading of FPMS and ICBS data will be done through an upload facility/module in the BDOI
Brokerage System. Viewing, printing and transfer of accounts in the repository will also be done
through a module in the system. Right and access of the users to upload and delete data from
staging, match and upload to repositories, view and generate reports from the repositories will be
controlled through the security features of the system.
Page 8 of 27

BDOI Leasing
Version 1.0
3.
Functional Description
3.1. RID1 Validation and uploading of files to staging tables
This function provides a facility in the system that will validate the compliance of FPMS and ICBS
upload files with the defined standards and format. The upload program will arrange the data from
the flat file through a temporary table in the system to ensure that the format and contents complies
with the requirements before these are uploaded to the staging tables. Hash total versus record
count will be checked by the system to ensure that all records are readable before these are
matched with the Pipeline records and uploaded to the repositories.
3.1.1. Features
1. Facility to allow user to upload FPMS or ICBS (FIG. 1)
2. System detection on the type and location of files to be uploaded. The system will detect
the type and location of files to be uploaded to staging tables through the UPLOAD FILE
LOCATION MAINTENANCE TABLE that will be available in the BDOI Brokerage System.
FILE
FPMS
STATUS
For uploading
LOCATION
\\BDOI\For upload\\Leasing\FPMS
FILENAME
XMMDDYYYY
FPMS
Uploaded
\\BDOI\Processed\\Leasing\FPMS
XMMDDYYYY
ICBS
For uploading
\BDOI\For upload\\Leasing\ICBS
XMMDDYYYY
ICBS
Uploaded
\\BDOI\Processed\Leasing\ICBS
XMMDDYYYY
X = FPMS or ICBS, MM = Month (January to December), DD = 1 st up to the last day of the

month and YYYY = current year
FOR UPLOAD folder pertains to file that have not been uploaded to the system.
PROCESSED refers to files that have been uploaded to the system. Files that have been
matched and uploaded to the repositories will be automatically moved by the system from
the FOR UPLOAD folder to the PROCESSED folder.
Files will be placed in the path defined in the system to be detected by the system (FIG. 2)
Page 9 of 27

BDOI Leasing
Version 1.0
3. System validation on the correctness and readability of the contents of the upload file
through validation of HASH TOTAL versus RECORD COUNT. If there is a discrepancy on
the results of the validation, the system will reject the entire upload file.
4. System checking on duplicate records. The system checks if duplicate records are
included in the same upload file or on succeeding uploads. The system uses the first
record that had been uploaded to the repository to restrict succeeding records bearing
the same information from being saved in the repositories. Duplicate records will be
saved in the EXCEPTION LIST repository. To illustrate:
FILENAME
SAVING
FPMS04302014
FPMS04302014
FPMS05312014
FPMS06302014
1st
2nd
3rd
4th
COLUMN
1
X
X
X
X
COLUMN
2
X
X
X
X
COLUMN
3
RESULT
X
X
X
X
Considered as original
Considered as duplicate
5. System detection on duplicate upload files. The system will record the file name of the
upload file to a registry table inside the database to ensure that no duplicate files will be
uploaded to the system. It is presumed that upload of files will be done on a monthly basis;
time stamp will not be part of the validation for duplicate file name. Thus, uploading of files
will only be done once a day because of the validation on the date. To illustrate
Page 10 of 27

BDOI Leasing
Version 1.0
FILENAME
FPMS040120141:35 pm
FPMS040120141:35 pm
FPMS053120141:35 pm
FPMS063020141:35 pm
REMARKS
Considered as duplicate although with different time stamp
because the system will only validate based on the file name
( FPMS04012014)
Not duplicate
Not duplicate
3.1.2. UI Wireframe
FIG. 1
Page 11 of 27

BDOI Leasing
Version 1.0
3.1.3.
Inputs and Outputs
DATA ELEMENT
BEHAVIOR
FORMAT
RANGE OF
VALUES
REMARKS
SELECT
Tick Box
PROCESS FILE
Executable Button
DATE UPLOADED
Display
Varchar
Refers to the date

file was uploaded
by the user.
FILE LOCATION
Display
Varchar
Refers to the
path/location
defined in the
system where files
for upload will be
stored.
3.1.4.
N/A
3.1.5.
Reports Specification
Business Requirements Mapping

ITEM #
BR REQUIREMENTS
BRM-LS-RID1-001
BRM-LS-RID1-002
BRM-LS-RID1-003
BRM-LS-RID1-004
User should be able to indicate the

path of the upload file.
User should be able to select the
type of file (FPMS or ICBS) to be
uploaded
The system should be able to
detect and validate if the upload file
is valid for uploading to staging
detect if a duplicate file is uploaded
in the system
FEATURES
System detection on the source of
upload files.
System detection on the type of
upload file.
System detection on the validity of
upload files. System prompts
display message to the user of
valid and invalid upload files.
System detection on duplicate files.
Page 12 of 27

BDOI Leasing
Version 1.0
3.2. RID2 Matching and uploading to repositories

This function provides a facility in the system that will match the records from the staging tables to
the Pipeline and uploading these records based on the results of the matching to the different
repositories.
3.2.1. Features
1. System validation on completeness of data columns in the upload file. The list of required
data columns per upload file can be found in the table below:
2.
FPMS
Account Name
Account Officer
Address
Amount Insured
Amount Insured
Basic Premium
Birthdate
Booking Date
Branch
Color
Contact Number
Contact Person
Expiry Date
Facility
Inception Date
Insurance
Company
Maturity Date
Motor Number
OB
Plate No.
PN No.
Policy No
Premium
Remarks
Serial Number
TCT No.
Total Premium
Unit Description
ICBS
Account Name
Account Officer
Address
Amount Insured
Amount Insured
Basic Premium
Birthdate
Booking Date
Branch
Color
Contact Number
Expiry Date
Inception Date
Insurance Company
Maturity Date
Motor Number
OB
Plate No.
PN No.
Policy No
Premium
Remarks
Serial Number
TCT No.
Total Premium
Unit Description
System default on mandatory entries

required by Pipeline. Below is the list of
defaults for the mandatory entries of
Pipeline. For the DEFAULT values
pertains to the information that will be
supplied by the system when FPMS or
ICBS files are uploaded while the
SOURCE column refers to the values that
will be copied by the system depending on
the source of the upload file.
Page 13 of 27

BDOI Leasing
Version 1.0
PIPELINE
Account Type
Assured
Bank Branch
Bank Officer
Bank Referror
BDOI Account Officer
Business Origin
Commission
Commission Rate
Date Referred
Expiry Date
Inception Date
Line of Insurance
Package
Policy Currency
Premium
Premium Rate
Product Type
Request for Survey

Risk Account Detail
Risk Location
Tax Information
Total Sum Insured
Transaction Type
Type of Entry:
Fleet /Non-Fleet,
Single/Multiple
Location,
Group/Individual
DEFAULT VALUES
FPMS
SOURCE
ICBS
SOURCE
Leased
Account Name
Branch
Account Officer
Account Name
Branch
Account Officer
Expiry Date
Inception Date
Expiry Date
Inception Date
Sum Insured
Sum Insured
Pending finalization of
names in drop down
list
TL
Leasing
N/A
N/A
Date file was
uploaded
Not ticked
Disabled because
Leased was not ticked
Get value of product
type
Disable
Peso
Motor = Motor
Number and Serial
Number, Equipment =
Serial Number, Serial
Number and TCT
Number = Fire
N/A
Motor = Motor
Number and Serial
Number, Equipment =
Number and TCT
Number = Fire
Motor = Motor
Number and Serial
Number, Equipment =
Number and TCT
Number = Fire
N/A
New Business
Single
Page 14 of 27

BDOI Leasing
Version 1.0
COMPLIANCE DISPLAY MESSAG

The system will proceed with matching and uploading based on the based on the rule
below
CONDITION
Incomplete data columns
ACTION
Reject entire upload file
Missing mandatory entries > 90% of the

total number of records
Missing mandatory entries < 5% of the
total number of records
Reject entire upload file

Generate Exception List Report and
upload data with complete entries
3. System matching of data uploaded from FPMS and ICBS against Pipeline. The system will
match the data indicated on the following columns from FPMS and ICBS against
PIPELINE.
FPMS/ICBS
Account Name
REMARKS
Value on the Account
Name column of
FPMS/ICBS will be
concatenated to match
First Name, Last Name,
Middle Name
PIPELINE
First Name
Last Name
Middle Name
Motor Number
Plate No.
Serial Number
TCT No.
Unit Description
Motor Number
Plate No.
Serial Number
TCT No.
Unit Description
To illustrate: If a certain CLIENT A availed of a loan and rendered his car as collateral or
security to the loan, the motor number (A1261061N14B16AC) indicated in the MOTOR
NUMBER column of the FPMS or ICBS upload file will be compared to the MOTOR
NUMBER data in the Pipeline. In matching records, the system will disregard any special
characters and spaces that were included in the MOTOR NUMBER, SERIAL NUMBER,
TCT NUMBER and PLATE NUMBER. Please refer to the example below:
FPMS
SERIAL NUMBER
A***256HI9
HO9000 34GH*
G567$#45GN90
PIPELINE
SERIAL NUMBER
A256HI9
HO900034GH
G56745GN90
VALIDATION
Matched
Matched
Matched
Page 15 of 27

BDOI Leasing
Version 1.0
After the system had completed the matching process, it will upload records to the
different repositories based on the conditions as follows:
Page 16 of 27

BDOI Leasing
Version 1.0
REPOSITORY
MATCHED
ACCOUNTS
CONDITIONS
ASSURED NAME (Staging) = LAST
NAME, FIRST NAME, MIDDLE
NAME (Pipeline)
AND
REMARKS
Data in this repository will
be retained for one (1)
year. Beyond this period,
data will be automatically
purged by the system.
MOTOR NUMBER (Staging) =

MOTOR NUMBER (Pipeline) OR
SERIAL NUMBER (Staging) =
SERIAL NUMBER (Pipeline) OR
TCT NO. (Staging) = TCT NO.
(Pipeline) OR
PLATE NO. (Staging) = PLATE NO.
(Pipeline)
UNINSSURED
LIST
NO
INSURANCE
REQUIRED
EXCEPTION
LIST
MOTOR NUMBER (Staging) not

equal to MOTOR NUMBER
(Pipeline) OR
SERIAL NUMBER (Staging) not
equal to SERIAL NUMBER (Pipeline)
OR
TCT NO. (Staging) not equal to TCT
NO. (Pipeline) OR
PLATE NO. (Staging) not equal to
PLATE NO. (Pipeline)
Records FPMS or ICBS have no value
(blank) on the COLLATERAL column.
ASSURED NAME (Staging) is not
equal to LAST NAME, FIRST NAME,
MIDDLE NAME (Pipeline)
AND
MOTOR NUMBER (Staging) =
MOTOR NUMBER (Pipeline) OR
SERIAL NUMBER (Staging) =
SERIAL NUMBER (Pipeline) OR
TCT NO. (Staging) = TCT NO.
(Pipeline) OR
PLATE NO. (Staging) = PLATE NO.
(Pipeline)
BDOI Leasing will check if

the reason for the
unmatched account.
Accounts with collaterals
that do not require an
insurance coverage will be
transferred by the user to
the NO INSURANCE
REQUIRED repository.
Otherwise, account will be
transferred to Pipeline for
quotation proposal
Data will be purged by the
system before the next
uploading process
Duplicates records
captured by the system
during uploading will also
be saved in this repository.
Data in this repository will
be retained for one (1)
year. Beyond this period,
data will be automatically
purged by the system.
Page 17 of 27

BDOI Leasing
Version 1.0
4. System generation of display message and log files after records have been uploaded to
the repositories. As soon as the matching and uploading process have been completed,
the system will prompt a display message to the user informing him of the number of
records that have been uploaded to the different repositories (FIG. 3)
5. System generation of log files after completion of the uploading process (FIG. 4).
Filename and location of the logs files will be defined in the system by BDOI.
STATUS
Successful
LOCATION
\\BDOI\REPOSITORY\LOG
FILENAME
XMMDDYYYYS TS
Page 18 of 27

BDOI Leasing
Version 1.0
Unsuccessful
FILES\LEASING\SUCCESFUL
\\BDOI\REPOSITORY\LOG
FILES\LEASING\UNSUCCESFUL
XMMDDYYYYU TS
X= FI, refers to FPMS and ICBS file. First letter of the filename was taken, MM =Month of
January to December, DD = sequential, pertains to the 1 st up to the last day of the month,
YYYY = Year, S = Successful uploading, U = Unsuccessful uploading, TS = Time Stamp,
actual time records were saved/uploaded to the repositories.
FIG. 4
The format and contents of the log files are summarized as follows:
CRITERIA
Format
SUCCESSFUL UPLOADING
Text file
UNSUCCESSFUL UPLOADING
Text file
Contents
Total number of records

uploaded
Number of records uploaded
per repository
Date (MM/DD/YYYY)
Time stamp
User Id
After records have been
successfully matched and
uploaded to repositories
Should not overwrite existing
log file based on timestamp.
Remarks: Indicate error/s found.

Date (MM/DD/YYYY)
Time stamp
User Id
Occurrence
Manner of
appending
After records were not successfully

uploaded to repositories
Should not overwrite existing log file
based on timestamp.
6. System display of history of uploaded files. User will be informed of the previous files that
have been uploaded
to the system
5).
MATCHING
AND(FIG.
UPLOADING
MESSAGE
3.2.2.
Wireframe
A total UI
1000
records have been matched and uploaded to repositories. Breakdown as
follows:
FIG.
5003records uploaded to Matched Accounts List
250 records uploaded to Uninsured List
250 records uploaded to Exception List
Matched and uploaded on 04302014 at 1:35 PM by USER 1
OK
Page 19 of 27

BDOI Leasing
Version 1.0
FIG. 5
3.2.3.
Inputs and Outputs
DATA ELEMENT
BEHAVIOR
OK
Executable button
MESSAGE
CONTENTS
SEARCH
Display
FIELDS
Drop down list
VALUES
User entered
Varchar
OK
Display
Varchar
3.2.4.
N/A
User entered
FORMAT
RANGE OF
VALUES
REMARKS
Refer to FIG. 3
Varchar
Refer to FIG. 5
Data columns
available
Reports Specification
Page 20 of 27

BDOI Leasing
Version 1.0
3.2.5.
Business Requirements Mapping

ITEM #
BRM-LS-RID2-001
BRM-LS-RID2-002
BRM-LS-RID2-003
BR REQUIREMENTS
FEATURES

match the MOTOR NUMBER,
SERIAL NUMBER, and TCT NO.
and PLATE NO. from staging
against Pipeline
upload records based on the
results of the matching to the
different repositories
System matching based on defined

criteria and business rules

generate log files after matching
and uploading of records
The system will generate log file for

successful and unsuccessful
uploading to the repositories.
System uploading to different

repositories based on predefined
business rules
3.3. RID3 Viewing and transfer of records to other repository/Pipeline

This function provides a facility in the system that will allow the user to view and transfer records
from a repository to another repository or to the Pipeline.
3.3.1. Features
1. Facility available for the user to view records in the repository. User may filter the records
based on the repository chosen (FIG. 6). Data columns that will be shown when the user
views the records will be as follows:
DATA COLUMNS
REMARKS
Basic Premium
First Name
Account Name in the FPMS/ICBS that have been

concatenated. Refer to 3.2.1.3
Insurance Company
Last Name

Loan Booking Date

Loan Maturity Date
Middle Name

Outstanding Loan Balance

Policy No.
Sum Insured
Total Premium
Unit Description
2.
Facility available to the user to transfer records. The system allows user to transfer one or
several records from a repository to another repository or to the Pipeline (FIG. 7).
Transfer of records is limited to the following:
SOURCE
UNINSURED
TARGET
NO INSURANCE
REMARKS
Accounts that do not require an insurance
Page 21 of 27

BDOI Leasing
Version 1.0
REQUIRED
UNINSURED
coverage shall be transferred by BDOILeasing to the NO INSURANCE REQUIRED

repository
Accounts that need to have an insurance
coverage shall be transferred by the user to
the Pipeline to be able to create a quotation /
proposal or a COC. The system will check for
duplicates for records that will be transferred
to Pipeline.
PIPELINE
The system will check if client name (LAST

NAME, MIDDLE NAME and FIRST NAME) is
existing in the Pipeline. If existing, details will
be saved under the existing client id.
Otherwise, the system will create a new client
id and capturing the details of the account.
The loan account details of the client name in
the Pipeline will be updated based on the
information from the source repository.
3.
System generation of display message after records has been transferred to Pipeline.
User will be informed of the number of records that have been transferred from the
repository to the Pipeline (FIG. 8).
3.3.2. UI Wireframe
FIG. 7
FIG. 8
TRANSFER COMPLETED MESSAGE
A total 1000 records have been transferred from MATCHED LIST to the PIPELINE
Transferred on 04302014 at 1:35 PM by USER 1
OK
Page 22 of 27

BDOI Leasing
Version 1.0
3.3.3. Inputs and Outputs

DATA ELEMENT
SEARCH
BEHAVIOR
User entered
FORMAT
Varchar
FIELDS
Drop down
list
VALUES
User entered
MATCHED
ACCOUNTS
Radio button
FOR PIPELINE
CREATION
Radio button
EXCEPTION LIST
Radio button
SELECT
Tick box
DATA COLUMNS
Display
Varchar
OK
Display
Varchar
MESSAGE
CONTENTS
Display
Varchar
RANGE OF VALUES
REMARKS
Refer to FIG. 6
Data columns
available
Varchar
Refer to FIG. 7
3.3.4. Reports Specification

N/A
3.3.5. Business Requirements Mapping

ITEM #
BRM-DM-RID3-001
BRM-DM-RID3-002
BRM-DM-RID3-003
BR REQUIREMENTS
FEATURES
User should be able to view

records in the repository
User should be able to transfer
records from/to repository/Pipeline
The system should provide
summary of records that have
been transferred from/to
Facility that will allow the user to

view records
Facility that will allow the user to
transfer records
The system will display
confirmation after transfer of
records.
Page 23 of 27

BDOI Leasing
Version 1.0
repository/Pipeline
3.4. RID4 Other Requirements

Requirements listed in this section are those that are not part of the sanitation process but are
necessary to the operation of BDOI-Leasing. Requirements under this section will be coordinated
with the BDOI unit handling the specific process. Detailed design and functionality will be discussed
in the appropriate RSD.
3.4.1. Features
N/A
3.4.2. Reports specification
N/A
3.4.3. Inputs and Outputs
N/A
3.4.4. Business Requirements Mapping

ITEM #
BRM-LS-RID4-001
BRM-LS-RID4-002
BRM-LS-RID4-003
BR REQUIREMENTS
detect if loans have been fully paid.
For paid loan, user has the option
to change the status to FOR
RENEWAL subject to the advice of
the client or endorsed it to other
units
as
OPEN
MARKET
(BUSINESS ORIGIN) in case the
client declines to renew his
insurance coverage. For loans that
have not been fully paid with
expiring insurance coverage, the
system should automatically mark
the account as for renewal of
insurance coverage.
User should be able to update the
loan status as FULLY PAID upon
receipt of notice (FULLY PAID or
TERMINATED)
from
BDOLF.
Accounts with FULLY PAID status
will be placed in the FULLY PAID
repository.
generate
expired
insurance
coverage per accounts (EXPIRY
LIST in excel format)
User should be informed through
dashboard:
REMARKS
To be
discussed
RENEWAL RSD
in
the
Please refer to the RENEWAL

RSD
For inclusion to the
DASHBOARD RSD
Page 24 of 27

BDOI Leasing
Version 1.0
BRM-LS-RID4-004
BRM-LS-RID4-005
BRM-LS-RID4-006
BRM-LS-RID4-007
4.
120 days prior to expiry for

generation of 1st proposal
- 40 days prior to the expiry
for generation of the 2 nd
proposal
- 7 working days prior to
expiry for generation of the
3rd reminder letter
- To request for hold cover 7
days prior to expiry
- That the hold cover will
expire in 30 days
The system should generate
covering letter for the 1 st and 2nd
proposal. Refer to BRM-RID5-003
User should be able to create multiyear proposal to clients. Details of
the proposal will be as follows:
- Client Name
- Address (optional)
- Description of unit
- Fair Market Value
- Term of Loan (number of
years)
User should be able to create fleet
proposal for clients. Details of the
proposal will be as follows:
- Client Name
- Address (optional)
- Description of unit
- Fair Market Value
- Term of Loan (number of
years)
User should be able to generate the
following reports:
- Penetration Ratio
- New Availments Insurance
Report
Risks, Issues, and Constraints

FUNCTIONAL
TYPE
AREA
RID 1
Risk

SOLICITATION/PLACEMENT
RSD
RSD
Please refer to the

RSD
For inclusion to the REPORTS

RSD
DESCRIPTION
MITIGATION/RESOLUTION
Filename and location of

upload files have not been
properly complied with the
user
BDOI to ensure prescribed format

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

BDOI Leasing
Version 1.0
upload file
RID 2
Constraints
Accuracy and completeness

of the matching process will
depend on the completeness
of the data in the source
system and the correctness
of the extraction program
that generates the upload
files
BDOI to call the attention of the

system owners for any mishandling
of data noted in the extracted files.
4.1. Design Constraints

The design of the matching and upload facility is highly dependent on the format and contents of the
upload file. Any changes on the upload file will impact the workability of the upload facility
4.2. Hardware and Software Constraints

The performance of the upload process is highly dependent on the specification of the data server,
workstation and the number of records that needs to be uploaded to the Pipeline module.
5.
Assumptions and Dependencies

a. The accuracy of the matching process is highly dependent on the completeness and
correctness FPMS and ICBS upload files and the data in the Pipeline (Submitted Policy and
Booked Accounts) module.
b. Duplicate records in the upload files will be handled by the FPMS and ICBS source systems.
Page 26 of 27

BDOI Leasing
Version 1.0
6.
APPENDIX
6.1. Business Rules
a. If the same collateral had been used to avail of another loan, this will be treated by the
system as new loan availments.
b. Upload of FPMS and ICBS to the Brokerage System will be done every 1 st Friday of the
month.
c. Correction of data in the EXCEPTION repository will be done in the source system (FPMS,
ICBS or PIPELINE)
6.2. Access Matrix
PROCESS
Upload of FPMS/ICBS to staging
Delete records from staging
Match and upload FPMS/ICBS from
staging to repositories
View/print records from repository
View and print reports from the system
TEAM LEAD
ACCOUNT OFFICER
X
X
X
X
X
X
X
Page 27 of 27

RSD Leasing - v1.0

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

RSD Leasing - v1.0

Încărcat de

Drepturi de autor:

Formate disponibile

BDO Insurance Brokers, Inc.

Requirements Specification Document

April 24, 2014

Please refer to sign-off sheet

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

Requirements Specification Document

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

Requirements Specification Document

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

Requirements Specification Document

1.4. Definition of Terms and Acronyms

BDO Leasing and Finance

Banco De Oro Insurance

BDO Leasing and Finance Incorporation

Finance Product Management System

Integrated Computerized Banking System

Insurance Monitoring Database

Promissory Note Number

Requirements Specification Document

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

Requirements Specification Document

2.3. Process Schematic / Process Flow

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

Requirements Specification Document

VIEW AND TRANSFER OF RECORDS FROM/TO REPOSITORY/PIPELINE

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

Requirements Specification Document

Except for the

2.4. Interfaces with Users

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

Requirements Specification Document

X = FPMS or ICBS, MM = Month (January to December), DD = 1 st up to the last day of the

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

Requirements Specification Document

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

Requirements Specification Document

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

Requirements Specification Document

Inputs and Outputs

Refers to the date

Business Requirements Mapping

User should be able to indicate the

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

Requirements Specification Document

3.2. RID2 Matching and uploading to repositories

System default on mandatory entries

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

Requirements Specification Document

Request for Survey

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

Requirements Specification Document

COMPLIANCE DISPLAY MESSAG

Missing mandatory entries > 90% of the

Reject entire upload file

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

Requirements Specification Document

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

Requirements Specification Document

MOTOR NUMBER (Staging) =

MOTOR NUMBER (Staging) not

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

BDOI Leasing will check if

Requirements Specification Document