Allahabad Bank Head Office

Request for Proposal For SUPPLY, DEPLOYMENT, CUSTOMIZATION, IMPLEMENTATION, MAINTENANCE AND SUPPORT OF ASSET LIABILITY MANAGEMENT (ALM) SOLUTION Allahabad Bank Head Office 2, N. S. Road Kolkata 700 001 RFP Ref. No.: HO/DIT/ALM/2014-15/16 Dated: 20 th November, 2014 Page 1

Contents Disclaimer...5 1. Invitation for Bids...6 2. Instruction to Bidders (ITB)...8 2.1 About Allahabad Bank... 8 2.2 Objective of RFP... 8 2.3 Responsibilities of Bidder... 9 2.4 Eligibility Criteria... 12 2.5 Preparation & Submission of Bids... 13 2.6 Opening of Technical Bids... 16 2.7 Bid Security... 17 2.8 Modification and Withdrawal of Bids... 18 2.9 Rejection / Acceptance of Bid... 18 2.10 Cancellation of Bid... 18 2.11 Period of Validity of Bids... 18 2.12 Pre-Bid Meeting... 18 3. Selection Strategy...20 3.1 Objective... 20 3.2 Evaluation of Technical Bid... 20 3.3 Scoring Methodology for Functional Requirements (FR) and Technical Requirements (TR)... 21 3.4 Scoring Methodology for Product Demonstration and Bid Presentation (PB)... 22 3.5 Scoring Methodology for Approach, Methodology (AM) & Past Experience... 22 3.6 Scoring Methodology for Site Visits (SV)... 23 3.7 Disqualification Parameters in Technical Bid Evaluation... 23 3.8 Evaluation of Indicative Commercial Bid & Online Reverse Auction... 23 3.9 Reverse Auction... 24 4. Scope of Work...25 4.1 Broad scope... 25 4.2 Detailed scope... 25 4.2.1. Gap identification & Resolution...25 4.2.2. Design of Solution...26 4.2.3. Parameterization, Configuration and Customization of Software...26 4.2.4. Testing...27 4.2.5. Training...27 4.2.6. Implementation...28 4.2.7. Information Security...29 4.2.8. Facilities Management Services (FMS)...29 5. Functional & Technical Requirement...31 5.1 Functional requirement for ALM Solution... 31 5.2 Technical Requirement... 60 5.3 Format Specification... 67 6. Terms & Conditions of Contract...68 Page 2

6.1 Source Code... 68 6.2 Software Delivery & Installation... 68 6.3 Acceptance of Software... 68 6.4 Inspection and Tests... 69 6.5 Information Ownership... 69 6.6 Adherence to Standards... 70 6.7 Security Configuration, Monitoring and Audit... 70 6.8 Considerations for Proposed Hardware & Software to support Solution... 70 6.9 Performance Guidelines... 71 6.10 Confidentiality... 71 6.11 Disaster Recovery System... 71 6.12 Service Level Agreement (SLA)... 72 6.13 Software Licenses for Solution... 73 6.14 Hardware Requirement... 73 6.15 Environments... 74 6.16 Phased Implementation... 74 6.17 Project Documentation and Manuals... 74 6.18 Interface & Integration Requirements... 75 6.19 Warranty & Annual Maintenance... 76 6.20 Training... 78 6.21 Obligations of the Bidder... 79 6.22 Termination for Default... 80 6.23 Exit Option... 80 6.24 Force Majeure... 81 6.25 Performance Security... 81 6.26 Liquidated Damages... 82 6.27 Settlement of Disputes... 82 6.28 Time Schedule... 83 6.29 Payment... 83 6.30 Paying Authority... 84 6.31 System Administration... 84 6.32 Database Access... 84 6.33 Software Maintenance... 84 6.34 Software Maintenance and Support Services during Warranty and AMC... 85 6.35 Software support... 87 6.36 Application Management... 87 6.37 Patch Management... 88 6.38 Change Management... 88 7. Annexures...89 Annexure-1... 89 Annexure-2... 90 Page 3

Annexure-3... 91 Annexure-4... 95 Annexure - 5... 97 Annexure - 6... 99 Annexure - 7... 100 Annexure - 8... 101 Annexure - 9... 102 Annexure - 10... 104 Annexure - 11... 105 Annexure-12 A... 106 Annexure-12 B... 107 Annexure-13... 109 Annexure-14... 111 Annexure-15... 113 Annexure-16... 114 Annexure-17... 116 Annexure 18... 119 Annexure 19... 120 Annexure-20... 121 Annexure 21... 122 Annexure 22... 123 Annexure 23... 124 Page 4

Disclaimer The information contained in this Request for Proposal (RFP) document or information provided subsequently to bidder(s) whether verbally or in documentary form by or on behalf of Allahabad Bank is provided to the bidder(s) on the terms and conditions set out in this RFP document and all other terms and conditions subject to which such information is provided. This RFP document is not an agreement and is not an offer or invitation to bid by Allahabad Bank to any parties other than the applicants who are qualified to submit the bids ( bidders ). The purpose of this RFP is to provide the bidder(s) with information to assist them in formulation of their proposals. This RFP does not claim to contain all the information each bidder may require. Each bidder should conduct its own investigations and analysis and should check the accuracy, reliability and completeness of the information in this RFP and where necessary obtain independent advice. Allahabad Bank make no representation or warranty and shall incur no liability under any law, statute rules or regulations as to the accuracy, reliability or completeness of this RFP. Allahabad Bank may in its absolute discretion, but without being under any obligation to do so, update, amend or supplement the information in this RFP. Page 5

1. Invitation for Bids 1. The Allahabad Bank, a body corporate established under the Banking Companies (Acquisition and Transfer of Undertaking) Act 1970, having its Head Office at 2, Netaji Subhas Road, Kolkata-700001, India, hereinafter called The Purchaser or Bank, which term or expression unless excluded by or repugnant to the context or the meaning thereof, shall be deemed to include its successors and permitted assigns, intends to issue this Bid document, hereinafter called Request for Proposal, or RFP, to invite Techno-Commercial bids from eligible Bidder for Supply, Deployment, Customization, Implementation, Maintenance and Support of Asset Liability Management Solution in accordance with the Industry Best Practices and for complying with Guidelines of RBI/BCBS/IBA/GOI as also for MIS requirements pertaining to ALM. 2. A complete set of RFP documents may be purchased by any interested Bidder on the submission of a written application, in duplicate, from The Asstt. General Manager (I T) Allahabad Bank, Head Office,, 2 nd Floor, 2, Netaji Subhas Road, Kolkata 700 001, India upon payment of non-refundable fee of INR 25,000/- (INR Twenty Five Thousand only) in the form of Demand Draft or Banker s Cheque in favour of Allahabad Bank, payable at Kolkata. Only the Bidders, who purchase the RFP in their names, are eligible for submission of bid. The RFP may be obtained from the above address during office hours on all working days either in person or by post. 3. A complete set of RFP may also be downloaded from Bank s official website www.allahabadbank.in. The Bidder who has downloaded the RFP from above website, is required to submit a non-refundable fee of INR 25000/- (INR Twenty Five Thousand only) in the form of Demand Draft or Banker s Cheque, in favour of Allahabad Bank payable at Kolkata, during office hours within the last date and time of submission of bid, failing which the Bid of the concerned Bidder will not be entertained. This tender is not transferable. Only the Bidders who have officially purchased this tender document shall be entitled to quote subject to their fulfilling the eligibility criteria. The Details are as under: Sl. No. Items Details 1 Bid Reference 2 Price of RFP Document HO/DIT/ALM/2014-15/16 dated 20.11.2014 INR 25,000/- (INR Twenty Five Thousand Only) 3 Date of Commencement of Sale of RFP 20 th November, 2014,11:00 Hours 4 Date and time for Pre-Bid Meeting 8 th December, 2014, 15:00 Hours 5 Last date of receipt of Pre bid queries 05 th December, 2014, 12:00 Hours 5 6 Last Date and time for submission of Bid (Technical and Indicative Commercial) Date and Time of Opening of Technical Bids 22 nd December, 2014,15:00 Hours 22 nd December, 2014,16:00 Hours Page 6

Sl. No. Items Details 7 Date and Time of Opening of Indicative Commercial Bids 8 Date of Online Reverse Auction 9 Place of submission and opening of Bids 10 Address for Communication To be notified subsequently to the eligible Bidders Will be intimated to the technically qualified bidders The Asstt. General Manager (IT) Allahabad Bank, Head Office, Deptt. of Information Technology, 2 nd Floor, 2, Netaji Subhash Road, Kolkata 700 001,India Same As Above Tel : 091-033-22319471/72 Fax : 091-033-2210 6323 Email: ho.ditcbs@allahabadbank.in 4. Technical bids will be opened in the presence of the bidders representatives who choose to attend on the specified date and time. The indicative commercial bids of only technically qualified bidders will be opened and the lowest quote obtained through indicative commercial bids may be fixed as start price for the subsequent reverse auction to be carried out. However Bank may decide to fix the start price lower than the lowest indicative quote at its discretion. The online reverse auction process will be adopted for obtaining commercial quote from the technically qualified bidders on separate date and time which will be notified separately. 5. No further discussion/interface will be granted to the bidders whose bids have been disqualified on technical or any other ground declared/established as per terms/conditions of the RFP. 6. Non-attendance at the Bid Opening will not be a cause for disqualification of a bidder. 7. Allahabad Bank reserves the right to accept or reject, in part or full, any or all the offers without assigning any reasons whatsoever. The Asstt. General Manager (IT), Allahabad Bank, Head Office, 2, Netaji Subhas Road, Kolkata 700 001 Page 7

2. Instruction to Bidders (ITB) 2.1 About Allahabad Bank 1. Allahabad Bank ( the Bank ) was established on 24 April 1865 in Allahabad. In the year 1969, the Government of India nationalized 14 commercial banks and Allahabad Bank was one of them. For operational convenience, the Head Office of the Bank was shifted from Allahabad to Kolkata in 1923. 2. The Bank is a leading public sector commercial bank based in India. The Bank offers a range of financial services including cash management services, depository services, corporate agency arrangements, visa debit cum ATM card, bank assurance and mutual fund, real time gross settlement, gold card scheme for exporters, National Electronic Fund Transfer (NEFT), government business, and online payment. The bank operates through four business segments, namely, Treasury, Corporate / Wholesale Banking, Retail Banking, and Other Banking. 3. Presently, the Bank has a network of more than 2900 Domestic Branches, 7 FGM Offices, 49 Zonal Offices and 6 Staff Colleges, spread all over the country. The Bank also has an Overseas Branch at Hong Kong. 4. The Bank also has CBS Project Office & DC in Navi Mumbai, a CBS Project Monitoring Office in Kolkata and a DR Site in Lucknow. 5. The CBS implementation of the Bank was completed on 18th December 2010. Core Infrastructure for the Centralized Banking Solution is hosted at the Data Center (DC) and Disaster Recovery Center (DRC). DC & DRC are operational on 24 x 7 basis and have necessary infrastructure for that. 6. The replication is done directly at DRC from DC. The data at DRC is not more than 15 minutes behind the production data at DC. In case of disaster the DRC can be up and running within 4 hours. The above mentioned project office/ DC/ DR are for Bank s Indian operations. 7. The Bank has one overseas branch at Hong Kong. 8. Some of the business statistics (figures in crores of Indian Rupees) of the Bank as on 31st March 2014 are as under : Deposits 190,842.81 Total Advances 140,905.46 Investments (Gross) 64,347.94 Net Profit 1,172.02 9. The Bank has one wholly owned subsidiary All Bank Finance Ltd, One RRB Allahabad U.P. Gramin Bank, and two JVs ASREC & Universal Sompo General Insurance Co. Ltd. 10. The Bank will open/plans to open branches, offices from time to time & may also promote/acquire Associates/JVs as and when required. 2.2 Objective of RFP 1. The Bank intends to augment its existing infrastructure for ALM in line with industry best practices and extant RBI/ BCBS/IBA/GOI Guidelines and also Guidelines that may be issued up to the completion of the project. Page 8

2. This Request for Proposal (RFP) is intended to invite Techno-Commercial Bids from eligible bidders to provide an ALM Solution in tune with RBI/BCBS/IBA/GOI guidelines/ industry best practices. 3. The Bidder is required to, Supply, Install, Deploy, Customize, Test, Implement, Rollout, Maintain and Support the ALM Solution and train the concerned personnel of the bank as per the requirements of this RFP for the period of the contract. 4. The Bank intends to procure the hardware for the proposed solution separately. The selected vendor would be required to provide sizing and configuration of the required hardware and related software for the proposed solution. 5. The Bidder has to implement the solution as per requirements laid down in this document. 6. The Bank has appointed an external consultant for providing assistance for the implementation of ALM solution. They will provide requisite assistance/guidance to the Bank, wherever required, till project completion. 7. The Bank intends to implement ALM Solution in accordance with the provisions of following circulars/guidelines and industry best practices RBI guidelines on Liquidity Risk Management by Banks RBI No 2012-13/285 DBOD.BP.No.56/21.04.098/ 2012-13 dated November 7, 2012. RBI guidelines on Bank s Asset Liability Management Framework Interest Rate Risk RBI/2010-11/263 DBOD. No. BP. BC. 59 / 21.04.098/ 2010-11 dated November 4, 2010. RBI Guidelines on Basel III Framework on Liquidity Standards Liquidity Coverage Ratio, Liquidity Risk Monitoring Tools & LCR Disclosure Standards. RBI/2012-13/635/DBOD.BP.BC No.120/21.04.098/2013-14 dated 09th June, 2014 RBI Draft Guidelines on Liquidity Risk Management & Basel III Framework on Liquidity standards. RBI No. 2011-12/DBOD.BP.No./21.04.098/2011-12 dated 21.02.2012 RBI guidelines on Basel III Framework on Liquidity Standards Monitoring tools for Intraday Liquidity Management. - RBI/2014-15/293 DBR.BP.BC.No.46/21.04.098/2014-15 dated November 3, 2014. Any other relevant guidelines issued by RBI/BCBS/IBA/GOI, till completion of the project, shall be applicable. 2.3 Responsibilities of Bidder The successful bidder selected on the basis of the evaluation criteria specified in this RFP should, at the minimum, 1. Implement a solution which is capable of: Achieving compliance with all RBI/BCBS/IBA/GOI guidelines issued on ALM. Supporting ALM in accordance with best industry practices. 2. Advise the Bank the appropriate sizing of the hardware, OS, RDBMS, Networking equipment, Bandwidth etc. required at its data centre at Mumbai and Disaster Recovery Site at Lucknow for successful implementation of the ALM solution. Bank will provide the required hardware infrastructure for the project. 3. Prepare a Business Requirement Document, Test Cases and Test Plans based on the gap analysis and other requirements of the RFP. The bidder shall be required to take Bank s Page 9

approval of the Business requirement documentation and associated project plans before software customization work commences. The document should provide the plan in detail based on the criticality of the requirements. 4. Ensure that the system is in compliance with RBI requirements and other relevant regulatory guidelines. Any instances of non-compliance observed, even at a later date, will need to be rectified at no additional cost to the Bank and well within timelines stipulated by the regulator/bank. 5. Ensure that software solution being supplied is capable of being integrated with existing ADF system of the Bank and a Data Ware housing solution; which the Bank may procure at a later point of time. It needs to have standard interfacing capabilities. Bidder shall directly interact with the vendors and provide necessary integration with the required systems of the Bank at no extra cost to the Bank. There should also be a flow of report level data from the proposed system to the ADF system of the Bank for regulatory submission as well. The bidder will be required to ensure correct data flow at all times. 6. Identify Project Manager, Project Leaders and members of the development teams with relevant skills. The bidder will intimate the Bank, in advance, if there is any change in the project team during the course of implementation. The bidder will ensure proper back up of project leaders and managers and the plan should be intimated to the Bank. The minimum experience of the project team personnel like Project Manager, Project Leader and Programmers put on work should preferably be 2 years. Systems study and all development activities will have to be undertaken at the Bank s locations acceptable to Bank. 7. Provide Facilities Management support for ALM Solution proposed by the bidder for the entire project duration. 8. Ensure that the solution offered should have all components mentioned clearly with its license requirements. 9. Impart both functional and technical/system training on ALM Solution to designated personnel of the Bank. 10. Incorporate changes in system arising due to amendment to regulations/ Bank s policy at no additional cost and well within timelines stipulated by the regulator till completion of the project 11. Assist the Bank in conducting the User Acceptance Tests by providing test plans, scenarios and resolving gaps. 12. Provide complete module wise documentation including logic used, empirical analysis done, methodology etc. as per regulatory and audit requirements. 13. Provide all statutory, regulatory Management Information System (MIS), ad -hoc MIS (including development if needed) and Executive Information System (EIS) reports as required by the Bank in the desired format as per regulatory and Bank s requirements during the entire project duration at no additional cost. 14. Ensure that the system meets all functional and technical requirements specified in this RFP. 15. In case the product/ solution/ Bidder are amalgamated/ dissolved, the impact of such an event should not have any adverse implication on the service level/ time line/cost that is proposed for implementation of the solution. Such event would not dilute the responsibility of the successful bidder in completing the implementation within mutually agreed time lines. Page 10

16. The bidder is required to provide interface with all external IT systems of the Bank for generation of desired reports/returns without any manual intervention. The term external system also includes proposed systems such as LOS or other source systems, data capture systems, workflow tools, etc. which the Bank uses from time to time. The bidder is also expected to ascertain gaps in the data and provide solution to the bank, which should be in line with the requirements and acceptable to the Bank. Bidder should implement & maintain the application software in Main Data centre, and Disaster Recovery (DR) sites. The day to day work will be carried out at ALM Cell, Head Office. Appropriate functionality should be provided for the purpose. 17. Bidder should provide Modular wise user manual as well as Administrator s manual, postimplementation on-site support till next regulatory review from the GO LIVE date and further support till the end of agreed AMC period. 18. Data migration should be done by the bidder from the existing data already collected by the Bank (available in various source systems) to the new system with consistency. After going LIVE, the incremental data shall be moved onto the ALM solutions in a scheduled manner. Bidder to provide necessary interface and/or tools for the same. 19. Reports in regard of migration of data, as required by the Bank have to be developed and generated by the bidder during the migration with all required controls, checks and balances. 20. The successful bidder shall provide technical support for the software application systems supplied under this contract, and will have overall responsibility of the performance, functionality and operation of the systems under this contract. Any supporting software provided /installed/configured by the bidder shall be maintained /fine-tuned/ parameterized by the bidder, from time to time, so that the solution delivers optimal performance. 21. Security features should meet the standards and procedures as per Bank s IT Security Policy and procedures should be followed, in line with prevailing Industry Standards. 22. The bidder to provide the Bank with the proper backup and recovery procedure, with necessary documents so as to meet any exigencies. 23. The bidder should ensure that all verification processes in the software solutions should be governed by maker checker controls. 24. The bidder s overall responsibility includes offering suitable framework, supporting software solution, implementing DR facility, recommending the appropriate hardware, impart necessary training and supply the required documentations/manual. 25. The bidder will convey to the Bank that all the customizations that are required to Go Live, as agreed upon and signed off by the Bank are completed and the solution is ready for testing. 26. The bidder shall also be responsible for the following: Managing the activities of its personnel or sub-contracted personnel and will hold itself responsible for any misdemeanours. The Supplier's representative or the local office nearest to Kolkata shall be the contact point for the Bank and all the authentic status of Delivery and Installation should be made available in writing. Keep the Bank informed on the progress of the project as per the agreed reporting schedules. The bidder and the Bank together will prepare acceptance test plan, for which bidder will station its officers at the venue decided by the Bank at no additional cost. Page 11

Incorporate the review comments received from the users. Prepare contingency plans. Customize software at the Bank s premises. Incorporate change management as per mutual agreement. Help in change management and implementation support at agreed costs, if so desired by the Bank. Inform the Bank about IT infrastructure required for implementation. Framing the Service Level Agreement (SLA) Document in consultation with the Bank. 2.4 Eligibility Criteria 1) The Bank is looking to identify an ALM Solution provider who has demonstrable technical competency for implementing ALM in tune with RBI/BCBS guidelines and Industry Best Practices. The Bidder should have capability to review the existing ALM framework of the Bank (including the prevailing policies, structures, processes, etc.).the Bidder is expected to have adequate experience in implementation of software products/ projects compliant with the integrated risk management framework for ALM, and also possess high quality process accreditation(s). 2) The Bidder should be well established and have sound financial standing. Only those Bidders who fulfil all the eligibility criteria are eligible to respond to the RFP. Any effort by Bidder to influence the Bank in the Bank s bid evaluation, bid comparison or contract award decision may result in the rejection of the Bidder s bid. Bank s decision will be final and without prejudice and will be binding on all Bidders. 3) The bidders are required to meet the following eligibility criteria and provide adequate documentary evidence as specified for each of the criteria stipulated. Only those bids would be further processed, which satisfy all the eligibility criteria. 4) ALM Solution for the purpose of Eligibility Criteria will comprise of the core ALM functionalities i.e. Liquidity Risk Report (SLS) and Interest Rate Risk Reports (IRST & IRSD). Sr. No. General Eligibility Eligibility Criteria Documentary Evidence to be submitted to the bank 1 The bidder should be in existence for 5 years as on 31st March 2014. (In case of mergers/acquisitions/restructuring or name change, the date of establishment of earlier/original firm would be taken into consideration.) Certificate of incorporation. 2 The bidder as well as the OEM should be a Profit making entity for last three financial years i.e.2011-12, 2012-13, and 2013-14. (If 2013-14 results are not finalized yet, then 2010-11, 2011-12, 2012-13 will be considered). Copies of Annual Reports in case of listed companies and Copies of audited balance sheets and P&L statements in case of others for past 3 financial years. Page 12

Sr. No. 3 4 5 Eligibility Criteria The Bidder must have a presence in India for at least 3 years and should have average revenues in excess of INR 50.00 Cr. (INR Fifty Crores) for the past 3 financial years i.e. 2011-12, 2012-13, and 2013-14. (If 2013-14 results are not finalized yet, then 2010-11, 2011-12, 2012-13 will be considered). The bidder should own the intellectual property rights of the product/solution or he should have rights from the owner, if not, the Bidder should have in place proper tieups, commercial agreements, authorised implementation partnerships etc. for development /resale/ customisation of software with the product bidder or any third party, whose software products are offered. The Bidder and OEM should not have been blacklisted at the time of submission by the Central/any of the State Governments/ statutory body/ regulatory body/indian Banks Association in India Documentary Evidence to be submitted to the bank Copies of Annual Reports in case of listed companies and Copies of audited balance sheets and P&L statements in case of others for past 3 financial years. Letter /Certificate from OEM Self-declaration of bidder & OEM Product Capabilities 6 The ALM Solution should have been procured by at least 2 Scheduled Commercial Banks amongst which at least 1 should be a Public Sector Bank. Credential letter on bank s letter head 7 8 The ALM Solution should have been satisfactorily implemented by a Bank operating in India as on 30.06.2014. The Bidder should have experience of implementing ALM solution in a Bank in India. Credential letter on bank s letter head The bidder needs to submit the credentials of the team who will do the implementation. 2.5 Preparation & Submission of Bids Mode of submission The bidder shall prepare two copies each of the Technical, Indicative Commercial and Eligibility Criteria. The bidder shall seal the original and copy of these three bids in separate envelopes (Total Six envelopes). All the original bids should be further sealed in to one outer envelope marked as Original Bid and all the copy bids should be sealed in a separate outer envelope marked as Copy Bid. The two outer envelopes shall be marked as BID FOR ALM SOLUTION AGAINST RFP REF. NO.: HO/DIT/ALM/2014-15/16 ORIGINAL BID and BID FOR ALM SOLUTION AGAINST RFP REF. NO.: HO/DIT/ALM/2014-15/16 COPY BID. In case the bidders opt to remit the non- Page 13

refundable bid submission fee by way of DD/Banker s Cheque at the time of bid submission, the same shall be safely kept in the outer envelope containing Original Bids. In addition to the DD/Banker s Cheque, this outer envelopes shall contain following envelopes (Original /copy as the case may be) : 1. Envelope labelled as Eligibility Criteria ; 2. Envelope labelled as Technical Bid ; 3. Envelope titled Indicative Commercial Bid ; All documents/papers should be self-attested by the authorized representative of the bidder and stamped properly. Soft copies of the requisite documents/papers contained in a Compact Disc (CD) should also be included in the respective envelopes. The response should be organized and submitted in the following manner: 1) Envelope labelled as Eligibility Criteria This envelope should contain the documentary proof and annexure required if any in respect of each of the criterion listed out in Section-2.4. The check list for submission of eligibility criteria is given in Annexure-4. This envelope should also contain- The profile of bidder as specified in Annexure-5. Letter with details of authorized signatories/power of Attorney s in the name of the authorized signatories who can represent the Bidder/s with regard to the obligations under the RFP or contract Two hardcopies (one original and one duplicate) of duly filled up Annexure 4 & 5, along with supporting documents. 2) Envelope labelled as Technical Bid The Technical Bid containing the response to both technical and functional requirements for the Solution is to be sealed in a separate Envelope superscripted on the top of the cover as TECHNICAL BID. The Technical Bid must not contain any price information. Soft copy of the response to the technical bids should also be provided in MS excel/ms word. The soft copy is to be placed in the envelope. The Bidder should certify that the contents of the soft copy are same as that provided in hardcopy as per Annexure - 21 Undertaking Document Correctness. In case of any discrepancies between the hardcopy and softcopy the Bank will use the hardcopy submitted by the Bidder for the evaluation. Two hard copies of the technical proposal (one original and one duplicate) with pages properly numbered, each page signed and stamped. The technical proposal should be bound in such a way that the sections of the proposal can be removed and separated easily. Signed copy of the RFP, all annexure and appendices fully filled up need to be submitted. Contents of Technical Bid 1. Implementation methodology as given in Annexure-6 2. Responses against functional and technical requirement specified in this RFP (as indicated in above paragraphs). 3. Reference site details in the format specified in Annexure-7 4. Details of past experience as specified in the Annexure-8 5. The proposed project team profile as given in Annexure-9 Page 14

