Pre-Bid Response: RFP for implementation of Mobile Banking ... · proposal. Bank is looking for an...

Pre-Bid Response: RFP for implementation of Mobile Banking Solution (Ref No. BCC/DB/MB/107/003 dated 16.09.2015) of 57

RFP for implementation of Mobile Banking Solution (Ref No. BCC/DB/MB/107/003 dated 16.09.2015)

Pre-Bid Queries, Responses and Corrigendum / Amendments

S.No. Page # Point/Section # Clarification point as stated in the tender document

Query Response

1. 24 Point 1, Section 5.2 The Bidder would be responsible for implementation of an end-to-end mobile banking solution with required hardware, software, database, middleware, etc.

Is bank having any preference of OS on server (Windows, Linux, etc.)?

The Bidder is required to provide licensed OS for the proposed solution and should include arrangement for support, regular patch update, fixes and upgrades. The Bidder is required to provide Bill of Material with their proposal which should cover all the requirements as per the scope of the RFP.

2. 24 Point 1, Section 5.2 The Bidder would be responsible for implementation of an end-to-end mobile banking solution with required hardware, software, database, middleware, etc.

Is bank fine with open source softwares (Linux, app containers like Tomcat, etc.)?

The Bidder is expected to provide licensed software’s for the proposed solution and should include arrangement for support, regular patch update, fixes and upgrades. Open Source software is not allowed. The Bidder is required to provide Bill of Material with their proposal which should cover all the requirements as per the scope of the RFP.


3. 24 Point 2, Section 5.2 Bidder to provide a composite solution of mobile banking services as Native/Hybrid/J2MEapplication to Bank’s customers with ability to work in all types of network/handsets, for e.g. GSM, CDMA, USSD/NUUP, Android, Windows, RIM-based systems

Please mention what use cases are applicable for USSD/NUUP based app

The use cases will be as per the NPCI certification test cases and will be shared with the successful bidder.


Please mention what use cases are applicable for non-smartphone devices (J2ME devices, WAP based and low end handsets)

All features that are listed in Annexure O-(Basic module of mobile banking) should be available on all platforms including low-end handsets / J2ME devices.


Please elaborate RIM based system. We understand blackberry devices - Please confirm. Is bank looking at app traffic routed through BES. If so, a) what version of BES bank has b) Please confirm if we can assume providing / configuring and maintaining BES is not in scope of this RFP

RIM would refer to blackberry devices and platform.

6. 24 Point 2, Section 5.2 Bidder to provide a composite solution of mobile banking services as Native/Hybrid/J2MEapplication to Bank’s customers with ability to

Blackberry phones are not having much future and existing BB users are fast migrating to other platforms. Considering this, is bank looking at supporting blackberry

Yes, the proposed solution should run on Blackberry devices also.


work in all types of network/handsets, for e.g. GSM, CDMA, USSD/NUUP, Android, Windows, RIM-based systems

phones and tablets

7. 24 Point 3, Section 5.2 The proposed Mobile banking solution should support facilities like IMPS (P2P, P2A, P2M, P2U etc.) funds transfer across Banks as well as intra bank, Mobile/DTH recharge, Utility Bill Payments, Ticket (Movie, Air, Railway) Booking, M-commerce, Card/Account to Card/Account Payments, necessary integration with NPCI (IMPS) and other payment aggregators for these services/various applications through Mobile Phones and should be enabled for Web based services.

Please confirm for fund transfer, What kind of data interface bank would provide for mobile solution to integration. Assuming that bank would provide odata based web services

The details will be shared with the successful bidder.

8. 22 Point 3, Section 5.2 The proposed Mobile banking solution should support facilities like IMPS (P2P, P2A, P2M, P2U etc.) funds transfer across Banks as well as intra bank, Mobile/DTH recharge, Utility Bill Payments, Ticket (Movie, Air, Railway) Booking, M-commerce, Card/Account to Card/Account Payments, necessary integration with NPCI (IMPS) and other payment aggregators for these

Please confirm assuming necessary documentation and technical support would be provided for such web services

Bank will share the necessary documentation with the successful bidder.


services/various applications through Mobile Phones and should be enabled for Web based services.


Is bidder required to directly interface with external service providers and core banking system, ATM switch etc. or bank has existing middleware which would provide the interfaces for mobile solution. Is providing middleware in scope?

If the proposed solution includes provision for middleware, then bidder needs to factor the same in the TCO under other software required for implementation of the solution. Bidder to provide Bill of material with their technical proposal. Bank is looking for an end to end complete solution and RFP is clear on the scope.

10. 22 Point 3, Section 5.2 The proposed Mobile banking solution should support facilities like IMPS (P2P, P2A, P2M, P2U etc.) funds transfer across Banks as well as intra bank, Mobile/DTH recharge, Utility Bill Payments, Ticket (Movie, Air, Railway) Booking, M-commerce, Card/Account to Card/Account Payments, necessary integration with NPCI (IMPS) and other payment aggregators for these

What kind of data interfaces shall we consider? (Assuming odata web services. Please confirm)

The bidder is expected to have experience in implementation of mobile banking with all the mentioned interfaces.


services/various applications through Mobile Phones and should be enabled for Web based services.


Please confirm if mobile solution is required to consume web services and not expose web services?

The bidder is expected to have experience in implementation of mobile banking with all the mentioned interfaces and details will be shared with the successful bidder.

12. 24 Point 4, Section 5.2 It should run on all types of handsets/TAB/Smart phone existing as well as new handsets coming in

We assume we will only provide support on the below platforms. Kindly confirm : - Android V 4.x to 5.x - iOS version 6 to 8 - Windows Phone version 8.x - Windows tablets (Windows version 8.x) - BlackBerry version 7 to 10

The proposed solution should work on all handsets/TAB/smart phones existing in the market as well as new devices/handsets coming in the market.



Please confirm if we assume support for new handsets coming in market would be provided as part of AMC and not part of project implementation.

RFP is clear on the scope.


Is there a recommended set devices and OS version that the solution should support.

The proposed solution should work on all handsets/TAB/smart phones existing in the market as well as new devices/handsets coming in the market.

15. 25 Point 6, Section 5.2 The mobile banking solution must be capable to work on varied communication modes and support GPRS, SMS, USSD and WAP based transactions with or without encryption as per the requirement of the Bank.

Please mention what use cases are applicable for SMS based app

The application should also work on SMS mode of communication. Application should support varied modes of communication as mentioned in the RFP.


Please mention what use cases are applicable for WAP based app

The application should also work on WAP mode of communication. Application should support varied modes of communication as mentioned in the RFP.


Please confirm if the app is required to work over SMS channel to make transactions in place of internet or the transaction would be performed in native sms editor (using some short codes for ex sms TXN to 111)

The application should also work on SMS mode of communication. Application should support varied modes of communication as mentioned in the RFP.



