01._RFP Solicitation.pdf

1300 East Main Street

Richmond, Virginia 23219

This public body does not discriminate against faith-based organizations or against an Offeror because of race, religion, color, sex, sexual orientation, gender identity, national origin, age, disability, or any other basis prohibited by state law relating to discrimination in employment.

REQUEST FOR PROPOSALS (RFP) SCC-26-018-BFI

For

Short-Term Lending Database

Issue Date: October 20, 2026

Due Date/Time: November 20, 2026, at 2:00 PM ET

Single Point of Contact (SPOC): Kendra J. Briscoe

E-mail Address: kendra.briscoe@scc.virginia.gov mailto:kendra.briscoe@scc.virginia.gov

RFP SCC-26-018-BFI – Short-Term Lending Database

Table of Contents

1.0 Introduction

1.1 Purpose, Subcontracting, and Limitation

1.2 Single Point of Contact (SPOC)

1.3 Timeline

1.4 Offeror Questions and Answers

1.5 Period of Contract

1.6 Optional Pre-proposal Conference

2.0 Background

2.1 SCC Overview

2.2 Bureau of Financial Institutions

2.3 Current State

2.3.1 Short-Term Lending in Virginia

2.3.2 The Database

2.3.3 Statutory and Other References

Current information on short-term lending database fees can be found at the following links:

3.0 Statement of Needs

3.1 Statement of Needs

3.1.1 Short-Term Loan Database System Roles

4.0 Proposal Format and Submission Instructions

4.1 Overview

4.2 Proprietary Information

4.3 Proposal Format and Content

4.4 Proposal Submission

4.4.1 Electronic Sealed Response

4.4.2 Submission via eVA

5.0 Evaluation and Award Criteria

5.1 Evaluation Process

5.2 Evaluation Criteria

5.3 Solution and Product Demonstrations

5.4 Additional Offeror Information

5.5 Announcement of Award

5.6 Excluded Parties List

Appendices to the RFP

Appendix A: Offeror Profile

Appendix B: Offeror Proprietary Information Form

Appendix C: Authorization to Transact Business in the Commonwealth of Virginia (SCC Form)

Appendix D: Proposed Changes

RFP Exhibits

Exhibit A: Services Agreement

Exhibit B: Solution Requirements

Exhibit C: Solution Description

Exhibit D: Service Level Agreement

Exhibit E: Deliverables

Exhibit F: Proposed Fee & Cost Analysis

Exhibit G: Subcontracting Plan

Attachments are used to provide additional information about the current state, needs, and requirements of the SCC. Attachments are supplemental to the RFP document and for reference purposes only.

Appendices are used to capture information about the Offeror’s company or its proposal. Appendices are primarily administrative documents that may be used to inform aspects of SCC’s review and evaluation of Offeror proposals.

Exhibits are used to capture details about the Offeror’s proposed solution and its approach to achieving the SCC’s requirements. Exhibits are the primary focus of SCC’s proposal review and evaluation efforts. Exhibits are incorporated as formal components of the contract between SCC and the selected Supplier.

1.0 Introduction

1.1 Purpose, Subcontracting, and Limitation

The purpose of this Request for Proposals (RFP) is to solicit sealed proposals to establish a contract through competitive negotiations with a qualified source to provide a short-term lending database solution (the “Database”) that is Internet-accessible on a real-time basis by all Virginia short-term lending licensees (the “Licensees”) and State Corporation Commission (the “SCC”) through its Bureau of Financial Institutions (the “Bureau”).

The SCC intends to award a single contract to one Offeror that will provide a comprehensive solution meeting the requirements found in Exhibit B: Solution Requirements. The contract will be awarded only to one Offeror that is organized as a single entity. That Offeror will be solely responsible for the successful delivery and operation of all components of the comprehensive solution.

Throughout this RFP and its appendices, attachments, and exhibits, the term “Solution” should be understood to encompass the full range of components – technology, plans, deliverables, services, etc. – needed to satisfy the SCC’s requirements and achieve the SCC’s objectives.

