RSD All Market Segments - Courier Report and Transmittal Slip - v2

BDO Insurance Brokers, Inc.
(BDOI)
Requirements Specification Document
For uploading of:
Courier Confirmation
Transmittal Slip
Version 0.01
Creation Date: January 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.

Uploading requirements 02
Version 0.01
Document History
Version
Date
Author
Description of
Change
Reviewed By
0.01
January 28, 2015
Jeffrey Oliveros
Document creation
Conchita Valena
Approved By
Reference Documents
Document Name
Version
Date Updated
Business Requirement Pipeline Management

Business Systems Proposal of BDOI Online Brokerage System (BBS)
CLG Renewal Module
Requirements Specification Document for Pipeline Management,
Solicitation and Placement
2
1.0
3/4/2014
3/12/2014
0.04
4/3/2014
Classification: GENPACT Internal All rights reserved. Copyright(2008-2014)
Page 2 of 29

Version 0.01
TABLE OF CONTENTS
1. Process Schematic / Process Flow............................................................................................... 4

2. Functional Description................................................................................................................... 6
2.1 RID 1 Extraction of data............................................................................................................ 6
2.1.1 Features.......................................................................................................................... 6
2.1.2 UI Wireframe................................................................................................................... 9
2.1.3 Inputs and Outputs........................................................................................................ 11
2.1.4 Reports Specification..................................................................................................... 12
2.1.5 Business Requirements Mapping..................................................................................12
2.2 RID 2 Uploading of Data to Staging Repository......................................................................12
2.2.1 Features........................................................................................................................ 12
2.2.2 UI Wireframe................................................................................................................. 17
2.3 RID 3 Uploading of Data from Staging to Pipeline..................................................................20
2.3.1 Features........................................................................................................................ 20
2.3.2 UI Wireframe................................................................................................................. 23
Page 3 of 29

Version 0.01
1. Process Schematic / Process Flow

EXTRACTION OF DATA
BDOI
BROKER SYSTEM
Start
Generates
extract file
Broker System
Fills out values

in File
the
Extract
extraction parameter
Saves file to
predefined location
UPLOADING OF DATA TO STAGING REPOSITORY

BDOI
BROKER SYSTEM
Checks and validates

file
A
C
C
Sends extract file

Passed
to Courier
criteria?
Companies or for
confirmation
N
End
Uploads file
STAGING
Page 4 of 29

Version 0.01
UPLOADING OF DATA FROM STAGING REPOSITORY TO PIPELINE

BROKER SYSTEM
B
Validates and matches

data against Pipeline
With
unmatched
records?
Generates exception
report
Extract File
N
Uploads
confirmation/feedback
to the Pipeline
PIPELINE
End
Page 5 of 29

Version 0.01
2. Functional Description
2.1 RID 1 Extraction of data
This function provides a facility in the system that will allow the user to extract data from the broker
system that will be sent to the courier for their CONFIRMATION OR REPLY.
2.1.1 Features
1. System facility to allow user to extract data based on the required parameters. The
following filtering options will be available to the user when extracting data from the broker
system.
FILTER
Year
Month
Product Type
Courier Company
Location
2.
DESCRIPTION
Extraction of data will be limited on a yearly basis (e.g.
2014, 2015 or 2016).
Extraction of data will be on a monthly basis or for
several CONSECUTIVE months (e.g. January, January
to April).
Extraction of data can be on a per product type namely
FIRE, MOTOR and MRI.
Extraction of data can be on a per courier company.
However, user has the option to include all the courier
company by not indicating a particular insurer in the
extraction parameter.
Extraction of data may be based on location covered by
the courier company.
System facility to allow user to extract data to be sent to the COURIER SERVICE
PROVIDERS. Extraction of data for COURIER CONFIRMATION will be based on
PRODUCT TYPE to include FIRE, MOTOR and MRI taking into consideration other
values defined by the user in the system parameters. The following information from the
broker system for these product types will be extracted from the system.
DATA
Transmittal Reference
Number
Courier Company
Date Sent to Courier
Account Number
Mailing Address
Address
Areas
Assureds Name
VALUES/SOURCE
Reference number generated by the system after creation of
the transmittal
Name of the courier company maintained in the system and
defined during creation of transmittal tasked to send the letter
to the addressee
Date indicated during creation of transmittal when the letter
was forwarded to the courier company that will send the letter
to the addressee
Account Reference Number (Pipeline > Account Management
> Basic Information)
Billing Address (Pipeline > Account Management > Basic
Information)
House Number, Street, Barangay, City or Municipality and
Province (Pipeline > Client Administration > Address)
City/Municipality (Pipeline > Client Administration > Address)
Assured Name (Pipeline > Account Management > Basic
Page 6 of 29

Version 0.01
Information)
The following columns will be part of the extract file where the Courier companies can
indicate their reply, confirmation or comments which will be uploaded to the broker
system. This requirement will be discussed further in the succeeding sections of this
document.
COURIER
VALUES
REMARKS
Status
Delivered, Pending delivery or