Please confirm if the app is required to work over USSD / NUUP channel to make transactions in place of internet or the transaction would be performed in native phone dialer (using short codes like *111*10#)

The application should also work on USSD mode of communication. Application should support varied modes of communication as mentioned in the RFP.

19. 25 Point 7, Section 5.2 The mobile banking solution has to interface with Bank’s Core banking application i.e. Finacle 7.0.25, ATM Switch/any other middleware of the Bank with seamless parameterization and customization for successful implementation. The required customization at CBS/Switch end shall be done by the Bank.

What kind of interfaces the bank would provide. We assume odata web services. Please confirm


20. 25 Point 7, Section 5.2 The mobile banking solution has to interface with Bank’s Core banking application i.e. Finacle 7.0.25, ATM Switch/any other middleware of the Bank with seamless parameterization and customization for successful implementation. The required customization at CBS/Switch end shall be done by the Bank.

We understand required documentation and technical support would be provided for such web services / other interfaces. Please confirm

Bank will share the necessary documentation with the successful bidder.

21. 25 Point 8, Section 5.2 Bank also intends to procure a mobile application development platform

Please specify if the bank is having any preference for mobile application development platform

The details for mobile application development platform are mentioned in the RFP.

22. 25 Point 8, Section 5.2 Bank also intends to procure a mobile application development

Kindly let us know if the commercials will include

Yes


platform procurement and support for the platform

23. 25 Point 9, Section 5.2 Bidder will be responsible for supply, installation and end to end implementation of Mobile Banking Solution, including customization, training to bank officials, etc.

How many people shall we consider for training ?

Initially, the technical team would be trained for complete solution maintenance and thereafter operations team members will be trained for application and web admin portal usage.

24. 25 Point 9, Section 5.2 Bidder will be responsible for supply, installation and end to end implementation of Mobile Banking Solution, including customization, training to bank officials, etc.

We assume training will be in "Train the trainer model" please confirm

Initially, the technical team would be trained for complete solution maintenance and thereafter operations team members will be trained for application and web admin portal usage.

25. 25 Point 13, Section 5.2

The successful bidder has to provide support for troubleshooting and enhancements in the services during the contract period. Enhancement would include inclusion of all new browser/handset/ devices/mobile platform OS coming in the market within 1 month of their launch and also new market/industry related functionalities.

Please mention the other factors the bank considers apart from hardware, software, database and middleware.

The query is not proper.


The successful bidder has to provide support for troubleshooting and enhancements in the services during the contract period. Enhancement would include

Please confirm (since the scope is not known) if we can take up Enhancements related to new mobile OS, market or industry trends as per change management process

RFP is clear on these terms and to be taken as part of project implementation as per the scope of the RFP. No change management process is acceptable.


inclusion of all new browser/handset/ devices/mobile platform OS coming in the market within 1 month of their launch and also new market/industry related functionalities.


The successful bidder has to provide support for troubleshooting and enhancements in the services during the contract period. Enhancement would include inclusion of all new browser/handset/ devices/mobile platform OS coming in the market within 1 month of their launch and also new market/industry related functionalities.

Specify the scope of enhancements that are being proposed

RFP is clear on these terms.


The bidder has to undertake to incorporate, at no cost to the Bank, suitable changes in the solution including the software, procedure and operations as required from time to time to comply with any new rules of Indian Law from RBI/IBA/MFI/TRAI/Govt. of India/NPCI and other Regulators for providing the Mobile Banking services.

Please specify the nature and magnitude of this work. The work will be accepted only in the form of Change Requests

RFP is clear on these terms and to be taken as part of project implementation as per the scope of the RFP. No change management process is acceptable.



The scope of work of the proposed mobile banking solution is not restricted to only domestic operations but should extend to cover Banks domestic operations, Regional Rural Bank’s (RRB’s), subsidiaries in India and branches, offices and subsidiaries in overseas center's. The requirement at RRB’s, subsidiaries and overseas center's are on need basis. Currently, bank proposes to include six overseas territories in addition to domestic operations.

It is stated that "The requirement at RRB’s, subsidiaries and overseas center's are on need basis." However it is also stated that "Currently, bank proposes to include six overseas territories" The above statements conflict with each other. Please confirm if we need to propose only for domestic operations for now.

Currently, bank proposes to include six overseas territories and three RRB’s in addition to domestic operations. The hardware and application licensing requirement would be common with separate instances running for RRB’s, subsidiaries and overseas territories. The bidder to factor-in enterprise wide application licensing. Implementation cost for overseas territories and RRB’s would be payable separately which would also include cost of customization and hardware upgrade.


The hardware and application licensing requirement would be common with separate instances running for RRB’s, subsidiaries and overseas territories.

Is each territory having separate DC and DR setup and application instances are to be replicated at each DC and DR site

Yes


The hardware and application licensing requirement would be common with separate instances running for RRB’s, subsidiaries and overseas territories.

If separate instances are running at each territory, how is bank looking at interaction among the instances in these territories ? Please elaborate

The details will be shared with successful Bidder.


The bidder to factor-in enterprise wide application licensing. Implementation cost for overseas territories would be payable separately which would also include cost of customization and hardware upgrade.

We assume to consider only one instance of mobile solution at one DC and one DR site as part of current proposal. Please confirm if the cost of support for other territories / instances would be discussed separately.

Yes, bidder to quote the cost of each territory and RRB. For overall costing six overseas territories and three RRB’s to be considered.



The Bidder should provide a Composite solution for both retail and corporate customers. Initially the retail solution will be implemented and in a phased manner corporate solution will be executed. The implementation modalities would be discussed between bank and the selected vendor for a smooth transition.

Please mention the difference in scope for retail and corporate solution

Currently bank is expecting application for its retail customers only. However, bank would like to extend the facility to corporate customers with multiple limits, authorization for specific products at a later stage.


The Bidder should provide a Composite solution for both retail and corporate customers. Initially the retail solution will be implemented and in a phased manner corporate solution will be executed. The implementation modalities would be discussed between bank and the selected vendor for a smooth transition.

Will the scope and cost for the solution for corporate customers discussed and agreed separately or shall be part of commercials of this proposal ?

Currently bank is expecting application for its retail customers only. However, bank would like to extend the facility to corporate customers with multiple limits, authorization for specific products at a later stage.


The Administrator Web portal should generate MIS/settlement report for reconciliation including IMPS.

How many reports shall we consider?

Bank intends the bidder to deliver a composite solution which includes a web portal for customer registration; transaction monitoring and such web portal should have capabilities as mentioned in Annexure D – Reports / MIS, reconciliation and monitoring. Bidder will have to provide a separate user management system for mobile banking application as a part of the offered solution. The details will be shared with the


successful bidder at the time of implementation.


The Bidder should propose to offer active support to enhance activation and usage of mobile banking by Bank’s customer. The Bidder can suggest criteria for incentivizing the customers and its monitoring.

As scope is not known, We propose Enhancements to be as per change management process, Please confirm.

Support for increasing activation and usage of the application is within the scope of this RFP. The Bidder is expected to commit all resource for successful implementation and continual usage by Bank’s customer. No change management process is acceptable. RFP is clear on these terms.


The Bidder should propose to offer active support to enhance activation and usage of mobile banking by Bank’s customer. The Bidder can suggest criteria for incentivizing the customers and its monitoring.

What is the scope of enhancements that are being proposed?

Support for increasing activation and usage of the application is within the scope of this RFP. The Bidder is expected to commit all resource for successful implementation and continual usage by Bank’s customer. RFP is clear on these terms.

38. 37 Annexure D Annexure D For all features mentioned in Annexure D, we consider that all workflow / business logic is available / to be done by bank / third parties as applicable. We understand mobile solution would interface to these systems to enable users of mobile app to use the services offered. Please confirm.

Details would be discussed with the selected bidder and is part of project implementation.


39. 37 Annexure D - Point 15

Type of Mobile Banking b) SMS Banking

Is bank looking at developing a middleware solution where it will receive sms from users (using native phone editor) and the sms would be processed at middleware system. We envision the middleware would be interfaced to bank's existing backend system to propagate the request for further processing. Please confirm if our understanding is correct

Bank will provide necessary access to mail server and SMS gateway. The details will be shared with the successful bidder.


Type of Mobile Banking Mobile Browser Based

What features are expected to be considered for browser based mobile app? Shall we assume full scope mentioned in RFP

Yes


Type of Mobile Banking Mobile Browser Based

What are the browsers expected to be supported ? We assume, IE, chrome, safari and Opera mini. Please confirm

All browsers supported on all handsets as per the industry trend.


Integration with existing systems - Internet Banking

What kind of interfaces would be provided for integrating with internet banking ?

Bank will arrange for interfacing details required for such interface, details will be shared with the successful bidder.



M-Commerce (Bill payment, Airline / Movie ticketing, Restaurant reservation and Payment) (Bank would bring such merchant aggregator and this proposed solution is required to interface with them for transaction/related information services. Bank may consider evaluating any such arrangement available with the selected bidder. However, it is not necessary for bank to accept all/any such arrangements)

Please elaborate on features / workflows expected. Our assumption is as below. Please confirm For Airline / Movie ticketing - Workflow 1: Select date, display available list with schedule (without MAP) - Workflow 2: Select the choice, make payment - Workflow 3: Save the ticket in app for reference - Workflow 4: Check current status of booking done

