Objectives of the Selection Process

Identification of Qualified Providers

Evaluation and Selection

Negotiating the Contract

Summary

Appendix

Requests for Proposal (RFP) - Definition and Overview

The Process

A Typical RFP Format

This brochure suggests techniques that can facilitate the process by which financial institutions conduct due diligence and select the best service provider.

In some situations, the bank will either already know or quickly be able to determine a "short list" of provider candidates. This may occur when a specialized service is offered by a small number of providers, when size or geographic location is important, or when existing relationships with other providers (e.g., the bank’s core data processor) are critical factors. If the bank has already identified possible providers and does not seek to expand the pool of candidates, management can proceed to evaluation and contract negotiation.

However, when the bank seeks to create or expand a list of possible service providers, it may be helpful to use tools and techniques such as Requests for Proposal (RFP), Requests for Information (RFI), and Requests for Quote (RFQ). These are ways to obtain specific information about a service provider’s ability to meet the bank’s requirements and the fees that they charge for the service. In an RFP, the bank outlines its business objectives and technical requirements and solicits responses from service providers that describe their ability to meet these needs and related prices. A more detailed discussion of the RFP process is provided in the Appendix. The RFI and RFQ are respectively targeted at obtaining specific information about the technical solutions that are available and prices charged for a particular service.

In initial communications with service provider candidates, the bank should want to make clear that: (1) the service provider cannot disclose any information about the bank’s systems or its business plans to others outside the candidate’s team; (2) the service provider expects that commitments made during the selection process will be binding in any final agreement; and (3) the service provider identify all subcontractors, consultants, or third parties on which it is relying to provide services to the bank.

The evaluation criteria are essential to the selection process and allow the financial institution to methodically review the candidates’ proposals. The overriding objective is to select the most qualified provider. Utilizing standard evaluation criteria assists in this selection effort. Some suggested evaluation criteria are:

• Compatibility of the service provider’s vision/value proposition with that of the bank.
• Ability to execute the vision/value proposition.
• Functionality of the service or system proposed. (Do the functional features meet the stated requirements?)
• Technology in terms of type, power, modularity, and ability to upgrade/refresh or scale.
• Service and support in terms of maintenance hours, response time, resolution time, security, disaster planning, and other service levels.
• Cost/Price.
• Financial stability of the vendor.

• Be specific in all requests for information from candidates. Prioritize the requested information and indicate minimums and maximums for the length of response. A useful rule of thumb is that "You get what you ask for."
• Consider using numerical scores based on quality ranking factors. By using consistent scoring systems or metrics, objective evaluation standards can be applied. Make sure the quality ranking factors are aimed at achieving the bank’s goal.
• Determine minimum acceptable scores for the criteria used before rating the bids. Narrow the list of proposals by eliminating bids that do not meet the required minimums.
• Document the evaluation process and methodology used to score the respective proposals. It is generally a good practice to document requirements and priorities before starting the evaluation stage of a project.
• Consider conducting meetings and/or oral presentations where service providers can respond to questions and provide additional information.
• Consider ways to keep the process manageable. Depending on the complexity of the outsourced activity, the evaluation process can be time consuming and resource intensive.
• When working with a larger list of prospective candidates, narrow the group to a small number (e.g., two or three) to solicit "best and final" offers.

After the selection process has narrowed the choice to one or a small number of strong candidates, negotiations with the provider(s) can help the bank finalize the terms of the contract. The negotiation process can help the bank establish terms that are agreeable to all parties and confirm that there is common understanding of the roles and responsibilities. Direct communication with the provider may help to determine whether organizational cultures are compatible and may provide an opportunity to interact with personnel who will play a key role in the future relationship.

Negotiating a contract is the final step in the procurement process. If a Request for Proposal was used or a Statement of Work was provided to the candidates to solicit their proposals, these documents can be directly incorporated into the contract. Key terms and conditions, as well as technical solutions and pricing, are generally established based on the proposal responses and final offers. A few points that might be useful in the contract negotiation and approval phases follow:

• As a general industry practice, information technology contracts are commonly set for a three- to five-year term. The shorter term enables the institution to reflect the pace of change in the technology industry.
• Prices indicated in the contract and service provider’s proposal can be more effectively considered when they are broken down by each category of service (workspace, network services, etc.) and for the technology services by platform group.
• It is useful to explicitly state all charges as part of the invoicing procedures, occupancy policy, communication protocols, additional test time, and annual increases. Specifying each additional increment of cost is important in order to minimize the financial risk of increased prices for additional or reduced workload.
• Many contracts contain exit clauses that allow the institution to cancel the contract for reasons such as a failure to perform.
• Service level agreements should be stated in the contract. (Further information on service level agreements is provided in a separate FDIC document on technology outsourcing.)
• Having a clear understanding of the current and anticipated future requirements of the outsourced service can allow the bank to obtain a long-term solution rather than a quick fix.
• Set a realistic time line for completing the contract negotiation process.
• Obtain a list of all key personnel and a list of any subcontractors, consultants, or third parties on which service delivery depends.

The final outcome of the process should be the selection of a viable service provider that meets the procurement needs and objectives of the bank. Undertaking this commitment can provide significant benefits for complex information technology services or projects. Benefits include, but are not limited to, focusing the bank on the objective and strategic fit of the procurement, as well as facilitating due diligence in the selection of a service provider.

APPENDIX

• Determine the purpose and goal of the procurement.
• Assign a proposal project team and an evaluation team.
• Plan the outsourcing project in terms of cost schedule, functional requirements, and resource requirements.
• Develop a "baseline" that represents a current "as is" description of the affected environment in terms of current cost, inventory of systems, and services.
• Develop a "needs assessment" which describes management’s assumptions on how to more effectively serve its customers.
• Determine the future requirements by analyzing anticipated needs and project objectives.
• Determine the disparity between the current environment and the future requirements in order to identify the gaps that need to be filled to get from the current environment to the desired environment.

Proposal Preparation:

• Develop the Statement of Work, a technical document that outlines basic requirements.
• Draft the RFP based on the contents of the Statement of Work.

• Executive summary.
• Introduction:
  • Background on the financial institution and/or business division
  • Scope of services being requested, (e.g., web hosting, infrastructure outsourcing, disaster recovery, etc.).
  • Background on the business process, including current status, existing roles, and responsibilities of the people who will be working with the vendor.
  • Statement on the confidentiality of information.
• Overview:
• Statement of mission/vision of the financial institution.
• Statement of business objectives the institution wants to achieve.
• Statement of scope in terms of which business functions, business units, applications, packages, geographies, and technology platforms are being covered by the RFP.
• Role of the service provider.
• Project schedule:
• Service provider RFP question deadline.
• Service provider analysis meeting (optional).
• Proposal due date. (Generally, according to industry practices, service providers need four weeks to respond comprehensively to anything other than simple configurations. Less time may result in poorer, less innovative and probably costlier solutions.)
• Service provider demonstration day.
• Contract negotiation.
• Final decision.
• Proposed implementation start date.
• Statement of Work:
• Detailed technical requirements, describing the required business applications and their functionality, as well as the hardware and infrastructure platform and communications requirements for each outsourced area and operational configuration.
• Transition, implementation, training, start-up, maintenance, and security requirements.
• Performance criteria for success of solution.
• Project management and service level reporting requirements.
• Indication of performance/service level incentives and penalties.

Return to Introduction | Return to Bank Technology Bulletins