Return to Sender.
Recipient
Name of the person who received

the letter for the addressee.
Relationship of the receiver to the
addressee of the letter.
Relationship
Date Received
Reason for
unsuccessful
delivery
Receipt
Reference
Number
Date the letter was received

Reason letter was not delivered
Reference number by the courier
report indicating the successful
sending of letter to the addressee
D = Delivered, PD = Pending
Delivery, RTS = Return To
Sender
Free text format
Values that will be indicated
should be based on the data
defined in the broker system
MM/DD/YYYY format
Free text format
Free text format
Extract files will be generated in EXCEL format. The system will disregard the version
release of the application installed in the workstation of the users.
3.
System validation to extract information for confirmation. The following conditions should
be present before accounts can be included in the extraction:
CONDITION
There was a transmittal transaction created
for
the
ACCOUNT
REFERENCE
NUMBER. BDOI Module for the transaction
created is RENEWAL.
The following data fields in the Transmittal
transactions have no values:
o Status
o Recipient
o Relationship
o Date Received
o Receipt Reference Number
4.
REMARKS
Transaction was created in the
Transmittal Facility of the broker system.
System facility to establish the type of extract file. Since the information that will be
extracted will differ depending on who is the target recipient of the file, a HEADER CODE
with the NUMBER OF EXTRACTED RECORDS will be placed in each extract file. As
discussed in the main section of the RSD, there will be a CENTRALIZED uploading
module but the format of the extract and upload file will differ based on the data per
process per module that will be uploaded to the broker system.
Page 7 of 29

Version 0.01
Below is the proposed naming convention for the header code.

EXTRACT FILE
HEADER CODE
To be sent to the Courier Companies
XZAB
WHERE:
5.
HEADER CODE
DESCRIPTION
X
Z
A
B
C = Courier Confirmation
Date (MMDDYYYY format) of extraction
Time stamp (HH:MM:SS format)
Number of records
System facility to keep temporary record of files that have been extracted. The system will
keep records or logs of HEADER CODE and TOTAL RECORDS per extracted file. These
will be compared when the same extract files will be uploaded (with reply from the courier
companies) back to the system. To illustrate:
If there are 200 transmittal transactions created for the month of January that will be
extracted based on current date of January 21, 2015 at 3 pm, the system will generate
header code of C0121153:00:00 with 200 records which will be placed on the header of
the extract file. The system will also log C0121153:00:00 with 200 records in the
database. During uploading, the system will validate if C0121153:00:00 is a valid file by
comparing the header code and the total number of records as against those that have
been logged. This feature will be discussed further in section 2.2.1.4 of this document
HEADER CODE
NUMBER OF RECORDS
RESULTS
C0121153:00:00
C0121153:00:00
C0121153:00:00
200
300
100
Valid
Not valid
Not valid
6.
System facility to allow duplicate extraction of accounts. The system will allow the user to
extract accounts (repeated extractions) as many times depending on his needs subject to
the conditions mentioned in the preceding regarding the inclusion of accounts in the
extraction. This is to accommodate the possibility that the user will extract records but for
some reason will not actually process or upload the file to the system.
7.
System facility to automatically save and indicate filename of the extracted file. The
system will store the extract file to a predefined directory maintained in the system.
Filename will also be generated by the system for the user.
FILE
Courier confirmation
STATUS
Extracted
LOCATION
\\BDOI\Extracted\ Courier Confirmation
FILENAME
XZAB
Page 8 of 29