6. The details of training programs conducted by the bidder in format specified in Annexure-10. 7. The documentary proof in support of these programmes in the customer- Bank s letter head shall also be included in this envelope. Other Relevant Information a. Executive summary of Bidder s response b. Detailed technical write up covering the detailed scope of work c. Duly signed covering letter by the authorized signatory Bid Form d. Manufacturers Authorization Form from the Bidders proposed partners e. Data Centres requirements f. Comments on the RFP terms and conditions g. Reverse auction compliance statement h. Soft copy of the technical bid only. i. Two originals of all the documents submitted in the technical bid j. Any other information in general This envelope shall also contain all the Annexures specified in this RFP related to technical evaluation. It shall also include documentary proof required for substantiating the information given in Annexure, if any. In addition to the Annexures specifically listed out in this RFP this envelope shall also include: 1. Technology, architecture of proposed solution, exact tools to be used 2. List of all software / tools to be used together with licensing details 3. Tentative project time schedule and plan 4. Project management, control and tracking mechanism 5. Quality control setup and procedures to be followed 6. Implementation & Training plan 7. Technical brochures and user manual In case any Bidder does not quote for any of the components, the response would be deemed to include the quote for such unquoted components required for meeting the functional and technical requirements including the service levels specified in this RFP. The Bank reserves the right not to permit changes in the technical specifications and not to evaluate the offer in case of non-submission of the technical details in the required format or partial submission of technical details. 3) Envelope titled Indicative Commercial Bid The Indicative Commercial Bid should be given by the Bidders in the format as shown in Annexure -13. The Bidder is expected to quote unit price in Indian Rupees (without decimal places) for all components on a fixed price basis as part of the commercial Bid inclusive of all costs and taxes like customs duty, excise duty, import taxes, freight, forwarding, insurance, delivery, installation, training etc. at the respective delivery location of the Bank but exclusive of only applicable (in India) Sales Tax/VAT, Service Tax and Octroi / Entry Tax / equivalent local authority cess, which shall be paid / reimbursed on actual basis on production of bills. Further, receipts of such payments made to relevant authorities must be produced for Octroi / Entry Tax / equivalent local authority cess. The Bank will not pay any other taxes, cost or charges. The indicative price should be quoted for each item, each unit with total cost, module wise, if modular. Indicative Prices for all items including optional items, if any, should also be mentioned. AMC for each item year wise should be provided. The envelope labelled as Indicative Commercial Bid should include the following: 1. Covering letter duly signed by the authorized signatory Page 15

2. Details of cost of deliverables for the system (in the format given in Annexure-12 A 3. Details of hardware sizing/configuration suggested for the proposed solution in the format given in Annexure -12 B. 4. Annexure - 13 containing the total cost of ownership computation. The Bidders have to note that the commercial proposal post reverse auction must contain the following: 1. The bid covering letter cum declaration format is given in Annexure - 11 2. Format for furnishing details of Software & Hardware (Annexure 12 A & 12 B) 3. Complete Table for Arriving at the Total Ownership Cost (as per Annexure 13) including all tables (i.e. Tables A, B, C, D & E). 4. Soft copy of Commercial Bid/Commercial Proposal. The Bidder shall take care to submit the Bid properly filed so that the papers are intact. The Bidder shall submit the bid in suitable capacity of the file such that the papers do not bulge out and tear during scrutiny. The Bids, which are not sealed as indicated above, are also liable to be rejected. The price schedule shall be submitted in indicative commercial Bid only. In a nutshell, the indicative commercial Bid details will need to be provided for all requirements of the Bank to arrive at TCO (Total Cost of ownership) of the solution. The Bidder while furnishing the cost under the above heads must furnish the split up cost particulars of all major components/line items under each head. The indicative commercial bid is obtained for the complete solution and Bank will place the order after finalizing the Bidder. Further, while the Bidder has to quote for all the components of the solution, Bank may at its discretion wherever beneficial, procure licenses for some software separately, based on any existing agreements entered into for purchase of such software. The envelope shall be addressed to the Bank at the address given below; The Asstt. General Manager (IT), Allahabad Bank, Head Office, 2, Netaji Subhash Road, Kolkata 700 001, India The Project name and a statement: DO NOT OPEN BEFORE 22 nd December, 2014, 16:00 Hours should also be mentioned on the envelopes. 2.6 Opening of Technical Bids The technical bids (containing Technical & Eligibility Criteria) will be opened at 16:00 Hours on 22 nd December, 2014 in the presence of Bidders Representatives. 1) The Bidders may note that no further notice will be given in this regard. Further, in case Bank does not function on the aforesaid date due to unforeseen circumstances or holiday then the Page 16

bid will be accepted on the next working day and bids will be opened at the same venue on the same day. 2) Bank however reserves the right to change the date & time for opening of Technical bid without assigning any reason whatsoever. In case there is a change in the schedule the same will be intimated to the Bidders by putting up on the Bank s website for enabling them to be present during the Bid opening. 3) The Bidders names, bid modifications or withdrawals and the presence or absence of the requisite bid security and such other details as the Bank, at its discretion, may consider appropriate, will be announced at the bid opening. No bid shall be rejected at bid opening, except late bids, which shall be returned unopened to the Bidder. 4) The technically qualified Bidders will be intimated to participate in the demo sessions. Date and schedule of demo sessions will be announced at an appropriate date and time. 5) These bidders will also be informed about the Online Reverse Auction Process, to identify Lowest Quoted (L1) Bidder. Online Reverse Auction procedures and timings will be informed separately. Technically qualified Bidders will be informed the modus operandi for this purpose and Bidders will have to abide by the E-Tendering rules. 6) Bank shall be under no obligation to accept the lowest price bid or any other offer received in response to this RFP. Bank will not be obliged to meet and have discussions with any Bidder, and / or to listen to any representations in respect of the rejection. 2.7 Bid Security 1) The bidder shall furnish a bid security for Rs. 50,00,000 (Rs. Fifty Lacs only) as a part of their bid. 2) The Bid security is required to protect the Bank against the risk of Bidder s conduct, which would warrant the security s forfeiture. 3) The Bid security shall be denominated in Indian Rupees and shall be one of the following forms:- a. A bank guarantee for Rs. 50,00,000/- (Rupees Fifty Lakhs Only) issued by a Private sector / Public Sector bank in India (other than Allahabad Bank), acceptable to the Bank, in the form as per format in Annexure-20, valid for Sixty (60) days beyond the validity of the Bid. b. A Banker s Cheque / Demand Draft, issued by a Private Sector / Public sector Bank in India (other than Allahabad Bank), drawn in favour of Allahabad Bank payable at Kolkata for a sum of Rs. 50,00,000/- (Rupees Fifty Lakhs Only). 4) Unsuccessful Bidders Bid Security will be discharged or returned after the issuance of Purchase Order to the Successful Bidder. The successful Bidder s Bid Security will be discharged upon the Bidders signing the Contract and furnishing the Performance Security. 5) The Bid Security will be forfeited, I. If the Bidder a. withdraws its Bid during the period of bid validity or b. does not accept the correction of errors in accordance with the Instructions to Bidders; or II. If the Bidder, having been notified of the acceptance of its bid by the Purchaser during the period of bid validity: a. fails or refuses to execute the Contract Form if required; or Page 17

b. fails or refuses to furnish the performance security, in accordance with the Terms & Conditions of the RFP or contract. 2.8 Modification and Withdrawal of Bids The bidder may modify or withdraw its bid after the bid s submission, provided that the Bank receives written notice for modification or withdrawal of the bids, before the expiration of deadline prescribed for submission of bids. In case of modifications, the bidder is expected to resubmit entire bid before the last date of submission. Only addendums/amendments will not be accepted. 2.9 Rejection / Acceptance of Bid The Bank reserves the right to accept or reject any or all the bids without assigning any reason whatsoever. Any decision of the Bank in this regard shall be final, conclusive and binding on the bidder. 2.10 Cancellation of Bid The Bank reserves right to re-issue/re-commence the entire bid process and or any part in case of any anomaly, irregularity or discrepancy in regard thereof without assigning any reason whatsoever, at its sole discretion. The decision of the Bank in this regard shall be final, conclusive and binding on the bidder. 2.11 Period of Validity of Bids Validity Period: - Bids shall remain valid for 180 days from the last date specified for submission of bids in this RFP. The Bank holds the rights to reject a bid valid for a period shorter than 180 days. Extension of Period of Validity: - In exceptional circumstances, the Bank may solicit the Bidder s consent to an extension of the validity period. The request and the response thereto shall be made in writing. Extension of validity period by the Bidder should be unconditional and irrevocable. 2.12 Pre-Bid Meeting The prospective bidders, who have purchased a copy of the RFP and submitted the bid price (for downloaded RFP), shall be permitted to attend a pre-bid meeting to be held as indicated in the Invitations for Bids. Up to a maximum of 2 (two) representatives of each prospective bidder will be permitted to attend the pre-bid meeting. However the Bank, at its discretion, may permit any additional representative of any prospective bidder to attend the pre-bid meeting. The purpose of the meeting is to clarify issues and to answer queries on any matter that may be raised up to that stage. The issues/queries to be raised must be in writing and submitted at least 2 working days before the scheduled pre bid meeting. The Bank will have liberty to invite any outside agency, wherever necessary, to be present in the pre-bid meeting to reply to the queries of the bidders in the meeting. Any modification in the RFP, which may become necessary as a result of the Pre-Bid Meeting, shall be made by the Bank exclusively through the issue of an Addendum and will be sent to all Page 18

prospective bidders who have purchased the RFP, at least 4 working days prior to the last date for submission of bids. Non-attendance at the Pre-bid Meeting will not be a cause for disqualification of a bidder. The text of the questions raised (without identifying the source of enquiry) and the responses given, together with amendment to the bid document, if any, will be posted on our web site and also informed to all purchasers of the bid documents. Page 19

3. Selection Strategy 3.1 Objective 1) The objective of the evaluation process is to evaluate the bids to select an effective and best fit solution at a competitive price. The evaluation will be undertaken by the Selection Committee formed by the Bank, which may also include external experts/consultants. The committee or authorised official shall recommend the successful bidder to be engaged for this assignment to the Board and the decision of our Board shall be final, conclusive and binding on the bidders. 2) Through this Request for Proposal, Bank aims to select a Bidder/ application provider who would undertake the designing and implementation of the required solution. The Bidder shall be entrusted with end to end responsibility for the execution of the project under the scope of this RFP. 3) The Bank will scrutinize the offers to determine whether they are complete, whether any errors have been made in the offer, whether required technical documentation has been furnished, whether the documents have been properly signed, and whether items are quoted as per the schedule. The Bank may, at its discretion, waive any minor non- conformity or any minor deficiency in an offer. This shall be binding on all Bidders and the Bank reserves the right for such waivers and the Bank s decision in the matter will be final. 4) Bank may call for any clarifications/additional particulars required, if any, on the technical/ commercial bids submitted. The bidder has to submit the clarifications/ additional particulars in writing within the specified date and time. The bidder s offer may be disqualified, if the clarifications/ additional particulars sought are not submitted within the specified date and time. Bank reserves the right to call for presentation/s, product walkthroughs, on the features of the solution offered etc., from the bidders based on the technical bids submitted by them. Bank also reserves the right to conduct Reference Site Visits at the bidder s client sites. Based upon the final technical scoring, short listing would be made of the eligible bidders for final commercial bidding. 5) The evaluation will be a four-phase process:- Phase 1 Eligibility Criteria Evaluation Phase 2 Technical Bid Evaluation Phase 3 Indicative Commercial Bid Evaluation &Online Reverse Auction Phase 4 Weighted Evaluation 6) The Technical evaluation and the Commercial evaluation (post reverse auction) shall have the weight-age of 70% and 30% respectively for evaluation, and this weight-age shall be taken into consideration for arriving at the Successful Bidder. NOTE: The Bank's decision in respect of eligibility criteria, evaluation methodology and short listing of bidders will be final and no claims, whatsoever in this respect, shall be entertained. The Bidders meeting the eligibility criteria as laid out in Section 2.4 would be shortlisted for the Technical Bid Evaluation. 3.2 Evaluation of Technical Bid The proposal submitted by the Bidders shall be evaluated on the following group of parameters. Page 20

Functional Requirements (FR) Technical Requirements (TR) Product Demonstration and Bid Presentation (PB) Approach and Methodology (AM) & Past Experience (PE) Site Visits (SV) 1) The marks are assigned for each individual parameter under these groups and marks scored by each bidder under each parameter are aggregated to find out the total technical score of the bidder. 2) The score for evaluation of different Modules & systems shall be decided by the Internal Selection Committee. 3) The selection parameters are explained in following paragraphs 4) This evaluation will be carried out on a total score of 1,000 on the basis of the following evaluation parameters defined in this section Sl. No. Proposal Bid Evaluation Sub Scores 1 Functional Requirement (FR) 200 2 Technical Requirement (TR) 200 3 Product Demonstration & Bid Presentation (PB) 350 4 Approach, Methodology (AM) & Past Experience (PE) 100 5 Site Visit (SV) 150 Maximum Technical Proposal Bid Evaluation Score 1000 3.3 Scoring Methodology for Functional Requirements (FR) and Technical Requirements (TR) 1) The expected functional capabilities are given in Section 5. All the functional and technical requirements which are necessary for achieving regulatory compliance are mandatory. Bidder shall indicate the availability against each requirement/capability. The means of indicating availability is given in the following table. The marks thus scored will be scaled to the Sub-Score given in Sec. 3.2. The Type of Response/Scale Description** Max. Marks S Standardized, this scale indicates that this feature is a standard feature of the solution. 10 A Alternative available 7 C Customization required. Vendor will provide the customization with the stipulated date of the phased rollout 5 U Unavailable. Functionality is not available and will not be provided by the bidder. 0 **Any responses other than S/C/A/U are not acceptable and will be treated as U. 2) The Software solution offered, however, should have at least 75% of the requirements as standardized. The remaining should be customized before GO LIVE, at no extra cost to the Bank. Page 21

3.4 Scoring Methodology for Product Demonstration and Bid Presentation (PB) 1) Eligible Bidders will be required to make presentations to supplement their bids and show a detailed product demonstration. The number of eligible bidders called for product demonstration is purely a matter of discretion of the Bank. 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 will result in rejection of the proposal. 2) The marks awarded under this parameter shall be based on the effectiveness of the demonstrations and presentations made by the bidder. Using the Functional & Technical Requirements as a base in part or as a whole, the Bank may formulate a detailed questionnaire for the product demonstrations. 3.5 Scoring Methodology for Approach, Methodology (AM) & Past Experience 1) The bidder is expected to provide, as a part of the technical bid, a detailed document that explains the approach and methodology proposed by the bidder for the implementation of the proposed solution. The Approach and Methodology adopted for the Implementation would be evaluated by Bank and would at the minimum cover Team Strength, Project Management and Training. 2) Team Strength: Bidder responses to each point under Team Strength in Proposed Team Profile, including the team profile provided by the Bidder, would be evaluated. The Bidder should ensure that the people above the role of the Team Lead who are proposed for this project should have worked on projects in Banks earlier. The members of the proposed project team and team lead should have a minimum experience of 2 years and 5 years respectively in implementation of similar kind of projects in India /Abroad. 3) In addition to the profile of his team members, the bidder is bound to furnish the profile of team members of his partner. The format for furnishing the team profile is given in Annexure 09. The marks assigned under this parameter are based on the qualifications and experience of team members. 4) Project Management: Bidders are required to respond to each point under Project Management in Annexure-6. Each question will be evaluated for suitability of response. The Bidder should provide explanation on the Project Management process that is proposed for the Bank including details of how the same was applied in a similar project. 5) The Bank will require the Bidders to make presentations regarding the various aspects of the proposed solutions. This process will also enable the Bank to clarify issues that may be identified from the Bidders responses to the RFP. The Evaluation Committee decided by the Bank would be scoring the presentation made by the Bidders at Bank s premises based on a structured questionnaire broadly across the following:- a. Project Execution Methodology b. Solution Architecture and Design Key Features and Functionalities c. Interface approach and methodology d. Adherence to Project Timelines e. Execution Competency (Solution Accelerators, Functional & Technical Competency) f. Approach and Resource Commitment (for Managed Services and People profiles of all key personnel as part of this project) g. Project Execution Methodology h. Solution Architecture and Design Key Features and Functionalities 6) Past Experience: The Bidder s past experience shall be evaluated on the basis on the details given in the Annexure-8 Past Experience Page 22

3.6 Scoring Methodology for Site Visits (SV) 1) Reference site visit/ Tele conference/written Correspondence: The Bank requires the Bidders to provide at least TWO references from any Scheduled Commercial Bank in India, amongst which at least one should be a Public Sector Bank, where the solution has been deployed. The reference site should be one where the Bidder has implemented the ALM Solution and is currently in use as of date of the RFP. 2) A committee of officials from the Bank would carry out Reference Site Visits and/or Telephonic interviews, Written Correspondence with the existing customers of the Bidder. The inputs that have been received from the Customer would be considered by the Bank and this might not need any documentary evidence. This scoring would be purely on the basis of inputs (like satisfaction of the organization of the product, timeliness of implementation, promptness of support services etc.) provided by the Bidder s customers. The Bank at its discretion may reject the proposal of the Bidder without giving any reasons whatsoever, in case the responses received from the Site Visits are negative. 3) The Cost for travel and lodging for the team identified by the Bank will be borne by the Bank for site visits. However, the Bidder may be expected to facilitate these arrangements. 3.7 Disqualification Parameters in Technical Bid Evaluation 1) The bidders who fail to score above or equal to 80% of the technical score shall be disqualified. If only one bidder/none of the bidders qualify, Bank at its discretion may select bidders with the top two/three technical scores for commercial evaluation. 2) 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 and also where the responses received from the Site Visits are negative. 3.8 Evaluation of Indicative Commercial Bid & Online Reverse Auction 1) Only technically qualified Bidders (as per the laid out criteria) will be intimated to participate in the Online Reverse Auction to identify L1 (lowest quoted) Bidder. The comparison shall be between the prices quoted. The price quoted should include all components specified in the Total Bid Price (as arrived in Table E: Total Cost of Ownership/Total Bid Price in Annexure 13) i.e. The price should be inclusive of all Duties, Freight, Insurance, Delivery, Installation and Warranty for 3 years etc. and AMC for 2 years (post-warranty) exclusive of VAT/CST, Service Tax, Octroi/Entry Tax only. 2) Computation Methodology for arriving at Best Price : The techno-commercial score shall be calculated as follows: Total Score = (C-LOW / C n ) * C-weight + (T n / T-HIGH) * T-weight Where, C-Low = Lowest Commercial Quote C n = Commercial Quote of the Bidder being evaluated C Weight = Weight of the Commercial Bid i.e. 30% T n = Technical Score of the Bidder being evaluated Page 23

T-High = Highest Technical Score T-weight = Weight of the Technical i.e. 70% Here C and T are the commercial and technical scores of the respective bidders. The scores would be rounded-off to two decimal points. C-weight & T-weight shall be weighted on 30% and 70% criteria respectively. The evaluation criteria mentioned in this RFP is tentative and the score earned by the bidders in accordance with the evaluation parameters listed out above does not confer them the right to be awarded the contract. Further, the Bank has sole discretion in selection of the successful bidder and decision of the Bank in this regard shall be final. 3.9 Reverse Auction Bank would conduct an online reverse auction process on the commercials submitted by the Bidders. As such it is necessary that authorized personnel of the firm or organization sign the BID. The designated personnel should be authorized by the organization or by a senior official of the organization having authority to do so. The same person or a different person should be authorized, who should have digital certificate issued in his name and should have authority to quote bid amount in the commercial bid and also quote offer price during on-line reverse auction. The details of digital certificate, like Name, Digital Key details, issuing authority and validity etc. to be provided later. Page 24

4. Scope of Work 4.1 Broad scope The broad scope of the project envisages: 1) Supply, Installation, Deployment, Customization, Testing, Implementation, Rollout, Maintenance and Support of the software for ALM Solution to achieve compliance with RBI/BCBS/IBA/GOI Guidelines pertaining to ALM. Bidder have to provide the sizing/configuration of the required hardware, OS, RDBMS, Networking Equipment, Bandwidth etc. to the Bank. Any other hardware/software which is essential to run application but not advised to the Bank in the bid will be supplied and installed by the bidder free of cost. 2) Gap Analysis, Parameterization, historical data management, verifying data quality, migrating data, user acceptance testing, documentation, knowledge transfer and support. 3) Interfacing with other external systems including core Banking software solution, Treasury Solution, Risk Management Solutions, Automated Data Flow, Foreign branch banking Software, validation of models and processes and maintenance of application software, system software, interfaces etc. provided by the bidder. 4) Providing training to Bank s designated personnel and also provide Modular wise user manual as well as administrator s manual, post-implementation on-site support up to the next regulatory review from GO LIVE date and further support as referred for the warranty and AMC period 5) The solution/s offered should be web based, open platform and support data transfer and consolidation from the networked systems either online or dial up. 6) In case of discrepancies within the RFP, the discretion of Bank will prevail and shall be binding on the bidder. The project development and UAT would be held at the Head office of the Bank, located in Kolkata, West Bengal. The software shall be installed, implemented and maintained at the Banks data centre, in Mumbai, Maharashtra and at the Disaster Recovery Site in Lucknow, U.P. The bidder is supposed to provide functional and operational support to the above or other centres as per requirements of the Bank. 4.2 Detailed scope The detailed scope of assistance has been given below 4.2.1. Gap identification & Resolution 1) The selected bidder will be responsible for conducting the gap analysis for identifying gaps in Bank s framework, policies, procedures, governance, and existing systems which needs to be bridged prior to deployment of ALM architecture. The gap analysis should be done in the context of industry best practices and regulatory guidelines issued by RBI/BCBS etc. pertaining to ALM. 2) Provide the Bank with the gap identification report along with the recommendations and estimated time frames to resolve the same. 3) Provide various tools/utilities to bridge the gaps identified during GAP analysis phase without any extra cost. 4) Determine the customization requirements, in case a particular functionality requirement is not supported by the existing version of the ALM solution. Page 25

5) Resolve gaps by customizing the proposed solution by way of modifications/ enhancements, as necessary. 6) Facilitate data migration from the existing data already collected by the Bank to the new system with consistency. All the details from the migration date till the date of GO LIVE should also be migrated from the existing data to the proposed solution. 4.2.2. Design of Solution 1) The selected bidder is required to design the ALM Solution, with the functionalities identified in the Functional Requirements and Technical Solution Requirements for, Asset Liability Management Solution as detailed in this RFP. 2) Automated Interfaces required for the solution with other internal systems and external systems has to be provided by the selected bidder to ensure satisfaction of the functional and technical requirements. Bidder will be responsible for the procurement of any tool required to develop the interface. Bidder will document the entire interface logic and process with change management procedures in compliance with Bank s policies and best international practices. 3) The selected bidder is expected to leverage the Bank s existing/proposed data centre services, EDW infrastructure (as and when operational), storage, backup tape libraries, archival, legacy data etc. with the endeavour to reduce the overall cost of procurement to the Bank. The bidder shall also continuously explore avenues to reduce the cost and act in the best interest of the Bank. 4) Bidder shall provide the Bank, understanding and full access to Database, Database Table Structures and Data Dictionary of the proposed solution. 4.2.3. Parameterization, Configuration and Customization of Software 1) To assist in bridging the identified data gaps for compliance with RBI and other relevant guidelines. 2) The Bidder shall be responsible for accuracy of the parameters set in the system according to business needs of the Bank. 3) The cost of all customizations is required to be included in the Commercial Bid and the Bank will not make any additional costs for this throughout the term of the contract if the same has been specified as a requirement of the Bank in this RFP. Thus, this is a fixed bid and all necessary customizations based on the functional requirements specified in the RFP will need to be conducted by the Bidder. 4) Bidder needs to give detailed plan for customization. All customization has to be completed within the project timelines. 5) The Bidder should ensure that the quality assurance and development standards outlined in the development methodology of the proposed solution are adhered to and required functionalities/reports related to same are generated and shared with the Bank team on a regular basis. 6) Enhancements provided by the Bidder would include changes in the software due to statutory and Regulatory changes and those required due to changes in industry practices or any other requirements of the Bank related to the above, which will need to be provided at no extra cost to the Bank for the entire period of the contract. It will include, but not limited to, all the functionalities mentioned in the Functional Requirements. 7) Before completing this phase, the bidder shall ensure that ALM solution / architecture proposed to be implemented/laid down is capable of meeting all functional and technical requirements specified in this RFP. 8) Apart from the reports specified elsewhere in this document, the vendor will be required to configure an additional 50 (fifty) number of reports in the solution as per specifications provided Page 26

by the Bank. System should also have provision for dashboards, which should be configured as per bank s requirement. 9) The vendor shall also be responsible for customizing and generating regulatory/statutory reports/returns/disclosure statements as per IFRS requirements, when it becomes mandatory. 4.2.4. Testing 1) The Bidder will be responsible for conducting system integration testing to verify that all system elements have been properly integrated and that the system performs all its functions. The system integration testing will be required to be confirmed by the Bank. 2) The Bank will conduct User Acceptance Tests ( UAT ) under guidance, review and Supervision of the bidder to ensure that all the functionality required by the Bank as mentioned in this RFP is available and is functioning accurately as per the expectations of the Bank. Consequent to UAT, if some of the functionalities, specified in this RFP are not present in tune with the Bank s expectations, the bidder shall make appropriate changes. All UATs would require sign-off from the Bank after meeting the specified and expected standards. 3) Bidder will be responsible for setting and maintaining the test environment during the entire period of project implementation. The bidder will ensure that test environment s configuration and parameterization for conducting the UAT is in line with bank's risk management framework and this RFP s requirements. The bidder shall ensure that the test environment has the same configuration and functionalities as that of the production environment. 4) The Bank will provide scenarios for UAT and the Bidder will prepare test cases including the test data to support all the Business scenarios. The Bidder will assist the Bank in analysing / comparing the results of testing. 5) Bidder shall provide adequate resources for trouble-shooting during the entire UAT process of the Bank. 6) The Bidder will be responsible for maintaining appropriate program change control and version control of the system as well as documentation of UAT and change of configuration and parameterization after making changes in the system. 7) All errors, bugs enhancements/modifications identified during and after testing will be resolved within the overall timelines for implementation. 8) The Bidder will be responsible for using appropriate tools for logging, managing, resolving and tracking issues and its progress, arising out of testing and ensuring that all issues are addressed in a timely manner to the satisfaction of the Bank and as per requirements mentioned in this RFP. 9) The Bidder will be responsible for performing functional UAT and integrated UAT on minimum two snapshots (End of Quarter & End of Month on Pre-Audit and Post-Audit data) of production data. 4.2.5. Training 1) The Bidder shall be responsible for training the concerned employees of the Bank in the areas of system administration, implementation, use / operations, management, database management, error handling /troubleshooting, etc. of the ALM Solution. 2) Structure of the training program covering number of trainings, locations and number of participants etc. is to be advised by the bidder in writing. 3) Bidder will also be responsible to develop training and reference materials for all the functionality of the software. Training / reference materials should be designed separately for operational staff / user, IT department and senior management. Training material should comprehensively cover all the functionality of the proposed ALM solution and be written in a user friendly manner with use of graphs, processes flows, screen-shots of the actual system functionality etc. Page 27

