market risk management policy - allahabad bank€¦ · allahabad bank rfp ref. no....

Allahabad BankRFP Ref. No. HO/DIT/ALM/2014-15/16

Department of Information Technology

Request for ProposalFor

SUPPLY, DEPLOYMENT, CUSTOMIZATION,IMPLEMENTATION, MAINTENANCE AND SUPPORT OF

ASSET LIABILITY MANAGEMENT (ALM) SOLUTION

Allahabad BankHead Office

Department of Information Technology2, N. S. Road

Kolkata – 700 001

RFP Ref. No.: HO/DIT/ALM/2014-15/16Dated: 20th November, 2014



ContentsDisclaimer..................................................................................................................................51. Invitation for Bids..............................................................................................................62. Instruction to Bidders (ITB) ..............................................................................................82.1 About Allahabad Bank........................................................................................................ 82.2 Objective of RFP................................................................................................................. 82.3 Responsibilities of Bidder................................................................................................... 92.4 Eligibility Criteria ............................................................................................................. 122.5 Preparation & Submission of Bids.................................................................................... 132.6 Opening of Technical Bids ............................................................................................... 162.7 Bid Security ...................................................................................................................... 172.8 Modification and Withdrawal of Bids .............................................................................. 182.9 Rejection / Acceptance of Bid .......................................................................................... 182.10 Cancellation of Bid ........................................................................................................... 182.11 Period of Validity of Bids ................................................................................................. 182.12 Pre-Bid Meeting................................................................................................................ 183. Selection Strategy...........................................................................................................203.1 Objective ........................................................................................................................... 203.2 Evaluation of Technical Bid ............................................................................................. 203.3 Scoring Methodology for Functional Requirements (FR) and TechnicalRequirements (TR)........................................................................................................................ 213.4 Scoring Methodology for Product Demonstration and Bid Presentation (PB)................. 223.5 Scoring Methodology for Approach, Methodology (AM) & Past Experience................. 223.6 Scoring Methodology for Site Visits (SV)........................................................................ 233.7 Disqualification Parameters in Technical Bid Evaluation ................................................ 233.8 Evaluation of Indicative Commercial Bid & Online Reverse Auction............................. 233.9 Reverse Auction................................................................................................................ 244. Scope of Work .................................................................................................................254.1 Broad scope....................................................................................................................... 254.2 Detailed scope................................................................................................................... 25

4.2.1. Gap identification & Resolution ....................................................................254.2.2. Design of Solution .........................................................................................264.2.3. Parameterization, Configuration and Customization of Software .................264.2.4. Testing............................................................................................................274.2.5. Training..........................................................................................................274.2.6. Implementation ..............................................................................................284.2.7. Information Security ......................................................................................294.2.8. Facilities Management Services (FMS).........................................................29

5. Functional & Technical Requirement.............................................................................315.1 Functional requirement for ALM Solution ....................................................................... 315.2 Technical Requirement ..................................................................................................... 605.3 Format Specification......................................................................................................... 676. Terms & Conditions of Contract ....................................................................................68



6.1 Source Code ...................................................................................................................... 686.2 Software Delivery & Installation ...................................................................................... 686.3 Acceptance of Software .................................................................................................... 686.4 Inspection and Tests.......................................................................................................... 696.5 Information Ownership..................................................................................................... 696.6 Adherence to Standards .................................................................................................... 706.7 Security Configuration, Monitoring and Audit................................................................. 706.8 Considerations for Proposed Hardware & Software to support Solution ......................... 706.9 Performance Guidelines.................................................................................................... 716.10 Confidentiality .................................................................................................................. 716.11 Disaster Recovery System ................................................................................................ 716.12 Service Level Agreement (SLA) ...................................................................................... 726.13 Software Licenses for Solution......................................................................................... 736.14 Hardware Requirement ..................................................................................................... 736.15 Environments .................................................................................................................... 746.16 Phased Implementation..................................................................................................... 746.17 Project Documentation and Manuals ................................................................................ 746.18 Interface & Integration Requirements .............................................................................. 756.19 Warranty & Annual Maintenance ..................................................................................... 766.20 Training............................................................................................................................. 786.21 Obligations of the Bidder.................................................................................................. 796.22 Termination for Default .................................................................................................... 806.23 Exit Option........................................................................................................................ 806.24 Force Majeure ................................................................................................................... 816.25 Performance Security........................................................................................................ 816.26 Liquidated Damages ......................................................................................................... 826.27 Settlement of Disputes ...................................................................................................... 826.28 Time Schedule .................................................................................................................. 836.29 Payment............................................................................................................................. 836.30 Paying Authority............................................................................................................... 846.31 System Administration...................................................................................................... 846.32 Database Access................................................................................................................ 846.33 Software Maintenance ...................................................................................................... 846.34 Software Maintenance and Support Services during Warranty and AMC ....................... 856.35 Software support ............................................................................................................... 876.36 Application Management.................................................................................................. 876.37 Patch Management............................................................................................................ 886.38 Change Management ........................................................................................................ 887. Annexures........................................................................................................................89Annexure-1 ................................................................................................................................... 89Annexure-2 ................................................................................................................................... 90



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



Disclaimer

The information contained in this Request for Proposal (RFP) document or information providedsubsequently to bidder(s) whether verbally or in documentary form by or on behalf of AllahabadBank is provided to the bidder(s) on the terms and conditions set out in this RFP document and allother 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 toany parties other than the applicants who are qualified to submit the bids (“bidders”). The purpose ofthis 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 shouldconduct its own investigations and analysis and should check the accuracy, reliability andcompleteness 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. AllahabadBank may in its absolute discretion, but without being under any obligation to do so, update, amendor supplement the information in this RFP.



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, NetajiSubhas Road, Kolkata-700001, India, hereinafter called “The Purchaser” or “Bank”, whichterm 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 Biddocument, hereinafter called Request for Proposal, or “RFP”, to invite Techno-Commercialbids from eligible Bidder for Supply, Deployment, Customization, Implementation,Maintenance and Support of Asset Liability Management Solution in accordance with theIndustry Best Practices and for complying with Guidelines of RBI/BCBS/IBA/GOI as also forMIS requirements pertaining to ALM.

2. A complete set of RFP documents may be purchased by any interested Bidder on thesubmission of a written application, in duplicate, from The Asstt. General Manager (IT)Allahabad Bank, Head Office, Department of Information Technology, 2nd Floor, 2,Netaji Subhas Road, Kolkata – 700 001, India upon payment of non-refundable fee of INR25,000/- (INR Twenty Five Thousand only) in the form of Demand Draft or Banker’s Chequein favour of ‘Allahabad Bank’, payable at Kolkata. Only the Bidders, who purchase the RFPin their names, are eligible for submission of bid.

The RFP may be obtained from the above address during office hours on all working dayseither in person or by post.

3. A complete set of RFP may also be downloaded from Bank’s official websitewww.allahabadbank.in. The Bidder who has downloaded the RFP from above website, isrequired to submit a non-refundable fee of INR 25000/- (INR Twenty Five Thousand only) inthe form of Demand Draft or Banker’s Cheque, in favour of ‘Allahabad Bank’ payable atKolkata, during office hours within the last date and time of submission of bid, failing whichthe Bid of the concerned Bidder will not be entertained. This tender is not transferable. Onlythe Bidders who have officially purchased this tender document shall be entitled to quotesubject to their fulfilling the eligibility criteria.

The Details are as under:

Sl. No. Items Details

1 Bid Reference HO/DIT/ALM/2014-15/16 dated20.11.2014

2 Price of RFP Document INR 25,000/-(INR Twenty Five Thousand Only)

3 Date of Commencement of Sale of RFP 20th November, 2014,11:00 Hours

4 Date and time for Pre-Bid Meeting 8th December, 2014, 15:00 Hours

5 Last date of receipt of Pre bid queries 05th December, 2014, 12:00 Hours

5 Last Date and time for submission of Bid(Technical and Indicative Commercial)

22nd December, 2014,15:00Hours

6 Date and Time of Opening of TechnicalBids

22nd December, 2014,16:00Hours



Sl. No. Items Details

7 Date and Time of Opening of IndicativeCommercial Bids

To be notified subsequently to theeligible Bidders

8 Date of Online Reverse Auction Will be intimated to the technicallyqualified bidders

9 Place of submission and opening of Bids

The Asstt. General Manager (IT)Allahabad Bank, Head Office,Deptt. of Information Technology,2nd Floor,2, Netaji Subhash Road,Kolkata – 700 001,India

10 Address for Communication

Same As AboveTel : 091-033-22319471/72Fax : 091-033-2210 6323Email:[email protected]

4. Technical bids will be opened in the presence of the bidders’ representatives whochoose to attend on the specified date and time. The indicative commercial bids ofonly technically qualified bidders will be opened and the lowest quote obtainedthrough indicative commercial bids may be fixed as start price for the subsequentreverse auction to be carried out. However Bank may decide to fix the start pricelower than the lowest indicative quote at its discretion. The online reverse auctionprocess will be adopted for obtaining commercial quote from the technicallyqualified 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 beendisqualified on technical or any other ground declared/established as perterms/conditions of the RFP.

6. Non-attendance at the Bid Opening will not be a cause for disqualification of abidder.

7. Allahabad Bank reserves the right to accept or reject, in part or full, any or all theoffers without assigning any reasons whatsoever.

The Asstt. General Manager (IT),Allahabad Bank, Head Office,

2, Netaji Subhas Road, Kolkata – 700 001



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 year1969, the Government of India nationalized 14 commercial banks and Allahabad Bank wasone of them. For operational convenience, the Head Office of the Bank was shifted fromAllahabad to Kolkata in 1923.

2. The Bank is a leading public sector commercial bank based in India. The Bank offers arange of financial services including cash management services, depository services,corporate agency arrangements, visa debit cum ATM card, bank assurance and mutualfund, real time gross settlement, gold card scheme for exporters, National Electronic FundTransfer (NEFT), government business, and online payment. The bank operates throughfour 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 anOverseas Branch at Hong Kong.

4. The Bank also has CBS Project Office & DC in Navi Mumbai, a CBS Project MonitoringOffice in Kolkata and a DR Site in Lucknow.

5. The CBS implementation of the Bank was completed on 18th December 2010. CoreInfrastructure for the Centralized Banking Solution is hosted at the Data Center (DC) andDisaster Recovery Center (DRC). DC & DRC are operational on 24 x 7 basis and havenecessary infrastructure for that.

6. The replication is done directly at DRC from DC. The data at DRC is not more than 15minutes behind the production data at DC. In case of disaster the DRC can be up andrunning within 4 hours. The above mentioned project office/ DC/ DR are for Bank’s Indianoperations.

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 – AllahabadU.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 alsopromote/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 bestpractices and extant RBI/ BCBS/IBA/GOI Guidelines and also Guidelines that may be issuedup to the completion of the project.



2. This Request for Proposal (RFP) is intended to invite Techno-Commercial Bids from eligiblebidders to provide an ALM Solution in tune with RBI/BCBS/IBA/GOI guidelines/ industry bestpractices.

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 asper the requirements of this RFP for the period of the contract.

4. The Bank intends to procure the hardware for the proposed solution separately. Theselected vendor would be required to provide sizing and configuration of the requiredhardware 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 theimplementation of ALM solution. They will provide requisite assistance/guidance to theBank, wherever required, till project completion.

7. The Bank intends to implement ALM Solution in accordance with the provisions of followingcirculars/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 Liquiditystandards. 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 forIntraday 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 RFPshould, 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, Networkingequipment, Bandwidth etc. required at its data centre at Mumbai and Disaster Recovery Siteat Lucknow for successful implementation of the ALM solution. Bank will provide therequired hardware infrastructure for the project.

3. Prepare a Business Requirement Document, Test Cases and Test Plans based on the gapanalysis and other requirements of the RFP. The bidder shall be required to take Bank’s



approval of the Business requirement documentation and associated project plans beforesoftware customization work commences. The document should provide the plan in detailbased on the criticality of the requirements.

4. Ensure that the system is in compliance with RBI requirements and other relevant regulatoryguidelines. Any instances of non-compliance observed, even at a later date, will need to berectified at no additional cost to the Bank and well within timelines stipulated by theregulator/bank.

5. Ensure that software solution being supplied is capable of being integrated with existing ADFsystem of the Bank and a Data Ware housing solution; which the Bank may procure at alater point of time. It needs to have standard interfacing capabilities. Bidder shall directlyinteract with the vendors and provide necessary integration with the required systems of theBank at no extra cost to the Bank. There should also be a flow of report level data from theproposed system to the ADF system of the Bank for regulatory submission as well. Thebidder will be required to ensure correct data flow at all times.

6. Identify Project Manager, Project Leaders and members of the development teams withrelevant skills. The bidder will intimate the Bank, in advance, if there is any change in theproject team during the course of implementation. The bidder will ensure proper back up ofproject leaders and managers and the plan should be intimated to the Bank. The minimumexperience of the project team personnel like Project Manager, Project Leader andProgrammers put on work should preferably be 2 years. Systems study and all developmentactivities 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 theentire project duration.

8. Ensure that the solution offered should have all components mentioned clearly with itslicense requirements.

9. Impart both functional and technical/system training on ALM Solution to designatedpersonnel of the Bank.

10. Incorporate changes in system arising due to amendment to regulations/ Bank’s policy at noadditional cost and well within timelines stipulated by the regulator till completion of theproject

11. Assist the Bank in conducting the User Acceptance Tests by providing test plans, scenariosand 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 asrequired by the Bank in the desired format as per regulatory and Bank’s requirements duringthe entire project duration at no additional cost .

14. Ensure that the system meets all functional and technical requirements specified in thisRFP.

15. In case the product/ solution/ Bidder are amalgamated/ dissolved, the impact of such anevent should not have any adverse implication on the service level/ time line/cost that isproposed for implementation of the solution. Such event would not dilute the responsibility ofthe successful bidder in completing the implementation within mutually agreed time lines.



16. The bidder is required to provide interface with all external IT systems of the Bank forgeneration of desired reports/returns without any manual intervention. The term externalsystem also includes proposed systems such as LOS or other source systems, data capturesystems, workflow tools, etc. which the Bank uses from time to time. The bidder is alsoexpected to ascertain gaps in the data and provide solution to the bank, which should be inline with the requirements and acceptable to the Bank. Bidder should implement & maintainthe application software in Main Data centre, and Disaster Recovery (DR) sites. The day today work will be carried out at ALM Cell, Head Office. Appropriate functionality should beprovided for the purpose.

17. Bidder should provide Modular wise user manual as well as Administrator’s manual, post-implementation on-site support till next regulatory review from the GO LIVE date and furthersupport till the end of agreed AMC period.

18. Data migration should be done by the bidder from the existing data already collected by theBank (available in various source systems) to the new system with consistency. After goingLIVE, 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 andgenerated 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 systemssupplied under this contract, and will have overall responsibility of the performance,functionality and operation of the systems under this contract. Any supporting softwareprovided /installed/configured by the bidder shall be maintained /fine-tuned/ parameterizedby 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 SecurityPolicy 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, withnecessary documents so as to meet any exigencies.

23. The bidder should ensure that all verification processes in the software solutions should begoverned by maker checker controls.

24. The bidder’s overall responsibility includes offering suitable framework, supporting softwaresolution, implementing DR facility, recommending the appropriate hardware, impartnecessary 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 fortesting.

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 bemade available in writing.

Keep the Bank informed on the progress of the project as per the agreed reportingschedules.

The bidder and the Bank together will prepare acceptance test plan, for which bidder willstation its officers at the venue decided by the Bank at no additional cost.



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 technicalcompetency for implementing ALM in tune with RBI/BCBS guidelines and Industry BestPractices. The Bidder should have capability to review the existing ALM framework of theBank (including the prevailing policies, structures, processes, etc.).The Bidder is expected tohave adequate experience in implementation of software products/ projects compliant with theintegrated risk management framework for ALM, and also possess high quality processaccreditation(s).

2) The Bidder should be well established and have sound financial standing. Only those Bidderswho fulfil all the eligibility criteria are eligible to respond to the RFP. Any effort by Bidder toinfluence the Bank in the Bank’s bid evaluation, bid comparison or contract award decisionmay result in the rejection of the Bidder’s bid. Bank’s decision will be final and withoutprejudice and will be binding on all Bidders.

3) The bidders are required to meet the following eligibility criteria and provide adequatedocumentary evidence as specified for each of the criteria stipulated. Only those bids wouldbe further processed, which satisfy all the eligibility criteria.

4) ALM Solution for the purpose of ‘Eligibility Criteria’ will comprise of the core ALMfunctionalities i.e. Liquidity Risk Report (SLS) and Interest Rate Risk Reports (IRST & IRSD).

Sr. No. Eligibility Criteria Documentary Evidence to besubmitted to the bank

General Eligibility

1

The bidder should be in existence for 5years as on 31st March 2014. (In case ofmergers/acquisitions/restructuring or namechange, the date of establishment ofearlier/Original firm would be taken intoconsideration.)

Certificate of incorporation.

2

The bidder as well as the OEM should be aProfit making entity for last three financialyears i.e.2011-12, 2012-13, and 2013-14. (If2013-14 results are not finalized yet, then2010-11, 2011-12, 2012-13 will beconsidered).

Copies of Annual Reports in case oflisted companies and Copies of auditedbalance sheets and P&L statements incase of others for past 3 financial years.



Sr. No. Eligibility Criteria Documentary Evidence to besubmitted to the bank

3

The Bidder must have a presence in Indiafor at least 3 years and should haveaverage revenues in excess of INR 50.00Cr. (INR Fifty Crores) for the past 3 financialyears i.e. 2011-12, 2012-13, and 2013-14.(If 2013-14 results are not finalized yet, then2010-11, 2011-12, 2012-13 will beconsidered).

Copies of Annual Reports in case oflisted companies and Copies of auditedbalance sheets and P&L statements incase of others for past 3 financial years.

4

The bidder should own the intellectualproperty rights of the product/solution or heshould have rights from the owner, if not,the Bidder should have in place proper tie-ups, commercial agreements, authorisedimplementation partnerships etc. fordevelopment /resale/ customisation ofsoftware with the product bidder or any thirdparty, whose software products are offered.

Letter /Certificate from OEM

5

The Bidder and OEM should not have beenblacklisted at the time of submission by theCentral/any of the State Governments/statutory body/ regulatory body/IndianBanks Association in India

Self-declaration of bidder & OEM

Product Capabilities

6

The ALM Solution should have beenprocured by at least 2 ScheduledCommercial Banks amongst which at least1 should be a Public Sector Bank.

Credential letter on bank’s letter head

7

The ALM Solution should have beensatisfactorily implemented by a Bankoperating in India as on 30.06.2014. Credential letter on bank’s letter head

8The Bidder should have experience ofimplementing ALM solution in a Bank inIndia.

The bidder needs to submit thecredentials of the team who will do theimplementation.

2.5 Preparation & Submission of Bids

Mode of submission

The bidder shall prepare two copies each of the Technical, Indicative Commercial and EligibilityCriteria. The bidder shall seal the original and copy of these three bids in separate envelopes (TotalSix envelopes). All the original bids should be further sealed in to one outer envelope marked asOriginal Bid and all the copy bids should be sealed in a separate outer envelope marked as CopyBid.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 AGAINSTRFP REF. NO.: HO/DIT/ALM/2014-15/16 – COPY BID”. In case the bidders opt to remit the non-



refundable bid submission fee by way of DD/Banker’s Cheque at the time of bid submission, thesame 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 andstamped 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 andsubmitted in the following manner:

1) Envelope labelled as “Eligibility Criteria”

This envelope should contain the documentary proof and annexure required if any in respectof each of the criterion listed out in Section-2.4. The check list for submission of eligibilitycriteria 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 theauthorized signatories who can represent the Bidder/s with regard to the obligationsunder 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 forthe 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/MSword. The soft copy is to be placed in the envelope. The Bidder should certify that thecontents 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 hardcopyand 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 pagesproperly numbered, each page signed and stamped. The technical proposal should bebound 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-62. 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-74. Details of past experience as specified in the Annexure-85. The proposed project team profile as given in Annexure-9



6. The details of training programs conducted by the bidder in format specified inAnnexure-10.

7. The documentary proof in support of these programmes in the customer- Bank’sletter head shall also be included in this envelope.

Other Relevant Informationa. Executive summary of Bidder’s responseb. Detailed technical write up covering the detailed scope of workc. Duly signed covering letter by the authorized signatory– Bid Formd. Manufacturers Authorization Form from the Bidders proposed partnerse. Data Centres requirementsf. Comments on the RFP terms and conditionsg. Reverse auction compliance statementh. Soft copy of the technical bid only.i. Two originals of all the documents submitted in the technical bidj. Any other information in general

This envelope shall also contain all the Annexures specified in this RFP related to technicalevaluation. It shall also include documentary proof required for substantiating the informationgiven 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 used2. List of all software / tools to be used together with licensing details3. Tentative project time schedule and plan4. Project management, control and tracking mechanism5. Quality control setup and procedures to be followed6. Implementation & Training plan7. Technical brochures and user manual

In case any Bidder does not quote for any of the components, the response would be deemed toinclude the quote for such unquoted components required for meeting the functional and technicalrequirements including the service levels specified in this RFP.

The Bank reserves the right not to permit changes in the technical specifications and not to evaluatethe offer in case of non-submission of the technical details in the required format or partialsubmission of technical details.