Subcontracting: Offerors may choose to enter into subcontracting and other relationships with qualified parties to provide the highest quality of goods and services that meet the full scope of the Solution requirements in an efficient and cost-effective manner. In all such cases, only the prime contractor will be a party to the awarded contract. While the prime contractor must perform core functions of the Solution, there is no requirement that the prime contractor perform a specific percentage of the services.

For the purposes of this RFP, “Offeror” means any entity that submits a proposal in response to this RFP (Offeror includes potential Offerors). “Supplier” means the Offeror selected to receive an award of a contract.

1.2 Single Point of Contact (SPOC)

Submit all inquiries concerning this RFP in writing by email, subject: “RFP # SCC-26-018-BFI” to:

SPOC: Kendra J. Briscoe

Email: kendra.briscoe@scc.virginia.gov

Offerors must limit all contact, whether oral or written, pertaining to this RFP to the designated SPOC for the duration of this procurement process. Failure to do so may jeopardize further consideration of an Offeror’s proposal.

1.3 Timeline

The timetable below is provided for planning purposes only.

mailto:kendra.briscoe@scc.virginia.gov

Activity Target Completion Date

RFP Posted to eVA 10/20/2026

Deadline to Register for Pre-proposal Conference 10/25/2026 at 1:00 PM ET

Pre-proposal Conference (optional) 10/26/2026 at 1:00 PM ET

Deadline for Offeror Questions Prior to Proposal Submission* 11/06/2026 at 5:00 PM ET

Proposals Due 11/20/2026 at 2:00 PM ET

Project Start Date (estimated) ** 12/1/2026

Table 1 – Timeline of Events

* Offerors should visit the solicitation on the eVA VBO frequently for answers to questions. Answers to questions received by the above deadline will be posted to the VBO by 11/12/2026 and will not be distributed by the SCC in any other manner. Answers to questions received after the above deadline will be posted to the VBO at the discretion of the SCC and will not be distributed by the SCC in any other manner.

** Project Start Date is an estimated date provided for the purpose of developing standard schedules across Offerors’ responses. The contract will start at an agreed upon date, after it is approved and signed by the SCC and the selected Supplier.

1.4 Offeror Questions and Answers

All questions and requests for clarification of the RFP should be submitted to the SPOC at the contact email address provided in section 1.2 SPOC no later than November 6, 2026, at 5:00 PM ET. The SPOC, in her sole discretion, may not respond to questions or requests for clarification received after that date.

SCC reserves the right to hold internet-based audio or video calls with potential Offerors if it determines live calls will assist in clarifying the requirements of the solicitation. If these audio or video calls are held, they will be open to all potential Offerors. Notice of audio or video calls will be posted to eVA in advance.

1.5 Period of Contract

The initial period of a contract resulting from this RFP is anticipated to be for approximately two (2) years with the option for SCC to exercise three (3) successive renewals of up to two (2) years each.

1.6 Optional Pre-proposal Conference

There will be an optional virtual pre-proposal conference held on the date specified in Table 1. The pre-proposal conference is open to all interested Offerors, and you are encouraged to attend. There will be no opportunity for a private or individual presentation.

To participate in the pre-proposal conference, register by sending an email to the SPOC stating your firm’s name, participating representative(s), and the email address for the representative(s). Offeror will then receive the conference information to virtually attend the conference. It is strongly recommended that you register no later than the date and time specified in Table 1 to ensure registration is confirmed.

2.0 Background

This section presents background information on the current environment and contains technical and other information that may be helpful for Offerors in preparing proposal responses. The contents of this section are not intended to set forth requirements but rather are intended to assist Offerors to gain a general understanding of the business context of the requirements. Detailed requirements are included in Exhibit B:

Solution Requirements.

2.1 SCC Overview

The SCC exercises regulatory authority over many business and economic interests in Virginia, including public utilities, insurance, state-chartered financial institutions, securities, retail franchising, and railroads. It is organized as a separate department of government with delegated administrative, legislative, and judicial powers.

