Punjab & Sind Bank · 2019-06-14 · Punjab & Sind Bank Addendum - 6 (A Govt. of India Undertaking)...

Punjab & Sind Bank (A Government of India undertaking)

Addendum No. 6 Dated: 14/06/2019

Tender No. PSB/HOIT/RFP/131/2018-19 Dated 12.04.2019

Request for Proposal For

Selection of Vendor for Setting Up & Maintenance of Omni

Channel Digital Banking Solution

Punjab & Sind Bank, Second Floor, IT Department Plot Number 151, Sector 44,

Gurugram, 122003

Punjab & Sind Bank Addendum - 6

(A Govt. of India Undertaking)

Where service is a way of life

of 30

Contents

Introduction ................................................................................................................................... 3

Section 1: Modifications in RFP Dates .......................................................................................................... 3

Section 2: Modifications in RFP Clauses ....................................................................................................... 4

Section 2: Bank’s Volumetrics .................................................................................................................... 22

Section 3: Revised Eligibility Criteria ........................................................................................................... 24

Section 4: Revised Project Timelines .......................................................................................................... 27

Section 5: Revised Technical Bid Evaluation Criteria .................................................................................. 28




of 30

Introduction

Bank has published the RFP vide tender No. PSB/HOIT/RFP/131/2018-19 dated 12.04.2019 for Selection of Vendor for Setting Up & Maintenance of Omni Channel Digital Banking Solution

Following amendments have been made in the above stated RFP. All other terms and conditions of the RFP shall remain unchanged. Please treat this Addendum as an integral part of the RFP documents issued.

Addendum-6 for Setting Up & Maintenance of Omni Channel Digital Banking Solution

In reference to the aforesaid RFP, all are advised to note following:

Section 1: Modifications in RFP Dates

S.No RFP Pg.

RFP Section

Original Clause Revised Clause

1. 11 Section 2: Key Information

Bid submission last date and time

15.06.2019 14:00 HOURS

25.06.2019 14:00 HOURS

2. 11 Section 2: Key Information

Eligibility cum Technical bid opening date and time

15.06.2019 15:00 HOURS

25.06.2019 15:00 HOURS




of 30

Section 2: Modifications in RFP Clauses

S.No. RFP Pg.

RFP Section


1. -- Volumetric Bank’s Volumetric Please refer Section 3 for Bank’s Volumetric

2. 25 Section 7.2: Hardware Requirement

In case, Bidder fails to do so and the project demands additional components at a later stage, then Bidder will have to provide additional components at no additional cost to the bank. DB audit trail should be enabled across all environments and bidder is required to size the hardware accordingly.

In case, Bidder fails to do so and the project demands additional components at a later stage, then Bidder/ Consortium Partner will have to provide additional components at no additional cost to the bank. DB audit trail should be enabled across all environments and bidder is required to size the hardware accordingly.

3. Section 5: Eligibility Criteria

Entire Section Please refer Section 4 for the revised Eligibility Criteria

4. 16, 79 Section 5: Eligibility Criteria & Section 10.7: Technical Bid Evaluation

Addition Bank reserves the right to conduct reference site visit/ video conference/ voice call with the Client to substantiate the credentials/ copy of PO/ Contract copy/ sign-off submitted by Bidder and/ or OEM. In case the input/ feedback received from the Customer is negative/ unsatisfactory, bank reserves the right to reject the Bid.

5. 25 Section 7.2: Hardware Requirements

The bidder shall propose hardware (only from the sizing perspective) such that at any point in time during the contract period, the average CPU utilization should not exceed 70% at the primary data center.

The bidder shall propose hardware (only from the sizing perspective) such that at any point in time during the contract period, the average CPU utilization should not exceed 70% at the primary data center and Disaster Recovery Center. The average CPU utilization for Non-production Environments: Test, Training and Development should not exceed 80%.

6. 26 Section 7.2: Hardware Requirements

Bidder can consider Logical separation/ Virtualization for production and non-production environment at compute and storage level. The bidder should note that the production and non-production environment should

Bidder can consider Logical separation/ Virtualization for production and non-production environment at compute and storage level for respective Environments. The bidder should note that the production and non-




of 30

S.No. RFP Pg.

RFP Section


be physically separate. production environment should be physically separate with respect to Compute. Additional Clause: Bidder is required to consider and propose SAN Switch, Backup Solution (Backup Software, Backup Server, Tape Library, D2D) which can be used both for production and Non-Production environment Logical separation / Virtualization / zoning.

7. 28 Section 7.2: Hardware Requirements Responsibility Matrix

S.No. Solution DC DRC (% of DC)

HA

14 Development and customization instances

Only at DRC

20% of Prod

No

15 User acceptance testing / Sandbox instances

16 Product walkthrough, Training and handholding instances

17 Intermittent arrangement of migration instances

S.No. Solution DC DRC (% of DC)

HA

14 Development and customization instances

At DC Compute should be 20% of Prod DC

No

15 User acceptance testing / Sandbox instances

At DC Compute should be 20% of Prod DC

16 Product walkthrough, Training and handholding instances

At DR Compute should be 10% of Prod DC

17 Intermittent arrangement of migration instances

At DC Bidder is required to right size

8. 50 Section 7.17: Project Timeline

Project Timelines Please refer Section 4 for revised Project Timelines




of 30

S.No. RFP Pg.

RFP Section


9. 55 Section 8: Terms & Condition Clause 8.11: Performance Bank Guarantee (Addendum 4), Pt.8

The Bank shall also be entitled to make recoveries from the Successful Bidder's bills, Performance Bank Guarantee, or any other amount due to him due to inadvertence, error, collusion, misconstruction or misstatement.

The Bank shall also be entitled to make recoveries from the Successful Bidder's bills, Performance Bank Guarantee, or any other amount due to him due to collusion, misconstruction or misstatement.

10. 56 Section 8: Terms & Condition Clause 8.15: Insurance- Insurance Obligations of the Vendor

The equipment (software etc.) supplied under the contract shall be fully insured by the successful Vendor against loss or damage incidental to manufacture or acquisition, transportation, storage, delivery and installation. The insurance shall be obtained by the Vendor naming PSB as the beneficiary, for an amount equal to 100% of the invoiced value of the goods on all risks" basis. The period of insurance shall be up to the date the supplies are accepted and the rights of the property are transferred to Bank. The successful bidder shall ensure that the insurance policy is in force and make necessary arrangement for renewal of the policy whenever required. Should any loss or damage occur, the selected Bidder shall: i. initiate and pursue claim till settlement; and ii. Promptly make arrangements for repair and / or replacement of any damaged item irrespective of settlement of claim by the underwriters. The Vendor shall not hold the Bank responsible for rejection of the insurance claims of the Vendor by the insurer. The Vendors obligation to maintain insurance coverage

The equipment (software etc.) supplied under the contract shall be fully insured by the successful Bidder against loss or damage incidental to manufacture or acquisition, transportation, storage, delivery and installation. The insurance shall be obtained for an amount equal to 100% of the invoiced value of the goods on all risks" basis. The period of insurance shall be up to the date the supplies are accepted and the rights of the property are transferred to Bank. The successful bidder shall ensure that the insurance policy is in force and make necessary arrangement for renewal of the policy whenever required. Should any loss or damage occur, the selected Bidder shall: i. initiate and pursue claim till settlement; and ii. Promptly make arrangements for repair and / or replacement of any damaged item irrespective of settlement of claim by the underwriters. The Bidder shall not hold the Bank responsible for rejection of the insurance claims of the Vendor by the insurer. The Bidder's obligation to maintain insurance coverage hereunder shall be in addition to, and not in lieu of, the




of 30

S.No. RFP Pg.

RFP Section


hereunder shall be in addition to, and not in lieu of, the Vendors other obligations hereunder, and the Vendor’s liability to the Bank shall not be limited to the amount of coverage required hereunder. All the disputes arising out of or in connection with the agreement shall be deemed to have arisen in Delhi. Only the courts/s in Delhi shall have the jurisdiction to determine the same to the exclusion of all other courts'.

Bidder's other obligations hereunder, and the Bidder's liability to the Bank shall not be limited to the amount of coverage required hereunder. All the disputes arising out of or in connection with the agreement shall be deemed to have arisen in Delhi. Only the courts/s in Delhi shall have the jurisdiction to determine the same to the exclusion of all other courts’.

11. -- Section 8: Terms & Condition Clause 8.18: Indemnity (Addendum 4)

The bidder shall, at its own cost and expenses, defend and indemnify the Bank against all third-party claims (subject to notice in writing within 30 days of receipt of claim) arising out of the infringement of Intellectual Property Rights, including patent, trademark, copyright, arising from the performance of the contract that is directly attributable to the bidder in concurrence with the Vendor's Liability. The bidder, subject to being notified within 30 days of such claims and shall have full rights to defend itself therefrom. Subject to the above, if the Bank is required to pay compensation to a third-party resulting from such infringement, the Bidder will bear all court awarded damages/ expenses including legal fees, as awarded by the Court.

The bidder shall, at its own cost and expenses, defend and indemnify the Bank against all third-party claims (subject to notice in writing within 30 days of receipt of claim) arising out of the infringement of Intellectual Property Rights, including patent, trademark, copyright that is directly attributable to the bidder in concurrence with the Vendor's Limit to Liability agreed under the contract. The bidder, subject to being notified within 30 days of such claims and shall have full rights to defend itself therefrom. Subject to the above, if the Bank is required to pay compensation to a third-party resulting from such infringement, the Bidder will bear all court awarded damages/ expenses including legal fees, as awarded by the Court.

12. -- Section 8: Terms & Condition Clause 8.21: Vendor’s Liability (Addendum 4)

Notwithstanding anything contained in this RFP, the Vendor’s aggregate liability in connection with obligations undertaken as a part of the project regardless of the form or nature of the action giving rise to such liability (whether in contract, tort or otherwise) shall be at actuals and limited to the overall contract value. The vendor’s liability in case of claims against the

Notwithstanding anything contained in this RFP, the Vendor’s aggregate liability in connection with obligations undertaken as a part of the project regardless of the form or nature of the action giving rise to such liability (whether in contract, tort or otherwise) shall be at actuals and limited to the overall contract value. The vendor’s liability in case of claims against the Bank resulting from




of 30

S.No. RFP Pg.

RFP Section


Bank resulting from willful misconduct of the Vendor, its employees and subcontractors or from infringement of patents, trademarks, copyrights or such other Intellectual property rights or breach of confidentiality (excluding personal sensitive data), shall be unlimited. In no event shall either party be liable to the other for any indirect, incidental or consequential damages or liability, loss of profits or goodwill, revenue, and anticipated savings. Gross Negligence means serious disregard which involves an indifference to, and a blatant violation of a legal duty with respect to the rights of others, being a conscious and voluntary disregard of the need to use reasonable care, which is likely to cause foreseeable grave injury or harm to persons, property, or both. Willful Misconduct means where a party intentionally causes actual harm upon the other party and does not involve error or mistake in any form.

willful misconduct of the Vendor, its employees and subcontractors or from infringement of patents, trademarks, copyrights or such other Intellectual property rights or breach of confidentiality (excluding personal sensitive data), shall be limited to two times the contract value. In no event shall either party be liable to the other for any indirect, incidental or consequential damages or liability, loss of profits or goodwill, revenue, and anticipated savings. Gross Negligence means serious disregard which involves an indifference to, and a blatant violation of a legal duty with respect to the rights of others, being a conscious and voluntary disregard of the need to use reasonable care, which is likely to cause foreseeable grave injury or harm to persons, property, or both. Willful Misconduct means where a party intentionally causes actual harm upon the other party and does not involve error or mistake in any form.

13. 59 Section 8: Terms & Condition Clause 8.23: Subcontracting

Selected Bidder may subcontract or permit anyone other than its personnel to supply and maintain the hardware, OS, Peripheral Applications and its maintenance and is required under the contract. Bidder shall be the single point of contact and solely responsible for the supply, installation, implementation, integration, support and maintenance for the entire project that includes the hardware offered by the other Sub- Contracting members. However, Bidder will be solely responsible for ensuring adherence to the Service Levels, terms & condition and Service Quality for each of the

Selected Bidder may subcontract or permit anyone other than its personnel for the following activities: 1. Supply, installation and maintenance of the hardware 2. L1 Resources 3. OEM Services. OEM should ensure that OEM resources are on OEM's payroll.. Bidder shall be the single point of contact and solely responsible for the supply, installation, implementation, integration, support and maintenance for the entire project that includes the hardware and services offered by the other Sub- Contracting members. However, Bidder




of 30

S.No. RFP Pg.

RFP Section


deliverables executed by bidder and its sub-contractor(s). Bidder shall not sub-contract for any part of the RFP scope other than for the supply and maintenance of Hardware.

will be solely responsible for ensuring adherence to the Service Levels, terms & condition and Service Quality for each of the deliverables executed by bidder and its sub-contractor(s). Bidder shall not sub-contract for any part of the RFP scope other than the activities mentioned above.

14. -- Section 8: Terms & Condition Clause 8.24: Cancellation of Contract (Addendum 4)

The Bank reserves the right to terminate the order/ contract of the selected bidder (after providing a cure period of 30 days and thereafter providing a 90 days’ notice period) and recover expenditure incurred by the Bank on the following circumstances: 1. The selected bidder commits a material breach of any of the terms and conditions of the contract. 2. The bidder goes into liquidation voluntarily or otherwise. 3. An attachment is levied or continues to be levied for 7 days upon effects of the bid. 4. Termination if progress regarding the execution of contract by the bidder is not as per SLA, Timelines, scope of the RFP or if any material breach of contract. 5. Deduction on account of liquidated damages exceeds 10% of the total contract price. After the award of the contract, if the selected bidder does not perform as per the SLA, terms, conditions and timelines as mentioned in RFP or delays execution of the contract, the Bank shall give a 30 days cure period. Thereafter, if the selected bidder does not perform as per the SLA, terms, conditions and timelines as mentioned in RFP or delays execution of the contract, the Bank reserves the right to

Clause stands deleted




of 30

S.No. RFP Pg.

RFP Section


get the balance contract executed by another party of its choice. In this event, the selected bidder is bound to make good the additional expenditure, which the Bank incurs to carry out the bidding process and if any escalation of biding price for the execution of the balance of the contract to be borne by Bidder. However, this cost is capped to 5% of the contract value. This clause is applicable if for any reason the contract or a part of the Contract is cancelled. The Bank reserves the right to recover any dues payable by the selected bidder from any amount outstanding to the credit of the selected bidder, including the pending bills and/or invoking Bank Guarantee, if any, under this contract. In case of any termination of the contract, the Bidder shall be paid for all the services/ products provided by the Bidder until the date of termination after deducting any penalties, Liquidated damages and/or invoking PBG as the case may be. In the event of termination by the Bank, the Bidder shall be paid for the following services till the date of termination: 1. Goods delivered 2. Services rendered 3. Unpaid AMCs and ATS

15. 65 Section 8: Terms & Condition Clause 8.38: Compliance with Statutory and Regulatory Provisions

It shall be the sole responsibility of the Vendor to comply with all statutory, regulatory & Law of Land and provisions while delivering the services mentioned in this RFP. All suggested changes due to changes in Changes in Govt. Rule, Changes by Regulators shall be done without extra cost to the Bank, till SRS Sign-off. All