3) Envelope titled “Indicative Commercial Bid”The Indicative Commercial Bid should be given by the Bidders in the format as shown inAnnexure -13. The Bidder is expected to quote unit price in Indian Rupees (without decimalplaces) for all components on a fixed price basis as part of the commercial Bid inclusive ofall costs and taxes like customs duty, excise duty, import taxes, freight, forwarding,insurance, delivery, installation, training etc. at the respective delivery location of the Bankbut 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 onproduction of bills. Further, receipts of such payments made to relevant authorities must beproduced for Octroi / Entry Tax / equivalent local authority cess. The Bank will not pay anyother taxes, cost or charges.

The indicative price should be quoted for each item, each unit with total cost, module wise, ifmodular. Indicative Prices for all items including optional items, if any, should also bementioned. 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



2. Details of cost of deliverables for the system (in the format given in Annexure-12 A3. 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 containthe following:

1. The bid covering letter cum declaration format is given in Annexure - 112. 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 outand tear during scrutiny. The Bids, which are not sealed as indicated above, are also liable to berejected.

The price schedule shall be submitted in indicative commercial Bid only. In a nutshell, the indicativecommercial 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 particularsof all major components/line items under each head.

The indicative commercial bid is obtained for the complete solution and Bank will place the orderafter finalizing the Bidder.

Further, while the Bidder has to quote for all the components of the solution, Bank may at itsdiscretion wherever beneficial, procure licenses for some software separately, based on any existingagreements 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),Department of Information TechnologyAllahabad Bank,Head Office,2, Netaji Subhash Road,Kolkata – 700 001,India

The Project name and a statement: “DO NOT OPEN BEFORE 22nd December, 2014, 16:00Hours” 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 22nd

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 Bankdoes not function on the aforesaid date due to unforeseen circumstances or holiday then the



bid will be accepted on the next working day and bids will be opened at the same venue on thesame day.

2) Bank however reserves the right to change the date & time for opening of Technical bid withoutassigning any reason whatsoever. In case there is a change in the schedule the same will beintimated to the Bidders by putting up on the Bank’s website for enabling them to be presentduring the Bid opening.

3) The Bidders’ names, bid modifications or withdrawals and the presence or absence of therequisite bid security and such other details as the Bank, at its discretion, may considerappropriate, 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 andschedule 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 identifyLowest Quoted (L1) Bidder. Online Reverse Auction procedures and timings will be informedseparately. Technically qualified Bidders will be informed the modus operandi for this purposeand 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 inresponse 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 theirbid.

2) The Bid security is required to protect the Bank against the risk of Bidder’s conduct, whichwould warrant the security’s forfeiture.

3) The Bid security shall be denominated in Indian Rupees and shall be one of the followingforms:-

a. A bank guarantee for Rs. 50,00,000/- (Rupees Fifty Lakhs Only) issued by a Privatesector / 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 ofthe Bid.

b. A Banker’s Cheque / Demand Draft, issued by a Private Sector / Public sector Bank inIndia (other than Allahabad Bank), drawn in favour of Allahabad Bank payable atKolkata 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 ofPurchase Order to the Successful Bidder. The successful Bidder’s Bid Security will bedischarged upon the Bidders signing the Contract and furnishing the Performance Security.

5) The Bid Security will be forfeited,

I. If the Biddera. withdraws its Bid during the period of bid validity

orb. 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 duringthe 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 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 Bankreceives written notice for modification or withdrawal of the bids, before the expiration of deadlineprescribed for submission of bids. In case of modifications, the bidder is expected to resubmit entirebid 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 reasonwhatsoever. Any decision of the Bank in this regard shall be final, conclusive and binding on thebidder.

2.10 Cancellation of Bid

The Bank reserves right to re-issue/re-commence the entire bid process and or any part in case ofany 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 onthe bidder.

2.11 Period of Validity of Bids

Validity Period: - Bids shall remain valid for 180 days from the last date specified for submission ofbids 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’sconsent to an extension of the validity period. The request and the response thereto shall be madein 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 (fordownloaded RFP), shall be permitted to attend a pre-bid meeting to be held as indicated in theInvitations for Bids. Up to a maximum of 2 (two) representatives of each prospective bidder will bepermitted to attend the pre-bid meeting. However the Bank, at its discretion, may permit anyadditional 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 beraised up to that stage. The issues/queries to be raised must be in writing and submitted at least 2working days before the scheduled pre bid meeting. The Bank will have liberty to invite any outsideagency, wherever necessary, to be present in the pre-bid meeting to reply to the queries of thebidders in the meeting.

Any modification in the RFP, which may become necessary as a result of the Pre-Bid Meeting, shallbe made by the Bank exclusively through the issue of an Addendum and will be sent to all



prospective bidders who have purchased the RFP, at least 4 working days prior to the last date forsubmission 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 alsoinformed to all purchasers of the bid documents.



3. Selection Strategy

3.1 Objective

1) The objective of the evaluation process is to evaluate the bids to select an effective and best fitsolution at a competitive price. The evaluation will be undertaken by the Selection Committeeformed by the Bank, which may also include external experts/consultants. The committee orauthorised official shall recommend the successful bidder to be engaged for this assignment tothe 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 whowould undertake the designing and implementation of the required solution. The Bidder shall beentrusted with end to end responsibility for the execution of the project under the scope of thisRFP.

3) The Bank will scrutinize the offers to determine whether they are complete, whether any errorshave 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 theschedule. The Bank may, at its discretion, waive any minor non- conformity or any minordeficiency in an offer. This shall be binding on all Bidders and the Bank reserves the right forsuch 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 inwriting within the specified date and time. The bidder’s offer may be disqualified, if theclarifications/ 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 thesolution offered etc., from the bidders based on the technical bids submitted by them. Bank alsoreserves the right to conduct Reference Site Visits at the bidder’s client sites. Based upon thefinal technical scoring, short listing would be made of the eligible bidders for final commercialbidding.

5) The evaluation will be a four-phase process:-Phase 1 – Eligibility Criteria EvaluationPhase 2 – Technical Bid EvaluationPhase 3 – Indicative Commercial Bid Evaluation &Online Reverse AuctionPhase 4 – Weighted Evaluation

6) The Technical evaluation and the Commercial evaluation (post reverse auction) shall have theweight-age of 70% and 30% respectively for evaluation, and this weight-age shall be taken intoconsideration for arriving at the Successful Bidder.

NOTE: The Bank's decision in respect of eligibility criteria, evaluation methodology and shortlisting 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 theTechnical Bid Evaluation.

3.2 Evaluation of Technical Bid

The proposal submitted by the Bidders shall be evaluated on the following group of parameters.



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 byeach bidder under each parameter are aggregated to find out the total technical score of thebidder.

2) The score for evaluation of different Modules & systems shall be decided by the InternalSelection Committee.

3) The selection parameters are explained in following paragraphs4) This evaluation will be carried out on a total score of 1,000 on the basis of the following

evaluation parameters defined in this sectionSl. 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 technicalrequirements which are necessary for achieving regulatory compliance are mandatory. Biddershall indicate the availability against each requirement/capability. The means of indicatingavailability is given in the following table. The marks thus scored will be scaled to the Sub-Scoregiven in Sec. 3.2.

The Type ofResponse/Scale Description** Max.

Marks

S Standardized, this scale indicates that this feature is astandard feature of the solution. 10

A Alternative available 7

C Customization required. Vendor will provide thecustomization with the stipulated date of the phased rollout 5

U Unavailable. Functionality is not available and will not beprovided 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 asstandardized. The remaining should be customized before “GO LIVE”, at no extra cost to theBank.



3.4 Scoring Methodology for Product Demonstration andBid Presentation (PB)

1) Eligible Bidders will be required to make presentations to supplement their bids and show adetailed product demonstration. The number of eligible bidders called for product demonstrationis purely a matter of discretion of the Bank. The Bank will schedule presentations and the timeand location will be communicated to the Bidders. Failure of a Bidder to complete a scheduledpresentation to the Bank will result in rejection of the proposal.

2) The marks awarded under this parameter shall be based on the effectiveness of thedemonstrations and presentations made by the bidder. Using the Functional & TechnicalRequirements as a base in part or as a whole, the Bank may formulate a detailed questionnairefor 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 thatexplains the approach and methodology proposed by the bidder for the implementation of theproposed solution. The “Approach and Methodology” adopted for the Implementation would beevaluated by Bank and would at the minimum cover Team Strength, Project Management andTraining.

2) Team Strength: Bidder responses to each point under Team Strength in Proposed TeamProfile, including the team profile provided by the Bidder, would be evaluated. The Biddershould ensure that the people above the role of the Team Lead who are proposed for thisproject should have worked on projects in Banks earlier. The members of the proposed projectteam and team lead should have a minimum experience of 2 years and 5 years respectively inimplementation 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 teammembers of his partner. The format for furnishing the team profile is given in Annexure 09. Themarks assigned under this parameter are based on the qualifications and experience of teammembers.

4) Project Management: Bidders are required to respond to each point under ProjectManagement in Annexure-6. Each question will be evaluated for suitability of response. TheBidder should provide explanation on the Project Management process that is proposed for theBank 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 theproposed solutions. This process will also enable the Bank to clarify issues that may beidentified from the Bidders’ responses to the RFP. The Evaluation Committee decided by theBank would be scoring the presentation made by the Bidders at Bank’s premises based on astructured questionnaire broadly across the following:-

a. Project Execution Methodologyb. Solution Architecture and Design – Key Features and Functionalitiesc. Interface approach and methodologyd. Adherence to Project Timelinese. 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 Methodologyh. Solution Architecture and Design – Key Features and Functionalities

6) Past Experience: The Bidder’s past experience shall be evaluated on the basis on thedetails given in the Annexure-8 “Past Experience



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 beendeployed. The reference site should be one where the Bidder has implemented the ALMSolution 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/orTelephonic interviews, Written Correspondence with the existing customers of the Bidder.The inputs that have been received from the Customer would be considered by the Bankand this might not need any documentary evidence. This scoring would be purely on thebasis of inputs (like satisfaction of the organization of the product, timeliness ofimplementation, 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 reasonswhatsoever, 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 Bankfor site visits. However, the Bidder may be expected to facilitate these arrangements.

3.7 Disqualification Parameters in Technical Bid Evaluation1) 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 selectbidders 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 reasonwhatsoever, if in Bank’s opinion, the Solution Sizing was not made appropriately to meet theperformance criteria as stipulated by Bank and also where the responses received from theSite Visits are negative.

3.8 Evaluation of Indicative Commercial Bid & OnlineReverse Auction

1) Only technically qualified Bidders (as per the laid out criteria) will be intimated to participatein the Online Reverse Auction to identify L1 (lowest quoted) Bidder. The comparison shall bebetween the prices quoted. The price quoted should include all components specified in theTotal 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, Installationand 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 becalculated as follows:

Total Score = (C-LOW / Cn) * C-weight + (Tn / T-HIGH) * T-weight

Where,C-Low = Lowest Commercial QuoteCn = Commercial Quote of the Bidder being evaluatedC – Weight = Weight of the Commercial Bid i.e. 30%Tn = Technical Score of the Bidder being evaluated



T-High = Highest Technical ScoreT-weight = Weight of the Technical i.e. 70%

Here C and T are the commercial and technical scores of the respective bidders. Thescores 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 conferthem the right to be awarded the contract. Further, the Bank has sole discretion inselection 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 theBidders. 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 theorganization 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 amountin the commercial bid and also quote offer price during on-line reverse auction. The details of digitalcertificate, like Name, Digital Key details, issuing authority and validity etc. to be provided later.



4. Scope of Work

4.1 Broad scope

The broad scope of the project envisages:

1) Supply, Installation, Deployment, Customization, Testing, Implementation, Rollout, Maintenanceand Support of the software for ALM Solution to achieve compliance with RBI/BCBS/IBA/GOIGuidelines pertaining to ALM. Bidder have to provide the sizing/configuration of the requiredhardware, OS, RDBMS, Networking Equipment, Bandwidth etc. to the Bank. Any otherhardware/software which is essential to run application but not advised to the Bank in the bidwill be supplied and installed by the bidder free of cost.

2) Gap Analysis, Parameterization, historical data management, verifying data quality, migratingdata, user acceptance testing, documentation, knowledge transfer and support.

3) Interfacing with other external systems including core Banking software solution, TreasurySolution, 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 manualas well as administrator’s manual, post-implementation on-site support up to the next regulatoryreview 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 andconsolidation 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 bindingon 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 supposedto provide functional and operational support to the above or other centres as per requirements ofthe 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 inBank’s framework, policies, procedures, governance, and existing systems which needs to bebridged prior to deployment of ALM architecture. The gap analysis should be done in thecontext of industry best practices and regulatory guidelines issued by RBI/BCBS etc. pertainingto ALM.

2) Provide the Bank with the gap identification report along with the recommendations andestimated time frames to resolve the same.

3) Provide various tools/utilities to bridge the gaps identified during GAP analysis phase withoutany extra cost.

4) Determine the customization requirements, in case a particular functionality requirement is notsupported by the existing version of the ALM solution.



5) Resolve gaps by customizing the proposed solution by way of modifications/ enhancements, asnecessary.

6) Facilitate data migration from the existing data already collected by the Bank to the new systemwith consistency. All the details from the migration date till the date of GO LIVE should also bemigrated 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 inthe Functional Requirements and Technical Solution Requirements for, Asset LiabilityManagement Solution as detailed in this RFP.

2) Automated Interfaces required for the solution with other internal systems and external systemshas to be provided by the selected bidder to ensure satisfaction of the functional and technicalrequirements. Bidder will be responsible for the procurement of any tool required to develop theinterface. Bidder will document the entire interface logic and process with change managementprocedures 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, legacydata etc. with the endeavour to reduce the overall cost of procurement to the Bank. The biddershall also continuously explore avenues to reduce the cost and act in the best interest of theBank.

4) Bidder shall provide the Bank, understanding and full access to Database, Database TableStructures and Data Dictionary of the proposed solution.

4.2.3. Parameterization, Configuration and Customization ofSoftware

1) To assist in bridging the identified data gaps for compliance with RBI and other relevantguidelines.

2) The Bidder shall be responsible for accuracy of the parameters set in the system according tobusiness needs of the Bank.

3) The cost of all customizations is required to be included in the Commercial Bid and the Bankwill not make any additional costs for this throughout the term of the contract if the same hasbeen specified as a requirement of the Bank in this RFP. Thus, this is a fixed bid and allnecessary customizations based on the functional requirements specified in the RFP will needto be conducted by the Bidder.

4) Bidder needs to give detailed plan for customization. All customization has to be completedwithin the project timelines.

5) The Bidder should ensure that the quality assurance and development standards outlined in thedevelopment methodology of the proposed solution are adhered to and requiredfunctionalities/reports related to same are generated and shared with the Bank team on aregular basis.

6) Enhancements provided by the Bidder would include changes in the software due to statutoryand Regulatory changes and those required due to changes in industry practices or any otherrequirements of the Bank related to the above, which will need to be provided at no extra costto the Bank for the entire period of the contract. It will include, but not limited to, all thefunctionalities mentioned in the Functional Requirements.

7) Before completing this phase, the bidder shall ensure that ALM solution / architecture proposedto be implemented/laid down is capable of meeting all functional and technical requirementsspecified in this RFP.

8) Apart from the reports specified elsewhere in this document, the vendor will be required toconfigure an additional 50 (fifty) number of reports in the solution as per specifications provided



by the Bank. System should also have provision for dashboards, which should be configured asper bank’s requirement.

9) The vendor shall also be responsible for customizing and generating regulatory/statutoryreports/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 systemelements have been properly integrated and that the system performs all its functions. Thesystem integration testing will be required to be confirmed by the Bank.

2) The Bank will conduct “User Acceptance Tests” (“UAT”) under guidance, review andSupervision of the bidder to ensure that all the functionality required by the Bank as mentionedin 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 tunewith the Bank’s expectations, the bidder shall make appropriate changes. All UATs wouldrequire 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 entireperiod of project implementation. The bidder will ensure that test environment’s configurationand parameterization for conducting the UAT is in line with bank's risk management frameworkand this RFP’s requirements. The bidder shall ensure that the test environment has the sameconfiguration and functionalities as that of the production environment.

4) The Bank will provide scenarios for UAT and the Bidder will prepare test cases including thetest 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 ofthe Bank.

6) The Bidder will be responsible for maintaining appropriate program change control and versioncontrol of the system as well as documentation of UAT and change of configuration andparameterization after making changes in the system.

7) All errors, bugs enhancements/modifications identified during and after testing will be resolvedwithin the overall timelines for implementation.

8) The Bidder will be responsible for using appropriate tools for logging, managing, resolving andtracking issues and its progress, arising out of testing and ensuring that all issues areaddressed in a timely manner to the satisfaction of the Bank and as per requirementsmentioned in this RFP.

9) The Bidder will be responsible for performing functional UAT and integrated UAT on minimumtwo snapshots (End of Quarter & End of Month on Pre-Audit and Post-Audit data) of productiondata.

4.2.5. Training

1) The Bidder shall be responsible for training the concerned employees of the Bank in the areasof system administration, implementation, use / operations, management, databasemanagement, error handling /troubleshooting, etc. of the ALM Solution.

2) Structure of the training program covering number of trainings, locations and number ofparticipants etc. is to be advised by the bidder in writing.

3) Bidder will also be responsible to develop training and reference materials for all thefunctionality of the software. Training / reference materials should be designed separately foroperational staff / user, IT department and senior management. Training material shouldcomprehensively cover all the functionality of the proposed ALM solution and be written in auser friendly manner with use of graphs, processes flows, screen-shots of the actual systemfunctionality etc.



4) Bidder should provide Bank specific training material designed considering its requirements inthis RFP. Training material so provided will be subject to review and sign-off by the Bank as aproject 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 andrecovery, trouble shooting, data synchronisation, file uploads etc.

6) The minimum number of training sessions shall be decided by the Bank and the successfulbidder is bound to oblige.

4.2.6. Implementation

1) The proposed solution should cover all the Branches/Offices/Departments of the Bank andhave the capability to scale up for meeting future requirements. The solution should be scalableand capable to handle increased volumes. In the event the Bank adds/changes/updatessource/core banking systems in the future the solution should be flexible to handle such newsource systems.

2) Generation of required reports for domestic as well as overseas operations3) 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 proposedsystem to the ADF system of the Bank for regulatory submission as well. The vendor will berequired to ensure the correct data flow at all times.

6) At present, the Bank has various solutions running on both Windows and RISC platforms withOracle and SQL Server databases. The solution provided shall be capable to integrate withthese databases directly. Ultimately, the ALM Solution shall be linked to Enterprise DataWarehouse (as and when operational). The solution should be able to seamlessly integrate withupcoming Enterprise Data Warehouse and shall function as a Data Mart to the EDW. Theproposed solution should be compatible to the following platforms i.e. Windows, UNIX andLinux with Intel and/or RISC systems. Also include overseas branch (es).



7) By means of diagrammatic/pictorial representations, the Bidder should provide complete detailsof the hardware, software and network architecture of the ALM Solution (module andsub‐module wise), including source / method of Data capture and transfer, validation, updatingand database maintenance for networked branches. In this regard the bidder should alsoprovide logical architecture and high level diagram of hardware/software/network architecture.

8) The Bidder should recommend the hardware, operating system, database, data replicationrequirements 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 toensure that vulnerabilities at application level in case of any breach shall be handled by theoffered application software.

10) The total storage requirement proposed by the bidder shall take into account incrementalgrowth of the Bank, over the next 7 years. The Bidder should specify appropriate size storageto meet the requirements of the Bank.

11) Complete details for the hardware required for the successful operation of the Solution shouldalso be provided by the Bidder, with full particulars like configuration, memory type, futureexpandability, processor type, number of processors, processor speed etc. Keeping in mindthat there should be no single point of failure. (Annexure 12 B)

12) The Bidder should specify the hardware requirement taking into consideration the efficiencylevel, response time, data processing requirement, number of users, and all other parametersto ensure that the efficiency of software system is not affected because of hardware. Biddershould provide details for DR site such as network and security requirements, switches, routersetc.

13) The Bidder will certify that the hardware specified is adequate for meeting performancestandards 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 andrated power) and any other specific requirements for the servers / equipment (Network andsecurity requirements, switches, routers etc.) and associated infrastructure for both DC (DataCentre) & DR (Disaster Recovery) sites.

15) Sizing of equipment, hardware etc. as required, depending on the functionalities required by theBank as mentioned in the RFP, should be provided by the Bidder for processing of existingportfolio of the Bank with increase in volumes at approximately 20% p.a. and addition of newproducts/instruments and data maintenance for a minimum period of 7 years as per RBIguidelines.

16) As part of implementation all data migration (as and when required) from the existing systemincluding any other system procured by the Bank during the period of contract to the proposedALM system will be done by the Bidder. The Bidder shall demonstrate to the satisfaction of theBank 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 FMcharges for the entire duration of project, however Bank will have liberty to discontinue the FMServices at any point of time during the contract period.



1) Facilities Management: Facilities Management would include support for all applicationsoftware, provided by the Bidder. Bidder should elaborate on FMS like number of resources tobe 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 nextregulatory review from the “GO LIVE Date” till the completion of the project. Uninterruptedservices of helpdesk shall be available to the bank during working hours. The bank may requirethe resource/helpdesk to be available for extended hours during select working days e.g. duringfinalisation of financial results, department audit, regulatory review, etc.

2) The Bidder needs to consider and envisage all services and associated cost that would berequired in the maintenance of all the applications and interfaces provided, quoted anddeveloped by the Bidder.