4) Bidder should provide Bank specific training material designed considering its requirements in this RFP. Training material so provided will be subject to review and sign-off by the Bank as a project deliverable. 5) The training should at least cover the following areas: Functionality available in the solution including logic and methodology of the same; Customization / Parameterization; Techniques for Slicing and dicing of data, information, and output Auditing techniques including generation of audit trail reports; Advanced trouble shooting techniques; Techniques for generation, view and reporting of intermittent results; Deployment of various processes, risk reporting and identification procedures, Application of controls, analysis procedures provided as part of the solution; Techniques of Customization, development and configuration of required reports including ad-hoc reports from the solution provided; Development and deployment of new functionalities using the proposed solution; System & Application Administration such as creation of user, user groups, assigning rights, System Information Security Settings etc. Perform Impact Analysis using the solution; Business use of the solution Technical training to be provided to IT staff of the Bank, and this shall include installation, technical architecture, configuration & setup, customization, report generation, backup and recovery, trouble shooting, data synchronisation, file uploads etc. 6) The minimum number of training sessions shall be decided by the Bank and the successful bidder is bound to oblige. 4.2.6. Implementation 1) The proposed solution should cover all the Branches/Offices/Departments of the Bank and have the capability to scale up for meeting future requirements. The solution should be scalable and capable to handle increased volumes. In the event the Bank adds/changes/updates source/core banking systems in the future the solution should be flexible to handle such new source systems. 2) Generation of required reports for domestic as well as overseas operations 3) Setting up of User Acceptance Test Environment, Live System and Disaster Recovery System. 4) To assist in obtaining any approvals from regulator or registration with any statutory Body, if required, regarding the implementation of ALM solution. 5) The Bidder will have to provide the necessary interface with all applications as required at no extra cost to the Bank. There should also be a flow of report level data from the proposed system to the ADF system of the Bank for regulatory submission as well. The vendor will be required to ensure the correct data flow at all times. 6) At present, the Bank has various solutions running on both Windows and RISC platforms with Oracle and SQL Server databases. The solution provided shall be capable to integrate with these databases directly. Ultimately, the ALM Solution shall be linked to Enterprise Data Warehouse (as and when operational). The solution should be able to seamlessly integrate with upcoming Enterprise Data Warehouse and shall function as a Data Mart to the EDW. The proposed solution should be compatible to the following platforms i.e. Windows, UNIX and Linux with Intel and/or RISC systems. Also include overseas branch (es). Page 28

7) By means of diagrammatic/pictorial representations, the Bidder should provide complete details of the hardware, software and network architecture of the ALM Solution (module and sub module wise), including source / method of Data capture and transfer, validation, updating and database maintenance for networked branches. In this regard the bidder should also provide logical architecture and high level diagram of hardware/software/network architecture. 8) The Bidder should recommend the hardware, operating system, database, data replication requirements along with data replication solution and a required Test server for ALM solution. 9) IT infrastructure including hardware, OS, database, Storage Firewall & Network Security etc. will be provided by the Bank as per requirement specified by the bidder. The Bidder has to ensure that vulnerabilities at application level in case of any breach shall be handled by the offered application software. 10) The total storage requirement proposed by the bidder shall take into account incremental growth of the Bank, over the next 7 years. The Bidder should specify appropriate size storage to meet the requirements of the Bank. 11) Complete details for the hardware required for the successful operation of the Solution should also be provided by the Bidder, with full particulars like configuration, memory type, future expandability, processor type, number of processors, processor speed etc. Keeping in mind that there should be no single point of failure. (Annexure 12 B) 12) The Bidder should specify the hardware requirement taking into consideration the efficiency level, response time, data processing requirement, number of users, and all other parameters to ensure that the efficiency of software system is not affected because of hardware. Bidder should provide details for DR site such as network and security requirements, switches, routers etc. 13) The Bidder will certify that the hardware specified is adequate for meeting performance standards set by the Bank. 14) The Bidder should also recommend the Bank with the number of racks required for the servers / equipment and associated infrastructure, as well as power requirements (average, peak and rated power) and any other specific requirements for the servers / equipment (Network and security requirements, switches, routers etc.) and associated infrastructure for both DC (Data Centre) & DR (Disaster Recovery) sites. 15) Sizing of equipment, hardware etc. as required, depending on the functionalities required by the Bank as mentioned in the RFP, should be provided by the Bidder for processing of existing portfolio of the Bank with increase in volumes at approximately 20% p.a. and addition of new products/instruments and data maintenance for a minimum period of 7 years as per RBI guidelines. 16) As part of implementation all data migration (as and when required) from the existing system including any other system procured by the Bank during the period of contract to the proposed ALM system will be done by the Bidder. The Bidder shall demonstrate to the satisfaction of the Bank regarding accuracy and comprehensiveness of the data migrated to the new system. 4.2.7. Information Security System should have standard input, communication, processing and output validations and controls. 4.2.8. Facilities Management Services (FMS) Facility Management services will be provided by the bidder. Bidder should quote per year FM charges for the entire duration of project, however Bank will have liberty to discontinue the FM Services at any point of time during the contract period. Page 29

1) Facilities Management: Facilities Management would include support for all application software, provided by the Bidder. Bidder should elaborate on FMS like number of resources to be deployed post implementation. FM services should be provided for entire project duration. The resource for facility management shall be deployed on site after completion of next regulatory review from the GO LIVE Date till the completion of the project. Uninterrupted services of helpdesk shall be available to the bank during working hours. The bank may require the resource/helpdesk to be available for extended hours during select working days e.g. during finalisation of financial results, department audit, regulatory review, etc. 2) The Bidder needs to consider and envisage all services and associated cost that would be required in the maintenance of all the applications and interfaces provided, quoted and developed by the Bidder. 3) The Bidder is expected to develop a methodology for conducting the FM for Bank based on the requirements. The personnel being deployed by the Bidder for FM at the Bank should have relevant experience. 4) The Facilities Management services would at least include: System Administration Software Distribution Software License Management Software maintenance Updates/Upgrades/New releases/new versions Operations Management Functional Support 5) The Bidder shall provide detailed list of services provided under FM, breakup of manpower and methodology for providing above services at each of the locations, respectively. 6) The Bidder will be solely responsible for providing and maintaining all services as mentioned above for all third party support applications quoted by the Bidder as a part of their proposal. 7) Restore to Service: Provide standard maintenance services including diagnostics and troubleshooting System, component & network maintenance Configuration changes, tracking, and documentation Upgrade / Enhancement. The maintenance for the services would be for all the items and other infrastructure provided by the Bidder under this RFP. 8) All the software items provided by the bidder should be of enterprise version and on perpetual basis. The Bank shall have the Right to use the software provided /installed /configured by the Vendor/bidder and/or software application systems supplied under this contract after the expiry of the period under this contract and it shall be at liberty to use/run the said software solutions with the help/support of its in house IT Officers or through any other out sourcing service Agencies. The bidder/vendors shall not have any right to question or object for continuation of the use of such software or software solutions irrespective of entering into any AMC with the Bidder/Vendor after the expiry period or not. The Bank will decide at its sole discretion after expiry of the period under this contract either to enter into an AMC with the Vendor or not. The Bidder/Vendor shall not have any right to challenge the decision of the Bank in any manner or in any proceedings. Page 30

5. Functional & Technical Requirement 5.1 Functional requirement for ALM Solution 1.1 S No Functional Requirements Extraction of Transaction Data The system should interface with all operational systems currently being used by the Bank, to extract transaction data from each source system in respective currencies Importance ( / Important / Desirable) 1.2 1.3 1.4 1.5 The system should be scalable and allow the interfacing of other systems as and when such systems are procured/implemented As a back-stop measure, the system should support the manual upload of transaction data from various operational systems in formats provided by the Bank The system should allow users to manually edit or enter a transaction / position At a minimum, the system should capture the following parameters at a transaction level to enable cash flow generation: 1.5.1 Application ID (Unique identifier) 1.5.2 Counterparty name 1.5.3 Product / instrument 1.5.4 Account number 1.5.5 Originating branch 1.5.6 Originating Business Unit 1.5.7 Originating / disbursal date 1.5.8 Maturity date / tenor 1.5.9 Outstanding balance 1.5.10 Original amount 1.5.11 Fixed / floating rate 1.5.12 Benchmark curve (if floating) 1.5.13 Fixed spread over benchmark (if floating) 1.5.14 Re-pricing frequency (if floating) 1.5.15 Re-pricing dates (previous and next) 1.5.16 Pay dates 1.5.17 Payment frequency 1.5.18 Frequency of interest accrual 1.5.19 Compounding frequency 1.5.20 Status (i.e. performing or non-performing) 1.5.21 Amortization schedule 1.5.22 Original currency Page 31

S No Functional Requirements Importance ( / Important / Desirable) 1.5.23 Defeasance Period for trading book investments 1.5.24 Account level Ratings for Investment, advances etc. 1.5.25 Sanctioned Limits for advances 1.5.26 General Ledgers Accounts 1.6 The system should be capable of accepting the external data feeds from following systems: 1.6.1 Reuters/ Newswire 1.6.2 Bloomberg 1.6.3 Any other system 1.7 The system should perform data validation checks on the source data extracted from the operational systems. The exact nature of the data validation checks will be based on inputs from the bank's IT team during implementation. 1.8 1.9 The system should alert the user through pop up or through a report, in the event of failed data validation checks. The system should also have the capability to allow users to manually enter any market yield curve or Spread Curve or Deposit Curve or any other user defined rate which is to be used as coupon or yield Cash Flow Generation 2.1 The system should be capable of generating cash flows using position data and amortization schedules for assets/ liabilities on a daily basis 2.2 At the minimum, the system should be capable of generating cash flows using position data and amortization schedules/ assumptions for all the following asset categories including 2.2.1 Advances Product 2.2.1.1 - Term Loan 2.2.1.2 - Cash credit/ Over drafts 2.2.1.3 - Demand loans 2.2.1.4 - Bills purchased and discounted 2.2.1.5 - Any other advances 2.2.2 Investments 2.2.2.1 - Investments in forwards/ futures 2.2.2.2 - Derivatives - IRS, CCS 2.2.2.3 - Investments in bonds/ equities/ Mutual Funds 2.2.2.4 - Investments in SRs/ PTC/ VCF 2.2.2.5 - Investment in Options (All types) 2.2.2.6 - Swaps (Sell/Buy)/ maturing forwards 2.2.2.7 - Any other investment/ treasury product Page 32

S No Functional Requirements Importance ( / Important / Desirable) 2.2.3 Off-balance sheet exposures 2.2.4 Other assets 2.3 At the minimum, the system should be capable of generating cash flows using position data and amortization schedules for the following liability categories: 2.3.1 Current deposits 2.3.2 Savings deposits 2.3.3 Term Deposits 2.3.4 Foreign Currency Non-Resident (Banks) (FCNR (B)) deposits 2.3.5 Exchange Earners Foreign Currency (EEFC) deposits 2.3.6 Resident Foreign Currency (RFC) deposits 2.3.7 Resident Foreign Currency Domestic (RFC (D)) deposits 2.3.8 Borrowings - Call, Notice, Repo, Term Repo, CBLO etc. 2.3.9 Bankers Acceptance Facility (BAF) borrowings 2.3.10 Contingent liabilities and off-balance sheet exposures 2.3.11 Other liabilities 2.4 The system should have the capability to generate cash flows for products having the following types of amortization schedules: 2.4.1 Conventional amortization (EMI) 2.4.2 Principal only payment 2.4.3 Balloon Payments 2.4.4 Amortization for floating rate instruments 2.4.5 Negative amortization 2.4.6 Hybrid / user defined amortization 2.4.7 Amortization on the basis of behavioural studies performed in the system 2.4.8 User defined behavioural pattern 2.5 The system should have the capability to generate cash flows for both standard and user defined re-pricing patterns for floating rate products, including: 2.5.1 Provision for defining/ capturing different benchmark curves 2.5.2 Provision for defining/ capturing different re-pricing characteristics for different periods in the life of a product 2.5.3 Provision for capturing rate caps, floors and gaps 2.5.4 Provision to capture foreign exchange rates manually or through interface with Treasury/ Newswire 2.5.5 Current reference rate 2.6 The system should allow the user to model the following and incorporate the same into the cash flow patterns generated. 2.6.1 Prepayment patterns Page 33

S No Functional Requirements Importance ( / Important / Desirable) 2.6.2 Rollovers and premature withdrawal patterns 2.6.3 Behaviour models in to Core and Volatile 2.7 The system should be capable of generating the cash flows in multiple currencies 2.8 The system should support both standard (i.e. based on product characteristics, amortization schedules, behavioural maturities etc.) and user defined payment patterns 2.9 The system should be capable of converting the cash flows from multiple currencies into a single user defined home currency based on user defined/ automatically FEDAI exchange rates The system should be capable of generating the cash flows for 2.10 the Bank separately at each of the following levels in accordance with the Regulator s requirements 2.10.1 Indian operations- Domestic currency 2.10.2 Indian operations- Foreign currency 2.10.3 Overseas operations country wise (in each currency and Total converted into home currency) 2.10.4 Consolidated Indian operations (home currency) 2.10.5 Consolidated operations at bank level (reporting currency) Reconciliation with Trial Balance 3.1 3.2 3.3 3.4 The system should accept the Trial Balance as an MS-Excel upload/ manual input/ through STP through GL system The system should also be able to draw distribution under inflows/ outflow based on data mentioned in the Balance Sheet schedule and given in the form of Excel/ file upload/ manual input/ any other mode The system should perform item-wise, automatic reconciliation of the Trial Balance with the aggregated assets and liabilities as per the liquidity profile The system should automatically alert the user in the event of discrepancies between the liquidity profile and the Trial Balance The system should allow users to identify line item under which 3.5 reconciliation difference can be parked The system should be capable of accepting balances manually 3.6 to reconcile (by passing transaction or position or GL Balance) difference between GL and the Account Level Balances The system should maintain audit trail or a separate report for 3.7 such manual adjustments Development of Structural Liquidity Profile The system should be capable of generating the structural 4.1 liquidity profile on a daily basis in accordance with Regulatory Requirement. The system should support the classification of assets and 4.2 liabilities into precise time buckets and generation of the Liquidity Profile Page 34

S No Functional Requirements Importance ( / Important / Desirable) 4.3 4.4 4.5 The system should have the ability to define product-wise asset / liability categories, sub-categories and define product hierarchies The system should allow users to define the time buckets to be used for developing the Structural Liquidity profile. The system should allow the user to define bucketing assumptions for each product or asset/liability type 4.6 The system should be capable of accepting bucketing assumptions in the following forms: 4.6.1 Original contractual maturity 4.6.2 Residual maturity 4.6.3 Percentages to each time bucket for each line item in the SLS report 4.6.4 Defeasance Period for trading book investments 4.6.5 Custom expression 4.7 The system should allow the user to develop multiple liquidity profiles with different bucketing assumptions and/or time buckets. 4.8 The system should allow the user to drill down from liquidity profile to the desired granularity (i.e. portfolio level, account level, position level, instrument level, product level, asset class level etc.) 4.9 Post development of the liquidity profile, the system should conduct automatic validation checks to ensure that aggregate asset and liability balances are equal 4.10 The system should be capable of generating the structural liquidity profile in multiple formats given by the Bank in multiple currencies 4.11 The system should be capable of converting the structural liquidity profiles in multiple currencies into one user defined home currency 4.12 The system should be capable of converting the structural liquidity profiles in multiple currencies into one user defined reporting currency 4.13 The system should be capable of aggregating the structural liquidity profiles into one consolidated profile based on user preferences 4.14 The system should be capable of generating the structural liquidity profiles for the Bank and its subsidiaries separately at each of the following levels as per the RBI format 4.14.1 Statement of structural liquidity - Domestic currency, Indian operations 4.14.2 Statement of structural liquidity - Foreign currency, Indian operations (in each currency as well as converted into home currency) 4.14.3 Statement of structural liquidity - Overseas operations country wise (in each currency as well as converted into home currency) Page 35

S No Functional Requirements Importance ( / Important / Desirable) 4.14.4 Statement of structural liquidity - Combined Indian operations Domestic and Foreign Currency 4.14.5 Statement of structural liquidity Consolidated Bank operations 4.14.6 4.14.7 4.15 4.16 4.17 4.18 4.19 4.20 4.21 4.22 4.23 4.24 4.25 Statement of structural liquidity - Currency wise Gap Analysis ( Consolidated for Non-Significant currencies in local currency) Statement of structural liquidity Subsidiaries/ JVs/ Associates Country Wise The system should be capable of generating structural liquidity profiles for user defined future dates based on current balance sheet position. The system should be capable of generating structural liquidity profiles for user defined future dates considering cash flow projections. The system should compute DTL profile and as per RBI guidelines, specific line items should be distributed on the basis of DTL Ratio with a fortnight lag or otherwise The system should compute Minimum CRR Balance, compute excess or shortfall in maintenance and the do appropriate bucketing of Balances The system should compute current SLR, compute the excess/ shortfall and appropriately bucket the Investments as per the Regulatory requirement The system should be able to handle bucketing of Non SLR securities as per regulatory guidelines The system should allow users to allocate amounts in specific bucket(s) through percentage or amount allocation The system should distribute NPA based on its category, i.e., Sub Standard, Doubtful and Loss The system should identify event cash flows and handle the distribution as suggested in the guidelines The system should facilitate distribution of line items based on the product s underlying System should be capable of projecting the Structural Liquidity Profile for future dates based on assumptions provided by the Bank. Structural Liquidity Mismatch Limit Monitoring and Reporting 5.1 The system should be capable of accepting structural liquidity mismatch limits in the form of: 5.1.1 Percentage of total outflow in a time bucket 5.1.2 Cumulative mismatch limits 5.1.3 Individual Bucket wise limits 5.1.4 Custom expression 5.2 The system should be configurable to define the authorities to whom limit breaches must be escalated Page 36

S No 5.3 5.4 5.5 5.6 Functional Requirements The system should automatically alert the user and all predefined authorities in the event of a breach of mismatch limits The system should have the capability to allow scheduling of automatic Structural Liquidity Report generation and mismatch limit verification The system should provide the Structural Liquidity report in the format prescribed by RBI The system should be capable of automatically archiving the Structural Liquidity Reports generated by the user, with appropriate time stamps Importance ( / Important / Desirable) Calculation of Balance Sheet Ratios The system should allow the user to define criteria for following 6.1 asset categories and map the items from the structural liquidity report, balance sheet and inputs from risk systems to each of the defined categories 6.1.1 Liquid Assets 6.1.2 Core Assets 6.1.3 Medium term assets 6.1.4 Long term assets 6.1.5 Any other category required for computation of balance sheet ratios 6.2 The system should allow the user to define criteria for following liability categories and map the items from the structural liquidity report, balance sheet and inputs from risk systems to each of the defined categories 6.2.1 Tier I capital/ Tier II capital/ Total capital 6.2.2 Short term liabilities 6.2.3 Medium term liabilities 6.2.4 Long term liabilities 6.2.5 Core deposits 6.2.6 Wholesale Deposits 6.2.7 Market Borrowings 6.2.8 Any other category 6.3 The system should handle and compute below mentioned ratios as per the formula given by the Bank at the time of implementation: 6.3.1 Bulk Deposit / Total Deposit 6.3.2 Deposits Maturing Within 1 Year / Total Deposits (Considering Renewal) 6.3.3 Deposits Maturing Within 1 Year / Total Deposits (W/o Considering Renewal) 6.3.4 Core Assets / Core Liabilities (As per SLS) Page 37

S No Functional Requirements Importance ( / Important / Desirable) 6.3.5 (Volatile Liabilities - Temporary Assets) / (Earning Assets - Temporary Assets) 6.3.6 Core deposits / Total assets 6.3.7 (Term Loans + Mandatory SLR + Mandatory CRR + Fixed Assets) / Total Assets 6.3.8 (Term Loans + Mandatory SLR + Mandatory CRR + Fixed Assets) / Core Deposits 6.3.9 Temporary Assets / Total Assets 6.3.10 Temporary assets / Volatile liabilities 6.3.11 Volatile liabilities / Total assets 6.3.12 (Customer deposit + Net worth) / (Total assets balance with RBI) 6.3.13 Purchase Funds/ Total Assets 6.3.14 Net loans/ Customer deposits 6.3.15 Time deposits / Total deposits 6.3.16 Prime Assets / Total assets 6.3.17 Liquid assets / Total assets 6.3.18 Short Term Liabilities/ Total assets 6.3.19 Liquid assets / Short Term Liabilities 6.3.20 Funding volatility ratio (Liquid asset / CASA deposits) 6.3.21 Market liabilities / Total assets 6.3.22 Un-availed limits / Total advances 6.3.23 CASA Ratio 6.3.24 Credit-Deposit Ratio 6.3.25 Investment-Deposit Ratio 6.3.26 Rate Non-Sensitive Assets to Total Rate Sensitive Assets (As per IRS) 6.3.27 Customer Deposits to Total Deposits 6.3.28 Customer Deposits to Total Assets 6.3.29 Top 20 Depositors to Total Deposits 6.3.30 Top 50 Depositors to Total Deposits 6.3.31 Top 20 Borrowers to Total Advances 6.3.32 Top 50 Borrowers to Total Advances 6.3.33 Trading Investments to Total Assets 6.3.34 BPLR Linked Advances to Total Advances 6.3.35 Fixed Rate Advances to Total Advances 6.3.36 Base Rate Linked Advances to Total Advances 6.3.37 Below Base Rate Advances to Total Advances 6.3.38 Bank Deposits to Total Deposits 6.3.39 Off-Balance Sheet Exposure to Total Assets Page 38

S No Functional Requirements Importance ( / Important / Desirable) 6.3.40 High Value Deposit to Total Deposit Ratio 6.4 Call money borrowings ratio: 6.4.1 6.4.2 6.4.3 6.4.4 6.4.6 The system should be capable of calculating the ratio of call money borrowings to capital on a daily basis The system should be capable of calculating the running fortnightly average of call money borrowings to capital ratio The system should be capable of monitoring the limits prescribed by RBI for the fortnightly average of the ratio The system should be capable of monitoring the limit prescribed by RBI for the daily value of the ratio The system should alert the user and predefined authorities in the event of breach of the limits defined for the ratio 6.5 Call money lending ratio: 6.5.1 The system should be capable of calculating the ratio of call money lending to capital on a daily basis 6.5.2 6.5.3 6.5.4 6.6 6.7 6.8 6.9 The system should be capable of calculating the running fortnightly average of call money lending to capital ratio The system should be capable of monitoring the limit prescribed by RBI for the daily value of the ratio The system should alert the user and predefined authorities in the event of breach of the limits defined for the ratio The system should be capable of calculating total amounts under each of the categories defined above based on data inputs from balance sheet and/ or structural liquidity statement The system should allow users to define formulas for customized ratios to be calculated on the basis of asset/ liability categories defined in above The system should allow users to set/ edit limits for each of the ratios defined The system should calculate any other ratios defined by the user and identify the breaches and alert the predefined set of users automatically Multiple Bucket Definition The system should allow users to define their own buckets (coexist) 7.1 for Liquidity Risk, Interest Rate Sensitivity, Dynamic Liquidity, MIS Reports, etc. 7.1.1 - As per regulatory 7.1.2 - As per monthly buckets 7.1.3 - Any other user definable bucket Internal MIS reporting 8.1 The system should generate the report for classifying the assets/ Page 39

S No liabilities on the basis of: Functional Requirements Importance ( / Important / Desirable) 8.1.1 Amount range 8.1.2 Interest Rate range 8.1.3 Maturity Range wise Interest Rate Range Wise 8.1.4 Any other category defined by the user 8.1.5 The system should allow user to set/ modify the ranges for generating the report 8.2 The system should allow users to bucket their liquidity and interest rate sensitive position as per regulatory requirement as part of single run/ process 8.3 The system should have capability of reporting Liquidity position without interest for regulatory and with interest for non-regulatory reporting 8.4 The system should allow users to view Total Inflow, Total Outflow, Gap, Cumulative Gap and Cumulative Gap % for period range defined by user The system should allow users to compare any past 2 SLS 8.5 /IRST/IRSD/DLS reports and provide line item wise increase/decrease in Inflows/ Outflows and final mis-match 8.6 The system should facilitate users with distribution on the basis of contractual maturity across all formats mentioned in previous section 8.7 For the overseas branch, system should generate following reports: 8.7.1 Liquidity Ratio 8.7.2 Maturity Mis-Match Report - Currency Wise 8.7.3 Cash Flow analysis 8.7.4 Loan to Deposit Ratio - Currency Wise 8.7.5 Concentration Report - Short Term Liquidity Mis-Match report 8.8 System should be able to generate the following reports for domestic operations as well as for the Bank as a whole : Interest Rate Wise Maturity Pattern of Bulk Term Deposits 8.8.1 (Contractual Maturity) Interest Rate Wise Maturity Pattern of Bulk Term Deposits 8.8.2 (Residual Maturity) Interest Rate Wise Maturity Pattern of Retail Term Deposits 8.8.3 (Contractual Maturity) Interest Rate Wise Maturity Pattern of Retail Term Deposits 8.8.4 (Residual Maturity) Interest Rate Wise Maturity Pattern of Total Term Deposits - 8.8.5 Excl. CDs (Contractual Maturity) Interest Rate Wise Maturity Pattern of Total Term Deposits - 8.8.6 Excel.CDs (Residual Maturity) Interest Rate Wise Maturity Pattern of Certificate of Deposits 8.8.7 (Contractual Maturity) Page 40