Version 0.01
WHERE:
CODE
X
Z
A
B
C
8.
VALUE
C = Courier Confirmation
Start Month (MM format) ) indicated in the filter
options during extraction
End Date (MM) format) indicated in the filter
options during extraction
Date extracted (MMDDYYYY format)
Timestamp (HH:MM:SS format)
REMARKS
Filtering will be on a
per month or for
several
consecutive
months.
System facility to prompt system message after records have been extracted. The user
will be prompted of a system message informing the user of the following:
o
o
Whether extraction was successful or failed;

If successful,
o Number of records that have been extracted;
o Location where the extract file was saved.
2.1.2 UI Wireframe
DATA EXTRACTION MENU
Page 9 of 29

Version 0.01
REPORT GENERATION PARAMETERS
DATA EXTRACTION CONFIRMATION MESSAGE
Page 10 of 29

Version 0.01
2.1.3 Inputs and Outputs

DATA EXTRACTION MENU
DATA ELEMENT
BEHAVIOR
Executable
button
FORMAT
RANGE OF VALUES
REMARKS
Directs the system
administrator to the
DATA
EXTRACTION
PARAMETERS.
DATA EXTRACTION PARAMETERS
Page 11 of 29

Version 0.01
DATA ELEMENT
BEHAVIOR
FORMAT
RANGE OF VALUES
Year
Drop down
Start Month
Drop down
January to December
End Month
Drop down
January to December
Product Type
Drop down
Fire, Motor and MRI
Courier Company
Drop down
Clear All
Executable
button
Extract
Executable
button
Close
Executable
button
REMARKS
Drop down will
reflect previous to
current year
subject to the
archiving rules
defined in the
system.
o All
o Particular courier
company
User can indicate a

particular courier
company or may
chose all by
selecting the ALL
option.
Erases all values
in the extraction
parameters
indicated by the
user.
Extracts
data/generates
extract file based
on the parameters
indicated by the
user.
Closes the DATA
EXTRACTION
PARAMETER
WINDOW.
RANGE OF VALUES
REMARKS
DATA EXTRACTION CONFIRMATION MESSAGE

DATA ELEMENT
Confirmation
Message
Ok
BEHAVIOR
FORMAT
Display
Executable
button
Closes the
EXTRACTION
CONFIRMATION
MESSAGE
2.1.4 Reports Specification

Refer to Annex 1- extract file generated from the broker system.
Page 12 of 29

Version 0.01
2.1.5 Business Requirements Mapping

ITEM #
BR REQUIREMENTS
FEATURES
BRM-UP02-RID1-001
User should be able to extract

data listed in section 2.1.1.2
based parameters discussed in
2.1.1.1 of this document.
BRM-UP02-RID1-002
User should be able to generate

and save extracted data based
on the predefined location.
System facility to allow the user to

extract data based on the
requirements mentioned in the
section 2.1.1.1 and 2.1.1.2 of this
document.
System facility to extract and save
data to a predefined repository.
2.2 RID 2 Uploading of Data to Staging Repository

This function provides a facility in the system that will validate the format and completeness of the
uploading files. The uploading files refer the COURIER CONFIRMATION and/or TRANSMITTAL
REPORT. The Courier confirmation upload file refer to extract file that had been submitted to the
courier companies for reply or feedback while the transmittal report are those that have been
prepared manually by BDOI. Unlike the Courier report, contents of the transmittal report were not
extracted from the system. These are new data that will be introduced to the system through
uploading instead of data entry. The upload program will validate the format and contents of the file
to ensure that this complies with the system requirements before this is uploaded to the Staging
Repository.
2.2.1 Features
1. System facility to allow user to upload files. A module will be available to the user to
upload the Courier Confirmation and Transmittal Report. Below are the contents of each
upload file.
COURIER CONFIRMATION
BDOI Module
Transmittal Reference Number
Courier Company
Account Number
Mailing Address
Address
Areas
Assureds Name
Status
Recipient
Relationship
Date Received
Reason for unsuccessful delivery
Receipt Reference Number
TRANSMITTAL REPORT
BDOI Module
Slip
Date Sent to Insurer
Date Sent to Client
Date Received Feedback from Insurer
Mode of Transmittal
Name of Receiver
Relationship to the Assured
Date Received from Insurer
Date Received from the Bank
Date Sent to the Bank
TAT
BDOI Module
Slip
Date Sent to Client
Date Received Feedback from Insurer
Mode of Transmittal
Page 13 of 29