3) The Bidder is expected to develop a methodology for conducting the FM for Bank based on therequirements. The personnel being deployed by the Bidder for FM at the Bank should haverelevant 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 manpowerand 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 mentionedabove 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 andtroubleshooting System, component & network maintenance Configuration changes, tracking,and documentation Upgrade / Enhancement. The maintenance for the services would be for allthe 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 perpetualbasis. The Bank shall have the Right to use the software provided /installed /configured by theVendor/bidder and/or software application systems supplied under this contract after the expiryof the period under this contract and it shall be at liberty to use/run the said software solutionswith the help/support of its in house IT Officers or through any other out sourcing serviceAgencies. The bidder/Vendors shall not have any right to question or object for continuation ofthe use of such software or software solutions irrespective of entering into any AMC with theBidder/Vendor after the expiry period or not. The Bank will decide at its sole discretion afterexpiry of the period under this contract either to enter into an AMC with the Vendor or not. TheBidder/Vendor shall not have any right to challenge the decision of the Bank in any manner orin any proceedings.



5. Functional & Technical Requirement

5.1 Functional requirement for ALM Solution

S No Functional Requirements

Importance

(Critical /Important /Desirable)

Extraction of Transaction Data

1.1The system should interface with all operational systemscurrently being used by the Bank, to extract transaction datafrom each source system in respective currencies

Critical

1.2 The system should be scalable and allow the interfacing of othersystems as and when such systems are procured/implemented Critical

1.3As a back-stop measure, the system should support the manualupload of transaction data from various operational systems informats provided by the Bank

Critical

1.4 The system should allow users to manually edit or enter atransaction / position Critical

1.5 At a minimum, the system should capture the followingparameters at a transaction level to enable cash flow generation:

1.5.1 Application ID (Unique identifier) Critical1.5.2 Counterparty name Critical1.5.3 Product / instrument Critical1.5.4 Account number Critical1.5.5 Originating branch Critical1.5.6 Originating Business Unit Critical1.5.7 Originating / disbursal date Critical1.5.8 Maturity date / tenor Critical1.5.9 Outstanding balance Critical

1.5.10 Original amount Critical1.5.11 Fixed / floating rate Critical1.5.12 Benchmark curve (if floating) Critical1.5.13 Fixed spread over benchmark (if floating) Critical1.5.14 Re-pricing frequency (if floating) Critical1.5.15 Re-pricing dates (previous and next) Critical1.5.16 Pay dates Critical1.5.17 Payment frequency Critical1.5.18 Frequency of interest accrual Critical1.5.19 Compounding frequency Critical1.5.20 Status (i.e. performing or non-performing) Critical1.5.21 Amortization schedule Critical1.5.22 Original currency Critical




Importance


1.5.23 Defeasance Period for trading book investments Critical1.5.24 Account level Ratings for Investment, advances etc. Critical1.5.25 Sanctioned Limits for advances Critical1.5.26 General Ledgers Accounts Critical

1.6 The system should be capable of accepting the external datafeeds from following systems:

1.6.1 Reuters/ Newswire Critical1.6.2 Bloomberg Critical1.6.3 Any other system Critical

1.7

The system should perform data validation checks on the sourcedata extracted from the operational systems. The exact nature ofthe data validation checks will be based on inputs from thebank's IT team during implementation.

Critical

1.8 The system should alert the user through pop up or through areport, in the event of failed data validation checks. Critical

1.9

The system should also have the capability to allow users tomanually enter any market yield curve or Spread Curve orDeposit Curve or any other user defined rate which is to be usedas coupon or yield

Critical

Cash Flow Generation

2.1The system should be capable of generating cash flows usingposition data and amortization schedules for assets/ liabilities ona daily basis

Critical

2.2At the minimum, the system should be capable of generatingcash flows using position data and amortization schedules/assumptions for all the following asset categories including

2.2.1 Advances Product Critical2.2.1.1 - Term Loan Critical2.2.1.2 - Cash credit/ Over drafts Critical2.2.1.3 - Demand loans Critical2.2.1.4 - Bills purchased and discounted Critical2.2.1.5 - Any other advances Critical2.2.2 Investments Critical

2.2.2.1 - Investments in forwards/ futures Critical2.2.2.2 - Derivatives - IRS, CCS Critical2.2.2.3 - Investments in bonds/ equities/ Mutual Funds Critical2.2.2.4 - Investments in SRs/ PTC/ VCF Critical2.2.2.5 - Investment in Options (All types) Critical2.2.2.6 - Swaps (Sell/Buy)/ maturing forwards Critical2.2.2.7 - Any other investment/ treasury product Critical




Importance


2.2.3 Off-balance sheet exposures Critical2.2.4 Other assets Critical

2.3At the minimum, the system should be capable of generatingcash flows using position data and amortization schedules forthe following liability categories:

2.3.1 Current deposits Critical2.3.2 Savings deposits Critical2.3.3 Term Deposits Critical2.3.4 Foreign Currency Non-Resident (Banks) (FCNR (B)) deposits Critical2.3.5 Exchange Earners Foreign Currency (EEFC) deposits Critical2.3.6 Resident Foreign Currency (RFC) deposits Critical2.3.7 Resident Foreign Currency Domestic (RFC (D)) deposits Critical2.3.8 Borrowings - Call, Notice, Repo, Term Repo, CBLO etc. Critical2.3.9 Bankers Acceptance Facility (BAF) borrowings Critical

2.3.10 Contingent liabilities and off-balance sheet exposures Critical2.3.11 Other liabilities Critical

2.4 The system should have the capability to generate cash flows forproducts having the following types of amortization schedules:

2.4.1 Conventional amortization (EMI) Critical2.4.2 Principal only payment Critical2.4.3 Balloon Payments Critical2.4.4 Amortization for floating rate instruments Critical2.4.5 Negative amortization Critical2.4.6 Hybrid / user defined amortization Critical

2.4.7 Amortization on the basis of behavioural studies performed inthe system Critical

2.4.8 User defined behavioural pattern Critical

2.5The system should have the capability to generate cash flows forboth standard and user defined re-pricing patterns for floatingrate products, including:

2.5.1 Provision for defining/ capturing different benchmark curves Critical

2.5.2 Provision for defining/ capturing different re-pricingcharacteristics for different periods in the life of a product Critical

2.5.3 Provision for capturing rate caps, floors and gaps Critical

2.5.4 Provision to capture foreign exchange rates manually or throughinterface with Treasury/ Newswire Critical

2.5.5 Current reference rate Critical

2.6 The system should allow the user to model the following andincorporate the same into the cash flow patterns generated.

2.6.1 Prepayment patterns Critical




Importance


2.6.2 Rollovers and premature withdrawal patterns Critical2.6.3 Behaviour models in to Core and Volatile Critical

2.7 The system should be capable of generating the cash flows inmultiple currencies Critical

2.8The system should support both standard (i.e. based on productcharacteristics, amortization schedules, behavioural maturitiesetc.) and user defined payment patterns

Critical

2.9The system should be capable of converting the cash flows frommultiple currencies into a single user defined home currencybased on user defined/ automatically FEDAI exchange rates

Critical

2.10The system should be capable of generating the cash flows forthe Bank separately at each of the following levels inaccordance with the Regulator’s requirements

2.10.1 Indian operations- Domestic currency Critical2.10.2 Indian operations- Foreign currency Critical

2.10.3 Overseas operations country wise (in each currency and Totalconverted into home currency) Critical

2.10.4 Consolidated Indian operations (home currency) Critical2.10.5 Consolidated operations at bank level (reporting currency) Critical

Reconciliation with Trial Balance

3.1 The system should accept the Trial Balance as an MS-Excelupload/ manual input/ through STP through GL system Critical

3.2

The system should also be able to draw distribution underinflows/ outflow based on data mentioned in the Balance Sheetschedule and given in the form of Excel/ file upload/ manualinput/ any other mode

Critical

3.3The system should perform item-wise, automatic reconciliation ofthe Trial Balance with the aggregated assets and liabilities asper the liquidity profile

Critical

3.4 The system should automatically alert the user in the event ofdiscrepancies between the liquidity profile and the Trial Balance Critical

3.5 The system should allow users to identify line item under whichreconciliation difference can be parked Critical

3.6The system should be capable of accepting balances manuallyto reconcile (by passing transaction or position or GL Balance)difference between GL and the Account Level Balances

Critical

3.7 The system should maintain audit trail or a separate report forsuch manual adjustments Critical

Development of Structural Liquidity Profile

4.1The system should be capable of generating the structuralliquidity profile on a daily basis in accordance with RegulatoryRequirement.

Critical

4.2The system should support the classification of assets andliabilities into precise time buckets and generation of the LiquidityProfile

Critical




Importance


4.3 The system should have the ability to define product-wise asset /liability categories, sub-categories and define product hierarchies Critical

4.4 The system should allow users to define the time buckets to beused for developing the Structural Liquidity profile. Critical

4.5 The system should allow the user to define bucketingassumptions for each product or asset/liability type Critical

4.6 The system should be capable of accepting bucketingassumptions in the following forms:

4.6.1 Original contractual maturity Critical4.6.2 Residual maturity Critical

4.6.3 Percentages to each time bucket for each line item in the SLSreport Critical

4.6.4 Defeasance Period for trading book investments Critical4.6.5 Custom expression Critical

4.7The system should allow the user to develop multiple liquidityprofiles with different bucketing assumptions and/or timebuckets.

Critical

4.8

The system should allow the user to drill down from liquidityprofile to the desired granularity (i.e. portfolio level, accountlevel, position level, instrument level, product level, asset classlevel etc.)

Critical

4.9Post development of the liquidity profile, the system shouldconduct automatic validation checks to ensure that aggregateasset and liability balances are equal

Critical

4.10The system should be capable of generating the structuralliquidity profile in multiple formats given by the Bank in multiplecurrencies

Critical

4.11The system should be capable of converting the structuralliquidity profiles in multiple currencies into one user definedhome currency

Critical

4.12The system should be capable of converting the structuralliquidity profiles in multiple currencies into one user definedreporting currency

Critical

4.13The system should be capable of aggregating the structuralliquidity profiles into one consolidated profile based on userpreferences

Critical

4.14The system should be capable of generating the structuralliquidity profiles for the Bank and its subsidiaries separately ateach of the following levels as per the RBI format

4.14.1 Statement of structural liquidity - Domestic currency, Indianoperations Critical

4.14.2Statement of structural liquidity - Foreign currency, Indianoperations (in each currency as well as converted into homecurrency)

Critical

4.14.3 Statement of structural liquidity - Overseas operations countrywise (in each currency as well as converted into home currency) Critical




Importance


4.14.4 Statement of structural liquidity - Combined Indian operations –Domestic and Foreign Currency Critical

4.14.5 Statement of structural liquidity – Consolidated Bank operations Critical

4.14.6 Statement of structural liquidity - Currency wise Gap Analysis (Consolidated for Non-Significant currencies in local currency) Critical

4.14.7 Statement of structural liquidity – Subsidiaries/ JVs/ Associates –Country Wise Critical

4.15The system should be capable of generating structural liquidityprofiles for user defined future dates based on current balancesheet position.

Critical

4.16The system should be capable of generating structural liquidityprofiles for user defined future dates considering cash flowprojections.

Critical

4.17The system should compute DTL profile and as per RBIguidelines, specific line items should be distributed on the basisof DTL Ratio with a fortnight lag or otherwise

Critical

4.18The system should compute Minimum CRR Balance, computeexcess or shortfall in maintenance and the do appropriatebucketing of Balances

Critical

4.19The system should compute current SLR, compute the excess/shortfall and appropriately bucket the Investments as per theRegulatory requirement

Critical

4.20 The system should be able to handle bucketing of Non SLRsecurities as per regulatory guidelines Critical

4.21 The system should allow users to allocate amounts in specificbucket(s) through percentage or amount allocation Critical

4.22 The system should distribute NPA based on its category, i.e.,Sub Standard, Doubtful and Loss Critical

4.23 The system should identify event cash flows and handle thedistribution as suggested in the guidelines Critical

4.24 The system should facilitate distribution of line items based onthe product’s underlying Critical

4.25System should be capable of projecting the Structural LiquidityProfile for future dates based on assumptions provided by theBank.

Critical

Structural Liquidity Mismatch Limit Monitoring and Reporting

5.1 The system should be capable of accepting structural liquiditymismatch limits in the form of:

5.1.1 Percentage of total outflow in a time bucket Critical5.1.2 Cumulative mismatch limits Critical5.1.3 Individual Bucket wise limits Critical5.1.4 Custom expression Critical

5.2 The system should be configurable to define the authorities towhom limit breaches must be escalated Critical




Importance


5.3 The system should automatically alert the user and all pre-defined authorities in the event of a breach of mismatch limits Critical

5.4The system should have the capability to allow scheduling ofautomatic Structural Liquidity Report generation and mismatchlimit verification

Critical

5.5 The system should provide the Structural Liquidity report in theformat prescribed by RBI Critical

5.6The system should be capable of automatically archiving theStructural Liquidity Reports generated by the user, withappropriate time stamps

Critical

Calculation of Balance Sheet Ratios

6.1

The system should allow the user to define criteria for followingasset categories and map the items from the structural liquidityreport, balance sheet and inputs from risk systems to each of thedefined categories

6.1.1 Liquid Assets Critical6.1.2 Core Assets Critical6.1.3 Medium term assets Critical6.1.4 Long term assets Critical

6.1.5 Any other category required for computation of balance sheetratios Critical

6.2

The system should allow the user to define criteria for followingliability categories and map the items from the structural liquidityreport, balance sheet and inputs from risk systems to each of thedefined categories

6.2.1 Tier I capital/ Tier II capital/ Total capital Critical6.2.2 Short term liabilities Critical6.2.3 Medium term liabilities Critical6.2.4 Long term liabilities Critical6.2.5 Core deposits Critical6.2.6 Wholesale Deposits Critical6.2.7 Market Borrowings Critical6.2.8 Any other category Critical

6.3The system should handle and compute below mentioned ratiosas per the formula given by the Bank at the time ofimplementation:

6.3.1 Bulk Deposit / Total Deposit Critical

6.3.2 Deposits Maturing Within 1 Year / Total Deposits (ConsideringRenewal) Critical

6.3.3 Deposits Maturing Within 1 Year / Total Deposits (W/oConsidering Renewal) Critical

6.3.4 Core Assets / Core Liabilities (As per SLS) Critical




Importance


6.3.5 (Volatile Liabilities - Temporary Assets) / (Earning Assets -Temporary Assets) Critical

6.3.6 Core deposits / Total assets Critical

6.3.7 (Term Loans + Mandatory SLR + Mandatory CRR + FixedAssets) / Total Assets Critical

6.3.8 (Term Loans + Mandatory SLR + Mandatory CRR + FixedAssets) / Core Deposits Critical

6.3.9 Temporary Assets / Total Assets Critical6.3.10 Temporary assets / Volatile liabilities Critical6.3.11 Volatile liabilities / Total assets Critical

6.3.12 (Customer deposit + Net worth) / (Total assets – balance withRBI) Critical

6.3.13 Purchase Funds/ Total Assets Critical6.3.14 Net loans/ Customer deposits Critical6.3.15 Time deposits / Total deposits Critical6.3.16 Prime Assets / Total assets Critical6.3.17 Liquid assets / Total assets Critical6.3.18 Short Term Liabilities/ Total assets Critical6.3.19 Liquid assets / Short Term Liabilities Critical6.3.20 Funding volatility ratio (Liquid asset / CASA deposits) Critical6.3.21 Market liabilities / Total assets Critical6.3.22 Un-availed limits / Total advances Critical6.3.23 CASA Ratio Critical6.3.24 Credit-Deposit Ratio Critical6.3.25 Investment-Deposit Ratio Critical

6.3.26 Rate Non-Sensitive Assets to Total Rate Sensitive Assets (Asper IRS) Critical

6.3.27 Customer Deposits to Total Deposits Critical6.3.28 Customer Deposits to Total Assets Critical6.3.29 Top 20 Depositors to Total Deposits Critical6.3.30 Top 50 Depositors to Total Deposits Critical6.3.31 Top 20 Borrowers to Total Advances Critical6.3.32 Top 50 Borrowers to Total Advances Critical6.3.33 Trading Investments to Total Assets Critical6.3.34 BPLR Linked Advances to Total Advances Critical6.3.35 Fixed Rate Advances to Total Advances Critical6.3.36 Base Rate Linked Advances to Total Advances Critical6.3.37 Below Base Rate Advances to Total Advances Critical6.3.38 Bank Deposits to Total Deposits Critical6.3.39 Off-Balance Sheet Exposure to Total Assets Critical




Importance


6.3.40 High Value Deposit to Total Deposit Ratio Critical6.4 Call money borrowings ratio:

6.4.1 The system should be capable of calculating the ratio of callmoney borrowings to capital on a daily basis Critical

6.4.2 The system should be capable of calculating the runningfortnightly average of call money borrowings to capital ratio Critical

6.4.3 The system should be capable of monitoring the limitsprescribed by RBI for the fortnightly average of the ratio Critical

6.4.4 The system should be capable of monitoring the limit prescribedby RBI for the daily value of the ratio Critical

6.4.6 The system should alert the user and predefined authorities inthe event of breach of the limits defined for the ratio Critical

6.5 Call money lending ratio:

6.5.1 The system should be capable of calculating the ratio of callmoney lending to capital on a daily basis Critical

6.5.2 The system should be capable of calculating the runningfortnightly average of call money lending to capital ratio Critical

6.5.3 The system should be capable of monitoring the limit prescribedby RBI for the daily value of the ratio Critical

6.5.4 The system should alert the user and predefined authorities inthe event of breach of the limits defined for the ratio Critical

6.6The system should be capable of calculating total amountsunder each of the categories defined above based on datainputs from balance sheet and/ or structural liquidity statement

Critical

6.7The system should allow users to define formulas for customizedratios to be calculated on the basis of asset/ liability categoriesdefined in above

Critical

6.8 The system should allow users to set/ edit limits for each of theratios defined Critical

6.9The system should calculate any other ratios defined by the userand identify the breaches and alert the predefined set of usersautomatically

Critical

Multiple Bucket Definition

7.1The system should allow users to define their own buckets (co-exist) for Liquidity Risk, Interest Rate Sensitivity, DynamicLiquidity, MIS Reports, etc.

7.1.1 - As per regulatory Critical7.1.2 - As per monthly buckets Critical7.1.3 - Any other user definable bucket Critical

Internal MIS reporting8.1 The system should generate the report for classifying the assets/




Importance


liabilities on the basis of:

8.1.1 Amount range Critical8.1.2 Interest Rate range Critical8.1.3 Maturity Range wise Interest Rate Range Wise Critical8.1.4 Any other category defined by the user Critical

8.1.5 The system should allow user to set/ modify the ranges forgenerating the report Critical

8.2The system should allow users to bucket their liquidity andinterest rate sensitive position as per regulatory requirement aspart of single run/ process

Critical

8.3The system should have capability of reporting Liquidity positionwithout interest for regulatory and with interest for non-regulatoryreporting

Critical

8.4The system should allow users to view “Total Inflow”, “TotalOutflow”, “Gap”, “Cumulative Gap” and “Cumulative Gap %” forperiod range defined by user

Critical

8.5The system should allow users to compare any past 2 SLS/IRST/IRSD/DLS reports and provide line item wiseincrease/decrease in Inflows/ Outflows and final mis-match

Critical

8.6The system should facilitate users with distribution on the basisof contractual maturity across all formats mentioned in previoussection

Critical

8.7 For the overseas branch, system should generate followingreports:

8.7.1 Liquidity Ratio Critical8.7.2 Maturity Mis-Match Report - Currency Wise Critical8.7.3 Cash Flow analysis Critical8.7.4 Loan to Deposit Ratio - Currency Wise Critical8.7.5 Concentration Report - Short Term Liquidity Mis-Match report Critical

8.8 System should be able to generate the following reports fordomestic operations as well as for the ‘Bank as a whole’:

8.8.1Interest Rate Wise Maturity Pattern of Bulk Term Deposits(Contractual Maturity) Critical

8.8.2Interest Rate Wise Maturity Pattern of Bulk Term Deposits(Residual Maturity) Critical

8.8.3Interest Rate Wise Maturity Pattern of Retail Term Deposits(Contractual Maturity) Critical

8.8.4Interest Rate Wise Maturity Pattern of Retail Term Deposits(Residual Maturity) Critical

8.8.5Interest Rate Wise Maturity Pattern of Total Term Deposits -Excl. CDs (Contractual Maturity) Critical

8.8.6Interest Rate Wise Maturity Pattern of Total Term Deposits -Excel .CDs (Residual Maturity) Critical

8.8.7Interest Rate Wise Maturity Pattern of Certificate of Deposits(Contractual Maturity) Critical




Importance


8.8.8Interest Rate Wise Maturity Pattern of Certificate of Deposits(Residual Maturity) Critical

8.8.9Monthly Outstanding with Weighted Average Cost (Retail & BulkTerm Deposits) Critical

8.8.10Monthly Outstanding with Weighted Average Cost - Certificate ofDeposits Critical

8.8.11Month-Wise Maturity Pattern with Weighted Average Cost -Retail Term Deposits Critical

8.8.12Month-Wise Maturity Pattern with Weighted Average Cost - BulkTerm Deposits Critical

8.8.13Month-Wise Maturity Pattern with Weighted Average Cost -Certificate of Deposits Critical

8.8.14Date-Wise Maturity Pattern - Retail Term Deposits (between'From' and 'To' Dates) Critical

8.8.15Date-Wise Maturity Pattern - Bulk Term Deposits (between'From' and 'To' Dates) Critical

8.8.16Date-Wise Maturity Pattern - Certificate of Deposits (between'From' and 'To' Dates) Critical