S No Functional Requirements Importance ( / Important / Desirable) Interest Rate Wise Maturity Pattern of Certificate of Deposits 8.8.8 (Residual Maturity) Monthly Outstanding with Weighted Average Cost (Retail & Bulk 8.8.9 Term Deposits) Monthly Outstanding with Weighted Average Cost - Certificate of 8.8.10 Deposits Month-Wise Maturity Pattern with Weighted Average Cost - 8.8.11 Retail Term Deposits Month-Wise Maturity Pattern with Weighted Average Cost - Bulk 8.8.12 Term Deposits Month-Wise Maturity Pattern with Weighted Average Cost - 8.8.13 Certificate of Deposits Date-Wise Maturity Pattern - Retail Term Deposits (between 8.8.14 'From' and 'To' Dates) Date-Wise Maturity Pattern - Bulk Term Deposits (between 8.8.15 'From' and 'To' Dates) Date-Wise Maturity Pattern - Certificate of Deposits (between 8.8.16 'From' and 'To' Dates) Date-Wise Maturity Pattern of Bulk Deposits With Account Level 8.8.17 Details (between 'From' and 'To' Dates) Deal Wise Maturity Report of CDs (i.e. CDs Maturing between 8.8.18 'From' and 'To' Dates) 8.8.19 Money Market O/s Position Day-Wise Money Market Borrowing/Lending Position (Instrument 8.8.20 Wise) (Between 'From' & 'To' Dates) 8.8.21 Asset Class Wise Investments O/s & Sensitivities 8.8.22 SLR/NSLR Wise Investment Classification & O/s Investment Portfolio Wise (i.e. HTM, AFS, HFT) O/s & 8.8.23 Sensitivities 8.8.24 Rating-Grade Wise Investments O/s 8.8.25 Rating-Grade Wise Advances O/s A/c Wise Inflow Report of Bulk Deposits (i.e. Bulk Deposit A/cs 8.8.26 opened between 'From' and 'To' Dates) Deal Wise Inflow Report of CDs (i.e. CDs issued between 'From' 8.8.27 and 'To' Dates) A/c Wise Maturity of Bulk Deposits (i.e. Bulk Deposit Maturing 8.8.28 between 'From' and 'To' Dates) 8.9 Actual interest paid / received (in %) on borrowings and advances respectively as compared to the total weighted average interest Important Sourcing Required Data and Projections for Dynamic Liquidity 9.1 The system should allow users to define the product / instrument level at which the source data and projections must be provided as inputs Page 41

S No Functional Requirements Importance ( / Important / Desirable) 9.2 9.3 9.4 9.5 The system should allow users to define the time buckets to be used for developing the Dynamic Liquidity profile The system should be capable of extracting the actual inflows and outflows for the relevant time buckets from the Structural Liquidity Report The system should have the capability to source projections provided by the business units through an MS Excel file upload/ manual input The system should be capable of accepting projections from business units at each of the following levels: 9.5.1 Line of Business 9.5.2 General Ledger 9.5.3 Line Item as per Dynamic Liquidity format of RBI 9.5.4 Product / instrument level 9.5.5 Asset class level 9.6 The system should be capable of accepting projections both at each time bucket level and at an aggregate level. 9.7 The system should be capable of sourcing projections with following parameters: 9.7.1 Origination date 9.7.2 Projection Amount/ Total Amount 9.7.3 Maturity Date/ Tenure 9.7.4 Amortization schedule/ parameter for amortisation schedule 9.7.5 Interest rate 9.8 The system should have the capability to allow users to manually enter projection data at any desired granularity. 9.9 The system should be capable of accepting projections in the form of: 9.9.1 Absolute figures 9.9.2 Percentage 9.9.3 Custom expressions 9.10 The system should be capable of accepting the projections in multiple currencies 9.11 The system should be capable of accepting the projections from each jurisdiction/ overseas branch of the Bank separately 10.1 10.2 Development of Dynamic Liquidity Profile The system should integrate the projections with the structural liquidity profile to generate the dynamic liquidity profile as per RBI format and internal MIS The system should allow the user to define rules based on which aggregated projections will be segregated into different time Page 42

S No buckets and/or line items Functional Requirements Importance ( / Important / Desirable) 10.3 The system should have the ability to define product-wise asset / liability categories, sub-categories and define product hierarchies 10.4 The system should allow the user to define bucketing assumptions for each product or asset/liability type as per RBI or internal rules of the Bank 10.5 The system should be capable of accepting bucketing assumptions in the following forms: 10.5.1 Original contractual maturity 10.5.2 Residual maturity 10.5.3 Percentages to each time bucket for each asset class 10.5.4 Custom expression 10.6 The system should allow the user to develop multiple dynamic liquidity profiles with different bucketing assumptions, time buckets and projections 10.7 The system should allow the user to generate liquidity profiles at each of the following levels: 10.7.1 Business unit or Zone or Branch level 10.7.2 Overall Bank level The system should allow the user to drill down the dynamic 10.8 liquidity profile to the desired granularity (i.e. position level, product level, GL Level etc.) 10.9 The system should be capable of generating the dynamic liquidity profile in multiple currencies 10.10 The system should be capable of converting the dynamic liquidity profiles in multiple currencies in one user defined home currency 10.11 10.12 10.13 10.14 10.15 10.16 10.17 The system should be capable of generating the dynamic liquidity profile for different zones/ overseas branch separately The system should allow users to compute consolidated as well as currency wise cost to close using borrowing as well as asset liquidation on dynamic gaps The system should be capable of consolidating the multiple dynamic liquidity profiles in the same currency as per user preference The system should allow users to facilitate projections for user define horizon period. E.g.: 3 months, 12 months, 3 years, 5 years etc. System should be capable of computing impact on Liquidity and Bank's interest rate sensitivity for longer term The system should be capable of computing NII/ NIM on a 1 year rolling basis The system should be able to compute revised NII/ NIM on the basis of user defined yield curve across interest sensitive assets/ liabilities or shift from the current curve Page 43

10.18 S No Functional Requirements System should also allow users to define projections on a quarterly basis and revise them every month. Importance ( / Important / Desirable) Dynamic liquidity mismatch limit monitoring and reporting 11.1 The system should be capable of accepting dynamic liquidity mismatch limits in form of: 11.1.1 Absolute figures 11.1.2 Percentage of total outflow in a time bucket 11.1.3 Cumulative mismatch limits 11.1.4 Custom expression 11.2 The system should be configurable to define the authorities to whom limit breaches must be escalated 11.3 11.4 11.5 11.6 The system should automatically alert the user and all predefined authorities in the event of a breach of mismatch limits The system should have the capability to allow scheduling of automatic Dynamic Liquidity Report generation and mismatch limit verification The system should provide the Dynamic Liquidity report in the format prescribed by RBI The system should be capable of automatically archiving the Dynamic Liquidity Reports generated by the user, with appropriate time stamps Dynamic liquidity report: Back testing 12.1 The system should be capable of conducting a back testing of dynamic liquidity reports by comparing archived dynamic liquidity report as on a date with structural liquidity report on the target horizon date 12.2 The system should be capable of calculating the differences in projected values in dynamic liquidity report and actual values in structural liquidity report at each of the following levels: 12.2.1 Time bucket 12.2.2 Product level 12.2.3 GL Level 12.3 The system should be capable of identifying the mismatch in projected and actual values in following terms 12.3.1 Absolute figures 12.3.2 Percentage terms Development of Interest Rate Sensitivity Profile - Traditional Gap Approach 13.1 The system should be capable of generating the Interest rate sensitivity profile as and when required Page 44

13.2 13.3 13.4 13.5 13.6 S No Functional Requirements The system should support the classification of assets and liabilities into precise time buckets and generation of the Interest Rate Sensitivity Profile on a branch-wise and region-wise basis The system should have the ability to define product-wise asset / liability categories, sub-categories and define product hierarchies The system should allow users to define the time buckets to be used for developing the Interest Rate Sensitivity profile. The system should allow the user to define bucketing assumptions for the repricing cash flows occurring for each product or asset / liability type. The system should be capable of accepting bucketing assumptions for the repricing cash flows in the following forms: Importance ( / Important / Desirable) 13.6.1 All outstanding balances as per re-pricing tenor 13.6.2 As a percentage of total outstanding to be assigned to each time bucket, at a product level or an asset class level 13.6.3 Custom expression 13.7 The system should ensure that when outstanding balances are bucketed as per repricing tenor, cash flows occurring prior to the repricing bucket are bucketed as per residual maturity 13.8 The system should allow the user to develop multiple interest rate sensitivity profiles with different bucketing assumptions and/or time buckets 13.9 The system should allow the user to generate interest rate sensitivity profiles at any of the following levels: 13.9.1 Product level 13.9.2 Portfolio Level 13.9.3 Book Wise (Banking Book/ Trading Book Level) 13.9.4 Business unit level 13.9.5 Overall Bank level 13.9.6 Any other level, based on custom rules 13.20 13.21 13.22 13.23 13.24 The system should be capable of computing Earnings at Risk and Impact on NII based on the interest rate sensitivity profile. The system should allow the user to drill down from the interest rate sensitivity profile to the desired granularity (i.e. position level, product level, asset class level, account level etc.) The system should allow user to define/ change the home currency. The system should also be capable of converting interest rate sensitivity profiles generated from one currency into user defined home currency. The system should be capable of aggregating selected interest rate sensitivity profiles in the same currency into one consolidated profile. Page 45

S No Functional Requirements Importance ( / Important / Desirable) 13.25 Post development of the Interest rate profile, the system should conduct automatic validation checks to ensure that aggregate asset and liability balances are equal 13.26 The system should be capable of generating the Interest rate sensitivity profiles for the Bank and its subsidiaries separately at each of the following levels 13.26.1 Indian operations- Domestic currency 13.26.2 Indian operations- Foreign currency (Separately for Significant and Residual Currencies) 13.26.3 Consolidated Indian operations (home currency) 13.26.4 Overseas operations country wise (in each currency converted into home currency) 13.26.5 Consolidated operations at bank level (reporting currency) 13.27 The system should be capable of generating interest rate sensitivity profiles for user defined future dates based on current balance sheet position. 13.28 The system should be capable of generating interest rate sensitivity profiles for user defined future dates considering cash flow projections. 13.29 The system should be flexible to use different basis for distribution in SLS and IRS. For e.g.: Small Deposit in SLS needs to be distributed on the basis of residual maturity in SLS and on the basis of behavioural in IRS Development of Interest Rate Sensitivity Profile- Duration Gap Approach 14 14.1 14.2 14.3 14.4 14.5 14.6 14.7 The system should allow user to define customized curves as coupon curves and yield curves The system should be capable of accepting the data feeds from external agencies such as FIMMDA, Reuters, Bloomberg, flat files and to be used as coupon and yield curves The system should have the ability to define product-wise asset/ liability categories, sub-categories and define product hierarchies The system should allow user to map the product categories/ sub categories/ individual positions to coupon rate curves/ yield rate curves defined in the system The system should allow user to define coupon and yield rates at individual cash flow level The system should be capable of determining the modified duration of assets and liabilities at a position level The system should be capable of calculating the weighted average modified duration for product category/ sub categories defined by the user The system should allow the user to develop multiple interest rate sensitivity profiles with different bucketing assumptions and/or time buckets Page 46

S No Functional Requirements Importance ( / Important / Desirable) 14.8 The system should allow the user to generate interest rate sensitivity profiles at any of the following levels: 14.8.1 - Product / instrument level 14.8.2 - Sub-unit level 14.8.3 - Business unit level 14.8.4 - Overall Bank level 14.8.5 - Any other level, based on custom rules 14.9 The system should allow the user to generate duration gap analysis profiles at any of the following levels: 14.9 - Product / instrument level 14.9 - Sub-unit level 14.9 - Business unit level 14.9 - Overall Bank level 14.9 - Any other level, based on custom rules 14.10 The system should be capable of computing modified duration gap and Impact on MVE based on the interest rate sensitivity profile as per the requirement of RBI. 14.11 The system should allow the user to drill down from the interest rate sensitivity profile to the desired granularity (i.e. position level, instrument level, product level, asset class level) 14.12 The system should allow user to define/ change the home currency. 14.13 The system should also be capable of converting interest rate sensitivity profiles generated in other currencies into one user defined home currency. 14.14 The system should be capable of aggregating selected interest rate sensitivity profiles in the same currency into one consolidated profile. 14.15 Post development of the interest rate sensitivity profile under DGA, the system should conduct automatic validation checks to ensure that aggregate asset and liability balances are equal 14.16 System should compute month wise EVE, Impact on NII with change in 100,200, 300bps, Modified Duration Gap and Market Value of Equity with a comparison of change in NII due to parallel shift by 100, 200, 300 bps 14.17 The system should be capable of generating interest rate sensitivity profiles for user defined future dates based on current balance sheet position. Interest rate sensitivity mismatch limit monitoring and reporting 15.1 The system should be capable of accepting interest rate sensitivity mismatch limits in form of: 15.1.1 Percentage of total outflow in a time bucket 15.1.2 Net mismatch limits as a percentage of Bucket RSA/ Equity/ Page 47

S No Total assets/ Total RSA Functional Requirements Importance ( / Important / Desirable) 15.1.3 Cumulative mismatch limits 15.1.4 EaR limits 15.1.5 MVE impact limits 15.1.6 Duration gap limits 15.2 The system should be configurable to define the authorities to whom limit breaches must be escalated 15.3 15.4 15.5 The system should automatically alert the user and all predefined authorities in the event of a breach of mismatch limits The system should have the capability to allow scheduling of automatic Interest Rate Sensitivity Report generation and mismatch limit verification The system should be capable of automatically archiving the Interest Rate Sensitivity Reports generated by the user with appropriate time stamps> User should be able to retrieve past reports (all) using the front end Other regulatory requirements The system should be able to segregate the total investment 16.1 portfolio in following categories and accordingly bucket the sensitivity: 16.1.1 - Available for Sale ('AFS') 16.1.2 - Held For Trading ('HFT') 16.1.3 - Held Till Maturity ('HTM') 16.1.4 - Any other user defined category 16.2 The system should be capable of generating the report having following components for the three sub-portfolios mentioned above separately as well as consolidated: 16.2.1 - Book value 16.2.2 - Realisable value 16.2.3 - PV01 16.2.4 - Modified duration 16.2.5 - Outstanding amount 16.3 The system should be able to generate report for DGA as per requirement of RBI 16.4 The system should allow users to compute product wise report on Cost of Fund/ Yield on Asset 16.5 The system should have provisions to compute NII and NIM Computation 16.6 The system should have pre built models for predicting Interest Rates and thereby compute Interest Income, Interest Expenses and the NII Page 48

S No Functional Requirements Importance ( / Important / Desirable) Extraction of transaction data for Behavioural analysis The system should interface with all operational systems 17.1 currently being used by the Bank's business units to extract end of day portfolio level/account level data for following items from each source system 17.1.1 Current Accounts 17.1.2 Savings deposits 17.1.3 Cash Credit ('CC') 17.1.4 Overdrafts ('OD') 17.1.5 Demand loans ('DL') 17.1.6 Un-availed limits of CC/OD/DL 17.1.7 Bills payable 17.1.8 Premature withdrawal of retail term deposits 17.1.9 Prepaid term loans 17.1.10 Renewed retail term deposits 17.1.11 Total term loans outstanding 17.1.12 Total deposits due for maturity 17.1.13 Total deposits outstanding 17.1.15 Devolvement of LCs/ Invoked BGs 17.1.16 Premature withdrawal of Bulk term deposits 17.1.17 Renewed wholesale term deposits 17.1.18 Renewed WCDL 17.1.19 Any other non-maturity products 17.1.20 Any other products containing embedded options Development of behavioural pattern results The system should be capable of performing the statistical 18.1 analysis on the archived portfolio level/account level data, to determine the core and volatile portions for following products, currency wise: 18.1.1 Current Accounts 18.1.2 Savings deposits 18.1.3 Drawn portions of CC 18.1.4 Drawn portions of OD 18.1.5 Drawn portions of DL 18.1.6 Bills payable 18.1.7 Any other non-maturity products 18.1.8 EEFC 18.1.9 RFC Page 49

S No Functional Requirements Importance ( / Important / Desirable) 18.2 The system should be capable of performing the statistical analysis on the archived portfolio level/account level data, to determine the behavioural pattern of following products, currency wise: 18.2.1 Pre mature withdrawal of retail term deposits 18.2.2 Prepayment of term loans 18.2.3 Rollover pattern of retail term deposits 18.2.4 Invocation/ Devolvement pattern of LCs/ BGs 18.2.5 Pre mature withdrawal of wholesale term deposits 18.2.6 Rollover pattern of wholesale term deposits 18.2.7 Rollover pattern of WCDL 18.2.8 Any other products containing embedded options 18.2.9 18.2.10 18.2.11 18.2.12 18.2.13 18.2.14 18.2.15 18.3 18.4 18.5 18.6 The system should allow user to select the time interval for which the statistical analysis is to be performed The system should make available option of results of behavioural studies to automatically use them for preparation of structural liquidity statement and interest rate sensitivity statement The system should be capable of storing the results of past behavioural studies The system should allow user to schedule the statistical analysis to be performed The behavioural study reports should be generated as and when required The system should enable the back testing of results generated by comparing the forecasted percentages vis-à-vis actual figures from balance sheet For Back testing, the system should allow users to select the period on which Back Testing needs to be applied The system should interface with all operational systems currently being used by the Bank, to extract transaction data from each source system in respective currencies The system should be scalable and allow the interfacing of other systems as and when such systems are procured/implemented As a back-stop measure, the system should support the manual upload of transaction data from various operational systems in formats provided by the Bank System should have the capability to re-plot line items and regenerate historical reports/statements based on changes in assumptions plotting of line items. Stress Testing Page 50

S No Functional Requirements Importance ( / Important / Desirable) 19.1 Users, at the minimum, should be able to define scenarios for Liquidity Risk under 3 categories- Bank Specific - Market Specific - Combined 19.2 Line item wise liquidity profile at a product / business unit level/ branch wise/ consolidated level 19.3 The system should allow the user to develop and save scenarios based on any or all of the following: 19.3.1 Redefine haircuts on investment portfolio 19.3.2 Increase/ decrease Prepayment/ Rollover of Loans/ Deposits 19.3.3 Re-define current market rates and review impact on market value of assets. Actual market rates should remain intact 19.3.4 Allow users to simulate scenario of selling long term investments 19.3.5 System should allow users to simulate fall in Market Value of derivatives like Options and Swaps and view their impact on SLS/ IRS reports 19.3.6 It should be configurable for users to define any other scenario for stressing liquidity and interest rates 19.4 The system should be able to build following stress scenarios and corresponding stress levels 19.4.1 Scenarios to include significant strategic or reputational risk in particular for significant business lines 19.4.2 19.4.3 19.4.4 19.4.5 19.4.6 19.4.7 19.5 Scenarios to include, where relevant, an episode of financial market turbulence or a shock to market liquidity; Scenarios under which capital might not be freely transferable within banking groups in periods of severe downturn or extended market disruption; Scenarios under which a crisis impairs the ability of even very healthy banks to raise funds at reasonable cost Scenarios under which model-embedded statistical relationships break down Scenarios under which risk characteristics of new products projected on the basis of limited historical data are challenged Scenarios to include simultaneous pressures in funding and asset markets, and the impact of a reduction in market liquidity on exposure valuation, etc. System should allow users to identify components of Liquidity Buffer at Product and/ or GL level in the system 19.6 Based on the identification, system should separate the items identified under Liquidity Buffer from the user selected SLS statement and recomputed the Liquidity Gaps in the selected Gap Report 19.7 System should compute the Liquidity Buffer 19.8 System should compute Survival Horizon Period Page 51

19.9 19.10 19.11 19.12 19.13 S No Functional Requirements The system should allow the user to specify the amount of inflows or outflows in each time bucket to be considered for stress testing The system should be able to compute consolidated as well as currency wise "Cost to Close", the static/ dynamic liquidity gaps using stressed scenarios The system should take in to account the cost of additional borrowing as well as cost of asset liquidation to compute "Cost to Close" along with the impact on capital System should allow users to compute liquidity and interest rate stress on the dynamic Balance Sheet The system should allow the user to determine the impact of the following movements in the yield curve on the NII and EVE: Importance ( / Important / Desirable) 19.13.1 Parallel movements 19.13.2 Non-parallel movements 19.13.3 Inversion of curve 19.14 The system should allow user to develop scenarios in multiple currencies separately 19.15 The system should have provisions to review impact on Interest Income/ Interest Expense and NII across Rate Sensitive Asset and Rate Sensitive Liabilities due to stress in yield curve on immediate basis 19.16 The system should have provisions to review impact on Interest Income/ Interest Expense and NII across Rate Sensitive Asset and Rate Sensitive Liabilities due to stress in yield curve at a later date 19.17 The system should also be able to evaluate the Income/ expense/ NII/ NII increase or decrease in percentages due to the above mentioned change in yield curve as part of the same report 19.18 System should provide a front screen to capture Net Worth of the Bank and Compute the NII as a percentage of Net Worth under each of the scenario 19.19 The system should be capable of allowing the user to retrieve saved scenarios and specify the portfolio on which to conduct the stress test / simulation. 19.20 The system should allow the user to determine stressed liquidity ratios such as the Liquidity Coverage Ratio (LCR) and the Net Stable Funding Ratio (NSFR) 19.21 The system should compute the impact for all stress levels defined under Basel III requirement and as per guidelines released by RBI 19.22 The system should allow the user to manually input the CRAR and Tier I and Tier II capital details and RWA under Credit, Market and Operational Risk 19.23 System should allow users to view the impact of stress on the CRAR 19.24 System should be able to perform stress levels under 'reverse Page 52

19.25 S No stress testing' Functional Requirements System should be capable of re-plotting line items and regenerating reports/statements based on changes in inputs such as GL Balance, percentage in each bucket, and any other parameters used in such reports by way of simulation. Importance ( / Important / Desirable) Report generation 20.1 The system should be capable of archiving the computed Stress Test Results, with appropriate time stamps and currencies 20.2 The system should be configurable to define the authorities to whom the computed Stress Test Results must be circulated and the frequency of circulation. 20.3 The system should support intraday liquidity reporting Calculation of Liquidity Coverage Ratio 21.1 The system should be capable of computing LCR in accordance with RBI guideline and in the format specified by RBI 21.2 The system should be capable of calculating the total high quality liquid assets available by summing up Level 1 and Level 2A, 2B high quality liquid assets 21.3 The system should be capable of identifying Level 1 high quality liquid assets at position level based on: 21.3.1 Asset class 21.3.2 Issuer 21.3.3 Any other criteria 21.3.4 21.4 The system should be capable of applying adjustments to the Level 1 high quality liquid assets as per the RBI guidelines The system should be capable of identifying Level 2A, 2B high quality liquid assets at position level based on: 21.4.1 Asset class 21.4.2 Issuer 21.4.3 Risk Weights 21.4.4 Any other criteria 21.5 21.6 21.7 21.8 The system should be capable of applying haircuts to Level 2 high quality liquid assets as per the RBI guidelines The system should be capable of applying adjustments to the Level 2 high quality liquid assets as per the RBI guidelines The system should ensure that proportion of Level 2 liquid assets after applying the haircut remains within the regulatory limit prescribed The system should allow users to list Investments in securities issued by 0% risk weighted foreign sovereigns Page 53

21.9 21.10 21.11 21.12 21.13 S No Functional Requirements The system should allow users to list Investment in securities representing claims on or claims guaranteed by sovereigns, PSEs or multilateral development banks that are assigned a 20% risk-weight The system should be capable of calculating net outflows in the next 30 days based on the position level cash flow data The system should allow user to enter the internal as well as regulatory limits for liquidity coverage ratio The system should be capable of calculating the liquidity coverage ratio and alert the user and pre-defined authorities in event of breach of regulatory/ internal limit The system should be capable of calculating the liquidity coverage ratio for significant multiple currencies separately Importance ( / Important / Desirable) 21.14 The system should be capable of calculating the liquidity coverage ratio separately for domestic operations, each overseas branch and at a consolidated level 21.15 The system should be able to use the run off factor Calculation of Net Stable Funding Ratio 22.1 22.2 22.3 22.4 22.5 22.6 22.7 22.8 22.9 22.10 The system should be capable of computing LCR in accordance with RBI guideline and in the format specified by RBI The system should be capable of calculating available stable funding based on position level cash flow data available for liabilities The system should be capable of applying available stable funding factor as per the RBI guidelines to each of the product category included in the calculation of available stable funding The system should be capable of calculating the required stable funding based on position level cash flow data available for assets The system should be capable of applying required stable funding factor as per the RBI guidelines to each of the product category included in the calculation of required stable funding The system should be capable of identifying the required stable finding factor to be applied to off balance sheet exposures based on the results of behavioural studies conducted in the system The system should allow user to enter the internal limit for net stable funding ratio The system should be capable of calculating the net stable funding ratio and alert the user and pre-defined authorities in event of breach of regulatory/ internal limit The system should be capable of calculating the net stable funding ratio for significant multiple currencies separately The system should be capable of calculating the net stable funding ratio separately for each overseas branch and at a consolidated level also. Page 54

S No Functional Requirements Importance ( / Important / Desirable) Statement of funding concentration 23.1 The system should be capable of identifying and listing counterparties contributing more than user defined threshold limit for following categories using position level data 23.1.1 Deposits 23.1.2 Borrowings 23.1.3 Any other user defined category 23.2 The system should be capable of identifying and listing top 20 depositors describing details of following types of deposits 23.2.1 Current deposits 23.2.2 Savings deposits 23.2.3 Term deposits 23.3 The system should be capable of identifying the top 20 borrowings 23.4 The system should be capable of identifying significant products/ instrument 23.5 23.6 23.7 23.8 The system should be capable of identifying and listing down the details of significant funding sources through securitization The system should be capable of generating the statement in multiple currencies separately The system should be capable of significant borrowings and deposits The system should be capable of generating the statement for each overseas branch and at a consolidated level also. 23.9 The system should be capable of identifying and listing top 23.10 The system should compute funding concentration in the format prescribed by RBI Statement of Available Unencumbered Assets 24.1 24.2 24.3 The system should be capable of identifying the unencumbered assets from position level data The system should be capable of identifying the haircut required by the market for collateralization of unencumbered asset from position level data The system should be capable of identifying the unencumbered assets and the haircut necessary in multiple geographies and multiple significant currencies separately from position level data Statement on other information on liquidity 25.1 The system should be capable of identifying the movement in equity prices for the period of one month based on data fed from external market sources Page 55