Bidder should be able to interface with bill aggregator available/identified by bank at the time of project implementation. The interface details would be provided to the selected bidder. Bank may evaluate any arrangement already available with the bidder provided it offers more and prominent billers than available with bank. The selection discretion would be solely of the bank.


Purchase Gift card / Travel card (Expectation is to collect request/template based inputs with basic validation from customers using the mobile banking application. Details would be discussed with the selected bidder and it would be part of ATS and no separate charges would be payable)

What is the validation mechanism? Please share details of template to be used for purchasing gift / travel card

Expectation is to collect request/template based inputs with basic validation from customers using the mobile banking application. Details would be discussed with the selected bidder at the time of project implementation.


Reminders on schedule bill payments

What kind of reminders the bank is expecting? We assume sms based notification (provided the mobile number is already registered with bank

Alerts for bill payment may be sent as notification or as SMS alert through the application.



Content based services •Geo-location based Push / Notification Services

What are the features / use cases expected?

Bidder to offer geo location based services as part of the offered solution. Bank will share geo tagged locations of such sites with the successful bidder.


Content based services •Geo-location based Push / Notification Services

Is the bank expecting these feature to be available for low end and non-smart phones? Smartphones considered are Android, Windows, Blackberry and iOS. All other phones can be considered as non-smartphones

On all types of handsets.


Ability to push notifications for Merchant Discount Offers/Redemption of Coupons

Assume that such Merchants have integration with bank systems and the bank system can notify mobile solution servers when such event happens

The details will be shared with the successful bidder at the time of project implementation.


IFSC search / lookup Assume that the interface is provided to the bidder for making lookup / search request

The details will be shared with the successful bidder at the time of project implementation.


Application support for customer preferred language

What languages shall we consider? All regional Languages



Is translation of all app text part of the scope of this RFP or bank would provide the translation?

Translation of all application text is within the scope of this RFP.



Is the dynamic data coming from backend expected to be multilingual? If so we assume the bank / third parties would provide such data in multilanguages supported. Please confirm

Translation of all application text is within the scope of this RFP.



Application support for multiple languages, primarily multilingual and support advertisement of banking product within the mobile banking application. (Application should support multiple languages including multilingual user interface. It should also support multilingual advertisements of banking product within the mobile banking application. Such advertisement content / creatives would be provided by the bank and bidder is only expected to arrange for the display in the application at relevant places)

Is the advertisement to be displayed at runtime or would be bundled with the mobile app at the time of installation ?

Application should support multiple languages including multilingual user interface with skin and labels on screen in respective language. It should also support multilingual advertisements of banking product within the application. Such advertisement content / creatives would be provided by the bank and bidder is only expected to arrange for the display in the application at relevant places.


Customer education through product demo to promote adoption. The product demo should be bilingual defining process flow for application download, activation and usage of menu options and services. The demo should be process specific. (Bidder is expected to provide attractive presentation, flash demo, animated videos of registration process, activation and usage of various functionalities (separately in English, Hindi and 1 regional

We understand the demo would not be interactive and play like animation in flash / video. Please Confirm

Product demo is to promote and popularize the application. Local language would help in better acceptance and thus is the requirement. Bidder is expected to provide attractive presentation, flash demo, animated videos of registration process, activation and usage of various functionalities.


language) of the proposed solution in consultation with bank’s team. This will help bank’s customers to quickly adopt this new solution and use it effectively. Print/media or any other publicity is not in the scope)


Customer education through product demo to promote adoption. The product demo should be bilingual defining process flow for application download, activation and usage of menu options and services. The demo should be process specific. (Bidder is expected to provide attractive presentation, flash demo, animated videos of registration process, activation and usage of various functionalities (separately in English, Hindi and 1 regional language) of the proposed solution in consultation with bank’s team. This will help bank’s customers to quickly adopt this new solution and use it effectively. Print/media or any other publicity is not in the scope)

We Assume that the region specific info would be existing in bank database which can be used to choose regional language for the content. Please Confirm

The application will enable the user to select the regional language of his choice.



Remote access to view queues in nearby Branch/ATM before reaching the site

How will this be achieved. Is the camera installed at ATM would stream the content to mobile app for user to see the queue

Not an immediate requirement. Would be discussed with selected bidder, when required.


Call back facility to engage with interested customers and provide data to CRM/Contact Centre system (Bank has a CRM solution – CRM Oracle R12)

Please elaborate on the scope and workflow

Bank has a CRM solution (CRM Oracle R12). The expectation here is to provide feed/data to the system in a specified format and provide information/response to the mobile banking customers. Details would be discussed with selected bidder at the time of project implementation.


Cash withdrawal though ATM, OTP/PIN based authentication, allowing non-BOB customers to withdraw cash from any BOB ATM using mobile authentication/authorization(Bidder will have to interface with a third party application to enable mobile based authenticated request. Alternatively, an interface with bank’s switch to trigger an on-us transaction. Details would be discussed at the time of implementation)

We assume mobile application to be used only for authentication and other systems will interface with mobile solution based on the interface format exposed by it. Please confirm.

Bidder will have to interface with a third party application to enable mobile based authenticated request. Alternatively, an interface with bank’s switch to trigger an on-us transaction. Details would be discussed at the time of implementation. The cost for this customization would be as per the agreed rate of technical support and agreement with bank.



Capability to push weather information and important context sensitive news (Bank expects support for push notifications including customer message, product information, weather information etc.)

Is mobile solution expected to integrate with weather and context sensitive news system. If so we assume the necessary interfaces required for integration would be provided by the bank.

Bank expects support for push notifications including customer message, product information, weather information etc. Bidder to ensure readiness for such interface and details would be discussed with selected bidder at the time of project implementation.


Capability to push weather information and important context sensitive news (Bank expects support for push notifications including customer message, product information, weather information etc.)

What kind of push notification shall we consider?

Bank expects support for push notifications including customer message, product information, weather information etc. Bidder to ensure readiness for such interface and details would be discussed with selected bidder at the time of project implementation.


Registration method (Bank has SMS gateway and the access would be provided to selected bidder for SMS delivery. Registration mechanism will be 1 user only 1 device from security point of view.)

Does bank has any user management system where such features can be customized. Or providing such user management system is part of RFP scope

The Bidder will have to provide a user management portal and the requirement is within the scope of the RFP.


Registration method (Bank has SMS gateway and the access would be provided to selected bidder for SMS delivery. Registration mechanism will be 1 user only 1 device from security point of view.)

We expect all the systems from where registration request will come to follow a common interface exposed by mobile solution. Pls Confirm




Referral by active Mobile banking users

Request to please elaborate what will be the workflow for this feature

Any request sent by a registered mobile banking user for registering any other number should also be logged. Bank administration would oversee the registration of the referred number.


Multi-factor authentication (Token / OTP / CAPTCHA / Security Question, etc.) Minimum two factor authentication for registered mobile number

Any two preferred authentication mechanism the bank would like to highlight

The proposed solution by the bidder should offer minimum two factor authentication, additional authentication factors would be subject to evaluation.

65. 43 Annexure D - Point 118 & 121

•MPIN for securing financial transactions. •Ability to lock the application due to incorrect MPIN attempts, remotely block access, with auto activation after 24 hours for accounts locked due to three incorrect attempts.

Where will be MPIN database maintained and generation? Locking of the same will be managed. Shall we assume it will be part of / configured in the bank system where other PINs (ATM, internet banking etc.) are maintained

Generation, encrypted storage and maintenance of access credentials are a part of the offered solution proposed by the Bidder. Bank will not provide any system for storage of access credentials.


Application PIN for accessing the application and nonfinancial transactions.

Where shall be application database maintained and generation of the same will be managed. Shall we assume it will be part of / configured in the bank system where other PINs (ATM, internet banking etc.) are maintained

Generation, encrypted storage and maintenance of access credentials are a part of the offered solution proposed by the Bidder. Bank will not provide any system for storage of access credentials.



Mention details regarding the interoperability of the product and the components which can be used by other applications. (Bidder is required to provide details regarding interoperability of the system. For example, IMPS interface of the proposed solution should be able to process transactions when the same data is captured through internet banking, branch system etc. and passed-on to the proposed system)

Is bank expecting to integrate their existing systems like internet banking through mobility solution (for ex. IMPS etc.)

Bidder is required to provide details regarding interoperability of the system. For example, IMPS interface of the proposed solution should be able to process transactions when the same data is captured through internet banking, branch system etc. and passed-on to the proposed system.



Please elaborate on what other applications of bank are expected to be integrated with proposed solution

Bidder is required to provide details regarding interoperability of the system. For example, IMPS interface of the proposed solution should be able to process transactions when the same data is captured through internet banking, branch system etc. and passed-on to the proposed system.




Also please mention what components of mobility solution are to be exposed for integration by other bank systems. This will help us provide interoperability details

All


Application capability to work on encrypted/non-encrypted mode as per the requirement of the Bank.

We understand that solution would either be encrypted or non-encrypted and would not switch between either at runtime. Please confirm

The channel of communication would be secure encrypted channel.


Application platform support for native, hybrid-web, hybrid combination (hybrid with additional native UI and code capability) and mobile web app.

Is the bank expecting either of the mentioned platform support (native, hybrid-web, hybrid combination (hybrid with additional native UI and code capability) and mobile web app) or all of them

Bank intends to have all options available. Feasibility of choosing the platform will be concluded with the successful bidder.


Support for Contact Centre log-in or API to integrate with Bank’s CRM/Contact Centre for various activities such as: • View customer registration and activation details

We understand mobile solution would expose APIs to provide details of customer registration (only mobile users), handset details to block, etc. Bank's CRM would consume these APIs. Please confirm

Bank intends the bidder to deliver a composite solution which includes a web portal for customer registration; transaction monitoring and such web portal should have capabilities as mentioned in Annexure D – Reports /


• Block stolen handset number • Regenerate access credentials • Change mobile number / handset

if understanding is correct MIS, reconciliation and monitoring. Bank does not have a separate user management system for mobile banking application. The portal will be accessed by Bank team, contact centre agents for logging request for registration, regeneration of MPIN, block number and other such services. The details will be discussed with the successful bidder at the time of project implementation.


Support for Contact Centre log-in or API to integrate with Bank’s CRM/Contact Centre for various activities such as: • View customer registration and activation details • Block stolen handset number • Regenerate access credentials • Change mobile number / handset

Is the scope restricted to mentioned features or the Banks would like to highlight any other workflows to be part of such APIs

All existing services that are provided by contact centre agents will be within the scope & any new services that bank wishes to include, the details will be shared with the successful bidder at the time of project implementation.


m) Support for Contact Centre log-in or API to integrate with Bank’s CRM/Contact Centre for various activities such as: • View customer registration and activation details • Block stolen handset number • Regenerate access credentials • Change mobile number / handset