It shall be the sole responsibility of the Bidder as an entity registered in India to comply with all statutory, regulatory & Law of Land and provisions while delivering the services mentioned in this RFP. All suggested changes due to changes in Changes in Govt. Rule, Changes by Regulators shall be done without extra cost to the Bank, till SRS Sign-




of 30

S.No. RFP Pg.

RFP Section


subsequent changes can be on mutually agreed change request basis.

off. All subsequent changes can be on mutually agreed change request basis.

16. 65 Section 8: Terms & Condition Clause 8.39: Legal Compliance

The successful bidder hereto agrees that it shall comply with all applicable union, state and local laws, ordinances, regulations and codes in performing its obligations hereunder, including the procurement of licenses, permits and certificates and payment of taxes where required. If at any time during the term of the agreement, the Bank is informed or information comes to the Bank's attention that the Successful bidder is or may be in violation of any law, ordinance, regulation, or code (or if it is so decreed or adjudged by any court, tribunal or other authority), the Bank shall be entitled to terminate the agreement with immediate effect. The Successful bidder shall maintain all proper records, particularly but without limitation accounting records, required by any law, code, practice or corporate policy applicable to it from time to time including records, returns and applicable documents under the Labour Legislation. The Successful bidder shall ensure payment of minimum wages to persons engaged by it as fixed from time to time under the Minimum Wages Act, 1948. In case the same is not paid, the liability under the act shall solely rest with the successful bidder.

The successful bidder hereto agrees that it shall comply with all applicable union, state and local laws and regulations in performing its obligations hereunder, including the procurement of licenses, permits and certificates and payment of taxes where required. If at any time during the term of the agreement, the Bank is informed or information comes to the Bank's attention that the Successful bidder is or may be in violation of any law or regulation (or if it is so decreed or adjudged by any court, tribunal or other authority), the Bank shall be entitled to terminate the agreement with immediate effect. The Successful bidder shall maintain all proper records, particularly but without limitation accounting records, required by any law, code, practice or corporate policy applicable to it from time to time including records, returns and applicable documents under the Labour Legislation. The Successful bidder shall ensure payment of minimum wages to persons engaged by it as fixed from time to time under the Minimum Wages Act, 1948. In case the same is not paid, the liability under the act shall solely rest with the successful bidder.

17. 67 Section 8: Terms & Condition Clause 8.43: Termination

1. The Bank shall be entitled to terminate the agreement at any time by giving at least 30 days notice if: a. The bidder breaches its obligations under the tender document or the subsequent agreement and if the

1. The Bank shall be entitled to terminate the agreement at any time by giving at least 30 days notice if: a. The bidder breaches its obligations under the tender document or the subsequent agreement and if the




of 30

S.No. RFP Pg.

RFP Section


material breach is not cured within 30 days from the date of notice. b. The bidder (i) has a winding up order made against it; or (ii) has a receiver appointed over all or substantial assets; or (iii) is or becomes unable to pay its debts as they become due; or (iv) enters into any arrangement or composition with or for the benefit of its creditors; or (v) passes a resolution for its voluntary winding up or dissolution or if it is dissolved. 2. The bidder shall have right to terminate only in the event of winding up of Bank.

material breach is not cured within 30 days from the date of notice. b. The bidder (i) has a winding up order made against it; or (ii) has a receiver appointed over all or substantial assets; or (iii) is or becomes unable to pay its debts as they become due; or (iv) enters into any arrangement or composition with or for the benefit of its creditors; or (v) passes a resolution for its voluntary winding up or dissolution or if it is dissolved. 2. The bidder shall have right to terminate only in the event of winding up of Bank. The Bank reserves the right to terminate the order/ contract of the selected bidder (after providing a cure period of 30 days and thereafter providing a 90 days’ notice period) and recover expenditure incurred by the Bank on the following circumstances: 1. The selected bidder commits a material breach of any of the terms and conditions of the contract. 2. The bidder goes into liquidation voluntarily or otherwise. 3. An attachment is levied or continues to be levied for 7 days upon effects of the bid. 4. Termination if progress regarding the execution of contract by the bidder is not as per SLA, Timelines, scope of the RFP or if any material breach of contract. 5. Deduction on account of liquidated damages exceeds 10% of the total contract price. After the award of the contract, if the selected bidder does not perform as per the SLA, terms, conditions and timelines as mentioned in RFP or delays execution of the contract, the Bank shall




of 30

S.No. RFP Pg.

RFP Section


give a 30 days cure period. Thereafter, if the selected bidder does not perform as per the SLA, terms, conditions and timelines as mentioned in RFP or delays execution of the contract, the Bank reserves the right to get the balance contract executed by another party of its choice. In this event, the selected bidder is bound to make good the additional expenditure, which the Bank incurs to carry out the bidding process and if any escalation of biding price for the execution of the balance of the contract to be borne by Bidder. However, this cost is capped to 5% of the contract value. 6. The Bank shall also be entitled to terminate the agreement at any time by giving at least 30 days’ notice if: a. The bidder (i) has a winding up order made against it; or (ii) has a receiver appointed over all or substantial assets; or (iii) is or becomes unable to pay its debts as they become due; or (iv) enters into any arrangement or composition with or for the benefit of its creditors; or (v) passes a resolution for its voluntary winding up or dissolution or if it is dissolved. 7. The bidder shall have right to terminate only in the event of winding up of Bank. This clause is applicable if for any reason the contract or a part of the Contract is cancelled. The Bank reserves the




of 30

S.No. RFP Pg.

RFP Section


right to recover any dues payable by the selected bidder from any amount outstanding to the credit of the selected bidder, including the pending bills and/or invoking Bank Guarantee, if any, under this contract. In case of any termination of the contract, the Bidder shall be paid for all the services/ products provided by the Bidder until the date of termination after deducting any penalties, Liquidated damages and/or invoking PBG as the case may be. In the event of termination by the Bank, the Bidder shall be paid for the following services till the date of termination: 1. Goods delivered 2. Services rendered 3. Unpaid AMCs and ATS

18. 67 Section 8: Terms & Condition Clause 8.43: Termination, Effects of Termination, Pt. 1

Bank shall pay Bidder all fees for Services performed by Bidder till the effective date of termination of the Agreement

Point stands deleted

19. -- Section 8: Terms & Condition Addendum 4: Audits

Client can conduct any third party inspection / audit for any phase. The bidder must make all necessary changes as mentioned by the results of these audits. Client will incur the cost of appointment of a third party for audit. The bidder must ensure that the findings of the audit are successfully closed by the bidder within a mutually agreed timeline. The Successful Bidder(s) shall allow the Client, it’s authorized Personnel, its auditors (internal and external) and/or other statutory authorities, Statutory Authorities

Bank can conduct any third party inspection / audit for any phase. The bidder must make all necessary changes as mentioned by the results of these audits. Bank will incur the cost of appointment of a third party for audit. The bidder must ensure that the findings of the audit are successfully closed by the bidder within a mutually agreed timeline. The Successful Bidder(s) shall allow the Bank, it’s authorized Personnel, its auditors (internal and external) and/or other statutory authorities, and unrestricted right




of 30

S.No. RFP Pg.

RFP Section


shall have unrestricted right to inspect and audit the operations and records directly related to the services. The Cost & Accounting Records will be out of scope for the purpose of audit conducted by the Bank. If the Successful Bidder(s) is outsourcing any portion of the above activity, it will be the responsibility of the Successful Bidder(s) to ensure that the authorities/officials as mentioned above are allowed access to the places, systems, processes, records (expect Cost & Accounting Records) etc. of the activity, for inspection and verification. The Successful Bidder(s) shall keep complete and accurate records of all the operations in connection with the activities, per prevalent best practices in the industry. All books, records (except Cost & Accounting Records) and information relevant to the services shall be preserved in isolation and be presented to the Client or its designees for inspection as and when demanded. The Successful Bidder(s) should recognize the right of Reserve Bank of India (RBI) to cause an inspection to be made of the Successful Bidder(s) / service provider and its books and accounts by one or more of its officers or employees. One week’s of prior intimation shall be shared with the bidder, regarding the audit so as to notify the Client any potential conflict of interest. Except in cases of regulatory and statutory audits, the Client shall not exercise right to audit more than twice in a financial year.

to inspect and audit the operations and records directly related to the services. The Cost & Accounting Records will be out of scope for the purpose of audit conducted by the Bank. If the Successful Bidder(s) is outsourcing any portion of the above activity, it will be the responsibility of the Successful Bidder(s) to ensure that the authorities/officials as mentioned above are allowed access to the places, systems, processes, records (expect Cost & Accounting Records) etc. of the activity, for inspection and verification. The Successful Bidder(s) shall keep complete and accurate records of all the operations in connection with the activities, per prevalent best practices in the industry. All books, records (except Cost & Accounting Records) and information relevant to the services shall be preserved in isolation and be presented to the Bank or its designees for inspection as and when demanded. The Successful Bidder(s) should recognize the right of Reserve Bank of India (RBI) to cause an inspection to be made of the Successful Bidder(s) / service provider and its books and accounts by one or more of its officers or employees or other designated person. One week’s of prior intimation shall be shared with the bidder, regarding the audit so as to notify the Bank any potential conflict of interest. Except in cases of regulatory and statutory audits, the Bank shall not exercise right to audit more than twice in a financial year.

20. -- Section 8: Terms & The risk, title and ownership of the goods supplied The risk, title and ownership of the goods supplied under




of 30

S.No. RFP Pg.

RFP Section


Condition Addendum 4: Risk & Title

under this contract shall be transferred on to the Client on installation & acceptance of goods at the Client's site.

this contract shall be transferred on to the Client on delivery of goods at the site.

21. -- Section 8.31: Payment Terms

Addition Payment Terms for Building, Managing and Maintaining API: 30%- On successful signoff of SRS Document 40%- On UAT Signoff from the Bank 30%- Go-Live

22. 68 Section 8.31: Payment Terms

Payment Terms for:

Data Migration Audit, VAPT and IS Audit

25% Submission of Data Migration Audit Approach

50% Submission of draft Data Migration Audit Report

25% Submission of final Data Migration Audit Report

Payment Terms for:

Data Migration Audit, VAPT and IS Audit

25% Submission of respective Audit Approach

50% Submission of respective draft Audit Report

25% Submission of respective final Audit Report

23. 68 Section 8.31: Payment Terms

Payment Terms for:

Implementation Cost for Omni Channel

40% Successful sign off of SRS document by the bank.

25% Successful completion of customization of the module

25% UAT Signoff from the Bank

10% On successful release to production & acceptance by the bank with English & Hindi Language.

10% Go-Live of the Solution

Payment Terms for:

Implementation Cost for Omni Channel

40% Successful sign off of SRS document by the bank.

25% Successful completion of customization of the module

25% UAT Signoff from the Bank

5% On successful release to production & acceptance by the bank with English & Hindi Language.

5% Go-Live of the Solution




of 30

S.No. RFP Pg.

RFP Section


with all other specified languages

with all other specified languages

24. 86 Section 10.7: Technical Bid Evaluation Criteria

Entire Section Please refer Section 5 for the revised Technical Bid Evaluation Criteria

25. -- Section 12: Service Levels & Penalties

Additional Clause The bidder shall not be penalized for any SLA breach outside the scope of bidder and for any reason not attributable to the Bidder.

26. 99 Section 12: Service Levels & Penalties

Implementation Penalty

The selected bidder must adhere to the timelines as

stated in the RFP. Delay in successful implementation of

the solution within the stipulated timelines shall attract

penalty

In case, Bidder has not implemented the solution within

the stipulated timelines, the bidder shall be liable to pay a

penalty of equivalent to 1 (one) percent of the

implementation cost of the respective solution for every

week of delay or part thereof.

Point stands deleted

27. -- Addendum 4, Pt.21, Section 12: Service Levels & Penalties

Level Classification: Severity 1 During business hours: Response Time: 30 mins Resolution Time: 2 hrs During Non-business hours: Response Time: 45 mins Resolution Time: 4 hrs Severity 2 During business hours: Response Time: 1 hr

Level Classification: Severity 1 During business hours: Response Time: 30 mins Resolution Time: 1 hrs During Non-business hours: Response Time: 45 mins Resolution Time: 2 hrs Severity 2 During business hours: Response Time: 30 mins




of 30

S.No. RFP Pg.

RFP Section


Resolution Time: 4 hrs During Non-business hours: Response Time: 1 hrs Resolution Time: 6 hrs Severity 3 During business hours: Response Time: 2 hrs Resolution Time: 6 hrs During Non-business hours: Response Time: 2 hrs Resolution Time: 8 hrs

Resolution Time: 2 hrs During Non-business hours: Response Time: 45 mins Resolution Time: 3 hrs Severity 3 During business hours: Response Time: 2 hrs Resolution Time: 4 hrs During Non-business hours: Response Time: 2 hrs Resolution Time: 6 hrs

28. -- Addendum 4, Pt.22, Section 12: Service Levels & Penalties, Cross Functional, Incident Management Services, Calculation

Call Tickets per month responded and resolved within the timelines divided by the total number of call tickets per month Severity 1 During business hours: Response Time: 30 mins Resolution Time: 2 hrs During Non-business hours: Response Time: 45 mins Resolution Time: 4 hrs Severity 2 During business hours: Response Time: 1 hr Resolution Time: 4 hrs During Non-business hours: Response Time: 1 hrs Resolution Time: 6 hrs Severity 3

Call Tickets per month responded and resolved within the timelines divided by the total number of call tickets per month Severity 1 During business hours: Response Time: 30 mins Resolution Time: 1 hrs During Non-business hours: Response Time: 45 mins Resolution Time: 2 hrs Severity 2 During business hours: Response Time: 30 mins Resolution Time: 2 hrs During Non-business hours: Response Time: 1 hrs Resolution Time: 3 hrs Severity 3




of 30

S.No. RFP Pg.

RFP Section


During business hours: Response Time: 2 hrs Resolution Time: 6 hrs During Non-business hours: Response Time: 2 hrs Resolution Time: 8 hrs

During business hours: Response Time: 2 hrs Resolution Time: 4 hrs During Non-business hours: Response Time: 2 hrs Resolution Time: 6 hrs

29. 99 Addendum 4, Pt.23 Section 12: Service Levels & Penalties

The Bank reserves the right to recover the penalty from any payment to be made under this contract. The penalty would be deducted from the quarterly payouts and the cap on quarterly penalty will be 10% of the quarterly payout. For the purpose of this RFP, the total of penalties as per SLA and the Liquidated damages will be subject to a maximum of 10% of the overall contract value.

The Bank reserves the right to recover the penalty from any payment to be made under this contract. The penalty would be deducted from the payouts. For the purpose of this RFP, the total of penalties as per SLA and the Liquidated damages will be subject to a maximum of 10% of the overall contract value.

30. -- Appendix 1A: Functional Specifications; IMPS, Pt.2

Solution must be able to support all latest version of Mobile Devices/OS/IOS/Windows/Android etc. for the entire contract period.

Solution must be able to support all latest version of Mobile Devices OS like IOS and Android for the entire contract period.

31. -- Appendix 1A: Functional Specifications; IMPS

Addition IMPS should be integrated with FI and CBS

32. -- Appendix 1A: Functional Specifications; IMPS, Technical Requirements, Pt.1

IMPS solution shall have the capability of processing 150 Transaction Per Second and should be scalable.


33. -- Appendix 1A: Functional Specifications; UPI,

UPI solution shall have the capability of processing 500 Transaction Per Second and should be scalable





of 30

S.No. RFP Pg.

RFP Section


Technical Requirements, Pt.1