25.2 S No Functional Requirements The system should be capable of extracting the interest rates and tenors for bond and certificate of deposits issued by the bank for last one month based on position level data Importance ( / Important / Desirable) Reporting Requirements 26.1 The system should allow the user to generate currency wise as well consolidated SLS/ IRS/ DGA profiles at any of the following levels: 26.1.1 - Product level 26.1.2 - Portfolio Level 26.1.3 - Branch level 26.1.4 - Book Wise (Banking Book/ Trading Book Level) 26.1.5 - Region / Zone Level 26.1.6 - Business unit level 26.1.7 - Overall Bank level 26.1.8 - Any other level, based on custom rules 26.2 26.3 26.4 26.5 26.6 26.7 The system should allow users to view limits and display exceptions when compared with limits/ benchmarks The system should be capable of generating the liquidity coverage ratio report for significant currencies and multiple geographies as and when required in the format prescribed by RBI The system should be capable of generating the net stable funding ratio report as and when required in the format prescribed by RBI The system should be capable of generating the statement of funding concentration as and when required in the format prescribed by RBI The system should be capable of generating the statement of unencumbered assets as and when required in a format prescribed by RBI The system should be capable of generating the statement on other information on liquidity as and when required in format prescribed by RBI Support for System Based Analysis 27.1 The system should support the following analysis and computations: 27.1.1 SLR calculation with a customizable bucket-wise breakup 27.1.2 Duration analysis Important 27.1.3 Variance analysis between annual operating plan vs. actual performance at a business unit level 27.2 The system should be capable of conducting the following analysis for the purpose of management reporting: Important Page 56

S No Functional Requirements Importance ( / Important / Desirable) 27.2.1 Net interest income 27.2.2 Economic Value of Equity Important 27.3 The system should allow users to perform back dated analysis on all/ any reports in this RFP 27.4 The system should allow users to review/ generate reports on post audit data on all/ any reports in this RFP Regulatory Reporting 28.1 The system, at the minimum, should support the generation of the following reports/statements in the regulatory/statutory prescribed formats: 28.1.1 Statement of structural liquidity at following levels: 28.1.1.1 Statement of structural liquidity - Domestic currency, Indian operations Statement of structural liquidity - Foreign currency, Indian 28.1.1.2 operations (in each currency as well as converted into home currency) 28.1.1.3 Statement of structural liquidity - Overseas operations country wise (in each currency as well as converted into home currency) 28.1.1.4 Statement of structural liquidity - Combined Indian operations Domestic and Foreign Currency 28.1.1.5 Statement of structural liquidity Consolidated Bank operations 28.1.1.6 Statement of structural liquidity - Currency wise Gap Analysis ( Consolidated for Non-Significant currencies in single currency) 28.1.2 Statement of short term dynamic liquidity at following levels: 28.1.2.1 Statement of short term dynamic liquidity - Domestic operations 28.1.2.2 Statement of short term dynamic liquidity - Overseas operations (Jurisdiction wise) 28.1.2.3 Statement of short term dynamic liquidity - Overseas operations (Overall overseas positions) 28.1.3.1 Statement of interest rate sensitivity - Traditional Gap Approach (Currency wise) 28.1.3.2. Statement of Modified Duration Gap (Currency wise) 28.1.3.3 Report in computation of impact on MVE 28.1.4.1 Statement on Liquidity Coverage Ratio (Consolidated level) 28.1.4.2 Statement on Liquidity Coverage Ratio (Significant currency wise) 28.1.4.3 Statement on Net Stable Funding Ratio 28.1.4.4 Statement of Funding Concentration 28.1.4.5 Statement of Available Unencumbered Assets 28.1.4.6 Statement on Other Information on Liquidity 28.1.4.67 Statement of balance sheet ratios as per Basel III guidelines stipulated by RBI Page 57

S No Functional Requirements Importance ( / Important / Desirable) 28.2 The system should support the generation of the following regulatory-statutory reports for disclosure purpose: 28.2.1 Liquidity Coverage Ratio (in the RBI prescribed disclosure format) 28.2.2 Maturity Pattern of Certain Items of Assets & Liabilities 28.3 Any other regulatory/statutory ALM reports in the prescribed formats/ Report Customization 29.1 29.2 29.3 29.4 29.5 29.6 29.7 29.8 29.9 29.10 29.11 The system should have a report builder tool for customization and generation of reports. The system should generate reports based on available data as per any user defined format. The system should be flexible in allowing users to specify the exact layout of the required report including location of fields, header, footer, page numbering, title etc. The system should be flexible in allowing users to define structures and fields of each report by selecting fields from databases of their choice. The system should allow reports to be exported into Microsoft Excel, Adobe PDF format and other databases. The system should allow users to print reports directly from the system. The system should allow users to save reports to a disc in a noneditable as well as an editable format. The system should provide context sensitive help to guide users to form the reports required by them. The system should have a report writing wizard that provides users with step by step menus and allows them to draw up reports in the required format. The system should allow users to present outputs from reports in the form of graphs, charts and other graphic representation The system should allow for filtering and sorting of data in reports. Important Important Important Important Important Scheduling of Reports 30.1 30.2 30.3 The system should allow for generation of pre-defined end-ofday, end of week and end-of month reports. Pre-defined reports should be generated with a minimum of user involvement. The system should have the capability to assign frequency of generation to each report, including but not limited to: 30.3.1 Daily 30.3.2 Weekly 30.3.3 Fortnightly Page 58

S No Functional Requirements Importance ( / Important / Desirable) 30.3.4 Monthly 30.3.5 Quarterly 30.3.6 Half-yearly 30.3.7 Annual 30.3.8 Any other frequency 30.4 The system should have the ability to define a schedule for reports. 30.4.1 Any exception, data non availability, exception caused due to breach of limits should lead trigger automatic sending reports to users as defined by the System Admin 30.4.2 The system should allow defining the users to whom reports are to be automatically sent. Archiving of Reports 31.1 The system should allow for archiving of reports in the following relevant formats: 31.1.1 Adobe PDF 31.1.2 Microsoft Excel 31.1.3 Microsoft Word 31.1.4 Microsoft Access 31.1.5 Comma separated values (.CSV) 31.2 The system should allow for archiving of circulars, notifications and other communication received from regulators. 31.3 The system should archive historical rates extracted from market information systems 31.4 The system should allow for archiving of historical reports. 31.5 Archiving of reports should be possible in a pre-defined format to facilitate ease of retrieval. 31.6 The system should have a provision in the front end to archive any of the past reports generated by the system Page 59

5.2 Technical Requirement Sl. No Requirement 1 Multiple Currency Support 1.1 The system should support multiple currencies including USD, INR, EUR, AUD, CHF, JPY, GBP etc. The system should also be scalable so as to support other currencies as and when they get added. 2 Multiple entity support 2.1 The system should provide full support for multiple organizational levels and relationships, including regional offices, branches, subsidiaries, and within each hierarchy the system should also support multiple levels of hierarchy. Importance ( / Important / Desirable) 2.2 The system should support Asset Liability Management at each of the following levels: 2.3 Multiple Country 2.4 Multiple Currency 2.5 Multiple Business units 2.6 Multiple Branches 2.7 Multiple Products 2.8 Multiple Product Categories 2.9 Multiple Customer Categories 3 Data Validation for Manual Inputs 3.1 The system should perform logical checks on all manual input fields. 3.2 The system should provide intelligent edit error messaging to assist correction and re-entry of data. N/A Important 3.3 The system should flag the entries that cause edit errors. The system should have the ability to flag specific data for 3.4 investigation where the data does not fit in a reasonable range or is Important incomplete. 3.5 The system should be capable of allowing the user to over-ride edited errors and should generate the log of such cases. 3.6 The system should support maker-checker work steps for every manual input or manual upload of data. 4 Day Count, Business Day and Holiday Conventions 4.1 The system should handle all types of day count basis including 30/360, Actual/360, Actual/365, Actual/Actual, 30E/360 etc. Important 4.2 The system should support internationally accepted business day conventions such as following, modified following, preceding, next month, this month, average of the month etc. Page 60

Sl. No 4.3 4.4 4.5 4.6 4.7 4.8 Requirement The system should load calendar schedules from external sources including but not limited to SWIFT, International Holiday schedule and Bloomberg holiday schedule etc. The system should allow calendar schedules to be set by users directly in the system and/ or through interfaces / patch updates. The system should allow for multiple holiday tables for each currency and country. The system should allow users to edit and override global calendar and holiday tables. The system should move value dates based on holidays declared at the last moment. The system should model cash flows and interest accruals based on holiday calendar and standard day roll conventions. 5 Currency Translation 5.1 The system should convert between currencies without converting to the home currency as an interim step in the process using externally fed/ user defined exchange rates 6 Product Set-up 6.1 The system should allow for the creation of products, sub-products and corresponding codes in line with those present on the operational systems. 7 Ease of Use 7.1 7.2 7.3 The system should support quick and easy navigation e.g. provision of function keys/hot keys with drop-down help. The system should provide print facility i.e. print to file, print screen, print to printer etc. The system should have a user friendly menu structure to lessen the learning curve for the user 8 User Interfaces 8.1 8.2 The system should provide a consistent and user-friendly Microsoft Windows based interface. The system should generate intelligent error messages based on predefined parameters. Importance ( / Important / Desirable) Important Important Important Important Important 8.3 The system should provide online and offline context sensitive help. 8.4 8.5 8.6 8.7 8.8 The system should provide users the ability to define menus and shortcuts. The system should interface with mail clients and corporate instant messenger service to generate notifications and auto-mailers. Specific reports should be made available in a graphical mode. This should be configurable. Report Creation utility should be provided for the user to generate new reports. The system should provide user-friendly design, short-cuts, smart tags and other productivity features Desirable Important Page 61

Sl. No Requirement Importance ( / Important / Desirable) 8.9 The system should allow the user to filter, sort and assimilate data. 9 Help Facility 9.1 9.2 9.3 9.4 9.5 9.6 The system should provide Help facility which is context sensitive at a field, screen level etc. The Help facility should explain probable causes of errors and possible solutions. Manual documentation i.e. user manuals, system management manuals, technical manual, training manuals etc. should be provided. The text content in help messages and error alerts should be customizable. The system should provide intuitive and current online documentation covering scope of application. Online support for the application and updated user manuals should also be provided from time to time. 10 Report Generation 10.1 10.2 Existing reports and existing formats of all MIS reports should be supported by the system. The system should generate all Regulatory reports pertaining to banks as required by the following regulators: Important Important Important Important 10.3 Reserve Bank of India 10.4 Securities and Exchange Board of India 10.5 National Stock Exchange 10.6 Bombay Stock Exchange 10.7 Host regulators for international branches and subsidiaries 10.8 Other regulators 10.9 10.1o 10.11 10.12 The system should be flexible to accommodate changes in formats of regulatory/ MIS reports MIS Reports to top management should have the ability to provide drill-down where necessary. Exception and breach reports should be generated as and when the breach occurs. Exception reports should be sent to pre-defined users either through auto-mailers via the e-mail client or via pop-ups within the system. 11 Report Customization 11.1 11.2 11.3 The system should generate reports based on available data as per any user defined format. The system should be flexible in allowing users to specify the exact layout of the required report including location of fields, header, footer, page numbering, title, etc. The system should be flexible in allowing users to define structures and fields of each report by selecting fields from databases of their choice. N/A Important Important Important Page 62

Sl. No 11.4 11.5 11.6 11.7 11.8 11.9o Requirement The system should allow reports to be exported into Microsoft Excel, Adobe PDF format and other databases. The system should allow users to print reports directly from the system. The system should allow users to save reports to a disc in a noneditable as well as an editable format. The system should provide context sensitive help to guide users to form the reports required by them. The system should have a report writing wizard that provides users with step by step menus and allows them to draw up reports in the required format and define the frequency of the report generation. The system should allow users to present outputs from reports in the form of graphs, charts and other graphic representation Importance ( / Important / Desirable) Important Important 11.11 The system should allow for filtering and sorting of data in reports. 12 File Import and Export Functionality 12.1 The system should have a flat file import and export functionality to import and export transaction data and static data in various formats, including but not limited to: N/A 12.2 Microsoft Excel Format (.XLS) 12.3 Web Page (.HTML) Important 12.4 Comma separated values (.CSV) 12.5 Text file (.TXT) 12.6 Microsoft Word (.DOC) 12.7 Adobe Reader (.PDF) 12.8 ASCII (Flat File) 12.9 Extended Markup Language (XML) 12.1o The system should allow for extraction of all data from the system which includes but is not limited to: 12.11 Transaction details 12.12 Static data (masters) 12.13 Current market information 12.14 Historical market information 12.15 Audit trails 12.16 The system should validate the number of records exported / imported. 13 System Availability 13.1 13.2 The system should allow for source data upload / transaction entry, viewing of positions and creation of ad-hoc reports on a 24-hour basis, 7 days a week. The system should be capable of running background batch operations and automatically uploading all transaction data from the operational systems on an EOD basis every day through a staging N/A Page 63

Sl. No Requirement area. Importance ( / Important / Desirable) 13.3 13.4 The data upload from operational systems may also be initiated manually at any time by the user. The system should support simultaneous use of the system by multiple users without significant performance and integrity issues. 14 Integration With Other Systems 14.1 The integration should be through exposed APIs and/or a staging area and not through any change in code. 14.2 Integration should be supported across all platforms. 14.3 14.4 14.5 14.6 The system should capture and utilize static data associated with counterparties, products, accounts etc. The system should ensure that there are effective checks and controls to ensure that transactions are not loaded multiple times in the system. The system should hold data in an error queue pending review when the data fails criteria for uploading into the system. The system should allow for changing error queue criteria without hard coding. 15 System architecture 15.1 The system should be built in a Client Server Architecture model. 15.2 The system should be platform independent. 15.3 15.4 The client environment should be Windows XP/ Windows VISTA/ Windows 7&8. The system should be available in complete browser based environment for connected / networked locations as also in fat / thin client-server modes 15.5 The system should be available in fat / thin client modes. Important 16 Data archiving 16.1 System should support archiving of data / reports that are beyond a specified time horizon. The time horizon should be parametric. 16.2 16.3 16.4 16.5 Export of data to secondary storage device should be supported by the system without down-time. System should support data retrieval from the specified archives. The archival and retrieval programs shall facilitate easier analysis of old data. The system shall possess in-built data warehousing capabilities or standard interface with data warehousing solutions. The vendor should provide access to the data dictionary so that the Bank has the option to use an external report writer like Crystal/ Business Objects/ MS EXCEL. Desirable Page 64

Sl. No Requirement 17 Backup and Recovery 17.1 17.2 17.3 The system should have a day-end back-up process and allow the user to configure more frequent back-ups, if required. The system should have auto-recovery features in case of system failures Back-up should be possible through external media (CD, tapes, DVD) for off-site storage Importance ( / Important / Desirable) 17.4 The system should support data duplication and accessing 17.5 at same site (LAN environment) 17.6 at different site ( WAN environment) 18 Scalability 18.1 Without the necessity of re-writing code or undertaking other major efforts, the system should be easily upgradable to facilitate: 18.2 Increased Workload 18.3 Better Performance 18.4 Additional Users 18.5 Improved Network Capability 19 Web Access 19.1 19.2 19.3 The system should be internet and intranet enabled and should provide remote access to authorized users. The system should utilize latest available internet technologies and languages like.net/.asp,.xml/.rss, JAVA/.PHP and be compatible with third party internet delivery mechanisms The system should receive and process transactions / queries from the internet, and be able to post transaction processing/ query results on to the internet. 20 Security Management 20.1 20.2 20.3 20.4 20.5 20.6 The system should allow user accounts to be controlled by a specific administrator The system should permit access only through password verification and all user IDs should be unique The system should also have a provision of access through biometrics and access cards. The system should allow upgrades and patches to be uploaded only through the system upgrade path and not to the run-time system Addition of features should be allowed only through a properly revised upgrade and data migration method The system should have the ability to provide or restrict access privileges based upon hierarchy and / or any additional criteria N/A Desirable 20.7 The systems should provide role based access for different types of users (e.g. Treasury, ALM Department, Top Management, etc.) Page 65

Sl. No 20.8 20.9 20.1o 20.11 Requirement The system should allow for creation of unlimited user profiles and assign each user profile to a particular role with pre-defined access rights User ID and login should determine level of access to data e.g. read/view data, print data, write/modify data, delete data etc. The system should have the ability to synchronize the user ID and password with network user ID and password All databases should have database locking features in the situation that there are multiple access and updates on the same record Importance ( / Important / Desirable) 20.12 Standard password management features should include: N/A 20.13 Minimum six length alphanumeric 20.14 Password history to prevent reuse of password for the particular user 20.15 Bank defined password expiry period 20.16 Password encryption 20.17 Automatic user disabling after three successive erroneous tries 20.18 Automatic user time-out on inactivity for a predefined time duration 20.19 Forgot Password functionality 20.2o 20.21 20.22 The system should allow for creation, deletion and modification of users, upgrades of users and data access rights by authorized administrators. There should be a maker-checker facility for key functions in the system. The system should support smart card authenticator for users to access the system by way of digital signatures and PIN. 21 Audit Trail 21.1 The system should have the ability to generate a detailed audit trail on a daily basis for the following minimum features: Desirable 21.2 Attempted unauthorized logins 21.3 Time of login and logout 21.4 Change of passwords 21.5 Change of parameters 21.6 21.7 21.8 21.9 22 The audit trail should be at a granular level, and track the user across each activity All transactions should be time stamped with user ID along with details of modification, if any Details of databases accessed and modified by the users should be maintained by the system The system should have the ability to store and track all system events, including corrections and cancellations by multiple criteria The system should allow manual amendments only after creating an audit trail N/A Page 66

Sl. No 22.1 Requirement The system should maintain an error log in case of missing and/or erroneous data Importance ( / Important / Desirable) 22.2 The system should maintain backups of Audit Log files 5.3 Format Specification It is mandatory to furnish the Technical & Functional Specification in the above format. The means of indicating response (apart from detailed remarks) is given in the following table. The Type of Response/Scale S A C U Description** Standardized, this scale indicates that this feature is a standard feature of the solution. Alternative available Customization required. Vendor will provide the customization with the stipulated date of the phased rollout Unavailable. Functionality is not available and will not be provided by the bidder. **Any responses other than S/C/A/U are not acceptable and will be treated as U. Bidders are expected to explain the functionality in details against responses S, A, C. Page 67

6.1 Source Code 6. Terms & Conditions of Contract 1) The source code of the proposed solution and other applications/ periodical updates shall be kept under escrow arrangement with approved/recognised Escrow Agency mutually acceptable to the Bank and the Bidder but at the bidder s cost for entire duration of the project. The Bank reserves the right to audit the Application / Source Code by suitable Security auditor. 2) In case of a disagreement between the Bank and the bidder regarding appointment of an Escrow agent, the Bank will appoint an Escrow agent in its entire discretion which shall be final and binding on the bidder. 3) The Bank and the bidder shall enter into a tripartite escrow agreement with the designated escrow agent which will set out, inter alia, the events of the release of the source code and the obligations of the escrow agent 4) The Bidder shall provide complete legal documentation of all subsystems, licensed operating systems, licensed system software, and licensed utility software and other licensed software. The Bidder shall also provide licensed software for all software products whether developed by it or acquired from others as part of the project. The Bidder shall also indemnify the Bank against any levies / penalties on account of any default in this regard. 5) The bidder needs to produce certificates of quality control and security audit done on the software in the recent past. 6.2 Software Delivery & Installation 1) The bidder will provide the complete compiled code. The bidder will supply the automated Installation procedures. The bidder will install the application software on computers (servers and selected desktops) of the BANK. Bidder will also provide two sets of backup copies. The installation of the base product will be considered complete only after demonstration of functional features of the software as given in RFP and as per documented procedure and as acceptable to the Bank. 2) The solution must comply with all applicable requirements defined by any regulatory, statutory or legal body which shall include but not be limited to RBI or other Regulatory Authority, judicial courts in India and as of the date of execution of Agreement. 6.3 Acceptance of Software The Bank will accept the developed/ customized software only after implementation of the software with successful conduct of acceptance testing by users. Software will be considered to be accepted only after the Bank issues an acceptance letter to the Bidder. New Software may be audited for risk analysis and security features by Bank s Internal Audit Team or a Third Party Auditor appointed by the Bank, if so desired by the Bank. Go-Live date will be the date from which the software has been accepted by the bank in its full form subject to the conditions specified above. Page 68

6.4 Inspection and Tests 1) Bank or its representative shall have the right to inspect and/or to test the software or the Goods to confirm their conformity to the requirements/specifications mentioned in this RFP at no extra cost to the Bank. 2) Should any inspected or tested software fail to conform to the specifications, the Bank may reject it, and the Bidder shall either replace the rejected software or make alterations necessary to meet specification requirements free of cost to the Bank. 3) Bank may choose to carry out a technical inspection/audit and performance evaluation of products offered by the Bidders. The Bidder would permit Bank or any person/persons appointed by Bank to observe the technical and performance evaluation / benchmarks carried out by the Bidder. 4) There will be an acceptance test by Bank or its nominated representatives after installation of the systems. In case of any discrepancy in the software supplied, Bank reserves the right to cancel the entire contract. The test will be arranged by the Bidder at the identified sites in the presence of the officials of Bank and / or its representatives. The tests will involve trouble-free operation of the complete system during UAT apart from physical verification and testing. There shall not be any additional charges for carrying out this acceptance test. Bank will take over the system on successful completion of the above acceptance test. The installation cum acceptance test & check certificates jointly signed by Bidder's representative and Bank's official or any consultant / auditor appointed by Bank should be submitted along with invoice etc. for scrutiny before taking up the request for consideration of payment. 5) The Bank will give UAT sign-off only for reports/statements in their final form and/or documents specifically mentioned in this RFP. 6) All reports/statements for which UAT Sign-Off has been given by the Bank shall come to production within 7 days from the date of the respective sign-off. 7) The Bank s right to inspect, test and, where necessary, reject the Goods after the Goods arrival in the destination shall in no way be limited or waived by reason of the Goods having previously been inspected, tested and passed by the Bank or its representative prior to the Goods shipment. 6.5 Information Ownership 1) All information processed, stored, or transmitted by successful Bidder s software belongs to the Bank. By having the responsibility to maintain the software, the Bidder does not acquire implicit access rights to the information or rights to redistribute the information. The Bidder understands that civil, criminal, or administrative penalties may apply for failure to protect information appropriately. 2) Any information considered sensitive by the Bank must be protected by the successful Bidder from unauthorized disclosure, modification or access. The Bank s decision in this regard will be final. 3) Types of sensitive information that will be found on Bank system s which the Bidder plans to support or have access to include, but are not limited to: Information subject to special statutory protection, legal actions, disciplinary actions, complaints, IT security, pending cases, civil and criminal investigations, etc. The successful bidder shall exercise adequate judgment to decide if particular information is sensitive and consult with the Bank in case of doubts. 4) The successful Bidder shall not publish or disclose in any manner, without the Bank s prior written consent, the details of any security safeguards designed, developed, or implemented by the Bidder or existing at any of the Bank location. The Bidder will have to develop procedures and implementation plans to ensure that IT resources leaving the control of the assigned user (such as being reassigned, removed for repair, replaced, or upgraded) are cleared of all Bank data and sensitive application software. Page 69

6.6 Adherence to Standards The bidder should adhere to laws of land and rules, regulations and guidelines prescribed by various regulatory, statutory and Government authorities in India. The Bank reserves the right to conduct an audit/ongoing audit of the services provided by the bidder. The Bank reserves the right to ascertain information from the Banks and other institutions to which the bidders have rendered their services for execution of similar projects. 6.7 Security Configuration, Monitoring and Audit 1) The baseline security configuration of the software/other applications provided by the bidder should be done by the bidder, according to the industry best practices and the Banks internal policy. 2) Compliance with security best practices may be monitored by periodic computer security audits performed by or on behalf of the Bank. The periodicity of these audits will be decided at the discretion of the Bank. Periodicity for Regulatory Audits would be required as per the rules and guidelines laid down by the regulator or as required by the regulator. These audits plan to include, but are not limited to, a review of: access and authorization procedures, physical security controls, input/output controls, DB controls, backup and recovery procedures, network security controls and program change controls. 3) To the extent that the Bank deems it necessary to carry out a program of inspection and audit to safeguard against threats and hazards to the confidentiality, integrity, and availability of data, the Bidder shall afford the Bank s representatives access to the Bidder s facilities, installations, technical resources, operations, documentation, records, databases and personnel. The Bidder must provide the Bank access to various monitoring and performance measurement systems (both manual and automated). The Bank has the right to get the monitoring and performance Measurement systems (both manual and automated) audited without prior approval / notice to the Bidder. 6.8 Considerations for Proposed Hardware & Software to support Solution 1) All software should be of the latest tested proven bug-free version. 2) The Bidder should provide the details for all the hardware including OS & RDBMS, networking equipment and any other requirement (to be procured by the Bank) for successful implementation of their software proposed. 3) The proposed solution should facilitate application level encryption. 4) Proposed solution shall be platform independent i.e. it should function both Intel based and Risk based platform. 5) The proposed solution should have full capability to support database to database replication and storage to storage replication between DC and DR with a Recovery Point Objective (RPO) of 30 minutes and Recovery Time Objective (RTO) of 4 hours. The replication between DC and DR should be possible in both directions. 6) The bidder shall specify the suitable hardware and supporting software which shall deliver the best throughput and performance considering the present volumes and the sizing proposed should consider the probable increase in volumes for next 7 years. The necessary information Page 70

required by bidder to estimate sizing required hardware may be obtained from the bank (if required). 6.9 Performance Guidelines The proposed solution should comply with the following guidelines on performance and solution components in minimum. 1) Bidder should clearly specify the detailed configuration and specifications of the applications and corresponding hardware required at various levels based on the technical requirements. The bidder should separately list down the reasons for the recommended hardware configurations and specifications. The bidder has to explain through proper calculations how the performance of the system vis-à-vis business statistics, projected growth, redundancy, projected growth in functional requirements, concurrent users, performance parameters expected on peak load. The bidder should provide data on any other parameter which would be required. 2) Bidder should also provide data on the solution as how the individual components under the solution (application and associated hardware as advised to the Bank) would be able to meet the current volumes as well as the future scalability requirements. 3) The bidder should provide information on industry standard benchmarks for the system such as TPC certified by Transaction Processing Council. 4) The bidder has to furnish the details of the configuration of the servers, OS and databases to be used in such benchmarking exercise for TPC etc. 5) The bidder should also provide the benchmarks with Risk Management application software preferably conducted with real time loads for similar requirement or as acceptance test with credential and details of references involved in conducting such benchmarks. 6) The Bidder has to relate the same to the model and configuration of the hardware proposed for Bank s requirement. 6.10 Confidentiality The vendor will be required to treat as confidential all data and information about the Bank, obtained in the execution of his responsibilities, in strict confidence and shall not reveal such information to any other party without the prior written approval of the Bank/Purchaser. A non-disclosure agreement should be signed between Bank and vendor. The format of non-disclosure agreement form is given in Annexure-3. 6.11 Disaster Recovery System The proposed system must be capable of and compatible for Disaster Recovery Implementation. The successful bidder should describe the provisions for disaster recovery and show that the proposed solution facilitates disaster recovery. It will be the responsibility of the bidder to implement Disaster Recovery facility for the ALM solution. System must resume processing using the disaster recovery secondary site within 4 hrs. The bidder needs to submit the technical architecture relating to data replication between primary and secondary site. The Recovery Time Objective (RTO) and Recovery Point Objective (RPO) for the proposed solution should be 4 hrs and 30 minute respectively. Page 71