How are current bank and portal users managed

Through the vendor provided web portal for existing mobile banking application.

75. 44 Annexure D - Point Support for Contact Centre log-in Are mobile user and existing portal / Yes


141 or API to integrate with Bank’s CRM/Contact Centre for various activities such as: • View customer registration and activation details • Block stolen handset number • Regenerate access credentials • Change mobile number / handset

bank users to be managed and maintained in separate systems. Please confirm.


Administrator Web portal capability for i.Search customer record ii. Approving user creation iii. Register and De-register users for mobile banking application iv. Terminate the users. v. Maintenance of activation requests vi. Change of Handset / Mobile number of users. vii. All administrator activities logged to indicate the creation, modification and deletion of data. viii. The web portal support to work on maker and checker concept for any addition, deletion, modification request made by the authorized users. ix. Support bulk upload for creation of users x. Handle concurrent uses of the

How are existing users authenticated and their profile / rights / access managed.

Through the vendor provided web portal for existing mobile banking application. The details will be shared with the Successful bidder.


same user ID. xi. Set thresholds, frequency limits (daily, weekly and monthly) etc.


Administrator Web portal capability for i.Search customer record ii. Approving user creation iii. Register and De-register users for mobile banking application iv. Terminate the users. v. Maintenance of activation requests vi. Change of Handset / Mobile number of users. vii. All administrator activities logged to indicate the creation, modification and deletion of data. viii. The web portal support to work on maker and checker concept for any addition, deletion, modification request made by the authorized users. ix. Support bulk upload for creation of users x. Handle concurrent uses of the same user ID. xi. Set thresholds, frequency limits (daily, weekly and monthly) etc.

If it exists shall we consider that user management features such as "terminate the users" "approving user creation" "Register and De-register users for mobile banking application" etc. would be handled in the existing bank's user management system ?

No. It is expected from the bidder that a separate user management module will be provided to handle all such services.

78. 46 Annexure D - Point Bank expects to reach a volume of How many years shall we project for Yes


171 daily 1,00,000 IMPS transactions, 50,000 Fund transfer transactions and 20,000 M-Commerce transactions within the initial six months and then upgrade as per the requirement of the Bank.

sizing the hardware. We consider 4 years. Please confirm


Bank expects to reach a volume of daily 1,00,000 IMPS transactions, 50,000 Fund transfer transactions and 20,000 M-Commerce transactions within the initial six months and then upgrade as per the requirement of the Bank.

How many transactions are expected to grow in next 4 years

Bank is currently having 38 lakh registered users, of which around 5 lakhs are active. The total retail customer base is around 4 crores and growing. Bidder should size the solution for multi-fold increase in mobile banking customer’s y-o-y with adequate scalability for users and simultaneous requests. Bank expects at least 3+ lac new registrations in each month and activations atleast 50% of the registrations.


Bank expects to reach a volume of daily 1,00,000 IMPS transactions, 50,000 Fund transfer transactions and 20,000 M-Commerce transactions within the initial six months and then upgrade as per the requirement of the Bank.

Shall we consider the upgrade of hardware in future on need basis as change request and take it up as per change management process. Please confirm

This would be on need basis and would be discussed with the bidder as and when the requirement arises. No change management process is acceptable.


81. 47 Annexure D - Migration from existing mobile banking solution Point 175 to 180

Migration from existing mobile banking solution

For how long the bank would support old mobile solution

Old and new system will run in parallel, once the new system stabilizes migration would take place.



Will both new and old mobile solution work parallely. If so what will be overlapping period before the old solution is sunset

Yes, old and new system will run in parallel, once the new system stabilizes migration would take place.



Is the existing mobile solution browser based, native or hybrid.

Native



Does it support non smartphones Yes


• Road map for migration of existing customer database to the new platform. • D96Road map including features of export/import of mobile app for easier migration.

Will it be a one-time activity or real time.

Migration of existing customer database would be in a phased manner.



• Road map for migration of existing customer database to the new platform. • Road map including features of export/import of mobile app for easier migration.

Please confirm if we can assume APIs to be exposed by the old solution provider for such facility

Only customer and transaction database will be made available for migration. Bank will provide customer data in txt/xls/csv format or nay other format which would be made available by the current vendor.


Availability of an export feature to backup App configuration data (Backup is required to sync the settings created by the user for beneficiary grouping, transaction grouping, etc.)

Please confirm if export feature is from new proposed solution

Backup is required to sync the settings created by the user for beneficiary grouping, transaction grouping, etc., in the new solution.


Application •OS Security check up. Application should have capability to detect if the application is running on a jail-broken/rooted /malware infected device. •Capability of the Application to read SIM serial no. and IMEI (International Mobile Equipment Identity) no. •Application must prevent hackers from accessing the app in a case where the device is rooted or jail-broken. •Blacklisting/Blocking of older versions of the Application on the back end, if there is a security breach. •Security logging where all

Ideally detection of jail broken / rooted devices is provided by "Mobile Device Management" tools. Is bank proposing to include scope and license for such tools

Bank is expecting a secured system with latest industry standard security. The solution should be audited by a reputed agency/IS auditor/management consultant not earlier than 6 month of this RFP date. Bank will also arrange for an independent audit any time during the contract period and bidder to arrange for necessary rectification/updation. Bidder providing advance security features would be preferred. Security features to be provided in the technical proposal.


security events that happen inside the application should be logged and sent to the back-end server.

89. 64 Annexure M - Point 2