8.8.17Date-Wise Maturity Pattern of Bulk Deposits With Account LevelDetails (between 'From' and 'To' Dates) Critical

8.8.18Deal Wise Maturity Report of CDs (i.e. CDs Maturing between'From' and 'To' Dates) Critical

8.8.19 Money Market O/s Position Critical

8.8.20Day-Wise Money Market Borrowing/Lending Position (InstrumentWise) (Between 'From' & 'To' Dates) Critical

8.8.21 Asset Class Wise Investments O/s & Sensitivities Critical

8.8.22 SLR/NSLR Wise Investment Classification & O/s Critical

8.8.23Investment Portfolio Wise (i.e. HTM, AFS, HFT) O/s &Sensitivities Critical

8.8.24 Rating-Grade Wise Investments O/s Critical

8.8.25 Rating-Grade Wise Advances O/s Critical

8.8.26A/c Wise Inflow Report of Bulk Deposits (i.e. Bulk Deposit A/csopened between 'From' and 'To' Dates) Critical

8.8.27Deal Wise Inflow Report of CDs (i.e. CDs issued between 'From'and 'To' Dates) Critical

8.8.28A/c Wise Maturity of Bulk Deposits (i.e. Bulk Deposit Maturingbetween 'From' and 'To' Dates) Critical

8.9Actual interest paid / received (in %) on borrowings andadvances respectively as compared to the total weightedaverage interest

Important

Sourcing Required Data and Projections for Dynamic Liquidity

9.1The system should allow users to define the product / instrumentlevel at which the source data and projections must be providedas inputs

Critical




Importance


9.2 The system should allow users to define the time buckets to beused for developing the Dynamic Liquidity profile Critical

9.3The system should be capable of extracting the actual inflowsand outflows for the relevant time buckets from the StructuralLiquidity Report

Critical

9.4The system should have the capability to source projectionsprovided by the business units through an MS Excel file upload/manual input

Critical

9.5 The system should be capable of accepting projections frombusiness units at each of the following levels:

9.5.1 Line of Business Critical9.5.2 General Ledger Critical9.5.3 Line Item as per Dynamic Liquidity format of RBI Critical9.5.4 Product / instrument level Critical9.5.5 Asset class level Critical

9.6 The system should be capable of accepting projections both ateach time bucket level and at an aggregate level. Critical

9.7 The system should be capable of sourcing projections withfollowing parameters:

9.7.1 Origination date Critical9.7.2 Projection Amount/ Total Amount Critical9.7.3 Maturity Date/ Tenure Critical9.7.4 Amortization schedule/ parameter for amortisation schedule Critical9.7.5 Interest rate Critical

9.8 The system should have the capability to allow users to manuallyenter projection data at any desired granularity. Critical

9.9 The system should be capable of accepting projections in theform of:

9.9.1 Absolute figures Critical9.9.2 Percentage Critical9.9.3 Custom expressions Critical

9.10 The system should be capable of accepting the projections inmultiple currencies Critical

9.11 The system should be capable of accepting the projections fromeach jurisdiction/ overseas branch of the Bank separately Critical

Development of Dynamic Liquidity Profile

10.1The system should integrate the projections with the structuralliquidity profile to generate the dynamic liquidity profile as perRBI format and internal MIS

Critical

10.2 The system should allow the user to define rules based on whichaggregated projections will be segregated into different time Critical




Importance


buckets and/or line items


10.4The system should allow the user to define bucketingassumptions for each product or asset/liability type as per RBI orinternal rules of the Bank

Critical

10.5 The system should be capable of accepting bucketingassumptions in the following forms:

10.5.1 Original contractual maturity Critical10.5.2 Residual maturity Critical10.5.3 Percentages to each time bucket for each asset class Critical10.5.4 Custom expression Critical

10.6The system should allow the user to develop multiple dynamicliquidity profiles with different bucketing assumptions, timebuckets and projections

Critical

10.7 The system should allow the user to generate liquidity profiles ateach of the following levels:

10.7.1 Business unit or Zone or Branch level Critical10.7.2 Overall Bank level Critical

10.8The system should allow the user to drill down the dynamicliquidity profile to the desired granularity (i.e. position level,product level, GL Level etc.)

Critical

10.9 The system should be capable of generating the dynamicliquidity profile in multiple currencies Critical

10.10The system should be capable of converting the dynamicliquidity profiles in multiple currencies in one user defined homecurrency

Critical

10.11 The system should be capable of generating the dynamicliquidity profile for different zones/ overseas branch separately Critical

10.12The system should allow users to compute consolidated as wellas currency wise cost to close using borrowing as well as assetliquidation on dynamic gaps

Critical

10.13The system should be capable of consolidating the multipledynamic liquidity profiles in the same currency as per userpreference

Critical

10.14The system should allow users to facilitate projections for userdefine horizon period. E.g.: 3 months, 12 months, 3 years, 5years etc.

Critical

10.15 System should be capable of computing impact on Liquidity andBank's interest rate sensitivity for longer term Critical

10.16 The system should be capable of computing NII/ NIM on a 1year rolling basis Critical

10.17The system should be able to compute revised NII/ NIM on thebasis of user defined yield curve across interest sensitive assets/liabilities or shift from the current curve

Critical




Importance


10.18 System should also allow users to define projections on aquarterly basis and revise them every month. Critical

Dynamic liquidity mismatch limit monitoring and reporting

11.1 The system should be capable of accepting dynamic liquiditymismatch limits in form of:

11.1.1 Absolute figures Critical11.1.2 Percentage of total outflow in a time bucket Critical11.1.3 Cumulative mismatch limits Critical11.1.4 Custom expression Critical



11.4The system should have the capability to allow scheduling ofautomatic Dynamic Liquidity Report generation and mismatchlimit verification

Critical

11.5 The system should provide the Dynamic Liquidity report in theformat prescribed by RBI Critical

11.6The system should be capable of automatically archiving theDynamic Liquidity Reports generated by the user, withappropriate time stamps

Critical

Dynamic liquidity report: Back testing

12.1

The system should be capable of conducting a back testing ofdynamic liquidity reports by comparing archived dynamic liquidityreport as on a date with structural liquidity report on the targethorizon date

Critical

12.2The system should be capable of calculating the differences inprojected values in dynamic liquidity report and actual values instructural liquidity report at each of the following levels:

12.2.1 Time bucket Critical12.2.2 Product level Critical12.2.3 GL Level Critical

12.3 The system should be capable of identifying the mismatch inprojected and actual values in following terms Critical

12.3.1 Absolute figures Critical12.3.2 Percentage terms Critical

Development of Interest Rate Sensitivity Profile - Traditional Gap Approach

13.1 The system should be capable of generating the Interest ratesensitivity profile as and when required Critical




Importance


13.2The system should support the classification of assets andliabilities into precise time buckets and generation of the InterestRate Sensitivity Profile on a branch-wise and region-wise basis

Critical


13.4 The system should allow users to define the time buckets to beused for developing the Interest Rate Sensitivity profile. Critical

13.5The system should allow the user to define bucketingassumptions for the repricing cash flows occurring for eachproduct or asset / liability type.

Critical

13.6 The system should be capable of accepting bucketingassumptions for the repricing cash flows in the following forms:

13.6.1 All outstanding balances as per re-pricing tenor Critical

13.6.2 As a percentage of total outstanding to be assigned to each timebucket, at a product level or an asset class level Critical

13.6.3 Custom expression Critical

13.7The system should ensure that when outstanding balances arebucketed as per repricing tenor, cash flows occurring prior to therepricing bucket are bucketed as per residual maturity

Critical

13.8The system should allow the user to develop multiple interestrate sensitivity profiles with different bucketing assumptionsand/or time buckets

Critical

13.9 The system should allow the user to generate interest ratesensitivity profiles at any of the following levels:

13.9.1 Product level Critical13.9.2 Portfolio Level Critical13.9.3 Book Wise (Banking Book/ Trading Book Level) Critical13.9.4 Business unit level Critical13.9.5 Overall Bank level Critical13.9.6 Any other level, based on custom rules Critical

13.20 The system should be capable of computing Earnings at Riskand Impact on NII based on the interest rate sensitivity profile. Critical

13.21The system should allow the user to drill down from the interestrate sensitivity profile to the desired granularity (i.e. positionlevel, product level, asset class level, account level etc.)

Critical

13.22 The system should allow user to define/ change the homecurrency. Critical

13.23The system should also be capable of converting interest ratesensitivity profiles generated from one currency into user definedhome currency.

Critical

13.24The system should be capable of aggregating selected interestrate sensitivity profiles in the same currency into oneconsolidated profile.

Critical




Importance


13.25Post development of the Interest rate profile, the system shouldconduct automatic validation checks to ensure that aggregateasset and liability balances are equal

Critical

13.26The system should be capable of generating the Interest ratesensitivity profiles for the Bank and its subsidiaries separately ateach of the following levels

13.26.1 Indian operations- Domestic currency Critical

13.26.2 Indian operations- Foreign currency (Separately for Significantand Residual Currencies) Critical

13.26.3 Consolidated Indian operations (home currency) Critical

13.26.4 Overseas operations country wise (in each currency convertedinto home currency) Critical

13.26.5 Consolidated operations at bank level (reporting currency) Critical

13.27The system should be capable of generating interest ratesensitivity profiles for user defined future dates based on currentbalance sheet position.

Critical

13.28The system should be capable of generating interest ratesensitivity profiles for user defined future dates considering cashflow projections.

Critical

13.29

The system should be flexible to use different basis fordistribution in SLS and IRS. For e.g.: Small Deposit in SLSneeds to be distributed on the basis of residual maturity in SLSand on the basis of behavioural in IRS

Critical

Development of Interest Rate Sensitivity Profile- Duration Gap Approach

14 The system should allow user to define customized curves ascoupon curves and yield curves Critical

14.1The system should be capable of accepting the data feeds fromexternal agencies such as FIMMDA, Reuters, Bloomberg, flatfiles and to be used as coupon and yield curves

Critical

14.2 The system should have the ability to define product-wise asset/liability categories, sub-categories and define product hierarchies Critical

14.3The system should allow user to map the product categories/sub categories/ individual positions to coupon rate curves/ yieldrate curves defined in the system

Critical

14.4 The system should allow user to define coupon and yield rates atindividual cash flow level Critical

14.5 The system should be capable of determining the modifiedduration of assets and liabilities at a position level Critical

14.6The system should be capable of calculating the weightedaverage modified duration for product category/ sub categoriesdefined by the user

Critical

14.7The system should allow the user to develop multiple interestrate sensitivity profiles with different bucketing assumptionsand/or time buckets

Critical




Importance


14.8 The system should allow the user to generate interest ratesensitivity profiles at any of the following levels:

14.8.1 - Product / instrument level Critical14.8.2 - Sub-unit level Critical14.8.3 - Business unit level Critical14.8.4 - Overall Bank level Critical14.8.5 - Any other level, based on custom rules Critical

14.9 The system should allow the user to generate duration gapanalysis profiles at any of the following levels:

14.9 - Product / instrument level Critical14.9 - Sub-unit level Critical14.9 - Business unit level Critical14.9 - Overall Bank level Critical14.9 - Any other level, based on custom rules Critical

14.10The system should be capable of computing modified durationgap and Impact on MVE based on the interest rate sensitivityprofile as per the requirement of RBI.

Critical

14.11The system should allow the user to drill down from the interestrate sensitivity profile to the desired granularity (i.e. positionlevel, instrument level, product level, asset class level)

Critical

14.12 The system should allow user to define/ change the homecurrency. Critical

14.13The system should also be capable of converting interest ratesensitivity profiles generated in other currencies into one userdefined home currency.

Critical

14.14The system should be capable of aggregating selected interestrate sensitivity profiles in the same currency into oneconsolidated profile.

Critical

14.15Post development of the interest rate sensitivity profile underDGA, the system should conduct automatic validation checks toensure that aggregate asset and liability balances are equal

Critical

14.16

System should compute month wise EVE, Impact on NII withchange in 100,200, 300bps, Modified Duration Gap and MarketValue of Equity with a comparison of change in NII due toparallel shift by 100, 200, 300 bps

Critical

14.17The system should be capable of generating interest ratesensitivity profiles for user defined future dates based on currentbalance sheet position.

Critical

Interest rate sensitivity mismatch limit monitoring and reporting

15.1 The system should be capable of accepting interest ratesensitivity mismatch limits in form of:

15.1.1 Percentage of total outflow in a time bucket Critical15.1.2 Net mismatch limits as a percentage of Bucket RSA/ Equity/ Critical




Importance


Total assets/ Total RSA

15.1.3 Cumulative mismatch limits Critical15.1.4 EaR limits Critical15.1.5 MVE impact limits Critical15.1.6 Duration gap limits Critical



15.4The system should have the capability to allow scheduling ofautomatic Interest Rate Sensitivity Report generation andmismatch limit verification

Critical

15.5

The system should be capable of automatically archiving theInterest Rate Sensitivity Reports generated by the user withappropriate time stamps> User should be able to retrieve pastreports (all) using the front end

Critical

Other regulatory requirements

16.1The system should be able to segregate the total investmentportfolio in following categories and accordingly bucket thesensitivity:

16.1.1 - Available for Sale ('AFS') Critical16.1.2 - Held For Trading ('HFT') Critical16.1.3 - Held Till Maturity ('HTM') Critical16.1.4 - Any other user defined category Critical

16.2The system should be capable of generating the report havingfollowing components for the three sub-portfolios mentionedabove separately as well as consolidated:

16.2.1 - Book value Critical16.2.2 - Realisable value Critical16.2.3 - PV01 Critical16.2.4 - Modified duration Critical16.2.5 - Outstanding amount Critical

16.3 The system should be able to generate report for DGA as perrequirement of RBI Critical

16.4 The system should allow users to compute product wise reporton Cost of Fund/ Yield on Asset Critical

16.5 The system should have provisions to compute NII and NIMComputation Critical

16.6The system should have pre built models for predicting InterestRates and thereby compute Interest Income, Interest Expensesand the NII

Critical




Importance


Extraction of transaction data for Behavioural analysis

17.1

The system should interface with all operational systemscurrently being used by the Bank's business units to extract endof day portfolio level/account level data for following items fromeach source system

17.1.1 Current Accounts Critical17.1.2 Savings deposits Critical17.1.3 Cash Credit ('CC') Critical17.1.4 Overdrafts ('OD') Critical17.1.5 Demand loans ('DL') Critical17.1.6 Un-availed limits of CC/OD/DL Critical17.1.7 Bills payable Critical17.1.8 Premature withdrawal of retail term deposits Critical17.1.9 Prepaid term loans Critical17.1.10 Renewed retail term deposits Critical17.1.11 Total term loans outstanding Critical17.1.12 Total deposits due for maturity Critical17.1.13 Total deposits outstanding Critical17.1.15 Devolvement of LCs/ Invoked BGs Critical17.1.16 Premature withdrawal of Bulk term deposits Critical17.1.17 Renewed wholesale term deposits Critical17.1.18 Renewed WCDL Critical17.1.19 Any other non-maturity products Critical17.1.20 Any other products containing embedded options Critical

Development of behavioural pattern results

18.1

The system should be capable of performing the statisticalanalysis on the archived portfolio level/account level data, todetermine the core and volatile portions for following products ,currency wise:

18.1.1 Current Accounts Critical18.1.2 Savings deposits Critical18.1.3 Drawn portions of CC Critical18.1.4 Drawn portions of OD Critical18.1.5 Drawn portions of DL Critical18.1.6 Bills payable Critical18.1.7 Any other non-maturity products Critical18.1.8 EEFC Critical18.1.9 RFC Critical




Importance


18.2

The system should be capable of performing the statisticalanalysis on the archived portfolio level/account level data, todetermine the behavioural pattern of following products, currencywise:

Critical

18.2.1 Pre mature withdrawal of retail term deposits Critical18.2.2 Prepayment of term loans Critical18.2.3 Rollover pattern of retail term deposits Critical18.2.4 Invocation/ Devolvement pattern of LCs/ BGs Critical18.2.5 Pre mature withdrawal of wholesale term deposits Critical18.2.6 Rollover pattern of wholesale term deposits Critical18.2.7 Rollover pattern of WCDL Critical18.2.8 Any other products containing embedded options Critical

18.2.9 The system should allow user to select the time interval forwhich the statistical analysis is to be performed Critical

18.2.10

The system should make available option of results ofbehavioural studies to automatically use them for preparation ofstructural liquidity statement and interest rate sensitivitystatement

Critical

18.2.11 The system should be capable of storing the results of pastbehavioural studies Critical

18.2.12 The system should allow user to schedule the statistical analysisto be performed Critical

18.2.13 The behavioural study reports should be generated as and whenrequired Critical

18.2.14The system should enable the back testing of results generatedby comparing the forecasted percentages vis-à-vis actual figuresfrom balance sheet

Critical

18.2.15 For Back testing, the system should allow users to select theperiod on which Back Testing needs to be applied Critical

18.3The system should interface with all operational systemscurrently being used by the Bank, to extract transaction datafrom each source system in respective currencies

Critical

18.4 The system should be scalable and allow the interfacing of othersystems as and when such systems are procured/implemented Critical

18.5As a back-stop measure, the system should support the manualupload of transaction data from various operational systems informats provided by the Bank

Critical

18.6System should have the capability to re-plot line items andregenerate historical reports/statements based on changes inassumptions plotting of line items.

Critical

Stress Testing




Importance


19.1

Users, at the minimum, should be able to define scenarios forLiquidity Risk under 3 categories- Bank Specific- Market Specific- Combined

Critical

19.2 Line item wise liquidity profile at a product / business unit level/branch wise/ consolidated level Critical

19.3 The system should allow the user to develop and save scenariosbased on any or all of the following: Critical

19.3.1 Redefine haircuts on investment portfolio Critical19.3.2 Increase/ decrease Prepayment/ Rollover of Loans/ Deposits Critical

19.3.3 Re-define current market rates and review impact on marketvalue of assets. Actual market rates should remain intact Critical

19.3.4 Allow users to simulate scenario of selling long term investments Critical

19.3.5System should allow users to simulate fall in Market Value ofderivatives like Options and Swaps and view their impact onSLS/ IRS reports

Critical

19.3.6 It should be configurable for users to define any other scenariofor stressing liquidity and interest rates Critical

19.4 The system should be able to build following stress scenariosand corresponding stress levels Critical

19.4.1 Scenarios to include significant strategic or reputational risk inparticular for significant business lines Critical

19.4.2 Scenarios to include, where relevant, an episode of financialmarket turbulence or a shock to market liquidity; Critical

19.4.3Scenarios under which capital might not be freely transferablewithin banking groups in periods of severe downturn or extendedmarket disruption;

Critical

19.4.4 Scenarios under which a crisis impairs the ability of even veryhealthy banks to raise funds at reasonable cost Critical

19.4.5 Scenarios under which model-embedded statistical relationshipsbreak down Critical

19.4.6 Scenarios under which risk characteristics of new productsprojected on the basis of limited historical data are challenged Critical

19.4.7Scenarios to include simultaneous pressures in funding andasset markets, and the impact of a reduction in market liquidityon exposure valuation, etc.

Critical

19.5 System should allow users to identify components of LiquidityBuffer at Product and/ or GL level in the system Critical

19.6

Based on the identification, system should separate the itemsidentified under Liquidity Buffer from the user selected SLSstatement and recomputed the Liquidity Gaps in the selectedGap Report

Critical

19.7 System should compute the Liquidity Buffer Critical19.8 System should compute Survival Horizon Period Critical




Importance


19.9The system should allow the user to specify the amount ofinflows or outflows in each time bucket to be considered forstress testing

Critical

19.10The system should be able to compute consolidated as well ascurrency wise "Cost to Close", the static/ dynamic liquidity gapsusing stressed scenarios

Critical

19.11The system should take in to account the cost of additionalborrowing as well as cost of asset liquidation to compute "Cost toClose" along with the impact on capital

Critical

19.12 System should allow users to compute liquidity and interest ratestress on the dynamic Balance Sheet Critical

19.13 The system should allow the user to determine the impact of thefollowing movements in the yield curve on the NII and EVE: Critical

19.13.1 Parallel movements Critical19.13.2 Non-parallel movements Critical19.13.3 Inversion of curve Critical

19.14 The system should allow user to develop scenarios in multiplecurrencies separately Critical

19.15

The system should have provisions to review impact on InterestIncome/ Interest Expense and NII across Rate Sensitive Assetand Rate Sensitive Liabilities due to stress in yield curve onimmediate basis

Critical

19.16

The system should have provisions to review impact on InterestIncome/ Interest Expense and NII across Rate Sensitive Assetand Rate Sensitive Liabilities due to stress in yield curve at alater date

Critical

19.17

The system should also be able to evaluate the Income/expense/ NII/ NII increase or decrease in percentages due to theabove mentioned change in yield curve as part of the samereport

Critical

19.18System should provide a front screen to capture Net Worth ofthe Bank and Compute the NII as a percentage of Net Worthunder each of the scenario

Critical

19.19The system should be capable of allowing the user to retrievesaved scenarios and specify the portfolio on which to conductthe stress test / simulation.

Critical

19.20The system should allow the user to determine stressed liquidityratios such as the Liquidity Coverage Ratio (LCR) and the NetStable Funding Ratio (NSFR)

Critical

19.21The system should compute the impact for all stress levelsdefined under Basel III requirement and as per guidelinesreleased by RBI

Critical

19.22The system should allow the user to manually input the CRARand Tier I and Tier II capital details and RWA under Credit,Market and Operational Risk

Critical

19.23 System should allow users to view the impact of stress on theCRAR Critical