6.12 Service Level Agreement (SLA) These Service Levels are only indicative and the Service Level Agreement (SLA) will be finalized in agreement with the selected vendor. The vendor shall be bound to provide the agreed service levels. Service Levels will include Availability measurements, Performance parameters, call resolution time, etc. Bank requires the Bidder to provide reports for all availability and performance parameters and a log of all issues that have been raised and Closed/ Pending Closure by the Bidder. The frequency of these reports would be Weekly, Monthly, Quarterly and Yearly as mutually agreed. Apart from reports on each availability and performance measurement parameter mentioned below, the reporting should also include the following: Utilization of CPU, RAM, Hard Disk, (Peak and Average) CPU utilized percentage by the system and user activity. Percentage of physical memory utilized by system and user processes. Problem Trends Call Resolution Time Audits will normally be done on monthly/quarterly basis or as required by Bank and will be performed by Bank or Bank appointed third party agencies. The bidder is bound to provide on-site support to meet the requirements specified in SLA. In other words, if the services rendered by the system falls short of standards stipulated in SLA, the bidder shall provide on-site assistance. Availability Measurements Expected Service Level Base Amount on which penalty will be calculated Penalty* Availability of software components and Test and Development infrastructure 98% Value of the software 10% The cost of AMC/ ATS after the warranty period will not be included in value of the software, for the purpose of penalty calculation. Type of Infrastructure System Response Time Performance Measurement # End to End response time within the DC Time or DR to the Database should be < 60 seconds. Expected Service Level 99.50% Base Amount on which PENALTY will be Calculated The bidder is to upgrade the Hardware along with related software and services without any additional cost to the Bank, if service level is not met. Until Service level is met, penalty will be charged on the value of the business infrastructure at DC or DRC, as the case may be. Penalty 10% Page 72

Type of Infrastructure Disaster Recovery Site Availability Data Point Availability Performance Measurement # Business operations to resume from Disaster Recovery Site within 4hrs of the Data Centre failing and vice versa Recovery Point Objective (RPO) of 30 minutes. Expected Service Level 100.00% 100.00% Base Amount on which PENALTY will be Calculated Penalty will be charged on the value of the business infrastructure at DC or DRC, as the case may be. Penalty will be charged on the value of the business infrastructure at DC or DRC, as the case may be. Penalty 10% 10% * The amount indicated in this column represents the maximum penalty, which would be charged in case of default. In the event of failure of maintaining the uptime SLA, liquidated damages of 10,000/- per day will be charged. # Bank will measure all the performance parameters through periodic audits based on logs to be provided by Bidder. 6.13 Software Licenses for Solution Bidders are required to propose Enterprise Wide Application License on perpetual basis. The bidder shall furnish the price details of licenses in the format given in Annexure 12 A. 6.14 Hardware Requirement The Bidder is required to advise the Bank detailed requirement/sizing of adequate hardware based on the relevant parameters for the ALM Solution. Bank will provide the required hardware including OS & RDBMS for implementation of ALM solution. System should be sized adequately to ensure maintenance of historical data and in pursuant with purging policy. The data will be retained for a period of 7 years, beginning from the previous 6 years and ending with the current year. All the data previous to the 7 years will be archived and will be retained offline. The vertical scalability available within the server should be at least 20% to accommodate additional CPUs, Memory (including cache) over and above the terminal year sizing requirements. Hardware sizing should be done in such a manner that any point in time during the contract period, during business hours, the hourly average CPU, Memory, Hard Disk utilization should not exceed 70% threshold for more than 30 minutes. The hardware sized should be scalable and fault tolerant. All the components within the server should be hot swappable or pluggable and should incur no downtime due to component failure. All the core product servers suggested should have dual power supplies. The power input to the power supplies will be from separate UPS. In case of failure of one power supply, the second power supply should be able to take the full load without causing any interruption in services The bank would like to stagger the deployment of the hardware resources over the years based on projected and actual utilization. Accordingly, bidder needs to advise the Bank the hardware Page 73

requirement over the tenure of the contract period. The initial hardware advised should be capable of handling at least the first three years load, volume and sizing. the Bidder has to advise appropriate hardware and other resources to be incrementally added based on the increase in the load and volumes to support the growth for the remaining contract period. The Bidder has to ensure that the configuration proposed is capable enough of handling the respective year s load and volume. 6.15 Environments Bank intends to procure physically separate adequately sized hardware for unified test & development server. Bidder to advise the sizing of T&D servers also which will be kept only at DC. The Test & Development server sizing should be minimum 50% of the size of the production database server as per the first year sizing with minimum 25% available space for vertical scalability within the test and development server. 6.16 Phased Implementation The Bidder has to implement the ALM Solution in a modular and phased manner. 1) The Bidder will be responsible for installing the applications with all the customizations. 2) The Bidder will set all the parameters in the application as accepted in the test environment. The Bidder shall be responsible for accuracy of the parameters set according to the business needs of the Bank. 3) The Bidder will be responsible to interface the Solution with identified data sources. 4) During the entire phased implementation of the Solution, OEM should provide onsite resources on a full time basis including a full time onsite project manager as part of their implementation team for the phased implementation. 6.17 Project Documentation and Manuals Soft copies of User and Technical manuals are to be provided for all the functionalities/modules/ /tools proposed for the solution separately. In addition, online help with search option has to be made available for all users for all applications. Bank will require the Bidder to follow worldwide practice and international standard for the documentation for the entire System Development Life cycle and provide the same. All such documentation and manuals will be kept up to date with proper version control during the entire contract period. Bank may require the bidder to deliver the following documents (in addition to standard documentation from OEM) both in hard and soft copy to Bank during development and implementation of ALM solution 1) Installation Document 2) System Requirement Specification Document 3) Architecture Document 4) Risks and Mitigation Document 5) Gap analysis Document 6) Data requirement Document 7) High Level Design Document 8) Proof of Concept for the ALM 9) Low Level Design Document 10) Test Plans 11) Comprehensive Test Cases Document (Unit, Integration and SIT Test Cases) Page 74

12) Security Management Guide 13) User Management Guide 14) Configuration Document 15) Operational Manual 6.18 Interface & Integration Requirements 1) The Bidder has to supply, install, customize, implement, train, rollout and maintain the interfaces including, tools necessary for the functioning of the Interface if required. 2) The Bidder is required to build interfaces between the proposed Solution with the applications and systems mentioned below (but not limited to) at no extra cost to the Bank: Core Banking Solution Integrated Treasury Management System (ITMS) Exim Bills General Ledger Automated Data Flow Overseas Branch s Banking Solution 3) The bidder is also expected to ascertain gaps in the data and provide solution to the bank, which should be in line with the requirements and acceptable to the Bank. 4) It is the expectation of the Bank that the integration/interface architecture is based around industry best practices and uses an enterprise ETL tool. 5) The Bidder will be responsible for identifying the detailed interface requirements for integrating the proposed packages to the existing systems of the Bank and for all other functionalities as mentioned in this RFP. 6) The interface architecture should be clearly defined. The integration architecture should include the types of interfaces supported; the standards used and should comply with Bank architecture principles. 7) The Bidder will present to the Bank the interface requirements for review. 8) Any suggestions from the Bank will have to be included by the Bidder. 9) The Bidder will be responsible for developing (extraction, transformation and loading of data), testing and maintaining the interfaces. When developing the interfaces, the Bidder should ensure the requirements of data format, frequency of data transfer, quality checks and validations before data transfer and priorities for data transfer are identified and addressed. 10) The Bidder must ensure that all applicable interfaces are automated with no manual intervention. 11) The Bidder will ensure and incorporate all necessary security and control features within the applications as to maintain integrity and confidentiality of data at all times. 12) The Bidder will be responsible for setting up the test environment for interface testing. 13) The Bidder will help/assist the Bank in preparing the test cases for the testing. Bidder shall ensure that the test cases meet all the testing requirements of the Bank. 14) The Bidder must ensure that a sound methodology is implemented (e.g. SOA governance framework, integration competency center) to manage the interfaces. 15) As a back-stop measure, the system should support the manual upload of transaction data from various operational systems in formats provided by the Bank. Page 75

6.19 Warranty & Annual Maintenance 1) The Supplier warrants that the software supplied under the Contract is of the most recent or updated version and will incorporate all recent improvements in design and materials unless provided otherwise in the Contract. The Supplier further warrants that all Goods supplied under this Contract shall have no defect arising from design, materials or workmanship (except when the design and / or material is required by the B ank s Specifications) or from any act or omission of the Supplier, that may develop under normal use of the supplied Goods in the conditions prevailing in the country of final destination. 2) This onsite comprehensive warranty with 24/7 Support shall remain valid for 36 months from the date of GO LIVE. The Bank shall promptly notify the Supplier in writing of any claims arising under this warranty. The AMC shall be for a period of 2 years beginning from the date of completion of the Warranty Period. 3) Upon receipt of such notice, the Supplier shall with all reasonable speed, rectify the issues without cost to the Bank. If the Supplier, having been notified, fails to rectify the defect(s) within a reasonable period, the Bank may proceed to take such remedial action as may be necessary, at the Supplier s risk and expense and without prejudice to any other rights which the Bank may have against the Supplier under the Contract. 4) During the period of AMC, if the service provided by the Bidder is not satisfactory, the Bank reserves the right to terminate the AMC contract and appoint any other agency at the risk and cost of the Bidder. 5) The maximum response time for a maintenance complaint from the site of installation (i.e. time required for Bidder s maintenance engineers to report to the installation site after a request call / fax /email is made or letter is written) shall not exceed One hour. 6) The Bank reserves the right to modify/update the parameter files/configuration with required awareness of its consequences and any such modification/ updating will be recorded for information of the selected bidder without any impact on the media as per OEM descriptions. 7) The bidder shall provide centralized complaint booking facility to the Bank and the dash board, if available, shall be provided to the Bank. The method of booking complaints shall be through E-mail, Toll-free no, on line portal, web, etc. 8) The products & services offered must include comprehensive on-site warranty from the date of installation and acceptance of the solution by the Bank including all software parts, media, patches, updates and licenses. The Warranty will commence from the date of GO LIVE. 9) Bidder must provide onsite full time personnel for next 5 years from the date of GO LIVE. 10) During the warranty period Bidder shall maintain the systems and repair all defective components that are brought to the Bidder s notice at the installation site and at no charge to the Bank, 11) In the event of system breakdown or failures at any stage, protection available shall be specified which would include the following: - Diagnostic for identification - Protection of data entered - Recovery / restart facilities - Backup facilities Page 76

12) The selected bidder must agree that during the warranty / AMC period, the software will be kept up-to-date in terms of followings, without any additional cost to The Bank: - User suggestions and feedback. - Bugs removal and troubleshooting. - Maintenance and support for patches, version control and release. - Import data from any new input source to the proposed Solution database as and when required. - Regular performance tuning of the proposed solution and process optimization for users. - Regular backup of the proposed software & database. - Data rectification, if required, on being caused due to any program malfunction or due to any other reason whatsoever. - Re-installation and configuration of software for the proposed solution, database, etc. if required. - Conduct DR Drill on a quarterly basis. 13) The bidder must agree that during the warranty/ AMC period, they will provide the following operational support: - On-site support including training and hand-holding to the concerned personnel of the bank. - Tuning and configuration of software - Conducting regular server capacity analysis and take remedial measures as required - Conducting routine database assessments to ensure data quality and optimal data base performance - Conducting periodic assessments of the proposed solution and/or its infrastructure to ensure that all the functional requirements are satisfied. - Determining when the proposed Solution and/or its infrastructure need to be upgraded, replaced, or retired as per user/regulator s requirements. - Installation, configuration of user specific various Master Tables. - The selected bidder is required to perform following user administration activities like creation of users, defining user authorization, granting of respective user rights and privileges. - Migration of data from source system, at the start of the project. Assisting user to carry out live run. - Redress various operational problems. - Carry out various housekeeping works and explain the same to users. - Facilitate the Bank with the functionality for regulatory reporting, as required by the regulator. 14) Upgrades would include product releases made by the Bidder to incorporate technological changes, consolidating all bug fixes, all enhancement requests made by the Bank. 15) No customization and subsequent implementation charges will be payable by the Bank for enhancements, modifications and upgrades. 16) The Bidder agrees that any future upgrades, modifications or enhancements shall not affect the current working of the licensed software and all current functionality shall be migrated to the new/enhanced version. Page 77

17) The Bidder shall implement the new/enhanced version and that the Bank will bear no cost for migrating the existing functionality to the new/enhanced version. 18) For implementing different versions of Application Software, if adjustments / change in the configuration are to be made in base memory the same should be carried out by the Vendor as a part of warranty. 19) The Bidder shall ensure that the warranty complies with the agreed Technical Standards, Security Requirements, Operating Procedures, and Recovery Procedures. 20) The Bidder shall develop and maintain an inventory database to include the registered software licenses existing as of the Start Date, and the warranties and licenses for software: - Procured through the Bidder, or - Procured by the Bank with notification to the Bidder for inclusion in such data base 21) The Bidder shall perform warranty and license registration, if any, with the appropriate manufacturer, of software: - Procured through the Bidder, or - Procured by the Bank with notification to the Bidder for inclusion in such data base. 22) Bidder shall monitor warranties to check adherence to preventive and repair maintenance terms and conditions. 23) Bidder shall provide the Bank with access to asset control information 24) Bidder shall provide to the Bank, as reasonably requested, reports that aid the Bank in performing asset management and financial management functions of the Bank as these relate to software licenses. 25) Bidder shall maintain data regarding entitlement for software upgrades, enhancements, refreshes, replacements and maintenance; 26) Bidder shall provide technical information as reasonably requested by the Bank for preparation and implementation of budgets and cost benefit analysis. 6.20 Training The successful Bidder shall be responsible for providing Training to various target groups consisting of Asset Liability Management Personnel. 1) Training Infrastructure will be provided by The Bank. 2) The functional and technical training would be in batches, as desired by the Bank on full time basis for at least 10 days. Training shall be provided to the concerned Personnel. User training should cover at least the following areas - Functional Training Functionality available in the system Deployment of various products / packages as part of the solution Customization development Parameterization Interface development (data mapping, field validations, default values, gaps in data, manual data entry programs etc.) Page 78

Techniques of generating various MIS / EIS reports from solution provided Using of all the audit tools being provided - Technical Training System and application administration Log analysis and monitoring 3) The Bank reserves the right to change reasonably the number of training programs/batches, team size, Training Dates, Location, Modalities and Curriculum. 4) Training Study Material for each program in soft copy and hard copy shall be provided by successful Bidder to The Bank. 5) Self e-learning training kit of the entire solution to be provided by the successful Bidder to the Bank. The Bidder has to ensure that there is online help available for each functional area within the ALM Solution post go live of the application for every user of the Bank. 6.21 Obligations of the Bidder In the course of rendering the aforesaid Software Maintenance & Support services, Bidder shall be responsible for the following: 1) The Bidder shall render both on-site and off-site maintenance and support services to the Bank. The Bidder shall provide troubleshooting / customer support mechanism. The Software Maintenance and Support Services shall be provided by the Bidder from the Bank s premises. 2) Bidder shall assign personnel of appropriate qualifications and experience to perform the services in order to fulfil its obligations. 3) Bidder shall designate one of its personnel as the Project Manager, to interact with the Designated Customer Support Contact from the Bank for the purposes of getting approvals, progress report, discussing and resolving issues, arranging meetings, etc. 4) Bidder shall exercise requisite control and supervision over its personnel in the course of rendering the services and make best efforts to ensure that the services are rendered in a continuous and uninterrupted manner. 5) Though Bidder has the right to withdraw its personnel, Bidder will replace the persons with other personnel having appropriate experience and skills at no extra cost to the Bank. 6) In the event that any person engaged/deputed/deployed for rendering services, is, either; No longer available by reason of resignation or termination or the like; or, Unable to render satisfactory services; or, Not acceptable to the Bank by reason of any misconduct or non-performance/under performance on the part of such person, then Bidder will use all reasonable endeavours to replace such individual(s) promptly by other sufficiently skilled, qualified, and experienced person(s) at no extra cost to the Bank. Bidder will in the discharge of its obligations use all reasonable endeavours to minimize changes in personnel. 7) Bidder will respect the confidentiality of all information given to it by the Bank and will not divulge such information to any third party or other units without the consent of the Bank. 8) Bidder shall impart to the authorized employees of the Bank, additional technical and/or user training in respect of any corrected licensed software provided, if required by the Bank. Page 79

9) The Bidder shall promptly install/implement the corrected licensed software and/or maintenance releases provided at the Designated Location(s) of the Bank at no additional cost or fees or expenses. 10) The Bidder shall undertake regular preventive maintenance of the licensed software. 11) All bug fixations / modifications / enhancements relating to the licensed software shall be done by the Bidder in a time bound manner as per the SLA. The bidder shall also provide a leading and current anti-virus for the requisite systems to be placed in the DC/DR. The Bidder shall adopt a common, smooth, timely and effective and satisfactory bug/enhancement handling mechanism. The Bidder agrees that the errors resulting from the licensed software shall not be attributed to alleged misuse, improper use, alteration or damage by users. The Bidder shall compensate the Bank such financial loss suffered by the Bank if the Bidder fails to fix bugs, provide the modifications / enhancements / customization as required by the Bank as per the terms and conditions of this tender and to meet the services level agreements as will be entered into by the Bidder with the Bank. 6.22 Termination for Default The Bank, without prejudice to any other remedy for breach of contract, by 30 days written notice of default sent to the Supplier, may terminate this Contract in whole or in part under any of the below conditions:- 1) If the Supplier fails to deliver any or all of the Goods within the period(s) specified in the Contract, or within any extension thereof granted by the Bank. 2) If the Supplier fails to perform any other obligation(s) under the Contract. 3) If the Supplier, in the judgment of the Bank has engaged in corrupt or fraudulent practices in competing for or in executing the Contract. corrupt practice means the offering, giving, receiving or soliciting of anything of value to influence the action of a public official in the procurement process or in contract execution; and fraudulent practice means a misrepresentation of facts in order to influence a procurement process or the execution of a contract to the detriment of the Bank, and includes collusive practice among Bidders (prior to or after bid submission) designed to establish bid prices at artificial non - competitive levels and to deprive the Bank of the benefits of free and open competition. In the event the Bank terminates the Contract in whole or in part, the Bank may procure, upon such terms and in such manner as it deems appropriate, Goods or Services similar to those undelivered, and the Supplier shall be liable to the Bank for any excess costs for such similar Goods or Services. However, the Supplier shall continue performance of the Contract to the extent not terminated. In addition to the termination of contract, Bank reserves the right to appropriate the damages through encashment of Bid Security/ Security Deposit /Performance Guarantee given by the Bidder and retention money and/or any payments due to the bidder. 6.23 Exit Option The Bank reserves the right to cancel the contract in the event of happening of one or more of the following Conditions: Failure of the successful Bidder to accept the terms of the contract, furnish the Performance Guarantee and sign the contract within the time frame specified by the Bank Page 80

Delay in completing installation / implementation and acceptance tests/ checks and/or any other obligations, beyond the specified periods; Serious discrepancy in functionalities to be provided or the performance levels agreed upon, which have an impact on the functioning of the Bank. The Exit Clause may be enforced by the Bank in above cases if the bidder is not able to provide an alternate agreeable to the Bank within a period of 90 days. In addition to the cancellation of contract, Bank reserves the right to appropriate the damages through encashment of Bid Security/ Security Deposit /Performance Guarantee given by the Bidder and retention money. When LD reaches the level of 10% of the Contract Price. 6.24 Force Majeure Force Majeure is herein defined as any cause, which is beyond the control of the selected Bidder or The Bank as the case may be which they could not foresee or with a reasonable amount of diligence could not have foreseen and which substantially affect the performance of the contract, such as: 1. Natural phenomenon, including but not limited to floods, droughts, earthquakes and epidemics 2. Acts of any government, including but not limited to war, declared or undeclared priorities, quarantines and embargos 3. Terrorist attack, public unrest in work area Provided either party shall immediately notify the other in writing of such causes. The Bidder or The Bank shall not be liable for delay in performing his/her obligations resulting from any force majeure cause as referred to and/or defined above. Any delay beyond 30 days shall lead to termination of contract by parties and all obligations expressed quantitatively shall be calculated as on date of termination. Notwithstanding this, provisions relating to indemnity, confidentiality survive termination of the contract. 6.25 Performance Security 1) Within 21 days of issue of Purchase Order, the supplier shall furnish to the Bank an unconditional and irrevocable Performance Guarantee equivalent to 10% of the total Contract Amount in the form of a Bank Guarantee, valid for seven years from the date of purchase order in the format enclosed. In case of delay in submission of the Bank Guarantee, Bank may charge 0.5% penalty of the contract amount per week or part thereof subject to a maximum of 10% value of the contract. 2) The project will be deemed complete only when all the solutions and items contracted for by Bank are delivered in good condition, installed, commissioned, implemented, tested and accepted along with the associated certification, documentation and training provided to Bank s employees in compliance with the terms of this RFP and as per the requirements of the contract executed between Bank and the Bidder and the acceptance criteria defined in this document is met. 3) The Performance Security shall be invoked by the Bank as compensation for any loss resulting from the Supplier s failure to complete its obligations under the Contract. 4) The Performance Security will be discharged by the Bank and returned to the Supplier after expiry of the claim period. Page 81

6.26 Liquidated Damages In case of delayed supply or implementation, the supplier shall be liable to pay as Liquidated damages at the rate specified below, for each completed week of delay or part thereof, on the purchase order value of the proposed Solution. Liquidate Damages: Rate Delay Period 0.50% of the contract price with a cap of 10% Per week or part thereof The bank may however extend the time of completion under Force Majeure conditions. The liquidated damages shall be deducted / recovered by the bank from any money due or becoming due to the bidder under this purchase contract or may be recovered by encashment of bank guarantees or otherwise from supplier. 6.27 Settlement of Disputes 1) If any dispute or difference of any kind whatsoever shall arise between the purchaser and the supplier in connection with or arising out of the contract, the parties shall make every effort to resolve amicably such disputes or difference by mutual consultation. 2) If after 30 days the parties have failed to resolve their disputes or difference by such mutual consultation, then either the purchaser or the supplier may give notice to the other party of its intention to commence arbitration, as hereinafter provided, as to the matter in dispute, and no arbitration in respect of this matter may be commenced unless such notice is given. 3) Any dispute or difference in respect of which a notice of intention to commence arbitration has been given in accordance with this clause shall be finally settled by arbitration. Arbitration may be commenced prior to or after delivery of the goods under the contract. 4) Arbitration proceedings shall be conducted in accordance with the following rules of procedure. The dispute resolution mechanism to be applied shall be as follows: a) In case of dispute or difference arising between the parties to the contract relating to any matter arising out of or connected with this agreement, such dispute or difference shall be settled in accordance with the Arbitration and Conciliation Act, 1996. The arbitral tribunal shall consist of 3 arbitrators one each to be appointed by the Purchaser and the Supplier; the third Arbitrator shall be chosen by the two Arbitrators so appointed by the Parties and shall act as Presiding Arbitrator. In case of failure of the two arbitrators appointed by the parties to reach upon a consensus, the Presiding Arbitrator shall be appointed by the competent court of law under Arbitration Act, which shall be final and binding on the parties. b) If one of the parties fails to appoint its arbitrator within 30 days after receipt of the notice of the appointment of its Arbitrator by the other party, then the competent court of law under Arbitration Act, both in cases of the Foreign Supplier as well as Indian Supplier, shall appoint the Arbitrator. A certified copy of the order of the competent court of law under Arbitration Act making such an appointment shall be furnished to each of the parties. c) Arbitration proceedings shall be held at Kolkata India, and the language of the arbitration proceedings and that of all documents and communications between the parties shall be English. d) The decision of the majority of arbitrators shall be final and binding upon both parties. The cost and expenses of Arbitration proceedings will be paid as determined by the Arbitral Tribunal. However, the expenses incurred by each party in connection with the preparation, presentation etc. of its proceedings as also the fees and expenses paid to the arbitrator appointed by such party or on its behalf shall be borne by each party itself. Page 82

6.28 Time Schedule The following time schedules should be adhered to for completion of the activities. 1. Business Requirement Study: Within 90 Days from the date of the Purchase Order. 2. Interface development, integration, customization, Installation of Customised Software: Within 120 Days after completion of activities stated in point 1 above. 3. UAT, Operationalization & Training: Within 150 days after completion of activities stated in point 2 above. Please note that maximum expected time frame of the project to GO LIVE is 15 months* from the date of issuing Purchase Order. Accordingly vendors have to deploy the resources. *Appropriate decision of extending the implementation period will be taken by bank, if required. 6.29 Payment Payment Terms Supplier will have to submit the Documents at the Bank s office along with request letter for payment. Documents related to each Phase should be submitted for payment in single lot. Terms of Payment will be as under: 1) No advance payment will be made. 2) TDS will be applicable 3) The payments made will be after completion of project milestones as under: Terms for ALM System The Bank shall make payments to the selected vendor in accordance with the commercial proposal submitted post reverse auction: Cost of Application Software for items specified in Table A of Commercial Bid Format (Annexure 13) plus applicable taxes o 20% after Interface development, integration, customization and Installation of Customised Software o 20% after UAT Sign Off of key reports/returns (i.e. SLS, IRST/IRSD, DLS, LCR, NSFR); o 20% after UAT Sign Off of balance reports/returns; o 20% after full Go Live and successful completion of Training & one DR Drill; o 20% after 6 Months from the date of successful implementation and Go Live; Cost of Implementation Primary Site & DR Site as specified in Table B of Commercial Bid Format (Annexure 13) plus applicable taxes o 10% on sign off on Business Requirement Document o 20% after UAT Sign Off of key reports/returns (i.e. SLS, IRST/IRSD, DLS, LCR, NSFR); o 10% after UAT Sign Off of balance reports/returns; o 40% after full Go Live and successful completion of Training & one DR Drill; o 20% after 6 Months from the date of successful implementation and Go Live; Page 83