Version 0.01

Name of Receiver
TAT
2. System detection on the type and location of files to be uploaded. The system will detect
the type and location of files to be uploaded to the broker system through the UPLOAD
FILE MAINTENANCE TABLE in the BDOI Brokerage System.
FILE
Courier
confirmation
Courier
confirmation
Transmittal
Report
Transmittal
Report
STATUS
For uploading
FILENAME
XZAB
Uploaded
LOCATION
\\BDOI\For uploading\Courier
confirmation
\\BDOI\Uploaded\Courirer confirmation
For uploading
\\BDOI\For Uploading\Transmittal Report
XZAB
Uploaded
\\BDOI\Uploaded\Transmittal Report
XZAB
XZAB
WHERE:
CODE
X
Z
A
B
VALUE
C = Courier Confirmation, TR = Transmittal Report
Start Month (MM format) ) indicated in the filter options during extraction
End Date (MM) format) indicated in the filter options during extraction
Date of target upload (MMDDYYYY format)
To illustrate how the codes Z and A operates, if the month covering the contents of the
extracted file for courier confirmation includes January 2014 to March 2014, the filename
of the extract file that will be uploaded based on current date of January 21, 2015 will be
C010301212015.
FOR UPLOAD folder pertains to files that have not been uploaded to the system.
UPLOADED 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
UPLOADED folder.
3. System detection on the files due for uploading. Based on the date indicated in the
filename of the upload files, the system will prompt the user regarding files that should be
uploaded. To illustrate:
Let us assumed that an extract file courier confirmation have been replied by the courier
Page 14 of 29

Version 0.01
companies.
C010301212015
C040501212015
C060703212015
C070904212015
C091207212015
TRANSMITTAL REPORT
TR010301212015
TR040501212015
TR060703212015
TR070904212015
TR091207212015
If the system date is January 1, 2014, user will be prompted of the following files that
should be uploaded to the system. The date of the upload which was 01212015
(corresponding to B in the naming convention) was compared by the system as against the
month of January.
C010301212015
C040501212015
TRANSMITTAL REPORT
TR010301212015
TR040501212015
In the case of files that have not been uploaded based on the date corresponding to its
filename, the system will allow the user to upload these provided that the filename dates
are not beyond the current or system date. Let us presume that the current date is June 1,
2015. Based on the above example, the user will be prompted of the following files that are
due for uploading.
C010301212015
C040501212015
C060703212015
C070904212015
TRANSMITTAL REPORT
TR010301212015
TR040501212015
TR060703212015
TR070904212015
4. System checking on the validity of the upload files. In the case of the COURIER REPORT,
the system will check if the upload file is valid for uploading based on the FORMAT,
REQUIRED DATA COLUMNS AND HEADER CODE STORED IN THE SYSTEMS
DATABASE AND THE TOTAL NUMBER OF RECORDS VERSUS THE HEADER CODE
AND THE TOTAL RECORDS OF THE UPLOAD FILE. In case there is a matched, the
system will upload the data. Otherwise, the system will REJECT the ENTIRE upload file.
To illustrate:
In the systems database, the following are the logs of the extract files generated by the
system.
COURIER
CONFIRMATION
C010301212015
C040501212015
C060703212015
C070904212015
TOTAL
RECORDS
200
100
250
400
If I upload a file whose header code indicates C120904212015, the system will reject this
file because the header code does not match any records in the systems database. One
of the possible causes of the discrepancy is due to manual/accidental alteration made by
the user on the header code of the extract file. Unless, corrections will be made on the
code, the user will be barred from uploading the file. In the same manner, if there is a
matched in the header code but the total number of records differs, the system will reject
Page 15 of 29

Version 0.01
the upload file.

The system will allow uploading of the file with the same header code in cases that not all
of the contents were uploaded to the system due to errors (refer to section 2.3.1.1) but
there will be validation on the following:
VALIDATION
Filename of the upload file
Target data fields where the data will