19.24 System should be able to perform stress levels under 'reverse Critical




Importance


stress testing'

19.25

System should be capable of re-plotting line items andregenerating reports/statements based on changes in inputssuch as GL Balance, percentage in each bucket, and any otherparameters used in such reports by way of simulation.

Report generation

20.1 The system should be capable of archiving the computed StressTest Results, with appropriate time stamps and currencies Critical

20.2The system should be configurable to define the authorities towhom the computed Stress Test Results must be circulated andthe frequency of circulation.

Critical

20.3 The system should support intraday liquidity reporting Critical

Calculation of Liquidity Coverage Ratio

21.1 The system should be capable of computing LCR in accordancewith RBI guideline and in the format specified by RBI Critical

21.2The system should be capable of calculating the total highquality liquid assets available by summing up Level 1 and Level2A, 2B high quality liquid assets

Critical

21.3 The system should be capable of identifying Level 1 high qualityliquid assets at position level based on: Critical

21.3.1 Asset class Critical21.3.2 Issuer Critical21.3.3 Any other criteria Critical

21.3.4 The system should be capable of applying adjustments to theLevel 1 high quality liquid assets as per the RBI guidelines Critical

21.4 The system should be capable of identifying Level 2A, 2B highquality liquid assets at position level based on: Critical

21.4.1 Asset class Critical21.4.2 Issuer Critical21.4.3 Risk Weights Critical21.4.4 Any other criteria Critical

21.5 The system should be capable of applying haircuts to Level 2high quality liquid assets as per the RBI guidelines Critical

21.6 The system should be capable of applying adjustments to theLevel 2 high quality liquid assets as per the RBI guidelines Critical

21.7The system should ensure that proportion of Level 2 liquidassets after applying the haircut remains within the regulatorylimit prescribed

Critical

21.8 The system should allow users to list Investments in securitiesissued by 0% risk weighted foreign sovereigns Critical




Importance


21.9

The system should allow users to list Investment in securitiesrepresenting claims on or claims guaranteed by sovereigns,PSEs or multilateral development banks that are assigned a20% risk-weight

Critical

21.10 The system should be capable of calculating net outflows in thenext 30 days based on the position level cash flow data Critical

21.11 The system should allow user to enter the internal as well asregulatory limits for liquidity coverage ratio Critical

21.12The system should be capable of calculating the liquiditycoverage ratio and alert the user and pre-defined authorities inevent of breach of regulatory/ internal limit

Critical

21.13 The system should be capable of calculating the liquiditycoverage ratio for significant multiple currencies separately Critical

21.14The system should be capable of calculating the liquiditycoverage ratio separately for domestic operations, eachoverseas branch and at a consolidated level

Critical

21.15 The system should be able to use the run off factor Critical

Calculation of Net Stable Funding Ratio

22.1 The system should be capable of computing LCR in accordancewith RBI guideline and in the format specified by RBI Critical

22.2The system should be capable of calculating available stablefunding based on position level cash flow data available forliabilities

Critical

22.3The system should be capable of applying available stablefunding factor as per the RBI guidelines to each of the productcategory included in the calculation of available stable funding

Critical

22.4The system should be capable of calculating the required stablefunding based on position level cash flow data available forassets

Critical

22.5The system should be capable of applying required stablefunding factor as per the RBI guidelines to each of the productcategory included in the calculation of required stable funding

Critical

22.6The system should be capable of identifying the required stablefinding factor to be applied to off balance sheet exposures basedon the results of behavioural studies conducted in the system

Critical

22.7 The system should allow user to enter the internal limit for netstable funding ratio Critical

22.8The system should be capable of calculating the net stablefunding ratio and alert the user and pre-defined authorities inevent of breach of regulatory/ internal limit

Critical

22.9 The system should be capable of calculating the net stablefunding ratio for significant multiple currencies separately Critical

22.10The system should be capable of calculating the net stablefunding ratio separately for each overseas branch and at aconsolidated level also.

Critical




Importance


Statement of funding concentration

23.1The system should be capable of identifying and listingcounterparties contributing more than user defined thresholdlimit for following categories using position level data

Critical

23.1.1 Deposits Critical23.1.2 Borrowings Critical23.1.3 Any other user defined category Critical

23.2 The system should be capable of identifying and listing top 20depositors describing details of following types of deposits Critical

23.2.1 Current deposits Critical23.2.2 Savings deposits Critical23.2.3 Term deposits Critical

23.3 The system should be capable of identifying the top 20borrowings Critical

23.4 The system should be capable of identifying significant products/instrument Critical

23.5 The system should be capable of identifying and listing down thedetails of significant funding sources through securitization Critical

23.6 The system should be capable of generating the statement inmultiple currencies separately Critical

23.7 The system should be capable of significant borrowings anddeposits Critical

23.8 The system should be capable of generating the statement foreach overseas branch and at a consolidated level also. Critical

23.9 The system should be capable of identifying and listing top Critical

23.10 The system should compute funding concentration in the formatprescribed by RBI Critical

Statement of Available Unencumbered Assets

24.1 The system should be capable of identifying the unencumberedassets from position level data Critical

24.2The system should be capable of identifying the haircut requiredby the market for collateralization of unencumbered asset fromposition level data

Critical

24.3The system should be capable of identifying the unencumberedassets and the haircut necessary in multiple geographies andmultiple significant currencies separately from position level data

Critical

Statement on other information on liquidity

25.1The system should be capable of identifying the movement inequity prices for the period of one month based on data fed fromexternal market sources

Critical




Importance


25.2The system should be capable of extracting the interest ratesand tenors for bond and certificate of deposits issued by thebank for last one month based on position level data

Critical

Reporting Requirements

26.1The system should allow the user to generate currency wise aswell consolidated SLS/ IRS/ DGA profiles at any of the followinglevels:

Critical

26.1.1 - Product level Critical26.1.2 - Portfolio Level Critical26.1.3 - Branch level Critical26.1.4 - Book Wise (Banking Book/ Trading Book Level) Critical26.1.5 - Region / Zone Level Critical26.1.6 - Business unit level Critical26.1.7 - Overall Bank level Critical26.1.8 - Any other level, based on custom rules Critical

26.2 The system should allow users to view limits and displayexceptions when compared with limits/ benchmarks Critical

26.3

The system should be capable of generating the liquiditycoverage ratio report for significant currencies and multiplegeographies as and when required in the format prescribed byRBI

Critical

26.4The system should be capable of generating the net stablefunding ratio report as and when required in the formatprescribed by RBI

Critical

26.5The system should be capable of generating the statement offunding concentration as and when required in the formatprescribed by RBI

Critical

26.6The system should be capable of generating the statement ofunencumbered assets as and when required in a formatprescribed by RBI

Critical

26.7The system should be capable of generating the statement onother information on liquidity as and when required in formatprescribed by RBI

Critical

Support for System Based Analysis

27.1 The system should support the following analysis andcomputations: Critical

27.1.1 SLR calculation with a customizable bucket-wise breakup Critical27.1.2 Duration analysis Important

27.1.3 Variance analysis between annual operating plan vs. actualperformance at a business unit level Critical

27.2 The system should be capable of conducting the followinganalysis for the purpose of management reporting: Important




Importance


27.2.1 Net interest income Critical27.2.2 Economic Value of Equity Important

27.3 The system should allow users to perform back dated analysison all/ any reports in this RFP Critical

27.4 The system should allow users to review/ generate reports onpost audit data on all/ any reports in this RFP Critical

Regulatory Reporting

28.1The system, at the minimum, should support the generation ofthe following reports/statements in the regulatory/statutoryprescribed formats:

Critical

28.1.1 Statement of structural liquidity at following levels: Critical

28.1.1.1 Statement of structural liquidity - Domestic currency, Indianoperations Critical

28.1.1.2Statement of structural liquidity - Foreign currency, Indianoperations (in each currency as well as converted into homecurrency)

Critical

28.1.1.3 Statement of structural liquidity - Overseas operations countrywise (in each currency as well as converted into home currency) Critical

28.1.1.4 Statement of structural liquidity - Combined Indian operations –Domestic and Foreign Currency Critical

28.1.1.5 Statement of structural liquidity – Consolidated Bank operations Critical

28.1.1.6 Statement of structural liquidity - Currency wise Gap Analysis (Consolidated for Non-Significant currencies in single currency) Critical

28.1.2 Statement of short term dynamic liquidity at following levels: Critical28.1.2.1 Statement of short term dynamic liquidity - Domestic operations Critical

28.1.2.2 Statement of short term dynamic liquidity - Overseas operations(Jurisdiction wise) Critical

28.1.2.3 Statement of short term dynamic liquidity - Overseas operations(Overall overseas positions) Critical

28.1.3.1 Statement of interest rate sensitivity - Traditional Gap Approach(Currency wise) Critical

28.1.3.2. Statement of Modified Duration Gap (Currency wise) Critical28.1.3.3 Report in computation of impact on MVE Critical28.1.4.1 Statement on Liquidity Coverage Ratio (Consolidated level) Critical

28.1.4.2 Statement on Liquidity Coverage Ratio (Significant currencywise) Critical

28.1.4.3 Statement on Net Stable Funding Ratio Critical28.1.4.4 Statement of Funding Concentration Critical28.1.4.5 Statement of Available Unencumbered Assets Critical28.1.4.6 Statement on Other Information on Liquidity Critical

28.1.4.67 Statement of balance sheet ratios as per Basel III guidelinesstipulated by RBI Critical




Importance


28.2 The system should support the generation of the followingregulatory-statutory reports for disclosure purpose: Critical

28.2.1 Liquidity Coverage Ratio (in the RBI prescribed disclosureformat) Critical

28.2.2 Maturity Pattern of Certain Items of Assets & Liabilities Critical

28.3 Any other regulatory/statutory ALM reports in the prescribedformats/ Critical

Report Customization

29.1 The system should have a report builder tool for customizationand generation of reports. Critical

29.2 The system should generate reports based on available data asper any user defined format. Important

29.3The system should be flexible in allowing users to specify theexact layout of the required report including location of fields,header, footer, page numbering, title etc.

Important

29.4The system should be flexible in allowing users to definestructures and fields of each report by selecting fields fromdatabases of their choice.

Important

29.5 The system should allow reports to be exported into MicrosoftExcel, Adobe PDF format and other databases. Critical

29.6 The system should allow users to print reports directly from thesystem. Critical

29.7 The system should allow users to save reports to a disc in a non-editable as well as an editable format. Important

29.8 The system should provide context sensitive help to guide usersto form the reports required by them. Important

29.9The system should have a report writing wizard that providesusers with step by step menus and allows them to draw upreports in the required format.

Critical

29.10 The system should allow users to present outputs from reports inthe form of graphs, charts and other graphic representation Critical

29.11 The system should allow for filtering and sorting of data inreports. Critical

Scheduling of Reports

30.1 The system should allow for generation of pre-defined end-of-day, end of week and end-of month reports. Critical

30.2 Pre-defined reports should be generated with a minimum of userinvolvement. Critical

30.3 The system should have the capability to assign frequency ofgeneration to each report, including but not limited to: Critical

30.3.1 Daily Critical30.3.2 Weekly Critical30.3.3 Fortnightly Critical




Importance


30.3.4 Monthly Critical30.3.5 Quarterly Critical30.3.6 Half-yearly Critical30.3.7 Annual Critical30.3.8 Any other frequency Critical

30.4 The system should have the ability to define a schedule forreports. Critical

30.4.1Any exception, data non availability, exception caused due tobreach of limits should lead trigger automatic sending reports tousers as defined by the System Admin

Critical

30.4.2 The system should allow defining the users to whom reports areto be automatically sent. Critical

Archiving of Reports31.1 The system should allow for archiving of reports in the following

relevant formats: Critical

31.1.1 Adobe PDF Critical31.1.2 Microsoft Excel Critical31.1.3 Microsoft Word Critical31.1.4 Microsoft Access Critical31.1.5 Comma separated values (.CSV) Critical

31.2 The system should allow for archiving of circulars, notificationsand other communication received from regulators. Critical

31.3 The system should archive historical rates extracted from marketinformation systems Critical

31.4 The system should allow for archiving of historical reports. Critical

31.5 Archiving of reports should be possible in a pre-defined format tofacilitate ease of retrieval. Critical

31.6 The system should have a provision in the front end to archiveany of the past reports generated by the system Critical



5.2 Technical Requirement

Sl. No RequirementImportance(Critical /Important /Desirable)

1 Multiple Currency Support

1.1The system should support multiple currencies including USD, INR,EUR, AUD, CHF, JPY, GBP etc. The system should also be scalableso as to support other currencies as and when they get added.

Critical

2 Multiple entity support

2.1

The system should provide full support for multiple organizationallevels and relationships, including regional offices, branches,subsidiaries, and within each hierarchy the system should alsosupport multiple levels of hierarchy.

Critical

2.2 The system should support Asset Liability Management at each of thefollowing levels: N/A

2.3 Multiple Country Critical2.4 Multiple Currency Critical2.5 Multiple Business units Critical2.6 Multiple Branches Critical2.7 Multiple Products Critical2.8 Multiple Product Categories Critical2.9 Multiple Customer Categories Critical3 Data Validation for Manual Inputs

3.1 The system should perform logical checks on all manual input fields. Critical

3.2 The system should provide intelligent edit error messaging to assistcorrection and re-entry of data. Important

3.3 The system should flag the entries that cause edit errors. Critical

3.4The system should have the ability to flag specific data forinvestigation where the data does not fit in a reasonable range or isincomplete.

Important

3.5 The system should be capable of allowing the user to over-ride editederrors and should generate the log of such cases. Critical

3.6 The system should support maker-checker work steps for everymanual input or manual upload of data. Important

4 Day Count, Business Day and Holiday Conventions

4.1 The system should handle all types of day count basis including30/360, Actual/360, Actual/365, Actual/Actual, 30E/360 etc. Critical

4.2The system should support internationally accepted business dayconventions such as following, modified following, preceding, nextmonth, this month, average of the month etc.

Critical




4.3The system should load calendar schedules from external sourcesincluding but not limited to SWIFT, International Holiday schedule andBloomberg holiday schedule etc.

Important

4.4 The system should allow calendar schedules to be set by usersdirectly in the system and/ or through interfaces / patch updates. Critical

4.5 The system should allow for multiple holiday tables for each currencyand country. Critical

4.6 The system should allow users to edit and override global calendarand holiday tables. Critical

4.7 The system should move value dates based on holidays declared atthe last moment. Critical

4.8 The system should model cash flows and interest accruals based onholiday calendar and standard day roll conventions. Critical

5 Currency Translation

5.1The system should convert between currencies without converting tothe home currency as an interim step in the process using externally

fed/ user defined exchange ratesCritical

6 Product Set-up

6.1The system should allow for the creation of products, sub-productsand corresponding codes in line with those present on the operationalsystems.

Critical

7 Ease of Use

7.1 The system should support quick and easy navigation e.g. provision offunction keys/hot keys with drop-down help. Important

7.2 The system should provide print facility i.e. print to file, print screen,print to printer etc. Critical

7.3 The system should have a user friendly menu structure to lessen thelearning curve for the user Important

8 User Interfaces

8.1 The system should provide a consistent and user-friendly MicrosoftWindows based interface. Important

8.2 The system should generate intelligent error messages based on pre-defined parameters. Important

8.3 The system should provide online and offline context sensitive help. Critical

8.4 The system should provide users the ability to define menus andshortcuts. Desirable

8.5 The system should interface with mail clients and corporate instantmessenger service to generate notifications and auto-mailers. Critical

8.6 Specific reports should be made available in a graphical mode. Thisshould be configurable. Critical

8.7 Report Creation utility should be provided for the user to generate newreports. Critical

8.8 The system should provide user-friendly design, short-cuts, smart tagsand other productivity features Important




8.9 The system should allow the user to filter, sort and assimilate data. Critical9 Help Facility

9.1 The system should provide “Help” facility which is context sensitive ata field, screen level etc. Important

9.2 The “Help” facility should explain probable causes of errors andpossible solutions. Important

9.3 Manual documentation i.e. user manuals, system managementmanuals, technical manual, training manuals etc. should be provided. Critical

9.4 The text content in help messages and error alerts should becustomizable. Important

9.5 The system should provide intuitive and current online documentationcovering scope of application. Important

9.6 Online support for the application and updated user manuals shouldalso be provided from time to time. Critical

10 Report Generation

10.1 Existing reports and existing formats of all MIS reports should besupported by the system. Critical

10.2 The system should generate all Regulatory reports pertaining to banksas required by the following regulators: N/A

10.3 Reserve Bank of India Critical10.4 Securities and Exchange Board of India Critical10.5 National Stock Exchange Critical10.6 Bombay Stock Exchange Critical10.7 Host regulators for international branches and subsidiaries Critical10.8 Other regulators Critical

10.9 The system should be flexible to accommodate changes in formats ofregulatory/ MIS reports Critical

10.1o MIS Reports to top management should have the ability to providedrill-down where necessary. Critical

10.11 Exception and breach reports should be generated as and when thebreach occurs. Critical

10.12 Exception reports should be sent to pre-defined users either throughauto-mailers via the e-mail client or via pop-ups within the system. Critical

11 Report Customization

11.1 The system should generate reports based on available data as perany user defined format. Important

11.2The system should be flexible in allowing users to specify the exactlayout of the required report including location of fields, header, footer,page numbering, title, etc.

Important

11.3The system should be flexible in allowing users to define structuresand fields of each report by selecting fields from databases of theirchoice.

Important




11.4 The system should allow reports to be exported into Microsoft Excel,Adobe PDF format and other databases. Critical

11.5 The system should allow users to print reports directly from thesystem. Critical

11.6 The system should allow users to save reports to a disc in a non-editable as well as an editable format. Important

11.7 The system should provide context sensitive help to guide users toform the reports required by them. Important

11.8The system should have a report writing wizard that provides userswith step by step menus and allows them to draw up reports in therequired format and define the frequency of the report generation.

Critical

11.9o The system should allow users to present outputs from reports in theform of graphs, charts and other graphic representation Critical

11.11 The system should allow for filtering and sorting of data in reports. Critical12 File Import and Export Functionality

12.1The system should have a flat file import and export functionality toimport and export transaction data and static data in various formats,including but not limited to:

N/A

12.2 Microsoft Excel Format (.XLS) Critical12.3 Web Page (.HTML) Important12.4 Comma separated values (.CSV) Critical12.5 Text file (.TXT) Critical12.6 Microsoft Word (.DOC) Critical12.7 Adobe Reader (.PDF) Critical12.8 ASCII (Flat File) Critical12.9 Extended Markup Language (XML) Critical

12.1o The system should allow for extraction of all data from the systemwhich includes but is not limited to: N/A

12.11 Transaction details Critical12.12 Static data (masters) Critical12.13 Current market information Critical12.14 Historical market information Critical12.15 Audit trails Critical

12.16 The system should validate the number of records exported /imported. Critical

13 System Availability

13.1The 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.

Critical

13.2The system should be capable of running background batchoperations and automatically uploading all transaction data from theoperational systems on an EOD basis every day through a staging

Critical




area.

13.3 The data upload from operational systems may also be initiatedmanually at any time by the user. Critical

13.4 The system should support simultaneous use of the system bymultiple users without significant performance and integrity issues. Critical

14 Integration With Other Systems

14.1 The integration should be through exposed APIs and/or a staging areaand not through any change in code. Critical

14.2 Integration should be supported across all platforms. Critical

14.3 The system should capture and utilize static data associated withcounterparties, products, accounts etc. Critical

14.4The system should ensure that there are effective checks and controlsto ensure that transactions are not loaded multiple times in thesystem.

Critical

14.5 The system should hold data in an error queue pending review whenthe data fails criteria for uploading into the system. Critical

14.6 The system should allow for changing error queue criteria without hardcoding. Critical

15 System architecture15.1 The system should be built in a Client Server Architecture model. Critical15.2 The system should be platform independent. Critical

15.3 The client environment should be Windows XP/ Windows VISTA/Windows 7&8. Critical

15.4The system should be available in complete browser basedenvironment for connected / networked locations as also in fat / thinclient-server modes

Critical

15.5 The system should be available in fat / thin client modes. Important16 Data archiving

16.1 System should support archiving of data / reports that are beyond aspecified time horizon. The time horizon should be parametric. Critical

16.2 Export of data to secondary storage device should be supported bythe system without down-time. Critical

16.3System should support data retrieval – from the specified archives.The archival and retrieval programs shall facilitate easier analysis ofold data.

Critical

16.4 The system shall possess in-built data warehousing capabilities orstandard interface with data warehousing solutions. Desirable

16.5The vendor should provide access to the data dictionary so that theBank has the option to use an external report writer like Crystal/Business Objects/ MS EXCEL.

Critical




17 Backup and Recovery

17.1 The system should have a day-end back-up process and allow theuser to configure more frequent back-ups, if required. Critical

17.2 The system should have auto-recovery features in case of systemfailures Critical

17.3 Back-up should be possible through external media (CD, tapes, DVD)for off-site storage Critical

17.4 The system should support data duplication and accessing Critical17.5 at same site (LAN environment) Critical17.6 at different site ( WAN environment) Critical18 Scalability

18.1 Without the necessity of re-writing code or undertaking other majorefforts, the system should be easily upgradable to facilitate: N/A

18.2 Increased Workload Critical18.3 Better Performance Critical18.4 Additional Users Critical18.5 Improved Network Capability Critical19 Web Access

19.1 The system should be internet and intranet enabled and shouldprovide remote access to authorized users. Critical