Headquartered in downtown Richmond, Virginia, the SCC is near the State Capitol and adjacent to Richmond’s financial and commerce center.

2.2 Bureau of Financial Institutions

The Bureau is a regulatory division of the SCC. This division is involved in consumer protection through administration of state laws regarding depository and non-depository financial institutions.

Depository financial institutions are comprised of Virginia-chartered banks and related holding companies, savings institutions and related holding companies, and credit unions. Non-depository institutions consist of trust companies, consumer finance companies, mortgage lenders and brokers, money transmitters, credit counseling agencies, motor vehicle title lenders, industrial loan associations, short-term lenders, check cashers, student loan servicers, and debt settlement services providers. Each institution is required to obtain a certificate of authority or a license prior to engaging in business with the exception of check cashers and sales-based financing providers. Check cashers and sales-based financing providers are required to register with the Bureau.

The Bureau also investigates and responds to consumer complaints. In addition to written complaints, the staff responds to thousands of telephone inquiries. The Bureau also has an outreach program for the purpose of improving the financial literacy of Virginians.

2.3 Current State

2.3.1 Short-Term Lending in Virginia

Section 6.2-1800 et seq. (formerly § 6.1-444 et seq.) of the Code of Virginia was enacted by the Virginia General Assembly on July 1, 2002. Regulatory changes that took effect January 1, 2009, prompted substantial changes to the small-dollar lending market in Virginia. These regulations expanded data-reporting requirements, imposed new rules on loan terms, introduced mandatory use of the statewide payday-lending database, restricted database access, and tightened compliance obligations around extended payment plans, prepayment rules, fee posting, and protections for military borrowers. These measures increased operational complexity and reduced flexibility for Licensees, causing an early decline in market participation as smaller operators struggled to absorb rising compliance costs and newly constrained loan structures.

In 2020, Virginia enacted sweeping reforms through the Fairness in Lending Act. These changes fundamentally reshaped the industry by replacing the payday-loan model with tightly regulated short-term loans subject to a 36% interest cap, strict fee limitations, mandatory income verification, longer minimum loan durations, expanded borrower protections, and uniform rules applied across Licensees. The legislation eliminated balloon-payment structures and closed loopholes that previously allowed high-cost lending under open-end credit provisions. Collectively, these reforms effectively transformed the market, causing further decline in the number of Licensees.

In 2015, Virginia had 18 licensed Licensees with 191 offices statewide, and these Licensees made 352,385 loans that year. In 2025, 5 Licensees operated 20 offices statewide, but only 3 of those Licensees were active, generating a total of 16,205 loans during this period.

2.3.2 The Database

The current Database contract was awarded in 2018. The SCC certifies and oversees the real-time, Internet-accessible short-term lending database under § 6.2-1810 of the Code of Virginia. As required by subdivision B 4 of § 6.2-1810 of the Code of Virginia, Licensees, not the SCC or taxpayers, are responsible for paying the inquiry fee to the Database provider for each short-term loan consummated, remitting those fees weekly. The cost of the Database is funded through these inquiry fees, and no funding or fees are provided by the SCC or taxpayers. The current contract expires on March 13, 2027. SCC desires a solution that is ready for go-live on March 14, 2027.

2.3.3 Statutory and Other References

Database requirements can be found at the following links:

2.3.3.1 Code of Virginia § 6.2-1810. Loan database:

https://law.lis.virginia.gov/vacode/title6.2/chapter18/section6.2-1810/

2.3.3.2 10 VAC 5-200-110. Short-term lending database:

https://law.lis.virginia.gov/admincode/title10/agency5/chapter200/section110/

2.3.3.3 10 VAC 5-200-113. Limited disclosure of data from short-term lending database: 10VAC5-200-113.

Limited disclosure of data from short-term lending database.

Current information on short-term lending database fees can be found at the following links:

2.3.3.4 10 VAC 5-200-115. Database inquiry fee: 10VAC5-200-115. Database inquiry fee.