34. -- Appendix 1B: Technical Specifications; D2D, Pt. 2

The proposed D2D storage should be configured with minimum 60 TB backend usable capacity. The capacity of the proposed D2D storage/appliance must cater to sequential backup read/write workload and should be configured with SAS 10K/15K or NL-SAS 7.2K RPM Disks of less than 4TB and must be able to complete full backup of 15 TB Data in 1 Hour and equivalent time for restoration. This is minimum requirement, bidder is required to factor the sizing in line with the proposed application and database architecture.

The proposed D2D storage should be configured with minimum 60 TB backend usable capacity. The capacity of the proposed D2D storage/appliance must cater to sequential backup read/write workload and should be configured with SAS 10K/15K or NL-SAS 7.2K RPM Disks of less than 6TB and must be able to complete full backup of 15 TB Data in 1 Hour and equivalent time for restoration. This is minimum requirement, bidder is required to factor the sizing in line with the proposed application and database architecture.


Write Cache should be mirrored between controllers on a controller pair.

Write Cache/ NVRAM/ DRAM should be mirrored between controllers on a controller pair to protect rights or a mechanism where proposed back disk storage/ appliance should be offered with cache/ NVRAM/ DRAM for protection against data loss in power/ controller failure scenarios.


In the event of power failure, the cache needs to have battery backup for at least 72 hours or destage to permanent flash.

In the event of power failure, the cache / NVRAM/ DRAM needs to have battery backup for at least 72 hours or destage to permanent flash.


Offered Storage Array should be configurable in a No Single Point of Configuration including Array Controller card, Backplane, Cache Memory, FAN, Power Supply etc.

Offered Storage Array / Disk Appliance should be configurable in a No Single Point of Configuration including Array Controller card, Backplane, Cache Memory, FAN, Power Supply etc.

38. -- Appendix 1B: Technical Specifications; D2D,

The proposed storage should offer minimum 32 GB Usable Data Cache / DRAM available after memory mirroring / protection overheads. Bidders to offer more

The proposed storage array/disk appliance should offer minimum 32 GB Usable Data Cache / DRAM /NVRAM available after memory mirroring / protection overheads.




of 30

S.No. RFP Pg.

RFP Section


Pt. 10 memory if required by the Storage / Appliance. Bidders to offer more Data Cache/DRAM/NVRAM if required by the storage array/disk appliance.

39. -- Appendix 1B: Technical Specifications; Backup Software, Pt. 9

For Faster recovery, backup data should be preferably kept in usable format eliminating the need for restoring large amounts of data and simply mapping the production servers to the backup target array.

For Faster recovery, backup data should be preferably kept in usable format eliminating the need for restoring large amounts of data and simply mapping the production servers to the backup target array. If the proposed backup software do not support this feature, then the bidder can propose backup data in native format.

40. -- Appendix 1B: Technical Specifications; Backup Software, Pt. 10

The proposed solution should support the following algorithms and provide better security in deployment across sites - BLOWFISH, GOST, Serpent, AES, Twofish, 3-DES’

The proposed solution should support the following algorithms and provide better security in deployment across sites - BLOWFISH/GOST/Serpent/AES/Twofish/3-DES.

41. -- Appendix 1B: Technical Specifications; Storage, Pt. 18

Proposed storage is required to be scalable to 512 GB Usable Cache, Cache upgrade can be done by either adding the cache to the controller or adding more controller to the storage. 100 TB Usable Capacity & 1,00,000 IOPS on 4K block size at 50:50 r:w ratio to meet future requirements.

Proposed storage is required to be scalable to 512 GB usable Data cache / memory available across the pair of controller post write mirroring / protection overheads, Cache upgrade can be done by either adding the cache to the controller or adding more controller to the storage. 100 TB Usable Capacity & 1,00,000 IOPS on 4K block size at 50:50 r:w ratio to meet future requirements.

42. -- Appendix 2: Bill of Material

Bill of Material Updated format for Commercial Bill of Material will be shared with Bidders who have purchased the RFP document on submission of Tender Document Fees.




of 30

Section 2: Bank’s Volumetrics

S.No. Particulars As on Date

1. Total number of registered Customers per channel

Internet Banking Retail: 5,00,000 Corporate: 15,000

Mobile Banking: 10,00,000 *This include IMPS

UPI: 3,00,000

2. Total number of Accounts registered per channel Internet Banking Retail: 5,00,000 Corporate: 15,000

Mobile Banking: 10,00,000 *This include IMPS

UPI: 3,00,000

Internet Banking- Retails Customers

3. Total number of registered Retail users for Internet Banking

5,00,000

4. Max number of Retail users Logged on to Internet Banking System at any point of time

50,000

5. Period over which transaction history data has to be maintained in Retail e-banking solution database

10 years

6. Average number of requests/queries received per day from the customers by all relationship managers

80

7. Periods over which requests/queries data received by relationship manager has to be maintained in Retail e-banking database

6 months

8. Number of financial transactions during peak hour (one hour window)

1,000

9. Number of non-financial transactions during peak hour (one hour window)

1,000

10. Percentage of Simple Transactions (like balance enquiry / mini statement )

15%

11. Percentage of Medium Transactions (like fund transfer / payment transactions)

80%

12. Percentage of Complex Transactions (like detailed statement / batch transactions)

5%

Internet Banking- Corporate Customers

13. Total number of registered Corporate users for Internet Banking

15,000

14. Max number of Corporate users Logged in to Internet Banking System at any point of time

1500

15. Period over which transaction history data has to be maintained in corporate e-banking solution database

10 years

16. Average number of requests/queries received per day from the customers by all relationship managers

30

17. Periods over which requests/queries data received by relationship manager has to be maintained in corporate e-banking database

6 months




of 30

S.No. Particulars As on Date


800


500


15%


80%

22. Percentage of Complex Transactions (like detailed statement / batch transactions)

5%

Mobile Banking

23. Total number of Accounts with Mobile Banking facility 10,00,000

24. Max number of Mobile users Logged in to Mobile Banking System at any point of time

350

25. Average number of Financial transactions per day 16,000

26. Average number of Non-Financial transactions per day 20,000

27. Period over which transaction history data has to be maintained in m-banking database

June 2013


1,500


2,000


20%


80%

UPI

32. Max number of users Logged in to UPI Ecosystem at any point of time

200

33. Average number of Financial transactions per day 80,000

34. Average number of Non-Financial transactions per day 1,20,000

35. Period over which transaction history data has to be maintained in UPI database

April 2017


8,000


10,000

PKI Solution

38. PKI Registration 10,00,000 tokens for 5 years

Transaction Per Second

39. Omni Channel 200 Scalable to 500




of 30

Section 3: Revised Eligibility Criteria

Bank is looking for eligible bidders for selecting a Vendor for Setting up & Maintenance of Omni Channel Digital Banking Solution.

Only those Bidders who fulfil the following criteria are eligible to respond to the RFP. Offers received from Bidders who do not fulfil any of the following eligibility criteria are liable for rejection.

If required, bidder may utilize participating entities to provide part of the scope of work. However, bidder will be responsible for delivering the end to end solution. Bidder shall also be the single point of contact and solely responsible for the implementation, integration, support and maintenance for the entire project. Bidder will be solely responsible for ensuring adherence to the Service Levels, terms & condition and Service Quality for each of the deliverables executed. The bidder must fulfil the criteria mentioned in the table below in order to bid for this RFP:

S.No. Eligibility Criteria Supporting Documents

Bidder’s Experience

1. The bidder should be a Government Organization/ PSU/ PSE /Public/ Private Limited Company under companies Act, 1956 India or later.

Certificate of Incorporation

2. The Bidder should have been in operation for at least 5 years as on as on date of bid submission.


3. The Bidder should have an annual turnover of INR 100 Cr. for each of the past three financial years i.e. 2015-16, 2016-17 & 2017-18 from its IT operations in India

Copies of Annual Reports in case of listed companies and copies of audited balance sheets and P&L statements in case of others. AND CA Certificate

4. The bidder should have a positive net-worth in any two out of last three financial years i.e. 2015-16, 2016-17, 2017-18

Copies of Annual Reports in case of listed companies and copies of audited balance sheets and P&L statements in case of others. AND CA Certificate

5. The Bidder should not have been blacklisted at the time of submission of the bid by any regulator / statutory body/ any government department/ PSU/ PSE/Financial Institution or banks in India.

Self-Declaration on Bidder’s Letterhead signed by the authorized signatory

6. The bidder should be an OEM or a certified or authorized agent/ reseller/ partner of the solution offered

Manufacturer’s Authorization Form

7. The bidder must be CMMI level 5 Certified Company and the certificate should be valid as on date of bid submission

Copy of certification

8. The Bidder should have experience of implementing and managing any Internet Banking or Mobile Banking for at least one Scheduled Commercial Bank in India OR The Bidder should have experience of

For Domestic Credentials: For completed projects: Relevant Credential Letter from the client or PO/ Contract Copy along with Sign off from the client




of 30


implementing and managing any Internet Banking or Mobile Banking for at least one Bank abroad having a total business of more than 50,000 cr Only completed/ On-going/ initiated projects would be considered for evaluation Only completed/ On-going/ initiated projects would be considered for evaluation

For on-going projects: PO/ Contract copy

And

Self-Declaration on Bidder’s Letterhead signed by the board authorized signatory confirming the total business of the client

For Foreign Credentials: Self-Declaration on Bidder’s Letterhead signed by the board authorized signatory/ Company Secretary

OEM’s Experience

1. The OEM for Omni Channel should have presence in India for least last 5 years as on as on date of bid submission.


2. OEM’s Omni-Channel Digital Banking Product should have been implemented/under-implementation in at least one Scheduled Commercial Bank in India having more than 1500 branches and 15,00,000 users OR OEM’s Internet and Mobile Banking Product should have been implemented /under-implementation in at least one Scheduled Commercial Banks in India having more than 1500 branches and 15,00,000 users Or OEM’s Internet or Mobile Banking Product should have been implemented and live in at least one Scheduled Commercial Banks in India having more than 1500 branches and 15,00,000 users

*The Proposed Internet Banking, Mobile Banking and Omni Channel Solution should be from the Same OEM.

For Implemented projects: Relevant Credential Letter from the client or PO/ Contract Copy along with Sign off from the client

And

Self-Declaration on Bidder’s Letterhead signed by the board authorized signatory confirming the total number of users

3. The proposed UPI Solution should have been implemented in at least one scheduled commercial bank in India with more than 1500 branches or having 5,00,000 users.

For completed projects: Relevant Credential Letter from the client or PO/ Contract Copy along with Sign off from the client

4. The proposed IMPS Solution should have been implemented in at least one scheduled commercial bank in India with more than 1500 branches or having 5,00,000 users.

For completed projects: Relevant Credential Letter from the client or PO/ Contract Copy along with Sign off from the client

5. External testing agency should have experience of functional testing & data migration in areas of

For Domestic Credentials: Relevant Credential Letter from the




of 30


Internet & Mobile Banking/ Omni-Channel Banking for one scheduled commercial Bank in India or a Bank Abroad, having a total business of 50,000 cr

client Or Copy of Purchase Order/ Contract And


For Foreign Credentials: Self-Declaration on OEM’s Letterhead signed by the board authorized signatory/ Company Secretary

Note:

Attested photocopies of all relevant documents / certificates should be submitted as proof in

support of the claims made. The bidder should provide relevant additional information wherever

required in the eligibility criteria. The Bank reserves the right to verify /evaluate the claims made

by The Bidder independently. Any decision of The Bank in this regard shall be final, conclusive

and binding upon the Bidder.

Scheduled commercial banks do not include small finance banks, payment banks, regional rural banks and cooperative banks.

Either the Indian agent on behalf of the Principal/OEM or Principal/OEM itself can bid but both

cannot bid simultaneously for the same solution.

In case of business transfer where bidder has acquired a Business from an entity (“Seller”), work

experience credentials of the Seller in relation to the acquired Business may be considered.

In-case of corporate restructuring the earlier entity’s incorporation certificate, financial

statements, Credentials, etc. may be considered.

If an agent submits a bid on behalf of the Principal/ OEM, the same agent shall not submit a bid

on behalf of another Principal/ OEM for the same solution.

Proposed solution need not be the proposed version of the solution

Bidder is required to propose a product with inbuilt framework of extension and not a

framework to build digital banking capabilities.

Branches mean bank branches only and exclude extension counters, satellite offices, part-shifted

branches, ultra-small branches, specialized branches and banking correspondents.




of 30

Section 4: Revised Project Timelines

The Selected Bidder shall be responsible for overall implementation and rollout of Omni-channel digital banking solutions required under this RFP and also must agree to the time duration specified. If the BIDDER fails to do so within the stipulated time schedule or by the date extended by the Bank, it will be a breach of contract. In such case, the Bank would be entitled to charge a penalty as specified in this RFP.

The time period required for the completion of activities is mentioned below:

Activity Duration (T + Months) Hardware & Software Delivery T+ 1.5 months Hardware, OS & DB Installation T+ 3 months SRS Finalization & Sign-off by Bank T+ 3 months SIT & UAT T+ 7 months

Sign-off and Go-Live of the Solution **i.e. Go-Live with at least English and Hindi language

T+ 10 months

Go-Live of the Multi-Lingual features T+13 months

**T is the date of signing of Contract




of 30

Section 5: Revised Technical Bid Evaluation Criteria

The technical bid submitted by the Bidder will be evaluated only if they fulfil the eligibility criteria. The technical bid evaluation will be done on a total score of 1000. The proposal evaluation will be based on the evaluation matrix consisting of the following parameters.

S. No. Evaluation Criteria Maximum Marks

Minimum Marks

Minimum Passing

Percentage

1. Functional Specifications 300 270 90%

2. Technical Specifications 200 200 100%

3. Bidder & OEM’s Capability and Experience 200 150 75%

4. Technical Presentation 100 80 80%

5. Product Demonstration 200 160 80%

Total 1000 860 86%

Bidders scoring at least the minimum score in each section mentioned in the table above and an

overall score of 860 marks or more will be declared technically qualified.

The bidders scoring less than 860 marks (cut-off score) out of 1000 marks in the technical evaluation

shall not be considered for further selection process and their offers will be dropped at this stage.

Bidders should score minimum as mentioned in the above table.

In case none of the participating bidders qualify on technical criteria by reaching or exceeding the cut

off score of 86%, then the bank, at its sole discretion, may relax the cut-off score to a lower value,

which, in any case, shall not fall below 75%. In case at-least two participants have not scored 75%,

then the Bank reserves the right to cancel and go for retendering process. However, this would be at

the sole discretion of the Bank.

If only one bidder qualifies, Bank at its discretion may select bidders with the top two technical scores for final evaluation process. Bank, at its discretion, may choose to open the commercial bid of the only bidder who qualifies. Bank at its discretion may reject the proposal of the Bidder without giving any reason whatsoever, if in Bank’s opinion, the Solution Sizing was not made appropriately to meet the performance criteria as stipulated by Bank.

The evaluation of technical proposals, among other things, will be based on the following:

S.No. Technical Evaluation Evaluation Methodology

1 Functional Specifications

Max. Marks- 300 marks

The Bidder is required to submit the compliance for Functional Specifications. Bidders should score 90% in Compliance to Functional Specifications (Appendix 1A).

Marks would be awarded as:

Status Marks

Standardized Product (S) 10

Customization (C) 5

The total marks of the Appendix will be scaled down on a scale

of 300 marks

2 Technical Specifications