be uploaded
REMARKS
The upload file will contain the same header
code but the filename will be different since
the file was generated as an exception report.
The system will not allow the user to overwrite
or supersede existing values in the data field
through uploading. User has to delete or
remove the existing data before a new data
can be uploaded.
In the case of the TRANSMITTAL REPORT, the system will only check based on the
FORMAT AND REQUIRED DATA COLUMNS of the upload file. Header Code will not be
checked because the contents were not extracted from the system.
5. System checking on the contents of the upload file. The system will validate the following
entries prior to uploading in the broker system.
BDOI Module
Account Reference Number
Courier Company
Status
Recipient
Relationship
Date Received
Reason for unsuccessful delivery
CONDITION
There should be no NULL values
There should be no DUPLICATE records and
NULL values
Page 16 of 29

Version 0.01
TRANSMITTAL REPORT
BDOI Module
Slip
Date Sent to Client
Date Received Feedback from
Insurer
Mode of Transmittal
Name of Receiver
TAT
CONDITION
There should be no
NULL values
There should be no
NULL values
There should be no
NULL values
There should be no
NULL values
There should be no
NULL values
There should be no
NULL values
There should be no
NULL values
There should be no
NULL values
There should be no
NULL values
There should be no
NULL values
There should be no
NULL values
There should be no
NULL values
There should be no
NULL values
APPLICABLE BDOI
MODULES
Quotation, Proposal,
Renewal, Placement,
Booking and Submitted
Quotation and Placement
Proposal, Booking and
Renewal
Quotation and Proposal
Proposal, Renewal,
Placement, Booking
Renewal
Renewal and Booking
Renewal and Booking
Booking
Submitted
Submitted
Submitted
The system will REJECT the ENTIRE upload file if there are DUPLICATE records or NULL
values detected by the system. Please note that the account reference number will be used
to match and determine records in the Pipeline where the INSURER CONFIRMATION and
TRANSMITTAL REPORT will be uploaded.
6. System facility to prompt system message after records have been validated. In the event
that the file had been validated to be NOT valid for uploading, the user will be prompted of
a system message informing him that the file cannot be uploaded to the system. For files
that are valid for uploading, the system will not prompt a system message to the user.
Page 17 of 29

Version 0.01
2.2.2 UI Wireframe
DATA UPLOADING MENU
DATA UPLOADING WINDOW
Page 18 of 29

Version 0.01
DATA VALIDATION RESULT MESSAGE

DATA UPLOADING MENU
Page 19 of 29

Version 0.01
DATA ELEMENT
BEHAVIOR
Executable
button
Transmittal Report
Executable
button
FORMAT
RANGE OF VALUES
REMARKS
Directs the user to
the DATA
UPLOADING
WINDOW
Directs the user to
the DATA
UPLOADING
WINDOW
DATA UPLOADING WINDOW

DATA ELEMENT
BEHAVIOR
File
Display
Location
Display
Select
Check box
Select All
Check box
Upload
Executable
button
Close
Executable
button
FORMAT
RANGE OF VALUES
REMARKS
Shows file for
uploading per
product type.
Shows location of
files for uploading.
If checked,
includes the file for
uploading.
If checked, selects
all file for
uploading. If
unchecked,
deselects all data
for uploading.
Uploads the file
selected by the
user to the system.
Closes the DATA
UPLOADING
WINDOW
Page 20 of 29

Version 0.01
DATA VALIDATION RESULT MESSAGE

DATA ELEMENT
BEHAVIOR
Error Message
Display
Ok
Executable
button
FORMAT
RANGE OF VALUES
REMARKS
Closes the
VALIDATION
RESULT
MESSAGE
WINDOW

N/A

ITEM #
BRM-UP02-RID2-001
BRM-UP02-RID2-002
BR REQUIREMENTS
FEATURES
The
system
should
automatically show or prompt
the user regarding files to be
uploaded.
The system should be able to
validate if the upload file is valid
for uploading to the broker
system.
System facility to detect and

prompt the user due for uploading
based on the predefined location in
the system.
System facility to check if:
o The format and contents
conforms to the system
requirements
o The upload file has a
corresponding extract file
through the header code
validation.
Page 21 of 29