The hardware should be sized to meet bank’s current volume of around 50,000 transactions per day originated from 26 lakh customers (5lakh+ active customers) and the recent spurt in usage of mobile banking in India. The numbers are expected to grow significantly in coming 2-3 years. Bank expects at least 3+ lac new registrations in each month and the system configuration should cater to the requirements of the Bank.

Please provide how many concurrent users are to be supported

The concurrent session of users and TPS should be as per the industry standards. TPS ideally could range between 200-300.


The hardware should be sized to meet bank’s current volume of around 50,000 transactions per day originated from 26 lakh customers (5lakh+ active customers) and the recent spurt in usage of mobile banking in India. The numbers are expected to grow significantly in coming 2-3 years. Bank expects at least 3+ lac new registrations in each month and the

How many transactions shall we assume to increase in next 4 years

Bank expects to reach a volume of daily 1,00,000 IMPS transactions, 50,000 Fund transfer transactions and 20,000 M-Commerce transactions within the initial six months. Bank is currently having 38 lakh registered users, of which around 5 lakhs are active. The total retail customer base is around 4 crores and growing. Bidder should size the


system configuration should cater to the requirements of the Bank.

solution for multi-fold increase in mobile banking customer’s y-o-y with adequate scalability for users and simultaneous requests. Bank expects at least 3+ lac new registrations in each month and activations atleast 50% of the registrations.


The hardware should be sized to meet bank’s current volume of around 50,000 transactions per day originated from 26 lakh customers (5lakh+ active customers) and the recent spurt in usage of mobile banking in India. The numbers are expected to grow significantly in coming 2-3 years. Bank expects at least 3+ lac new registrations in each month and the system configuration should cater to the requirements of the Bank.

Kindly provide more details on the below statement "The bank expects bidder to consider active users (5 lakhs) for sizing or total customers (26 lakhs)."

Bank expects to reach a volume of daily 1,00,000 IMPS transactions, 50,000 Fund transfer transactions and 20,000 M-Commerce transactions within the initial six months. Bank is currently having 38 lakh registered users, of which around 5 lakhs are active. The total retail customer base is around 4 crores and growing. Bidder should size the solution for multi-fold increase in mobile banking customer’s y-o-y with adequate scalability for users and simultaneous requests. Bank expects at least 3+ lac new registrations in each month and activations atleast 50% of the registrations.


The hardware should be sized to meet bank’s current volume of

How many active users bank expects to grow in next 4 years

Bank is currently having 38 lakh registered users, of which around 5


around 50,000 transactions per day originated from 26 lakh customers (5lakh+ active customers) and the recent spurt in usage of mobile banking in India. The numbers are expected to grow significantly in coming 2-3 years. Bank expects at least 3+ lac new registrations in each month and the system configuration should cater to the requirements of the Bank.

lakhs are active. The total retail customer base is around 4 crores and growing. Bidder should size the solution for multi-fold increase in mobile banking customer’s y-o-y with adequate scalability for users and simultaneous requests.

93. General Query

General Query NA Please provide details of mechanism of user authentication. We assume user registration is not part of scope of this RFP

It is the part of scope of this RFP

94. General Query

General Query NA Please provide details of mechanism of user authentication with third party services. We assume user registration is not part of scope of this RFP

It is the part of scope of this RFP

95. General Query

General Query NA We assume one DC and one DR site. Please mention if solution is to be hosted at any other site

Solution to be hosted at DC site in Mumbai and DR site in Hyderabad.

96. General Query

General Query NA Are the required data interfaces (web service, etc. for mobile solution integration) already developed and ready or they will be developed during project execution

It is expected from the Bidder to provide an end – to –end Mobile Banking solution with all required data interfaces.


97. 20 3.6.21 The vendor may not subcontract or permit anyone other than its personnel to perform any of the work, service or other performance required of the vendor under the contract without prior explicit written consent of the Bank.

We assume vendor means OEM / OSD and not necessarily bidder. Please confirm

The successful Bidder.

98. 24 Section 5.1 Point 24

Bidder should be Original Solution Developer (OSD) / Original Equipment Manufacturer (OEM) of the Solution offered or agency authorized by the OSD to implement their solution on their behalf.

Is Bank expecting bidder to implement on behalf of OSD by taking access to their code base ? OSD would never share their code / IP. We understand that bidder may partner with the OSD and OSD would customise their existing solution. Please confirm our understanding.

Yes.

99. 26 5.3.1 The Bidder should provide a dashboard for uptime check and related reports

Kindly confirm, Bank will be provide monitoring system or SI need to proposed for same

Bank intends the bidder to deliver a composite solution which includes a web portal for customer registration, transaction monitoring and such web portal should have capabilities as mentioned in Annexure D – Reports / MIS, reconciliation and monitoring.


100. 46 Annexure D: 173.cc The predefined pages of the web portal should handle web application security threats like Cross-site scripting, SQL injection flaws, Malicious file execution, Information leakage, Improper error handling, Broken authentication and session management, Insecure Cryptographic storage, Failure to restrict URL access. Separate Document to be submitted for the same.

Kindly confirm, Bank will be provide tools for security or SI needs to factor on same in proposal

No, it is within the scope of this RFP and bidder needs to factor the same in their proposal.

101. 47 Annexure D: 176.b Road map for migration of existing customer database to the new platform.

Kindly confirm , Bank has any current setup on Mobile banking along with DB version.

No.

102. 64 Annexure M:1 The UAT setup is required only at DC and would be replica of the production setup. Storage would be provided by the bank and necessary interfacing cards/devices are mentioned in the hardware details.

Kindly confirm, For UAT bank will be provide storage or SI needs to proposed for same

The DC DR production setup would be one to one replica. The UAT setup is required only at DC and would be replica of the production setup UAT setup can have common application and database. In DC, production and UAT environment will be required.


103. 65 Annexure M:16 Required hardware and related software (like OS, Database etc.) for the solution should be quoted and will be considered as a part of TCO for the purpose of evaluation. However Bank has sole and absolute discretion not to procure hardware and related software from the vendor as the Bank may use existing IT infrastructure or procure separately / directly.

Kindly Confirm, Bank has looking for specific OS and Database for mobile banking

The Bidder is required to provide licensed software for the proposed solution and should include arrangement for support, regular patch update, fixes and upgrades. The Bidder is required to provide Bill of Material with their proposal which should cover all the requirements as per the scope of the RFP.

104. General Query

General Query NA As we are going to Test the Banking Services in various Mobile sets, whether we need to setup a Mobile Lab for the same?

Bank will do User acceptance testing on available mobile handsets /devices.

105. 27 5.6 NA Performance expected by the client?. Based on that we can plan for Performance Testing.


106. 25 5.2/Broad Scope of work

Open source platform is not acceptable. Bank is looking for industry standard development platform with prior installations

Is it only for MADP platform. Can we propose open source platform for call login/Admin portal etc. Please advise.

The admin portal is the requirement of the RFP, the portal should comply with the security features as listed in Annexure D and provide all specifications as listed in Annexure D for dashboard.

107. 22 Point 3, Section 5.2 The proposed Mobile banking solution should support facilities like IMPS (P2P, P2A, P2M, P2U etc.) funds transfer across Banks as well as intra bank, Mobile/DTH recharge, Utility Bill Payments, Ticket (Movie, Air, Railway)

What kind of data interfaces shall we consider? (Assuming odata web services. Please confirm). Please confirm the protocols that need to supported for this implementation?

Bidder should be able to interface with bill aggregator available/identified by bank. The interface details would be provided to the selected bidder. Bank may evaluate any arrangement already available with the bidder provided it


Booking, M-commerce, Card/Account to Card/Account Payments, necessary integration with NPCI (IMPS) and other payment aggregators for these services/various applications through Mobile Phones and should be enabled for Web based services.

offers more and prominent billers than available with bank. The selection discretion would be solely of the bank. Details will be shared with successful Bidder at the time of project implementation.


Please let us know the number applications with which middleware is expected to integrate and number of services that are expected to be built? Please confirm the complexity split of the services that are expected to built in middleware.

Bidder should be able to interface with bill aggregator available/identified by bank. The interface details would be provided to the selected bidder. Bank may evaluate any arrangement already available with the bidder provided it offers more and prominent billers than available with bank. The selection discretion would be solely of the bank.