The Bidder is required to submit the compliance for Technical Specifications. Bidders must score 100% in




of 30


Compliance to Technical Specifications (Appendix 1B).

Marks would be awarded as:

Status Marks

Yes (Y) 10

No (N) 0

The total marks of the Appendix will be scaled down on a scale of 200 marks

3 Bidder & OEM’s Capability

and Experience


Bidder’s Experience The Bidder should have experience of implementing and managing any Internet Banking or Mobile Banking for at least one or more Scheduled Commercial Banks in India

or

The Bidder should have experience of implementing and managing any Internet Banking or Mobile Banking for at least one or more Banks abroad having a total business of more than 50,000 cr (50 marks)

- Only completed/ On-going/ initiated projects would be considered for evaluation

Supporting Document For Domestic Credentials: For completed projects: Relevant Credential Letter from the client or PO/ Contract Copy along with Sign off from the client

For on-going projects: PO/ Contract copy

And



OEM’s Experience OEM’s Omni-Channel Digital Banking Product should have been Implemented in Scheduled Commercial Bank(s) in India having more than 1500 branches and 15,00,000 customers Four or more credentials (150 marks) Three credentials (100 marks) Two credentials (75 marks) One credential (50 marks)

Please further note:




of 30


Incase OEM submits a credential of both Internet and Mobile Banking Solution that has been implemented in a Scheduled Commercial Bank in India having more than 1500 branches and 15,00,000 customers it will be scored same as above.

Incase OEM submits a credential of Internet or Mobile Banking Solution that has been implemented in a Scheduled Commercial Bank in India having more than 1500 branches and 15,00,000 customers it will be scored as 80% of the above.

Incase OEM is providing a reference of a foreign bank, the said credential/ reference should have at least 20, 00,000 users. 80% of the marks of respective category of credentials will be given in case any of credentials/reference are from foreign Banks. However, at least one credential has to mandatorily be of India.

80% of the marks will be given in case bidder submits the credential of any under implementation projects of any of the above. This 80% marks will be of respective credential marks/category as stated above

Supporting Document

For Domestic Credentials: For completed projects: Relevant Credential Letter from the client or PO/ Contract Copy along with Sign off from the client

And

Self-Declaration on Bidder’s Letterhead signed by the board authorized signatory confirming the total number of users


4 Technical Presentation


All eligible bidders will be required to make presentations.

The bank will schedule presentations and the time and

location will be communicated to the bidders. Failure of a

bidder to complete a scheduled presentation to the bank

may result in rejection of the proposal.

5 Product Demonstration


All eligible bidders will be required to showcase the overall

solution proposed. The bank will schedule product

demonstration and the time and location will be

communicated to the bidders. Failure of a bidder to

complete a scheduled product demonstration to the bank

may result in rejection of the proposal.

Punjab Sind Bank Pre-Bid Replies- Part 2 RFP Ref: PSB/HOIT/RFP/131/2018-19

S.No. RFP Section (Point No.) RFP Pg

No.

RFP Excerpt Query PSB Reply

1 Appendix 1A: Functional

Specifications; IMPS; Pt.5

Transaction processing P2P, P2A, P2U, P2M, M2P and file

upload both remitter and beneficiary

P2P & P2A - exists

However, P2U & P2M ,M2P is scrapped as per latest NPCI

guidelines. Please advise if this should be as per latest NPCI

guidelines

Yes, Bidder to adhere to NPCI guidelines


Specifications; UPI

For UPI, do you need only backend services (issuer platform)?

Do you need acquirer platform? In that case, do you need

separate UPI app or integrated with Mobile Banking App?

Bank requires both issuer and acquirer platform with Omni

Channel.


Specifications; UPI; Pt.17

Solution must provide complete Merchant onboarding

module with all reports and Admin portal. It should also

support bulk merchant onboarding.

For merchants, is the portal required for the bank or for

merchants as well?

Yes, Portal is required for both- Merchant and Bank


Specifications; UPI; Pt.16

IMPS Switch should build in Software Security Module. HSM

supports should available

Why HSM required in UPI? NPCI common library will be distributed to PSP (Payment

Service Provider)’s which needs to be embedded into the

PSP App for secure credentials capture. NPCI common

library will be available for all the major mobile operating

systems viz. Android, iOS Phone. Credentials will be

encrypted by a 2048 bit NPCI public key using PKI. UPI will

use HSM to decrypt the credential and re-encrypt using

issuer bank’s 2048 bit public key. Issuer Bank will use their

HSM to decrypt and validate the credential.

Issuer Bank will get the encrypted credentials as part of the

RuPay (debit) or other meta-APIs like Balance Inquiry, OTP

request etc. These credentials will be encrypted using the

PSP public key shared with NPCI for UPI. Issuer bank will

store the private key in FIPS certified temper resistant PKI

HSM to decrypt the credentials and process the transaction.

PKI HSM should have a feature of dynamic onsite firmware

upgrade to accommodate any changes in the UPI

application architecture as per the directives of NPCI or IT

ACT 2000 / 2008. PKI HSM should be Post Quantum Ready

so that HSM works with Post Quantum Ready algorithms in

case of any regulatory requirements from RBI, NPCI or

Government of India.


Specifications; IMPS; Pt.2

Solution must be able to support all latest version of Mobile

Devices/OS/IOS/Windows/Android etc. for the entire

contract period.

Windows OS on mobile devices will run out of support soon.

Request to consider iOS and Android only

Please refer Addendum for the revised clause

6 Section 7.17: Project

Timeline

51 Project Timelines NPCI certification time for each channel to be kept out of scope

of implementation timelines since it is dependent on NPCI

Please be guided by the RFP

7 Section 6: Scope Summary;

Pt.1

20 MADP Platform Does the bank expect an off the shelf MADP product or can we

propose a mobile development framework that meets the

requirements of technical compliance ?




No.


8 Addendum 4

Section 8: Terms and

Conditions

Clause 8.21: Vendor’s

Liability

9 Latest Corrigendum Current Clause after corrigendum: Notwithstanding anything

contained in this RFP, the Vendor’s aggregate liability in

connection with obligations undertaken as a part of the project

regardless of the form or nature of the action giving rise to such

liability (whether in contract, tort or otherwise) shall be at

actuals and limited to the overall contract value. The vendor’s

liability in case of claims against the Bank resulting from wilful

misconduct of the Vendor, its employees and subcontractors or

from infringement of patents, trademarks, copyrights or such

other Intellectual property rights or breach of confidentiality

(excluding personal sensitive data), shall be unlimited.

In no event shall either party be liable to the other for any

indirect, incidental or consequential damages or liability, loss of

profits or goodwill, revenue, and anticipated savings. Gross

Negligence means serious disregard which involves an

indifference to, and a blatant violation of a legal duty with

respect to the rights of others, being a conscious and voluntary

disregard of the need to use reasonable care, which is likely to

cause foreseeable grave injury or harm to persons, property, or

both. Wilful Misconduct means where a party intentionally

causes actual harm upon the other party and does not involve

error or mistake in any form.

Changed clause: Notwithstanding anything contained in this

RFP, the Vendor’s aggregate liability in connection with

obligations undertaken as a part of the project regardless of the

form or nature of the action giving rise to such liability (whether

in contract, tort or otherwise) shall be at actuals and limited to

the overall contract value. The vendor’s liability in case of claims

against the Bank resulting from wilful misconduct of the Vendor,


9 General We have 2 clauses on Termination for clause 8.24 and 8.43 . The

contradiction between 2 clause on payment in the event of

termination seems to have been resolved since both the clauses

mentions more or less payment for the service provided. But we

need clarity if there is any difference between these 2 clause

and if yes, then how payment will happen exactly. In case No,

request to delete one of the clauses to avoid confusion.




No.


10 Penalty

Clause 8.14 and in clause 12

99 There are 2 places where Penalty for implementation is

specified. clause 8.14 and in clause 12(page 99). Under clause

8.14 RFP mentions that the penalty is 0.5% of the complete

contract value per week of delay or part thereof for delay in

delivering goods or services as per the timelines and amximum

deduction is 10% of the total project value.. However under

clause 12(page 99) RFP mentions the penalty as 1% of the

implementation cost of the respective solution. This is

contradictory and we request:

a. Penatly for delay to be @0.55 of the implementation cost of

the respectve solution as it cannto be a % of the contract value.

It should always be at percentage of the milestone delayed

b. Also implementation penalty shall be capped at 10% of the

total implementation value of the respective solution.

LD will be imposed during delivery, installation and

implementation.

Penalty due to SLA shall be applicable post Go-Live of the

Solution(s).

11 Section 8.31: Payment Terms 62 For Billing terms for implementation team would need to be

checked against the months in which the same would be

delivered and if any gaps. Software billing term are stretched. If

Bidder SWG is involved this billing term would be highly difficult

for approval. Else If we have only GBS We can try to get a back

to back with vendor if we cannot get this changed


12 Annexure 1: Bank Guarantee

Form

103 This guarantee will remain in force up to and including 180

days after the period of the bid validity i.e. up to (mention

date of expiry which should be a minimum of bid validity =

180 days),

We request to rectify the highlighted term which looks to be an

error as the EMD shall be valid till the bid validity period which

is 180 days from bid submission and not for 180 days after the

bid validity period.

No Change in Clause.

However, Bidder to note that the validity of bid is 180 days

from the date of bid submission.

13 General Sizing questionnaire Kindly refer to enclosed sheet (excel) for volumetrics required

for sizing . Request you to share the same urgently as without

these details it will not be possible to size the solution

appropriately.

Please refer Addendum for the Volumetric

14 General Bid Submission date Since sizing based on voulumetric & solutioning to integrate

multiple solutions/ plaltforms will be required, we request time

for submission to be extended till 20 June for approvals and

proposing a comprehensive techno-commercial bid resposne

Please refer Addendum for the revised submission date


Specifications; Retail IB &

MB; Pt.1.10.1

1.10.1 The solution should allow maker/checker/approver role for

all modules defined by the Bank

Maker-Checker and Authorisation is a Corporate Banking

functionality.

Is this requirement applicable for Retail Banking Customers?

Who is expected to be the Checker/Authoriser in the process?

Bank will define the users for various roles during SRS Phase



MB; Pt.6.7.1.4

6.7.1.4 Apply online for loan Please provide more details on the Loan application process

steps.

Additionally, please let us know the number and type of loan

porducts that have to be estimated as part of this RFP?

Requisite details will be shared with the successful bidder

during SRS phase



MB; Pt.6.13.9

6.13.9 Wealth Management Please provide detailed information on the scope of

functionality to be implemanted as part of Wealth

Managemement?




No.



Specifications; Corporate IB

& MB; Pt.3.2.8

3.2.8 Captcha and audio message for login Does the Bank expect vendor to provide and budget for captcha

/ audio message framework?

Or will the channel applications integrate with any exixsting

Captcha / Audio Message framework at the Bank.

Bidder is required to ensure that the proposed Omni

Channel Digital Banking Solution has the said functionality



& MB; Pt.6.13.13.1 -

6.13.13.7

Tax Payment Please provide details on the functionalities expected to be

implemented as part of each Tax payment requirement.




& MB; Pt.6.17.1

6.17.1 The solution should support real-time customer analytics &

predictive analytics from various sources

Does the Bank expect implementation of a Customer analytics /

predictive analytics backend engine?

The proposed Dgital channel solution will integrate with these

backend.





& MB; Pt.6.17.2

6.17.2 Customer should have the ability to do monthly budgeting Does the Bank expect vendor to propose a PFM tool to support

this requirement?

Incase there is an existing PFM tool that the proposed solution

will untegrate with, please provide more information on the

same.





& MB; Pt.6.17.4

6.17.4 The solution should have the capability for Spending

Analytics

Same as above Bidder is required to ensure that the proposed Omni




& MB; Pt.6.17.5

6.17.5 The solution should have the capability for analytics based

cross-sell offers

Does the Bank expect implementation of a Offers engine based

on customer analytics ?

The proposed Dgital channel solution will integrate with thes

Offers engine to enable the required functionality.





& MB; Pt.6.18.8

6.18.8 eComm payment acceptance Please provide more details on this requirement. Please be guided by the RFP



& MB; Pt.6.15.2

The solution should have the provision to maintain outside

PSB account details

Please provide more details on this requirement and the

expected mode of integration for getting outside PSB account

information?




& MB; Pt.6.15.3

The solution should have the provision to maintain policy

details

Please provide more details on the functionalities expected to

be implemented as part of this requirement?

Please be guided by the RFP. Further details will be shared

with the successful Bidder during the SRS phase



& MB; Pt.6.15.4

The solution should have the provision to maintain MF Please provide more details on the functionalities expected to





Specifications; MADP; Pt.17

17 The solutions should provide a visual administration and

monitoring

Please provide more details on this requirement. Please be guided by the RFP



No.


29 Section 5: Bidder's Eligibility

Criteria; Pt.8

16 The Bidder should have experience of implementing and

managing any Internet Banking or Mobile Banking for at

least one Scheduled Commercial Bank in India having a total

business of 1,00,000 cr OR The Bidder should have

experience of implementing and managing any Internet

Banking or Mobile Banking for at least one Bank abroad

having a total business of more than 1,00,000 cr Only

completed/ On-going/ initiated projects would be

considered for evaluation

Request relaxation in the Eligibility Criteria, in terms of business

size of the Bank. Since the implementation experince is with a

Scheduled Commercial Bank, bidder's credential can be

established. The clause may be

modified as follows: The Bidder should

have experience of implementing and managing any Internet

Banking or Mobile Banking for at least one Scheduled

Commercial Bank in India having a total business of 60,000 cr OR

The Bidder should have experience of implementing and

managing any Internet Banking or Mobile Banking for at least

one Bank abroad having a total business of more than 60,000 cr

Only completed/ On-going/ initiated projects would be

considered for evaluation

Please refer addendum for the revised clause

30 Section 5: OEM's Eligibility

Criteria; Pt.4

17 The proposed IMPS Solution should have been

implemented in at least one scheduled commercial bank in

India with more than 1500 branches

Request relaxation in the Eligibility Criteria, in terms of number

of branches. Since the implementation experince is with a

Scheduled Commercial Bank, OEM's credential can be

established. The clause may be modified as folows:

The IMPS Solution should have been implemented in at least

one scheduled commercial bank in India with more than 900

branches


31 Addendum 4; Pt.2: Scope of

Work for PKI Solution

Bidder is required to take over the support of the existing

PKI solution along with underlying infrastructure. Bidder is

required to perform the user migration, credential

migration & data migration.

Bidder is required to factor in the AMC and ATS for the

existing PKI Solution till the sunset of the existing

application & infrastructure. The new proposed Application

and its related infrastructure should ensure adherence to

the scope and SLA as defined in the RFP.

Bidder is required to design, size, supply (Replace/

Upgrade), implement, integrate, maintain and manage the

PKI Solution and its related infrastructure for entire contract

duration.

Bank is currently using PKI Solution provided by Snorkel

For bidder to take over support of existing PKI solution, Please

share Architecture/High level diagram of existing PKI setup.

Please refer Addendum 5 for the revised Scope for PKI

Solution.



No.
















duration.



share foll. Infrastructure details for existing PKI solution.

• Hardware

• Software

• Operating System

• Database

• Snorkel Version

• form factor

• Other platform details


Solution.















duration.


Request bank to confirm bidder's understanding that bank or its

appointed vendor will continue to support the hardware,

operating system, database, platform, middleware etc of

existing PKI solution.