Version 0.01
2.3 RID 3 Uploading of Data from Staging to Pipeline

This function provides a facility in the system that will upload the COURIER CONFIRMATION and/or
TRANSMITTAL REPORT. This stage presumes that the file have already confirmed to be valid for
uploading based on the validation procedure and criteria discussed in the preceding section.
2.3.1 Features
1. System facility to upload files. The following data from the courier confirmation and
transmittal report upload file will be compared and matched if existing in the system
BDOI Module
Courier Company
Status
Relationship
TRANSMITTAL REPORT
BDOI Module
Slip
Mode of Transmittal
TRANSMITTAL FACILITY
BDOI Module
Courier Company
Status
Relationship
TRASMITTAL
FACILITY
There should be no
NULL values
There should be no
NULL values
There should be no
NULL values
There should be no
NULL values
APPLICABLE BDOI
MODULES
Renewal, Placement,
Proposal, Renewal,
Placement, Booking
Renewal and Booking
If the above conditions are present, the system will upload the following information to the
broker system.
Page 22 of 29

Version 0.01
Status
Recipient
Relationship
Date Received
TRANSMITTAL REPORT
TRANSMITTAL FACILITY
Status
Recipient
Relationship
Date Received
BDOI Module
Slip
TRANSMITTAL
FACILITY
BDOI Module
Slip

Date Sent to Client

Date Sent to Client
Date Received Feedback from

Insurer
Mode of Transmittal
Date Received
Feedback from Insurer
Mode of Transmittal

Name of Receiver

Name of Receiver
Relationship to the
Assured
Date Received from
Insurer
Date Received from
the Bank
TAT

TAT
APPLICABLE BDOI
MODULES
Renewal, Placement,
Quotation and Placement
Proposal, Booking and
Renewal
Quotation and Proposal
Proposal, Renewal,
Placement, Booking
Renewal
Renewal and Booking
Renewal and Booking
Booking
Submitted
Submitted
Submitted
Page 23 of 29

Version 0.01
2. System facility to generate exception reports. In the event that records in the upload file did
not meet the criteria mentioned in 2.3.1.1, an exception report consisting of the same data
columns indicated in the uploaded file will be saved and generated by the system to a
predefined server directory. Below is the proposed repository of the exception report.
FILE
Courier
Confirmation
Transmittal Report
STATUS
Unmatched
Unmatched
LOCATION
\\BDOI\Unmatched\Courier
Confirmation\
\\BDOI\Unmatched\Transmittal
Report
FILENAME
XZAB
XZAB
WHERE:
CODE
X
Z
A
B
C
D
VALUE
I = Insurance Companies, T = Transaction Diary
Start Month (MM format) ) indicated in the filter options during extraction
End Date (MM) format) indicated in the filter options during extraction
Date Generated (MMDDYYYY format)
Timestamp (HH:MM:SS format)
E = Exception
User will be allowed to upload an exception file by indicating a target date of upload and
placing the file to the predefined path mentioned in section 2.2.1.1 of this document. To
illustrate:
If the system generated an exception file C01030121201503:00:00E and the user want to
upload this file after the errors have been corrected on the same day (the exception report
was generated), the filename will be C010301212015. If the file will be uploaded on a later
date, the filename will be C010301262015. Please note that in example 1, the Time Stamp
(C) and Exception (D) were removed and the Date Generated (B) was retained signifying
that the file will be uploaded on the same day the exception report was generated. In
example 2, C and D were removed while B was changed to a different date.
3. System generation of display message after uploading. The system will prompt the user of
a message regarding records that have been uploaded successfully and those that have
been rejected due conditions that have not been complied.
CONDITION
Errors are PRESENT in the
Staging repository
Errors are NOT PRESENT in
SYSTEM MESSAGE
The system will display an error message to inform the
user that ALL or SOME of the records were not uploaded
to the Pipeline.
The system will display a message to inform the user that
Page 24 of 29