2.3.3.5 Order Modifying Database Inquiry Fee (Case No. BFI-2025-00021):

https://www.scc.virginia.gov/docketsearch/DOCS/85%24z01!.PDF

3.0 Statement of Needs

3.1 Statement of Needs

The SCC requires a comprehensive, Internet-accessible Database that will be accessible on a real-time basis by all Licensees and the SCC through the Bureau. The Supplier shall ensure the proposed Database meets SCC’s functional, technical, security, and audit requirements.

The Supplier’s compensation is based on a per consummated loan basis through database inquiry fees paid entirely by Licensees pursuant to § 6.2-1810 B 4 of the Code of Virginia and 10 VAC 5-200-115.

3.1.1 Short-Term Loan Database System Roles

Expected system user roles are as follows:

3.1.1.1 Administrator User

Administrator User means BFI or other SCC users who shall have the ability to create, remove, and modify user accounts, and to assign or update user roles, including granting Administrator privileges. Agency users shall https://law.lis.virginia.gov/vacode/title6.2/chapter18/section6.2-1810/ https://law.lis.virginia.gov/admincode/title10/agency5/chapter200/section110/ https://law.lis.virginia.gov/admincode/title10/agency5/chapter200/section113/ https://law.lis.virginia.gov/admincode/title10/agency5/chapter200/section113/ https://law.lis.virginia.gov/admincode/title10/agency5/chapter200/section115/ https://www.scc.virginia.gov/docketsearch/DOCS/85%24z01!.PDF have access to all data stored within the system and the capability to generate or run reports. Initial Agency access must be provisioned directly by the third-party service provider.

3.1.1.2 Agency User

Agency User means BFI or other SCC users who shall have access to the data stored in the system and the ability to generate or run reports. Agency users shall not have the capability to create, remove, or modify user accounts.

3.1.1.3 Licensee Administrator

Licensee Administrator means Licensee personnel who shall have the ability to create, remove, and modify user accounts, and to assign or update user roles, including granting Administrator privileges to its own Licensee personnel. Administrators shall also be authorized to transmit data to the system and correct data within the system. Initial Administrator access must be provisioned directly by the third-party service provider.

3.1.1.4 Licensee User

Licensee User means personnel of the Licensee who shall have the ability to transmit data to the system.

4.0 Proposal Format and Submission Instructions

4.1 Overview

The issuance of this document and the receipt of information in response to this document will not cause the SCC to incur any liability or obligation, financial or otherwise, to any Offeror. The SCC assumes no obligation to reimburse or in any way compensate an Offeror for expenses incurred in connection with its proposal.

4.2 Proprietary Information

In general, proposals are not subject to public disclosure prior to the award of a contract, except as required by law or by court order.

If Offeror seeks to protect from disclosure any proprietary or trade secret information contained in its proposal, Offeror must:

a. Submit a completed Appendix B: Offeror Proprietary Information with its proposal, which lists proprietary information and the reason it deems such information proprietary. Offeror may not designate its entire proposal as proprietary or confidential. FAILURE TO COMPLETE APPENDIX B MAY

RESULT IN PUBLIC DISCLOSURE OF ALL PROPOSAL INFORMATION.

b. Submit both Original and Redacted electronic copies of those specific documents that contain proprietary information. Redacted copies of proposal documents must be consistent with the requirements of this RFP and Appendix B. IT IS OFFEROR’S SOLE RESPONSIBILITY TO REMOVE ANY

PROPRIETARY INFORMATION, DATA, OR MATERIAL IN REDACTED COPIES OF ITS PROPOSAL

DOCUMENTS. The SCC assumes no responsibility for release of proprietary information contained in Redacted proposal documents. A second, redacted copy is not required for those proposal documents that do not contain proprietary information.

4.3 Proposal Format and Content

The SCC may reject any proposal that is not in the required format or that does not address all requirements of this RFP.