Solution.















duration.



share License and support/AMC details of existing PKI solution.


Solution.



No.
















duration.



Provide sizing/integration details of Internal and External

Users/Devices/Servers/Applications and usage of existing PKI

solutions.


Solution.















duration.


Please confirm that for the scenario where bidder takes over

support of the existing PKI solution, Any support required from

Bank existing PKI OEM/partner will be available till the

migrations is successfully completed.


Solution.















duration.


Request bank to confirm whether the same set of users will be

migrated from the existing PKI solution to new PKI solution or

there will be two different set of users till the migration

completes.


Solution.



No.
















duration.


Request bank to confirm whether both (old & new) PKI solution

will function till migration?


Solution.















duration.


Request bank to confirm Why Bank wants to use both

(existing/new) PKI solution simultaneously as it will

operationally be more suitable to continue with one PKI

solution.


Solution.















duration.


Bidder suggests to decommission existing PKI solution once the

new solution is functional to optimize on cost, overhead of

managing two solutions and use set up based on more modern

standards. Request bank to confirm whether bidder can

propose this option.


Solution.



No.
















duration.


Request bank to clarify whether there are any specific use cases

and services expected from new PKI solution apart from given

specifications.


Solution.















duration.


11.Does the bank have an HSM device that is integrated with

existing PKI solution? If Yes, please confirm whether the same

HSM device will be leveraged for the new solution or will it need

to be replaced?


Solution.

43 Addendum 4; Pt.6 Bidder is required to migrate the Transaction log,

application logs, DB logs etc. for the previous 10 years from

the existing systems to the new proposed systems. The

maintenance of the archival of the data will be done either

on Storage, Hard Disk, Tape or DAT drive or any other

means desired by Bank/guidelines issued by RBI.

It is bidder's understanding that consumable media (tapes),

Offsite Fireproof Tape vault & offsite movement of tapes will be

provided / handled by Bank or its appointed vendor. Request

bank to confirm on the same.

Bidder is required to provision the consumables (tape

cartridges) as mentioned in the RFP. After the mentioned

number is utilized / consumed Bank will provide the

consumables. Offsite Fireproof Tape vault & offsite

movement of tapes will be provided / handled by Bank or

its appointed vendor.

44 Addendum 4; Pt.6 Bidder is required to migrate the Transaction log,


the existing systems to the new proposed systems. The

maintenance of the archival of the data will be done either

on Storage, Hard Disk, Tape or DAT drive or any other

means desired by Bank/guidelines issued by RBI.

Request bank to confirm the log size for previous 10 years that

needs to be migrated.

Log Size for Internet Banking: 450 GB

Log Size for Mobile Banking (including IMPS): 100 GB

45 Addendum 4; Pt.7 On site availability of L1 & L2 resource 24*7*365 Support

for the solution to meet the Service Levels

Request bank to clarify whether bidder can propose shared L2

resources located at its command centre while L1 resources will

be located onsite. This will help the bank to optimize on

operating cost of the project.




No.


46 Addendum 4; Pt.9 If the bank buys any other supplemental hardware which is

of the same OEM or is OEM recommended from a third

party and installs it within these hardware under intimation

to the bidder then the warranty should not become void.

However, the warranty will not apply to such supplemental

hardware is installed.

It is bidder's understanding that any supplemental hardware

parts that needs to be added to any of the bidder supplied

hardware will need to be procured through the bidder. Request

bank to confirm on the same.


47 Pre-Bid Replies; Pt.393 NLDR will be a site required to achieve Zero Data Loss. The

Operational activities will not be running from NDR. Only

delta Re-Sync will happen from NDR to DR, in order to make

DR available with Zero RPO

Request bank to consider near zero data loss at NLDR site as

Zero data loss will require transaction to be committed at NLDR

site before commit at DC site which will result in performance

degradation at DC Production instance.


48 Pre-Bid Replies; Pt.396 Bidder is required to keep full DB copies for DC, DR,

Development and Test Environment. For training

environment, Bidder is required to right size.

Request bidder to consider a optimized but fully functional DB

copy at Development and Test Environment as it will be only

masked or test data that will be populated in Dev & Test DB and

not actual production data. Hence it need not be the same size

as production DB.


49 Pre-Bid Replies; Pt.457 Backup Server is to be deployed in HA mode both at DC and

DR from Day One.

Request bank to modify this requirement to standalone backup

server at both DC & DR as per standard industry practice.



Timeline

51 Hardware & Software Delivery T+ 1.5 months

Hardware, OS & DB Installation T+ 3 months

As it would normally take 8-10 weeks for hardware delivery

once PO issued by bidder to hardware vendors post contract

signing, Request bank to modify the hardware timelines as

follows.

Hardware & Software Delivery T+ 2 months

Hardware, OS & DB Installation T+ 4 months

Please refer Addendum for the revised Project Timelines

51 Section 7: Detailed Scope of

Work; Pt.18

vs

Appendix 1B: Technical

Specifications; Storage, Pt.19

24 From RFP

Bidder is free to decide the zero data loss methodology

either through Host Based replication or storage based

replication or hybrid which will ensure bank to experience

zero RPO and RTO of 15 mins. Bidder has to ensure that

replication is performed for both database and application.

From Appendix 1B- Technical Specifications for Storage Sno

19

The proposed storage must support Synchronous and

Asynchronous replication across sites / storages for FC data

on the storage. The proposed solution must provide 3 Way

zero data loss solution with functionality to provide delta

resync capability from surviving site in case of disaster.

Storage is required to be configured with required

redundant IP ports / FC ports / FCIP routers for the

replication. The proposed storage must reduce OPEX costs

and have an native / external option to preserve bandwidth

by compressing the data being replicated to the DR site.

As bank has allowed bidder to select the zero data loss

methodology either through Host Based replication or storage

based replication or hybrid, and if bidder is going with host

based replication, it should be optional for the bidder to comply

with the Synchronous and Asynchronous replication for storage

else it will result in functionality that will be redundant and not

be used in the solution and will hence result in cost escalation.

Bidder is free to choose the replication method. However,

for implemnetation flexibility, the proposed storage must

have synchronous replication available from Day 1. All

required replication licenses for the required capacity

should be supplied by the Bidder from Day 1. Database and

Non-Database replication methodology can be either host

based or storage based.



No.



Work; Pt.18

vs


Specifications; Storage Data

Accelerator, Pt.6

24 From RFP






From Appendix 1B- Technical Specifications for Storage Data

Accelerator Sno 6

The Tiered File System should be able to automatically

manage data flow and placement between the server and

the storage. It should be able to protect data by

Synchronous replication HA / Cluster with Zero RPO and

Must have a DR with 30 Minutes RPO.





with the Synchronous replication HA / Cluster with Zero RPO for

Storage Data Accelerator else it will result in functionality that

will be redundant and not be used in the solution and will hence

result in cost escalation.

Data Accelerator and Zero RPO are two different

requirements.

Data Accelerator is required to accelerate the application(s).

Zero RPO is required for Zero Data Loss Data Protection

between DC and Near DR.


Work; Pt.18

vs



Accelerator, Pt.10

24 From RFP







Accelerator Sno 10

System should be able to support transparent and fast data

backup/HA by virtue of the shared data fabric - RPO = 0

minutes - without additional costs.





with RPO = 0 minutes for Storage Data Accelerator else it will

result in functionality that will be redundant and not be used in

the solution and will hence result in cost escalation.


requirements.

Data Accelerator is required to accelerate the application(s).

Zero RPO is required for Zero Data Loss Data Protection

between DC and Near DR.


Work; Pt.18

vs



Accelerator, Pt.11

24 From RFP







Accelerator Sno 11

System should be transparently mirrored in the disaster

recovery site by virtue of the shared data fabric - enabling

RTO <= 30 minutes.





with transparently mirrored in the disaster recovery site for

Storage Data Accelerator else it will result in functionality that

will be redundant and not be used in the solution and will hence

result in cost escalation.


requirements. Data Accelerator is required to accelerate the

application(s) with no data loss in case of component

failure. Zero RPO is required for Data Protection between

DC and Near DR site. Both the requirements must be

addressed in the proposed solution. The Data accelerator

must be proposed in No Data Loss, No Single Point of Failure

using HA or cluster deployment architecture.

55 Appendix 1B: Technical

Specifications; D2D, Pt.4

Sno 4 The array should have at least 2 nos. of active controllers for

better performance & redundancy. Each controller should

have minimum 2 physical ports per controller of 6/12 Gbps

links / lanes for backend disk connectivity. Should support

FC and IP for host connectivity

Request bank to allow bidder to propose single controller for

D2D as this is a backup device and dual controller will make the

backup proposition costlier.

The entire solution must be proposed in no single point of

failure architecture.



No.




Sno 13 "Bidder should propose the Enterprise Storages for DC & DR

– Capacity - 15 TB usable and NDR Capacity - 7 TB usable

and the capacity should be proposed on less than 1TB SSDs.

Once the SSD Storage Device reaches the write endurance

limits or service life, same needs to be replaced without any

cost during warranty/AMC period.

The proposed storage is required to be configured with

inline Deduplication and Compression. In case inline

Deduplication and/or compression is not offered, to protect

Banks interest, the bidder must offer 50% more usable

capacity to compensate the loss of space savings."

In the scenario where the storage requirement is less than 15TB

for the solution, can bidder propose a lower capacity as per

solution requirements and growth metrics to provide an

optimized cost proposal.

The specifications mentioned in Appendix 1B: Technical

Specifications are minimum.



Sno 2 The proposed D2D storage should be configured with

minimum 60 TB backend usable capacity. The capacity of

the proposed D2D storage/appliance must cater to

sequential backup read/write workload and should be

configured with SAS 10K/15K or NL-SAS 7.2K RPM Disks of

less than 4TB and must be able to complete full backup of

15 TB Data in 1 Hour and equivalent time for restoration.

This is minimum requirement, bidder is required to factor

the sizing in line with the proposed application and

database architecture.

In the scenario where the D2D storage requirement is less than

60TB for the solution, can bidder propose a lower capacity as

per solution requirements and growth metrics to provide an

optimized cost proposal.

The specifications mentioned in Appendix 1B: Technical

Specifications are minimum.



Accelerator

Appendix 1B- Technical Specifications for Storage Data

Accelerator

Request bank to confirm what is the IT component that this

specs refers to. Is it for application server or for Storage

controller unit?

Storage Data Accelerator is an application performance

enhancement solution providing ultra low latency to

drastically reduces the application response time from

underlying filesystem & storage (from milliseconds to

microseconds).59 General Date of Submission is 30.5.19 Reques the Bank to give extension in date of submission by

atleast 2 weeks post clarifications




MB; Pt.1.10.1

The solution should allow maker/checker/approver role for

all modules defined by the Bank

Maker-Checker and Authorisation is a Corporate Banking

functionality.

Is this requirement applicable for Retail Banking Customers?

Who is expected to be the Checker/Authoriser in the process?

Bank will define the users for various roles during SRS Phase



MB; Pt.6.7.1.4

Apply online for loan Please provide more details on the Loan application process

steps.

Additionally, please let us know the number and type of loan

porducts that have to be estimated as part of this RFP?

Requisite details will be shared with the successful bidder

during SRS phase



MB; Pt.6.13.9

Wealth Management Please provide detailed information on the scope of

functionality to be implemanted as part of Wealth

Managemement?




No.




& MB; Pt.3.2.8

Captcha and audio message for login Does the Bank expect vendor to provide and budget for captcha

/ audio message framework?

Or will the channel applications integrate with any exixsting

Captcha / Audio Message framework at the Bank.





& MB; Pt.6.13.13.1 -

6.13.13.7

Tax Payment Please provide details on the functionalities expected to be

implemented as part of each Tax payment requirement.




& MB; Pt.6.17.1

The solution should support real-time customer analytics &

predictive analytics from various sources

Does the Bank expect implementation of a Customer analytics /

predictive analytics backend engine?

The proposed Dgital channel solution will integrate with these

backend.





& MB; Pt.6.17.2

Customer should have the ability to do monthly budgeting Does the Bank expect vendor to propose a PFM tool to support

this requirement?

Incase there is an existing PFM tool that the proposed solution

will untegrate with, please provide more information on the

same.





& MB; Pt.6.17.4

The solution should have the capability for Spending

Analytics

Same as above Bidder is required to ensure that the proposed Omni




& MB; Pt.6.17.5

The solution should have the capability for analytics based

cross-sell offers

Does the Bank expect implementation of a Offers engine based

on customer analytics ?

The proposed Dgital channel solution will integrate with thes

Offers engine to enable the required functionality.





& MB; Pt.6.18.8

eComm payment acceptance Please provide more details on this requirement. Please be guided by the RFP



& MB; Pt.6.15.2

The solution should have the provision to maintain outside

PSB account details

Please provide more details on this requirement and the

expected mode of integration for getting outside PSB account

information?




& MB; Pt.6.15.3

The solution should have the provision to maintain policy

details

Please provide more details on the functionalities expected to






& MB; Pt.6.15.4

The solution should have the provision to maintain MF Please provide more details on the functionalities expected to





Specifications; MADP; Pt.17

The solutions should provide a visual administration and

monitoring

Please provide more details on this requirement. Please be guided by the RFP

74 Section 7.7: Migration Data Migration The number of source systems in scope for data migration Number of source systems in scope for data migration- 5

75 Section 7.7: Migration Data Migration Please provide the details of the source DB? Confirmation that

the data is stored in RDBMS.

Currently, Bank is using SQL Server and MySQL

76 Section 7.7: Migration Data Migration Number of tables per source systems Details will be shared with the successful bidder



No.


77 Section 7.7: Migration Data Migration What is the total Data Volume in GB/TB, which needs to be

migrated?

Please be guided by the RFP and subsequent Addendum

78 Section 7.7: Migration Data Migration Please share Data Flow architecture diagram of current system. Requisite details will be shared with the successful bidder

during SRS phase79 Section 7.7: Migration Data Migration What are the total number of transactions per year? Please refer Addendum for Volumetric

80 Section 7.7: Migration Data Migration How many years of data has to be migrated per year? Complete data for all in-scope applications has to be

migrated in one go81 Section 7.7: Migration Data Migration Does the bank have Oracle enterprise licenses? Please be guided by the RFP

82 Section 7.7: Migration Data Migration Is the current data have any unstructured data? No

83 Section 7.7: Migration Data Migration Does the bank have any ETL tools currently which they would

like to use?

No, Bank does not have any ETL tool.

84 Section 7.9: External Agency

for UAT & Audit

Performance Testing In addition to the volume information provided for sizing (40

Lakh Subscribers), request the bank to also share

Query not clear


for UAT & Audit

Performance Testing What is the expected daily transactions via Internet and mobile

channel ?

Please refer Addendum for Volumetric


for UAT & Audit

Performance Testing What is the expected concurrent user logins (retail +

corporate)?



for UAT & Audit

Functional Testing Please share the list of testing tools if any available with P&S

bank

Bank does not have any testing tool.


for UAT & Audit

Functional Testing It is mentioned that bidder team has to perform SIT and unit

testing prior to UAT, however in the external agency

responsibility it is mentioned that (point 22) - Conduct unit

testing, integration testing of the entire functionality of the

solution, please clarify that, if the testing by external agency has

to be performed after SIT by Vendor or SIT has be done by

External agency only (not by the vendor)

SIT is to be conducted by the Bidder and Data Migration

Audit and UAT is to be performed by the external agency


Criteria; Pt.3