19.2The system should utilize latest available internet technologies andlanguages like .NET/.ASP, .XML/.RSS, JAVA/.PHP and becompatible with third party internet delivery mechanisms

Critical

19.3The system should receive and process transactions / queries fromthe internet, and be able to post transaction processing/ query resultson to the internet.

Critical

20 Security Management

20.1 The system should allow user accounts to be controlled by a specificadministrator Critical

20.2 The system should permit access only through password verificationand all user IDs should be unique Critical

20.3 The system should also have a provision of access through bio-metrics and access cards. Desirable

20.4 The system should allow upgrades and patches to be uploaded onlythrough the system upgrade path and not to the run-time system Critical

20.5 Addition of features should be allowed only through a properly revisedupgrade and data migration method Critical

20.6 The system should have the ability to provide or restrict accessprivileges based upon hierarchy and / or any additional criteria Critical

20.7 The systems should provide role based access for different types ofusers (e.g. Treasury, ALM Department, Top Management, etc.) Critical




20.8The system should allow for creation of unlimited user profiles andassign each user profile to a particular role with pre-defined accessrights

Critical

20.9 User ID and login should determine level of access to data e.g.read/view data, print data, write/modify data, delete data etc. Critical

20.1o The system should have the ability to synchronize the user ID andpassword with network user ID and password Critical

20.11 All databases should have database locking features in the situationthat there are multiple access and updates on the same record Critical

20.12 Standard password management features should include: N/A20.13 Minimum six length alphanumeric Critical20.14 Password history to prevent reuse of password for the particular user Critical20.15 Bank defined password expiry period Critical20.16 Password encryption Critical20.17 Automatic user disabling after three successive erroneous tries Critical20.18 Automatic user time-out on inactivity for a predefined time duration Critical20.19 Forgot Password functionality Critical

20.2oThe system should allow for creation, deletion and modification ofusers, upgrades of users and data access rights by authorizedadministrators.

Critical

20.21 There should be a maker-checker facility for key functions in thesystem. Critical

20.22 The system should support smart card authenticator for users toaccess the system by way of digital signatures and PIN. Desirable

21 Audit Trail

21.1 The system should have the ability to generate a detailed audit trail ona daily basis for the following minimum features: N/A

21.2 Attempted unauthorized logins Critical21.3 Time of login and logout Critical21.4 Change of passwords Critical21.5 Change of parameters Critical

21.6 The audit trail should be at a granular level, and track the user acrosseach activity Critical

21.7 All transactions should be time stamped with user ID along with detailsof modification, if any Critical

21.8 Details of databases accessed and modified by the users should bemaintained by the system Critical

21.9 The system should have the ability to store and track all systemevents, including corrections and cancellations by multiple criteria Critical

22 The system should allow manual amendments only after creating anaudit trail Critical




22.1 The system should maintain an error log in case of missing and/orerroneous data Critical

22.2 The system should maintain backups of Audit Log files Critical

5.3 Format SpecificationIt 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 ofResponse/Scale Description**

S Standardized, this scale indicates that this feature is a standard feature of thesolution.

A Alternative available

C Customization required. Vendor will provide the customization with thestipulated date of the phased rollout

U Unavailable. Functionality is not available and will not be provided by thebidder.

**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.



6. Terms & Conditions of Contract

6.1 Source Code

1) The source code of the proposed solution and other applications/ periodical updates shall bekept under escrow arrangement with approved/recognised Escrow Agency mutually acceptableto the Bank and the Bidder but at the bidder’s cost for entire duration of the project. The Bankreserves 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 anEscrow agent, the Bank will appoint an Escrow agent in its entire discretion which shall be finaland binding on the bidder.

3) The Bank and the bidder shall enter into a tripartite escrow agreement with the designatedescrow agent which will set out, inter alia, the events of the release of the source code and theobligations of the escrow agent

4) The Bidder shall provide complete legal documentation of all subsystems, licensed operatingsystems, licensed system software, and licensed utility software and other licensed software.The Bidder shall also provide licensed software for all software products whether developed byit or acquired from others as part of the project. The Bidder shall also indemnify the Bankagainst 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 thesoftware in the recent past.

6.2 Software Delivery & Installation

1) The bidder will provide the complete compiled code. The bidder will supply the automatedInstallation procedures. The bidder will install the application software on computers (serversand selected desktops) of the BANK. Bidder will also provide two sets of backup copies. Theinstallation of the base product will be considered complete only after demonstration offunctional features of the software as given in RFP and as per documented procedure and asacceptable to the Bank.

2) The solution must comply with all applicable requirements defined by any regulatory, statutoryor legal body which shall include but not be limited to RBI or other Regulatory Authority, judicialcourts 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 softwarewith successful conduct of acceptance testing by users. Software will be considered to be acceptedonly after the Bank issues an acceptance letter to the Bidder. New Software may be audited for riskanalysis and security features by Bank’s Internal Audit Team or a Third Party Auditor appointed bythe Bank, if so desired by the Bank. “Go-Live” date will be the date from which the software hasbeen accepted by the bank in its full form subject to the conditions specified above.



6.4 Inspection and Tests

1) Bank or its representative shall have the right to inspect and/or to test the software or theGoods to confirm their conformity to the requirements/specifications mentioned in this RFP atno extra cost to the Bank.

2) Should any inspected or tested software fail to conform to the specifications, the Bank mayreject it, and the Bidder shall either replace the rejected software or make alterations necessaryto meet specification requirements free of cost to the Bank.

3) Bank may choose to carry out a technical inspection/audit and performance evaluation ofproducts offered by the Bidders. The Bidder would permit Bank or any person/personsappointed by Bank to observe the technical and performance evaluation / benchmarks carriedout by the Bidder.

4) There will be an acceptance test by Bank or its nominated representatives after installation ofthe systems. In case of any discrepancy in the software supplied, Bank reserves the right tocancel the entire contract. The test will be arranged by the Bidder at the identified sites in thepresence of the officials of Bank and / or its representatives. The tests will involve trouble-freeoperation of the complete system during UAT apart from physical verification and testing. Thereshall not be any additional charges for carrying out this acceptance test. Bank will take over thesystem on successful completion of the above acceptance test. The installation cumacceptance test & check certificates jointly signed by Bidder's representative and Bank's officialor any consultant / auditor appointed by Bank should be submitted along with invoice etc. forscrutiny 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 documentsspecifically mentioned in this RFP.

6) All reports/statements for which UAT Sign-Off has been given by the Bank shall come toproduction 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’ arrivalin the destination shall in no way be limited or waived by reason of the Goods having previouslybeen inspected, tested and passed by the Bank or its representative prior to the Goods’shipment.

6.5 Information Ownership1) 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 implicitaccess rights to the information or rights to redistribute the information. The Bidder understandsthat civil, criminal, or administrative penalties may apply for failure to protect informationappropriately.

2) Any information considered sensitive by the Bank must be protected by the successful Bidderfrom unauthorized disclosure, modification or access. The Bank’s decision in this regard will befinal.

3) Types of sensitive information that will be found on Bank system’s which the Bidder plans tosupport or have access to include, but are not limited to: Information subject to special statutoryprotection, legal actions, disciplinary actions, complaints, IT security, pending cases, civil andcriminal investigations, etc. The successful bidder shall exercise adequate judgment to decide ifparticular 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 priorwritten consent, the details of any security safeguards designed, developed, or implemented bythe Bidder or existing at any of the Bank location. The Bidder will have to develop proceduresand 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 Bankdata and sensitive application software.



6.6 Adherence to Standards

The bidder should adhere to laws of land and rules, regulations and guidelines prescribed by variousregulatory, statutory and Government authorities in India. The Bank reserves the right to conduct anaudit/ongoing audit of the services provided by the bidder. The Bank reserves the right to ascertaininformation from the Banks and other institutions to which the bidders have rendered their servicesfor execution of similar projects.

6.7 Security Configuration, Monitoring and Audit

1) The baseline security configuration of the software/other applications provided by the biddershould be done by the bidder, according to the industry best practices and the Banks internalpolicy.

2) Compliance with security best practices may be monitored by periodic computer security auditsperformed by or on behalf of the Bank. The periodicity of these audits will be decided at thediscretion of the Bank. Periodicity for Regulatory Audits would be required as per the rules andguidelines laid down by the regulator or as required by the regulator. These audits plan toinclude, but are not limited to, a review of: access and authorization procedures, physicalsecurity controls, input/output controls, DB controls, backup and recovery procedures, networksecurity controls and program change controls.

3) To the extent that the Bank deems it necessary to carry out a program of inspection and auditto 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 Biddermust 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 performanceMeasurement systems (both manual and automated) audited without prior approval / notice tothe Bidder.

6.8 Considerations for Proposed Hardware & Software tosupport 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 successfulimplementation 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 andDR should be possible in both directions.

6) The bidder shall specify the suitable hardware and supporting software which shall deliver thebest throughput and performance considering the present volumes and the sizing proposedshould consider the probable increase in volumes for next 7 years. The necessary information



required by bidder to estimate sizing required hardware may be obtained from the bank (ifrequired).

6.9 Performance GuidelinesThe proposed solution should comply with the following guidelines on performance and solutioncomponents in minimum.

1) Bidder should clearly specify the detailed configuration and specifications of the applicationsand corresponding hardware required at various levels based on the technical requirements.The bidder should separately list down the reasons for the recommended hardwareconfigurations and specifications. The bidder has to explain through proper calculations howthe performance of the system vis-à-vis business statistics, projected growth, redundancy,projected growth in functional requirements, concurrent users, performance parametersexpected on peak load. The bidder should provide data on any other parameter which wouldbe required.

2) Bidder should also provide data on the solution as how the individual components under thesolution (application and associated hardware as advised to the Bank) would be able to meetthe current volumes as well as the future scalability requirements.

3) The bidder should provide information on industry standard benchmarks for the system suchas TPC certified by Transaction Processing Council.

4) The bidder has to furnish the details of the configuration of the servers, OS and databases tobe used in such benchmarking exercise for TPC etc.

5) The bidder should also provide the benchmarks with Risk Management application softwarepreferably conducted with real time loads for similar requirement or as acceptance test withcredential 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 proposedfor Bank’s requirement.

6.10 ConfidentialityThe vendor will be required to treat as confidential all data and information about the Bank, obtainedin the execution of his responsibilities, in strict confidence and shall not reveal such information toany other party without the prior written approval of the Bank/Purchaser. A non-disclosureagreement should be signed between Bank and vendor. The format of non-disclosure agreementform is given in Annexure-3.

6.11 Disaster Recovery SystemThe 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 theproposed solution facilitates disaster recovery. It will be the responsibility of the bidder to implementDisaster Recovery facility for the ALM solution. System must resume processing using the disasterrecovery secondary site within 4 hrs.

The bidder needs to submit the technical architecture relating to data replication betweenprimary and secondary site. The Recovery Time Objective (RTO) and Recovery PointObjective (RPO) for the proposed solution should be 4 hrs and 30 minute respectively.



6.12 Service Level Agreement (SLA)These Service Levels are only indicative and the Service Level Agreement (SLA) will befinalized in agreement with the selected vendor. The vendor shall be bound to provide theagreed service levels. Service Levels will include Availability measurements, Performanceparameters, call resolution time, etc. Bank requires the Bidder to provide reports for all availabilityand performance parameters and a log of all issues that have been raised and Closed/ PendingClosure by the Bidder. The frequency of these reports would be Weekly, Monthly, Quarterly andYearly as mutually agreed. Apart from reports on each availability and performance measurementparameter 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 performedby Bank or Bank appointed third party agencies.

The bidder is bound to provide on-site support to meet the requirements specified in SLA. In otherwords, if the services rendered by the system falls short of standards stipulated in SLA, the biddershall provide on-site assistance .

Availability Measurements Expected ServiceLevel

Base Amount onwhich penalty will

be calculatedPenalty*

Availability of software componentsand Test and Developmentinfrastructure

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 thepurpose of penalty calculation.

Type ofInfrastructure

PerformanceMeasurement #

ExpectedServiceLevel

Base Amount on whichPENALTY will be Calculated Penalty

SystemResponseTime

End to Endresponse time withinthe DC Time or DRto the Databaseshould be < 60seconds.

99.50%

The bidder is to upgrade theHardware along with relatedsoftware and services withoutany additional cost to the Bank,if service level is not met. UntilService level is met, penalty willbe charged on the value of thebusiness infrastructure at DC orDRC, as the case may be.

10%



Type ofInfrastructure

PerformanceMeasurement #

ExpectedServiceLevel

Base Amount on whichPENALTY will be Calculated Penalty

DisasterRecovery SiteAvailability

Business operationsto resume fromDisaster RecoverySite within 4hrs ofthe Data Centrefailing and viceversa

100.00%

Penalty will be charged on thevalue of the businessinfrastructure at DC or DRC, asthe case may be.

10%

Data PointAvailability

Recovery PointObjective (RPO) of30 minutes.

100.00%

Penalty will be charged on thevalue of the businessinfrastructure at DC or DRC, asthe case may be.

10%

* The amount indicated in this column represents the maximum penalty, which would be charged incase 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 beprovided by Bidder.

6.13 Software Licenses for SolutionBidders are required to propose Enterprise Wide Application License on perpetual basis. The biddershall furnish the price details of licenses in the format given in Annexure 12 A.

6.14 Hardware RequirementThe Bidder is required to advise the Bank detailed requirement/sizing of adequate hardware basedon the relevant parameters for the ALM Solution. Bank will provide the required hardware includingOS & RDBMS for implementation of ALM solution.

System should be sized adequately to ensure maintenance of historical data and in pursuant withpurging policy. The data will be retained for a period of 7 years, beginning from the previous 6 yearsand ending with the current year. All the data previous to the 7 years will be archived and will beretained offline.

The vertical scalability available within the server should be at least 20% to accommodate additionalCPUs, 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 exceed70% threshold for more than 30 minutes.

The hardware sized should be scalable and fault tolerant. All the components within the servershould 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 thepower supplies will be from separate UPS. In case of failure of one power supply, the second powersupply 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 onprojected and actual utilization. Accordingly, bidder needs to advise the Bank the hardware



requirement over the tenure of the contract period. The initial hardware advised should be capable ofhandling at least the first three years load, volume and sizing. the Bidder has to advise appropriatehardware and other resources to be incrementally added based on the increase in the load andvolumes to support the growth for the remaining contract period. The Bidder has to ensure that theconfiguration proposed is capable enough of handling the respective year’s load and volume.

6.15 EnvironmentsBank 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 productiondatabase server as per the first year sizing with minimum 25% available space for vertical scalabilitywithin the test and development server.

6.16 Phased ImplementationThe 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 thebusiness 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 theirimplementation team for the phased implementation.

6.17 Project Documentation and ManualsSoft 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 bemade available for all users for all applications.

Bank will require the Bidder to follow worldwide practice and international standard for thedocumentation for the entire System Development Life cycle and provide the same. All suchdocumentation and manuals will be kept up to date with proper version control during the entirecontract period. Bank may require the bidder to deliver the following documents (in addition tostandard documentation from OEM) both in hard and soft copy to Bank during development andimplementation of ALM solution

1) Installation Document2) System Requirement Specification Document3) Architecture Document4) Risks and Mitigation Document5) Gap analysis Document6) Data requirement Document7) High Level Design Document8) Proof of Concept for the ALM9) Low Level Design Document10) Test Plans11) Comprehensive Test Cases Document (Unit, Integration and SIT Test Cases)



12) Security Management Guide13) User Management Guide14) Configuration Document15) Operational Manual

6.18 Interface & Integration Requirements1) 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 aroundindustry best practices and uses an enterprise ETL tool.

5) The Bidder will be responsible for identifying the detailed interface requirements forintegrating the proposed packages to the existing systems of the Bank and for all otherfunctionalities as mentioned in this RFP.

6) The interface architecture should be clearly defined. The integration architecture shouldinclude the types of interfaces supported; the standards used and should comply with Bankarchitecture 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 Biddershould ensure the requirements of data format, frequency of data transfer, quality checksand validations before data transfer and priorities for data transfer are identified andaddressed.

10) The Bidder must ensure that all applicable interfaces are automated with no manualintervention.

11) The Bidder will ensure and incorporate all necessary security and control features withinthe 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.



6.19 Warranty & Annual Maintenance1) 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 materialsunless provided otherwise in the Contract. The Supplier further warrants that all Goodssupplied under this Contract shall have no defect arising from design, materials orworkmanship (except when the design and / or material is required by the Bank’sSpecifications) or from any act or omission of the Supplier, that may develop under normaluse 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 monthsfrom the date of ‘GO LIVE”. The Bank shall promptly notify the Supplier in writing of anyclaims arising under this warranty. The AMC shall be for a period of 2 years beginning fromthe date of completion of the Warranty Period.

3) Upon receipt of such notice, the Supplier shall with all reasonable speed, rectify the issueswithout 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 benecessary, at the Supplier’s risk and expense and without prejudice to any other rightswhich 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 Bankreserves the right to terminate the AMC contract and appoint any other agency at the riskand 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 arequest 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 withrequired awareness of its consequences and any such modification/ updating will berecorded for information of the selected bidder without any impact on the media as perOEM descriptions.

7) The bidder shall provide centralized complaint booking facility to the Bank and the dashboard, if available, shall be provided to the Bank. The method of booking complaints shallbe through E-mail, Toll-free no, on line portal, web, etc.

8) The products & services offered must include comprehensive on-site warranty from thedate 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 GOLIVE.

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 defectivecomponents that are brought to the Bidder’s notice at the installation site and at no chargeto the Bank,

11) In the event of system breakdown or failures at any stage, protection available shall bespecified which would include the following:

- Diagnostic for identification- Protection of data entered- Recovery / restart facilities- Backup facilities



12) The selected bidder must agree that during the warranty / AMC period, the software will bekept 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 thefollowing 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 rightsand privileges.

- Migration of data from source system, at the start of the project. Assisting user tocarry 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 technologicalchanges, consolidating all bug fixes, all enhancement requests made by the Bank.

15) No customization and subsequent implementation charges will be payable by the Bank forenhancements, modifications and upgrades.

16) The Bidder agrees that any future upgrades, modifications or enhancements shall notaffect the current working of the licensed software and all current functionality shall bemigrated to the new/enhanced version.



17) The Bidder shall implement the new/enhanced version and that the Bank will bear no costfor migrating the existing functionality to the new/enhanced version.

18) For implementing different versions of Application Software, if adjustments / change in theconfiguration are to be made in base memory the same should be carried out by theVendor 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 registeredsoftware licenses existing as of the Start Date, and the warranties and licenses forsoftware:

- 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 appropriatemanufacturer, 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 maintenanceterms 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 inperforming asset management and financial management functions of the Bank as theserelate 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 forpreparation and implementation of budgets and cost benefit analysis.

6.20 Training

The successful Bidder shall be responsible for providing Training to various target groups consistingof 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.)



Techniques of generating various MIS / EIS reports from solutionprovided

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 trainingprograms/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 bysuccessful Bidder to The Bank.

5) Self e-learning training kit of the entire solution to be provided by the successful Bidder tothe Bank.

The Bidder has to ensure that there is online help available for each functional area within the ALMSolution 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 beresponsible for the following:

1) The Bidder shall render both on-site and off-site maintenance and support services to theBank. The Bidder shall provide troubleshooting / customer support mechanism. TheSoftware Maintenance and Support Services shall be provided by the Bidder from theBank’s premises.

2) Bidder shall assign personnel of appropriate qualifications and experience to perform theservices in order to fulfil its obligations.

3) Bidder shall designate one of its personnel as the Project Manager, to interact with theDesignated Customer Support Contact from the Bank for the purposes of gettingapprovals, progress report, discussing and resolving issues, arranging meetings, etc.

4) Bidder shall exercise requisite control and supervision over its personnel in the course ofrendering the services and make best efforts to ensure that the services are rendered in acontinuous and uninterrupted manner.

5) Though Bidder has the right to withdraw its personnel, Bidder will replace the persons withother 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/underperformance on the part of such person, then

Bidder will use all reasonable endeavours to replace such individual(s) promptly by othersufficiently 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 minimizechanges in personnel.

7) Bidder will respect the confidentiality of all information given to it by the Bank and will notdivulge 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/oruser training in respect of any corrected licensed software provided, if required by theBank.



9) The Bidder shall promptly install/implement the corrected licensed software and/ormaintenance releases provided at the Designated Location(s) of the Bank at no additionalcost 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 providea leading and current anti-virus for the requisite systems to be placed in the DC/DR. TheBidder shall adopt a common, smooth, timely and effective and satisfactorybug/enhancement handling mechanism. The Bidder agrees that the errors resulting fromthe licensed software shall not be attributed to alleged misuse, improper use, alteration ordamage by users. The Bidder shall compensate the Bank such financial loss suffered bythe 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 andto meet the services level agreements as will be entered into by the Bidder with the Bank.

6.22 Termination for DefaultThe Bank, without prejudice to any other remedy for breach of contract, by 30 days written notice ofdefault sent to the Supplier, may terminate this Contract in whole or in part under any of the belowconditions:-

1) If the Supplier fails to deliver any or all of the Goods within the period(s) specified in theContract, 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 influencethe 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 procurementprocess or the execution of a contract to the detriment of the Bank, and includes collusive practiceamong 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 suchterms 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 damagesthrough encashment of Bid Security/ Security Deposit /Performance Guarantee given by the Bidderand 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 thefollowing Conditions:

Failure of the successful Bidder to accept the terms of the contract, furnish the PerformanceGuarantee and sign the contract within the time frame specified by the Bank



Delay in completing installation / implementation and acceptance tests/ checks and/or anyother obligations, beyond the specified periods;