Version 0.01
the Staging repository
ALL records were uploaded to the Pipeline.
4. System capability to generate log file for SUCCESSFUL and UNSUCCESSFUL upload of
data from the Staging repository to the Pipeline module. The system will assign a filename
(XYZA format)for the log files and store this to a predefined location based on the table
below:
WHERE:
FORMAT
X
Y
Z
A
DESCRIPTION
S = Successful , U = Unsuccessful
Date file was generated in YY-MM-DD format.
Time file was generated HH:MM:SS format.
1- 99
AND
STATUS
Successful uploading
Successful uploading
Unsuccessful uploading
Unsuccessful uploading
LOCATION
\\BDOI\For Upload\Courier Confirmation\Successful
\\BDOI\For Upload\Courier Confirmation\Successful
\\BDOI\For Upload\ Transmittal Report\Unsuccessful
\\BDOI\For Upload\ Transmittal Report\Unsuccessful
The contents of the log 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
After a successful or unsuccessful uploading of records
Manner of appending
Should not overwrite existing log file based on timestamp.
5. System display of history of uploaded files. User will be able to VIEW records of previous
files that have been uploaded to the system. Below are the proposed parameter and data
columns that will be available to the user.
Page 25 of 29

Version 0.01
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
2.3.2 UI Wireframe
DATA UPLOADING CONFIRMATION/UNMATCHED RECORD MESSAGE WINDOW
VIEW UPLOADED FILES MENU
Page 26 of 29

Version 0.01
VIEW UPLOADED FILES SCREEN
Page 27 of 29

Version 0.01

DATA UPLOADING CONFIRMATION/UNMATCHED RECORD MESSAGE WINDOW
DATA ELEMENT
BEHAVIOR
Message
Display
Closes
Executable
button
FORMAT
RANGE OF
VALUES
REMARKS
Closes DATA
UPLOADING
CONFIRMATION/UN
MATCHED RECORD
MESSAGE WINDOW
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
Page 28 of 29

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

Refer to Annex 1 and Annex 2 for the upload file of Courier Confirmation and Transmittal Report
respectively.

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

the following to the broker
system:
o Courier Confirmation
o Transmittal Report
The system should be able to
match and validate target data
fields versus source data fields
in the upload file.
User should be able to view
files that have been uploaded
to the system.
Facility to allow the user to upload

the following to the broker system:
o Courier Confirmation
o Transmittal Report
System facility to match and

validate target data fields versus
source data fields in the upload file.
Facility to allow the user to view
files that have been uploaded to
the system.
Page 29 of 29

RSD All Market Segments - Courier Report and Transmittal Slip - v2

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

RSD All Market Segments - Courier Report and Transmittal Slip - v2

Hochgeladen von

Copyright:

Verfügbare Formate

BDO Insurance Brokers, Inc.

Requirements Specification Document

January 28, 2015

Business Requirement Pipeline Management

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

Requirements Specification Document

1. Process Schematic / Process Flow............................................................................................... 4

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

Requirements Specification Document

1. Process Schematic / Process Flow

Fills out values

UPLOADING OF DATA TO STAGING REPOSITORY

Checks and validates

Sends extract file

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

Requirements Specification Document

UPLOADING OF DATA FROM STAGING REPOSITORY TO PIPELINE

Validates and matches

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

Requirements Specification Document

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

Requirements Specification Document

Delivered, Pending delivery or

Name of the person who received

Date the letter was received

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

Requirements Specification Document

Below is the proposed naming convention for the header code.

To be sent to the Courier Companies

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

Requirements Specification Document

Whether extraction was successful or failed;

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

Requirements Specification Document

REPORT GENERATION PARAMETERS

DATA EXTRACTION CONFIRMATION MESSAGE

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

Requirements Specification Document

2.1.3 Inputs and Outputs

DATA EXTRACTION PARAMETERS

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

Requirements Specification Document

Fire, Motor and MRI

User can indicate a

DATA EXTRACTION CONFIRMATION MESSAGE

2.1.4 Reports Specification

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

Requirements Specification Document

2.1.5 Business Requirements Mapping

User should be able to extract

User should be able to generate

System facility to allow the user to

2.2 RID 2 Uploading of Data to Staging Repository

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

Requirements Specification Document

Date Sent to Courier

\\BDOI\For Uploading\Transmittal Report

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

Requirements Specification Document

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

Requirements Specification Document

the upload file.

Target data fields where the data will