Eligibility Criteria The proposed UPI Solution should have been implemented in at

least one scheduled commercial bank in India with more than

1500 branches, Request the bank to kindly modify this term as

"The bidder/OEM`s UPI Solution should have been implemented

in at least one public/ private Bank in India, running successfully

for one year or more



Criteria; Pt.4

Eligibility Criteria The proposed IMPS Solution should have been implemented in

at least one scheduled commercial bank in India with more than

1500 branches, Request the bank to kindly modify this term as

"The bidder/OEM`s IMPS Solution should have been

implemented in at least one public/ private Bank in India,

running successfully for one year or more




No.


91 Section 7.1: Supply of

Software License

Supply of Software Licenses The bidder shall supply a complete Omni Channel Digital

Banking solution to meet the functional and technical

specifications as mentioned in Appendix 1.

The following considerations must be taken for supply of

software:

1) All software envisaged is required to be on-premises software

licensed to PSB

2) The software supplied must be the latest version of the

software supplied by the OEM.

Request the bank to kindly clarify if the bank is looking for

perputual license for OS/DB kindly clarify.

Bidder is required to right size type of license and is

required to factor requisite support & Technical Assistance

from the OEM for the entire contract duration adhering to

the scope and SLA mentioned in the RFP

92 Section 7.2: Hardware

Requirement

Fiber channel SAN Switch with hardware level redundancy

at DC, DR and Near DR

Please confirm that is Near DR is in place because there is no

information for the same is mention and also apart from SAN

switch, no requirement is mention with respect to Compute and

storage

Bidder is required to provision Storage, SAN Switch and any

other IT Infrastructure required in order to get fully

functional solution at Near DR. Bank is in the process of

finalizing the Vendor for providing co-location services


Requirement

Server Operations – System Operations Please confirm that for monitoring Bidder need to bring new

monitoring tools or will utlized the existing tools of PSB

Please refer the RFP and subsequent addendum/replies

published by the Bank


Requirement

Server Operations – System Operations, Hardware, System

Software and Network problems

As bank is already having establisted Network, so Bidder not

need to provision any Network Infrastructure and support for

this engagement and will utilized the existing network

Infrastructure which will be supported by PSB

Bidder is required to liaison with the Bank's Networks

service provider in order to resolve any issue related to

network or network equipment


Requirement

Service Desk & Managed Services Please confirm that is bank is ok for remote support for

Infrastructure or need onsite support only

Bidder is required to provide the support for the proposed

application and infrastructure from bank's locations


Requirement

Bidder to ensure that banks provided (Existing and Future)

EMS Tools and Helpdesk tools are fully integrated with all

the solution proposed in the RFP to ensure smooth

functioning.

Please confirm that Banks existing EMS tools and Helpdesk tools

will be used for Ticketing, SLA and monitoring, or need

integration with Bidder provided tools




Requirement

24 Bidder is required to size, supply, design, commission and

maintain hardware, OS, DB as well as all software required

for the proposed applications that should be as per the

contract duration mentioned in RFP document for all

environments, i.e. DC, DR and Non-Production (Test,

Development & Training).

Bidder understands that below environment to be deployed at

primary DC location only

3. Test & Training 4. Development

Bidder is required to propose the following environments:

Production DC

Production DR

Production ZDL- Near DR

Non-Production Test & Sandboxing- only at DC

Non-Production Development- only at DC

Non-Production Training- at DR

Intermittent arrangement of Migration Instance- at DC

The compute at Development & Test should be 20% of the

production DC and compute at Training should be 10% of

the production DC



No.



Requirement

25 The bidder shall propose hardware (only from the sizing

perspective) such that at any point in time during the

contract period, the average CPU utilization should not

exceed 70% at the primary data center.

Bidder understands that average utilization is excluding the

planned activities and batch jobs.

The utilization refers to only OLTP in case of Batch jobs are

executed once in a day. However if the bidder is proposing

multiple batch jobs on smaller period basis (hourly, or every

4/6 hour etc.) then bidder is required to right size the

solution where the CPU consumption consideration shall be

for batch jobs also. Only a day batch job shall be excluded

from the threshold and SLA parameters. Bidder is also

recommended to avoid executing batch jobs during peak

business hours, between 10am to 6pm. Planned activities

are to be performed after approval from the Bank.


Requirement





bidder understands that this 70% utilization stands true for the

production environment at DC only and Disaster recovery

environment at DR. This is not applicable for below

environment.

3. Test & Training 4. Development

