RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
-
Upload
glutton-arch -
Category
Documents
-
view
215 -
download
0
Transcript of RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
1/25
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 publicwithout the prior express written permission of GENPACT.
BDO Insurance Brokers, Inc. (BDOI)
Requirements Specification DocumentFor uploading of:
Insurer Confirmation
Transaction Diary
Version 0.01
Creation Date: January 2015
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
2/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
Classification: GENPACT Internal© All rights reserved. Copyright(2008-2014) Page 2 of 25
Document History
Versio
n
Date Author Description of
Change
Reviewed By Approved
By
0.01 January 28, 2015 Jeffrey Oliveros Document creation Conchita Valena
Reference Documents
Document Name Version Date Updated
Business Requirement – Pipeline Management 2 3/4/2014
Business Systems Proposal of BDOI – Online Brokerage System (BBS) -Renewal
1.0 3/25/2014
Business Systems Proposal of BDOI – Online Brokerage System (BBS) -CLG Renewal Module
1.0 3/12/2014
Requirements Specification for Pipeline Management, Solicitation andPlacement
0.04 4/3/2014
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
3/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
Classification: GENPACT Internal© All rights reserved. Copyright(2008-2014) Page 3 of 25
TABLE OF CONTENTS
1. Process Schematic / Process Flow ........................................................................................ 42. Functional Description ............................................................................................................ 6
2.1 RID 1 Extraction of Data ............................................................................................................ 62.1.1 Features ................................................................................................................................ 62.1.2 UI Wireframe ....................................................................................................................... 122.1.3 Inputs and Outputs .............................................................................................................. 142.1.4 Reports Specification .......................................................................................................... 152.1.5 Business Requirements Mapping ....................................................................................... 15
2.2 RID 2 Checking and validation of upload files ......................................................................... 152.2.1 Features .............................................................................................................................. 162.2.2 UI Wireframe ....................................................................................................................... 192.2.3 Inputs and Outputs .............................................................................................................. 212.2.4 Reports Specification .......................................................................................................... 222.2.5 Business Requirements Mapping ....................................................................................... 22
2.3 RID 3 Uploading of files ........................................................................................................... 222.3.1 Features .............................................................................................................................. 222.3.2 UI Wireframe ....................................................................................................................... 24
2.3.3 Inputs and Outputs .............................................................................................................. 242.3.4 Reports Specification .......................................................................................................... 242.3.5 Business Requirements Mapping ....................................................................................... 25
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
4/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
Classification: GENPACT Internal© All rights reserved. Copyright(2008-2014) Page 4 of 25
1. Process Schematic / Process Flow
EXTRACTION OF DATA
BDOI BROKER SYSTEM
VALIDATION OF UPLOAD FILE
BDOI BROKER SYSTEM
Start
Fills out values in theextraction parameter
Valid?N
Y
Uploads file
Generates extract file
Saves to predefinedrepository
Extract File
A
A Checks if file is valid
for uploading
B
End
C
Sends extract file toInsurance Companies
or BDOI units forconfirmation
Broker System
STAGING
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
5/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
Classification: GENPACT Internal© All rights reserved. Copyright(2008-2014) Page 5 of 25
BROKER SYSTEM
N
Y
Matches andUploads data
End
B
Withunmatchedrecords?
Generates exceptionreport file C
Uploadsconfirmation/feedbackto the broker system
Broker System
Extract File
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
6/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
Classification: GENPACT Internal© All rights reserved. Copyright(2008-2014) Page 6 of 25
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 that will be sent tothe Insurance Companies and/or BDOI units for their confirmation or reply.
2.1.1 Features
1. System facility to allow user to extract data based on the required parameters. Thefollowing filtering options will be available to the user when extracting data from the brokersystem.
FILTER DESCRIPTION
Year Extraction of data will be limited on a yearly basis (e.g.2014, 2015 or 2016).
Start Month Extraction of data will be on a monthly basis or forseveral CONSECUTIVE months (e.g. January, Januaryto April).
End Month
Product Type Extraction of data will be on a per product type namelyFIRE, MOTOR and MRI.
Insurance Company Extraction of data may be on a per insurance company.However, user has the option to include all the insurancecompany by not indicating a particular insurer in theextraction parameter.
Package with changes If checked, the system will only extract those withchanges in the PACKAGED per product type.
Non-package with changes If checked, the system will only extract those withchanges in the NON-PACKAGED per product type.
Total Sum Insured (TSI)above a defined value
If checked, the system will only extract those accountswhose TSI is above the indicated value for bothPACKAGE and NON-PACKAGED per product type.
For Renewal If checked, the system will extract that have beenidentified for renewal only. Otherwise, the system willextract records regardless if the account is due forrenewal or not.
Transaction Diary If checked, the system will extract accounts excludingconditions (refer to section 3.3.1.1 of this document)defined in the extracting. However, extraction will still bebased on product type (FIRE, MOTOR and MRI). Userswill have the option to indicate a particular account.
2. System facility to allow user to extract data to be sent to the INSURANCE COMPANIES orBDOI units. Extraction of data for INSURER CONFIRMATION or for BDOI REMARKS willbe based on PRODUCT TYPE to include FIRE, MOTOR and MRI taking into
consideration other values defined by the user in the system parameters. The followinginformation from the broker system for these product types will be extracted from thesystem.
FIRE VALUES / SOURCE
Account Number Account Reference Number (Pipeline – AccountManagement – Basic Information)
Classification BDOI Booked or Submitted
Mortgaged Yes (if mortgaged) or No (for fully paid loan)
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
7/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
Classification: GENPACT Internal© All rights reserved. Copyright(2008-2014) Page 7 of 25
Loan PN Number Data uploaded from ICBS
Loan Outstanding Balance Data uploaded from ICBS
ICBS Date Date when the information from ICBS was uploaded tothe Broker System
BDO Branch Bank Unit (Pipeline – Account Management – Other
Information)/ Bank Branch (Pipeline – AccountManagement – Other Information)
Region Region (Pipeline – Account Management – OtherInformation)
Previous Account Number Previous / last BDOI Invoice Number
Loan Booking Data uploaded from ICBS
Maturity Date Data uploaded from ICBS
Account Name Last Name, Firs Name, Suffix, Middle Name (Pipeline – Client Administration - Client Name
Address House Number, Street, Barangay, City or Municipalityand Province (Pipeline – Client Administration –
Address)Contact Person Client type is Individual and Sole Proprietorship = ClientName Pipeline - Client Management – GeneralInformation). If Client is Corporation and Partnership =Contact Person (Pipeline - Client Management – Contact Person)
Contact Number Client type is Individual and Sole Proprietorship =Contact Number (all types) (Pipeline - ClientManagement – Contact Details). If Client is Corporationand Partnership = Contact Number (all) (Pipeline -Client Management – Contact Person)
Email Client type is Individual and Sole Proprietorship = Emailaddress (Pipeline - Client Management – GeneralInformation). If Client is Corporation and Partnership =Email address (all) (Pipeline - Client Management – Contact Person)
Previous InsuranceCompany
Last insurance company prior to renewal
Previous Policy Number Last policy number prior to renewal
Last Year Sum Insured Last sum insured prior to renewal
Last Year Premium Rate Last premium rate prior to renewal
Last Year Total Premium Total premium paid prior to renewal
Inception Date Inception Date (Pipeline – Account Management – RiskInfo)
Expiry Date Expiry Date (Pipeline – Account Management – RiskInfo)
Location of Risk Location of Risk (Pipeline – Account Management – Risk Details
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
8/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
Classification: GENPACT Internal© All rights reserved. Copyright(2008-2014) Page 8 of 25
MOTOR VALUES / SOURCE
Account Number Account Reference Number (Pipeline – AccountManagement – Basic Information)
Classification BDOI Booked or Submitted
Mortgaged Yes (if mortgaged) or No (for fully paid loan)
Loan PN Number Data uploaded from ICBS
Loan Outstanding Balance Data uploaded from ICBS
ICBS Date Date when the information from ICBS was uploadedto the Broker System
BDO Branch Bank Unit (Pipeline – Account Management – OtherInformation)/ Bank Branch (Pipeline – AccountManagement – Other Information)
Region Region (Pipeline – Account Management – OtherInformation)
Previous Account Number Previous / last BDOI Invoice Number
Loan Booking Data uploaded from ICBS
Maturity Date Data uploaded from ICBS
Account Name Last Name, Firs Name, Suffix, Middle Name (Pipeline – Client Administration - Client Name
Address House Number, Street, Barangay, City or Municipalityand Province (Pipeline – Client Administration – Address)
Contact Person Client type is Individual and Sole Proprietorship =Client Name Pipeline - Client Management – GeneralInformation). If Client is Corporation and Partnership =Contact Person (Pipeline - Client Management – Contact Person)
Contact Number Client type is Individual and Sole Proprietorship =Contact Number (all types) (Pipeline - ClientManagement – Contact Details). If Client is
Corporation and Partnership = Contact Number (all)(Pipeline - Client Management – Contact Person)
Email Client type is Individual and Sole Proprietorship =Email address (Pipeline - Client Management – General Information). If Client is Corporation andPartnership = Email address (all) (Pipeline - ClientManagement – Contact Person)
Last Year OD Theft Value
Previous InsuranceCompany
Last insurance company prior to renewal
Previous Policy Number Last policy number prior to renewal
Last Year Sum Insured Last sum insured prior to renewal
Last Year Premium Rate Last premium rate prior to renewalLast Year Total Premium Total premium paid prior to renewal
Inception Date Inception Date (Pipeline – Account Management – Risk Info)
Unit Description Motor Details (Pipeline – Account Management – RiskDetails
Serial Number Serial / Chassis Number (Pipeline – AccountManagement – Risk Details)
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
9/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
Classification: GENPACT Internal© All rights reserved. Copyright(2008-2014) Page 9 of 25
Motor Number Motor Number (Pipeline – Account Management – Risk Details)
Color Color (Pipeline – Account Management – RiskDetails)
Plate Number Plate Number (Pipeline – Account Management –
Risk Details)
MRI VALUES / SOURCE
Account Number Account Reference Number (Pipeline – Account Management – Basic Information)
Booking Date Date booked in the system
Maturity Date Last date of the duration of coverage
BranchDescription
Bank Unit (Pipeline – Account Management – OtherInformation)/ Bank Branch (Pipeline – Account Management – Other Information)
Business Origin Business Origin (Pipeline – Account Management – OtherInformation)
Officer Code Bank Officer (Pipeline – Account Management – OtherInformation)
Account Officer BDOI Account Officer (Pipeline – Account Management – OtherInformation)
Mailing Address Billing Address (Pipeline – Account Management – BasicInformation)
Address House Number, Street, Barangay, City or Municipality andProvince (Pipeline – Client Administration – Address)
Contact Person Client type is Individual and Sole Proprietorship = Client NamePipeline - Client Management – General Information). If Client isCorporation and Partnership = Contact Person (Pipeline - ClientManagement – Contact Person)
Contact Number Contact Number (all types) (Pipeline - Client Management)
Email Client type is Individual and Sole Proprietorship = Email address(Pipeline - Client Management – General Information). If Clientis Corporation and Partnership = Email address (all) (Pipeline -Client Management – Contact Person)
Birthdate Birthdate of enrollees (Pipeline – Account Management – RiskDetails)
Age Computed by the system based on birthdate date and date ofdata extraction
InsuranceCompany
Insurer (Pipeline – Account Management – Insurance/Co-BrokerDetails)
Policy Number Policy Number after placement
Assured’s Name Assured Name (Pipeline – Account Management – Basic
Information)Current YearBalance
Current Rate
Current DST
Current Premium Premium (Pipeline – Account Management – Risk Info)
Next Year Balance
Next Rate
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
10/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
Classification: GENPACT Internal© All rights reserved. Copyright(2008-2014) Page 10 of 25
Next DST
Next Premium
Inception Date Inception Date (Pipeline – Account Management – Risk Info)
Expiry Date Expiry Date (Pipeline – Account Management – Risk Info)
OR Number OR Number generated after payment
The following additional columns will be added to the extract file based on the followingconditions where the Insurance Companies and BDOI Units can indicate their reply,confirmation or comments which will be uploaded to the broker system. This will bediscussed further in the succeeding sections of this document.
Extract files will be generated in EXCEL format. The system will disregard the versionrelease of the application installed in the workstation of the users.
3. System validation to extract information for confirmation. The following conditions shouldbe present before accounts can be included in the extraction:
EXTRACT FILE DATA COLUMNS CONDTION REMARKS
InsurerConfirmation
Insurer Feedback Transaction diary is checked orunchecked
Free text
TransactionDiary
Transaction Diary Transaction diary is checked Free text
User ID Transaction diary is checked Free text
CONDITION REMARKS
Accounts have beenIDENTIFIED FOR RENEWAL
Records that will be included in theextraction are only those that havebeen determined to be FORRENEWAL based on the sanitationprocess of Consumer LendingGroup and Marketing. Please referto the respective RSD regarding theprocess in determining accountsthat are due for renewal.
There is change in theOLD/EXISTING RATES,OLD/EXISTING BASICPREMIUM and OLD TOTALPREMIUM
There is no data indicated in theINSURER CONFIRMATION fieldin Pipeline – Insurer Feedback
tab
Found in Pipeline – InsurerFeedback tab
Pipeline Status of the accountMAY OR MAY NOT be AWAITING FOR INSURER’SFEEDBACK.
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
11/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
Classification: GENPACT Internal© All rights reserved. Copyright(2008-2014) Page 11 of 25
4. System facility to establish the type of extract file. Since the information that will beextracted will differ depending on who is the target recipient of the file, a header code willbe placed in each extract file. As discussed in the main section of the RSD, uploading willbe through a centralized module but the format of the extract and upload file will differbased on the data per process per module that will be uploaded to the broker system.
Below is the proposed naming convention for the header code.
EXTRACT FILE HEADER CODE
Insurer Confirmation XYZA
Transaction Diary XZA
WHERE:
HEADER CODER DESCRIPTION
X I = Insurer Confirmation, T = Transaction Diary
Y F = Fire, M = Motor and MR = MRI
Z Date (MMDDYYYY format) of extraction A Time stamp (HH:MM:SS format)
5. System facility to keep temporary record of files that have been extracted. The system willkeep records or logs of HEADER CODE and TOTAL RECORDS per extracted file. Thesewill be compared when the same extract files will be uploaded to the system. To illustrate:
If there are 200 accounts with product type Fire that are due for renewal for the month ofJanuary that will be extracted based on current date of January 21, 2015 at 3 pm, thesystem will generate header code of IF0121153:00:00 which will be placed on the headerof the extract file. The system will also log IF0121153:00:00 with 200 records in thedatabase. During uploading, the system will validate if IF0121153:00:00 is a valid file by
comparing the header code and the total number of records as against those that havebeen logged.
HEADER CODER NUMBER OF RECORDS
IF0121153:00:00 200
6. System facility to allow duplicate extraction of accounts. The system will allow the user toextract accounts as many times depending on his needs subject to the conditionsmentioned in the preceding regarding the inclusion of accounts in the extraction.
7. System facility to automatically save and indicate filename of the extracted file. Thesystem 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 STATUS LOCATION FILENAME
Insurer confirmation Extracted \\BDOI\Extracted\ InsurerConfirmation and Transaction Diary
XYZAB
FIRE Extracted \\BDOI\Extracted\Insurer Confirmationand Transaction Diary\Fire
XFZABC
MOTOR Extracted \\BDOI\Extracted\Insurer Confirmationand Transaction Diary\Motor
XMZABC
http://bdoi/Extracted/http://bdoi/Extracted/Insurer%20Confirmation%20and%20Transaction%20Diary/http://bdoi/Extracted/Insurer%20Confirmation%20and%20Transaction%20Diary/http://bdoi/Extracted/Insurer%20Confirmation%20and%20Transaction%20Diary/http://bdoi/Extracted/Insurer%20Confirmation%20and%20Transaction%20Diary/http://bdoi/Extracted/Insurer%20Confirmation%20and%20Transaction%20Diary/http://bdoi/Extracted/Insurer%20Confirmation%20and%20Transaction%20Diary/http://bdoi/Extracted/Insurer%20Confirmation%20and%20Transaction%20Diary/http://bdoi/Extracted/Insurer%20Confirmation%20and%20Transaction%20Diary/http://bdoi/Extracted/
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
12/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
Classification: GENPACT Internal© All rights reserved. Copyright(2008-2014) Page 12 of 25
WHERE:
8. System facility to prompt system message after records have been extracted. The userwill be prompted of a system message informing of the NUMBER OF RECORDS thathave been extracted and the LOCATION of the extract file.
2.1.2 UI Wireframe
DATA EXTRACTION MENU
BDO Insurance Broker System Date / Time
DATA EXTRACTION A010000952
INSURER CONFIRMATION AND TRANSACTION DIARY
EXTRACT CLOSECLEAR ALL
MRI Extracted \\BDOI\Extracted\Insurer Confirmationand Transaction Diary\MRI
XMRZABC
CODE VALUE REMARKS
X I = Insurer Confirmation, T = TransactionDiary
If Transaction Dairywas checked in theextraction parameters,X = T
Y F = Fire, M = Motor, MR = MRI
Z Start Month (MM format) ) indicated in the filteroptions during extraction
A End Date (MM) format) indicated in the filteroptions during extraction
B Date extracted (MMDDYYYY format)
C Timestamp (HH:MM:SS format)
http://bdoi/Extracted/Insurer%20Confirmation%20and%20Transaction%20Diary/http://bdoi/Extracted/Insurer%20Confirmation%20and%20Transaction%20Diary/http://bdoi/Extracted/Insurer%20Confirmation%20and%20Transaction%20Diary/http://bdoi/Extracted/Insurer%20Confirmation%20and%20Transaction%20Diary/
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
13/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
Classification: GENPACT Internal© All rights reserved. Copyright(2008-2014) Page 13 of 25
DATA EXTRACTION PARAMETERS
DATA EXTRACTION PARAMETERS A010000952
BDO Insurance Broker SystemDate / Time
EXTRACT CLOSECLEAR ALL
TOTAL SUM INSURED
INSURANCE COMPANY
FIREMOTORMRI
PACKAGED WITH CHANGES
START MONTHYEAR END MONTH
PRODUCT TYPE
PACKAGED WITHOUT CHANGES
PHP
FOR RENEWAL
TRANSACTION DIARY
DATA EXTRACTION CONFIRMATION MESSAGE
BDO Insurance Broker System Date / Time
DATA EXTRACTION A010000952
IF010301212015 consisting of 200 Records was saved to
\\BDOI\Extracted\Insurer and BDOI feedback confirmation\Fire
OK
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
14/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
Classification: GENPACT Internal© All rights reserved. Copyright(2008-2014) Page 14 of 25
2.1.3 Inputs and Outputs
DATA EXTRACTION MENU
DATA EXTRACTION PARAMETERS
DATA ELEMENT BEHAVIOR FORMAT RANGE OF VALUES REMARKS
Insurer Confirmation/Transaction Diary
Executablebutton
Directs the systemadministrator tothe DATAEXTRACTIONPARAMETERS.
DATA ELEMENT BEHAVIOR FORMAT RANGE OF VALUES REMARKS
Year Drop down Drop down will
reflect previous tocurrent yearsubject to thearchiving rulesdefined in thesystem.
Start Month Drop down January to December
End Month Drop down January to December
Product Type Drop down Fire, Motor and MRI
Insurance Company Drop down o Allo Particular
insurancecompany
User can indicatea particularinsurancecompany or maychoose all byselecting the ALLoption.
Packaged withchanges
Check box
Packaged withoutchanges
Check box
Total Sum Insured Data Entry Default value is 10Million
For Renewal Check box
Transaction Diary Check box
Clear All Executablebutton
Erases all valuesin the extractionparametersindicated by theuser.
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
15/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
Classification: GENPACT Internal© All rights reserved. Copyright(2008-2014) Page 15 of 25
D
AT A
EXTRACTION CONFIRMATION MESSAGE
2.1.4 Reports Specification
N/A
2.1.5 Business Requirements Mapping
ITEM # BR REQUIREMENTS FEATURES
BRM-UP01-RID1-001 User should be able to extractdata listed in section 2.1.1.2and based parametersdiscussed in 2.1.1.1 of thisdocument.
System facility to allow the user toextract data based on therequirements mentioned in thesection 2.1.1.1 and 2.1.1.2 of thisdocument.
BRM-UP01-RID1-001 User should be able to generateand save extracted data basedon the predefined repository.
System facility to extract and savedata to a predefined repository.
2.2 RID 2 Checking and validation of upload files
This function provides a facility in the system that will validate the format and completeness of theuploading files. The uploading files refer to the extract files where the INSURER’S CONFIRMATIONand/or TRANSACTION DIARY have been filled out by the Insurance Company or BDOI Unitsrespectively. These will be uploaded again to the system when replies, feedback or comments havebeen indicated in the upload file. The upload program will validate the format and contents of the fileto ensure that this complies with the system requirements before this is uploaded to the brokersystem.
Extract Executablebutton
Extractsdata/generatesextract file basedon the parametersindicated by the
user.Close Executable
buttonCloses the DataDATAEXTRACTIONPARAMETERWINDOW.
DATA ELEMENT BEHAVIOR FORMAT RANGE OF VALUES REMARKS
Message Display
Ok Executable
button
Closes the
EXTRACTIONCONFIRMATIONMESSAGE
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
16/25
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
17/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
Classification: GENPACT Internal© All rights reserved. Copyright(2008-2014) Page 17 of 25
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 beenprocessed will be automatically moved by the system from the FOR UPLOAD folder tothe PROCESSED folder.
The system will allow the user to upload files in MS OFFICE OR OPEN OFFICEFORMAT provided that these complied with the system requirements. The system willdisregard the version release of these applications.
3. System detection on the files due for uploading. Based on the date indicated in thefilename of the upload files, the system will prompt the user regarding files that should beuploaded. To illustrate:
Let us assumed that an extract file for product type fire and motor have been replied bythe insurance companies.
If the system date is January 1, 2014, user will be prompted of the following files thatshould 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 againstthe month of January.
In the case of files that have not been uploaded based on the date corresponding to itsfilename, the system will allow the user to upload these provided that the filename datesare 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 also be prompted of the following filesthat are due for uploading.
FIRE MOTORIF010301212015
IM010301212015
IF040501212015 IM040501212015
IF060703212015 IM060703212015
IF070904212015 IM070904212015
IF091207212015 IM091207212015
FIRE MOTOR
IF010301212015
IM010301212015
IF040501212015
IM040501212015
FIRE MOTOR
IF010301212015 IM010301212015
IF040501212015 IM040501212015
IF060703212015 IM060703212015
IF070904212015
IM070904212015
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
18/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
Classification: GENPACT Internal© All rights reserved. Copyright(2008-2014) Page 18 of 25
4. System checking on the validity of the upload files. The system will check if an upload fileis valid for uploading based on the LOGS OF HEADER CODE STORED IN THESYSTEM’S DATABASE AND THE TOTAL NUMBER OF RECORDS VERSUS THEHEADER CODE THE TOTAL RECORDS OF THE UPLOAD FILE. In case there is nomatch, the system will reject the entire upload file. To illustrate:
In the system’s database, the following are the logs of the extract files generated by thesystem.
If I upload a file whose header code indicates IF120904212015 the system will reject thisfile because the header code does not match any records in the system ’s database. Oneof the possible causes of the discrepancy is due to manual alteration made by the user onthe header code of the extract file. Unless, corrections will be made on the code, the userwill be barred from uploading the file. Similarly, if there is a match in the header code butthe total number of records does not match, the system will reject the upload file.
The system will allow uploading of the file with the same header code in cases that not allof the contents are not uploaded to the system due to errors (refer to section 2.3.1.1) butthere will be validation on the following:
5. System validation on the format of the contents of the upload file. The system will check ifthe contents of the upload file comply with the requisites of the system. The format shouldsatisfy the standards defined in the system to be considered as READABLE CONTENTS.Otherwise, the system will reject the file. The list of special characters allowed in thesystem and the required data formats can be found in the RSD for PIPELINE and theTECHNICAL DESIGN DOCUMENT that will be prepared by GENPACT.
6. System validation on the correctness and readability of the contents of the upload filethrough validation of HASH TOTAL versus RECORD COUNT. If there is a discrepancy onthe results of the validation, the system will REJECT the ENTIRE upload file.
7. System checking on the contents of the upload file. The system will validate the followingentries prior to uploading in the broker system.
FIRE TOTALRECORDS
MOTOR TOTAL RECORDS
IF010301212015 200 IM010301212015 100
IF040501212015 100 IM040501212015 300
IF060703212015 250 IM060703212015 350
IF070904212015 400 IM070904212015 180
VALIDATION REMARKS
Filename of the upload file The upload file will contain the same headercode but the filename will be different sincethe file was generated as an exception report.
Target data fields where the data willbe uploaded
The system will not allow the user to overwriteor supersede existing values in the data fieldthrough uploading. User has to delete orremove the existing data before a new datacan be uploaded.
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
19/25
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
20/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
Classification: GENPACT Internal© All rights reserved. Copyright(2008-2014) Page 20 of 25
DATA UPLOADING WINDOW
DATA UPLOAD A010000952
BDO Insurance Broker System Date / Time
CLOSEUPLOAD
IF010301212015 \\BDOI\For uploading\Insurer confirmation\Fire
IF010501212015 \\BDOI\For uploading\Insurer confirmation\Fire
IF010601212015 \\BDOI\For uploading\Insurer confirmation/Fire
SELECT ALL
FILE LOCATION
DATA VALIDATION RESULT MESSAGE
BDO Insurance Broker System Date / Time
DATA UPLOAD A010000952
Upload file IF070904212015 has no corresponding header code log in the system
OK
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
21/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
Classification: GENPACT Internal© All rights reserved. Copyright(2008-2014) Page 21 of 25
2.2.3 Inputs and Outputs
DATA UPLOADING MENU
DATA UPLOADING WINDOW
DATA VALIDATION RESULT MESSAGE
DATA ELEMENT BEHAVIOR FORMAT RANGE OF VALUES REMARKS
Insurer Confirmation Executablebutton
Directs the user tothe DATAUPLOADINGWINDOW
Transaction Diary Executablebutton
Directs the user tothe DATAUPLOADINGWINDOW
DATA ELEMENT BEHAVIOR FORMAT RANGE OF VALUES REMARKS
File Display Shows file foruploading perproduct type.
Location Display Shows location offiles for uploadingper product type
Select Check box If checked,includes the file foruploading.
Select All Check box If checked, selectsall file foruploading. Ifunchecked,deselects all datafor uploading.
Upload Executablebutton
Uploads the fileselected by theuser to the system.
Close Executablebutton
Closes the DATAUPLOADINGWINDOW
DATA ELEMENT BEHAVIOR FORMAT RANGE OF VALUES REMARKS
Message Display
Ok Executablebutton
Closes the DATAVALIDATIONRESULTMESSAGEWINDOW
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
22/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
Classification: GENPACT Internal© All rights reserved. Copyright(2008-2014) Page 22 of 25
2.2.4 Reports Specification
N/A
2.2.5 Business Requirements Mapping
ITEM # BR REQUIREMENTS FEATURES
BRM-UP01-RID2-001 The system shouldautomatically show or promptthe user regarding files to beuploaded.
System facility to detect andprompt the user due for uploadingbased on the predefined location inthe system.
BRM-UP01-RID2-002 The system should be able tovalidate if the upload file is validfor uploading to the brokersystem.
System facility to check if:o The format and contents
conforms to the systemrequirements
o The upload file has acorresponding extract file
through the header codevalidation.
2.3 RID 3 Uploading of files
This function provides a facility in the system that will upload the INSURER CONFIRMATION and/orTRANSACTION DIARY that have been provided and indicated by the Insurance and BDO unitsrespectively. This stage presumes that the file have already confirmed to be valid for uploading basedon 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 Insurer confirmation andTransaction diary upload file will be compared and matched if existing in the system.
If the above conditions are present, the system will upload the following information to the
broker system.
INSURER CONFIRMATION PIPELINE
Account Reference Number Account Reference Number
Insurance Company Insurance Company (this does not apply if onlythe transaction diary will be uploaded to thesystem)
TRANSACTION DIARY PIPELINE
Account Reference Number Account Reference Number
User ID User
INSURERCONFIRMATION
PIPELINE TARGET DATAFIELDS
REMARKS
Insurer Confirmation InsurerFeedback tab
o Insurance Companyconfirmation
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
23/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
Classification: GENPACT Internal© All rights reserved. Copyright(2008-2014) Page 23 of 25
2. System facility to generate exception reports. In the event that records in the upload filedid not meet the criteria mentioned in 2.3.1.1, an exception report consisting of the samedata columns indicated in the uploaded file will be saved and generated by the system to apredefined server directory. Below is the proposed repository of the exception report.
WHERE:
User will be allowed to upload an exception file by adding a target date of upload andplacing the file to the predefined path mentioned in section 2.2.1.1 of this document.
3. System generation of display message after uploading. The system will prompt the user ofa message indicating that ALL records have been uploaded successfully and if there areUNMATCHED records.
4. System display of history of uploaded files. User will be able to VIEW records of previousfiles that have been uploaded to the system
TRANSACTIONDIARY
PIPELINE TARGET DATAFIELDS
REMARKS
Transaction Diary History tab o Usero Entry
Date in theTransaction Diary
screen will beupdated basedon the date thefile was updated
FILE STATUS LOCATION FILENAME
Insurer Confirmation Unmatched \\BDOI\Unmatched\Insurer
Confirmation\
XYZAB
Transaction Diary Unmatched \\BDOI\Unmatched\TransactionDiary
XZAB
CODE VALUE
X I = Insurance Companies, T = Transaction Diary
Y F = Fire, M = Motor, MR = MRI
Z Start Month (MM format) ) indicated in the filter options during extraction
A End Date (MM) format) indicated in the filter options during extraction
B Date Generated (MMDDYYYY format)
C Timestamp (HH:MM:SS format)D E = Exception
http://bdoi/Unmatched/Insurer%20Confirmation/http://bdoi/Unmatched/Insurer%20Confirmation/http://bdoi/Unmatched/Insurer%20Confirmation/http://bdoi/Unmatched/Transaction%20Diaryhttp://bdoi/Unmatched/Transaction%20Diaryhttp://bdoi/Unmatched/Transaction%20Diaryhttp://bdoi/Unmatched/Transaction%20Diaryhttp://bdoi/Unmatched/Transaction%20Diaryhttp://bdoi/Unmatched/Insurer%20Confirmation/http://bdoi/Unmatched/Insurer%20Confirmation/
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
24/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
Classification: GENPACT Internal© All rights reserved. Copyright(2008-2014) Page 24 of 25
2.3.2 UI Wireframe
DATA UPLOADING CONFIRMATION/UNMATCHED RECORD MESSAGE WINDOW
BDO Insurance Broker SystemDate / Time
DATA UPLOAD A010000952
30 unmatched records from upload file IF070904212015 were not uploaded.Extract file was generated and saved to \\BDOI\Unmatched\Insurer Confirmation
OK
2.3.3 Inputs and Outputs
DATA UPLOADING CONFIRMATION/UNMATCHED RECORD MESSAGE WINDOW
2.3.4 Reports Specification
N/A
DATA ELEMENT BEHAVIOR FORMAT RANGE OFVALUES
REMARKS
Message Display
Closes Executablebutton
Closes DATAUPLOADINGCONFIRMATION/UNMATCHED RECORDMESSAGE WINDOW
-
8/19/2019 RSD All Market Segments_Insurer Confirmation and Transaction Diary_v1
25/25
Requirements Specification DocumentUploading requirements 01
Version 0.01
2.3.5 Business Requirements Mapping
ITEM # BR REQUIREMENTS FEATURES
BRM-UP01-RID3-001 User should be able toupload the following tothe broker system:
o InsurerConfirmation
o Transaction Diary
Facility to allow the user to uploadthe following to the broker system:
o Insurer Confirmationo Transaction Diary
BRM-UP01-RID3-002 The system should beable to match and
validate target data fieldsversus source data fieldsin the upload file.
System facility to match andvalidate target data fields versus
source data fields in the uploadfile.