109. 22 Point 3, Section 5.2 The proposed Mobile banking solution should support facilities like IMPS (P2P, P2A, P2M, P2U etc.) funds transfer across Banks as well as intra bank, Mobile/DTH recharge, Utility Bill Payments, Ticket (Movie, Air, Railway)

Is middleware installation expected to be done by L&T Infotech?

Bank is looking for a complete end to end solution and RFP is clear on the terms and scope.


Booking, M-commerce, Card/Account to Card/Account Payments, necessary integration with NPCI (IMPS) and other payment aggregators for these services/various applications through Mobile Phones and should be enabled for Web based services.

110. 25 Section 5.1 Point 21

Bidder/Original Solution Developer (OSD) should be above CMM3/CMMI3 standards compliant.

Should the OSD be certified or only follow the process?

It should be compliant.

111. 57 Annexure - I Documentary evidence for PA-DSS compliance, Information security Audit, Vulnerability assessment & penetration testing reports and Usability Audit with undertaking duly signed by the Bidder/OSD to submit PA-DSS certificate within one year of acceptance of purchase order.

The Usability Audit results vary from app. to app. What is your expectation in terms of scope for the Usability Audit?

Usability Audit of the application developed for the Bank will be conducted.


112. 57 Section 3, Point 36 The license of the mobile application development platform should be for unlimited number of applications for the entire contract period. The applications developed and deployed using the mobile application development platform will have perpetual license. The licensing should cover two years of extended warranty after expiry of the contract.

We request the Bank to limit the number of applications as mobile application development platforms are priced according to the number of applications deployed on the same. This will be in the interest of the Bank as making this unlimited will unnecessarily overshoot the cost of the MADP. We suggest that the Bank identify the number of apps that it would like to deploy over a 4 year period and bidders can quote for the same. This will be beneficial to the Bank from a long term perspective.

No change in the RFP terms.

113. 9 Section 3: Evaluation process

d) Copies of the audited and published financial reports of the bidder/OSD. Audited Balance sheet for last three years (2012-13, 2013-14 and 2014-15) along with complete auditor’s certificate/qualifications. Audited balance sheet/P&L, certificate from Chartered Accountant.

We will submit audited balance sheet and P & L statements for the mentioned period. Apart from that bank has requested for a certificate from CA. Request the bank to consider either P&L and Balance Sheet or CA certificate .

Requirements mentioned in RFP have to be complied with.

114. 12 3.1. Technical details required

2) Reference calls / letters (overall weightage 5%) To assess the performance and support extended by the company to their other installations. The evaluation would be based on the letters received/calls made

The reference calls are already done for previous mobile banking RFP (RFP No: BCC/TBD/MBN/107/002; Dated: 25-06-2015). Will the bank consider previous calls for this RFP or fresh calling and evaluation will be done?

Fresh reference calls will be made for evaluation. Date and time for the calls would be conveyed to the bidder.


from/to the competent authorities of banks/financial institutions and the information gathered by the evaluation team during calls/site visits to the installation sites.


29. Certificate duly signed by the bidder/OSD for arrangement with Google/Apple/Windows etc., for uploading the application build on respective stores.

Whether applications will be hosted in vendor's name?

Bidder/OSD to submit certificate that the arrangement for uploading of application on respective stores is available. Though Bank has and will create account on respective stores and host the application under Bank’s name.

116. 23 5.1. Eligibility Criteria

5. OSD should have developed and implemented mobile banking application on the proposed Mobile Application Development Platform. The platform should have pre-built modules, functions, templates, interactive user interface for independent application development by bank’s in-house / 3rd party developers across all operating systems/mobile platforms.

"OSD/bidder should have developed and implemented any mobile application on the proposed Mobile Application Development Platform. The platform should have pre-built modules, functions, templates, interactive user interface for independent application development by bank’s in-house / 3rd party developers across all operating systems/mobile platforms."

No change in the RFP terms. OSD should have developed and implemented mobile application on the proposed Mobile Application Development Platform, such application should directly interface with Banks CBS and available to Banks customers for usage.


6. Applications which are only interfacing with an application developed on the platform will not be considered as third party mobile applications.

Need more clarification on the stated point.

Applications which have been designed, scripted/coded and published on the proposed mobile application development platform are third party mobile applications. Any application that only interfaces with the application designed, scripted/coded and published on the


proposed mobile application development platform will not be considered as third party mobile applications.


14. The bidder must enclose letter of appreciation/reference from Head Office / Central Office of the Bank where proposed Mobile banking solution and Mobile application development platform is operational currently. The letter of appreciation must be signed by an official of the Bank not below the rank of Deputy General Manager. The letters should be in English on the letterhead of the Bank duly stamped and signed. The certificate of implementation & satisfactory performance may be directly sent to Bank of Baroda by the issuing authority. Bidder to ensure its availability before commencement of evaluation work. As a part of eligibility bid Bidder must include mandatorily list of banks where proposed mobile banking solution developed by the OSD and Mobile application development platform is functional. The Bank will choose, in its absolute discretion, from amongst the list for the purpose of

We have already presented/submitted the Reference Letters on the bank's letterhead where the implementation of mobile banking solution is done for the previous RFP (RFP No: BCC/TBD/MBN/107/002; Dated: 25-06-2015). Will the bank consider the same for this RFP or Do we have to submit fresh certificates for the same.

Reference letters / certificates with date not earlier than three months from the date of issuance of this RFP, i.e.16.09.2015, may be submitted.


reference call.

119. 6 14 30 58

1.11 3.6.1 Annexure A Annexure J

Acceptance of Terms Recipient shall, by responding to the Bank with a submission, be deemed to have accepted the terms of this document in totality without any condition whatsoever.

Adherence to Terms and Conditions

Covering Letter Compliance to RFP Terms and Conditions

Request modification in clause. No change in the RFP terms.

120. 14 3.5.1 The bid security may be forfeited: i) If a bidder withdraws their bid during the period of bid validity; or ii) In case of a successful bidder, if the bidder fails:

a) To sign the Contract within the stipulated time; or b) To furnish Performance Bank Guarantee within the stipulated time and valid till the end of contract period plus three months



121. 14 3.5.3 Performance Bank Guarantee Request modification in clause. No change in the RFP terms.

122. 14 3.6.2 Execution of SLA/NDA We submit that the SLA and NDA shall be executed on such terms and conditions as may be mutually agreed between the parties at the time of contracting.


123. 15 3.6.4 Substitution of Project Team Members During the assignment, the substitution of key staff identified for the assignment shall not be allowed unless such substitution becomes unavoidable to overcome the undue delay or that such changes are critical to meet the obligation. In such circumstances, the vendor can do so only with the concurrence of the Bank by providing alternate staff of same level of qualifications and expertise. If the Bank is not satisfied with the substitution, the Bank reserves the right to terminate the contract and recover whatever payments made by the Bank to the vendor during the course of this assignment besides claiming an amount, equal to the contract value as liquidated damages. The Bank reserves the right to insist the vendor to replace any team member with

Request modification in clause.



another (with the qualifications and expertise as required by the Bank) during the course of assignment. The bidder will have to undertake that no such substitution would delay the project timelines.

124. 16 3.6.8 Penalty & Liquidated Damages (LD) Notwithstanding Bank’s right to cancel the order, liquidated damages at 1% (one percent) of the undelivered portion of the order value per week will be charged for every week’s delay in the specified delivery schedule subject to a maximum of 5% of the value of the order value. Bank reserves its right to recover these amounts by any mode such as adjusting from any payments to be made by Bank to the Bidder. Penalty will be calculated on per week basis. If the selected Bidder fails to complete the due performance of the contract in accordance to the terms and conditions, the Bank reserves the right either to cancel the contract or to accept