Bidder shall propose hardware (only from the sizing



exceed 70% at the primary data center and Disaster

Recovery Center.

The average CPU utilization for Non-production

Environments: Test, Training and Development should not

exceed 80%.


Requirement





Bidder understands that the propose HW needs to be provided

at 70% utilization in sync with the business volume provided in

the RFP and year on year growth

Bidder is required to right size the solution as per the

mentioned business volumes and SLA requirement

stipulated in the RFP.



No.



Specifications; Storage

Bidder should propose the Enterprise Storages for DC & DR










capacity to compensate the loss of space savings.

Bidder understands that clone and non-production environment

can be proposed on the SAS or NL_SAS HDD.

As new age banking is moving towards digital channel

adoptions so the growth of usage of OMNI channel shall be

considerably high, in turn transactions per second and IOPS

requirement of the storage. To avoid performance

bottlenecks in the solution, the proposed storage must be

an All Flash Storage.


Requirement

25 As per the architecture there are 4 copies of databases

required at DC. Prod, Dev, QA / UAT / Sandbox, Training

with a performance neutral volume clones for each of the

workloads and a full volume copy.




Requirement

25 Bidder needs to provide the detailed configuration of the

proposed Hardware (Test, Dev and Training, Production and

DR) environments




Requirement

26 Bidder can consider Logical separation/ Virtualization for

production and non-production environment at compute

and storage level. The bidder should note that the

production and non-production environment should be

physically separate.

Bidder understand that same SAN Switch, Backup Solution

(Backup Software, Backup Server, Tape Library, D2D)and

Network Switches can be used for production and Non-

Production environment. Please confirm if Bidder

understanding is correct.


"Bidder can consider Logical separation/ Virtualization for

production and non-production environment at compute

and storage level for respective Environments.

The bidder should note that the production and non-

production environment should be physically separate with

respect to Compute.

Additional Clause: Bidder is required to consider and

propose SAN Switch, Backup Solution (Backup Software,

Backup Server, Tape Library, D2D) which can be used both

for production and Non-Production environment Logical

separation / Virtualization / zoning."

Bidder understands that test&training environment is same as

per the pre-bid reply by Bank, As a result the Full DB copy needs

to be factored for all the environment except Near DR.



No.


105 Section 7.16.2: OS/ Server/

Hardware Management

46 Perform quarterly DC – DR drills Bidder understands that as part of the RFP no DRM solution to

be provided by the bidder.

Bank will provide the Disaster Recovery Management

solution; bidder is required to integrate OMNI channel with

Disaster Recovery Management solution. Bidder is required

to perform DR drill or actual DR migration through manual

process till the time DRM solution is not implemented by

the bank, adhering to SLA parameters.



Accelerator

NA Storage Data Accelerator Technical specifications of Storage Data Accelerator is being

mentioned for appliance whereas there is no integration,

interfaces, customisation has been asked in Applications (like

Mobile App, Internet Banking, Payment Gateway etc). Non of

the Application OEM has certification with said appliances, so

kindly remove storage accelerator device from the bid.

The Storage Data Accelerator is an application performance

enhancement solution enhancing ultra low latency solution

which drastically reduces the application response time

from underlying filesystem & storage ( from milliseconds to

microseconds). Since it’s a lower level solution, no

application changes are expected.


Requirement

25 The proposed servers should comply with the minimum

specifications provided as part of Appendix 1B- Technical

Specifications.

In the Appendix 1B-Technical Specification sheet, Server

Specifications is not present. Please share the minimum

technical specifications of Server

Please refer "Appendix 1B- Technical Specifications" sheet

"Instructions" point no. 9.


Specifications; Storage

NA 13:Bidder should propose the Enterprise Storages for DC &

DR – Capacity - 15 TB usable and NDR Capacity - 7 TB usable










5:The system must support intermixing of SSD's

of 960GB, 3.8TB Capacity or equivalent. The proposed SSD

types are indicative. Bidders can propose their near

equivalent SSDs.

We understand from clause no. 5 (from Storage specifications)

that bidder is allowed to propose near equivalent SSD capacity

of 960GB, 3.8TB disk. Request to clarify.

Small capacity of disks will increase data center cost in terms of

space & power. Whereas storage can be configured with higher

capacity of disks to deliver the asked performance in clause no.

12. Requesting you to please remove the limit of 1TB and

modify the clause as "Bidder should propose the Enterprise

Storages for DC & DR – Capacity - 15 TB usable and NDR

Capacity - 7 TB usable and the capacity should be proposed on

less than 4TB SSDs. Once the SSD Storage Device reaches the

write endurance limits or service life, same needs to be replaced

without any cost during warranty/AMC period.

The proposed storage is required to be configured with inline

Deduplication and Compression. In case inline Deduplication

and/or compression is not offered, to protect Banks interest,

the bidder must offer 50% more usable capacity to compensate

the loss of space savings."

Different OEMs have different capacity disks. Since the

capacity is less, to meet the minimum IOPS disks SSD disks

with less than 1TB SSDs are required or Bidder to propose

disk size between 960GB to 3.8TB or equivalent meeting the

IOPS requirement stated

Inline Deduplication and Inline compression together offer

significant data reduction and lowers the TCO for an SSD

based array Storage solution.

Also, Bidder is required to comply with the specifications

mentioned in Appendix 1B: Technical Specifications


Requirement

25 Vertical and horizontal scalability should be two important

requirements for these servers as well.

Since it will leave most of the resources unused, we would

suggest PSB to have the DB layer with Vertical and Horizontal

Scalability whereas Web and App layer should be with

Horizontal Scalability.




No.



Requirement

28 the indicative list of hardware and application instances are

given as below " the list of all the components in Table"

"The table ask that all the components specified in the Table has

to be proposed in HA."

Bidder understands that components like Storage and tape

Library is not required in HA (High Availability).

The storage and tape library must have No Single Point of

Failure high availability at the active component level.


Timeline

51 Hardware & Software Delivery T+ 1.5 months Bidder requests to modify the clause as "Hardware & Software

Delivery T+ 2 months" where T is the date of purchase

order/contract awarded to the bidder. Generally minimum 8

weeks is being taken by the respective OEM for delivering the

material.

Please refer Addendum for revised project timelines

112 Section 7.14: OEM Scope 37 Point 5- HLD/ LLD

Bidder to take inputs from the OEM and provide LLD & HLD

documents to the bank. However, it is the responsibility of

the OEM to review and recommend a methodology to

achieve best performance. The same needs to be

implemented upon sign-off on the documents by the Bank.

Bidder understand that this clause is applicable only for

Application per se and no Hardware (Infrastructure) OEM

inputs/review is required for the LLD and HLD provided by the

Bidder as part of the solution.

This is applicable for application as well as IT Infrastructure

OEM


Requirement; Responsibility

Matrix

27 UAT and Data migration Audit Bidder understands that the underlying Infrastructure required

for 3rd party audit will be provided by the Bank

No, it is the responsibility of the Bidder


Requirement; Responsibility

Matrix

27 UAT and Data migration Audit Bidder understands that any seating space/desktop required by

3rd party audit will be provided by the Bank.

Bank will provide necessary seating space, furnishing,

desktops, and electrical connections for the same along

with PSTN telephones with STD facility.

115 Section 7.14: OEM Scope 38 SIT & UAT

OEM to assist in SIT and UAT

Bidder understands this clause is applicable for Application

Vendor only. Please confirm.

Yes, your understanding is correct



NA Bidder should propose the Enterprise Storages for DC & DR






















write endurance limits or service life, same needs to be

replaced without any cost during warranty/AMC period.


















No.




NA The storage is required to have minimum 256 GB usable

Data cache / memory available across the pair of controller

post write mirroring / protection overheads. The cache

memory architecture and the proposed cache is required to

be explained in the proposal.

The usability of cache is very dynamic basis the nature of IO

coming to controller cache. There may be scenario where write

IO is high so more cache is used for write operation from total

cache and sometime read IO is high. So how PSB will measure

the amount of mirrored write cache, out of total cache, which

will dynamically change as per IO operations. Hence requesting

PSB to ask for raw cache as most of the storage rfp ask for raw

cache only across the controllers. Requesting you to modify the

clause as: "The storage is required to have minimum 256 GB


with write cache data always mirrored/protected. The cache

memory architecture and the proposed cache is required to be

explained in the proposal."

The bidder must get an undertaking from storage OEM that

minimum 256GB usable data cache/ memory will available

at any point after writes are protected and mirrored across

the controllers.



NA Storage is required to have work load balancing capabilities

and multipathing software for unlimited hosts.

Every storage model has limit to connect max SAN hosts. Kindly

modify the clause to "Storage is required to have work load

balancing capabilities and multipathing software for minimum

512 hosts."

The solution must not have host limitations for investment

protection and future scalability required in case of

augmentation, reuse etc.



NA The proposed D2D backup Storage must be a SAN Storage

System OR The proposed D2D Storage can be a purpose

build backup appliance from the backup software OEM in

No Single Point of Failure HA controller configuration

offering minimum 4 Nos of 16/32Gbps FC ports & 4 Nos of

10/25GbE iSCSI ports distributed evenly across the active

controllers. The proposed Backup solution must be offered

with Subscription based backup license.

The proposed D2D backup Storage must be a purpose build

backup appliance from the backup software OEM in No Single

Point of Failure HA controller configuration offering minimum 4

Nos of 16/32Gbps FC ports & 4 Nos of 10/25GbE iSCSI ports

distributed evenly across the active controllers. The proposed

Backup solution must be offered with Perpetual based backup

license.

Justification: SAN Storage write/read data randomly, while in

Backup environment we need storage/appliance that must

support Sequential data write/read. Hence request you to

please consider these changes. Also Subscription license can't

be used post warranty ends. Hence request you to please

consider perpetual licensing which can be used by PSB post

warranty/support ends.

The propose Backup Solution must be offered with

perpetual or subscription based backup licenses with the

warranty and ATS& AMC for the entire contract duration.



NA Write Cache should be mirrored between controllers on a

controller pair.

Proposed disk appliance should be offered with battery backed

up RAM / NVRAM for protection against data loss in power

failure scenario and continuous automated file system check to

ensure data integrity.

Justification: Write cache should be mirrored is logically

applicable in SAN Storage, but not Purpose Build Backup

Appliance. Hence request you to please consider this change

and also include continuous automated file system check to





NA In the event of power failure, the cache needs to have

battery backup for at least 72 hours or destage to

permanent flash.

In the event of power failure, the cache/NVRAM needs to have

battery backup for at least 72 hours or destage to permanent

flash.

Justification: Please consider this change so that maximum

number of solution providers can participate.




No.




NA Offered Storage Array should be configurable in a No Single

Point of Configuration including Array Controller card,

Backplane, Cache Memory, FAN, Power Supply etc.

Offered Storage Array/Appliance should be configurable in a No

Single Point of Configuration including Array Controller card,

Backplane, FAN, Power Supply etc.

Justification: Writing only storage array will restrict many other

OEM to participate hence please consider the requested

change.




NA The proposed storage should offer minimum 32 GB Usable

Data Cache / DRAM available after memory mirroring /

protection overheads. Bidders to offer more memory if

required by the Storage / Appliance.

The proposed disk appliance should offer minimum 32 GB

Usable Data Cache / DRAM available after memory mirroring /

protection overheads. Bidders to offer more memory if required

by the disk appliance.




NA Disk array / Appliance should have no single point of

failures (NSPoF), component and functional level

redundancy to provide high availability features for all the

components at RAID controller level, redundant power

supply, and redundant cooling fans.

DiskAppliance should have no single point of failures (NSPoF),

component and functional level redundancy to provide high

availability features for all the components at RAID controller

level, redundant power supply, and redundant cooling fans.



Specifications; Backup

Software, Pt.9

NA For Faster recovery, backup data should be preferably kept

in usable format eliminating the need for restoring large

amounts of data and simply mapping the production servers

to the backup target array.

Bidder request to please re-visit the clause as the data backed

up by the Backup software will have the different format than

the production environment, Secondly the target

hardware(Backup data dumping Array/tape Library/disk based

appliance) architecture in terms of filesystem, application will

not be similar to production environment, Thirdly the Backup

Target Hardware generally is not built to provide the IOPS

similar to the production Hardware.




Software, Pt.10

NA The proposed solution should support the following

algorithms and provide better security in deployment across

sites - BLOWFISH, GOST, Serpent, AES, Twofish, 3-DES’

The proposed solution should support the following algorithms

and provide better security in deployment across sites -

BLOWFISH/GOST/Serpent/AES/Twofish/3-DES’

Justification: There are many encryption algorithms and OEM

support one or two based on interopeatibilty with the base

code so please allow this change so that maximum OEM can

participate.



Requirement

28 Application Delivery Controller / Server Load Balancer for

Web and Application Instances

Please share the total count of ADC required as part of scope of

this RFP.

Bidder is required to propose ADC in HA for Production

environment at DC and DR for Non-Production Environment

like Test, Development, Training, Bidder can propose non

HA device 128 Appendix 1B: Technical

Specifications; API Gateway

NA Number of API calls should not be restricted. This is a generic statement. It is impossible to estimate efforts

or resource requirement based on mentioned statement. Please

let us know the number of API calls to be integrated

The is in reference to the API calls being made through

deployed API; this is not related to number of APIs to be

integrated or built.


for UAT & Audit

33 VAPT and the testing agency has to ensure that the IS Audit

is conducted before the Go-Live

Bidder understands that VAPT and IS Audit will be SI

responsibility. Request Bank to confirm that no external testing

agency is required to conduct VAPT and IS Audit. Request Bank

to share high level scope for IS Audit

VAPT and IS Audit is to be conducted by Cert-IN Empaneled

Testing Agency, Please refer Section 7.9 External Testing

Agency for UAT & Audit.

130 Section 6: Scope Summary

Clause 6.1.4: Multi-Lingual

21 The solution should have multi-lingual capability for UI Bidder understands that Bank is looking for multi-lingual

capability for Internet Banking and Mobile Banking channels

The Proposed Omni Channel Digital Banking Solution should

have multi-lingual capability.

131 Scope for PKI NA PKI Solution Please share the number of digital certificates required to

implement in PKI solution


Solution.



No.


132 Scope for HSM/ PKI NA HSM/ PKI Requirement Average number of the document per month which need to be

sign.


Solution. 133 Scope for HSM/ PKI NA HSM/ PKI Requirement How many authorized signatory will be there who will sign the

document .


Solution. 134 Scope for HSM/ PKI NA HSM/ PKI Requirement Which ERP they are using for billing. Please refer Addendum 5 for the revised Scope for PKI

Solution. 135 Scope for HSM/ PKI NA HSM/ PKI Requirement ERP is on cloud or in their own data center. Please refer Addendum 5 for the revised Scope for PKI

Solution. 136 Scope for HSM/ PKI NA HSM/ PKI Requirement Solution is only required for billing module for invoicing or it will

be integrate with all GenPect module like HRMS , PO processing

and other modules to automate the entire system.


Solution.

137 Scope for HSM/ PKI NA HSM/ PKI Requirement How many instances we need to factor like HA in DC and

whether DR is required or not , please confirm.


Solution. 138 Section 7.9: External Agency

for UAT & Audit

NA Vulnerability Assessment I Penetration Testing (VA/PT). Can you provide the distribution of assets based on the various

locations to be considered in scope for VA/PT? (Example: 500

devices in Mumbai, 250 Devices in Delhi)

Bidder is required to conduct the VAPT for the proposed

application and infrastructure


for UAT & Audit

NA Vulnerability Assessment I Penetration Testing (VA/PT). Total number of devices in scope for VA/PT Bidder is required to conduct the VAPT for the proposed

application and infrastructure140 Section 7.9: External Agency

for UAT & Audit

NA Web Application Security Testing How many web applications that will be in scope for security

testing.

Bidder is required to conduct the Security Testing for the

proposed application and infrastructure141 Section 7.9: External Agency

for UAT & Audit

NA Web Application Security Testing What can we assume to be the rough average size of

applications (in terms of number of web pages) across a

classification of Small (say 20 pages for a small app), medium

(40 pages for medium), large (60 pages for large)?

Bidder is required to conduct the Security Testing for the

proposed application and infrastructure


for UAT & Audit

NA Web Application Security Testing How many rescans/retesting are expected for each initial

scan/test?



for UAT & Audit

NA Web Application Security Testing Please provide the typical turnaround time for an application to

be available for rescan/retest? (E.g., 4 weeks Time period for

fixing vulnerabilities)



for UAT & Audit

NA Web Application Security Testing Please provide frequency. Please be guided by the RFP

145 General NA General Support model - Is it onsite/ offsite/ hybrid Onsite146 General NA General What Support window is required for security resources? Please be guided by the RFP147 General NA General Contract and OEM details of existing security tool if any. If its

part of scope.


148 General NA General If any existing ticketing and availability tool for operation

support? Or Bidder has to provide the same?


149 NA AV Do AV solution is required for end points or Servers? Kindly

confirm no. of licenses.

Bidder is required to provide only the sizing for Anti Virus

licenses. Bank and/or its appointed Vendor will install and

maintain the licenses and its agents.

However, Bidder is required to liaison with Bank and/or its

appointed Vendor in order to resolve and remediate any

issues arising due to Anti Virus150 NA AV Do AV solution require in HA in DC and DR? Bidder is required to provide only the sizing for Anti Virus

licenses. Bank and/or its appointed Vendor will install and

maintain the licenses and its agents. 151 NA IS Audit Is this require for entire DC and DR infra? Or limited to in scope

solution only.

In-Scope solutions and infrastructure only



No.


152 Annexure 5: Proposed

Agency Profile

109 Annexure 5: Proposed Agency Profile Please confirm this is to be responded by bidder or it is also

required from OEMs?

Annexure 5 has to be submitted by the Bidder

153 Annexure 20: Undertaking

for Back-Lining

143 Annexure 20: Undertaking for Back-Lining We assume this is to be provided by key OEMs - MADP, UPI,

IMPS, Internet Banking, Mobile Banking and Omni Channel

Solution. Please confirm.

Bidder is required to submit Annexure 20: Undertaking for

Back-Lining on Bidder’s Letterhead signed by the authorized

signatory confirming that the successful bidder will submit

the back lining agreement(s) within 1 month of successful

execution of the Contract from the following Solution

OEMs:

1. MADP

2. Omni Channel

3. UPI

4. IMPS

5. PKI


Specifications

Appendix 1A: Functional Specifications Please share updated Appendix 1A: Functional Specifications Please be guided by the RFP


Specifications

Appendix 1B: Technical Specifications Please share updated Appendix 1B: Technical Specifications Please be guided by the RFP

156 Appendix 2: Commercial Bill

of Material

Appendix 2: Commercial Bill of Material Please share updated Appendix 2: Commercial Bill of Material Please be guided by the RFP

157 General 4 Section 2: Data Sheet;

Bid submission last date and time- 30.05.2019 14:00 HOURS

Request bank to extend the submission date and time of the

RFP by four weeks from the date of clarification of additional

queries.


158 Section 6.2: Growth

Projections for this RFP

22 Hardware, OS, DB should be sized to support up to 40 Lakh

Internet, Mobile and Omni Channel users (Retail &

Corporate).

Request Bank to confirm whether hardware sizing needs to be

done on the basis of 40 Lakh users or on TPS. Bank has shared

below TPS

Also request Bank to share TPS for IMPS and wearable users

Omni-Channel Solution 300 TPS to 500 TPS (Minimum 250)

API Gateway 400-500

UPI 500 TPS


159 General NA DB Size Internet Banking: 100GB , Mobile Banking: 450 GB and UPI :

300GB.

Please let us know database size for IMPS

Currently, Mobile Banking data includes IMPS data as well


Requirement

28 HA Deployment Please let us know whether IMPS and UPI needs to deploy in HA

mode

Yes

161 General Munimum 3 resourses for FMS Since the applications has been increased, hence 15 minimum

resources will be required

Please refer Addendum for the revised Bill of Material


Timeline

51 Sign-off and Go-Live of the Solution

**i.e. Go-Live with at least English and Hindi language

9 month will be very dificult to achive, hence request bank to

gove 3 months extra.

Please refer Addendum for the revised Project Timelines

163 General Daily Transactions Volumes Please refer Addendum for Volumetric164 General Expected concurrent user logins Please refer Addendum for Volumetric165 6.3.1.21 NPS/PPF/APY/PPSBY/PMJJBY Does the GBM module provide front end capabilities for these

schemes which the digital solution can call for the subscription

and other capabilities

Bidder is required to integrate Omni Channel Solution with

Bank's (existing and future) GBM



No.



Work; Pt.15

23

(Addendu

m pg 5)

Bidder is required to migrate the Transaction log,


the existing systems to the new proposed systems

We believe this relates to the new 'archival' systems and

hardware and that logs of legacy application should not get

migrated to the new application, as that will not be

architecturally feasible or recommended.

Bidder is required to maintain the transaction logs,

application logs, DB logs etc. for the previous 10 years and

make it available in a readable format as and when required

by the Bank. The archived logs can be from the existing

system and the proposed system.

167 6.10.1.28 Subscribe for IPO Need to have more clarity on this point. Bidder is required to perform integration with ASBA in CBS.

Also, subscription of IPO can de done through UPI 2.0

mandate platform (both issuer and acquirer). Bidder is

required to integrate the proposed Omni Channel Solution

with the same168 Point.no.29 Application level security (Complliance) - The keys should

be be regenerated on the fly for future e-discovery for

specific requests on legacy encrypted data e.g. on a backup

tape

Need to have more clarity on this point. There will be not requirement to have any concept related

to key storing as it happens on the fly.

169 Section 7: Detailed Scope

of Work

22 What is the current cost for PKI Solution provided by Snorkel for

AMC and ATS support.


Solution. 170 Section 7: Detailed Scope

of Work

22 Can you please provide the tentative sunset dates for existing

PKI Solution or Can we replace it with the new PKI Solution


Solution.

171 Section 8: Terms &

Conditions

Clause 8.23: Subcontracting

59 Bidder shall not sub-contract for any part of the RFP scope

other than for the supply and maintenance of Hardware.

Given that we are planning to outsource some implementation

activities to OEMs/Service providers, we are in conflict with this

clause. Can you please remove this clause


172 General Need clarification if IMPS is need to be integrated with Core or

with the Omni Channel. In case, the integration is through the

channel, does it need to process the transaction originated

through Core Banking System?

IMPS is to be integrated with both Omni Channel and CBS

173 Section 7.16: Facilities

Management and AMC/ ATS

Kick-off meeting shall happen within 15 days after the

execution of the contract.

Request to consider 30 days for kick-off meeting after the

execution of the contract



of Material

Please allow us to give consolidated pricing, detailed break up

will be provided at a later satge.



of Material

Considering the number of applications, 5 resources for L1 & L2

each would be less hence request you to reconsider

Please refer Addendum for the revised Bill of Material


of Material

Please provide the break up of resource for DC and DR. Please be guided by the RFP

177 General Please give us extension of at least 4 weeks, 30th May onwards. Please refer Addendum for the revised submission date


Conditions

Clause 8.11: Performance

Bank Guarantee

55 Performance Bank Guarantee (8) The following sentence should exclude error, inadvertance.

"The Bank shall also be entitled to make recoveries from the

Successful Bidder's bills, Performance Bank Guarantee, or any

other amount due to him due to inadvertence, error, collusion,

misconstruction or misstatement."




No.



Conditions

Clause 8.14: Liquidated

Damages

55 Liquidated Damages L.D’s are capped at 0.50% of the complete contract amount until

actual delivery or performance, per week or part thereof (3 days

will be treated as a week); and the maximum deduction is 10%

of the Total Project Value. We propose L.D to be capped at

0.50% of the fees payable for the delayed deliverable per week.

Not agreeable to 3 days being considered to be a week. L.D and

performance Bank Guarantee should not be claimed at the

same time. Both should only trigerred for reasons solely

attributable to Bidder.

LD and Penalty due to SLA will be applicable for the reasons

solely attributable to the Bidder.


Conditions

Clause 8.15: Insurance

56 Insurance Insurance will be provided for services (commercial general

liability and professional indemnity insurance) and not

equipment. PSB cannot be named beneficiary in the insurance

obtained by the Bidder. The insurance will be in the name of

Bidder and certificate of Insurance as stated above will be

provided to the Client. Remaining clause is not acceptable.



Conditions

Clause 8.18: Indemnity

57 Indemnity Revised clause below- "The bidder shall, at its own cost and

expenses, defend and indemnify the Bank against all third-party

claims (subject to notice in writing within 30 days of receipt of

claim) arising out of the infringement of Intellectual Property

Rights, including patent, trademark, copyright that is directly

attributable to the bidder in concurrence with the Vendor's

Limit to Liability agreed under the contract. The bidder, subject

to being notified within 30 days of such claims and shall have

full rights to defend itself therefrom. Subject to the above, if the

Bank is required to pay compensation to a third-party resulting

from such infringement, the Bidder will bear all court awarded

damages/ expenses including legal fees, as awarded by the

Court."



Conditions

Clause 8.23: Subcontracting

59 Subcontracting Subcontracting will be allowed for software and hardware

components.



Conditions

Clause 8.24: Cancellation of

Contract

59 Cancellation of Contract This clause should replace 8.43 which has a separate clause on

Termination. There should be one clause on Termination.

Do not agree to payment of additional expenditure on

termination and execution of balance contract by another party.

We do not agree to 5% cap on such costs. Remaining clause is ok

other than what is highlighted below. Need to include clause on

Termination rights of Bidder incase of Material breach at client

end after providing notice of 30 days.



Conditions

Clause 8.25: Dispute

Resolution

60 Dispute Resolution The clause is agreed. However please mention jurisdiction of

courts in addition to arbitration.

Please refer Clause 8.13: Applicable law and Jurisdiction of

Court



No.



Conditions

Clause 8.27: Exit

Management

61 Exit Management What are the documentation related to IPR that Bidder is

required to provide to nominated vendor.

Documentation related to IPR refers to any customization

done specifically for the Bank which is not a copyright of the

OEM of the proposed solution or the Bidder.


Conditions

Clause 8.27: Termination

61 Transfer of certain Agreements Not agreeable. Please be guided by the RFP


Conditions

Clause 8.36: Awarding of

Purchase Order

65 Awarding of Purchase Order The contract signed between the Bidder and the Client shall be

the superseding document over the RFP/PO or any other

documents signed between parties. Hence do not agree to "The

terms and conditions of purchase order and RFP shall constitute

a binding contract." The contract will be a separate contract

which shall have T&C's from the RFP itself.

Contract Documents and Order of Precedence

The following documents shall be deemed to form and be

read and construed as part of the Contract, viz.,

a) The RFP/Q for selection of the company and Addendum