AMC and Facility Management Services o Payment of AMC/FMS Charges as specified in Table C & D of the Commercial Bid Format (Annexure 13) plus applicable taxes payable quarterly in arrears 6.30 Paying Authority The payments as per the Payment Schedule covered hereinabove shall be paid through Department of Information Technology of the Bank. However, Payment of the Bills would be made on receipt of advice/confirmation for satisfactory delivery/installation/re-installation, live running and service report from the concerned offices/department where the purchased items have been delivered and implemented. 6.31 System Administration Bidder to Provide for system administration services. Examples of these services are: Client account maintenance - Creating users, groups, creating user accounts, deleting user accounts, modifying user accounts, etc. on the system; File/system/application access management - Maintaining file and directory permissions on OS and application access management like creating user accounts at application level, assigning application access, setting application passwords, user lockout, etc.; Performance optimization and reporting - Process and Memory Management, monitoring CPU performance, monitoring Memory performance, monitoring Input/output performance, monitoring Ethernet traffic, etc.; Error detection and correction; Troubleshooting and client support 6.32 Database Access Vendor shall provide the Bank, understanding and full access to Database, Database Table Structures and Data Dictionary of the proposed solution. 6.33 Software Maintenance The Bidder should provide, through a set of standard software packages, software and software related services to hardware infrastructure. Types of service include requirement analysis, assisting the Bank in software product acquisition for testing, verification, and installation of Bidder supported software, in accordance with bug fixes, emergency changes and program changes initiated by the users. Prior to delivering any software to the Bank, the Bidder will be required to test the software and the media on which it is to be delivered with a current version of a leading anti-virus application in efforts to detect, and if so detected, to eliminate, any viruses or worms designed to damage, disrupt, disable, harm, or otherwise impede in any manner, the orderly operation of the software. The Bidder shall also ensure that the software does not and shall not contain any computer code or any other procedures, routines or mechanisms to: (i) disrupt, disable, harm or impair in any way the software (or other applications installed on the system the software is installed or interacts with) orderly operation based on the elapsing of a period of time, exceeding an authorized number of copies, advancement to a particular date or other numeral (sometimes referred to as time bombs, time locks, or drop dead devices); (ii) cause the software to damage or corrupt any of the Banks or its Page 84

clients data, storage media, programs, equipment or communications, or otherwise interfere with the Banks operations, or (iii) permit the Bidder and/or its personnel and/or its licensors and/or any other third party, to access the software (or any other software or Banks computer systems) to cause such disruption, disablement, harm, impairment, damage or corruption (sometimes referred to as traps, access codes or trap door devices). 6.34 Software Maintenance and Support Services during Warranty and AMC The Software Maintenance and Support Services contemplated herein shall be provided for all Licensed Software implemented by the Bidder. The Bidder shall provide remote trouble shooting / customer support mechanism from any single location like Head office of the Bank or through Web based methodology. The Maintenance and Support Services will cover: 1) All product upgrades, modifications, enhancements that have to be provided to the Bank free of charge. 2) Enhancements would include changes in the software due to Statutory and Regulatory changes and changes required due to changes in industry and other Banking practices in India. It will also include all the functionalities mentioned in Functional Requirement. Changes to be made applicable with in stipulated time period mutually agreed between Bank & bidder. 3) Modifications would include minor changes, bug fixes, error resolutions and minor enhancements that are incidental to proper and complete working of the application. 4) Upgrades would include product releases made by the Bidder to incorporate technological changes, consolidating all bug fixes, consolidating all enhancement requests made by the Bank. 5) No customization and subsequent implementation charges will be payable by the Bank for enhancements, modifications and upgrades. 6) The Bidder agrees that any future upgrades, modifications or enhancements shall not affect the current working of the licensed software and all current functionality shall be migrated to the new / enhanced version. 7) The Bidder shall implement the new/enhanced version and that the Bank will bear no cost for migrating the existing functionality to the new / enhanced version. 8) The Bidder shall have the responsibility to ensure that the designate OEM undertakes to perform all obligations with respect to the project and all other software contemplated in the Solution, upon the same terms and conditions as agreed to by the Bidder in the event that (i) OEM is unable to perform its obligations, (ii) OEM refuses to perform its obligations, (iii) expiry of the agreement and (iv) termination of agreement, with respect to the project for any reason whatsoever. The Bidder acknowledges that the rights mentioned herein are without prejudice to the rights and the remedies (under law or equity) that the Bank may have against the Bidder. 9) The Bidder shall apply regular patches to all the softwares supplied by them for which the Bank will bear no additional costs. The Bidder agrees that the functioning of the ALM solution of the Bank will not be affected adversely as a result of any new releases, enhancements, patches, etc. Page 85

10) The Bidder agrees at all times to meet the service levels as specified in this tender document. 11) The Bidder shall maintain the entire IT infrastructure for all the components implemented under this tender and subsequent agreement as well. 12) User support in case of technical difficulties in use of the software, answering procedural questions, providing recovery and backup information, and any other requirement that may be incidental/ancillary to the above. 13) Prompt receipt, analysis and reporting of reported deficiencies in the operation of the software and supply of information and advice on such deficiencies; 14) Installing/commissioning the software at the designated locations/changed designated location at no additional cost or fees or expenses to the Bank. Installing/commissioning the upgrades / new versions/ new releases of software at the designated locations/changed designated location at no additional cost or fees or expenses to the Bank. The requirements that are finalized with the Bank post the gap assessment phase and included in the business requirements document, will need to be provided by the Bank at no additional cost to the Bank. 15) Providing remedial support in case the software media is virus-inflicted at no additional cost or fees or expenses to the Bank; 16) Unscheduled, on call, corrective and remedial maintenance and support services; 17) Providing enhancements ; 18) Providing changes to the licensed software, which are of software fine-tuning in nature. Program Errors Correction: The Bidder shall use its best efforts in remedying any program error. All Program Errors shall be reported in accordance with the procedure prescribed in respect thereof and shall be accompanied by sufficient information including the input data that generated the program error so as to enable the Bidder to reproduce and verify the reported program error. On receipt of request together with all such information and data the Bidder shall use all-out efforts, consistent with the severity of the program error, to remedy such program error which is within the purview of the system logic, that it has been able to reproduce and verify. Such remedies may include providing instructions to the Bank to cure the program error or delivering updates at no additional cost. The Bidder warrants that any or all program errors that are reported will be remedied. In the event, the Bidder determines that the error reported/ problem notified in the support request in not a Program Error, it shall advise the Bank whether it can correct or assist in resolving such error/problem on a best effort basis. Updates / Upgrades / New releases / New versions: The Bidder/OEM from time to time has to release Updates/Upgrades/New releases/new versions and notify the Bank about the same. The Bidder/OEM agrees that all such Updates/Upgrades/New releases/new versions, as and when released during the term of warranty or ATS/AMC shall be provided to the Bank at no additional cost or fees or expenses including implementation cost during the contract period. Enhancements Page 86

1) All requests for Enhancements that may be required for any reason by the Bank shall be made in accordance with the procedures to be established by the Bank in this regard. 2) Any service provided by the Bidder, which is within the purview of the Software Maintenance and Support Services contemplated herein shall be at no additional cost or fees or expenses to the Bank. 3) The Bidder shall rectify any corruption in the application software or media at no extra cost to the Bank. 4) The Bidder shall ensure nil downtime of licensed software, prompt execution of customization and enhancement requirements, version control mechanism and also to develop smooth upgrades and version changes, ongoing training, user group meetings and feedback mechanism. 5) The Bidder agrees that licensed software support will include specifically the helpdesk, update, upgrade, technical guidance on usage of features and functionality, problem solving and troubleshooting including troubleshooting and operational errors/bug fixation, rectification of bugs, enabling features of the licensed software provided, providing additional user controlled reports, enabling parameterized features, future product information, migration path details and consultancy. The Bidder agrees that the support will be rendered in person in the normal course and in emergencies, support will be extended through telephone, fax, and email and that such instances should be an exception. 6.35 Software support 1) The Bidder shall provide complete technical support for software problems (all licensed software provided by the Bidder as a part of this tender or maintained by the Bidder as a part of this tender) and or questions, defect and non-defect related to Bank office automation products, systems and licensed applications. 2) The Bidder shall provide licensed software support including but not limited to problem tracking, problem source identification, problem impact (severity) determination, bypass and recovery support, problem resolution, management reporting and trend analysis and interfacing with other suppliers (as required) on behalf of the Bank. 3) Bidder shall provide a single-point-of-contact (via Helpdesk, E-mail address, web interface to log a service request) for Software support and respond to the initial request from the Bank within agreed service levels. 4) Bidder shall log any reported incident, identify it as defect or non-defect related, and tracks it till resolution. For all incidents, the Bidder will ask the Bank to assign a severity rank and handle it according to Service Levels given in Section 7 - Service Level Agreement. 5) For a defect related problem, depending on the Software, Bidder shall either: - Issue defect correction information, a restriction, or a bypass (provided the problem can be reproduced in that Software's specified operating environment), or - During resolution of a reported problem, Bidder shall provide the Bank with periodic status updates and also provide the Bank with a (monthly/weekly) report detailing the disposition of each reported problem, and other contents as desired by the Bank - The Bidder shall provide reasonable effort using available resources to assist the End Users at the Bank with Non-Standard Software support for problem determination and resolution 6) In the event of any dispute and or the commencement of arbitration proceedings the Vendor shall continue all facilities management services. 6.36 Application Management The Bidder should be able to provide Application Management services to manage software applications of the Bank. Page 87

The Bidder should be able to synchronize Application Management with IT infrastructure management. Deliverables for Application support should include: 1) Performance Monitoring & Management of application. 2) Installation & configuration of application 3) Application Patch management and version control. 4) Capacity Management. 5) Deployment of objects in Application server. 6) Up gradation & migration 7) Trouble shooting Application server product related issues 8) Troubleshooting Patch Management. 9) Start, stop, and manage Application Server services. 10) Configure and manage Application Web server. 11) Configure and manage HTTP. 12) Configure and use monitoring tools provided for Application Server. 13) Un-installation 14) SIP & performance management. 15) Logging a call with product Vendor 16) Version migration, testing and implementation 17) File Level Backup for Application Server 18) Backup & restoration management of application server. 19) Portal/content management. 20) User management 21) Support to known errors and problems 22) Monitor web / Application server availability 23) Monitor alert notifications, checking for impending problems, triggering appropriate actions 24) DR implementation 25) DR Drill conduction on quarterly basis Bidder is expected to provide relevant reports for the previous month in the 1st week of every month and same needs to be jointly reviewed by Bidder and Bank in next 3 working days. The reports should be benchmarked against the Service Levels defined in Service Level Agreement, and penalty should be calculated based on the level of deviation from Service levels defined. Bidder is required to submit the list of reports to track performance on service levels for all managed services under scope of this tender. 6.37 Patch Management Patch management should cover 1) Rollout planning. 2) Obtain Sign-off for Patch release implementation. 3) Communication, preparation and training to the team for Patch implementation. 4) Storage of controlled software in both centralized and distributed systems. 5) Patch Release, distribution and installation 6) Compliance & Adherence to Security Control Points as communicated by Bank. 7) Log history of patches applied is required to be maintained. 8) Firmware updates 6.38 Change Management The Bank may, at any time, by a written order given to the successful bidder, make changes within the general scope of the Contract in Technical and functional specifications No Change Request (CR) will be considered for any changes/amendments, in any reports/statements, requested by the Bank within 6 months from date of Go-Live. It shall be obligatory on the part of the vendor to comply with revised requirements of the Bank and arrange to deliver them within reasonable time, at no additional cost. Page 88

7. Annexures Annexure-1 Check List for Submission of Annexure Check List Sl. No. Description Annexure No. 1 Authorization Letter Format 2 2 Non-Disclosure Agreement Form 3 3 Check List for Submission of Eligibility Criteria 4 4 Profile of Bidder/Partner 5 5 Implementation Methodology 6 6 Reference Site Details 7 7 Past Experience 8 8 Team Profile 9 9 Training 10 10 Cover Letter for Commercial Bid 11 11 The Format for Furnishing the Details of Software 12 A 12 The Format for Furnishing the Details of Hardware (To be Purchased by the Bank) 12 B 13 Table for Arriving at the Total Ownership Cost 13 14 Bid Submission Covering Letter 14 15 Notification of Acceptance 15 16 Specimen Contract Form 16 17 Performance Bank Guarantee Format 17 18 Pre Bid Query Form 18 19 Self-Declaration Black Listing 19 20 Bid Security Form 20 21 Undertaking Document Correctness 21 22 Online Reverse Auction Compliance Statement 22 23 Functional and Technical requirements Section 5.1 & 5.2 24 Undertaking Legal 23 Page 89

Annexure-2 Authorization Letter Format (On Organization s Letter Head) Place: Date: To The Asstt. General Manager (IT), Allahabad Bank, Head Office, 2, Netaji Subhash Road, Kolkata 700 001, (W.B.) India Dear Sir, SUB: Authorization Letter for attending the Pre-Bid Meeting. Ref: Your RFP Ref. No: HO/DIT/ALM/2014-15/16 dated 20.11.2014 This has reference to your above RFP for implementation of ALM Solution according to the Industry Best Practices and Guidelines of RBI/BCBS on ALM. Mr. / Ms. is hereby authorized to attend the Pre-Bid Meeting & to discuss with you on the subject RFP on on behalf of our organization. The specimen signature is attested below: Specimen Signature of Mr. /Ms. --------------------------------------- -------------------------------------- Signature of Authorizing Authority Name & designation of Authorizing Authority Attested Photograph of the Authorized Representative ---------------------------------------- Name and designation of Attesting Authority Page 90

Annexure-3 NON DISCLOSURE AGREEMENT THIS AGREEMENT made and entered into at..on this the..day of 20... Between ALLAHABAD BANK, a body corporate constituted under the Banking Companies (Acquisition & Transfer of Undertakings) Act 1970, having its Corporate Office at --------------------------------------------- -----------------------------------------hereinafter called the BANK which term shall wherever the context so require includes its successors and assigns AND M/s.. Limited a company registered under the Companies Act having its registered office at.. Hereinafter called the Vendor which term shall wherever the context so require includes its successors and assigns, WITNESSETH: WHEREAS The Bank is inter alia engaged in the business of banking and has been procuring hardware/software for various banking operations. M/s. Limited has been engaged in the business of supply and installation of computer systems The parties intend to engage in discussions and negotiations concerning establishment of business relationship between them. In the course of discussions and negotiations, it is anticipated that the parties may disclose or deliver to the other certain or some of its trade secrets or confidential or proprietor information for the purpose of business relationship. NOW THERFORE THIS AGREEMENT WITNESSETH and it is hereby agreed by and between the parties hereto as follows: 1. Confidential information "Confidential Information" means and includes all data, documents and information disclosed or to be disclosed by either Party to other Party and its Representatives (as defined herein) (including information transmitted in written, electronic, magnetic or other form and also information transmitted orally or visually) and any and all information, in whole or in part, directly or indirectly, from such information including all notes, summaries, analyses, compilations and other writings. Confidential information shall include any copy, abstract, extract, sample, note or module thereof and electronic material or records. Receiving Party may use the information solely for and in connection with the Purpose. "Disclosing Party" means party who discloses Confidential Information. 2. Use of Confidential Information Each party agrees not to use the other s confidential information for any purpose other than for the specific purpose. Any other use of such confidential information by any party shall be made only upon the prior written consent from the authorized representative of the other party or pursuant to subsequent agreement between the Parties hereto. The receiving party shall not commercially use or disclose for commercial purpose any confidential information or any materials derived therefrom, to any other person or entity other than persons in the direct employment of the Receiving Party who have a need to access to and knowledge of the Page 91

confidential information solely for the purpose authorized above. The Receiving Party may disclose confidential information to consultants only if the consultant has executed non-disclosure agreement with the Receiving Party that contains terms and conditions that are no less restrictive than these and such consultant should also be liable to the original disclosing party for any unauthorized use or disclosure. The Receiving party shall take appropriate measures by instruction and written agreement prior to disclosure to such employees to assure against unauthorized use or disclosure. The Receiving Party agrees to notify the Disclosing Party immediately if it learns of any use or disclosure of the Disclosing party s confidential information in violation of the terms of this Agreement. Neither party shall make news release, public announcements, give interviews, issue or publish advertisements or Agreement, the contents/provisions thereof, other information relating to this agreement, the purpose, the Confidential information or other matter of this agreement, without the prior written approval of the other party. 3. Exemptions The obligations imposed upon either party herein shall not apply to information, technical data or know how whether or not designated as confidential, that: Is already known to the Receiving party at the time of the disclosure without an obligation of confidentiality. Is or becomes publicly known through no unauthorized act of the Receiving party. Is rightfully received from a third party without restriction and without breach of this agreement. Is independently developed by the Receiving party without use of the other party s Confidential Information and is so documented. Is disclosed without similar restrictions to a third party by the Party owning the confidential information. Is approved for release by written authorization of the disclosing party; or Is required to be disclosed pursuant to any applicable laws or regulations or any order of a court or a governmental body; provided, however that the Receiving party shall first have given notice to the Disclosing Party an made a reasonable effort to obtain a protective order requiring that the confidential information and / or documents so disclosed used only for the purposes for which the order was issued. 4. Term This agreement shall be effective from the date of the execution of this agreement and shall continue till expiration or termination of this agreement due to cessation of the business relationship between the parties. Upon expiration or termination as contemplated herein the Receiving party shall immediately cease any or all disclosures or uses of confidential information and at the request of the disclosing party, the receiving party shall promptly return or destroy all written, graphic or other tangible forms of the confidential information and all copies, abstracts, extracts, samples, note or modules thereof. The obligations of the receiving party respecting disclosure and confidentiality shall continue to be binding and applicable without limit until such information enters the public domain. 5. Title and Proprietary Rights Notwithstanding the disclosure of any confidential information by the Bank to the Vendor, the Bank shall retain title and all intellectual property and proprietary rights in the confidential information. No license under any trademark, patent or copyright or application for same which are or thereafter may be obtained by the Vendor is either granted or implied by the conveying of confidential information. Page 92

6. Return of Confidential Information Upon written demand of the disclosing party, the receiving party shall (I) cease using the confidential information (ii) return the confidential information and all copies, abstracts, extracts, samples, note or modules thereof to the disclosing party within seven (7) days after receipt of notice and (iii) upon request of the disclosing party, certify in writing that the receiving party has complied with the obligations set forth in this paragraph. The Vendor shall not make news releases, public announcements, give interviews, issue or publish advertisements or publicize in any other manner whatsoever in connection with this Agreement, the contents / provisions thereof, other information relating to this Agreement or information received under this Agreement, the Purpose, the Confidential Information or other matter of this Agreement, without the prior written approval of the Bank. The Vendor shall not reverse-engineer, de-compile, disassemble, or otherwise interfere with any software disclosed hereunder. 7. Remedies The receiving party acknowledges that if the receiving party fails to comply with any of its obligations hereunder, the disclosing party may suffer immediate, irreparable harm for which monetary damages may not be adequate. The receiving party agrees that, in addition to all other remedies provided at law or in equity, the disclosing party shall be entitled to injunctive relief hereunder. 8. Entire Agreement This agreement constitutes the entire agreement between the parties relating to the matter discussed herein and supersedes any and all prior oral discussion and/or written correspondence or agreements between the parties. This agreement may be amended or modified only with the mutual written consent of the parties. Neither this agreement nor any rights, benefits and obligations granted hereunder, shall be assignable or otherwise transferable. 9. Severability If any provision herein becomes invalid, illegal or unenforceable under any law, the validity, legality and enforceability of the remaining provisions and this agreement shall not be affected or impaired. 10. Indemnity The Vendor will indemnify the Bank against all actions, proceedings, claims, suits, damages and any other expenses for causes attributable to Vendor in connection with purchase of Hardware/software/goods under this contract. The total liability of the Vendor under the contract will not exceed the total cost of the project. 11. Dispute Resolution Mechanism In the event of any controversy or dispute regarding the interpretation of any part of this agreement or any matter connected with, arising out of, or incidental to the arrangement incorporated in this agreement, the matter shall be referred to arbitration and the award passed in such arbitration shall be binding on the parties. The arbitral proceeding shall be governed by the provisions of Arbitration and Reconciliation Act 1996 and the place of arbitration shall be Kolkata. 12. Jurisdiction The parties to this agreement shall submit to the jurisdiction of courts in Kolkata. Page 93

13. Governing Laws The provisions of this agreement shall be governed by the laws of India. 14. Authority to Execute the Contract Each person executing this Agreement warrants and represents that he or she has the authority to enter into this Agreement on behalf of the party whose name appears below their signature. In witness whereof, the parties hereto have set their hands through their authorized signatories. SIGNED: For and on behalf of BANK M/s..... Page 94

Annexure-4 Check List for Submission of Eligibility Criteria Sr. No. Eligibility Criteria Compliance (Yes/ No) Documentary Evidence to be Submitted to the BANK General Eligibility 1 The bidder should be in existence for 5 years as on 31st March 2014. (In case of mergers/acquisitions/restructuring or name change, the date of establishment of earlier/original firm would be taken into consideration.) Certificate of incorporation. 2 The bidder and the OEM should be a Profit making entity for last three financial years i.e.2011-12, 2012-13, and 2013-14. (If 2013-14 results are not finalized yet, then 2010-11, 2011-12, 2012-13 will be considered). Copies of Annual Reports in case of listed companies and Copies of audited balance sheets and P&L statements in case of others for past 3 financial years. 3 4 5 The Bidder must have a presence in India for at least 3 years and should have average revenues in excess of INR 50.00 Cr. (INR Fifty Crores) for the past 3 financial years i.e. 2011-12, 2012-13, and 2013-14. (If 2013-14 results are not finalized yet, then 2010-11, 2011-12, 2012-13 will be considered). The bidder should own the intellectual property rights of the product/solution or he should have rights from the owner, if not, the Bidder should have in place proper tieups, commercial agreements, authorised implementation partnerships etc. for development /resale/ customisation of software with the product bidder or any third party, whose software products are offered. The Bidder and OEM should not have been blacklisted at the time of submission by the Central/any of the State Governments/ statutory body/ regulatory body/indian Banks Association 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 for past 3 financial years. Credential letter on bank s letter head Credential letter on bank s letter head 6 The ALM Solution should have been procured by at least 2 Scheduled Commercial Banks amongst which at least Credential letter on bank s letter head Page 95

Sr. No. Eligibility Criteria Compliance (Yes/ No) Documentary Evidence to be Submitted to the BANK 1 should be a Public Sector Bank. 7 The ALM Solution should have been satisfactorily implemented by a Bank operating in India as on 30.06.2014. Credential letter on bank s letter head 8 The Bidder should have experience of implementing ALM solution in a Bank in India. The bidder needs to submit the credentials of team who will do the implementation. Page 96

Annexure - 5 Profile of Bidder Sl. No. Particulars Response 1 Company Name 2 Date of Incorporation 3 4 5 6 7 8 9 10 11 Name of Indian representative/office (indicate: own, dealer, distributor, JV) Company Head Office address * Contact person(s) * Designation * Phone Number * Mobile Number * Fax Number * E-mail Address Address of Indian representative/office * Contact person(s) * Phone Number * Fax Number * E-mail Address Number of Employees supporting the project In India: Marketing/Sales Technical Support Research and Development Implementation Outside India: Marketing/Sales Technical Support Research and Development Implementation Ownership structure (e.g. Inc., partnership) * Who are the primary shareholders? *State the major shareholders with percentage holding in case of limited companies. Location: Support (e.g. Asia Pacific, India) Since when has the support centre existed in India? Provide the range of services offered covering service description and different schemes available for: Customization Implementation Support Ongoing support (AMC, Help Desk) Training Any Others (Please Specify) State pending or past litigation if any within the last 3 years with details and explain reasons. Please also mention any claims/complaints received in the last three years. Enclose abstracts of the Balance sheet and P/L Account for the last three years Page 97

12 Independent analyst research report (if any) 13 Major changes in Management for last 3 years Page 98