Serious discrepancy in functionalities to be provided or the performance levels agreedupon, 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 toprovide 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 thedamages through encashment of Bid Security/ Security Deposit /Performance Guaranteegiven 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 orThe Bank as the case may be which they could not foresee or with a reasonable amount of diligencecould 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 andepidemics

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 TheBank shall not be liable for delay in performing his/her obligations resulting from any force majeurecause as referred to and/or defined above. Any delay beyond 30 days shall lead to termination ofcontract by parties and all obligations expressed quantitatively shall be calculated as on date oftermination. Notwithstanding this, provisions relating to indemnity, confidentiality survive terminationof the contract.

6.25 Performance Security

1) Within 21 days of issue of Purchase Order, the supplier shall furnish to the Bank anunconditional and irrevocable Performance Guarantee equivalent to 10% of the total ContractAmount in the form of a Bank Guarantee, valid for seven years from the date of purchase orderin the format enclosed. In case of delay in submission of the Bank Guarantee, Bank maycharge 0.5% penalty of the contract amount per week or part thereof subject to a maximum of10% value of the contract.

2) The project will be deemed complete only when all the solutions and items contracted for byBank are delivered in good condition, installed, commissioned, implemented, tested andaccepted along with the associated certification, documentation and training provided to Bank’semployees in compliance with the terms of this RFP and as per the requirements of the contractexecuted between Bank and the Bidder and the acceptance criteria defined in this document ismet.

3) The Performance Security shall be invoked by the Bank as compensation for any loss resultingfrom 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 afterexpiry of the claim period.



6.26 Liquidated DamagesIn case of delayed supply or implementation, the supplier shall be liable to pay as Liquidateddamages at the rate specified below, for each completed week of delay or part thereof, on thepurchase 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 orbecoming due to the bidder under this purchase contract or may be recovered by encashment ofbank 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 thesupplier in connection with or arising out of the contract, the parties shall make every effort toresolve 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 mutualconsultation, then either the purchaser or the supplier may give notice to the other party of itsintention to commence arbitration, as hereinafter provided, as to the matter in dispute, and noarbitration 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 hasbeen given in accordance with this clause shall be finally settled by arbitration. Arbitration maybe 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 anymatter arising out of or connected with this agreement, such dispute or difference shall besettled in accordance with the Arbitration and Conciliation Act, 1996. The arbitral tribunalshall 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 andshall act as Presiding Arbitrator. In case of failure of the two arbitrators appointed by theparties to reach upon a consensus, the Presiding Arbitrator shall be appointed by thecompetent court of law under Arbitration Act, which shall be final and binding on theparties.

b) If one of the parties fails to appoint its arbitrator within 30 days after receipt of the notice ofthe appointment of its Arbitrator by the other party, then the competent court of law underArbitration Act, both in cases of the Foreign Supplier as well as Indian Supplier, shallappoint the Arbitrator. A certified copy of the order of the competent court of law underArbitration 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 arbitrationproceedings and that of all documents and communications between the parties shall beEnglish.

d) The decision of the majority of arbitrators shall be final and binding upon both parties. Thecost and expenses of Arbitration proceedings will be paid as determined by the ArbitralTribunal. However, the expenses incurred by each party in connection with thepreparation, presentation etc. of its proceedings as also the fees and expenses paid to thearbitrator appointed by such party or on its behalf shall be borne by each party itself.



6.28 Time ScheduleThe 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* fromthe 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 forpayment. 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 applicable3) 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 proposalsubmitted 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 ofCustomised 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 BidFormat (Annexure 13) plus applicable taxes

o 10% on sign off on Business Requirement Documento 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;



AMC and Facility Management Services

o Payment of AMC/FMS Charges as specified in Table C & D of the Commercial BidFormat (Annexure 13) plus applicable taxes payable quarterly in arrears

6.30 Paying AuthorityThe payments as per the Payment Schedule covered hereinabove shall be paid through Departmentof Information Technology of the Bank. However, Payment of the Bills would be made on receipt ofadvice/confirmation for satisfactory delivery/installation/re-installation, live running and service reportfrom the concerned offices/department where the purchased items have been delivered andimplemented.

6.31 System AdministrationBidder to Provide for system administration services. Examples of these services are: Clientaccount 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 andapplication access management like creating user accounts at application level, assigningapplication access, setting application passwords, user lockout, etc.;

Performance optimization and reporting - Process and Memory Management, monitoring CPUperformance, monitoring Memory performance, monitoring Input/output performance, monitoringEthernet traffic, etc.;

Error detection and correction; Troubleshooting and client support

6.32 Database AccessVendor shall provide the Bank, understanding and full access to Database, Database TableStructures and Data Dictionary of the proposed solution.

6.33 Software MaintenanceThe Bidder should provide, through a set of standard software packages, software and softwarerelated services to hardware infrastructure.

Types of service include requirement analysis, assisting the Bank in software product acquisition fortesting, 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 themedia on which it is to be delivered with a current version of a leading anti-virus application in effortsto 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 Biddershall also ensure that the software does not and shall not contain any computer code or any otherprocedures, 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) orderlyoperation 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”, “timelocks”, or “drop dead” devices); (ii) cause the software to damage or corrupt any of the Banks’ or its



clients’ data, storage media, programs, equipment or communications, or otherwise interfere with theBanks operations, or (iii) permit the Bidder and/or its personnel and/or its licensors and/or any otherthird party, to access the software (or any other software or Banks computer systems) to cause suchdisruption, disablement, harm, impairment, damage or corruption (sometimes referred to as “traps”,“access codes” or “trap door” devices).

6.34 Software Maintenance and Support Services duringWarranty and AMC

The Software Maintenance and Support Services contemplated herein shall be provided for allLicensed 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 Webbased methodology.

The Maintenance and Support Services will cover:

1) All product upgrades, modifications, enhancements that have to be provided to the Bank freeof charge.

2) Enhancements would include changes in the software due to Statutory and Regulatorychanges and changes required due to changes in industry and other Banking practices inIndia. It will also include all the functionalities mentioned in Functional Requirement. Changesto be made applicable with in stipulated time period mutually agreed between Bank & bidder.

3) Modifications would include minor changes, bug fixes, error resolutions and minorenhancements that are incidental to proper and complete working of the application.

4) Upgrades would include product releases made by the Bidder to incorporate technologicalchanges, consolidating all bug fixes, consolidating all enhancement requests made by theBank.

5) No customization and subsequent implementation charges will be payable by the Bank forenhancements, modifications and upgrades.

6) The Bidder agrees that any future upgrades, modifications or enhancements shall not affectthe current working of the licensed software and all current functionality shall be migrated tothe new / enhanced version.

7) The Bidder shall implement the new/enhanced version and that the Bank will bear no cost formigrating the existing functionality to the new / enhanced version.

8) The Bidder shall have the responsibility to ensure that the designate OEM undertakes toperform all obligations with respect to the project and all other software contemplated in theSolution, 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) expiryof the agreement and (iv) termination of agreement, with respect to the project for any reasonwhatsoever. The Bidder acknowledges that the rights mentioned herein are without prejudiceto the rights and the remedies (under law or equity) that the Bank may have against theBidder.

9) The Bidder shall apply regular patches to all the softwares supplied by them for which theBank will bear no additional costs. The Bidder agrees that the functioning of the ALM solutionof the Bank will not be affected adversely as a result of any new releases, enhancements,patches, etc.



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 implementedunder this tender and subsequent agreement as well.

12) User support in case of technical difficulties in use of the software, answering proceduralquestions, providing recovery and backup information, and any other requirement that may beincidental/ancillary to the above.

13) Prompt receipt, analysis and reporting of reported deficiencies in the operation of the softwareand supply of information and advice on such deficiencies;

14) Installing/commissioning the software at the designated locations/changed designatedlocation at no additional cost or fees or expenses to the Bank. Installing/commissioning theupgrades / new versions/ new releases of software at the designated locations/changeddesignated location at no additional cost or fees or expenses to the Bank. The requirementsthat are finalized with the Bank post the gap assessment phase and included in the businessrequirements document, will need to be provided by the Bank at no additional cost to theBank.

15) Providing remedial support in case the software media is virus-inflicted at no additional cost orfees 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 bereported in accordance with the procedure prescribed in respect thereof and shall be accompaniedby sufficient information including the input data that generated the program error so as to enablethe Bidder to reproduce and verify the reported program error. On receipt of request together with allsuch information and data the Bidder shall use all-out efforts, consistent with the severity of theprogram error, to remedy such program error which is within the purview of the system logic, that ithas been able to reproduce and verify. Such remedies may include providing instructions to theBank to cure the program error or delivering updates at no additional cost. The Bidder warrants thatany 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 innot a Program Error, it shall advise the Bank whether it can correct or assist in resolving sucherror/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 versionsand notify the Bank about the same. The Bidder/OEM agrees that all such Updates/Upgrades/Newreleases/New versions, as and when released during the term of warranty or ATS/AMC shall beprovided to the Bank at no additional cost or fees or expenses including implementation cost duringthe contract period.

Enhancements



1) All requests for Enhancements that may be required for any reason by the Bank shall bemade 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 Maintenanceand Support Services contemplated herein shall be at no additional cost or fees or expensesto the Bank.

3) The Bidder shall rectify any corruption in the application software or media at no extra costto the Bank.

4) The Bidder shall ensure ‘nil’ downtime of licensed software, prompt execution ofcustomization and enhancement requirements, version control mechanism and also todevelop smooth upgrades and version changes, ongoing training, user group meetings andfeedback 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 solvingand troubleshooting including troubleshooting and operational errors/bug fixation,rectification of bugs, enabling features of the licensed software provided, providing additionaluser controlled reports, enabling parameterized features, future product information,migration path details and consultancy. The Bidder agrees that the support will be renderedin person in the normal course and in emergencies, support will be extended throughtelephone, fax, and email and that such instances should be an exception.

6.35 Software support1) 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 apart of this tender) and or questions, defect and non-defect related to Bank office automationproducts, systems and licensed applications.

2) The Bidder shall provide licensed software support including but not limited to problemtracking, problem source identification, problem impact (severity) determination, bypass andrecovery support, problem resolution, management reporting and trend analysis andinterfacing 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 tolog a service request) for Software support and respond to the initial request from the Bankwithin agreed service levels.

4) Bidder shall log any reported incident, identify it as defect or non-defect related, and tracks ittill resolution. For all incidents, the Bidder will ask the Bank to assign a severity rank andhandle 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 detailingthe disposition of each reported problem, and other contents as desired by theBank

- The Bidder shall provide reasonable effort using available resources to assist theEnd Users at the Bank with Non-Standard Software support for problemdetermination and resolution

6) In the event of any dispute and or the commencement of arbitration proceedings the Vendorshall continue all facilities management services.

6.36 Application ManagementThe Bidder should be able to provide Application Management services to manage softwareapplications of the Bank.



The Bidder should be able to synchronize Application Management with IT infrastructuremanagement. Deliverables for Application support should include:

1) Performance Monitoring & Management of application.2) Installation & configuration of application3) Application Patch management and version control.4) Capacity Management.5) Deployment of objects in Application server.6) Up gradation & migration7) Trouble shooting Application server product related issues8) 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-installation14) SIP & performance management.15) Logging a call with product Vendor16) Version migration, testing and implementation17) File Level Backup for Application Server18) Backup & restoration management of application server.19) Portal/content management.20) User management21) Support to known errors and problems22) Monitor web / Application server availability23) Monitor alert notifications, checking for impending problems, triggering appropriate actions24) DR implementation25) DR Drill conduction on quarterly basis

Bidder is expected to provide relevant reports for the previous month in the 1st week of every monthand same needs to be jointly reviewed by Bidder and Bank in next 3 working days. The reportsshould be benchmarked against the Service Levels defined in Service Level Agreement, and penaltyshould be calculated based on the level of deviation from Service levels defined. Bidder is requiredto submit the list of reports to track performance on service levels for all managed services underscope of this tender.

6.37 Patch ManagementPatch 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 installation6) 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 ManagementThe Bank may, at any time, by a written order given to the successful bidder, make changes withinthe general scope of the Contract in Technical and functional specificationsNo Change Request (CR) will be considered for any changes/amendments, in anyreports/statements, requested by the Bank within 6 months from date of Go-Live. It shall beobligatory on the part of the vendor to comply with revised requirements of the Bank and arrange todeliver them within reasonable time, at no additional cost.



7. Annexures

Annexure-1Check List for Submission of Annexure

Check ListSl. No. Description Annexure No.

1 Authorization Letter Format 22 Non-Disclosure Agreement Form 33 Check List for Submission of Eligibility Criteria 44 Profile of Bidder/Partner 55 Implementation Methodology 66 Reference Site Details 77 Past Experience 88 Team Profile 99 Training 10

10 Cover Letter for Commercial Bid 1111 The Format for Furnishing the Details of Software 12 A

12 The Format for Furnishing the Details of Hardware (To bePurchased by the Bank) 12 B

13 Table for Arriving at the Total Ownership Cost 1314 Bid Submission Covering Letter 1415 Notification of Acceptance 1516 Specimen Contract Form 1617 Performance Bank Guarantee Format 1718 Pre Bid Query Form 1819 Self-Declaration Black Listing 1920 Bid Security Form 2021 Undertaking – Document Correctness 2122 Online Reverse Auction Compliance Statement 22

23 Functional and Technical requirements Section 5.1 &5.2

24 Undertaking – Legal 23



Annexure-2Authorization Letter Format (On Organization’s Letter Head)

Place:Date:

ToThe Asstt. General Manager (IT),Department of Information TechnologyAllahabad 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 IndustryBest Practices and Guidelines of RBI/BCBS on ALM. Mr. / Ms.________________________________________ is hereby authorized to attend the Pre-BidMeeting & to discuss with you on the subject RFP _____________ on _____________ on behalf ofour organization.

The specimen signature is attested below:______________________________ Specimen Signature of Mr. /Ms.

--------------------------------------- --------------------------------------Signature of Authorizing Authority Name & designation of Authorizing

Authority

----------------------------------------Name and designation of AttestingAuthority

AttestedPhotograph of the

AuthorizedRepresentative



Annexure-3NON DISCLOSURE AGREEMENT

THIS AGREEMENT made and entered into at ……..on this the…..day of………20... BetweenALLAHABAD 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 contextso require includes its successors and assigns

AND

M/s.……………………………. Limited a company registered under the Companies Act having itsregistered office at…………………………………….. Hereinafter called the “Vendor” which term shallwherever 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 procuringhardware/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 businessrelationship between them. In the course of discussions and negotiations, it is anticipated that theparties may disclose or deliver to the other certain or some of its trade secrets or confidential orproprietor information for the purpose of business relationship.

NOW THERFORE THIS AGREEMENT WITNESSETH and it is hereby agreed by and betweenthe parties hereto as follows:

1. Confidential information

"Confidential Information" means and includes all data, documents and information disclosed or tobe disclosed by either Party to other Party and its Representatives (as defined herein) (includinginformation transmitted in written, electronic, magnetic or other form and also information transmittedorally or visually) and any and all information, in whole or in part, directly or indirectly, from suchinformation including all notes, summaries, analyses, compilations and other writings. Confidentialinformation shall include any copy, abstract, extract, sample, note or module thereof and electronicmaterial 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 thespecific purpose. Any other use of such confidential information by any party shall be made onlyupon the prior written consent from the authorized representative of the other party or pursuant tosubsequent agreement between the Parties hereto.

The receiving party shall not commercially use or disclose for commercial purpose any confidentialinformation or any materials derived therefrom, to any other person or entity other than persons inthe direct employment of the Receiving Party who have a need to access to and knowledge of the



confidential information solely for the purpose authorized above. The Receiving Party may discloseconfidential information to consultants only if the consultant has executed non-disclosure agreementwith the Receiving Party that contains terms and conditions that are no less restrictive than theseand such consultant should also be liable to the original disclosing party for any unauthorized use ordisclosure. The Receiving party shall take appropriate measures by instruction and writtenagreement 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 ordisclosure of the Disclosing party’s confidential information in violation of the terms of thisAgreement.

Neither party shall make news release, public announcements, give interviews, issue or publishadvertisements or Agreement, the contents/provisions thereof, other information relating to thisagreement, the purpose, the Confidential information or other matter of this agreement, without theprior written approval of the other party.

3. Exemptions

The obligations imposed upon either party herein shall not apply to information, technical data orknow how whether or not designated as confidential, that:

Is already known to the Receiving party at the time of the disclosure without an obligation ofconfidentiality.

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 havegiven notice to the Disclosing Party an made a reasonable effort to obtain a protective orderrequiring that the confidential information and / or documents so disclosed used only for thepurposes for which the order was issued.

4. Term

This agreement shall be effective from the date of the execution of this agreement and shall continuetill expiration or termination of this agreement due to cessation of the business relationship betweenthe parties. Upon expiration or termination as contemplated herein the Receiving party shallimmediately cease any or all disclosures or uses of confidential information and at the request of thedisclosing party, the receiving party shall promptly return or destroy all written, graphic or othertangible forms of the confidential information and all copies, abstracts, extracts, samples, note ormodules thereof.

The obligations of the receiving party respecting disclosure and confidentiality shall continue to bebinding 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 Bankshall retain title and all intellectual property and proprietary rights in the confidential information. Nolicense under any trademark, patent or copyright or application for same which are or thereafter maybe obtained by the Vendor is either granted or implied by the conveying of confidential information.



6. Return of Confidential Information

Upon written demand of the disclosing party, the receiving party shall (I) cease using the confidentialinformation (ii) return the confidential information and all copies, abstracts, extracts, samples, note ormodules thereof to the disclosing party within seven (7) days after receipt of notice and (iii) uponrequest of the disclosing party, certify in writing that the receiving party has complied with theobligations set forth in this paragraph.

The Vendor shall not make news releases, public announcements, give interviews, issue or publishadvertisements or publicize in any other manner whatsoever in connection with this Agreement, thecontents / provisions thereof, other information relating to this Agreement or information receivedunder 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 anysoftware disclosed hereunder.

7. Remedies

The receiving party acknowledges that if the receiving party fails to comply with any of its obligationshereunder, the disclosing party may suffer immediate, irreparable harm for which monetary damagesmay not be adequate. The receiving party agrees that, in addition to all other remedies provided atlaw 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 matterdiscussed herein and supersedes any and all prior oral discussion and/or written correspondence oragreements between the parties. This agreement may be amended or modified only with the mutualwritten consent of the parties. Neither this agreement nor any rights, benefits and obligations grantedhereunder, shall be assignable or otherwise transferable.

9. Severability

If any provision herein becomes invalid, illegal or unenforceable under any law, the validity, legalityand enforceability of the remaining provisions and this agreement shall not be affected or impaired.

10. IndemnityThe Vendor will indemnify the Bank against all actions, proceedings, claims, suits, damages andany other expenses for causes attributable to Vendor in connection with purchase ofHardware/software/goods under this contract. The total liability of the Vendor under thecontract 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 agreementor any matter connected with, arising out of, or incidental to the arrangement incorporated in thisagreement, the matter shall be referred to arbitration and the award passed in such arbitration shallbe binding on the parties. The arbitral proceeding shall be governed by the provisions of Arbitrationand 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.



13. Governing Laws

The provisions of this agreement shall be governed by the laws of India.

14. Authority to Execute the ContractEach person executing this Agreement warrants and represents that he or she has the authority toenter 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. …………..



Annexure-4

Check List for Submission of Eligibility Criteria

Sr. No. Eligibility CriteriaCompliance

(Yes/ No) Documentary Evidence to beSubmitted to the BANK

General Eligibility

1

The bidder should be in existence for 5years as on 31st March 2014. (In case ofmergers/acquisitions/restructuring or namechange, the date of establishment ofearlier/Original firm would be taken intoconsideration.)

Certificate of incorporation.

2

The bidder and the OEM should be a Profitmaking entity for last three financial yearsi.e.2011-12, 2012-13, and 2013-14. (If2013-14 results are not finalized yet, then2010-11, 2011-12, 2012-13 will beconsidered).

Copies of Annual Reports incase of listed companies andCopies of audited balance sheetsand P&L statements in case ofothers for past 3 financial years.

3

The Bidder must have a presence in Indiafor at least 3 years and should haveaverage revenues in excess of INR 50.00Cr. (INR Fifty Crores) for the past 3 financialyears i.e. 2011-12, 2012-13, and 2013-14.(If 2013-14 results are not finalized yet, then2010-11, 2011-12, 2012-13 will beconsidered).

Copies of Annual Reports incase of listed companies andCopies of audited balance sheetsand P&L statements in case ofothers for past 3 financial years.

4

The bidder should own the intellectualproperty rights of the product/solution or heshould have rights from the owner, if not,the Bidder should have in place proper tie-ups, commercial agreements, authorisedimplementation partnerships etc. fordevelopment /resale/ customisation ofsoftware with the product bidder or any thirdparty, whose software products are offered.

Credential letter on bank’s letterhead

5

The Bidder and OEM should not have beenblacklisted at the time of submission by theCentral/any of the State Governments/statutory body/ regulatory body/IndianBanks Association in India


6The ALM Solution should have beenprocured by at least 2 ScheduledCommercial Banks amongst which at least




Sr. No. Eligibility CriteriaCompliance

(Yes/ No) Documentary Evidence to beSubmitted to the BANK

1 should be a Public Sector Bank.

7The ALM Solution should have beensatisfactorily implemented by a Bankoperating in India as on 30.06.2014.


8The Bidder should have experience ofimplementing ALM solution in a Bank inIndia.

The bidder needs to submit thecredentials of team who will dothe implementation.



