Upload
others
View
5
Download
0
Embed Size (px)
Citation preview
Reply to Pre Bid Queries -RFP for EWS Solution
S. No. RFP Clause RFP Terms Clarification Sought Banks response
1 2. Objective
Page 4
Reverse integration Module to feedback the other systems Requesting the bank to provide an approximate number of
feedbacks that we need to support.
This approximation can be done only after
implementation and will be discussed with
successful vendor.
2 2. Objective
Page No.6
Last Date and Time of online e-tender
for the submission of Technical Bid and Price Bid.
Given the requirement of the RFP, requesting the bank to extend
the bid submission timelines to 3 weeks from the release of the pre-
bid response.
No change in RFP terms
3 2. Objective
Page No.6
#Table reference
Project Implementation Schedule: 180 days
As the scope of the RFP is very wide and includes integration with
various internal & external systems. 180 days timeline is very
stringent for the given scope. Hence requesting the bank to extend
the project timelines to 9 months.
No change in RFP terms
4 2. Objective
Page No.6
#Table reference
EWS license: 1000 users
Location of users will be decided by Bank across country.
Requesting the bank to provide the seggregation of users based on
Head Office, Regional Offices, Zonal Offices and branches.
This will be shared with the successful vendor.
5 2. Objective
Page No.6
#Table reference
EWS license: 1000 users
Location of users will be decided by Bank across country.
Requesting bank to provide the total number of named user access
required for monitoring of alerts.
This will be shared with the successful vendor.
6 2. Objective
Page No.6
#Table reference
Though Bank is providing the licenses for Databases i.e. SQL
and Oracle. But all necessary support related to database
Bidder has to provide. Bank will not provide any database
OEM or other support.
In case the bank is providing database licenses for Oracle or SQL, it
would not be possible for the bidder to provide support for the
same. The bank would have support available for the database
hence requesting the bank to arrange the support from the OEM
for database licenses.
No change in RFP terms
7 2. Objective
Page No.6
#Table reference
Hardware sizing to be provided by the bidders along with
technical proposal. Bank will provide the hardware. Rest of
the requirement to be supplied by the Bidder to make the
system live. Bidder should provide all software.
Requesting the bank to confirm that the bank will only provide
hardware and database license. All other required software and OS
to be provided by the bidder including KVM switches.
Bank will provide hardware and Hardware
AMC will rest with Bank. If vendor is not using
OS ( Windows/ Linux RedHat ) /DB provided
by Bank (SQL/Oracle) and proposing any
other OS and DB, the AMC pertaing to same
will be borne by the Vendor. Hardware
including KVM switches will be provided by
the Bank.
8 2. Objective
Page No.6
#Table reference
Hardware sizing to be provided by the bidders along with
technical proposal. Bank will provide the hardware. Rest of
the requirement to be supplied by the Bidder to make the
system live. Bidder should provide all software.
Is DR to be sized at 100% capacity of DC? Yes
Page 1 of 50
9 A. Introduction
3.1 General
Page No.10
3.1.2 In case BOI acquires or amalgamate or merge with any
Bank at any future date EWS Solution will also have to be
extended to such entity for which only imlementation cost
will be paid by the bank. Estimated no. of users for Bank will
be around 1000.
Typically no bidder or solution OEM provides the same license for
new entity in case of merger or amalgamation with other bank.
License has to be procured separately for the newly added entity.
Hence requesting the bank to drop this clause.
No change in terms of RFP. Application
License shoule be for 1000 users. After
amalgamation/merger with other Bank, bank
as entity will reamin one only and the total
number of users will be restricted to 1000
only.
10 Clause 3.1.2
Page 10
Estimated no. of users for Bank will be around 1000. This number of users would be for the additional entity/bank with
which the merger is expected or total number of users for the
merged entity. Kindly clarify
After amalgamation/merger with other Bank,
bank as entity will reamin one only and the
total number of users will be restricted to
1000 only.
11 3.2 Broad Scope of Work
Page No. 10
Historical data of 10 years will be migrated from CBS. Requesting the bank to provide the volume/size of such data to be
migrated from the CBS as this would be crucial for us to size
appropriate hardware and storage.
If need be all the historical data from
applicaions listed under clause 3.2.3.2 page 11
of RFP
12 3.2 Broad Scope of Work
Page No. 10
Solution must meet the RTO (recovery time objective) of 60
minutes and RPO (recovery point objective) of 30 minutes for
the solution
Requesting bank to consider the RPO of 60 minutes and RTO of 2
hours.
No change in RFP terms
13 Clause 3.2.3
Page 11
Risk Classification and Online as well as Present Customer
database screening against banned entities and Politically
Exposed Person (PEP)
These are items from a Customer's Anti-Money Laundering risk
score computation and to check if he/she exists within a Sanction
List, not typically required from an EWS Solution.
Kindly confirm if these modules would be required from an EWS
perspective by Bank of India.
No change in RFP terms
14 3.2 Broad Scope of Work
Page No. 11
3.2.3
The data provided to / made available to the Bank with the
aid of EWS solution should be precise, accurate and correct.
The MIS report should be generated by the Vendor as
detailed in Point 17under Reporting Module, page 84 of RFP.
The vendor holds full responsibility and shall be solely liable
for all the loss and consequences if any incurred by Bank due
to incorrect algorithm or incorrect logic applied by vendor or
the actions which are attributable to the Vendor.
All of the rules, logics and methods for red flagging of loan
accounts will be deployed in consultation with the bank during the
implementation. The bidder can not be held liable for any losse or
consequences due to incorrect logic. Hence requesing the bank to
drop this clause.
No such term in RFP.
15 3.2 Broad Scope of Work
Page No. 11
The EWS should include but not limited to the following
modules detailed later in the RFP
1. Data Integration Module,
2. Text Mining module,
3. Internet Scanner module,
4. Alerts Scoring module,
5. Reporting module,
6. Workflow module,
7. Audit module
Requesting the bank to provide more details on internet scanner
module.
The term internet scanner module is very wide and can mean any
information available on the internet. Requesting the bank to limit
this module to certain number of feeds or specific websites.
We envisage this capability in the Solution.
Page 2 of 50
16 3.2 Broad Scope of Work
Page No. 13
Financial Intelligence from Bank's internal sources:
a) Core Banking System (CBS): The Bank has envisaged to
upgrade the CBS in near future. Presently bank is having
Finacle 7i.
Requesting the bank to provide the estimated time range for the
CBS migration.
This is under process. The details will be
shared with the successful Vendor.
17 3.2 Broad Scope of Work
Page No. 14
The bidder is to propose the mandatory interfacing cost from
M/S Finacle (Core Banking Solution partner of the bank) as
part of the bidder’s commercial offering in the Commercial.
Getting integration cost for M/S Finacle might not be possible
during the RFP submission stage. Bidder can propose integration
cost and can coordinate with Finacle for integration.
No change in RFP terms, Bank will not pay
towards any separate or extra cost for
integration with M/s Finacle in existing
version of CBS as well as upon upgradation in
near future.
18 3.2.3.1 Financial
Statement Filing
Page 14
Inputs from periodic filings with the Banks such as
(indicative):
- Monthly Projections
- Quarterly Balance sheets
- Stock Statements
- Annual Audited Financial Statements
It is assumed that the bank is already capturing this information in
their Core System and it would be available for analysis in a
digitized format
Kindly confirm.
Please refer to functions under Data
Integration Capabilities: Data Entry Screen,
Page 66 of RFP.
19 3.2 Broad Scope of Work
Page No. 15
Financial and market Intelligence from Bank’s external
sources
The financial and market intelligence from external sources
that may be considered by bidders for their proposed EWS
Solution will involve data points such as:
Our understanding is that the bank will make available the
information from the external sources and data feeds. Kindly
confirm.
All Third Party external data from external
sources/ data aggregators will be provided to
the Vendor. Please also refer to page no. 15-
16 of RFP .
20 3.2 Broad Scope of Work
Page No. 16
Vendor to collect / extract the external data from sources
such as peer banks, stock exchanges, government websites,
credit bureau, stock exchanges, CERSAI, Rating Agencies,
information agencies, etc. through Data Aggregator by
entering into an Agreement with such Data Aggregator.
Membership/ subscription related to above services to be
taken by the bidder by suitably entering into an agreement
with such Data Aggregator to extract the data. Bank will make
the payment for the membership/ subscription fees on
reimbursement basis at actuals after verification.
The lists of Data Aggregator/Credit Bureau/ other external
data sources to be provided along with the technical bids with
details of such agencies. However the Bank reserves its right
to accept or reject or add other sources as deemed fit. In case
bank in its discretion finds the sufficient and important /
crucial data sources not covered in the list will advise the
vendor to include the same.
Requesting the bank to clarify whether the data mentioned here is
in addition to the list mentioned above in the RFP document?
No such term in RFP.
Page 3 of 50
21 3.2 Broad Scope of Work
Page No. 16
3.2.3.4 The main scope is implementation of Early Warning
Signals (EWS) solution is to have a report on market
intelligence and portfolio analysis of all Advance accounts
above Rs. 25 lakhs, its Inter Bank comparison /analysis &
dynamic monitoring through Auto Alert System, etc. and
recommendations forstrategic decisions at account/ portfolio
level.
Requesting the bank to provide the Total Number of Corporate
Customers with exposure greater than 25 lacs
- Listed Entities
- Unlisted Entities
Please refer to the data at the end of this
document.
22 3.2 Broad Scope of Work
Page No. 16
3.2.3.4 The main scope is implementation of Early Warning
Signals (EWS) solution is to have a report on market
intelligence and portfolio analysis of all Advance accounts
above Rs. 25 lakhs, its Inter Bank comparison /analysis &
dynamic monitoring through Auto Alert System, etc. and
recommendations forstrategic decisions at account/ portfolio
level.
Requesting the bank to provide the Total Number of SME
Customers with exposure greater than 25 lacs
- Listed Entities
- Unlisted Entities
Please refer to the data at the end of this
document.
23 3.2 Broad Scope of Work
Page No. 16
3.2.3.4 The main scope is implementation of Early Warning
Signals (EWS) solution is to have a report on market
intelligence and portfolio analysis of all Advance accounts
above Rs. 25 lakhs, its Inter Bank comparison /analysis &
dynamic monitoring through Auto Alert System, etc. and
recommendations forstrategic decisions at account/ portfolio
level.
Requesting the bank to provide the estimate of the number of
retail customer that are to be monitored under EWS.
Please refer to the data at the end of this
document.
24 3.2 Broad Scope of Work
Page No. 16
3.2.3.4 The main scope is implementation of Early Warning
Signals (EWS) solution is to have a report on market
intelligence and portfolio analysis of all Advance accounts
above Rs. 25 lakhs, its Inter Bank comparison /analysis &
dynamic monitoring through Auto Alert System, etc. and
recommendations forstrategic decisions at account/ portfolio
level.
Requesting the bank to provide the estimate of the number of
corporate customer that we are looking to monitor under EWS?
Please refer to the data at the end of this
document.
25 3.2 Broad Scope of Work
Page No. 16
3.2.3.4 The main scope is implementation of Early Warning
Signals (EWS) solution is to have a report on market
intelligence and portfolio analysis of all Advance accounts
above Rs. 25 lakhs, its Inter Bank comparison /analysis &
dynamic monitoring through Auto Alert System, etc. and
recommendations forstrategic decisions at account/ portfolio
level.
Requesting the bank to provide the estimate of the number of SME
customer that we are looking to monitor under EWS?
Please refer to the data at the end of this
document.
26 3.2 Broad Scope of Work
Page No. 16
3.2.3.4 The main scope is implementation of Early Warning
Signals (EWS) solution is to have a report on market
intelligence and portfolio analysis of all Advance accounts
above Rs. 25 lakhs, its Inter Bank comparison /analysis &
dynamic monitoring through Auto Alert System, etc. and
recommendations forstrategic decisions at account/ portfolio
level.
Requesting the bank to provide the breakdown of the number of
Corporate Customers (Listed / Non-Listed), SME, MSME,
Partnership etc.
Please refer to the data at the end of this
document.
Page 4 of 50
27 3.2 Broad Scope of Work
Page No. 16
3.2.3.4 The main scope is implementation of Early Warning
Signals (EWS) solution is to have a report on market
intelligence and portfolio analysis of all Advance accounts
above Rs. 25 lakhs, its Inter Bank comparison /analysis &
dynamic monitoring through Auto Alert System, etc. and
recommendations forstrategic decisions at account/ portfolio
level.
Requesting the bank to provide the profile wise distribution of the
corporate brorrowers i.e. how many are Public Ltd Cos/Pvt Ltd
Cos/Partnerships/Others(NGO etc).
Please refer to the data at the end of this
document.
28 3.2 Broad Scope of Work
Page No. 16
3.2.3.4 The main scope is implementation of Early Warning
Signals (EWS) solution is to have a report on market
intelligence and portfolio analysis of all Advance accounts
above Rs. 25 lakhs, its Inter Bank comparison /analysis &
dynamic monitoring through Auto Alert System, etc. and
recommendations forstrategic decisions at account/ portfolio
level.
Requesting the bank to provide the profile wise distribution of the
SME brorrowers i.e. how many are Public Ltd Cos/Pvt Ltd
Cos/Partnerships/Others(NGO etc).
Please refer to the data at the end of this
document.
29 3.2 Broad Scope of Work
3.2.3.7 Scope related to
service
Page No. 19
Post-implementation on-site support should be provided by
the vendor for warranty period of 2 year from the date of Go
Live and smooth handover of the System (On–site support
start date will be based on mutual agreement
between the vendor and the Bank) and 3 years under AMC.
How many resources are required for on-site support?
Please provide the following details:
1. No of Shifts:
2. Shift Timing:
3. L1 Resources / Shift:
4. L2 Resources / Shift:
5. L3 Resources / Shift (if any):
Only one On-stie support engineer (L1) will
be required.
a) Work timings will be 8 hours from 10 am
to6 p.m. on all working days.
b) The desktop will be provided by Bank
c) In case of any emergeny/ exigency, Services
to be provided for extra hours at no extra
cost.
E) the location of posting the onsite engineer
will be at Mumbai.
f) The duration of onsite support resources
will include both Warranty and AMC period.
g) Bank will make no separate payment.
towards on site support engineers, it should
be factored/included in Price BId. All
payments/ expenses/risks etc. towards
onsite support engineer resources to be borne
by vendor including insurance.
30 3.2 Broad Scope of Work
3.2.3.7 Scope related to
service
Page No. 20
Detailed documentation on system set up & configuration of
UAT, Production
(DC),Fallback (DR) and Near- DR (if any) environments.
Requesting the bank to provide the list of environments which
needs to maintained as part of project. Eg. Production, DR, UAT,
Development etc.
Bank will need all environments as mentioned
in RFP.
31 3.2 Broad Scope of Work
Support
Page No. 21
3.2.8 The solution provider (bidder) must ensure that the
solution given is compatible to integrate with our systems
especially the CBS used by all of our Branches
Requesting the bank to confirm that bank has single CBS installed
for all branches.
Yes, Bank has single CBS installed for all
branches.
Page 5 of 50
32 3.2 Broad Scope of Work
Support
Page No. 22
3.2.14 DC and DR should have at least one onsite support
engineers support
Our understanding is that the bank requires one onsite support
engineer combined at DC and DR (Not at least one resources
separately at both DC and DR). Kindly confirm if our understanding
is correct.
Only one support engineer resources will be
required in DC and DR collectively.
33 3.4 Eligibility Criteria
Page No. 22
3.4.3 The Bidder should have yearly sales turnover of not less
than Rs.50 Crores on standalone basis of the company during
the financial years FY 2015-16, 2016-17 and 2017-18.
As SMEs and MSMEs are allowed to bid for the RFP and it would be
very difficult for any SME/MSME to have 50 Crores turnover in the
last three years. Hence requesting the bank to change the criteria
to "The Bidder should have yearly sales turnover of not less than
Rs.10 Crores on standalone basis of the company during the
financial years FY 2015-16, 2016-17 and 2017-18."
No Change in RFP terms
34 3.4 Eligibility Criteria
Page No. 22
3.4.4 The bidder must be having positive net worth based on
standalone operations during the financial years FY 2015-16,
2016-17 and 2017-18.
As SMEs and MSMEs are allowed to bid for the RFP and it would be
very difficult for any SME/MSME to have positive net worth in the
last three years. Hence requesting the bank to change the criteria
to "The bidder should have positive Net worth as on 31-03-2018.
No Change in RFP terms
35 PART 5: TECHNICAL &
FUNCTIONAL
SPECIFICATIONS (TFS)
Page No. 66
4. The text mining utility should be capable of reading
documents in standard formats (Eg: .doc, .rtf, .odt, .pdf)
Our understanding is that the bank will provide the templates of
documents which needs to be read. Kindly clarify.
All standard formats to be available in
Solution. The formats may further be
customised based on RBI/statutory
bodies/Inspection/user requirements if any.
36 PART 5: TECHNICAL &
FUNCTIONAL
SPECIFICATIONS (TFS)
Page No. 69
25. The proposed solution should provide in-built feature of
Automated machine discovery to identify the core themes in
the input document collection with associated relevance
score
Requesting the bank to provide more details on "core themes"
mentioned in the statement.
By "core themes", does bank mean indentification of document
type. Please clarify.
Any informatin which is required for EWS is to
be captured.
Page 6 of 50
37 ANNEXURE C
5.3 Service Level
Agreement (SLA) and
Contracting
Page No. 149
5.3.1.8SLA for Software Support & Third Party Tools, if in use:
I. Any software bug identified by Bank/ vendor’s service
engineer would have to be fixed within the stipulated time
depending upon the criticality of the issue.
II. Software support for any new platform should be available
within six months.
Problem/Issue/Defect: This should be defined as any flaw
within the software system which does not allow the end user
to perform its regular operations as per the specifications /
operational guidelines /functionality requirements in a
stipulated timeframe.
Category: Problem/Issue/Defect
Severity: Critical
Problem Analysis & Response: 1 hour
Timeframe for Resolution / workaround (inclusive of
Response Time): 3 hours
Severity: High
Problem Analysis & Response: 1 hour
Timeframe for Resolution / workaround (inclusive of
Response Time): 8 hours
Severity: Low
Problem Analysis & Response: 1 hour
Timeframe for Resolution / workaround (inclusive of
EWS solution is typically runs in the background for monitoring
loan accounts and credit facilities. EWS is integrated with various
internal and external data sources which provides data in batches
and EWS solution run on EOD. Any issue occurred in the solution
will not adversely impact the red flagging of loan account. Hence
issue resolution timelines does not have to very stringent as
mentioned in the RFP.
Requesting the bank to modify the issue resolution timelines to as
per below:
Severity: Critical
Problem Analysis & Response: 1 hour
Timeframe for Resolution / workaround (inclusive of Response
Time): 24 hours
Severity: High
Problem Analysis & Response: 2 hours
Timeframe for Resolution / workaround (inclusive of Response
Time): 2 days
Severity: Low
Problem Analysis & Response: 2 hours
Timeframe for Resolution / workaround (inclusive of Response
Time): 10 days
No change in RFP terms.
38 7.16 Payment Terms
Page No. 145
On delivery of product, execution of Agreements and
submission of all documents including Performance Bank
Guarantee: 20% of total cost
"On delivery of product, execution of Agreements and submission
of all documents including Performance Bank Guarantee: 20% of
total cost"
No change in RFP terms
39 7.16 Payment Terms
Page No. 145
On due performance and completion of project and after
completion of warranty period. It is made clear That in case
Vendor commits default/ breach in the performance of
contract, the Bank shall have absolute right to retain the 10%
retention amount and without recourse to the vendor, Bank
can appropriate towards the loss / damage/ penalty incurred:
10% of total cost
As the bidder will submit the performance bank gaurantee which
provides insurance to the bank against default/breach in the
performance contract. Also, bidder's legal and finance function
would not approve of 10% retention of the payment. Hence
requesting the bank to drop the clause regarding 10% retention of
the payment.
No change in RFP terms
Page 7 of 50
40 7.16 Payment Terms
Page No. 145
On delivery of product, execution of Agreements and
submission of all documents including Performance Bank
Guarantee: 20% of total cost
On completion of customization as per requirement of Bank &
successful completion of UAT: 20% of total cost
Implementation, go-live of Solution as per the scope of RFP-
15% payable 3 months after Go Live and 15% payable 6
months after Go Live i.e. at Sign Off.
After successful completion of installation, commissioning,
acceptability test, receipt of deliverables, etc., and after the
solution runs successfully for six months after going live and
Bank is satisfied with the working on the system, the
acceptance certificate (as mutually decided and approved by
the Bank) signed by the Supplier (Vendor) and the
representative of the Purchaser (Bank) will be issued. The
date on which such certificate is signed shall be deemed to be
the date of successful commissioning (or Sign off) of the
systems as per Bank’s Format 6.9.: 30% of total cost
Completion of training & handing over of all documents and 6
months after Sign Off: 20% of total cost
On due performance and completion of project and after
completion of warranty period. It is made clear That in case
Requesting the bank to change the payment terms as below:
On delivery of product license, execution of Agreements and
submission of all documents including Performance Bank
Guarantee: 30% of total cost
On completion of customization as per requirement of Bank &
successful completion of UAT: 30% of total cost
On go-live of the EWS solution as per the RFP scope: 20% of total
cost
Completion of training & handing over of all documents and 6
months after Sign Off: 20% of total cost
No change in RFP terms
40 General General Requesting the bank to provide details on the below queries for us
to size hardware appropriately:
Core Banking System (for current year , after 1 year and after 2
years)
Core Banking System Name, Version and Vendor
Total Number of Corporate Customers
Total Number of Current Accounts of Corporate Customers (as in c)
Total Number of Loan Account / Credit Facilities held by these
customers (as in c)
Total Number of transactions for Deposits and Credit Accounts in a
day, month and year for these customers (as in c)
Total Number of Corporate Customers ith exposure greater than 50
crores
Total Number of Current Accounts of Corporate Customers (as in g)
Total Number of Loan Account / Credit Facilities held by these
customers (as in g)
41
Please refer to the data at the end of this
document.
General General
Page 8 of 50
42 General General Trade Finance (for current, after 1 year and after 2 years) (Please
replicate this section for all the products / channels in project
scope)
Trade Finance System Name and Vendor
Total number of Accounts in Trade Finance System
Total transactions volume per day, month and year
Average TPS of all transactions in Trade Finance System
Peak TPS of all transactions in Trade Finance System
Expected YOY growth rate of transactions
General General Treasury (for current, after 1 year and after 2 years) (Please
replicate this section for all the products / channels in project
scope)
Treasury System Name and Vendor
Total number of Account in Treasury
Total transactions volume per day, month and year
Average TPS of all transactions in Treasury
Peak TPS of all transactions in Treasury
Expected YOY growth rate of transactions
General General LMS (for current, after 1 year and after 2 years) (Please replicate
this section for all the products / channels in project scope)
LMS Name and Vendor
Total number of Account in LMS
Total transactions volume per day, month and year
Average TPS of all transactions in LMS
Peak TPS of all transactions in LMS
Expected YOY growth rate of transactions
General General CAPS (for current, after 1 year and after 2 years) (Please replicate
this section for all the products / channels in project scope)
CAPS Name and Vendor
Total number of Account in CAPS
Total transactions volume per day, month and year
44
45
Please refer to the data at the end of this
document.
Please refer to the data at the end of this
document.
Please refer to the data at the end of this
document.
Please refer to the data at the end of this
document.
43
Page 9 of 50
Average TPS of all transactions in CAPS
Peak TPS of all transactions in CAPS
Expected YOY growth rate of transactions
General General System X (for current, after 1 year and after 2 years) (Please
replicate this section for all the products / channels in project
scope)
System X Name and Vendor
Total number of Account in System X
Total transactions volume per day, month and year
Average TPS of all transactions in System X
Peak TPS of all transactions in System X
Expected YOY growth rate of transactions
47 Page no. 6 Threshold: The EWS solution should have full capability of any
exposure above Rs. 25 lakhs.
Please provide the number of customers who are greater than 25
lakhs exposure. This information will be useful in sizing the
hardware requirement optimally.
Please refer to the data at the end of this
document.
48 Clause 3.1.1 General Page
10
To comply with the guidelines of EASE / Reserve Bank of India
(RBI), Bank of India (hereinafter referred to BOI) wishes to put
in place end to end comprehensive IT Solution for Early
Warning Signals (EWS) to be implemented in Bank. It should
be in line with the Government / regulatory /anti money
laundering requirements as prescribed from time to time,
hosted at Bank’s Data Centre (DC) in Active / Passive mode,
along with DR and a
minimum uptime time of 99.50%.
please confirm DC should be in active mode and DR in passive
mode ensuring 99.5% availability.
Yes, DC should be active mode and DR in
passive mode and a minimum uptime of
99.50%. Please refer to the corrigendum.
49 Clause 3.8
Installation/Commissionin
g of Hardware/Software
Page 56
Hardware sizing to be provided by the bidders along with
technical proposal. Bank will provide the hardware. Rest of
the requirement to be supplied by the Bidder to make the
system live. Bidder should provide all software. In case of
oracle database Bank will provide necessary licenses. Though
Bank is providing the licenses for Databases i.e. SQL and
Oracle. But all necessary support related to database Bidder
has to provide. Bank will not provide any database OEM or
other support.
In addition to Database, whether bank will also provide OS and
application server software like Jboss/ Websphere, etc.
No.
Bank will provide only Windows/ Linux
RedHat Operating System. In case of any other
OS/ Middleware/ thrird party utility, price to
be quoted.
50 A. Introduction (Broad
Scope of Work) Page no:
10, Point no: 3.2.1
Historical data of 10 years will be migrated from CBS Based on our past experience on similar projects, historical data
migration for 10 years is not undertaken. This will have a major
impact on cost & project timelines as core banking/DB versions etc
may have undergone a change. Bank may please reconsider the
same. On a need basis, we can look at past data for reasonable
time period
No change in RFP terms.
45
46
Please refer to the data at the end of this
document.
Please refer to the data at the end of this
document.
Page 10 of 50
51 Clause 4.28 Termination
for Convenience Page 51
In addition to the right of the Bank to terminate the contract
for the delayed/unsatisfactory/nonperformance of the
Vendor and/or for various reasons detailed in the Service
Level Agreement to be executed with the Bank, the Bank shall
also be entitled to terminate the Contract at any time for its
convenience by giving one month notice to the Vendor. It is
hereby clarified that the termination for convenience shall be
without any compensation to the Vendor.
Termination needs to be for a reason or cause and the same to be
communicated to the vendor, please modify the clause accordingly
No change in RFP terms.
52 Clause 4.2.2 Country of
Origin / Eligibility of
Goods & Services Page 40
For purposes of this clause, “origin” means the place where
the goods are mined, grown, or manufactured or produced,
or the place from which the related services are supplied.
Goods are produced when, through manufacturing,
processing or substantial and major assembly of components,
a commercially-recognized product results that is
substantially different in basic characteristics or in purpose or
utility from its components.
Mention of 'goods' not in terms of software or software product,
please modify the clause suitably
No change in RFP terms.
53 Clause 5.3.1.7 Page 149 For any delay in implementation of this project, the Bank
reserves the right to charge Liquidated Damages (LD)/ penalty
at the rate of 1% of the cost of the Purchase Order per week,
subject to a maximum of 10% of the Purchase Order Value
and the amount will be recovered from any other amount due
to the Vendor or by invoking the Performance Bank
Guarantee (PBG).
We request the bank to modify the LD to a penaty rate of .5%,
subject to a maximum of 5%
No change in RFP terms.
Page 11 of 50
54 3.2 Broad Scope of Work
page 10
Onsite support from the bidder will be till date of go-live and
afterwards two dedicated resource i.e. onsite support
engineers(L1 and L2) will be onsite for support.
i) Please clarify the duration of placement of onsite support
engineers L1 & L2 (two dedicated resources). Will it cover both
warranty and AMC period.
Ii) Please specify the location for posting the onsite engineers
Only one On-stie support engineer (L1) will
be required.
a) Work timings will be 8 hours from 10 am
to6 p.m. on all working days.
b) The desktop will be provided by Bank
c) In case of any emergeny/ exigency, Services
to be provided for extra hours at no extra
cost.
E) the location of posting the onsite engineer
will be at Mumbai.
f) The duration of onsite support resource will
include both Warranty and AMC period.
g) Bank will make no separate payment.
towards on site support engineers, it should
be factored/included in Price BId. All
payments/ expenses/risks etc. towards
onsite support engineer resources to be borne
by vendor including insurance.
55 3.2 Broad Scope of Work
page 22
3.2.14 DC and DR should have at least two onsite support
engineers support (L1 and L2) during office hours of the bank
and in case of exigencies of the bank can request for extra
hours.
How many onsite engineers (L1 & L2 support) to the posted at DC &
DR sites respectively? Please clarify.
Only one support engineer resource will be
required in DC and DR collectively.
56 3.2 Broad Scope of Work 3.2.15 DC and DR should have at least two onsite support
engineers support (L1 and L2) during office hours of the bank
and in case of exigencies of the bank can request for extra
hours.
Please provide the payment terms for onsite support engineers.
We request the bank to consider monthly payment basis for onsite
support engineers.
Bank will make no separate payment.
towards on site support engineers it should be
factored/included in Price BId. All payments/
expenses/risks etc. towards onsite support
engineer resources to be borne by vendor
including insurance.
Page 12 of 50
57 4.38
Installation/Commissionin
g of hardware/ Software -
page 55
Project Implementation Schedule -
Business Requirement Document (BRD) & System
Requirement Specification (SRS) - Within 30 days
Customization & installation - 30-45 days
Data Collection & Integration - 45-75 days
UAT - 75-135 days
UAT – System Validations & Report Generation - 135-165 days
Go-Live - Within 180 days from Purchase Order (PO)
As per the proposed implementation schedule of RFP, 4 months is
consumed for UAT & Go-live. Only 2 months is available for BRD,
installation, customization, data collection and integration which is
practically not feasible given the scope of technical and functional
specifications.
We request the bank to please consider:
45 days for BRD/SRS
90 days for customization & installation,
140 days for Data collection & Integration
45 days for UAT
45 days for Go-live
TOTAL: 365 days/ 12 MONTHS
The changes if any proposed in
implementation schedule, will be discussed
with the successful vendor while executing
SLA. There will not be allowed any change in
outer limit of 180 days given for complete
implementation including Go Live. The Vendor
will be allowed to give any combination of
milestones within outer limit of 180 days.
Accordingly, the penalty clause in relation to
the dealy in implementation will be linked to
the milestones proposed by successful bidder
for complete implementation including Go
Live within 180 days from PO. In case, while
executive SLA, both Bank and the successful
Vendor are not mutually agreed on the
proposed changes in schedule, the
implementation schedule given in RFP will be
final.
58 CONFORMITY TO
ELIGIBILITY CRITERIA -
page 123-126
11 . The application software offered by the system integrator
or bidder should have adequate redundancy, fault tolerance
and Disaster recovery arrangement - A certificate to that
effect from any of the clients must be submitted.
Please provide the format of certificate to be obtained from OEM
to meet the requirement of this clause.
Any suitable format given by the OEM is
acceptable.
59 Data sources involved for
the solutions - page 11
3.2.3.2 Data sources involved for the solutions are as follows:
10. AML
11. EFRMS
1) Whether AML & EFRMS is operational in Bank of India.
2) Please provide name of OEM for AML & EFRMS solution.
1. Yes
2. this will be shared with the successufl
vendor.
60 Part II - Schedule for Annual Maintenance Cost page 109Annual Maintenance Charges and ATS for one years,
including Upgrades(AMC/ATS for software must be 18% to
21% of the total of cost of Software (A) & System Integration
(B) as
mentioned in Format 6.3 part I, per annum) for each item
(GST to be excluded)
Please clarify this condition?
AMC/ATS for software must be 18% to
21% of the total of cost of Software (A) & System Integration (B).
No change in RFP terms.
Page 13 of 50
61 7.16 Payment Terms Payment for the Supply of required Software, Design,
Installation,
Implementation, configuration, integration and Commission
of the EWS
Solution shall be made as per Scope of Work.
Milestone 1 - On delivery of product, execution of
Agreements and submission of all documents including
Performance
Bank Guarantee - 20% of total cost
Milestone 2 - On completion of customization as per
requirement of Bank & successful completion of UAT - 20% of
total cost
Milestone 3 - Implementation, go-live of Solution as per the
scope
of RFP- payable after 6 months after Go Live and
Sign off - 30% of total cost
Milestone 4 - Completion of training & handing over of all
documents and 6 months after Sign Off. - 20% of total cost
Milestone 5 - On due performance and completion of project
and
after completion of warranty period - 10% of total cost
we reqeust the Bank to release the payment for milestones - 3, 4,
& 5 within 30 days after completion of respective milestones to
avoid negative cashflow for the project.
Please confirm on the above.
No change in RFP terms.
62 Part 5 ( Technical and
Functional Specifications)
Page no: 82 , Point no: 13
Structuring Please explain the required functionality in more detail This is self explainatory. We envisage this
capability in the system.
63 Part 5 ( Technical and
Functional Specifications)
Page no: 82 , Point no: 13
Flow through Please explain the required functionality in more detail This is self explainatory. We envisage this
capability in the system.
64 Part 5 ( Technical and
Functional Specifications)
Page no: 82 , Point no: 15
Circulation of Funds Please explain the required functionality in more detail This is self explainatory. We envisage this
capability in the system.
65 Part 5 ( Technical and
Functional Specifications)
Page no: 82 , Point no: 15
The solution should support both online and off line data
validations and alerts
Online validation would require interfacing with the bank's systems
on a real time basis. Bank please provide the required interfaces in
co-ordination with the vendors. Kindly confirm.
Yes, The Bank will provide the required
Interface.
66 Part 5 ( Technical and
Functional
Specifications)Page no:
65, Point no: 1
The EWSS should provide for transformation rules library that
can be generic to a data source and which is reusable for
creating other transformation rules. The transformation rules
are expected to help clean, standardize, match and enhance
data as it moves into the master reference file and is reused
for downstream processes.
It is not part of standard EWS solution and relates to Data
Warehousing/Data Management. This will have an impact on the
cost of solution offerred and project timelines. In order to optimize
the same, bank may please consider removing the same.
No change in RFP terms.
Page 14 of 50
67 Part 5 ( Technical and
Functional
Specifications)Page no:
65, Point no: 4
EWS should have user interfaces for Data Profiling, Data
Standardization, and Clustering and Data Augmentation
capabilities. In Data Profiling it should be able to conduct the
following analysis :
Structure discoveries
Frequency distribution
Pattern distribution
Various Statistical Analysis
Redundant Data Analysis
It is not part of standard EWS solution and relates to Data
Warehousing/Data Management. This will have an impact on the
cost of solution offerred and project timelines. In order to optimize
the same, bank may please consider removing the same.
No change in RFP terms.
68 Part 5 ( Technical and
Functional Specifications)
Page no: 65, Point no: 6
Should support data cleansing and de-duplication, duplicate
suspect processing, house holding, with array of out-of-the-
box standardization rules conform data to corporate
standards – or can build customized rules for special
situations.
It is not part of standard EWS solution and relates to Data
Warehousing/Data Management. This will have an impact on the
cost of solution offerred and project timelines. In order to optimize
the same, bank may please consider removing the same.
No change in RFP terms.
69 Part 5 ( Technical and
Functional
Specifications)Page no:
65, Point no: 7
Should have business rules and GUI’s for automatic
merging and manual merging. It is not part of standard EWS solution and relates to Data
Warehousing/Data Management. This will have an impact on the
cost of solution offerred and project timelines. In order to optimize
the same, bank may please consider removing the same.
No change in RFP terms.
70 Part 5 ( Technical and
Functional Specifications)
Page no: 65, Point no: 8
The EWS should provide for Master Data Management with
semantic data descriptions of input and output data sources
uniquely identify each instance of a business element
customer, account, etc. and standardize the master data to
provide a single source of truth.
It is not part of standard EWS solution and relates to Data
Warehousing/Data Management. This will have an impact on the
cost of solution offerred and project timelines. In order to optimize
the same, bank may please consider removing the same.
No change in RFP terms.
71 Part 5 ( Technical and
Functional Specifications)
Page no: 67, Point no: 2
The EWSS must have facility to de-dupe information tagged to
a particular entity. It is not part of standard EWS solution and relates to Data
Warehousing/Data Management. This will have an impact on the
cost of solution offerred and project timelines. In order to optimize
the same, bank may please consider removing the same.
No change in RFP terms.
72 Part 5 ( Technical and
Functional Specifications)
Page no: 68, Point no: 19
EWSS should have the capability to automatically score the
text for early warning indicators.
This requirement is not clear. Please explain the requirement in
more detail
This is self explainatory. We envisage this
capability in the system.
73 Part 5 ( Technical and
Functional Specifications)
Page no: 69, Point no: 22
The proposed solution should provide an in- built ability to
create, modify and enable (or disable) custom concepts and
test linguistic rule definitions with validation checks within
the same interactive interface
It is not part of standard EWS solution and is typically a part of high-
end text mining products, impacting cost of solution offered and
timelines. In order to optimize the same, bank may please consider
removing the same.
No change in RFP terms.
74 Part 5 ( Technical and
Functional Specifications)
Page no: 69, Point no: 25
The proposed solution should provide in-built feature of
Automated machine discovery to identify the core themes in
the input document collection with associated relevance
score
It is not part of standard EWS solution and is typically a part of high-
end text mining products, impacting cost of solution offered and
timelines. In order to optimize the same, bank may please consider
removing the same.
No change in RFP terms.
Page 15 of 50
75 Part 5 ( Technical and
Functional Specifications)
Page no: 69, Point no: 26
The proposed solution should include a Predefined list of
concepts to automatically identify common definitions like
company, person, date, location, time, etc. - without a need
to add rules from scratch for them
It is not part of standard EWS solution, impacting cost of solution
offered and timelines. In order to optimize the same, bank may
please consider removing the same.
No change in RFP terms.
76 Part 5 ( Technical and
Functional Specifications)
Page no: 70, Point no: 40
The proposed solution should provide one integrated user
interface and workbench for data wrangling, data
exploration, business intelligence and visualization, feature
engineering, and modern statistical, data mining and
machine learning techniques all in a single, integrated in-
memory processing environment for faster insights, flexible
deployment and reliable and secure governance.
It is not part of standard EWS solution and relates to Data
Warehousing/Data Management. This will have an impact on the
cost of solution offerred and project timelines. In order to optimize
the same, bank may please consider removing the same.
No change in RFP terms.
77 Part 5 ( Technical and
Functional Specifications)
Page no: 70, Point no: 43
The proposed solution should provide out-of-box entity
analytics and direct intelligence analysts by showing
measures of centrality in entity networks - such as
closeness, betweenness and influence to highlight
suspicious borrowers/directors.
It is not part of standard EWS solution. This will have an impact on
the cost of solution offerred and project timelines. In order to
optimize the same, bank may please consider removing the same.
No change in RFP terms.
78 Part 5 ( Technical and
Functional Specifications)
Page no: 70, Point no: 44
The proposed solution should help analysts to visualize
complex network of relationships between entities - such as
people, organizations, places/ locations, things and events
over time and across multiple dimensions
It is not part of standard EWS solution. This will have an impact on
the cost of solution offerred and project timelines. In order to
optimize the same, bank may please consider removing the same.
No change in RFP terms.
79 Part 5 ( Technical and
Functional Specifications)
Page no: 70, Point no: 45
The proposed solution should help analysts identify entity
relationships that aren’t obvious, traverse and query
complex relationships, and uncover patterns and
communities interactively
It is not part of standard EWS solution. This will have an impact on
the cost of solution offerred and project timelines. In order to
optimize the same, bank may please consider removing the same.
No change in RFP terms.
80 Part 5 ( Technical and
Functional Specifications)
Page no: 71, Point no: 48
The proposed solution should have in-built modules for
Unsupervised learning with cluster analysis and mixed
variable clustering
It is not part of standard EWS solution. This will have an impact on
the cost of solution offerred and project timelines. In order to
optimize the same, bank may please consider removing the same.
No change in RFP terms.
81 Part 5 ( Technical and
Functional
Specifications)Page no:
71, Point no: 49
The proposed solution should in-built modules for modern
machine learning algorithms to build predictive models - such
as random forests, gradient boosting, artificial neural
networks, support vector machines and factorization
machines
It is not part of standard EWS solution. This will have an impact on
the cost of solution offerred and project timelines. In order to
optimize the same, bank may please consider removing the same.
No change in RFP terms.
82 Part 5 ( Technical and
Functional
Specifications)Page no:
71, Point no: 50
The proposed solution should provide a rich set of data
mining algorithms that can be used for classification,
regression, clustering, detection of outliers and
anomalies,feature extraction, association analysis, and
attributed ranking
It is not part of standard EWS solution and relates to Data
Warehousing/Data Management. This will have an impact on the
cost of solution offerred and project timelines. In order to optimize
the same, bank may please consider removing the same.
No change in RFP terms.
83 Part 5 ( Technical and
Functional Specifications)
Page no: 71, Point no: 52
The proposed solution should allow analysts to be able to
follow a champion challenger approach in model
development through developing different model versions,
compare results on different parameters, and select and
deploy best performing model.
It is not part of standard EWS solution and relates to Model Risk
Management solutions. This will have an impact on the cost of
solution offerred and project timelines. In order to optimize the
same, bank may please consider removing the same.
No change in RFP terms.
Page 16 of 50
84 Part 5 ( Technical and
Functional Specifications)
Page no: 71, Point no: 53
The proposed solution should automatically allow
identification and detection of special types of network
behavior such as cyclical flow of transactions and funds,
clusters etc. extractable from the networks.
It is not part of standard EWS solution and relates to Anti Money
Laundering solutions. This will have an impact on the cost of
solution offerred and project timelines. In order to optimize the
same, bank may please consider removing the same.
No change in RFP terms.
85 Part 5 ( Technical and
Functional Specifications)
Page no: 71, Point no: 56
The proposed solution should be capable of providing
centrality metrics like betweenness, closeness, eigenvector
etc. which determine the importance of a borrower/director
in the network
It is not part of standard EWS solution. This will have an impact on
the cost of solution offerred and project timelines. In order to
optimize the same, bank may please consider removing the same.
No change in RFP terms.
86 Part 5 ( Technical and
Functional Specifications)
Page no: 80, Point no: 1
The system should support detecting implicit and hidden
relationships between:
o Different accounts of the same customer
o Different customers
o Customers, non-customers and Walk in Customers
It is not part of standard EWS solution. This will have an impact on
the cost of solution offerred and project timelines. In order to
optimize the same, bank may please consider removing the same.
No change in RFP terms.
87 Part 5 ( Technical and
Functional Specifications)
Page no: 80, Point no: 2
The system should support automated relationship
identification between linked accounts It is not part of standard EWS solution and relates to Anti Money
Laundering solutions. This will have an impact on the cost of
solution offerred and project timelines. In order to optimize the
same, bank may please consider removing the same.
No change in RFP terms.
88 Part 5 ( Technical and
Functional Specifications)
Page no: 80, Point no: 5
The system should be able to know Money laundering,
diversion/siphoning patterns and fraud patterns like
structuring, circulation of fund etc. The system should have
no limits to parameterise these patterns based on the banks
experiences in money laundering and fraud
It is not part of standard EWS solution. This will have an impact on
the cost of solution offerred and project timelines. In order to
optimize the same, bank may please consider removing the same.
No change in RFP terms.
89 Part 5 ( Technical and
Functional Specifications)
Page no: 80, Point no: 7
The system should support artificial intelligence to setup and
tune the transaction monitoring logic in run time. It is not part of standard EWS solution. This will have an impact on
the cost of solution offerred and project timelines. In order to
optimize the same, bank may please consider removing the same.
No change in RFP terms.
90 Part 5 ( Technical and
Functional Specifications)
Page no: 80, Point no: 8
The system should support defining customer / group level
exceptions at any stage e.g. account opening, etc. The
systemshould be able to generate offline alerts also.If any
person approaches the Bank for any enquiry, which is of
doubtful nature and if any KYC document has been provided,
the system should be able to generate a subjective alert
It is not part of standard EWS solution and relates to Anti Money
Laundering solutions. This will have an impact on the cost of
solution offerred and project timelines. In order to optimize the
same, bank may please consider removing the same.
No change in RFP terms.
Page 17 of 50
91 Part 5 ( Technical and
Functional Specifications)
Page no: 81, Point no: 11
The system should provide the user to generate a suspicious
transaction report and fillup all the requisite information as
per the format provided by regulation and to submit the
same. The user can submit the report to the higher ups for
review and final submission to the concerned regulatory
authorities
It is not part of standard EWS solution and relates to Anti Money
Laundering solutions. This will have an impact on the cost of
solution offerred and project timelines. In order to optimize the
same, bank may please consider removing the same.
No change in RFP terms.
92 Part 5 ( Technical and
Functional Specifications)
Page no: 81, Point no: 19
Automatically generate alerts / reports on Blocked and
Rejected items It is not part of standard EWS solution and relates to Anti Money
Laundering solutions. This will have an impact on the cost of
solution offerred and project timelines. In order to optimize the
same, bank may please consider removing the same.
No change in RFP terms.
93 Part 5 ( Technical and
Functional Specifications)
Page no: 81, Point no: 20
The system should have tools to analyze historical
transactional attributes of an account & suggest benchmark
value. Should support analysis of sequencing of events such
as Placement, Layering and Integration accordingly, look
forward and backward.
It is not part of standard EWS solution and relates to Anti Money
Laundering solutions. This will have an impact on the cost of
solution offerred and project timelines. In order to optimize the
same, bank may please consider removing the same.
No change in RFP terms.
94 Part 5 ( Technical and
Functional Specifications)
Page no: 90, Point no: 14
System should also have a Fraud Detection Suite online for
IBA prescribed Scenarios It is not part of standard EWS solution and relates to Anti Money
Laundering/FRMS solutions. This will have an impact on the cost of
solution offerred and project timelines. In order to optimize the
same, bank may please consider removing the same.
Please refer to Corrigendum
95 Part 5 ( Technical and
Functional Specifications)
Page no: 90, Point no: 18
System should support Wire Transfer Surveillance with the
following features:
Identify wire transfers originating in Correspondent or Agent
banks,Identify suspicious activity based on patterns of
multiple wire transfers, Automatically generate reports on
Blocked and Rejected items, Monitor internal / external and
domestic / international wire transfers
It is not part of standard EWS solution and relates to Anti Money
Laundering/FRMS solutions. This will have an impact on the cost of
solution offerred and project timelines. In order to optimize the
same, bank may please consider removing the same.
No change in RFP terms.
96 Part 5 ( Technical and
Functional Specifications)
Page no: 84, Point no: 10
The solution should support distribution of Reports and
Dashboards to iPad and Android devices. The Native App
should be freely available for iPad on iTunes App Store and
for Android devices on Google Play
This is not a standard EWS feature. As of now, reports generated
can be viewed using mobile browsers in iPad. Native App will have
security implications as there is a chance of confidential
information getting leaked out. Further, when we have 3rd
party
customer identifiable data as well as bank customer data on
mobile app this will lead to huge issues with respect to leakage of
confidential information as there will be no control on the mobile
environment. This will also have an impact on cost and project
timelines. Bank may please reconsider the same.
No change in RFP terms.
97 Part 5 ( Technical and
Functional Specifications)
Page no: 84, Point no: 11
The solution should allow the analysis / explorations /
reports based on in-memory data to be pushed for offline
viewing to mobile devices
This is a not a standard EWS feature. This will involve use of third
party software having implication on cost of solution and timelines.
Bank may please reconsider the same.
No change in RFP terms.
Page 18 of 50
98 Part 5 ( Technical and
Functional Specifications)
The solution should have the ability for Interactive report
viewing for information consumers on iPad and Android
devices
This is a not a standard EWS feature. As of now, reports generated
can be viewed using mobile browsers in iPad. Native App will have
security implications as there is a chance of confidential
information getting leaked out. Further, when we have 3rd
party
customer identifiable data as well as bank customer data on
mobile app this will lead to huge issues with respect to leakage of
confidential information as there will be no control on the mobile
environment. This will also have an impact on cost and project
timelines. Bank may please reconsider the same.
No change in RFP terms.
99 Part 5 ( Technical and
Functional Specifications)
Page no: 84, Point no: 13
Reports and Dashboards access on iPad and Android
devices should be using a native application which helps
leverage most popular gestures and capabilities, including
zoom, swipe, etc., to optimize ease of use and user
engagement
This is a not a standard EWS feature. As of now, reports generated
can be viewed using mobile browsers in iPad. Native App will have
security implications as there is a chance of confidential
information getting leaked out. Further, when we have 3rd party
customer identifiable data as well as bank customer data on
mobile app this will lead to huge issues with respect to leakage of
confidential information as there will be no control on the mobile
environment. This will also have an impact on cost and project
timelines. Bank may please reconsider the same.
No change in RFP terms.
100 Part 5 ( Technical and
Functional Specifications)
Page no: 84, Point no: 16
The solution should provide collaboration support with
Annotation on Tablet
This is a not a standard EWS feature. This will involve use of third
party software having implication on cost of solution and timelines.
Bank may please reconsider the same.
No change in RFP terms.
101 Clause 4.36 Indemnity
Page 55
Suit or proceeding brought against the Bank including by a
third party as a result of : (Specifies the list of Indemnities) :
Vendor’s aggregate liability in connection with obligations
undertaken as a part of the RFP regardless of the form or
nature of the action giving rise to such liability (whether in
contract, tort or otherwise), shall be at actual and limited to
the Total Purchase Order value.
No change in RFP terms.Page 53 specifies a list for indemnity, another at page 55 for
unlimited liabilty, page 62 also mentions unlimited liability, we
request the bank to limit the indemnity clause to maximum upto
the value of PO except the cases identified and mentined on page
55 (highlighted).
Page 19 of 50
102 Clause 4.36 Indemnity
Page 55
Vendor’s liability in case of claims against the Bank resulting
from Willful Misconduct or Gross Negligence of vendor, its
employees and Subcontractors or from infringement of
patents, trademarks, copyrights or such other Intellectual
Property Rights or breach of confidentiality obligations or
Claims made by the Bank for claims relating to the loss of ; or
damage to real property and tangible personal property and
for bodily injury or death which is caused by negligence or
misconduct of the Vendor or its employees, personnel,
consultants, advisors, other representatives; shall be
unlimited.
No such term in RFP, Please refer to the RFP
page no. 55. No change in the RFP term.
103 Clause 4.55 Compliance
with Law Page 62
The Vendor is not absolved from its responsibility of
complying with the statutory obligations as specified above.
Indemnity would not be limited to court awarded damages
and shall include indirect, consequential and incidental
damages. Indemnity would cover damages, loss or liabilities
suffered by the Bank arising out of claims made by its
customers and/or regulatory authorities.
No change in RFP term.
104 Eligibility 3.4.2 Bidder should have implemented and managed end to
end Early Warning Signal (EWS) Solution/ Risk Management/
Fraud Risk Management solution/ CBS successfully, in at least
One Private / Public Sector Bank having minimum business
mix of Rs. 1.50 lakh crore as on 31.03.2019. The location must
be a ‘Core Banking Solution’ in India.
And
The EWS Solution / Risk Management/ Fraud Risk
Management Solution of the OEM should have been
implemented successfully in at least one Private / Public
sector Bank having minimum business mix of Rs. 1.50 lakh
crore as on 31.03.2019. The location must be a ‘Core Banking
Solution’ in India.
In Risk Management & Compliance, CARE Risk Solutions is a well
known player in international market, some of the biggest
implementations we have done are from Abroad. While we do
have implementations in India also, we also recommend
consideration of International Customers to fulfil this requirement.
Please note that the international implementations we have done
are very niche and as per global policies. Hence we recommend
below for this criteria:
3.4.2 Bidder should have implemented and managed end to end
Early Warning Signal (EWS) Solution/ Risk Management/ Fraud
Risk Management solution/ CBS successfully, in at least One
Private / Public Sector Bank having minimum business mix of Rs.
50 lakh crore (INR) as on 31.03.2019 in India or in international
Market. Vendor must have experience working with CORE
BANKING SOLUTIONS such as Finacle, Banks, Flex cube.
And
The EWS Solution / Risk Management/ Fraud Risk Management
Solution of the OEM should have been implemented successfully
in at least one Private / Public sector Bank having minimum
business mix of Rs. 50 lakh crore as on 31.03.2019 in India or
International Market. Vendor must have experience working with
CORE BANKING SOLUTIONS such as Finacle, Banks, Flex cube.
Please refer to the Corrigendum.
Page 53 specifies a list for indemnity, another at page 55 for
unlimited liabilty, page 62 also mentions unlimited liability, we
request the bank to limit the indemnity clause to maximum upto
the value of PO except the cases identified and mentined on page
55 (highlighted).
Page 20 of 50
105 Eligibility 3.4.3 The Bidder should have yearly sales turnover of not less
than Rs.50 Crores on standalone basis of the company during
the financial years FY 2015-16, 2016-17 and 2017-18.
Being a whole subsidiary of CARE Ratings Ltd, our consolidated
financials and relevant information e.g. turnover etc. are overall
combined as CARE Ratings Ltd. Being a Pvt Ltd firm, we do not
publish our own returns etc. publically. Hence we would request
bank to accept the relevant evidences from our Parent company
CARE Ratings Ltd for this criteria.
No change in RFP terms.
106 Eligibility 3.4.16 Site Visits by Evaluation Team. In addition to India, we have very large implementations in
international markets with huge volumes. CARE Risk Solutions
would like to request bank to allow us to arrange those
international site visits or video conferencing. Some of them are on
Finacle latest versions too.
No change in RFP terms.
107 2.b. Objective & page no. 4 An amount of Rs.10,00,000/- (Ten Lac only) towards Initial
Earnest Money Deposit
(EMD) / Bid Security
Request bank also to consider Bank Garuntee as EMD. No change in RFP terms.
108 3.2.1 Broad scope of work & page no. The selected bidder should also support obtaining the
requisite certifications, integration,
maintenance, patching, compliance, etc. and day to day
operations during office hours and
in case of exigencies, any time during the day. Licensing will
be for the Bank. Onsite
support from the bidder will be till date of go-live and
afterwards one dedicated resource
i.e. onsite support engineers (L1) will be onsite for support.
The vendor shall also provide
escalation matrix in respect of support and maintenance of
the application software
Request bank to provide clarity on the no. of shitsof L1 resource
required for onsite suport after go live of the proposed solution.
Only one On-stie support engineer (L1) will
be required.
a) Work timings will be 8 hours from 10 am
to6 p.m. on all working days.
b) The desktop will be provided by Bank
c) In case of any emergeny/ exigency, Services
to be provided for extra hours at no extra
cost.
E) the location of posting the onsite engineer
will be at Mumbai.
f) The duration of onsite support resources
will include both Warranty and AMC period.
g) Bank will make no separate payment.
towards on site support engineers, it should
be factored/included in Price BId. All
payments/ expenses/risks etc. towards
onsite support engineer resources to be borne
by vendor including insurance.
109 3.2.3. b. Broad Scope of WorkPage no. 21b) Post-implementation on-site support for 5 year from Go
Live date. The on-site support
can be extended on the same rates after the contract for
additional years as per
requirement
Request bank to consider," b) Post-implementation on-site support
for 5 year from Go Live date. The on-site support can be extended
on the mutually agreed rates after the contract for additional years
as per
requirement."
No change in RFP terms
Page 21 of 50
110 3.4.2 Eligibility Criteria 3.4.2 Bidder should have implemented and managed end to
end Early Warning Signal (EWS)
Solution/ Risk Management/ Fraud Risk Management
solution/ CBS successfully, in at
least One Private / Public Sector Bank having minimum
business mix of Rs. 1.50 lakh
crore as on 31.03.2019. The location must be a ‘Core Banking
Solution’ in India.
Request bank to consider,"Bidder should have implemented and
managed end to end Early Warning Signal (EWS) Solution/ Risk
Management/ Fraud Risk Management solution/ CBS successfully,
in at
least One Private / Public Sector Bank/ RRB`s having minimum
business mix of Rs. 1.50 lakh
crore as on 31.03.2019. The location must be a ‘Core Banking
Solution’ in India.
Please refer to Corrigendum
111 General Queries Request bank to confirm if there is any FMS services are required
snice the hardware is provided by the bank as per sizing provided
Yes, Hardware will be provided by the Bank,
sizing to be provided by the vendor .
112 3.2.3.1, Page Number -11 To provide a warning signal in case of potential lending
opportunities that are in Application /evaluation stage.
Early warning signals are related to the accounts wherein loans are
already sanctioned by the bank. It is related to the monitoring of
bank's loan accounts. Kindly remove the given term
No Change in terms of RFP.
113 3.2.3.2, Page - 16 Ability to generate SASCL type report generation. Please advise the Banks requirement for SASCL report in EWS
system?
It will be shared with the successful vendor.
114 Page -20 A copy of the source code of the application customized for
Bank of India shall be handed over to the Bank. A copy of all
subsequent updates to the source code shall also be handed
over to Bank after the release / Go Live.
As per the product policy we do not share our source code, request
the Bank to relax the given clause
Please refer to the 'Environmental Setup &
Configuration' sub-point 'h', page no. 20.
115 Pg No : 18
, 3.2.3.5xii. On-Site Support: The successful Bidder / OEM shall
provide onsite support during the contract period as required
by Bank
Is support needed only for EWS application or also for
Hardware/Databases?
8 hours on all working days.
8 hours on all working days support for EWS
Solution and database
116 Page -23, 3.4.5 The Bidder should have posted Profit after Tax (PAT) on
standalone basis of the company during financial years of FY
2015-16, 2016-17 and 2017-18
Request the bank to relax the given clause to any two out of 3 FY
given
No change in RFP term.
117 Data Integration Capabilities:
Document Visualization -
Page -65
The proposed application should be capable of integration
with standard DMS systems
What are the DMS software being used in existing DMS system and
What is the current volume of documents size in the DMS ?
This will be shared with the successful vendor.
118 3.2.3.1 , page -11 To detect financial stressed borrower accounts or in its
existing loan/lending portfolio
Please specify the total number of loan accounts across Retail,
SME, Agri & Corporates, to be considered for EWS monitoring
process.
Please refer to the data given at the end of
this document.
119 3.2.3.1 , page -11 To detect financial stressed borrower accounts or in its
existing loan/lending portfolio
Average number of daily transactions involving the loan accounts?
Pls specify.
Please refer to the data given at the end of
this document.
120 Page -90 System should also have a Fraud Detection Suite online for
IBA prescribed Scenarios
It is not part of standard EWS solution and relates to Anti Money
Laundering/FRMS solutions. The bank may please consider
removing the same.
Please refer to the corrigendum.
Page 22 of 50
121 Pg No : 18,
3.2.3.5 xiii aIntegrate the proposed solution with Bank’s Core Banking
Solution, Treasury, CAPS, LMS, DMS, IMAC, CMS cum Channel
Finance, KYC and AML, EFRMS, Trade
Finance and other softwares with necessary interface on real
time basis
Is there a need for real time integration with internal sources? Or
data can be refreshed on T-1 basis as a batch process?
Please refer to the corrigendum.
122 Pg No : 23,
3.3.43.3.4 The EWS solution proposed or Risk Management/ Fraud
Management Solution by the bidder should have been
operationalized and continue to be in successful operation in
at least one Private/Public sector undertaking Bank having
minimum business mix of Rs 1.50 Lakh Crore as on
31.03.2018. The location must be a 'Core Business Solution' in
India.
Can the requirement of minimum business mix in this clause be
relaxed?
There is no relaxation in the Business Mix in
this clause. However please refer to the
corrigendum.
123 Pg No : 32
3.242. Technical Presentation (TP) & Product Demonstration (PD)/
Proof of concept (POC)
What is Bank's expectation of POC? Will Bank share any customer
names or internal data for POC?
Please refer to the Page 33 'Scoring for Overall
Technical Presentation (TP) and Product
Demonstration (PD) / Proof of Concept (POC) '
of RFP. The concept for POC will be shared
with only qualified / shortlisted bidders.
124 pg 65
Data Integration Capabilities:
Standardization and Data
Quality
Point No 4
EWS should have user interfaces for Data Profiling, Data
Standardization, and Clustering and Data Augmentation
capabilities. In Data Profiling it should be able to conduct the
following analysis : Structure discoveries
Frequency distribution
Pattern distribution
Various Statistical Analysis
Redundant Data Analysis
Based on our past experience, we have seen that UI for data
profiling is not essential from EWS perspective. Including the same
has high cost impact
No Chang ein terms of RFP.
125 pg 65
Data Integration Capabilities:
Standardization and Data
Quality
Point No 7
Should have business rules and GUI’s for automatic merging
and manual merging.
Need clarity on this. Based on our past experience, this
requirement should not be a part of ews. We recommend to
remove this point from RFP
No Chang ein terms of RFP.
126 pg 66
Data Integration Capabilities:
Document Visualization
Point no 8
Text mining utility should have intelligent self-learning
capability
Will the bank provide with feedback for the algorithm to learn?
This process will be manual
No change in RFP terms, the details will be
discussed with the successful vendor.
Page 23 of 50
127 Pg 70
EWS Rules and Analytical
Capabilities
Point no. 40, 41, 42,
43,45,46,47,48,49,50,54,56
The proposed solution should provide one integrated user
interface and workbench for data wrangling, data exploration,
business intelligence and visualization, feature engineering,
and modern statistical, data mining and machine learning
techniques all in a single, integrated inmemory processing
environment for faster insights, flexible deployment and
reliable and secure governance
The proposed solution should contain a sophisticated and GUI
based predictive modeling and analytical workbench.
The proposed solution should enable identification of
suspicious borrowers through a judicious mix of anomaly
detection, business rules, predictive modeling and network
analytics
The proposed solution should provide out-of-box entity
analytics and direct intelligence analysts by showing measures
of centrality in entity networks - such as closeness,
betweenness and influence to highlight suspicious
borrowers/directors.
The proposed solution should help analysts to visualize
complex network of relationships between entities - such as
people, organizations, places/ locations, things and events
over time and across multiple dimensions
The proposed solution should help analysts identify entity
Based on our experience, these requirements are not essential
from an EWS perspective. Request the bank to consider dropping
these requirements
No change in RFP Terms.
128 Pg 72
EWS Rules and Analytical
Capabilities
Point no. 58
While onboarding the new customer in bank, based on inputs
given about entity, individuals such as PAN No of entity /
individuals, UID, CIN, DIN, Aadhar, Passport No., Driving
License, Voter ID card the Solution should generate market
intelligence / due diligence reports based on banks internal or
external sources about the profile of customer – both
positive/negative.
This relates to onboarding of a new customer. However, EWS
system is expected to track only those accounts where
disbursement has happended. This requirement should not be in
scope of EWS (post sanction monitoring). Bank's LOS is the right
system to deliver this requirement. Request the bank to consider
dropping
No change in RFP terms.
129 Pg 80
Transaction Monitoring
Point no. 8
The system should support defining customer / group level
exceptions at any stage e.g. account opening, etc. The system
should be able to generate offline alerts also. If any person
approaches the Bank for any enquiry, which is of doubtful
nature and if any KYC document has been provided, the
system should be able to generate a subjective alert.
This relates to onboarding of a new customer. However, EWS
system is expected to track only those accounts where
disbursement has happended. This requirement should not be in
scope of EWS (post sanction monitoring). Bank's LOS is the right
system to deliver this requirement. Request the bank to consider
dropping
No change in RFP terms.
130 Pg 99, Point no. 8 Physical Security of Facilities This will be an on premise installation with the hardware being
managed by the bank. Request you to drop this point from RFP
No change in RFP terms
Page 24 of 50
131 Pg 69, Point no. 22,23,24 The proposed solution should provide an in-built ability to
create, modify and enable (or disable) custom concepts and
test linguistic rule definitions with validation checks within
the same interactive interface
The proposed solution should include automated parsing,
tokenization, part-of-speech tagging, synonym detection,
spell checking and stemming by the in-built Natural language
processing feature provided by the solution
The proposed solution should include additional Text Mining
features such as - Output lists of terms to drop/keep and term
frequency counts, easy drag and drop between keep and drop
terms, ability to apply customized start and stop lists (for
terms to include/exclude from processing), ability to include
custom-defined categories and custom concepts
The proposed solution should provide in-built feature of
Automated machine discovery to identify the core themes in
the input document collection with associated relevance
score
Based on our experience, these requirements are not essential
from an EWS perspective. Request the bank to consider dropping
these requirements
No change in RFP terms
132 Pg 32, section 3.2.4 The proposed solution by the bidder should ensure minimum
compliance of 90% for the EWS Solution for technical and
functional requirement (i.e. (a) above) scoring based on the
defined functional parameters.
Request the bank bank to cap the minimum compliance to 75%. No change in RFP terms
Page 25 of 50
133 9- pg 38 Payment terms We request to add following:a) The fees and any amounts
payable under the Contract are exclusive of all applicable
taxes (including GST), levies, duties etc. Any such tax will be
charged over and above the fees and amounts payable to
CRIS under the Contract. The GST registration number
(“GSTIN”) provided by the Bank will be used by CRIS for filing
of the GST returns.
b) With regards to the applicability of Goods and Services
Tax, the Bank’s address as mentioned for the purposes of
GST will be considered as the consumption location for the
Services provided by CRIS under the Contract.
c) CRIS shall not be liable for loss of credit arising on account
of incomplete, erroneous or wrong details captured by the
Bank in the details and documents uploaded to the GSTN.
Additionally the Bank shall be responsible and liable for
providing its correct GSTIN and CRIS will not be responsible
for verification of the Bank’s GSTIN. Where the Bank fails to
furnish its GSTIN, CRIS will treat the Bank as being
unregistered for GSTIN.
d) Where CRIS issues a credit note to the Bank in relation to
any invoice, the Bank shall adjust and upload its Input Tax
Credit on the GSTN on or before the end of the month in
which the credit note is issued by CRIS to the Bank. If the
Bank fails to do so, and this results in additional liability for
CRIS, Bank shall be liable to be reimburse CRIS for any
liability incurred by CRIS (being the tax, interest and any
penalties thereon).
No change in RFP terms
134 10.1.7-pg 41 7In case of any variation (upward or down ward) in
Government levies / taxes / cess / excise / custom duty
etc. including introduction of any such new
tax/cess/excise etc. which has been included as part of
the price will be borne by the Bidder.
Request this to be amended to state that such variation to be
paid by the party required under law to incur such tax liability.
No change in RFP terms
135 10.1.11-pg 41 If any Tax authorities of any state, including, Local authorities
etc. or any Government authority or Statutory or autonomous or
such other authority imposes any tax, charge or levy or any
cess / charge other than GST and if the Bank has to pay the
same for any of the items or supplies made hereunder by the
Bidder, for any reason including the delay or failure or inability
of the Bidder to make payment for the same, the Bank has to
be reimbursed such amounts paid, on being intimated to the
Bidder along with the documentary evidence. If the Bidder does
not reimburse the amount within a fortnight, the Bank shall
adjust the amount out of the payments due to the Bidder from
the Bank along with the interest calculated at commercial rate.
Request deletion of this clause No change in RFP terms
Page 26 of 50
136 10.1.19-pg 43 The bidder shall represent and acknowledge to the Bank that it
possesses necessary experience, expertise and ability to
undertake and fulfil its obligations, involved in the performance
of the provisions of this RFP. The bidder represents that the
proposal to be submitted in response to this RFP shall meet
the proposed RFP requirement. If any services, functions or
responsibilities not specifically described in this RFP are an
inherent, necessary or customary part of the deliverables or
services and are required for proper performance or provision
of the deliverables or services in accordance with this RFP,
they shall be deemed to be included within the scope of the
deliverables or services, as if such services, functions or
responsibilities were specifically required and described in this
RFP and shall be provided by the bidder at no additional cost to
the Bank. The bidder also acknowledges that the Bank relies
on this statement
of fact, therefore neither accepting responsibility for, nor
relieving the bidder of responsibility for the performance of all
provisions and terms and conditions of this RFP, the Bank
expects the bidder to fulfil all the terms and conditions of this
RFP. The modifications, which are accepted by the Bank, shall
form a part
of the final contract.
Request deletion of following sub-clause:
The bidder represents that the proposal to be submitted in response
to this RFP shall meet the proposed RFP requirement. If any
services, functions or responsibilities not specifically described in this
RFP are an inherent, necessary or customary part of the deliverables
or services and are required for proper performance or provision of
the deliverables or services in accordance with this RFP, they shall
be deemed to be included within the scope of the deliverables or
services, as if such services, functions or responsibilities were
specifically required and described in this RFP and shall be
provided by the bidder at no additional cost to the Bank. The bidder
also acknowledges that the Bank relies on this statement of fact,
therefore neither accepting responsibility for, nor relieving
the bidder of responsibility for the performance of all provisions and
terms and conditions of this RFP, the Bank expects the bidder to
fulfil all the terms and conditions of this RFP. The modifications,
which are accepted by the Bank, shall form a part of the final
contract.
No change in RFP terms
137 10.2.2-pg 45 The Bank shall be under no obligation to accept the lowest
commercial bid or any other offer received in response to this
Tender and shall be entitled to reject any or all offers including
those received late or incomplete offers without assigning any
reason whatsoever. The Bank reserves the right to make any
changes in the terms and conditions of purchase. The Bank will
not be obliged to meet and have discussions with any bidder,
and / or to listen to any representations unless there is change
in the terms and conditions.
Request bank to confirm that the right to change terms and
conditions will cease post submission of BidNo change in RFP terms
138 10.6.7 pg 50 The Parties will keep in confidence and not disclose to any third
party any and all Confidential Information available to the
Parties, whether such information is given in writing or, is oral
or visual, and whether such writing is marked to indicate the
claims of ownership and/or secrecy or otherwise. Except as
otherwise
provided in this Tender, the Parties shall not use, nor
reproduce for use in any way, any Confidential Information. The
Parties agrees to protect the Confidential Information of the
other with at least the same standard of care and procedures
used to protect its own Confidential Information of similar
importance but at all times using at least a reasonable degree
of care.
After Oral or Visual request to include Only if recorded within 48
hours of such disclosureNo change in RFP terms
139 10.6.10.6 pg 52-53 This shall not be applicable and shall impose no obligation on
the receiving party with respect to any portion of Confidential
Information which:
Request to include:-
g) was allowed to be disclosed by the Disclosing Party.No change in RFP terms
Page 27 of 50
140 10.6.11 pg. 53 On termination of the Tender and subsequent Agreement, each
party must immediately return to the other party or delete or
destroy all Confidential Information of the other party and all
notes and memoranda (including copies of them) containing
Confidential Information of the other party in its possession or
control save for that training materials and Documentation that
has been provided to the Bank which is contemplated for
continued realization of the benefit of the Services.
Notwithstanding the foregoing, Bidder may retain a copy of
such information (but which shall not include customer data
and
Confidential Information) as may be necessary for archival
purpose. Where Confidential Information relates to the Bank’s
data or data of the Bank customers, including but not limited to
the Bank customers’ or the Bank employees’ personal data or
such other information as the Bank is required by banking
secrecy or such other laws to protect for an indefinite period,
such Confidential Information shall be protected by the
receiving party for an indefinite period or until such time when
the receiving party no longer has access to the Confidential
Information and has returned or destroyed all Confidential
Information in its
possession.
We suggest deleting the below text:-
Where Confidential Information relates to the Bank’s data or data of
the Bank customers, including but not limited to the Bank customers’
or the Bank employees’ personal data or such other information as
the Bank is required by banking secrecy or such other laws to protect
for an indefinite period, such Confidential Information shall be
protected by the receiving party for an indefinite period or until such
time when the receiving party no longer has access to the
Confidential Information and has returned or destroyed all
Confidential Information in its possession.
No change in RFP terms
141 10.6.14 pg. 54 Vendor will respect the confidentiality of all information given
to it by the Bank and will not divulge such information to any
third party or other units without the consent of the Bank. The
confidentiality obligations shall survive the expiry or termination
of the agreement between the bidder and the Bank
We suggest including the following line.
The confidentiality obligations can be abided for a period of 02 years
from the date of its disclosure
-- instead of --
The confidentiality obligations shall survive the expiry or termination
of the agreement between the bidder and the Bank.
No change in RFP terms
142 10.10.5 pg. 56 If a notice has to be sent to either of the parties following the
signing of the contract, it has to be in writing and shall be first
transmitted by facsimile transmission by postage prepaid
registered/speed post with acknowledgement due or by a
reputed courier service, in the manner as elected by the Party
giving such notice. All notices shall be deemed to have been
validly given on (i) the business date immediately after the date
of transmission with confirmed answer back, if transmitted by
facsimile transmission, or (ii) the expiry of five days after
posting if sent by registered/speed post with A.D., or (iii) the
business date of
receipt, if sent by courier.
Request to be amended as highlighted
(ii) after posting if sent by registered/speed post with A.D. on the date
of receipt by the recipient ,
No change in RFP terms
143 10.11.4 pg. 57 In such a case the time for performance shall be extended by a
period(s) not less than duration of such delay. If the duration of
delay continues beyond a period of three months, the Bank and
the Vendor shall hold consultations in an endeavour to find a
solution to the problem.
Suggest including the below clause towards the end:-
Neither party shall be liable for any failure to perform (except
payment obligations) if prevented from doing so by any Force
Majeure event.
No change in RFP terms
Page 28 of 50
144 10.12.3 pg. 57 The Vendor shall have right to terminate only in the event of
winding up of the Bank.
To be replaced with the following:-
Bidder may terminate:
(a) the Contract upon 7 days’ prior written notice to Bank if Bank
materially breaches any licence restrictions set forth in this Contract
or BIDDER’s intellectual property rights in the Service or BIDDER
Materials, and such breach is not cured by Bank within the notice
period stated afore;
(b) on written notice, should BIDDER’s rights to receive and/or
distribute any third party software or material be terminated which
would affect provision of Services under the Contract.
A termination of this Contract shall not limit a party's rights as shall
have accrued up to the effective date of termination (for the
avoidance of doubt, where BIDDER terminates under this clause,
Bank’s licence to use the Software and the right to receive related
Services shall terminate).
No change in RFP terms
145 10.13 pg. 57 10.13
Order / Contract Cancellation
10.13.2 The Bank reserves its right to cancel the order /
contract in
the event of one or more of the following situation(s and it will
be considered as a breach of obligations of bidder:
• Delay in implementation beyond the specified period that is
agreed in the contract that will be signed with the
successful bidder.
• Discrepancy in the quality of service / security expected
during the implementation, rollout and subsequent
maintenance process.
• The amount of penalties has exceeded the overall cap of
10% of the yearly contract value.
• Failure of the bidder make good the situation within the
remedy period
• The selected bidder commits a breach of any of the terms
and conditions of the RFP / contract.
• The selected bidder becomes insolvent or goes into
liquidation voluntarily or otherwise
• An attachment is levied or continues to be levied for a period
of 7 days
upon effects of the tender.
Request deletion of clause 10.13.2 to be deleted in entirety.
and Include the following:-
Post termination.
(a) Where the termination applies to an Contract under which
Software was supplied and that Contract is terminated by BIDDER
under this clause, BIDDER will refund to Bank the applicable Fees
for the affected Services that the Bank has paid in advance as relate
to the period following the effective date of termination, provided that
when the affected Services comprise Software license, BIDDER will
refund to Bank the Fees actually paid by the Bank for the Software,
depreciated on a straight-line basis over the shorter of the term of
the licence to the Software under the Contract or four years.
(b) Where the termination applies to Services, Bank shall pay to
BIDDER the applicable Fees and other payments as shall have
accrued until effective date of termination.
(c) Further, upon termination of any Contract, or this Contract
generally, by BIDDER Bank shall (i) cease all use of the applicable
Products provided under the applicable Contract; and (ii) expunge
the relevant Software and any portion or copies thereof from all of
Bank’s electronic storage systems. At BIDDER’s request, Bank shall
certify to BIDDER in writing that Bank has fully complied with this
requirement. Notwithstanding the restrictions set out in this clause,
Bank may retain those portions of the Product that are necessary for
statutory audit requirements and/or regulatory compliance purposes.
For the avoidance of doubt, on termination of the relevant Contract,
Bank shall cease all access to, and use of, the Product including
those portions of the deliverables under the Contract and/or Product
it retains as expressly permitted in the immediately preceding
sentence.
No change in RFP terms
Page 29 of 50
146 10.14.1 Compliance with all applicable laws: The Vendor shall
undertake to observe, adhere to, abide by, comply with and
notify the Bank about all laws in force or as are or as made
applicable in future, pertaining to or applicable to them, their
business, their employees or their obligations towards them
and all purposes of this tender and shall indemnify, keep
indemnified, hold harmless, defend and protect the Bank and
its employees/ officers/ staff/ personnel/ representatives/
agents from any failure or omission on its part to do so and
against all claims or
demands of liability and all consequences that may occur or
arise for any default or failure on its part to conform or comply
with the above and all other statutory obligations arising there
from.
Request to delete the following:-
failure or omission on its part to do so and against all claims or
demands of liability and all consequences that may occur or arise for
any default or failure on its part to conform or comply with the above
and all other statutory obligations arising there from.
and To include:-
or allegation by a third party that the Software infringes or
misappropriates (i) a valid patent of a third party issued prior to the
Commencement Date, or (ii) any copyright or trade secret right of a
third party (collectively, “IP Infringement Claims”); provided, however,
that with respect to any third party software or materials provided
hereunder, BIDDER will defend and indemnify Bank from any Loss
arising out of any claim or allegation by a third party that BIDDER
failed to obtain the rights from such third party to licence the use of
such third party software or material for purposes of this Agreement.
Notwithstanding the foregoing, if the Software becomes or, is likely to
become the subject of any infringement claim indemnified above,
BIDDER may, at its option, (1) procure for Bank the right to continue
using the Software, (2) replace or modify the Software so that it
becomes non-infringing while retaining materially equivalent
functionality, or, if (1) and (2) are not reasonably available, then (3)
terminate the affected Services and refund to Bank licence fees
actually paid thereunder, depreciated on a straight-line basis over the
shorter of the Licence Term or four years. The foregoing represents
the entire liability of BIDDER with respect to infringement of patents,
copyrights and trade secrets by the Software or any part thereof or by
its operation.
7.2 Infringement Indemnification Exclusions. The foregoing
obligation of BIDDER shall not apply with respect to: (i) modifications
to the Software performed by any party other than BIDDER or its
agents (unless BIDDER requests that party to make the
modification(s)), if the alleged infringement relates to such
modification and use of the unmodified version of the Software alone
No change in RFP terms
147 10.14.2 pg. 59 Compliance in obtaining approvals/permissions/licenses: The
Vendor shall promptly and timely obtain all such consents,
permissions, approvals, licenses, etc., as may be necessary or
required for any of the purposes of this project or for the
conduct of their own business under any applicable Law,
Government Regulation/Guidelines and shall keep the same
valid and in force during the term of the project, and in the
event of any failure or omission to do so, shall indemnify, keep
indemnified, hold harmless, defend, protect and fully
compensate the Bank and its employees/ officers/ staff/
personnel/ representatives/agents from and against all claims
or demands of liability and all consequences that may occur or
arise for any default or failure on its part to conform or comply
with the above and all other statutory obligations arising there
from and the Bank will give notice of any such claim or demand
of liability within reasonable time to the bidder.
Request to delete:-
and in the event of any failure or omission to do so, shall indemnify,
keep indemnified, hold harmless, defend, protect and fully
compensate the Bank and its employees/ officers/ staff/ personnel/
representatives/agents from and against all claims or demands of
liability and all consequences that may occur or arise for any default
or failure on its part to conform or comply with the above and all
other statutory obligations arising there from and the Bank will give
notice of any such claim or demand of liability within reasonable time
to the bidder.
No change in RFP terms
Page 30 of 50
148 10.15.4 pg.60 Under no circumstances the Bank shall be liable to the Service
Provider for direct, indirect, incidental, consequential, special or
exemplary damages arising from termination of this Agreement,
even if the Bank has been advised of the possibility of such
damages, such as, but not limited to, loss of revenue or
anticipated profits or lost business.
Request to be made mutual and be replaced with:-
Neither party is liable for any indirect or consequential losses or
damages or any loss of business, profit, goodwill or other economic
loss, even if advised of the possibility of such damages and
regardless of whether such liability is based in contract, tort
(including but not limited to negligence) and strict liability or any other
theory of legal liability. Without limiting the foregoing, under no
circumstances will the aggregate liability of party exceed the
proposed fees for the Services being procured
No change in RFP terms
149 10.15.5 pg.60 It is expressly agreed between the Parties that for any event
giving rise to a claim, Bank shall have the right to make a claim
(including claims for indemnification under the procurement in
this RFP) against vendor
Request to make the clause mutual No change in RFP terms
150 10.16.1 pg. 60 The Vendor agrees that the vendor shall not be entitled to
assign any or all of its rights and or obligations under this
Tender and subsequent Agreement to any entity including
bidder’s affiliate without the prior written consent of the Bank.
Request to make the clause mutual
This Agreement may not be assigned, transferred or novated by
either party without the prior written consent of the other party, except
that CRIS may assign, novate or transfer this Agreement to any of its
affiliates or successors to its business. All contract modifications,
additions and amendments mutually agreed upon, should be
properly endorsed by all parties to the contract and documented in
the revised Contract or Agreement. Modifications due to renewals
and/or change in scope can also be incorporated in the form of an
Addendum to the existing contract/agreement.
No change in RFP terms
151 10.16.2 pg. 60 If the Bank undergoes a merger, amalgamation, takeover,
consolidation, reconstruction, change of ownership, etc., this
RFP along with the subsequent Addendums published shall be
considered to be assigned to the new entity and such an act
shall not affect the rights of the bidder under this RFP
Request to be deleted in entirety. No change in RFP terms
152 10.17 pg. 60 Any publicity by the vendor in which the name of the Bank is to
be used should be done only with the explicit written permission
of the Bank.
Request to include -
Vendor may refer Bank as its customer and use Client’s name,
brands or logos (Client Brands) in its marketing or presentation
material.
No change in RFP terms
153 10.19.2 Notices shall be deemed given upon receipt, except that
notices send by registered/speed post in a correctly addressed
envelope shall be deemed to be delivered within 5 working
days (excluding Sundays and public holidays) after the date of
mailing dispatch and in case the communication is made by
facsimile transmission or email, on business date immediately
after the date of successful facsimile/email transmission (that
is, the sender has a hard copy of a confirmation page
evidencing that the facsimile was completed in full to the
correct fax number or email sent to correct email address).
Request to delete:-
except that notices send by registered/speed post in a correctly
addressed
envelope shall be deemed to be delivered within 5 working days
(excluding Sundays and public holidays) after the date of mailing
Dispatch
No change in RFP terms
Page 31 of 50
154 Request to include standard clauses as per attachment (additional
clauses)No change in RFP terms
155 Objectives page 4 Any upgradation or modification required by the
Bank till the time of Go-Live and thereafter any
upgradation or modification required as per the
requirement of any regulator ( RBI or IBA or FIU-
IND) to be provided free of
cost by the vendor
Upgradations may also be entailing major work in
terms of effort and change in data design. We thus
suggest and submit that the said clause may please
be modified as under: "Any upgradation or
modification required by the Bank till the time of Go-
Live and thereafter any upgradation or modification
required as per the requirement of any regulator (
RBI or IBA or FIU-IND) to be provided free of cost by
the vendor. However changes / upgradations that
would entail major rework and involve a revisit to the
data base design, shall on case to case basis, be
examined between the Bank & Vendor and a decision
of costing will be taken as per discussions"
No change in RFP terms.
156 Schedule of Bid
submission /
Address for
communication Page
4
However, the Bids can be submitted only
after depositing the following amounts in
favor of MSTC and Bank of India as under,
within the period of Bid submission
a. A non-refundable amount of Rs. 50,000/-
(Fifty Thousand only) towards cost of Bid
document and
b. An amount of Rs.10,00,000/- (Ten Lac only)
towards Initial Earnest Money Deposit (EMD)/ Bid
Security
c. An amount of 0.05% of Estimated Tender
Value (plus applicable GST) or as guided on fees
by MSTC or Maximum fees of Rs. 15,000/- while
making payment, towards
Transaction Fee (non-refundable) to MSTC
through Transaction fee payment link in the
vendor login.
A reference is also invited to the Gazette No. 503
dated March 26, 2012 page 19 Clause 10, ( Copy
enclosed) wherein it has been stipulated that MSME
units should be exempted from paying Bid document
Cost and EMD deposit. We thus request and submit
that the said exemption clause may please be
included in the clause and it be suitably modified.
Please refer to the Clause 3.4.23, page 24 and
the Format 6.14, sub-point 23 on page no.
128 of RFP.
Page 32 of 50
157 Project
Implementation
Schedule Page 6
Customization & installation - 30-45 days
Data Collection & Integration - 45-75 days
UAT - 75-
135 days
UAT – System Validations &
Report Generation - 135-165
days
Go Live - 180
days from PO
Considering the vast requirements of the Bank,
Schedule may be revised as follows:
Customization & installation - 30-60 days
Data Collection & Integration - 60-90 days
UAT - 90-135
days
UAT – System Validations &
Report Generation - 135-165 days
Go Live - 180 days
from PO
The changes if any proposed in
implementation schedule, will be discussed
with the successful vendor while executing
SLA. There will not be allowed any change in
outer limit of 180 days given for complete
implementation including Go Live. The Vendor
will be allowed to give any combination of
milestones within outer limit of 180 days.
Accordingly, the penalty clause in relation to
the dealy in implementation will be linked to
the milestones proposed by successful bidder
for complete implementation including Go
Live within 180 days from PO. In case, while
executive SLA, both Bank and the successful
Vendor are not mutually agreed on the
proposed changes in schedule, the
implementation schedule given in RFP will be
final.
158 3.1.2 Page 10 In case BOI acquires or amalgamate or merge
with any Bank at any future date EWS Solution
will also have to be extended to the such entity
for which only implementation cost will be paid
by the Bank. Estimated no. of users for Bank will
be around 1000.
Any increase in number of branches / data will
require upgrdation of hardware etc . We request you
to kindly include the above in the clause.
Any requirement of Hardware upon
happening of such an event will be taken care
by the bank. No change in RFP term.
159 3.2 Broad Scope of
Work
3.2.3.1 Page 11
To be able to predict and take necessary
corrective actions on loan accounts based on
their health as against the defined directive of
measurement of such assets.
Vendor will not be able to take corrective actions.
This needs to be handled by the Bank. We can
predict the possibility of the loan / exposure
becoming delinquent at a future date. We thus
request and submit that the clause may suitably be
amended or removed.
No change in RFP terms.
160 3.2.3.2 Page 16 Ability to assist in the audit process related to
loans which include
- Credit Audit
- Stock Audit
- Statutory Audit
- Long Form Audit Report
- Concurrent Audit
EWS system output does not have direct co-relation
with Audit. Kindy elaborate the requirements, please.
No change in RFP terms. The details will be
shared with the successful Vendor.
Page 33 of 50
161 3.2.3.5 2(XII) Page
18
a) Seamless integration of supplied, customized,
developed software for Bank of India to meet the
Bank’s Functional, Operational, Risk
Management, Regulatory and MIS requirements
of Credit Monitoring department (CrMD) with all
required interfaces. Integrate the proposed
solution with Bank’s Core Banking Solution,
Treasury, CAPS, LMS, DMS, IMAC, CMS cum
Channel Finance, KYC and AML, EFRMS, Trade
Finance and other softwares with necessary
interface on real time basis.
EWS system output does not have direct co-relation
with Functional, Operation, Risk Management,
Regulatory and MIS requirements of CrMD. Kindy
elaborate the requirements, please.
It is self explainatory. No change in RFP terms.
162 3.2.3.5 2(XII)
Page18
c) The proposed solution should provide audit
reports and Tools for the Bank’s internal /
concurrent / statutory / SEBI / RBI Audit /
Inspections / RBS RBI.
EWS system output does not have direct co-relation
with audit reports and Tools for the Bank’s internal /
concurrent / statutory / SEBI / RBI Audit /
Inspections / RBS RBI. Kindly elaborate the
requirements, please.
It is self explainatory. No change in RFP terms.
163 3.2.5 MIS Reports
generation : Page21
MIS Reports generation :The solution should
also generate data files as per the format of
Bank/ RBI and other statutory bodies from time
to time.
Number of reports may please be indicated All standard formats to be available.The
formats may further be customised based on
RBI/statutory bodies/Inspection/user
requirements if any.
164 3.4.3 Eligibility
Criteria Page 22
The Bidder should have yearly sales turnover of
not less than Rs.50 Crores on standalone basis of
the company during the financial years FY 2015-
16, 2016-17 and 2017-18
It is submitted that the average turnover of at least
Rs.50 Crore may be modified to Rs.5 crore. A
reference is also invited to the Ministry of MSME
instructions vide F.No. 22(1)/2003/EP&M dated
29.7.2003, where in it is mentioned that mandatory
minimum turnover should not be imposed on
SSI/MSME units . Further, as per the thrust of Govt.
to ensure the participation of FinTech / Startup
companies / MSMEs companies who may not have
generated the turnover but may have product, we
request to kindly oblige by reducing the minimum
turnover criteria.
No change in RFP term.
165 3.4.16 Page 23 Site Visits by Evaluation Team. By the time RFP is submitted , there would not be any
visit of BOI. Kindly arrange to inform the
requirement.
Site visit will be carried out during Technical
Evaluation stage.
166 4.38 Page 56 In case of oracle database Bank will provide
necessary licenses. Though Bank is providing the
licenses for Databases i.e. SQL and Oracle.
As per the clause and elsewhere mentioned in the
RFP, if database is SQL or Oracle , Licenses will be
provide by Bank but this clause mention only about
Oracle . Kindly clarify.
If database is SQL or Oracle, Licenses will be
provided by Bank for both these databases.
167 4.56 Page 62 The Vendor’s liability in case of claims against the
Bank resulting from following shall be unlimited
:
vi) Loss occasioned by Non-compliance of
Statutory or Regulatory Guidelines
As an vendor partner to Bank, we will be delivering
the requirement as per the terms of RFP and its use
solely depended on different stack holders of Bank
hence compliance to statutory and regulatory
guidelines should be handled by Bank
No change in RFP terms.
Page 34 of 50
168 Part 5 Page 78 The EWS solution Should be capable of
classifying the exposures as SMA 0/ SMA 1/ SMA
2 as per RBI definition, both individually and as
well as in a group.
As per the RFP Terms , scope is limited to all accounts
with 25 Lacs and above exposure. Kindly confirm.
Yes, scope as per RFP.
169 Format 6.14 Page
124
A certificate stating that OEM solution has been
implemented successfully to be submitted along
with Technical Bid. The Certificate should be
issued by CIO or IT Head of the Bank /
Institution.
We request that kindly arrange to include Functional
Head / Authorise signatory of dept also as signing
authority.
No change in RFP terms.
170 7.16 Payment Terms
Page 145
For operating system etc we request to include the
90% payment condition on delivery as we have to
pay 100% advance payment to Microsoft .
No change in RFP terms.
171 Pg 145 of 165 Payment
Terms Clause7.16
c) The bidder/OEM must accept the payment terms proposed
by the Bank. Any deviation from the proposed payment terms
would not be accepted. The Bank shall have the right to
withhold any payment due to the System Installation, in case
of delays or defaults on the part of the bidder. Such
withholding of payment shall not amount to a default on the
part of the Bank.
We submit for deletion of the right to withhold any payment due to
the System Installation as the payment milestones are sturcutured
in a manner that payment is released after the completion of the
activities in scope along with sign-off for the same, further a right
to withhold payment arises where payments are made in advance
before completion of the activities
No change in RFP term.
172 Pg 145 of 165 Payment
Terms Clause7.16
Payment for the Supply of required Software, Design,
Installation, Implementation, configuration, integration and
Commission of the EWS Solution shall be made as per Scope
of Work.
- On delivery of product, execution of Agreements and
submission of all documents including Performance Bank
Guarantee: 20% of total cost
- On completion of customization as per requirement of Bank
& successful completion of UAT: 20% of total cost
- Implementation, go-live of Solution as per the scope of RFP-
15% payable 3 months after Go Live and 15% payable 6
months after Go Live i.e. at Sign Off.: 30% of total cost
- Completion of training & handing over of all documents and
6 months after Sign Off.: 20% of total cost
- On due performance and completion of project and after
completion of warranty period. It is made clear That in case
Vendor commits default/ breach in the performance of
contract, the Bank shall have absolute right to retain the 10%
retention amount and without recourse to the vendor, Bank
can appropriate towards the loss / damage/ penalty incurred.:
10% of total cost
Bidder requests for the following changes
Payment for the Supply of required Software, Design, Installation,
Implementation, configuration, integration and Commission of the
EWS Solution shall be made as per Scope of Work.
- On delivery of product, execution of Agreements and submission
of all documents including Performance Bank Guarantee: 30% of
total cost
- On completion of customization as per requirement of Bank &
successful completion of UAT: 20% of total cost
- Implementation, go-live of Solution as per the scope of RFP- 15%
payable 3 months after Go Live and 15% payable 6 months after
Go Live i.e. at Sign Off.: 30% of total cost
- Completion of training & handing over of all documents and 6
months after Sign Off.: 20% of total cost
- On due performance and completion of project and after
completion of warranty period. It is made clear That in case
Vendor commits default/ breach in the performance of contract,
the Bank shall have absolute right to retain the 10% retention
amount and without recourse to the vendor, Bank can appropriate
towards the loss / damage/ penalty incurred.: 10% of total cost
No change in RFP term.
Page 35 of 50
173 Pg 145 of 165 Payment
Terms Clause7.16
e) Payment for annual maintenance charges:
The annual maintenance cost (after warranty period) shall be
paid at the end of each Half-year after the date of completion
of warranty period, subject to satisfactory services rendered,
till that date.
Bidder submits that the annual maintenance cost (after warranty
period) shall be paid Quarterly in Arrears
Please refer to Clause 4.18.2, Page No. 47 of
RFP 'Payment for annual maintenance
charges'. Please also refer to the
Corrigendum.
174 Pg 145 of 165 Payment
Terms Clause7.16
Payment Terms Bidder submits that the invoice raised shall be paid with 30 days
from the receipt of the invoice
As per RFP.
175 Pg 148 of 165Service Level
Agreement (SLA) and
Contracting Annexure C
5.3
Service Level Agreement (SLA) and Contracting Bidder understands that the maximum penalty under the SLA
Penalties including the Liquidated damages defined under this
project shall not exceed 10% of the Total Contract Value
As per RFP. No change in RFP term.
176 Pg. 36 of 165 Award of
Contract
clause 3.29.2
The notification of award will constitute the formation of the
Contract.
It is submitted that as per 3.30, a full fledged agreement needs to
be executed. It is hence requested to delete 3.29.2 as formation of
Contract will require agreement to be executed.
No change in RFP terms.
177 Pg 29 of 165 Period of
Validity of Bids Clause
3.16
3.16 Period of Validity of Bids
3.16.1 Bids shall remain valid for a period mentioned in Clause
7.2 from the date of opening of the Bid. A Bid valid for a
shorter period shall be rejected by the Bank as nonresponsive.
Bidder submits that the clause 7.2 mentions that Bids shall be valid
for 180 days from the date of submission and clause 3.16 says that
the validity of 180 days is from bid opening, please clarify which
one will prevail over the other
Please refer to the corrigendum.
178 Pg 37 of 165 Performance
Security / Guarantee
Clause 3.31
3.31.3 The selected bidder shall submit a Performance
Guarantee for an amount as mentioned in clause 7.6 from any
Nationalised/ Public Sector Bank in India other than Bank of
India and acceptable to Bank towards performance of the
contract, before execution of the contract, valid for period as
per clause 7.5 from the commencement of contract and with
further claim period of 12 months. Bank shall be within its
rights to invoke the performance guarantee without any
notice to the Vendor, if the Vendor in the opinion of Bank has
delayed or failed to perform its obligations under the contract
to the satisfaction of the Bank, or in the event of the Bank
terminating the contract and/or the Vendor failing to pay the
Penalty /Liquidated Damages payable to the Bank.
Bidder requests that the Performance Guarantee may be allowed
to be given from a Scheduled Bank as well.
It is submitted to revise the claim period to One month as 12 month
term is onerouns for the Bidders.
No change in RFP terms.
179 Pg 43 of 165 Performance
Guarantee
Clause 4.6
4.6.2 The proceeds of the performance security shall be
payable to the Bank as compensation for any loss resulting
from the Supplier’s failure to complete its obligations under
the Contract. Bank shall at its discretion has the absolute right
to appropriate the PBG’s upon breach or penalty without
notice.
Bidder requests to allow a cure period of 30 days before invoking
the Performance Guarantee
Please refer to the Clause 4.25.4, page 50.
Page 36 of 50
180 Pg 50 - 53 of 165
Termination for Default
clause 4.25
4.25 Termination for Default Bidder understands (as per 4.25.4) that the bidder shall be allowed
a cure period of 30 days for making right the default before
invoking the Termination for Default
Upon termination, the Bank shall pay for the products and or
services already delivered before the effective date of termination
As per RFP, no change in RFP term.
181 Pg. 50 of 165 Termination
for Default
Clause 4.25.5
The bidder would also be required to compensate the Bank
for any direct loss incurred by the Bank due to the
cancellation of the contract and any additional expenditure to
be incurred by the Bank to appoint any other bidder. This is
after repaying the original amount paid.
It is requested to delete the clause as the Bank is already invoking
the PBG to the extent of the loss suffered. There can be no
repayment of original amount paid for the invoices raised against
delivered portion of the work.
No change in RFP terms.
182 Pg. 51 of 165 Termination
for Convenience
Clause 4.28
the Bank shall also be entitled to terminate the Contract at
any time for its convenience by giving one month notice to
the Vendor.
It is requested to delet the clause.
In the alternative, it is requested that the notice period be
enhanced to 6 months and confirmed that the bidder shall be paid
for decommissioning charges as mutually arrived at.
No change in RFP terms.
183 Pg. 54 of 165 Indemnity
Clause 4.36
(iii) Breach of any terms of the Contract and/or the Service
level Agreement to be executed by the Vendor and/or breach
of any representation or warranty and/or.
(v) Breach of any of the terms of the Contract and/or Service
level Agreement by the subcontractors, if subcontracting of
any part is permitted by Bank and/or
(viii) Breach of any of the material terms of this agreement by
their subcontractors, if subcontracting of any part of this
agreement is permitted by Bank in writing.
The Bidder shall further indemnify the Bank against any loss
or damage arising out of loss of data, claims of infringement
of third-party copyright, patents, or other intellectual
property, and third-party claims on the Bank for
malfunctioning of the software or deliverables at all points of
time.
It is requested to delete subclauses (iii), (v) and (viii) as such
breaches would lead to claim for damages and not a claim of
indemnity.
Kindly delete the reference to "loss of data" as no liability or
indemnity can be provided for the same.
Kindly clarify that in no event shall either party be liable for any
indirect or consequential losses of any nature.
No change in RFP terms.
184 Pg 59 of 165 Acceptance
of Terms Clause 4.46
A Recipient will, by responding to the Bank’s RFP document,
be deemed to have accepted the terms as stated in this RFP
document.
Bidder requests to allow submission of certain modifications to the
terms and conditions of the RFP, which may be discussed at the
time of contracting
No change in RFP terms.
185 Pg. 62 of 165 Limitation of
Liability Clause 4.56
as per RFP It is requested to clarify that in no event shall either party be liable
for any indirect or consequential losses.
No change in RFP terms.
186 Pg 104 of 165 PROPOSAL
FORM (PRICE PROPOSAL)
Clause 6.1.2
PROPOSAL FORM (PRICE PROPOSAL) The Price Bid Format is missing from the RFP, request the same be
shared
The Indicative Price Bid is mentioned in
Format 6.3, Part-I, page No. 107-108 and
Format 6.3 Part-II, Page No. 109.
Page 37 of 50
187 Pg4
2. Objective
The solution will have to be upgraded by the Vendor free of
cost any time in the event of new scenarios or developing
EWS / any changes / modification / new regulatory
requirements or reporting requirements which warrants the
Bank’s compliance during the contract period
Bidder requests bank to consider efforts required for
development/modifications and provide complaince basis change
request.
No change in RFP term.
188 Pg 10
3.2 Broad Scope of Work
clause 3.2.1
Historical data of 10 years will be migrated from CBS Bidder requests bank to provide the data size of historical data.
Also please specify number of customer accounts.
Bank is using Oracle database size of approx.
50 TB.
189 Pg11 3.2 Broad Scope of
Work Clause 3.2.3.1
To detect financial stressed borrower accounts or in its
existing loan/lending portfolio (All Credit facilities with limits
above Rs. 25 lakhs).
Bidder requests bank to provide the number of accounts having
limit of Rs. 25 lakhs and above.
Please refer to the data at the end of this
document.
190 Pg22
3.3 Consortium
No consortium / sub-contract is allowed. Basis the clause we understand that bank expects bidder to
implement the proposed solution. Please note that generally we
sub contract in case we don't have the expertise. Request bank to
remove sub-contract.
No change in RFP terms.
191 Pg40
4.1 Definitions Clause
4.1.1
”Solution” means a package of Early Warning Signals (EWS)
application software, Bank’s Core Banking software, with
necessary hardware, servers, PCs, and system software,
database, third party utilities, middleware, etc. as proposed
by the Supplier, all seamlessly integrated to work together on
the Banks network to meet the Technical and functional
requirements of the Bank indicated in this document.
We understand that hardware, servers, PCs would be provided by
the bank. Request bank to remove the same from solution
definition.
Yes, the hardware will be provided by the
Bank. No change in RFP term.
192 Pg145
clause
7.16 Payment Terms
Payment for the Supply of required Software, Design,
Installation, Implementation, configuration, integration and
Commission of the EWS Solution shall be made as per Scope
of Work.
Bidder requests bank to segregate software and implementation
payments.
No change in RFP terms.
193 Pg149
clause 5.3.1.7
Penalty for delay in
project implementation:
For any delay in implementation of this project, the Bank
reserves the right to charge Liquidated Damages (LD)/ penalty
at the rate of 1% of the cost of the Purchase Order per week,
subject to a maximum of 10% of the Purchase Order Value
and the amount will be recovered from any other amount due
to the Vendor or by invoking the Performance Bank
Guarantee (PBG).
Bidder requests LD to be charged only on delayed/undelivered part
per week.
No change in RFP terms.
194 Pg48
Training
Clause 4.18.5
Batch size: 35-40 persons X 20 batches. Bidder wants understaning that -20 batches in each of the
mentioned locations or is it total of 20 bataches across all locations.
It is total of 20 batches across all locations.
195 Pg48
Training
Clause 4.18.5
Frequency of Training: Training as per need based
requirement of Bank.
Bidder want clarification that Can we have fixed frequency to
complete 20 batches?
No change in RFP terms.
Page 38 of 50
196 Pg11
3.2 Broad Scope of Work
Clause 3.2.3.1
To provide a warning signal in case of potential lending
opportunities that are in
Application /evaluation stage.
Bidder wants to understand that in case of Potential lending
opportunities, that are in application/evaluation stage, what are
the factors/parameters on the basis of which an Early Warning
Alert can be generated? How is it envisaged to implement Early
Warning on Potential Lending opportunities?
No change in RFP term.
197 Pg11
3.2 Broad Scope of Work
Clause 3.2.3.1
To be able to predict and take necessary corrective actions on
loan accounts based on their health as against the defined
directive of measurement of such assets.
Bidders request Bank to clarify what prediction is really sought for
over here? Bidder presumes PD model is already there to predict
defaults. Does corrective action means just sending notifications?
No change in RFP terms.
198 Pg11
3.2 Broad Scope of Work
Clause 3.2.3.2-1
Core Banking System Bidder requests clarification on
1. Total Number of Customers for EWS Monitoring (Retail or
Corporate)
2. Number of Accounts (Retail or Corporate)
3. Total Number of transactions in a day, month and year (Retail or
Corporate for monitoring)
4. Average TPS for transactions (Retail or Corporate)
5. Peak TPS for transactions (Retail or Corporate)
Please refer to the data at the end of this
document.
199 Pg12
EWS rule management
module
Clause 3.2.3.2
Transaction based parameters (e.g. excess withdrawal of cash
from loan accounts, transfer of loan funds to sister concerns,
transfer of loans)
Bidder wants to understand the the -Transfer of loan funds to sister
concerns has to be authorized with narration from the bank in
order to identify the payee as a sister concern of the obligor as the
related companies are not accounted for in the Relationship.
Similarly, clarification is required on what is meant by "transfer of
loans” and how it is carried out?
The solution should have capability for the
same.
200 Pg12
EWS rule management
module
Clause 3.2.3.2
Lists from regulators like RBI (e.g. SMA, C-KYC, CRILC, CERSAI)
and other
peer Banks
Bidder requests what lists are expected from other peer banks and
are they really provided to the subject bank? Also, in peer banks, is
consortium banking also included? How does the lead bank provide
narration for transactions?
Bidder wants to understand does fraud rule have to be integrated
to the EWS? These have different objective and different input
portfolio.
This will be shared with the successful vendor.
201 Pg12
EWS rule management
module
Clause 3.2.3.2
Alert rating mechanism, alert escalation matrix configurability
and features
Bidder request that Alert Escalation Matrix has to be defined by the
bank
This will be shared with the successful vendor.
202 Pg13 EWS reporting
module
The EWS solution is expected to have features around user
based dash boarding functionality.
Bidder Request clarification on below
1. Is the bank's expectation to integrate the reporting module with
any of its existing portal / dashboard or it can be a stand alone
reporting module?
2. Does the bank have any separate reporting software that it
would like to consume the data from the proposed EWS system
and do the required reporting?
It is self explanatory.
Page 39 of 50
203 Pg13 EWS case
management module
The EWS solution is expected to have features around case
management module where all alerts that are genuine for
which action needs to be taken for remediation are treated as
red flagged accounts.
Bidder Request clarification on below -
Does that bank has an existing case management system that it
would like the bidder to integrate with for case management
purpose? Please share the details of existing case management
system, if any.
This will be shared with the successful vendor.
204 Pg13 User based access
control and reporting
functionality
The EWS solution is expected to have features pertaining to
access control which will cover areas like:
Access privilege level configuration (i.e. who gets what access
or what rights)
Access granularity (to what extent can access be restricted
e.g. restriction of access at report level or data
extraction/saving etc.)
Bidder presumes that the bank has an Active Directory system in
place that can be used to give user / role based access to the EWS
system. Please clarify.
We envisage this capability in the Solution as
per RFP.
205 Pg14 Financial Intelligence
from Bank’s internal
sources clause
Clause3.2.3.2
Treasury systems: The Bank is currently using Treasury
application for front office, mid office and back office
operations, inputs from this module will include data for all
trading/rate agreements, which will include facilities such as
(indicative )
Bidder requests Bank to provide Treasury Application details used
by the bank
This will be shared with the successful vendor.
206 Pg14 Financial Intelligence
from Bank’s internal
sources clause 3.2.3.2
Security/collateral information: Inputs from
security/collateral management system for recording all
security provided against loans advanced by the Banks.
Security (property) valuation can be imputed from property indices.
Bank is requested to provide the source from which data for the
collateral valuation will be fetched. What are the security types
which the Bank intends to include within the scope of EW?
This will be shared with the successful vendor.
207 Pg14 Financial Intelligence Outstanding amount, payment history and loan servicing
delays (interest or principal amount)
Bidder Request clarification on below -
In case of consortium loan, how are the outstanding dues
determine when BOI Bank is:
a) Leader of the Consortium
b) Participants in the Consortium
This will be shared with the successful vendor.
208 Pg18 Broad Scope of Work
Clause3.2.3.5-2(xiii)e)
Any new regulatory requirement during / after
implementation must be covered.
Bidder understands that in the event that a new regulatory
requirement is required to be implemented, the same will be taken
up through a Change Request (CR) process.
No change in RFP terms.
209 Pg18 Broad Scope of Work
Clause3.2.3.5-2(xiii)f)
Necessary support should be provided to the IS Auditor
appointed by the Bank for conducting Vulnerability
Assessment and Penetration Testing (VAPT) on the solution
supplied.
Bidder understands that the third party auditor will be an
independent and unbiased party and audits will be carried out
during normal business hours and without any disruption to the
business and the project.
Bidder also understands that the third party auditor will execute
confidentiality agreement prior to access to the project
site/successful bidder's premise for any audit.
Such concerns will be taken care by the Bank.
210 Pg18 Broad Scope of Work
Clause 3.2.3.5-2(xiii)m)
The major responsibilities as specified above are indicative
only and are not exhaustive in any manner.
Bidder understands that the bidders will submit a technical
proposal that will comprehensively contain a detailed list of all
responsibilities and the scope prepared based on the RFP.
It is self explanatory.
Page 40 of 50
211 Pg18 The schedule of
Requirements
Deliverables Clause3.3.3.5-
ix
The Bidder / OEM must submit a detailed plan including the
manpower to be deployed during the post implementation
support of the solution. Manpower can be changed only with
an advance approval from the Bank.
Bidder requests the bank to clarify its expectation on the support
coverage. E.g. 9 X 5, 9 X 6, 14 X 6 etc.
Only one On-stie support engineer (L1) will
be required.
a) Work timings will be 8 hours from 10 am
to6 p.m. on all working days.
b) The desktop will be provided by Bank
c) In case of any emergeny/ exigency, Services
to be provided for extra hours at no extra
cost.
E) the location of posting the onsite engineer
will be at Mumbai.
f) The duration of onsite support resources
will include both Warranty and AMC period.
g) Bank will make no separate payment.
towards on site support engineers, it should
be factored/included in Price BId. All
payments/ expenses/risks etc. towards
onsite support engineer resources to be borne
by vendor including insurance.
212 Pg18
Clause 2-Xi-a
Seamless integration of supplied, customized, developed
software for Bank of India to meet the Bank’s Functional,
Operational, Risk Management, Regulatory and MIS
requirements of Credit Monitoring department (CrMD) with
all required interfaces. Integrate the proposed solution with
Bank’s Core Banking Solution, Treasury, CAPS, LMS, DMS,
IMAC, CMS cum Channel Finance, KYC and AML, EFRMS, Trade
Finance and other softwares with necessary interface on real
time basis.
Bidder Request clarification on below -
All data should reside in a common repository to be consumed for
EWS related rules/analytics. Monitoring/Investigation will be on
batch thus real time interfacing is not required. Data sourcing from
all mentioned systems should be on a pre-defined batch frequency.
Please suggest if this is acceptable to the bank
It is self explanatory.
213 Pg19 Broad Scope of Work
Clause3.2.3.6-5
Bidder / Solution Provider should incorporate regulatory
requirements and Global best practices while defining
requirements.
Bidder understand that the parties will discuss and document the
technical scope, timelines and commercial impact in the above-
mentioned CR document.
As per RFP.
214 Pg19 Scope related to
service Clasue3.2.3.7-e
After 5.5 year contract period, AMC will be extended by
bidder/vendor on mutually agreed terms.
Bidder requests to know What is the minimum extension period
that the bidder might be looking at?
This will be discussed/reviewed at the end of
contract period.
215 Pg50 Termination for
Default clause 4.25.5
The bidder would also be required to compensate the Bank
for any direct loss incurred by the Bank due to the
cancellation of the contract and any additional expenditure to
be incurred by the Bank to appoint any other bidder. This is
after repaying the original amount paid.
Bidder understands that this clause will not apply to this project as
payment are made only after acceptance of relevant
product/service.
No change in RFP term.
Page 41 of 50
216 Pg50 Termination for
Default clause 4.25.5
The progress regarding execution of the contract, made by
the selected Bidder is found to be unsatisfactory.
Bidder requests to specify the grounds under which the progress
will be marked as unsatisfactory.
As per RFP.
217 Pg54 Indemnity Clause
4.36
Bidder shall be responsible for any loss of data, Bodily injury,
loss of life, etc, due to acts of Bidder’s representatives, and
not just arising out of gross negligence or misconduct, etc, as
such liabilities pose significant risk.
Bidder requests Bank to ammend this clause as vendor does not
have any visibility/control on the customers or regulatory
authorities. Also, bidder should not be held responsible for
unintentional or accidental incidents.
No change in RFP term.
218 Pg55 Indemnity Clause
4.36
Indemnity would cover damages, loss or liabilities,
compensation suffered by the Bank arising out of claims made
by its customers and /or regulatory authorities.
Bidder understands that there would be proper and thorough
investigation before coming to a conclusion.
No change in RFP term.
219 Pg65
Data Integration
Capabilities:
Standardization and Data
Quality
The EWS should provide for transformation rules library that
can be generic to a data source and which is reusable for
creating other transformation rules. The transformation rules
are expected to help clean, standardize, match and enhance
data as it moves into the master reference file and is reused
for downstream processes.
Bidder Request more information and clarity on this requirement
with examples
We envisage this capability should be in
Solution.
220 Pg65 Data Integration
Capabilities:
Standardization and Data
Quality
The EWS should be rich in the set of in-built transformations
and functions that should include predefined table and
column-level transformations including slowly changing
dimensions.
The tool should provide pre-build functionalities for the
following:
- Financial Transformations
- Mathematical Transformations
- Statistical Computations
Bidder Request more information and clarity on this requirement
with examples
We envisage this capability should be in
Solution.
221 Pg65 Data Integration
Capabilities:
Standardization and Data
Quality
Support data quality measurement on an on-going basis
embedded into batch, near-time, and real- time process
Bidder Request more information and clarity on this requirement
with examples
We envisage this capability should be in
Solution.
222 Pg65 Data Integration
Capabilities:
Standardization and Data
Quality
Should support data cleansing and de-duplication, duplicate
suspect processing, house holding, with array of out-of-the-
box standardization rules conform data to corporate
standards – or can build customized rules for special
situations.
Bidder Request more information and clarity on this requirement
with examples
We envisage this capability should be in
Solution.
223 Pg65 Data Integration
Capabilities:
Standardization and Data
Quality
Should have business rules and GUI’s for automatic merging
and manual merging.
Bidder Request more information and clarity on this requirement
with examples
We envisage this capability should be in
Solution.
Page 42 of 50
224 Pg65 Data Integration
Capabilities:
Standardization and Data
Quality
The EWS should provide for Master Data Management with
semantic data descriptions of input and output data sources
uniquely identify each instance of a business element
customer, account, etc. and standardize the master data to
provide a single source of truth.
Bidder Request more information and clarity on this requirement
with examples
We envisage this capability should be in
Solution.
225 Pg65 Data Integration
Capabilities:
Standardization and Data
Quality
The EWS Should provide fuzzy logic to induce tolerance during
matching
Bidder Request more information and clarity on this requirement
with examples
We envisage this capability should be in
Solution.
226 Pg72 Early Warning
Indicators (ability to
generate results based on
different ranges such as
amount / period/No. of
times)
Alert for funding of the interest by sanctioning additional
facilities.
Bidder hopes that such funding entries can be distinctly identified
by transaction type within CBS or Loan System.
We envisage this capability should be in
Solution.
227 Pg74 Alerts from Trade
Finance System
(Illustrative listing given
below)
Alert for In merchanting trade, import leg not revealed to the
bank.
Bidder requests to know - Currently how is this data being
identified and captured in the system?
We envisage this capability should be in
Solution. It will be shared with the successful
vendor.
228 Pg74 Alerts from Trade
Finance System
(Illustrative listing given
below)
Alert for LCs issued for local trade/related party transactions. Bidder requests to know - Currently how is this data being
identified and captured in the system?
We envisage this capability should be in
Solution. It will be shared with the successful
vendor.
229 Pg82 Benchmarking The Default Benchmarks should be definable in the Solution
for all customers based on the Customer Category (Individual,
Corporate, Institution, NRI, etc.)
Bidder requests to clarify - According to RBI guidelines, EWS as a
subject is relevant for corporate borrowers. Does the bank intend
to include retail portfolio as well? If yes, then any specific reason of
doing so?
We envisage this capability should be in
Solution.
230 Pg88 Reporting Identify good customers and Enhance business by cross sell
campaigns thereby providing customer excellence
Bidder requests to clarify - This looks like data collection for healthy
accounts. How are these accounts identified? What are the types of
alerts required?
We envisage this capability should be in
Solution.
231 Pg89 General
Requirements
Should support processing on Real time, Online, Off-line,
batch mode, etc. Should also support scheduling and defining
of jobs.
Bidder requests that -EWS alerts need not be on real time basis as
it requires detailed investigation before a conclusion can be made
on the alert. Request bank to change requirement to batch
frequency which will be a standard practice
We envisage this capability should be in
Solution.
232 Pg93 Operating system All software including operating system licenses should be
provided by bidder.
Bidder requests the bank to reconsider this point and provide the
required software along with the hardware. Bidder will provide the
quantity required to be procurred.
Bank will provide only Windows/ Linux
RedHat Operating System. In case of any other
OS, price to be quoted.
Page 43 of 50
233 Pg94 Archival Bank requires the proposed Applications to be capable of
archiving all relevant data as per laid down Bank’s guidelines
Bidder requests for clarification -Is there any Archival Solution
currently being used? For example with Oracle Database- Oracle
Dataguard comes bundled. Or does Bank want Bidder to propose
archival solution also.
We envisage this capability should be in
Solution.
234 Pg97 Replication Solution to support local data and remote data replication for
all applications covered under the core suite, however the
DMS solution architecture should be centralized. The solution
should have the capability for federated architecture.
Request Bank to elaborate bank’s expectations for this requirement We envisage this capability should be in
Solution.
235 Pg98 IMPORTANT
INSTRUCTION: Other
Technical Specifcations
The solution should be capable of integrating with various
Bank systems viz. Core Banking solution, Treasury system,
Loan Origination Systems
Bidder requests for clarification - Number of Loan requests
processed in the Loan Origination System in a day, month or year
This will be shared with the succesful vendor.
236 Pg98 IMPORTANT
INSTRUCTION: Other
Technical Specifcations
The system should be able to handle multiple business units
of the Banks that include branches/Admin offices where
required.
Bidder requests for clarification -Do RRB and other subsidiaries
belong to this list?
No, RRB and other subsidiaries do not belong
to this list.
237 Pg99 Other Technical
Specifications
The Vendor should comply with Bank’s IS Security policy in
key concern areas relevant to the RFP.
Bidder requests for clarification -Whether BOI Bank will provide
their IS security policies in advance?
This will be shared with the succesful vendor.
238 Pg99 Other Technical
Specifications
Workflow for creating institutional memory for stake holders
for actionable remarks/ comments with automated reminders
through SMS, E-mails, any other messaging solution (e.g.
WhatsApp) to both action & info-stakeholders.
Bidder requests for clarification -Is it required for WhatsApp and
other messenger services, which requires Bank User consent for an
APP to be downloaded for usage?
We envisage this capability should be in
Solution.
239 Pg108 Important Notes:
Point 6
Bank will provide the hardware. Hardware sizing to be
provided by the bidders along with technical proposal.
To provide the hardware sizing, we need the following details -
• Total number of loan accounts to be monitored for EWS
• Total number of users handling EWS alerts/cases and
concurrency
• Number of daily transactions done on corporate loan accounts
and by other accounts owned by such corporate customers
Please refer to the data at the end of this
document
240 Pg149
clause5.3.1.7 Penalty for
delay in project
implementation:
For any delay in implementation of this project, the Bank
reserves the right to charge Liquidated Damages (LD)/ penalty
at the rate of 1% of the cost of the Purchase Order per week,
subject to a maximum of 10% of the Purchase Order Value
and the amount will be recovered from any other amount due
to the Vendor or by invoking the Performance Bank
Guarantee (PBG)
Bidder requests to limit the penalty for delayed implementation to
10% of the value of services for Implementation instead of the
order value.
No change in RFP term.
Page 44 of 50
241 Pg164 Process of E-tender
Annexure-E, Point 7(l)
Buyer reserves the right to cancel or reject or accept or
withdraw or extend the tender in full or part as the case may
be without assigning any reason thereof.
Bidder understands that cancel is synonymous to reject.
Bidder also understands that extend the tender means extension of
the due date of receipt of bid(s) as stated in Annexure-E, point 10
It is self explanatory.
242 Project Implementation
Schedule Page No. 6 of
165
Business Requirement Document (BRD) & System
Requirement Specification (SRS)- Within 30 days.
Customization & installation 30-45 days. Data Collection
& Integration 45-75 days. UAT 75-135 days. UAT –
System Validations & Report Generation 135-165 days.
Go-Live Within 180 days from date of PO .
Request you to rephrase it as: Business Requirement
Document (BRD) & System Requirement Specification (SRS)-
Within 30 days. Customization & installation 45-60 days.
Data Collection & Integration 60-120 days. UAT 120-180
days. UAT – System Validations & Report Generation 180-
210 days. Go-Live Within 240 days from date of PO .
The changes if any proposed in
implementation schedule, will be discussed
with the successful vendor while executing
SLA. There will not be allowed any change in
outer limit of 180 days given for complete
implementation including Go Live. The Vendor
will be allowed to give any combination of
milestones within outer limit of 180 days.
Accordingly, the penalty clause in relation to
the dealy in implementation will be linked to
the milestones proposed by successful bidder
for complete implementation including Go
Live within 180 days from PO. In case, while
executive SLA, both Bank and the successful
Vendor are not mutually agreed on the
proposed changes in schedule, the
implementation schedule given in RFP will be
final.
243 3.3 Consortium, Page No.
22 of 165
No consortium / sub-contract is allowed. Request the Bank to allow consortium in case an OEM and S.I wants
to be bid together.
Please refer to the eligibility norms given for
Bidder /OEM. Refer to Clause 3.4 Eligibility
Criteria page 22 and Format 6.14, Page 123 to
128.
244 3.4.2. Page No. 22 of 165 Bidder should have implemented and managed end to end
Early Warning Signal (EWS) Solution/ Risk Management/
Fraud Risk Management solution/ CBS successfully, in at least
One Private / Public Sector Bank having minimum business
mix of Rs. 1.50 lakh crore as on 31.03.2019. The location must
be a ‘Core Banking Solution’ in India. AND The EWS Solution /
Risk Management/ Fraud Risk Management Solution of the
OEM should have been implemented successfully in at least
one Private / Public sector Bank having minimum business
mix of Rs. 1.50 lakh crore as on 31.03.2019. The location must
be a ‘Core Banking Solution’ in India.
Request you to rephrase it as: Bidder should have implemented/
solution should have been implemented or under implementation
and managed end to end Early Warning Signal (EWS) Solution/ Risk
Management/ Fraud Risk Management solution/ CBS successfully,
in at least One Private / Public Sector Bank having minimum
business mix of Rs. 1.50 lakh crore as on 31.03.2019. The location
must be a ‘Core Banking Solution’ in India. OR The EWS Solution /
Risk Management/ Fraud Risk Management Solution of the OEM
should have been implemented successfully in at least one Private
/ Public sector Bank having minimum business mix of Rs. 1 lakh
crore as on 31.03.2019. The location must be a ‘Core Banking
Solution’ in India.
Please refer to the corrigendum.
Page 45 of 50
245 3.4.3. Page No. 22 of 165 The Bidder should have yearly sales turnover of not less than
Rs.50 Crores on standalone basis of the company during the
financial years FY 2015-16, 2016-17 and 2017-18
Request you to rephrase it as: The Bidder should have yearly sales
turnover of not less than Rs. 25 Crores on standalone basis of the
company during the financial years FY 2015-16, 2016-17 and 2017-
18
No change in RFP terms.
246 3.4.5 Page No. 23 of
165
The Bidder should have posted Profit after Tax (PAT) on
standalone basis of the company during financial years
of FY 2015-16, 2016-17 and 2017-18.
Request you to rephrase it as: The Bidder should have posted
Profit after Tax (PAT) on standalone basis of the company
during two of any three financial years of FY 2015-16, 2016-
17 and 2017-18.
No change in RFP terms.
247 7.16 Page No. 144 of
165
On delivery of product, execution of Agreements and
submission of all documents including Performance
Bank Guarantee - 20% of total cost. On completion of
customization as per requirement of Bank & successful
completion of UAT - 20% of total cost. Implementation,
go-live of Solution as per the scope of RFP- 15% payable
3 months after Go Live and 15% payable 6 months after
Go Live i.e. at Sign Off. After successful completion of
installation, commissioning, acceptability test, receipt
of deliverables, etc., and after the solution runs
successfully for six months after going live and Bank is
satisfied with the working on the system, the
acceptance certificate (as mutually decided and
approved by the Bank) signed by the Supplier (Vendor)
and the representative of the Purchaser (Bank) will be
issued. The date on which such certificate is signed
shall be deemed to be the date of successful
commissioning (or Sign off) of the systems as per Bank’s
Format 6.9. - 30% of total cost. Completion of training
& handing over of all documents and 6 months after
Sign Off - 20% of total cost.
Request you to rephrase it as: On delivery of product,
execution of Agreements and submission of all documents
including Performance Bank Guarantee - 20% of total cost.
On completion of customization as per requirement of Bank
& successful completion of UAT - 40% of total cost.
Implementation, go-live of Solution as per the scope of RFP-
15% payable 3 months after Go Live and 15% payable 6
months after Go Live i.e. at Sign Off. After successful
completion of installation, commissioning, acceptability
test, receipt of deliverables, etc., and after the solution
runs successfully for six months after going live and Bank is
satisfied with the working on the system, the acceptance
certificate (as mutually decided and approved by the Bank)
signed by the Supplier (Vendor) and the representative of
the Purchaser (Bank) will be issued. The date on which such
certificate is signed shall be deemed to be the date of
successful commissioning (or Sign off) of the systems as per
Bank’s Format 6.9. - 20% of total cost. Completion of
training & handing over of all documents and 6 months after
Sign Off - 10% of total cost.
No change in RFP terms.
248 Functional Requirements
/ 64
Reverse Integration module to feedback the other systems Elaborate more on the requirements stated w.r.t reverse
integration
It is self explanatory. We envisage this
capability should be in Solution.
249 Key Components &
Features envisaged in
EWS solution / 19
The Bidder would be responsible for implementing a well-
defined solution for Early Warning Signals (EWS) for all credit
facilities with limits above Rs. 25 lakhs.
Based on the RBI guidelines, the requirement is to have an EWS on
accounts with more than INR 50 cr exposure. Given that bank has
planned to consider accounts with limits above INR 25 lacs, can it
state the number of loan accounts and type of borrower - retail/
commercial and account owner - entity / individual ?
No change in RFP terms.
Page 46 of 50
250 Part 5 technical and
function specification/64
For reverse integration , customizations may required to be done in
your existing database and systems . That should be taken care of
by your existing IT vendors for such systems.
Bank will do changes as required in its own
existing systems however bidder to make
changes in proposed EWS Solution.
251 Functional Overview/75 Alert for substantial increase in unbilled revenue year after
year.
For various alerts and red flags to be raised, bank will provide the
criteria basis which such alerts to be raised . For example what
should be termed as substantial increase in unbilled revenue for an
account should be determined by the bank. Please confirm
We envisage this capability should be in
Solution.
252 Data Integration
Capabilities: Internal Data
systems / 64
The solution should support both online and off line data
validations and alerts.
Offline validation of data and alerts is not possible presuming the
requirement is to review alerts on the platform without any
internet and intranet. Please confirm and elaborate more on the
requirement offline validation of alerts generated through an EWS.
We envisage this capability should be in
Solution.
253 General Requirements/89 Should offer multi-currency support Request you to elaborate more on the end-use or module where a
multi currency functionality is expected from an EWS
We envisage this capability should be in
Solution.
254 Other Technical
Specifications/100
The application should have ability to interface with external
systems
Request you to elaborate more on this requirement in terms of
what kind of interface and with which external systems
It is self explanatory.
255 Consortium No consortium / sub-contract is allowed. Suggest Bank to relax the condition of consortium. No change in RFP terms.
256 Financial Websites / 15 Any publicly available data/ information would be part of
vendor scope and for paid subscription bank will decide
whether to purchase or not. The bidder is required to
indicate which subscriptions for external feeds are required
including but not limited to below. The bank will provide the
subscriptions to all the external feeds required, however it is
the Bidder’s responsibility to integrate with the required
external feeds.
There is a cost to integrate an external data feeds and given there is
not a defined scope prescribed for the data sources.
It would be fair to have a rate card on data source integration
based on the complexity, call frequency and processing.
No change in RFP terms.
257 Operating System / 93 Hardware will be provided by Bank. However
Hardware Sizing should be provided by the
bidders as part of technical Bid.
Suggest bank to share details of transactions processed primarily in
CBS, Branch Wise details, Account / User Group to recommend a
robust hardware for the solution.
Please refer to the data at the end of this
document.
Page 47 of 50
258 3.2.3.1 & Page No 11 The Bank is looking for a solution to provide an Early Warning
Signal (EWS) mechanism with the following objective: - To
detect financial stressed borrower accounts or in its existing
loan/lending portfolio (All Credit facilities with limits above
Rs. 25 lakhs).
Kindly elaborate the Total number of loan accounts to be
monitored for EWS. Also an indicative split of these Accounts
across different Lines of Businesses. This would be required from
an Implementation Scope point of view.
Please refer to the data at the end of this
document.
259 3.1.1 To comply with the guidelines of EASE / Reserve Bank of India
(RBI), Bank of India (hereinafter referred to BOI) wishes to put
in place end to end comprehensive IT Solution for Early
Warning Signals (EWS) to be implemented in Bank. It should
be in line with the Government / regulatory /anti money
laundering requirements as prescribed from time to time,
hosted at Bank’s Data Centre (DC) in Active / Passive mode,
along with DR and a minimum uptime time of 99.50%.
EWS systems are not used in Real-Time but based on scenarios &
rules. Based on this clause the Bank looking for Active site at DC
and Passive site at DR? Kindly confirm if our understanding is
correct.
Please refer to the corrigendum.
260 3.2.3.7 Environmental
Setup & Configuration,
Page:20
Detailed documentation on system set up & configuration of
UAT, Production
(DC),Fallback (DR) and Near- DR (if any) environments
How many envrionment sizing needs to be Provided?
Please clarify. We understand Bank would need only Production,
Development, Test and DR only
Bank will need all environment sizing as
mentioned in RFP.
261 3.2.3.7 Environmental
Setup & Configuration,
Page:20
Detailed documentation on system set up & configuration of
UAT, Production
(DC),Fallback (DR) and Near- DR (if any) environments
Please specify the exact percentage % of Production size that needs
to considered for other environments i.e. DR, UAT etc
Sizing is to be given by bidder as per data
provided by Bank.
262 Operating system, Page
:93, Point: 4
Hardware parameters (like CPU, Memory, hard disk,NIC, etc.)
should not cross the defined utilization levels at any point in
time.
what is utilization level that needs to consider for CPU core,RAM
and Stoarge?
Is this applicable to DR as well?
Kindly clarify
70% of the resources
Yes
263 Hardware Sizing, Page : 6 Supply of Server Hardware, OS, Database for EWS Solution
and other hardware requirements for EWS project
Implementation
How many years of Hardware sizing is required? What should be
growth rate that needs to consider for Year-on-Year increase for
Data size and user concurrency?
While arriving at Hardware sizing, vendor has
to take into consideration the existing volume
as well as the 5 -7 years (from go live)
projections as per the data given by the Bank.
15% annual increment in data. The user
concurrency as per point no. 7 on page 87 of
RFP.
264 The Broad scope of work
Page 17, Point 3.2.3.5
The broad scope of work is as follows:
i. Bank will provide the required hardware. Bidder should
provide the Hardware
sizing and specification as part of technical bid
Kindly elaborate the Total and concurrent number of users
handling EWS alerts/cases
Pl. refer to point no. 7, page 87 of RFP
Page 48 of 50
265 3.2.3.4 Page 16 The main scope is implementation of Early Warning Signals
(EWS) solution
is to have a report on market intelligence and portfolio
analysis of all Advance
accounts above Rs. 25 lakhs, its Inter Bank comparison
/analysis & dynamic
monitoring through Auto Alert System, etc. and
recommendations
forstrategic decisions at account/ portfolio level.
Average number of daily transactions done on these loan/lending
portfolio of accounts and other accounts owned by these
customers.
Please refer to the data at the end of this
document.
266 3.2.3.4 Page 16 The main scope is implementation of Early Warning Signals
(EWS) solution
is to have a report on market intelligence and portfolio
analysis of all Advance
accounts above Rs. 25 lakhs, its Inter Bank comparison
/analysis & dynamic
monitoring through Auto Alert System, etc. and
recommendations
forstrategic decisions at account/ portfolio level.
What is the indicative Number of documents that are currently
being considered from a Credit Monitoring point of view.
All standard documents as per Industry
Norms. This will be shared with the successful
bidder.
267 Point 3.2.3.1 EWS rule
management module
Page 12.
Configurable rules based on financial parameters namely:
Configurable rules based on non-financial parameters
Is there a indicative number of rules that Bank wants to implement. As per Part 5: Technical & functional
specifications.
268 Installation, Maintenance
and Support. Page 18
Integrate the proposed solution with Bank’s Core Banking
Solution, Treasury, CAPS, LMS, DMS, IMAC, CMS cum Channel
Finance, KYC and AML, EFRMS, Trade Finance and other
softwares with necessary interface on real time basis
EWS data integration is done on a batch basis where end of day
data is loaded into the repository for monitoring of borrowers. Real
time is requirement is relevant for fraud management where real
time decisioning is required. EWS is more about monitoring and
reporting. Please confirm if these are only EOD based batch mode
requirements and Bank is not expecting EWS to be a real time
system.
It is self explainatory.
Total No. of Corporate
borrowers
Total No. of accounts Total No. of transactions for accounts in a day
1500 2900 11000
CBS
Role of onsite support Engineers:Post acceptance, only two On Site Support Engineer will be needed, for which the role would be as follows:
1. Day to Day routine work
2. Data which needs to be uploaded in EWS Solution from Finacle or any other resources.
3. Generation of reports required by the department or the regulator or any other agencies.
4. Database tunning, backup, purging of any data or any database related activity
5. Any work of application management and database management
6. maintaing uptime for application
Page 49 of 50
Total No. of MSME
borrowers
Total No. of accounts Total No. of transactions for accounts in a day
29000 34000 112000
Total No. of Retail
borrowers
Total No. of accounts Total No. of transactions for accounts in a day
41000 43000 11000
Total No. of Agriculture
borrowers
Total No. of accounts Total No. of transactions for accounts in a day
6100 7500 9600
Total No. of
otherborrowers
Total No. of accounts Total No. of transactions for accounts in a day
1500 1800 2500
CBS
CBS
CBS
CBS
Page 50 of 50