Annexure - 6 Implementation Methodology Sl. No. Details of Methodology / Approach Response 1 1.1 The methodology section should adequately address the following stages of the project: Frequency and approach for periodic reporting on the progress of the project and actual status vis-à-vis scheduled status 1.2 Detailed Study of Current State, with detailed work steps and deliverables 1.3 Gap analysis including identification and resolution of gaps 1.4 Customization, development and necessary work around 1.5 Building up of interfaces with various applications currently used by the Bank 1.6 Setting up of the data centre and the disaster recovery site 1.7 User acceptance testing 1.8 Planning for roll out and identification of key issues that may arise along with proposed solutions 2 Timelines 3 Project Management Activities 4 5 Roles and responsibilities of proposed personnel both from the vendor and bank end. Following details with respect to the methodology followed by the vendor in Project Management for a Public/Private Sector Bank 5.1 Project Name 5.2 Project Location 5.3 Client Name 5.4 Client address 5.5 Client contact/reference person(s) 5.6 Project started (month/year) 5.7 Project elapsed time months 5.8 Man months effort 5.9 Project Size (No of branches, modules covered and any other relevant details) 5.1o Name of senior project staff 5.11 Nature of the Project 5.12 Project Management Methodology used 5.13 5.14 Role of the Bidder, whether complete end to end involvement or for a particular module Project detail ((Broad detail information about all activities handled, modules forming part of the ALM Solution of the Client Bank, associated activities, time lines activity wise and module wise may be detailed.) **The bidders are expected to provide crisp descriptive response against each point above Page 99

Annexure - 7 Reference Site Details The Reference Site details are to be provided in the following format: Particulars Name of the Bank/ Financial Institution Address of the Organization Annual Turnover of the Organization for the Financial Year 2013-14 Date of Commencement of Project Date of Completion of Project Scope of Work for Solution Partner for the Project Project Start Date and End Date Response List all the modules/components of the system being used. Type of Architecture in which the system has been implemented. Implementation details e.g. Number of Sites, time taken for Operationalization, volumes of processing etc. State the duration of the implementation Number of users and the geographical spread of the implementation Average Team size on site for project implementation (SI & OEM Team) Contact Details from the Bank/Financial Institution for reference Name of the Contact Person Designation Phone Number/e-mail The bidder has to submit a consent letter for conducting a reference site visit by Allahabad Bank s project evaluation team. The letter has to be on the letter head of the concerned Bank/Financial Institution. Page 100

Annexure - 8 Past Experience List of major customers where the proposed ALM solution has been implemented/under implementation in India/outside and their reference details: Sl. No. Name and complete Postal Address of the Customer Name & Brief scope of work done by OEM (specify the size of the Bank, the approaches supported etc.) Name & Brief scope of work done by SI (specify the size of the Bank, the approaches supported etc.) Attach Reference Letter Contact Details (Name, Designation, Phone, Email) Project Status (Completed/Under Implementation, Start Date, End Date) *In cases where SI acts as bidder, while counting the number of Banks for the purpose of assigning marks under this parameter only the number of Banks where SI has customized the software of the OEM shall be taken. (Enclose necessary documentary proof such as reference letter) Page 101

Annexure - 9 Project Team Profiles The general information on staff strength of the bidder/partner should be furnished in the following format & Specific information to be furnished in respect of each team member 1 Name a Brief Introduction (in bullets) 2 Date of Birth 3 Phone Number 4 Position in the firm 5 6 a b c d e f g Total years of post-qualification work experience Employment Record (Provide Company name, position held, duration, clients worked) 7 Number of years with the firm 8 Details of relevant assignments undertaken (include both past and current employment projects and highlight BFSI experience, if any) (Provide scope, duration, client name and status of assignment) a Duration of engagement in the assignment (In months) Location Client Name Main project title and features Position held Activities performed Page 102

Duration of engagement in the assignment (In months) b Location Client Name Main project title and features Position held Activities performed Degree Obtained Year of Degree obtained Institution 9 Education 10 Certifications (if any) a b c Page 103

Annexure - 10 Training A. General Information Particulars No: of Implementation trainings undertaken by the Bidder/partner Response A brief description on the Training approach taken by the Bidder/partner Names and experience of all trainers with the Bidder who would be involved with the Project B. Specific information to be furnished in respect of each training session* Particulars Name of the Bank where product was implemented and the training conducted Date and place where training conducted Training audience Duration of training Location Response *This information should be backed by the documentary proof in the customer-bank s letter head. Page 104

Annexure - 11 Cover Letter for Commercial Bid (Post Reverse Auction) Note: This Cover Letter for Commercial Bid (Post Reverse Auction) from the Bidder should be on the letterhead of the Bidder and should be signed by an authorized person. Date: To The Asstt. General Manager (IT) Allahabad Bank, Head Office, 2, Netaji Subhash Road, Kolkata 700 001, (W.B.) India Sub: Supply, Deployment, Customization, Implementation, Maintenance and Support of Asset Liability Management Solution Ref: Bid Document No.: Dated: Having examined the Bidding Documents including Addenda Nos.... (Insert numbers), the receipt of which is hereby duly acknowledged, we, the undersigned, offer to supply, install and maintain inconformity with the said Bidding documents for the sum of..... (Total amount in words and figures) or such other sums as may be ascertained in accordance with the commercial bid for hardware and software and total cost of ownership attached herewith and made part of this Proposal. We undertake, if our bid is accepted, to deliver the goods in accordance with the delivery schedule specified in the Schedule of Requirements. If our bid is accepted, we will obtain the Guarantee of a Bank for a sum equivalent to 10% of the total Contact Amount for the due performance of the Contract, in the form prescribed by the Bank. We agree to abide by this for the bid validity period specified and it shall remain binding upon us and may be accepted at any time before the expiration of that period. We agree to extend the Bid Validity Period and Bank Guarantee towards Earnest Money Deposit, if required. Until a formal contract is prepared and executed, this bid, together with your notification of award, shall constitute a binding Contract between us. We undertake that, in competing for (and, if the award is made to us, in executing) the above contract, we will strictly observe the laws against fraud and corruption in force in India. We understand that bank is not bound to accept the lowest or any bid bank may receive. We confirm that we comply with the qualification criteria of the bidding documents and are submitting proof of the same along with bid. Dated this... day of..... 201......... (In the Capacity of) Duly authorized to sign bid for and on behalf of (Name & Address of Bidder)...... Signature Mobile: Page 105

Email: Annexure-12 A Format for furnishing the details of Software (Bill of Material) The bidder shall furnish the details of Hardware, Software and Application Software for ALM solution in the below mentioned format. 1) The format for furnishing details of required Software Sl. No Description Make / Model/Part No./Version Qty I Licenses for proposed software for ALM Solution A Licenses for Asset Liability Management System # B Licenses for any other Software/Tool # The solution license should be perpetual based and should be Enterprise Edition ( not number of users based) Dated (Signature) (In the capacity of) Duly authorized to sign bid for & on behalf of (Name & Address of the Bidder) Page 106

Annexure-12 B Format for furnishing the details of Hardware (to be purchased by the Bank) The bidder shall furnish the details of Hardware/other items required for successful implementation of the ALM solution in the below mentioned format. A Hardware (Details to be provide by the bidder, to be purchased by the Bank) 1 Server DC site 1.1 Database Server for Asset Liability Management 1.2 Application Server for Asset Liability Management, if additionally needed above the 1.3 Web Server for Asset Liability Management, if any 1.4 Any other (Please Specify) 2 Server DR site 2.1 Database Server for Asset Liability Management 2.2 Application Server for Asset Liability Management, if additionally needed above the 2.3 Web Server for Asset Liability Management, if any 2.4 Any other (Please Specify) 3 Server UAT (only for DC) 3.1 Database Server for Asset Liability Management 3.2 Application Server for Asset Liability Management, if additionally needed above the 3.3 Web Server for Asset Liability Management, if any 3.4 Any other (Please Specify) B Database licenses 1 RDBMS DC site 1.1 RDBMS* for Asset Liability Management Database Server 1.2 Any other (Please Specify) 2 RDBMS DR site 2.1 RDBMS* for Asset Liability Management Database Server Page 107

2.2 Any other (Please Specify) 3 RDBMS UAT Servers 3.1 RDBMS* for Asset Liability Management Database Server 3.2 Any other (Please Specify) C Third Party Software (Other than RDBMS) 1 Operating System DC site 1.1 OS for Application Server 1.2 OS for Database Server 1.3 Any other (Please Specify) 2 OS DR site 2.1 OS for Application Server 2.2 OS for Database Server 2.2 Any other (Please Specify) 3 OS UAT Servers 3.1 OS for Application Server 3.2 OS for Database Server 3.2 Any other (Please Specify) D ** Any other Requirement of hardware/software/network & Security Equipments, LAN, Bandwidth etc. To be clearly mentioned. ** Any other requirements such as Networking Equipments, Peripherals, LAN, bandwidth etc. to be advised to the Bank with details. Dated (Signature) (In the capacity of) Duly authorized to sign bid for & on behalf of (Name & Address of the Bidder) Page 108

Annexure-13 Table for Arriving at the Total Ownership Cost TABLE-A: Cost of Application Software Sl. No Item description Application Cost - Licenses for Asset Liability Management 1 System # - 2 Any other supporting software/tool (Please Specify) Total Cost of Application Software TABLE-B: Cost of Implementation, Training, Warranty etc. Unit Price Total Price Sl. No Item description 1 Cost of Implementation (Installation, Configuration, Customization, Training etc.) - DC - DR 2 Any other Cost (Please Specify) 3 Cost of Comprehensive Warranty/ATS for three years in Terms of the RFP Total Cost of Implementation, Training, Warranty etc. TABLE-C: Cost of AMC/ATS for two years after the warranty Unit Price Total Price Sl. No Item description Amount 1 Cost of AMC for ALM Solution for next 2 years after expiry of warranty Any Other Cost (Please Specify) Total Cost of AMC after the warranty TABLE-D: Cost of FM for Five years Sl. No Item description Amount 1 Cost of FM Services per year (Vendor must provide the details of resources deployed for FM alongwith activities covered under FM) FM Cost per year should be fixed for five years. Any Other Cost (Please Specify) Total Cost of FM Services for Five years Page 109

Table E: Total Cost of Ownership/Total Bid Price (Amt. in Indian Rupees only) Particulars Amount TOTAL PAYABLE IN INDIAN RUPEES AS PER TABLE A TOTAL PAYABLE IN INDIAN RUPEES AS PER TABLE B TOTAL PAYABLE IN INDIAN RUPEES AS PER TABLE C TOTAL PAYABLE IN INDIAN RUPEES AS PER TABLE D TOTAL BID PRICE (A+B+C+D) Amount in words: # All the above prices should be inclusive of all the taxes except Sales Tax/Vat, Entry Tax /Octroi and Service Tax. *Cost of FM services for five years will be taken for TCO calculation. However Bank may discontinue FM services at any point of time at its discretion. Page 110

Annexure-14 Bid submission Covering Letter Note: This Bid Offer Covering letter should be on the letter head of the Bidder and should be signed by an authorized person. Date: To Asstt. General Manager (IT) Allahabad Bank, Head Office, 2, Netaji Subhash Road, Kolkata 700 001, (W.B.) India Dear Sir/ Madam, Subject: Response to RFP Ref No: HO/DIT/ALM/2014-15/16 With reference to the RFP, having examined and understood the instructions, terms and conditions forming part of the RFP, we hereby enclose our offer for the Supply, Customization, Deployment, Maintenance and Support of Asset Liability Management Solution in accordance with the International Industry Best Practices and Guidelines of RBI/BCBS for ALM, We agree and undertake that, if our Bid is accepted, we shall deliver, install and commission the Solution in accordance with the Requirements specified within the RFP for Solution of ALM within the timeframe specified, starting from the date of receipt of notification of award from Allahabad Bank. We acknowledge having received the following addenda to the bid document: If our Bid is accepted, we will obtain performance guarantee of a Bank for a sum equivalent to 10 percent of the Contract Price for the due performance of the Contract, in the form prescribed by the Bank. All the details mentioned by us are true and correct and if Bank observes any misrepresentation of facts on any matter at any stage, Bank has the absolute right to reject the bid / proposal and disqualify us from the selection process. We confirm that the offer is in conformity with the terms and conditions as mentioned in RFP. We undertake that, in competing for (and, if the award is made to us, in executing) the above contract, we will strictly observe the laws in force in India. We are also aware that Allahabad Bank has also right to re-issue / recommence the bid, to which we do not have right to object and have no reservation in this regard; the decision of Allahabad Bank in this regard shall be final, conclusive and binding upon us. We confirm that our company/system integrator/other partners participating in this bidding as part of the consortium have not been black listed/banned by a regulatory authority and any previous ban is not in force at present. Page 111

We enclose a Demand Draft /Bankers' Cheque bearing No. dated /../20 drawn by.. Bank, branch, in favour of Allahabad Bank, payable at Kolkata for a sum of Rs 25,000/- (Rupees Twenty Five Thousand Only) towards non-refundable Bid Submission fee. Yours faithfully, (Name of Authorized Signatory) (Designation) Duly authorized to sign Bid for and on behalf of Page 112

Annexure-15 Notification of Acceptance Note: This letter should be on the letterhead of the Bidder and should be signed by an authorized person. Date: To The Asstt. General Manager (IT) Allahabad Bank, Head Office, 2, Netaji Subhash Road, Kolkata 700 001, (W.B.) India Dear Sir/ Madam, Subject: Response to RFP Ref No: Ref. No. HO/DIT/ALM/2014-15/16 dated 20.11.2014 REF: Your Letter No: - Date. This has reference to your letter on the subject, notifying us about the selection of our bid. We hereby convey our absolute, unconditional and unqualified acceptance for the work and activities as per the Scope of Work mentioned in the subject RFP. Signature of Authorised Person (Seal) Page 113

Annexure-16 CONTRACT FORM THIS AGREEMENT made and entered into at..on this the..day of 201.. Between ALLAHABAD BANK, a body corporate constituted under the Banking Companies (Acquisition & Transfer of Undertakings) Act 1970, having its Corporate Office at --------------------------------------------- -----------------------------------------hereinafter called the BANK which term shall wherever the context so require includes its successors and assigns WHEREAS the Purchaser invited bids vide RFP No. HO/DIT/ALM/2014-15/16 dated 20.11.2014 for certain Goods and ancillary services viz.,... (Brief Description of Goods and Services) and has accepted a bid by the Supplier for the provision of those goods and services in the sum for... (Contract Price in Words and Figures) (hereinafter called the Contract Price ). NOW THIS AGREEMENT WITNESSETH AS FOLLOWS: 1. In this Agreement words and expressions shall have the same meanings as are respectively assigned to them in the Conditions of Contract referred to. 2. The following documents shall be deemed to form and be read and construed as part of this Agreement, viz.: a. Bid submission Covering Letter and the Total Ownership Cost submitted by the Bidder; b. The Functional Requirements c. The Technical Requirements d. The RFP e. The Service Level Agreement (SLA) 3. In consideration of the payments to be made by the Purchaser to the Supplier as hereinafter mentioned, the Supplier hereby covenants with the Purchaser to provide the goods and services and to remedy defects therein in conformity in all respects with the provisions of the Contract. 4. The Purchaser hereby covenants to pay the Supplier in consideration of the provision of the goods and services and the remedying of defects therein, the Contract Price or such other sum as may become payable under the provisions of the Contract at the times and in the manner prescribed by the Contract. Brief particulars of the goods and services which shall be supplied / provided by the Supplier are as under: S. No. 1 2 3 4 5 TOTAL VALUE: Description of the software/services Primary Site DR Qty Unit Price Total Price Page 114

5. The Vendor shall provide technical support for the software application systems supplied under this contract, and will have overall responsibility of the performance, functionality and operation of the systems under this contract. Any supporting software provided /installed /configured by the Vendor shall be maintained /fine-tuned/ parameterized by the Vendor, from time to time, so that the solution delivers optimal performance. The Bank shall have the Right to use supporting software provided /installed /configured by the Vendor and/or software application systems supplied under this contract of Sale after the expiry of the Warranty period under this contract and it shall be at liberty to use/ run the said software solutions with the help/support of its in house IT Officers or through any other out sourcing service Agencies. The Vendors shall not have any right to question or object for continuation of the use of such software or software solutions irrespective of entering into any AMC with the Vendor after the expiry period or not. The Bank will decide at its sole discretion after expiry of the period under this contract either to enter into an AMC with the Vendor or not. The Vendor shall not have any right to challenge the decision of the Bank in any manner or in any proceedings. 6. The Vendor shall ensure the meeting of the Security features, the standards and procedures as per Bank s IT Security Policy and procedures should be meticulously followed, in line with prevailing Industry Standards. In case of the any violation of the industry Standards, if the Bank has to incur any liability or penalty sanctioned by any Statutory/Supervisory Authority, the Vendor shall reimburse the same. 7. The Vendor has to provide the Bank with the proper backup and recovery procedure, with necessary documents so as to meet any exigencies. 8. The Vendor should ensure that all verification processes in the software solutions should be governed by maker checker controls. DELIVERY SCHEDULE: IN WITNESS whereof the parties hereto have caused this Agreement to be executed in accordance with their respective laws the day and year first above written. Signed, Sealed and Delivered by the said... (For Allahabad Bank) in the presence of:... Signed, Sealed and Delivered by the said... (For the Supplier) in the presence of:... Page 115

Annexure-17 Performance Bank Guarantee Format Bank Guarantee No: Bank Guarantee Amount: Expiry Date: Claim Period: Account To The Asstt. General Manager (IT) Allahabad Bank, Head Office, 2, Netaji Subhash Road, Kolkata 700 001, (W.B.) India Date: DD-MM-YYYY Dear Sir, WHEREAS...(Company Name) registered under the Indian Companies Act 1956 and having its Registered Office at... India (hereinafter referred to as the VENDOR ) proposes to tender and offer in response to tender Ref... dated 20.11.2014 (hereinafter called the TENDER ) AND WHEREAS, in terms of the conditions as stipulated in the TENDER, the VENDOR is required to furnish a Bank Guarantee in lieu of the Earnest Money Deposit (EMD), issued by a scheduled commercial bank in India in your favor to secure the order of the RFP in accordance with the RFP Document (which guarantee is hereinafter called as BANK GUARANTEE ) AND WHEREAS the VENDOR has approached us,... for providing the BANK GUARANTEE. AND WHEREAS at the request of the VENDOR and in consideration of the proposed TENDER to you, WE,... having... Office at..., India have agreed to issue the BANK GUARANTEE. THEREFORE, WE,..., through our local office at... India furnish you the Bank GUARANTEE in manner hereinafter contained and agree with you as follows: We..., undertake to pay the amounts due and payable under this Guarantee without any demur, merely on demand from you and undertake to indemnify you and keep you indemnified from time to time to the extent of Rs...(Rupees...only) an amount equivalent to the EMD against any loss or damage caused to or suffered by or that may be caused to or suffered by you on account of any breach or breaches on the part of the RFP of any of the terms and conditions contained in the RFP and in the event of the VENDOR commits default or defaults in carrying out any of the work or discharging any obligation in relation thereto under the RFP or otherwise in the observance and performance of any of the terms and conditions relating Page 116

thereto in accordance with the true intent and meaning thereof, we shall forthwith on demand pay to you such sum or sums not exceeding the sum of Rs...(Rupees... only) as may be claimed by you on account of breach on the part of the VENDOR of their obligations in terms of the RFP. Notwithstanding anything to the contrary contained herein or elsewhere, we agree that your decision as to whether the VENDOR has committed any such default or defaults and the amount or amounts to which you are entitled by reasons thereof will be binding on us and we shall not be entitled to ask you to establish your claim or claims under Bank Guarantee but will pay the same forthwith on your demand without any protest or demur. This Bank Guarantee shall continue and hold good until it is released by you on the application by the VENDOR after expiry of the relative guarantee period of the RFP and after the VENDOR had discharged all his obligations under the RFP and produced a certificate of due completion of work under the said Tender and submitted a No Demand Certificate provided always that the guarantee shall in no event remain in force after the day of... without prejudice to your claim or claims arisen and demanded from or otherwise notified to us in writing before the expiry of the said date which will be enforceable against us notwithstanding that the same is or are enforced after the said date. Should it be necessary to extend Bank Guarantee on account of any reason whatsoever, we undertake to extend the period of Bank Guarantee on your request under intimation to the VENDOR till such time as may be required by you. Your decision in this respect shall be final and binding on us. You will have the fullest liberty without affecting Bank Guarantee from time to time to vary any of the terms and conditions of the Tender or extend the time of performance of the Tender or to postpone any time or from time to time any of your rights or powers against the VENDOR and either to enforce or forbear to enforce any of the terms and conditions of the said RFP and we shall not be released from our liability under Bank Guarantee by exercise of your liberty with reference to matters aforesaid or by reason of any time being given to the VENDOR or any other forbearance, act or omission on your part of or any indulgence by you to the VENDOR or by any variation or modification of the RFP or any other act, matter or things whatsoever which under law relating to sureties, would but for the provisions hereof have the effect of so releasing us from our liability hereunder provided always that nothing herein contained will enlarge our liability hereunder beyond the limit of Rs...( Rupees...only ) as aforesaid or extend the period of the guarantee beyond the said day of... unless expressly agreed to by us in writing. The Bank Guarantee shall not in any way be affected by your taking or giving up any securities from the VENDOR or any other person, firm or company on its behalf or by the winding up, dissolution, insolvency or death as the case may be of the VENDOR. In order to give full effect to the guarantee herein contained, you shall be entitled to act as if we were your principal debtors in respect of all your claims against the VENDOR hereby guaranteed by us as aforesaid and we hereby expressly waive all our rights of surety ship and other rights, if any, which are in any way inconsistent with any of the provisions of Bank Guarantee. Page 117

Subject to the maximum limit of our liability as aforesaid, Bank Guarantee will cover all your claim or claims against the VENDOR from time to time arising out of or in relation to the said RFP and in respect of which your claim in writing is lodged on us before expiry of Bank Guarantee. Any notice by way of demand or otherwise hereunder may be sent by special courier, telex, fax or registered post to our local address as aforesaid and if sent accordingly it shall be deemed to have been given when the same has been posted. The Bank Guarantee and the powers and provisions herein contained are in addition to and not by way of limitation of or substitution for any other guarantee or guarantees here before given to you by us (whether jointly with others or alone) and now existing uncancelled and that Bank Guarantee is not intended to and shall not revoke or limit such guarantee or guarantees. The Bank Guarantee shall not be affected by any change in the constitution of the VENDOR or us nor shall it be affected by any change in your constitution or by any amalgamation or absorption thereof or therewith but will ensure to the benefit of and be available to and be enforceable by the absorbing or amalgamated company or concern. The Bank Guarantee shall come into force from the date of its execution and shall not be revoked by us any time during its currency without your previous consent in writing. We further agree and undertake to pay you the amount demanded by you in writing irrespective of any dispute or controversy between you and the VENDOR. Notwithstanding anything contained herein above; i) Our liability under this Guarantee shall not exceed Rs...( Rupees...only) ; ii) This Bank Guarantee shall be valid up to and including the date... ; and iii) We are liable to pay the guaranteed amount or any part thereof under this Bank Guarantee only and only if you serve upon us a written claim or demand on or before the expiry of this guarantee. We have the power to issue this Bank Guarantee in your favour under the Memorandum and Articles of Association of our Bank and the undersigned has full power to execute this Bank Guarantee under the Power of Attorney issued by the Bank. For and on behalf of Branch Manager Seal & Address Page 118

Annexure 18 Pre Bid Query Format Sl. No Section & Clause Ref. No. / Appendix No. / Annexure No Page No. RFP Text Query Response to Query (to be left blank by the vendor) Page 119

Annexure 19 SELF DECLARATION BLACKLISTING To The Asstt. General Manager (IT) Allahabad Bank, Head Office, 2, Netaji Subhash Road, Kolkata 700 001, (W.B.) India Dear Sir, Sub: Supply, Implementation, Customization, Deployment, Maintenance and Support of Systems. Ref: Bid Document No. Dated. We hereby certify that, we have not been blacklisted by any Government Dept. / PSU / Banks for non-implementation / non delivery of the order / not providing support currently. Signature of Authorized Official Name and Designation with Office Seal Place: Date: Page 120

Annexure-20 BID SECURITY FORM Whereas... (Hereinafter called the Bidder ) who intends to submit bid dated... (date of submission of bid ) for the supply of... (name and/or description of the goods) in response to Allahabad Bank s Request for Proposal (RFP) No. HO/DIT/ALM/2014-15/16 dated 20.11.2014 (Hereinafter called the Bid ). KNOW ALL PEOPLE by these presents that We... (Name of Bank) of... (Name of Country), having our registered office at... (address of Bank) (hereinafter called the Bank ), are bound unto Allahabad Bank (hereinafter called the Beneficiary ) in the sum of for which payment will and truly to be made to the said Beneficiary, the Bank binds itself, its successors, and assigns by these presents. Sealed with the Common Seal of the said Bank this day of 201. THE CONDITIONS of this obligation are: 1. If the Bidder (a) withdraws its Bid during the period of bid validity or (b) does not accept the correction of errors in accordance with the Instructions to Bidders; or 2. If the Bidder, having been notified of the acceptance of its bid by the Purchaser during the period of bid validity: (a) fails or refuses to execute the Contract Form if required; or (b) fails or refuses to furnish the performance security, in accordance with the Instruction to Bidders. We undertake to pay the Purchaser up to the above amount upon receipt of its first written demand, without the Beneficiary having to substantiate its demand, provided that in its demand the Beneficiary will note that the amount claimed by it is due to it, owing to the occurrence of one or both of the two conditions, specifying the occurred condition or conditions. This Guarantee will remain in force up to and any demand in respect thereof should reach the Bank not later than. Notwithstanding any other term contained herein: 1. This guarantee shall be valid only upto.(insert guarantee End Date) whereupon it shall automatically expire irrespective of whether the original guarantee is returned to the Bank or not: and 2. The total liability of Bank under this guarantee shall be limited to Rs. (Rs only). (Signature of the Authorised Official of Bank) NOTE: 1. Supplier should ensure that the seal and Code No. of the signatory is put by the bankers, before submission of the Bank Guarantee. 2. Bank Guarantee issued by Banks located in India shall be on a Non-Judicial Stamp Paper of requisite value. Page 121

Annexure 21 Undertaking Document Correctness This is to certify that the information furnished herein and as per the documents submitted (hard copy and soft copy) is true and accurate and nothing has been concealed or tampered with. We further certify that the contents of the soft copy are same as those provided in the hard copy. We have gone through all the conditions of RFP document and are liable to any punitive action for furnishing false information / documents. Dated this day of 201_ Signature (Company Seal) In the capacity of Duly authorized to sign bids for and on behalf of: Page 122

Annexure 22 ONLINE REVERSE AUCTION COMPLIANCE STATEMENT To Asstt. General Manager (IT),, Allahabad Bank, Head Office, 2, N.S. Road, Kolkata 700 001 West Bengal (To be submitted by all the technically qualified bidders) Date: ---------- DECLARATION 1 We.. (Name of the company) hereby confirm having submitted our bid for Participating in Bank s RFP Ref No. HO/DIT/ALM/2014-15/16 dated 20.11.2014 for Appointment of Vendor for Supply, Deployment, Customization, Implementation, Maintenance and Support of Asset Liability Management Solution. 2 We confirm having read and understood the terms and conditions of the RFP as well as the Procedures relating to the process. 3 We hereby undertake and agree to abide by all the terms and conditions stipulated by the Allahabad Bank in the RFP document including all Annexures/Appendixes and the Procedure, Business Rules and Terms and Conditions of E-tendering/Online Reverse Auction process. 4 We shall participate in the E tendering conducted by (auction service provider retained by the Bank) and submit our commercial quote through online Reverse Auction. In doing so, we shall abide by the procedures prescribed for online auction by the Bank and auction company. 5 We, hereby confirm that we will honor the Bids placed by us during the E tendering/online Reverse Auction process, failing which we shall be liable for any other consequential action that may be taken by the Bank including any debarment from participation in future procurement by the Bank. 6 We confirm having nominated our representative (Shri/Smt/Ms designated as.of our company to participate in the E tendering/online Reverse Auction process on behalf of the company. We accordingly authorize Bank and / or the Auction Company to issue user ID and password to the above named official of the company. We undertake that the company shall be bound by the actions made by him during the E tendering process and thereafter. 7 We undertake to submit the confirmation of last bid price and price breakup by us to the Auction Company /Bank within one working day of the completion of event and any other specific requirement indicated in the RFP. Name & Address of Company: Date: Signature with company seal Name & Designation of Authorized Representative: Signature of Authorized Representative: Page 123

Annexure 23 Undertaking Legal We hereby declare that no inquiries or investigations have been threatened, commenced or pending against us or any other member of the consortium by any statutory or regulatory or investigative agencies or lending institutions. Dated this day of Signature (Company Seal) In the capacity of Duly authorized to sign bids for and on behalf of: Page 124