Proposals should be written specifically to answer this RFP. General “sales” material should not be used. It is essential that the proposal be thorough and concise. Avoid broad, unenforceable, or immeasurable responses and include all requested information in each section as indicated below.

The required contents of the proposal and how the proposal must be organized are detailed in Table 2 – Proposal Format & Content. All documents that must be included in the proposal have been provided by the SCC except documents noted as “Offeror to Provide.” Unless specifically noted, no other documents or information should be included in the proposal. Proposal document formats are as follows:

• Template: Structured documents prepared by the SCC that must be populated and submitted by the Offeror. Each template includes instructions describing how to complete that template.

• Proposed Changes Form: Offeror is required to submit proposed changes and edits to Exhibits to this RFP, if any, using the forms provided in Appendix D: Proposed Changes Form. Pre-defined forms have been developed that correspond to each Exhibit to this RFP. Offeror should not provide proposed edits or redline changes directly in the Exhibits. Additional instructions are provided in Appendix D.

• Offeror to Provide: Documents to be provided by and included in Offeror’s response in accordance with the SCC’s instructions.

Note that, in some instances, elements of Offeror’s proposal will require responses using multiple proposal document formats.

Document

Name Document Title Content to be Included

Response Format

Required File Name 1,2

1a Transmittal Cover Page Completed cover page signed by an authorized representative of the Offeror.

• Cover Page

Template

(Word or

PDF)

[Company] – Cover

Page.docx or

[Company] – Cover Page.PDF

1b Transmittal Addenda Copies of all RFP Addenda signed by an authorized representative of the

Offeror, as applicable.

• Addenda

Template

(Word)