performance already made by the selected bidder. In case of termination of contract the Bank reserves the right to recover an amount equal to 5% of the Contract value as Liquidated Damages for non-performance. Penalty: (� If any act or failure by the Bidder under the agreement results in failure or inoperability of systems and if the Bank has to take corrective actions to ensure functionality of its property, the Bank reserves the right to impose penalty, which may be equal to the cost it incurs or the loss it suffers for such failures. � If the Bidder fails to complete the due performance of the contract in document, the Bank reserves the right either to cancel the order or to recover a suitable amount as deemed reasonable as Penalty / Liquidated damages for non-performance. SLA violation will attract penalties.

Bank may impose penalty to the


extent of damage to its any equipment, if the damage was due to the actions directly attributable to the staff of the Bidder. Damage to hardware equipment due to the actions directly attributable to the staff of the bidder, then bank may impose penalty on such damage. � The Bank shall implement all penalty clauses after giving due notice to the Bidder. If the bidder fails to maintain guaranteed uptime of 99.9% on quarterly basis then Bank may impose penalty as per the below table for the defaulting quarter subject to an annual cap of 5% of the Total Contract Value: Quarterly Uptime Amount of Penalty >=99.9% to 100% No penalty would be deducted >=99% to <99.9% 5% of amount payable for the quarter >=98% to <99% 10% of amount payable for the quarter >=97% to <98% 20% of amount payable for the quarter <97% 40% of amount payable


for the quarter Uptime calculation: The percentage uptime is calculated on quarterly basis as follows: (Total contracted hours in a month - downtime hours within contracted hours)X 100 / Total contracted hours in a month Bank will impose penalty for transaction decline and reversals due to technical reasons attributed by the Bidder. The Vendor should strictly comply to adhere with the Uptime guarantees mentioned above and penalty clause for downtime and non-adherence to uptime guarantees would be part of the Service Level Agreement (SLA). Vendor should provide dashboard for uptime check and related reports.

125. 17 3.6.9 Indemnity Request modification in clause. No change in the RFP terms


126. 17 3.6.10 Dispute Resolution (All questions, disputes or differences arising under and out of, or in connection with the contract, shall be referred to sole Arbitrator appointed by Bank and the award of the arbitrator shall be final and binding on the parties.)



127. 18, 19 3.6.12 & 3.6.18

Consequences of Termination for Default Cancellation of Contract and Compensation


128. 18 3.6.13 Confidentiality Request modification in clause. No change in the RFP terms.

129. 19 3.6.14 Limitation of Liability Request modification in clause. No change in the RFP terms.

130. 20 3.6.19 Non Payment of Professional Fees (If any of the items/activities as mentioned in the price bid are not taken up by the Bank during the course of this assignment, the Bank shall not pay the professional fees quoted by the vendor in the Price Bid against such activity/item.)



131. 20 3.6.21 Subcontracting (The vendor may not subcontract or permit anyone other than its personnel to perform any of the work, service or other performance required of the vendor under the contract without prior explicit written consent of the Bank.)



132. 20 3.6.22 Audit

Request modification in clause. No change in the RFP terms. Commercials for audits conducted by Bank will be borne by the Bank.

133. 24 5.1.23 Escrow Mechanism Request modification in clause. No change in RFP terms.

134. 26 26

5.2.16 5.3.4

The bidder has to undertake to incorporate, at no cost to the Bank, suitable changes in the solution including the software, procedure and operations as required from time to time to comply with any new rules of Indian Law from RBI/IBA/MFI/TRAI/Govt. of India/NPCI and other Regulators for providing the Mobile Banking services. The Bidder has to undertake suitable changes in the solution including the software, procedure and operations as required from time to time to comply with any


No change in RFP terms.


27 28

5.3.7 5.7.3

new rules of Indian Law/RBI/IBA/MFI/TRAI/Govt. of India/NPCI and other Regulators for Mobile Banking services. In this RFP, the ATS work would include version update/upgrade, bug fixing, updation to meet any regulatory/statutory changes, security alerts, audit observations, implementation and post implementation support etc. AMC for software as per the rates specified. It includes commercials for maintenance, version upgrade, enhancements on account of the changes in the industry/regulatory change etc.

135. 27 5.6 Acceptance Test Request modification in clause. No change in RFP terms. The mobile handsets will be made available by Bank. In any case where UAT cannot be carried out due to device constraints then vendor to arrange for UAT. Bank will not give sign off to bidder without completing the UAT on all types of OS and handsets.

136. 28 6 Section 6: Payment Terms, Support Services and Miscellaneous

Request modification in clause. No change in RFP terms.


Terms/Requirements

137. 50 Commercial Bid Template

Tax variations on TCO We would like to clarify that taxes on the invoices shall applicable as per the then prevailing tax laws and rates at the time of invoicing.

Bidder to quote the price inclusive of all taxes including service tax. The invoice submitted for payment should have clear break-up of all components including various taxes/levies, their rates, amount and related details.

138. Intellectual Property Rights (Additional Clause)

Request addition of clause. No change in the RFP terms

139. 72 Annexure S PRE CONTRACT INTEGRITY PACT Fall clause (page 75) Independent Monitors (page 75)

Request modification in clause. No change in the RFP terms Fall clause is revised, please refer amendments on page 57 of this document.

140. 25 5.2 Broad Scope of Work Point 8.

Bank also intends to procure a mobile application development platform

Please elaborate on the purpose of having to procure this platform as various mobile OS vendors have respective SDKs for developing mobile applications. Is the intent of bank to have a platform similar to Mobile Application content management so that Bank can make any changes such as changes in menu, changes in menu flows, look and feel etc.? Please clarify.

The features of the platform that bank intends to procure is mentioned in the scope of work. The platform should not be an open source platform. The Bidder is required to provide license for the proposed MADP and should include arrangement for support, regular patch update, fixes and upgrades for the entire contract period with extended warranty as mentioned in the RFP.

141. 64 Annexure M Hardware/ Software Specification

Sizing Please provide estimation on number of concurrent log ins in a given period of time say 1 hour, through web portal?



Point 4.

142.

38

Annexure D: Functional / Technical Specifications

Integration with third party service providers/software/middleware

For the Mobile Payment Transactions IMPS, Commerce, NPCI - is there going to be a payment hub or payment transaction gateway aggregator - like say BillDesk or will this be a bespoke API integration mechanism ?

Third party aggregation would be based on standard APIs / message format which would be provided / discussed at the time of implementation.

143.

42

Annexure D: Functional / Technical Specifications Registration and Download activity of mobile banking application

Registration method

Will the registration process involve an OTP mechanism - and is such a mechanism & system available currently within the bank ?

Yes. Bank has SMS gateway and the access would be provided to selected bidder for SMS delivery.

144.

42

Annexure D: Functional / Technical Specifications Registration and Download activity of mobile banking application

Registration method

What is the registration mechanism for the mobile banking solution - 1 user only 1 device, 1 user - Multiple devices or Multiple users from 1 device allowed ?

At present it is 1 user only 1 device. However, bidder to also factor 1 user multiple devices and multiple users one device

145. 43 Annexure D: Functional / Technical Specifications Security

Ability to store access credentials in encrypted format in the user’s handset

What user credentials need to be stored in the user handset - userid / password or MPIN? Will these user credentials be used to log into the mobile app in an offline mode?

Application password. No, GPRS connection will be checked and then user will be able to log on with the application password. For SMS, application password will be required to be entered by the user for login. The application password will be


What is the purge or archival policy for the on-device encrypted database?

saved in the application database in the device as long as the application is installed on the device. If user changes the handset or reinstalls a fresh setup then new application password will get saved in the application database in the device.

146.

43

Annexure D: Functional / Technical Specifications Security

Ability to deny access to handset that does not meet industry standard.

Pls clarify ... Does this mean jailbreak or rooted device detection ?

Yes, Bidder to ensure capability for such detection and the same should be parameterized / customizable as per bank’s requirement in the web administration portal.

147. 44 Annexure D: Functional / Technical Specifications Security

Mention any other security feature supported by the system with details and architecture of security components

Please elaborate on the security solutions required for the mobile banking solution - like (1) application authenticity - so that the app is not repackaged or reversed engineered (2) code obfuscation - to make it difficult for the code to be read and interpreted (3) source code encryption - to make it difficult for the code to be tampered with

Yes, all mentioned security features needs to be incorporated.

148. 44 Annexure D: Functional / Technical Specifications Scalability and Availability

No. of concurrent users the platform can support and handle requests in a second.

What is the active user base that will install & configure the mobile banking solution ? What is the concurrent peak user concurrency during a given day and peak TPS to be supported on the mobile banking solution ?

Bank is currently having 38 lakh registered users, of which around 5 lakhs are active. The total retail customer base is around 4 crores and growing. Bidder should size the solution for multi-fold increase in mobile banking customer’s y-o-y with adequate scalability for users and simultaneous requests.



149.

45

Annexure D: Functional / Technical Specifications Scalability and Availability

Capability of the proposed solution to push new Changes over the air without frequent uploading on App store of various platforms

Does the fix need to come from the public appstore as a version update or does the patch need to be delivered directly from the middleware mobility solution ?

From both the sources.

150.

45

Annexure D: Functional / Technical Specifications Scalability and Availability

Solution capability to provide Force Update / Upgrade

Does the fix need to come from the public appstore as a version update or does the patch need to be delivered directly from the middleware mobility solution ?

From both the sources.

151. 42 Annexure D: Functional / Technical Specifications Innovative offerings in a phased manner

Capability to push weather information and important context sensitive news

Will there be a need to push update notifications like - bill reminders, transaction & funds-transfer summaries, pending payee transactions etc ?

Yes.


List from mobile application development platform provider of Banks/Financial Institutions where platform has been deployed and third party applications have been developed, this is required to be

What comes under financial institutions?

Institutions which deal with financial investments, loans and deposits.


submitted by the Platform Provider (OEM) for each such implementation in Banks/Financial Institutions (Year, Bank name, major functions) as per Annexure R

153. 63 Mobile Application Development Platform capabilities:

No. of 3rd party mobile/web applications developed on the Mobile application development platform, with atleast one functional application developed by the OSD on the proposed Mobile application development platform.

Can these be any mobile application ...or Banking app only ?

Only Mobile Apps related to Banking.


Bidder/OSD should have never been blacklisted/debarred by Central/State Govt. Dept., Public/Private sector Bank/Financial Institution or any other organization in India or abroad in last three years prior to the date of issuance of this RFP.


155. 8 2.1.2. RFP Submission Validity Period

RFP responses must remain valid and open for evaluation, according to RFP terms, for a period of at least 180 days from the time of RFP submission.

Request clarification in clause. This clause is applicable for validity of Bid submission.

156. 13 3.2. Commercial Proposal, Sub-Clause 3

The prices and other terms offered by bidders must be firm for an acceptance period of 180 days from the last date of opening of

Request clarification in clause. This clause is applicable for validity of price & other commercial terms from date of commercial bid opening.


commercial bid.

157. 13 3.2. Commercial Proposal, Last Para.

Refusal/failure to commit implementation of Mobile Banking Solution as per terms of RFP shall result in disqualification of the vendor from this process as well as future procurements of Bank and forfeiture of EMD.


158. 17 3.6.6. Adherence to Standards:

The vendor should adhere to laws of the land and rules, regulations and guidelines issued by the various regulatory, statutory and Government authorities. The Bidder should provide a fully compliant system with latest certification/standards prevailing in the industry and ensure their time to time updation. Bank reserves the right to ascertain information from the banks and other institutions to which the bidders have rendered their services for execution of similar projects. Such feedbacks from high ranking officials would also form part of vendor selection and any strong adverse comment/action about product or service would make the bidder ineligible for further assessment/processing.

Request clarification in clause. No change in the RFP terms.

159. 3.6.13 The bidder clarifies that the bidder Yes.


confidentiality and the bank shall enter into a mutually agreeable confidentiality agreement that will govern this project.

160. 20 3.6.18. Cancellation of Contract and Compensation:

The Bank reserves the right to cancel the contract of the selected bidder and recover expenditure incurred by the Bank on the following circumstances: 1. The bidder goes into liquidation voluntarily or otherwise. 2. An attachment is levied or continues to be levied for a period of 7 days upon effects of the bid. 3. If deductions on account of liquidated damages exceeds more than 10% of the total contract price.


161. 21 3.6.22 Audit Request clarification in clause. No change in the RFP terms. Commercials for audits conducted by Bank will be borne by the Bank.

162. 21 3.6.23. Information and Secrecy

The Vendor must provide a written undertaking to the bank to be submitted duly signed on company letter head to comply with the secrecy provision pursuant to provision of Banking Regulation Act, 1949 and other applicable laws. The Vendor will follow professional ethics and conduct in performing their duties. The Bank has right to terminate the services

Request removal of this clause. No change in the RFP terms.


of the Vendor if it fails to comply with the conditions imposed.

163. 64 Annexure M: Hardware/ Software Specification

Point 15: The bidder is responsible to arrive at the sizing independently. The Bank is not responsible for any assumption made by the bidder with respect to the sizing. In the event the sizing quoted by the bidder does not meet the performance / service levels of the Bank, the bidder will at their cost carry out the necessary upgrades / replacements. The Bank will not pay any additional amount during the period of the contract.


164. 58 1 The UAT setup is required only at DC and would be replica of the production setup.

Is it mandatory to have an exact replica of production in UAT set up?

Yes.

165. 59 12 Bidder should factor the requirement for networking links for communication between the various components. The communication / networking links should be redundant to enable the solution to work seamlessly on the event of any link failure.

Kindly provide details. Will Bank provide rack space in DC/DR with power, network, firewall, routers, LAN/WAN, internet connection, etc?

Network level security (firewall, SSL, antivirus, etc.) will be provided by the Bank. Operating system/ Database/ Application level security will have to be arranged by the Bidder and same will be validated by Bank’s security team. OS hardening and implementation of security profile would be in consultation with bank’s security team.

166. 75 Annexure S - Integrity Pact

Entire Annexure inclusing clauses Request clarification. No change in the RFP terms.


Amendments to RFP for implementation of Mobile Banking Solution (Ref No. BCC/DB/MB/107/003 dated 16.09.2015)

Sr. No.

Page #

Point / Section #

Clarification point as stated in the tender document Clarification stated


14. The bidder must enclose letter of appreciation/reference from Head Office / Central Office of the Bank where proposed Mobile banking solution and Mobile application development platform is operational currently. The letter of appreciation must be signed by an official of the Bank not below the rank of Deputy General Manager. The letters should be in English on the letterhead of the Bank duly stamped and signed. The certificate of implementation & satisfactory performance may be directly sent to Bank of Baroda by the issuing authority. Bidder to ensure its availability before commencement of evaluation work. As a part of eligibility bid Bidder must include mandatorily list of banks where proposed mobile banking solution developed by the OSD and Mobile application development platform is functional. The Bank will choose, in its absolute discretion, from amongst the list for the purpose of reference call.

Reference letters / certificates with date not earlier than three months from the date of issuance of this RFP, i.e.16.09.2015, may be submitted.

2. 75 Annexure S Pre Contract Integrity Pact Fall Clause The BIDDER undertakes that it has not supplied/is not supplying similar product/systems or subsystems at a price lower than that offered in the present bid in respect of any other Ministry/Department of the Government of India or PSU and if it is found at any stage that similar product/systems or sub systems was supplied by the BIDDER to any other Ministry/Department of the Government of India or a PSU at a lower price, then that very price, with due allowance for elapsed time, will be applicable to the present case and the difference in the cost would be refunded by the BIDDER to the BUYER, if the contract has already been concluded.

The BIDDER undertakes that it has not supplied/is not supplying similar solution of similar size during last six months from the date of issuance of this RFP i.e. 16.09.2015, at a price lower than that offered in the present bid in respect of any other Ministry/Department of the Government of India or PSU and if it is found at any stage that similar solution of similar size was supplied by the BIDDER to any other Ministry/Department of the Government of India or a PSU at a lower price, then that very price, with due allowance for elapsed time, will be applicable to the present case and the difference in the cost would be refunded by the BIDDER to the BUYER, if the contract has already been concluded.

Pre-Bid Response: RFP for implementation of Mobile Banking ... · proposal. Bank is looking for an...

Documents

Transcript of Pre-Bid Response: RFP for implementation of Mobile Banking ... · proposal. Bank is looking for an...