b) The Bid Form and Price (i.e. fee chargeable by the

company for its services) submitted by the Company and

subsequent amendments made into it as accepted by the

Bank if any.

c) The schedule of requirements ( i.e. Scope of Work and

Functional & Technical Requirements)

d) The Bank’s Notification of Selection of company/ Letter

of Offer/ work order

In case of any conflicts, ambiguities, inconsistencies, errors,

or omissions in, between or among any of the documents

mentioned above, the following order of precedence of the

documents in the interpretation or resolution of such

conflict hereunder shall prevail:-

a) This contract dated …………………

b) The RFP/Q for selection of the company and

Corrigendum

c) The Bid Form and Price (i.e. fee chargeable by company

for its services) submitted by the Company and subsequent

amendments made into it as accepted by the Bank if any.

d) The schedule of requirements (i.e. Scope of Work and

Functional & Technical Requirements)

e) The Bank’s Notification of Selection of company/ Letter of

Offer/work order


Conditions

Clause 8.38: Compliance

with Statutory and

Regulatory Provisions

65 Compliance with Statutory and Regulatory Provisions This clause shall be restricted to laws and regulations (not

ordinances/codes)applicable to Bidder as an entity registered in

India. This needs to be mentioned in the clause. We do not

agree to the following-"All suggested changes due to changes in

Changes in Govt. Rule, Changes by Regulators shall be done

without extra cost to the Bank, till SRS Sign-off. All subsequent

changes can be on mutually agreed change request basis"




No.



Conditions

Clause 8.39: Legal

Compliance

65 Legal Compliance This clause shall be restricted to laws and regulations (not

ordinances/codes) applicable to Bidder as an entity registered in

India. This needs to be mentioned in the clause. Termination for

non compliance with laws can only get triggerred after Bidder

gets opportunity to rectify the same.



Conditions

Clause 8.42: Confidentiality

66 Confidentiality We understand that this clause is mutual and Receiving Party

and Disclosing Party can be used interchangeably between

Bidder and Client.

Yes


Conditions

Clause 8.43: Termination

67 Termination We need to retain one clause on termination. 8.28 already exists

on cancellation subject to changes proposed above. Hence 8.43

needs to be removed.


192 Section 9: General

Instructions

Clause 9.14: Acceptance of

Terms

73 Acceptance to Terms Acceptance to RFP terms is subject to deviations proposed by

Bidder. Legal T&C's are not accepted as is.


193 Section 11: Additional

Instructions for Bidders

Clause 11.1.3: Security

Configuration, Monitoring

and Audit

89 Security Configuration, Monitoring and Audit 1.Any audit made under this agreement shall be strictly limited

to the records, documents, information and matters directly

linked to the Services.

2.No access shall be granted to any records, information or

matters related to Bidder's internal costs and pricing (i.e, costs

not passed to client) or relating to other customers of Bidder.

Please refer Addendum for the revised clause on Audits

194 Section 12: Service Level &

Penalties

99 Penalties Need to add the following under penalties and L.D's - Penalties

should only trigerred for reasons solely attributable to Bidder.

We understand penalty and L.D both are capped to 10% of

contract value.

Please refer Addendum for the additional clause

195 Addendum 4 Audit Audit should be with prior notice.Any audit made under this

Agreement shall be strictly limited to the records, documents,

information and matters directly linked to the Services under

the Agreement. No access shall be granted to any records,

information or matters related to Company internal costs and

pricing (i.e, costs not passed to Client) or relating to other

customers of Company.


196 Addendum 4 Risk and Title Revised clause- "The risk, title and ownership of the goods

supplied under this contract shall be transferred on to the Client

on delivery."


197 Annexure 12: NDA Format Governing law Revise clause- "The provisions of this Agreement shall be

governed by the laws of India and the competent court at Delhi

shall have exclusive jurisdiction in relation thereto".

Please refer Addendum 4 for the revised clause



No.




Bidder should propose the Enterprise Storages for DC & DR






















write endurance limits or service life, same needs to be

replaced without any cost during warranty/AMC period.


















The storage is required to have minimum 256 GB usable


post write mirroring / protection overheads. The cache

memory architecture and the proposed cache is required to

be explained in the proposal.

The usablility of cache is very dynamic basis the nature of IO

coming to controller cache. There may be scenario where write

IO is high so more cache is used for write operation from total

cache and sometime read IO is high. So how PSB will measure

the amount of mirrored write cache, out of total cache, which

will dynamically change as per IO operations. Hence requesting

PSB to ask for raw cache as most of the storage rfp ask for raw

cache only across the controllers. Requesting you to modify the

clause as: "The storage is required to have minimum 256 GB


with write cache data always mirrored/protected. The cache

memory architecture and the proposed cache is required to be

explained in the proposal."

The bidder must get an undertaking from storage OEM that

minimum 256GB usable data cache/ memory will available

at any point after writes are protected and mirrored across

the controllers.



Storage is required to have work load balancing capabilities

and multipathing software for unlimited hosts.

Every storage model has limit to connect max SAN hosts. Kindly

modify the clause to "Storage is required to have work load

balancing capabilities and multipathing software for minimum

512 hosts and maximum 1024 hosts."

The solution must not have host limitations for investment

protection and future scalability required in case of

augmentation, reuse etc.



The storage must provide mandatory migration of data

capabilities from existing storage to new proposed storage

seamlessly without any disruption to current storage layout.

Request bank to provide more details like -

- Model of existing storage

- Total data size to be migrated

- Type and size of data (Database, file etc)

- How much block data and file data.

The response is below:

1. DC & DRC Storage: VNX 5500

2. NDR Storage VNX 5300

3. Internet Banking Data Size: 900 GB (DB and Logsize

included)

4. Mobile Banking Data Size: 200 GB (DB and Logsize

included)-- This includes IMPS data

5. UPI Data Size: 350 GB (DB and Logsize included)

6. Type and size of data: No unstructured data

7. How much block data and file data: No unstructured data



No.




The proposed D2D backup Storage must be a SAN Storage

System OR The proposed D2D Storage can be a purpose

build backup appliance from the backup software OEM in

No Single Point of Failure HA controller configuration

offering minimum 4 Nos of 16/32Gbps FC ports & 4 Nos of

10/25GbE iSCSI ports distributed evenly across the active

controllers. The proposed Backup solution must be offered

with Subscription based backup license.

The proposed D2D backup Storage must be a purpose build

backup appliance from the backup software OEM in No Single

Point of Failure HA controller configuration offering minimum 4

Nos of 16/32Gbps FC ports & 4 Nos of 10/25GbE iSCSI ports

distributed evenly across the active controllers. The proposed

Backup solution must be offered with Perpetual based backup

license.

Justification: SAN Storage write/read data randomly, while in

Backup environment we need storage/appliance that must

support Sequential data write/read. Hence request you to

please consider these changes. Also Subscription license can't

be used post warranty ends. Hence request you to please

consider perpetual licensing which can be used by PSB post

warranty/support ends.

The propose Backup Solution must be offered with

perpetual or subscription based backup licenses with the

warranty and ATS& AMC for the entire contract duration.



The proposed D2D storage should be configured with

minimum 60 TB backend usable capacity. The capacity of

the proposed D2D storage/appliance must cater to

sequential backup read/write workload and should be

configured with SAS 10K/15K or NL-SAS 7.2K RPM Disks of

less than 4TB and must be able to complete full backup of

15 TB Data in 1 Hour and equivalent time for restoration.

This is minimum requirement, bidder is required to factor

the sizing in line with the proposed application and


The proposed D2D storage should be configured with minimum

60 TB usable capacity. The capacity of the proposed D2D

appliance must cater to sequential backup read/write workload

and should be configured with SAS 10K/15K or NL-SAS 7.2K RPM

Disks of less than 4TB capacity and must be able to complete full

backup of 15 TB Data in 1 Hour and equivalent time for

restoration. This is minimum requirement, bidder is required to

factor the sizing in line with the proposed application and


Justification: Backend usable capacity won't help in calculating

the disk appliance. It is suggested to mention minimum usable

capacity with backup retention policy. Hence request you to

please consider this change and also include new added point as

per bank's backup retention policy.




Write Cache should be mirrored between controllers on a

controller pair.

Proposed disk appliance should be offered with battery backed

up RAM / NVRAM for protection against data loss in power

failure scenario and continuous automated file system check to


Justification: Write cache should be mirrored is logically

applicable in SAN Storage, but not Purpose Build Backup

Appliance. Hence request you to please consider this change

and also include continuous automated file system check to





In the event of power failure, the cache needs to have

battery backup for at least 72 hours or destage to

permanent flash.

In the event of power failure, the cache/NVRAM needs to have

battery backup for at least 72 hours or destage to permanent

flash.

Justification: Please consider this change so that maximum

number of solution providers can participate.




Offered Storage Array should be configurable in a No Single

Point of Configuration including Array Controller card,

Backplane, Cache Memory, FAN, Power Supply etc.

Offered Storage Array/Appliance should be configurable in a No

Single Point of Configuration including Array Controller card,

Backplane, FAN, Power Supply etc.

Justification: Writing only storage array will restrict many other

OEM to participate hence please consider the requested

change.




No.




The proposed storage should offer minimum 32 GB Usable

Data Cache / DRAM available after memory mirroring /

protection overheads. Bidders to offer more memory if

required by the Storage / Appliance.

The proposed disk appliance should offer minimum 32 GB

Usable Data Cache / DRAM available after memory mirroring /

protection overheads. Bidders to offer more memory if required

by the disk appliance.




Disk array / Appliance should have no single point of

failures (NSPoF), component and functional level

redundancy to provide high availability features for all the

components at RAID controller level, redundant power

supply, and redundant cooling fans.

DiskAppliance should have no single point of failures (NSPoF),

component and functional level redundancy to provide high

availability features for all the components at RAID controller

level, redundant power supply, and redundant cooling fans.




Proposed appliance should be sized appropriately for backup of

XX TB (XX% DB and XX% File System) data as per below backup

policies.

a. Daily Incremental Backup – retained for X nos. of weeks in

disk based appliance

b. Weekly Full Backup for all data types – retained for X no. of

month in disk based appliance.

c. Monthly Full Backups – Retained for X no. of months in the

same appliance.

d. Yearly Full Backups - Retained for X no. of years in the same

appliance.

The solution should be quoted with a minimum usable capacity

of XX TB and should be scalable upto XX TB or higher. Any

additional capacity required as per above mentioned retention

policy sizing needs to be provided by the bidder/OEM for an

entire warranty period of the disk appliance.

Justification: This point is very important as De-dup and

compression ratio vary from OEM to OEM and difficult to

predict the actual capacity where multiple OEMs are

participating so defining the retention policy will ensure that

every OEM has done their due diligence and providing the right

capacity as per need to avoid any further procurement requests

with additional cost to bank.

An indicative data capacity is specified. However if the

proposed data capacity is more or less than the specified

capacity, the bidder must propose Backup solution as per

the actual sizing to meet the following Backup schedule.

The indicative backup policy is as follows:

Daily: Incremental

Weekly: Incremental

Monthly: Full

Quarterly: Full

Half-yearly: Full

Yearly: Full

Bidder is required to factor disk storage / appliance based

backup solution considering the size of the data till the end

of tenure of the contract.



Software, Pt.9

For Faster recovery, backup data should be preferably kept




Appliance should support the throughput of 30TB/hr or higher

to achieve the RPO requirement and should also support instant

access to VM from appliance itself in case of any disaster.

Justification: It will ensure the timely completion of backup and

instant access to achieve the aggressive RPO and RTO.




Software, Pt.10

The proposed solution should support the following



The proposed solution should support the following algorithms

and provide better security in deployment across sites -

BLOWFISH/GOST/Serpent/AES/Twofish/3-DES’

Justification: There are many encryption algorithms and OEM

support one or two based on interopeatibilty with the base

code so please allow this change so that maximum OEM can

participate.




No.




Software, Pt.11

The proposed solution should have the ability of detecting

Ransomware malware on client computer. Any attempt to

backup ransomware affected data should be flagged off by

a notification to the administrator. Solution should have the

ability to configure automated tasks like removing the

computer from the network and send notification mails.

The proposed solution should have the ability of

detecting/avoiding Ransomware malware on backup data using

AirGAP for backup repository. Any attempt to backup

ransomware affected data should be flagged off by a

notification to the administrator. Solution should have the

ability to configure automated tasks like identifying the

computer from the network and send notification mails.

Justification: Ransomware can be avoided by using the AirGap

technology by configuring the Cyber Recovery site as per NIST (

National Institute of Standards and Technology) recommended

standards.




Storage must support native multipathing for all the

operating systems. Vendor must provide multipathing

software for OS which do not have native multipathing

feature. If licensed separately, the vendor needs to provide

all the necessary licenses for entire offered capacity.

Request bank to provide more information. The storage must have no limits on multipathing software

for present and future use and bidder must be able to

provide multipathing software for hosts during any

configuration/reconfiguration during warranty and AMC

period without any cost to bank.



Accelerator

Storage Data Accelerator Is Storage Data Accelerator a hardware or software solution? The proposed solution can be offered as a software,

hardware or software + hardware, adhering to the

requirements mentioned in Appendix 1 B: Technical

Specifications215 Appendix 1B: Technical


Software, Pt.9

For Faster recovery, backup data should be preferably kept




If offered appliance support CIFS/NFS, where data can be kept in

native format but mapping the same for production server will

leads to performance issues hence not supported. Is it

acceptable?




Software, Pt.10

The proposed solution should support the following



If the proposed solution supports AES. Is it acceptable? Please refer Addendum for the revised clause



Write Cache should be mirrored between controllers on a

controller pair.

The offered appliance has NVRAM instead of Cache, to avoid

any data loss in case of power failure. Is it acceptable ?



Specifications; Aplication

Level Security, Pt.29

The keys should be be regenerated on the fly for future e-

discovery for specific requests on legacy encrypted data e.g.

on a backup tape.

Request bank to provide more clarity. Bidder is required to propose a solution which does not

required any key vault for storing keys as the key generation

happens on fly. 219 Appendix 1B: Technical


Proposed storage is required to be scalable to 512 GB

Usable Cache, Cache upgrade can be done by either adding

the cache to the controller or adding more controller to the

storage. 100 TB Usable Capacity & 1,00,000 IOPS on 4K block

size at 50:50 r:w ratio to meet future requirements.

Min. Tech. Specs. - Storage Sheet Pt. No. 15, Cache states: The

storage is required to have minimum 256 GB usable Data cache

/ memory available across the pair of controller post write

mirroring / protection overheads. The cache memory

architecture and the proposed cache is required to be explained

in the proposal.

Clarification Requested:

We understand that the scalability statement is equivalently

applicable as follows "Proposed storage is required to be

scalable to 512 GB usable Data cache / memory available across

the pair of controller post write mirroring / protection

overheads."


Punjab & Sind Bank · 2019-06-14 · Punjab & Sind Bank Addendum - 6 (A Govt. of India Undertaking)...

Documents

Transcript of Punjab & Sind Bank · 2019-06-14 · Punjab & Sind Bank Addendum - 6 (A Govt. of India Undertaking)...