[Company] – [Addendum

#].docx

2 Offeror

Profile

Appendix A: Offeror

Profile

Offeror’s response to the items set forth in Appendix A, including overview of Offeror, Offeror references, resumes, and financial documentation.

• Appendix A

Template

(Word)

[Company] – Appendix A.

Offeror Profile.docx

3 Proprietary

Info Form

Appendix B: Offeror

Proprietary Form

Indicate specific information contained in the proposal that

Offeror deems proprietary.

• Appendix B

Template

(Word)

[Company] – Appendix B.

Proprietary Info Form.docx

4 SCC Form Appendix C:

Authorization to

Transact Business in the Commonwealth of

Virginia

Indicate applicable status regarding

Offeror’s authorization to transact business in the Commonwealth of

Virginia.

• Appendix C

Template

(Word)

[Company] – Appendix C.

SCC Form.docx

5 Proposed

Changes

Appendix D: Proposed

Changes

Submit proposed changes to content and language contained in the

Exhibits to this RFP using the

• Appendix D

Template

(Word)

[Company] – Appendix D.

Proposed Changes.docx

Name Document Title Content to be Included

Response Format

Required File Name 1,2 appropriate forms provided in

Appendix D: Proposed Changes.

6 Exhibit A Exhibit A: Services

Agreement

Proposed changes to Exhibit A:

Services Agreement must be submitted in the appropriate form provided in Appendix D.

• Appendix D

Template

(Word)

N/A – to be included in response to Appendix D

7 Exhibit B Exhibit B: Solution

Requirements

Provide Offeror’s response to each item set forth in Exhibit B: Solution

Requirements. Responses must be captured directly in the MS Excel template provided in accordance with the SCC’s instructions. Specific changes Offeror wishes to propose to items in Exhibit B: Solution

Requirements must be submitted in the appropriate form provided in

Appendix D.

• Exhibit B

Template

(Excel)

• Appendix D

Template

(Word)

[Company] – Exhibit B.

Solution Requirements.xlsx

8 Exhibit C Exhibit C: Solution

Description

Provide Offeror’s response to each item set forth in Exhibit C: Solution

Description. Responses must be captured directly in the MS Word template provided in accordance with the SCC’s instructions.

• Exhibit C

Template

(Word)

[Company] – Exhibit C.

Solution Description.docx

9 Exhibit D Exhibit D: Service

Level Agreement

Provide Offeror’s proposed metrics and performance standards for each service level item.

Responses must be captured directly in the MS Excel template provided in accordance with the SCC’s instructions. Specific changes Offeror wishes to propose to items in Exhibit

D: Service Level Agreement must be submitted in the appropriate form provided in Appendix D.

• Exhibit D

Template

(Excel)

• Appendix D

Template

(Word)

[Company] – Exhibit D.

Service Level.xlsx

10 Exhibit E Exhibit E: Deliverables Provide Offeror’s responses to the information requested by the SCC.

Specific changes Offeror wishes to propose to items in Exhibit E:

Deliverables must be submitted in the appropriate form provided in

Appendix D.

• Exhibit E

Template

(Word)

• Appendix D

Template

(Word)

[Company] – Exhibit E.

Deliverables.docx

12 Exhibit F Exhibit F: Proposed

Fee & Cost Analysis

Provide a detailed itemization of all direct and indirect costs associated

• Exhibit F

Template

(Word)

[Company] – Exhibit F.

Proposed Fee and CA.docx

Name Document Title Content to be Included

Response Format

Required File Name 1,2 with the Database including, but not limited to labor categories, labor hours, rates, materials, software, licensing, hosting, equipment, subcontractor costs, travel, overhead, general and administrative costs, and any other applicable cost components. Provide Offeror’s detailed price proposal as specified in

Exhibit F: Proposed Fee & Cost

Analysis. Do not include pricing data in any other section of the proposal.

13 Exhibit G Exhibit G:

Subcontracting Plan

Indicate Offeror’s and subcontractor(s) DSBSD SWaM certification information and subcontracting plan, as applicable.

Include copy(ies) of DSBSD certification(s), as applicable.

• Exhibit G

Template

(Word)

[Company] – Exhibit G.

Subcontracting Plan.docx

Table 2 – Proposal Format & Content

Notes: Table 2 – Proposal Format & Content

1. All proposal documents should be submitted using the file naming conventions provided. Offerors should replace “[Company]” with their company name. For example:

• Acme Co. – Addendum 1.docx

• Acme Co. – Appendix A. Offeror Profile.docx

• Acme Co. – Exhibit B. Solution Requirements.xlsx

• Acme Co. – Exhibit C. Solution Description.docx

2. Redacted copies of proposal documents should be submitted using the file naming conventions provided with the addition of “Redacted” at the end. For example:

• Acme Co. – Appendix A. Offeror Profile – Redacted.docx

• Acme Co. – Exhibit C. Solution Description – Redacted.docx

4.4 Proposal Submission

4.4.1 Electronic Sealed Response

This RFP is an invitation for an electronic sealed response. Proposals will be received until the closing date and time provided in the solicitation. Any proposal received after the closing date and time specified in the solicitation WILL NOT be considered.

Prior to the due date, Offerors should:

a. Check the status of the solicitation on eVA at eva.virginia.gov by clicking on Business Opportunities and then click on Virginia Business Opportunities (VBO) for any updates, changes, amendments, cancellations, etc.;

b. Check the “Reminders” section in VBO for all attachments and documents to be completed and submitted; and

c. Complete all attachments, amendments, exhibits, product information, etc. and include electronically with the Offeror’s electronic submission.

Offerors are solely responsible for reviewing, complying, and returning a complete proposal. Changes to the solicitation’s forms and formats are prohibited except where clearly instructed and permitted.

4.4.2 Submission via eVA

The SCC requires that an Offeror submit its proposal electronically through eVA. Offerors must be registered in eVA in order to submit an electronic response. Offerors must submit one complete copy of the response including all appendices and exhibits.

Instructions for submitting electronic proposals can be found at www.eva.virginia.gov.

If an Offeror needs assistance submitting an electronic response, the Offeror must contact eVA Customer Care at 866-289-7367 or https://eva.virginia.gov/get-help-customer-care.html.

5.0 Evaluation and Award Criteria

5.1 Evaluation Process

The SCC will only consider proposals received by the due date and time. All proposals received after the due date and time will be returned to the Offeror and receive no further consideration. Failure to meet other submission requirements in this RFP may result in the rejection and return of the proposal, or in a request from the SPOC to immediately remedy the deficiency, all in the sole discretion of the SPOC. Failure of a proposal to meet functional or technical requirements in an Offeror’s proposed solution will be considered in the evaluation and scoring process. Additions, deletions, and changes to functional, technical, and other solution requirements may be requested and negotiated by the SCC during negotiations with individual Offerors based on their respective solution and proposal.

Each Offeror’s proposal received in response to this RFP, subject to the above paragraph, will be evaluated based on the submitted materials in accordance with some or all of the Evaluation Criteria in Section 5.2 below. Based on that evaluation, the SCC will then select the Offeror(s) for negotiations. Negotiations may include requests that Offeror(s) clarify or explain certain aspects of their proposals.

At any point in the negotiation process, the SCC may employ the following means of continued evaluation:

• Reviewing industry research

• Offeror presentations

• Site visits

• Contacting Offeror's references

• Product demonstrations

• Sandbox testing

• Review of sample code

• Review of pricing

• Contacting Offeror’s customers

• Interviewing key personnel

• Requesting that Offerors elaborate on or clarify specific portions of their proposal

• Security audit compliance documentation

SCC may limit all of the above to the most qualified proposals. No Offeror is guaranteed an opportunity to explain, supplement or amend its initial proposal. Offerors should submit their best proposals and not assume there will be an opportunity to negotiate, amend or clarify any aspect of their initially submitted proposal.

Therefore, each Offeror is encouraged to ensure that its initial proposal contains and represents its best http://www.eva.virginia.gov/ https://eva.virginia.gov/get-help-customer-care.html offering.

SCC will then select one or more Offerors which, in its opinion, has made the best proposal, and will award the contract to that Offeror(s). The selection of an Offeror to receive an award may be based on factors outside the numerical Evaluation Criteria in section 5.2 below.

The SCC may cancel this Request for Proposals or reject proposals at any time prior to an award and is not required to furnish a statement of the reason(s) why a particular proposal was not deemed to be the most advantageous.

SCC SHALL NOT BE CONTRACTUALLY BOUND TO ANY OFFEROR PRIOR TO THE EXECUTION OF A DEFINITIVE

WRITTEN CONTRACT.

5.2 Evaluation Criteria

Proposals will be evaluated using the criteria contained in Table 3 – Evaluation Criteria.

Evaluation Criteria

1 Technical Response and Proposed Solution

2 Implementation Approach

3 Supplier Profile and Experience

4 Supplier Procurement and Subcontracting Plan

5 Total Cost Analysis

Table 3 – Evaluation Criteria

5.3 Solution and Product Demonstrations

Offerors may be required to give a product demonstration to SCC. SCC will schedule the time and location of product demonstrations. Product demonstrations are an option of SCC.

The SCC may request access to a working or test environment of all or part of the proposed solution for a minimum of ten (10) Business Days to perform hands-on experimentation and testing of the proposed solution to further evaluate its functionality. The Offeror must provide personnel who are highly knowledgeable of the product to assist the SCC during this hands-on experimentation period.

5.4 Additional Offeror Information

Offerors may be asked at any time to provide additional information beyond what is required in this RFP to assist the SCC in assessing the organizational, operational, or financial stability, viability, and capabilities of the Offeror or its subcontractors and affiliates. Offerors agree to provide the SCC with additional information as requested.

5.5 Announcement of Award

Announcement of the decision to award a contract will be posted on the DGS/DPS eVA web site (http://www.eva.virginia.gov). Any final contract, proposed fee and cost analysis, awarded as a result of this RFP shall be made available for public inspection.

http://www.eva.virginia.gov/

5.6 Excluded Parties List

No Offeror, its affiliates or subcontractors may be awarded a contract if excluded based on the Commonwealth of Virginia’s Debarment List as provided by the Code of Virginia §2.2-4321 at the time of award.