Annexure - 5Profile of Bidder

Sl. No. Particulars Response

1 Company Name

2 Date of Incorporation

3 Name of Indian representative/office (indicate: own, dealer,distributor, JV)

4

Company Head Office address* Contact person(s)* Designation* Phone Number* Mobile Number* Fax Number* E-mail Address

5

Address of Indian representative/office* Contact person(s)* Phone Number* Fax Number* E-mail Address

6

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

7

Ownership structure (e.g. Inc., partnership)* Who are the primary shareholders?*State the major shareholders with percentage holding in case oflimited companies.

8 Location: Support (e.g. Asia Pacific, India) Since when has thesupport centre existed in India?

9

Provide the range of services offered covering service descriptionand different schemes available for:

Customization Implementation Support Ongoing support (AMC, Help Desk) Training Any Others (Please Specify)

10

State pending or past litigation if any within the last 3 years withdetails and explain reasons.Please also mention any claims/complaints received in the lastthree years.

11 Enclose abstracts of the Balance sheet and P/L Account for the lastthree years



12 Independent analyst research report (if any)

13 Major changes in Management for last 3 years



Annexure - 6Implementation Methodology

Sl. No. Details of Methodology / Approach Response

1 The methodology section should adequately address the followingstages of the project:

1.1 Frequency and approach for periodic reporting on the progress of the projectand 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 withproposed solutions

2 Timelines

3 Project Management Activities

4 Roles and responsibilities of proposed personnel both from the vendorand bank end.

5 Following details with respect to the methodology followed by thevendor 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 relevantdetails)

5.1o Name of senior project staff

5.11 Nature of the Project

5.12 Project Management Methodology used

5.13 Role of the Bidder, whether complete end to end involvement or for aparticular module

5.14Project detail ((Broad detail – information about all activities handled,modules forming part of the ALM Solution of the Client Bank, associatedactivities, time lines activity wise and module wise may be detailed.)

**The bidders are expected to provide crisp descriptive response against each point above



Annexure - 7Reference Site Details

The Reference Site details are to be provided in the following format:

Particulars ResponseName of the Bank/ Financial InstitutionAddress of the OrganizationAnnual Turnover of the Organization for the Financial Year 2013-14Date of Commencement of ProjectDate of Completion of ProjectScope of Work for SolutionPartner for the ProjectProject Start Date and End Date

List all the modules/components of the system being used. Type ofArchitecture in which the system has been implemented.

Implementation details e.g. Number of Sites, time taken forOperationalization, volumes of processing etc.State the duration of the implementationNumber of users and the geographical spread of the implementationAverage Team size on site for project implementation (SI & OEM Team)Contact Details from the Bank/Financial Institution for referenceName of the Contact PersonDesignationPhone Number/e-mail

The bidder has to submit a consent letter for conducting a reference site visit by AllahabadBank’s project evaluation team. The letter has to be on the letter head of the concernedBank/Financial Institution.



Annexure - 8Past Experience

List of major customers where the proposed ALM solution has been implemented/underimplementation in India/outside and their reference details:

Sl.No.

Name andcomplete

PostalAddress

of theCustomer

Name & Briefscope of

work done byOEM (specify

the size ofthe Bank, theapproachessupported

etc.)

Name & Briefscope of

work done bySI (specifythe size of

the Bank, theapproachessupported

etc.)

AttachReference

Letter

ContactDetails(Name,

Designation,Phone,Email)

Project Status(Completed/UnderImplementation,Start Date, End

Date)

*In cases where SI acts as bidder, while counting the number of Banks for the purpose of assigningmarks under this parameter only the number of Banks where SI has customized the software of theOEM shall be taken.

(Enclose necessary documentary proof such as reference letter)



Annexure - 9Project Team Profiles

The general information on staff strength of the bidder/partner should befurnished in the following format & Specific information to be furnished inrespect of each team member1 Name

a Brief Introduction (in bullets)

2 Date of Birth

3 Phone Number

4 Position in the firm

5 Total years of post-qualification workexperience

6Employment Record(Provide Company name, position held,duration, clients worked)

a

b

c

d

e

f

g

7 Number of years with the firm

8

Details of relevant assignmentsundertaken (include both past andcurrent employment projects andhighlight BFSI experience, if any)(Provide scope, duration, client nameand status of assignment)

a

Duration of engagement in the assignment(In months)

Location

Client Name

Main project title and features

Position held

Activities performed



b

Duration of engagement in the assignment(In months)

Location

Client Name

Main project title and features

Position held

Activities performed

9 Education

DegreeObtained

Year ofDegree

obtainedInstitution

10 Certifications (if any)

a

b

c



Annexure - 10Training

A. General Information

Particulars ResponseNo: of Implementation trainings undertaken by the Bidder/partner

A brief description on the Training approach taken by the Bidder/partner

Names and experience of all trainers with the Bidder who would beinvolved with the Project

B. Specific information to be furnished in respect of each training session*

Particulars ResponseName of the Bank where product was implemented and the trainingconductedDate and place where training conductedTraining audienceDuration of trainingLocation

*This information should be backed by the documentary proof in the customer-Bank’sletter head.



Annexure - 11Cover Letter for Commercial Bid (Post Reverse Auction)

Note: This Cover Letter for Commercial Bid (Post Reverse Auction) from the Bidder should be on theletterhead of the Bidder and should be signed by an authorized person.

Date: ___________________To

The Asstt. General Manager (IT)Allahabad Bank,Head Office,Department of Information Technology

2, Netaji Subhash Road,Kolkata – 700 001, (W.B.)IndiaSub: 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), thereceipt of which is hereby duly acknowledged, we, the undersigned, offer to supply, install andmaintain inconformity with the said Bidding documents for the sum of ...................………….. (Totalamount in words and figures) or such other sums as may be ascertained in accordance with thecommercial bid for hardware and software and total cost of ownership attached herewith and madepart of this Proposal.

We undertake, if our bid is accepted, to deliver the goods in accordance with the delivery schedulespecified 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 totalContact 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 andmay be accepted at any time before the expiration of that period. We agree to extend the BidValidity 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 abovecontract, 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 submittingproof of the same along with bid.

Dated this.......................... day of .....................….. 201...........….......Signature

...................................................(In the Capacity of)

Duly authorized to sign bid for and on behalf of

(Name & Address of Bidder) ............................................................…...........

Mobile:



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 solutionin the below mentioned format.

1) The format for furnishing details of required Software

Sl. No Description Make / Model/PartNo./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 (notnumber of users based)

Dated……(Signature)

(In the capacity of)Duly authorized to sign bid for & on behalf of(Name & Address of the Bidder)



Annexure-12 BFormat 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 implementationof 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





3 Server – UAT (only for DC)





B Database licenses

1 RDBMS – DC site

1.1 RDBMS* for Asset Liability ManagementDatabase Server


2 RDBMS – DR site





3 RDBMS – UAT Servers



C Third Party Software (Other than RDBMS)

1 Operating System – DC site

1.1 OS for Application Server

1.2 OS for Database Server


2 OS – DR site




3 OS – UAT Servers




D **Any other Requirement ofhardware/software/network & SecurityEquipments, LAN, Bandwidth etc. To beclearly mentioned.

** Any other requirements such as Networking Equipments, Peripherals, LAN, bandwidth etc. to beadvised 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)



Annexure-13Table for Arriving at the Total Ownership Cost

TABLE-A: Cost of Application Software

Sl. No Item description UnitPrice

TotalPrice

1 Application Cost - Licenses for Asset Liability ManagementSystem# -

2 Any other supporting software/Tool (Please Specify)Total Cost of Application Software

TABLE-B: Cost of Implementation, Training, Warranty etc.

Sl. No Item description UnitPrice

TotalPrice

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 RFPTotal Cost of Implementation, Training, Warranty etc.

TABLE-C: Cost of AMC/ATS for two years after the warranty

Sl.No

Item description Amount

1 Cost of AMC for ALM Solution for next 2 years after expiry of warrantyAny 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 ofresources deployed for FM alongwith activities covered under FM) FMCost per year should be fixed for five years.Any Other Cost (Please Specify)

Total Cost of FM Services for Five years



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 Bankmay discontinue FM services at any point of time at its discretion.



Annexure-14Bid submission Covering Letter

Note: This Bid Offer Covering letter should be on the letter head of the Bidder and should be signedby an authorized person.

Date:

ToAsstt. General Manager (IT)Department of Information TechnologyAllahabad 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 conditionsforming 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 theInternational 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 theSolution in accordance with the Requirements specified within the RFP for Solution of ALM withinthe timeframe specified, starting from the date of receipt of notification of award from AllahabadBank.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 10percent of the ‘Contract Price’ for the due performance of the Contract, in the form prescribed by theBank.

All the details mentioned by us are true and correct and if Bank observes any misrepresentation offacts on any matter at any stage, Bank has the absolute right to reject the bid / proposal anddisqualify 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 abovecontract, 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 wedo not have right to object and have no reservation in this regard; the decision of Allahabad Bank inthis regard shall be final, conclusive and binding upon us.

We confirm that our company/system integrator/other partners participating in this bidding as part ofthe consortium have not been black listed/banned by a regulatory authority and any previous ban isnot in force at present.



We enclose a Demand Draft /Bankers' Cheque bearing No……………. dated ……/ …../20… drawnby ……….. 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



Annexure-15Notification of Acceptance

Note: This letter should be on the letterhead of the Bidder and should be signed by anauthorized person.

Date:

ToThe Asstt. General Manager (IT)Department of Information TechnologyAllahabad 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 andactivities as per the Scope of Work mentioned in the subject RFP.

Signature of Authorised Person (Seal)



Annexure-16CONTRACT FORM

THIS AGREEMENT made and entered into at ……..on this the…..day of………201.. BetweenALLAHABAD 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 contextso require includes its successors and assigns

WHEREAS the Purchaser invited bids vide RFP No. HO/DIT/ALM/2014-15/16 dated 20.11.2014 forcertain Goods and ancillary services viz., ..................................... (Brief Description of Goods andServices) and has accepted a bid by the Supplier for the provision of those goods and services inthe sum for .............................. (Contract Price in Words and Figures) (hereinafter called “theContract Price”).

NOW THIS AGREEMENT WITNESSETH AS FOLLOWS:

1. In this Agreement words and expressions shall have the same meanings as are respectivelyassigned 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 thisAgreement, viz.:

a. Bid submission Covering Letter and the Total Ownership Costsubmitted by the Bidder;

b. The Functional Requirementsc. The Technical Requirementsd. The RFPe. The Service Level Agreement

(SLA)

3. In consideration of the payments to be made by the Purchaser to the Supplier as hereinaftermentioned, the Supplier hereby covenants with the Purchaser to provide the goods andservices and to remedy defects therein in conformity in all respects with the provisions of theContract.

4. The Purchaser hereby covenants to pay the Supplier in consideration of the provision of thegoods and services and the remedying of defects therein, the Contract Price or such othersum as may become payable under the provisions of the Contract at the times and in themanner prescribed by the Contract.

Brief particulars of the goods and services which shall be supplied / provided by the Supplier are asunder:

S. No. Description of thesoftware/Services

PrimarySite DR Qty Unit Price Total

Price12345

TOTAL VALUE:



5. The Vendor shall provide technical support for the software application systems suppliedunder this contract, and will have overall responsibility of the performance, functionality andoperation 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 theRight to use supporting software provided /installed /configured by the Vendor and/orsoftware application systems supplied under this contract of Sale after the expiry of theWarranty period under this contract and it shall be at liberty to use/ run the said softwaresolutions with the help/support of its in house IT Officers or through any other out sourcingservice Agencies. The Vendors shall not have any right to question or object for continuationof the use of such software or software solutions irrespective of entering into any AMC withthe Vendor after the expiry period or not. The Bank will decide at its sole discretion afterexpiry 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 orin any proceedings.

6. The Vendor shall ensure the meeting of the Security features, the standards and proceduresas per Bank’s IT Security Policy and procedures should be meticulously followed, in line withprevailing Industry Standards. In case of the any violation of the industry Standards, if theBank 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, withnecessary documents so as to meet any exigencies.

8. The Vendor should ensure that all verification processes in the software solutions should begoverned by maker checker controls.

DELIVERY SCHEDULE:

IN WITNESS whereof the parties hereto have caused this Agreement to be executed in accordancewith their respective laws the day and year first above written.

Signed, Sealed and Delivered by thesaid ..................................................... (For Allahabad Bank)in the presence of:.......................................

Signed, Sealed and Delivered by thesaid ..................................................... (For the Supplier)in the presence of:.......................................



Annexure-17Performance Bank Guarantee Format

Bank Guarantee No:Bank Guarantee Amount:Expiry Date:Claim Period:Account

Date: DD-MM-YYYYToThe Asstt. General Manager (IT)Department of Information TechnologyAllahabad Bank,Head Office,2, Netaji Subhash Road,Kolkata – 700 001, (W.B.)India

Dear Sir,

WHEREAS..........................................(Company Name) registered under the Indian Companies Act1956 and having its Registered Office at.................................................................. India (hereinafterreferred 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 requiredto furnish a Bank Guarantee in lieu of the Earnest Money Deposit (EMD), issued by a scheduledcommercial bank in India in your favor to secure the order of the RFP in accordance with the RFPDocument (which guarantee is hereinafter called as “BANK GUARANTEE”)

AND WHEREAS the VENDOR has approached us,............................................................ forproviding the BANK GUARANTEE. AND WHEREAS at the request of the VENDOR and inconsideration of the proposed TENDER to you, WE,............................................................ having............................................................ Office at..........................................................., India haveagreed to issue the BANK GUARANTEE.

THEREFORE, WE, ......................................................., through our local office at ................... Indiafurnish 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 Guaranteewithout any demur, merely on demand from you and undertake to indemnify you and keep youindemnified from time to time to the extent of Rs........................(Rupees ..............................only) anamount equivalent to the EMD against any loss or damage caused to or suffered by or that may becaused to or suffered by you on account of any breach or breaches on the part of the RFP of any ofthe terms and conditions contained in the RFP and in the event of the VENDOR commits default ordefaults in carrying out any of the work or discharging any obligation in relation thereto under theRFP or otherwise in the observance and performance of any of the terms and conditions relating



thereto in accordance with the true intent and meaning thereof, we shall forthwith on demand pay toyou 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 obligationsin terms of the RFP.

Notwithstanding anything to the contrary contained herein or elsewhere, we agree that your decisionas to whether the VENDOR has committed any such default or defaults and the amount or amountsto which you are entitled by reasons thereof will be binding on us and we shall not be entitled to askyou to establish your claim or claims under Bank Guarantee but will pay the same forthwith on yourdemand without any protest or demur.

This Bank Guarantee shall continue and hold good until it is released by you on the application bythe VENDOR after expiry of the relative guarantee period of the RFP and after the VENDOR haddischarged all his obligations under the RFP and produced a certificate of due completion of workunder the said Tender and submitted a “No Demand Certificate “provided always that the guaranteeshall in no event remain in force after the day of ....................... without prejudice to your claim orclaims arisen and demanded from or otherwise notified to us in writing before the expiry of the saiddate which will be enforceable against us notwithstanding that the same is or are enforced after thesaid date.

Should it be necessary to extend Bank Guarantee on account of any reason whatsoever, weundertake to extend the period of Bank Guarantee on your request under intimation to the VENDORtill such time as may be required by you. Your decision in this respect shall be final and binding onus.

You will have the fullest liberty without affecting Bank Guarantee from time to time to vary any of theterms and conditions of the Tender or extend the time of performance of the Tender or to postponeany time or from time to time any of your rights or powers against the VENDOR and either to enforceor forbear to enforce any of the terms and conditions of the said RFP and we shall not be releasedfrom our liability under Bank Guarantee by exercise of your liberty with reference to mattersaforesaid or by reason of any time being given to the VENDOR or any other forbearance, act oromission on your part of or any indulgence by you to the VENDOR or by any variation ormodification of the RFP or any other act, matter or things whatsoever which under law relating tosureties, would but for the provisions hereof have the effect of so releasing us from our liabilityhereunder provided always that nothing herein contained will enlarge our liability hereunder beyondthe limit of Rs..................( Rupees....................................only ) as aforesaid or extend the period ofthe 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 fromthe 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 wereyour principal debtors in respect of all your claims against the VENDOR hereby guaranteed by us asaforesaid and we hereby expressly waive all our rights of surety ship and other rights, if any, whichare in any way inconsistent with any of the provisions of Bank Guarantee.



Subject to the maximum limit of our liability as aforesaid, Bank Guarantee will cover all your claim orclaims against the VENDOR from time to time arising out of or in relation to the said RFP and inrespect 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 orregistered post to our local address as aforesaid and if sent accordingly it shall be deemed to havebeen given when the same has been posted.

The Bank Guarantee and the powers and provisions herein contained are in addition to and not byway of limitation of or substitution for any other guarantee or guarantees here before given to you byus (whether jointly with others or alone) and now existing uncancelled and that Bank Guarantee isnot 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 usnor shall it be affected by any change in your constitution or by any amalgamation or absorptionthereof or therewith but will ensure to the benefit of and be available to and be enforceable by theabsorbing or amalgamated company or concern.

The Bank Guarantee shall come into force from the date of its execution and shall not be revoked byus 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 ofany 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 ............. ; andiii) We are liable to pay the guaranteed amount or any part thereof under this Bank Guarantee onlyand 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 Articlesof Association of our Bank and the undersigned has full power to execute this Bank Guaranteeunder the Power of Attorney issued by the Bank.

For and on behalf of

Branch Manager

Seal & Address



Annexure 18Pre Bid Query Format

Sl.No

Section & ClauseRef. No. /

Appendix No. /Annexure No

Page No. RFP Text QueryResponse to Query

(to be left blank by thevendor)



Annexure 19SELF DECLARATION – BLACKLISTING

ToThe Asstt. General Manager (IT)Department of Information Technology

Allahabad Bank,Head Office,2, Netaji Subhash Road,Kolkata – 700 001, (W.B.)India

Dear Sir,

Sub: Supply, Implementation, Customization, Deployment, Maintenance and Support ofSystems.

Ref: Bid Document No. Dated.

We hereby certify that, we have not been blacklisted by any Government Dept. / PSU / Banks fornon-implementation / non delivery of the order / not providing support currently.

Signature of Authorized Official

Name and Designation with Office Seal

Place:

Date:



Annexure-20BID SECURITY FORM

Whereas........................... (Hereinafter called “the Bidder”) who intends to submit biddated................. (date of submission of bid) for the supply of ............................ (name and/ordescription 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 boundunto Allahabad Bank (hereinafter called “the Beneficiary”) in the sum of_______________________for which payment will and truly to be made to the said Beneficiary, theBank binds itself, its successors, and assigns by these presents. Sealed with the Common Seal ofthe 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 validityor

(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 theperiod 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 toBidders.

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 theBeneficiary will note that the amount claimed by it is due to it, owing to the occurrence of one orboth of the two conditions, specifying the occurred condition or conditions.

This Guarantee will remain in force up to _____________ and any demand in respect thereof shouldreach 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 isreturned 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.



Annexure 21Undertaking – Document Correctness

This is to certify that the information furnished herein and as per the documents submitted (hardcopy and soft copy) is true and accurate and nothing has been concealed or tampered with. Wefurther certify that the contents of the soft copy are same as those provided in the hard copy. Wehave gone through all the conditions of RFP document and are liable to any punitive action forfurnishing false information / documents.

Dated this _____ day of ____________________ 201_

Signature(Company Seal)

In the capacity ofDuly authorized to sign bids for and on behalf of:



Annexure 22ONLINE REVERSE AUCTION COMPLIANCE STATEMENT

(To be submitted by all the technically qualified bidders)Date: ----------

ToAsstt. General Manager (IT),Department of Information Technology,Allahabad Bank,Head Office,2, N.S. Road,Kolkata – 700 001West Bengal

DECLARATION

1 We ………………………….. (Name of the company) hereby confirm having submitted our bid forParticipating in Bank’s RFP Ref No. HO/DIT/ALM/2014-15/16 dated 20.11.2014 for Appointmentof Vendor for Supply, Deployment, Customization, Implementation, Maintenance and Support ofAsset Liability Management Solution.

2 We confirm having read and understood the terms and conditions of the RFP as well as theProcedures relating to the process.

3 We hereby undertake and agree to abide by all the terms and conditions stipulated by theAllahabad 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 serviceprovider 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 andauction company.

5 We, hereby confirm that we will honor the Bids placed by us during the E tendering/OnlineReverse Auction process, failing which we shall be liable for any other consequential action thatmay be taken by the Bank including any debarment from participation in future procurement bythe Bank.

6 We confirm having nominated our representative (Shri/Smt/Ms……………… designatedas……………………………….of our company to participate in the E tendering/Online ReverseAuction process on behalf of the company. We accordingly authorize Bank and / or the AuctionCompany to issue user ID and password to the above named official of the company. Weundertake that the company shall be bound by the actions made by him during the E tenderingprocess and thereafter.

7 We undertake to submit the confirmation of last bid price and price breakup by us to the AuctionCompany /Bank within one working day of the completion of event and any other specificrequirement indicated in the RFP.

Signature with company sealName & Address of Company:Date:

Name & Designation of Authorized Representative:

Signature of Authorized Representative:



Annexure 23Undertaking – Legal

We hereby declare that no inquiries or investigations have been threatened, commenced or pendingagainst us or any other member of the consortium by any statutory or regulatory or investigativeagencies or lending institutions.

Dated this _____ day of ____________________

Signature

(Company Seal)

In the capacity of

Duly authorized to sign bids for and on behalf of: