2-SLCI26089.docx

Salt Lake City Corporation Request for Proposals, RFP No. SLCI26089 Customer Identity Verification and Credit Check Services Department of Public Utilities

I. REQUEST FOR PROPOSALS (RFP) OVERVIEW

Issued By: Salt Lake City Corporation, Purchasing Division Salt Lake City Corporation (the "City") is soliciting competitive sealed proposals from qualified offerors to provide customer identity verification and credit check services.

The City’s procurement processes, including this competitive solicitation, are governed by Salt Lake City Code Chapter 3.24 and Salt Lake City Administrative Rules for Procurement Article 53-1A.

Issue Date: Date stated in U3P posting

Question Due Date: Date stated in U3P posting

Close Date: Date stated in U3P posting

Purpose of this Solicitation The purpose of this RFP is to competitively select an offeror (Offeror or Offerors) to enter into a contract with City to provide customer identity verification and credit check services.

It is anticipated that this RFP will result in a single contract award to the responsive and responsible Offeror with the highest score justified by the procurement code.

Background The City intends to select an Offeror to provide an automated identity verification solution for integration into the Department of Public Utilities (DPU) Customer Information System (CIS) as part of their Systems and Software enQuesta v6 implementation. The CIS includes an online customer self service portal through which customers can sign up for utility, garbage, streetlighting and other services. Customers can also view and pay their account balances. The Offeror’s proposed solution shall include consumer credit reports and identify verification using the customer’s social security number, state issued identification, driver’s license, or other federal or state issued identification. The proposed solution must also include providing a risk model for initial customer setup to help determine the need for a security deposit, identify confirmation, and fraud detection.

DPU is responsible for establishing and maintaining utility accounts for approximately 89,000 customers. DPU strives to provide a high quality, low stress customer experience to customers during their application for services. This process involves two separate but essential processes:

New customers are asked to provide a social security number or other government issued form of identification. This information, along with their name, is entered into the CIS. DPU staff then verifies a customer’s identity prior to establishing services by directly accessing a 3rd party firm’s secure service and/or API. This site provides for both identity verification and information to assist in the decision regarding the need for a utility deposit.

DPU processed the following number of accounts over the past twelve months:

Term The contract resulting from this RFP will be from the effective date of the Agreement through February 19, 2034.

RFP Contents RFP document (this document) Attachment 1: Sample Agreement Attachment 2: Cost Sheet Attachment 3: Score Sheet All proposals submitted in response to this RFP MUST be submitted electronically through the Utah Public Procurement Place (U3P) website as detailed in Section III, Proposal Submission, below.

Proposal Submission Deadline: The deadline is the date and time listed in U3P. The upload of all proposal documents MUST be fully complete by the date and time deadline or the proposal will not be accepted.

NO LATE PROPOSALS WILL BE ACCEPTED.

II. GENERAL INFORMATION

a. Sample Agreement. Any contract resulting from this RFP will include, but not be limited to, the Sample Agreement (Attachment 1). Exceptions and/or additions to the Sample Agreement are strongly discouraged. For more information regarding exceptions, please see Section III, Proposal Submission, below.

b. Insurance Requirements. Offerors should review the required insurance coverage and notice of policy cancellation requirements that will be part of the resulting contract(s). Such insurance information is provided under Paragraph 5 of the Sample Agreement (Attachment 1). Proposed pricing must include associated insurance costs. The selected Offeror will be required to provide insurance certificates meeting all requirements at the time of notification of conditional selection.

For insurance policies listed in Paragraph 5 that require Offeror to include Salt Lake City Corporation as an additional insured, you will be required to have the policy endorsed to provide either 30-days “Notice of Cancellation to a Third Party” or 30-days “Notice of Material Change to a Third Party.” A copy of the endorsement must be provided with the Certificate of Insurance. (Note: Either endorsement may be conditioned to allow 10-days notice if the reason for the cancellation is non-payment of premiums).

c. The selected Offeror must be registered with the following websites prior to signing the Agreement.

i. Business Registration with the State of Utah: www.corporations.utah.gov

ii. System for Award Management: Sam.gov

iii. E-Verify: https://www.e-verify.gov/e-verify-employer-search

d. Offerors or their agents are instructed not to contact selection committee members, City officials or employees, or attempt to externally manipulate or influence the procurement process in any way, other than through the instructions contained herein, from the date of release of this RFP to the date of execution of the Agreement resulting from this solicitation. City, in its sole discretion, may disqualify Offerors who violate this paragraph.

e. Offerors or their agents are instructed not to submit any gifts or promotional items with Offeror’s proposal. City employees are not allowed to accept such items regardless of their value.

f. Cost of Developing Proposals. All costs related to the preparation of the proposals and any related activities are the sole responsibility of the Offeror. The City assumes no liability for any costs incurred by Offerors throughout the entire selection process.

g. Interviews. City may establish a date and time for interviews or presentations and shall notify eligible Offerors of such date and time. Offerors invited to interviews or presentations shall be limited to those Offerors meeting the minimum requirements and minimum technical score threshold specified in the RFP. Representations made by an Offeror during interviews or presentations shall become an addendum to the Offeror's proposal and shall be documented. Representations must be consistent with the Offeror's original proposal and may only be used for purposes of clarifying or filling in gaps in the Offeror's proposal. Interviews and presentations will be at the Offeror's expense.

h. Proposal Ownership. All proposals, including attachments, supplementary materials, addenda, etc., shall become the property of the City and will not be returned to the Offeror.

i. No proposal shall be accepted from, or contract awarded to, any person, firm or corporation that is in arrears to the City upon a debt or contract or that is in default, as surety or otherwise, upon any obligation to the City, or that may be deemed irresponsible or unreliable by the City. Offerors may be required to submit satisfactory evidence that they have the necessary financial resources to perform and complete the work outlined in this RFP.

j. Proposal Submission.

Subject to any exceptions Offeror identifies pursuant to subparagraph III(2)(c), Offeror’s submission of a proposal or other offer or submission constitutes the Offeror's agreement to all of the terms, conditions and provisions of the proposal package, or other solicitation documents. By the submission of proposal or other offer or submission, the Offeror represents that the matters stated in such proposal, offer, or submission are true and correct. By submitting a proposal, offer, or submission; Offeror also acknowledges that the Offeror is willing to enter into the agreement if awarded the contract.

By submitting this proposal, the Offeror does hereby offer to perform such services on behalf of the City in the manner described and subject to the terms and conditions set forth in the attached proposal. Services will be performed at the rates set forth in said proposal.

By submitting this proposal, Offeror acknowledges that it has viewed all materials published on U3P, including any addenda to this RFP.

k. The City reserves the right to reject any or all proposals received. Furthermore, the City shall have the right to waive any informality or technical defect in proposals received when in the best interest of the City.

III. PROPOSAL SUBMISSION

a. U3P Registration and Submission

i. Registration

Registration is required for electronic submission. It is the Offeror’s responsibility to register for notification to receive any changes, corrections, question/answer documents, and addendums issued for RFP documents.

Offeror must complete a one-time registration by providing their company information through Bonfire. Click this link and select “Register” to complete the registration process.

Once registered the Offeror may go to this link: Utah Public Procurement Place (U3P), to search and select any RFP project listed, log-in, download the project documents, ask questions, confirm an intent to respond, and respond to solicitations published there. Failure to register and log-in with an intent to respond to a RFP constitutes an automatic waiver of Offeror’s right to receive a direct notification of any changes, corrections or addenda for a RFP.

ii. Submission

ELECTRONIC SUBMISSION REQUIRED. THERE IS NO OPTION TO SUBMIT A PAPER RESPONSE.

All proposals submitted in response to this RFP MUST be submitted electronically and MUST be submitted through the U3P website. The deadline for submission stated is a hard deadline. If a proposal response is not fully and completely uploaded at the stated date and time, the proposal will not be accepted by the U3P website and will not be considered.

Deadline for submission: The deadline for complete proposal submission, including all uploads is listed in U3P.

Responses through the U3P website require uploading of electronic attachments. The U3P site will accept a variety of document types, including but not limited to Word, Excel, and PDF attachments, but not all document types are necessarily compatible with the U3P website. You MAY NOT submit documents that are embedded (zip files), movies, wmp, mp3 or mp4 files or password protected files, etc. Such actions may cause your response to be deemed as “non-responsive”.

After uploading your response file, Offerors MUST go to “Submit and Finalize”and click “SUBMIT & FINALIZE MY SUBMISSION” to complete the process.

Please allow sufficient time to complete initial registration, including any online forms, and to upload documents. The solicitation will end at the closing time published. If you are in the middle of uploading your documents at the closing time, the system will stop the process and your response will not be received by the system. It is recommended that the submission process be completed the day prior to the due date, with the understanding that any subsequent changes/updates to that initial submission will still be accepted up to the due date and time for complete proposal submission.

b. Proposal Content

Upload cover sheet and response document as described below to the U3P website. Your proposal must be uploaded and the electronic submission completed by the time and date specified. Other uploaded documents such as an exceptions document, declarations of confidentiality, or other reference documents related to the primary response criteria are allowed but should be minimal. Do not include links to Offeror’s website in Offeror’s response.

DO NOT submit all pages of this RFP document with response. Include only the response sections described below:

i. Cover Sheet including the following information:

Company Name: ________________________________________________ Doing business as: [ ] an individual [ ] a partnership [ ] a corporation [ ] a limited liability company (mark appropriate box), duly organized under the laws of the State of _________________.

Name of Authorized Representative:

PRINCIPAL OFFICE ADDRESS:

Telephone:

Email Address:

Indicate if Offeror is registered with the following websites State of Utah Department of Commerce business search, Sam.gov, and E-Verify as further described in Section II.c above.

ii. Minimum Mandatory Requirements and Technical Response

When preparing proposals, Offeror shall reply to each of the minimum mandatory requirements and technical scoreable criteria in the order listed. Restate each numbered point listed below followed by Offeror’s response in full, narrative sentences and provide any requested materials.

c. Exceptions

i. Exceptions and/or additions to the Sample Agreement (Attachment 1) are strongly discouraged.

Any exceptions submitted or required acceptance of an Offeror’s terms and conditions may render the submission as non-responsive to the requirements listed. The City shall be the sole determiner of the acceptability of any exception. Exceptions shall be considered in the evaluation and the award processes.

The City may refuse to negotiate exceptions and/or additions that are determined to be excessive; that are inconsistent with similar contracts of the procurement unit; to warranties, insurance, or indemnification provisions that are necessary to protect the procurement unit after consultation with the City Attorney's Office or other applicable legal counsel; where the solicitation specifically prohibits exceptions and/or additions; or that are not in the best interest of the procurement unit.

An award resulting from this RFP is subject to successful contract terms and conditions negotiation (if required). The City may reject a proposal if execution of the Agreement by the Offeror is unduly delayed. In a multiple award, the City reserves the right to negotiate exceptions and/or additions to terms and conditions in a manner resulting in expeditious resolutions. Contracts may be executed and become effective as negotiations are completed.

ii. Offeror must provide the City’s Sample Agreement for this solicitation in Microsoft Word format with redline edits along with Offeror’s proposal as a separate and distinct document and clearly marked “Exceptions or Additions to RFP documents”. Additional terms or documents must be submitted in separate Microsoft Word documents. Offeror must also provide the name, contact information, and access to the person(s) that will be directly involved in legal negotiations.

Exceptions and/or additions submitted after the date and time deadline for receipt of proposals will not be considered.

Offerors may not submit requests for exceptions and/or additions by reference to an Offeror's website or URL. URLs provided with a proposal may result in that proposal being rejected as non-responsive.

d. Confidentiality If applicable to Offeror’s proposal submit the following:

i. A written claim of business confidentiality accompanied by a concise written statement of reasons supporting the claim of business confidentiality. Blanket claims that the entire RFP is confidential will be denied and the proposal may be considered non-responsive. (Please use the form provided with this RFP).

ii. One redacted version of the proposal for public release, with all protected business confidential information either blacked-out or removed, clearly marked as “Redacted Version”.

iii. One non-redacted version for evaluation purposes clearly marked as “Protected Business Confidential Information Included Within”.

All three of the foregoing items must be submitted concurrently with the records (with the initial proposal submission and with any other records submitted by Offeror during the evaluation process).

All responses, inquiries, and correspondence relating to this RFP and all reports, charts, displays, schedules, exhibits, and other documentation produced by the Offeror that are submitted to the City, as part of the proposal or otherwise, shall become the property of the City when received by the City and may be considered public information under applicable law. The City is subject to the disclosure requirements of the Government Records Access and Management Act, Title 63G, Chapter 2, Utah Code Annotated (GRAMA). The City generally considers proposals and all accompanying material to be public and subject to disclosure.

The City cannot guarantee that any information will be held confidential. If the Offeror makes a claim of business confidentiality, the City, upon receipt of a request for disclosure, will determine whether the material should be classified as public or nonpublic, and will notify the offeror of such determination. The Offeror is entitled under GRAMA to appeal an adverse determination. The City is not obligated to notify the Offeror of a request to see the Offeror’s proposal, and will not consider a claim of confidentiality, unless the Offeror's claim of confidentiality is made at the time of proposal submission in accordance with GRAMA.

e. Cost Proposal

Offeror must upload a completed cost proposal form through U3P. If an Offeror fails to upload a completed cost proposal form, then its proposal will be considered non-responsive and the proposal will be rejected.

Failure to submit cost or pricing data separately may result in Offeror’s proposal being judged as non-responsive and ineligible for contract award.

Offerors must not include costs or pricing data in their responses to the mandatory minimum requirements and the technical response.

VI. QUESTIONS AND CLARIFICATION

If Offerors have questions, need clarification of provisions, or think the City has omitted anything from this RFP which is necessary to a clear understanding of the work, or should it appear that various instructions are in conflict, then the Offeror shall submit questions online through the U3P website prior to the questions due date and time listed in U3P.

No interpretation of the meaning of any provision in this RFP, nor correction of any apparent ambiguity, inconsistency, error, or any other matter pertaining to this RFP shall be made to the Offeror orally. All questions requesting clarification or interpretation of any section or sections of this RFP must be submitted online through the solicitation on the U3P website prior to the date and time listed in U3P.

Questions received after the question submission date identified above may not be considered nor receive a response. If questions prompt the need for changes to the RFP document(s), the City will issue a written addendum. Any Q & A information and/or written addendums issued by the City shall be available for interested Offerors to view or download through the U3P website within a reasonable period of time following the above referenced deadline.

VII. PROPOSAL CONTENT

When preparing proposals, Offeror shall reply to each of the following minimum mandatory requirements and technical scoreable criteria in the order listed. Restate each numbered point listed below followed by Offeror’s response in full, narrative sentences and provide any requested materials. The score sheet has been attached to this RFP as Attachment 3: Score Sheet. The score sheet states the relative weight that will be given to each technical scoreable criteria.

a. Minimum Mandatory Requirements

Offerors must demonstrate the ability to meet or exceed the mandatory minimum requirements outlined below by providing a narrative point by point response, in the order listed, to each requirement.

The following mandatory minimum requirements must be met in order for a proposal to be considered responsive:

i. City Ethics Requirement. Offeror must include the following two paragraphs in Offeror’s proposal including Offeror’s own written acknowledgement that Offeror has read the first two paragraphs and agrees to comply with the terms thereof. Failure to do so will result in disqualification of Offeror.

Representation regarding ethical standards for city officers and employees and former city officers and employees. The offeror represents that it has not: (1) provided an illegal gift or payoff to a City officer or employee or former City officer or employee, or his or her relative or business entity; (2) retained any person to solicit or secure this contract upon an agreement or understanding for a commission, percentage, or brokerage or contingent fee, other than bona fide employees or bona fide commercial selling agencies for the purpose of securing business; (3) knowingly breached any of the ethical standards set forth in the City's conflict of interest ordinance, Chapter 2.44, Salt Lake City Code; or (4) knowingly influenced, and hereby promises that it will not knowingly influence, a City officer or employee or former City officer or employee to breach any of the ethical standards set forth in the City's conflict of interest ordinance, Chapter 2.44, Salt Lake City Code.

It is the City’s policy that City employees are prohibited from personally accepting gifts, incentives, or marketing or promotional items from suppliers and that suppliers shall not offer such items to City employees. Such offers from suppliers are inappropriate and may result in suspension or debarment of the supplier from the City's procurement processes.

ii. Offeror certifies that Offeror’s proposed solution must be cloud based and data must be hosted in the United States.

iii. Offeror certifies that Offeror must have successfully completed at least five (5) operational system implementations of similar or larger size and scope. Proposals must provide evidence of demonstrated successful experience in providing these services to similar industry organizations, as evidenced by client qualifications and references.

iv. Offeror shall upload all required attachments labelled as follows:

1. Attachment #2 – Cost Sheet

2. Attachment #4 - SOC 2 Report

3. Attachment #5 - Statement or Audit of Red Flag Rules compliance

4. Attachment #6 - Training Course Lists

5. Attachment #7 - Training Guides

6. Attachment #8 - Service Level Agreement

7. Attachment #9 - Release Notes

v. Offeror shall indicate if Offeror and/or Offeror’s subcontractor(s) will be using or offering GenAI technology, model(s), service(s), or system(s)s.

1. If yes, provide the following information below details regarding the GenAI system(s). Failure to provide details regarding the GenAI system(s) may result in disqualification.

a. GenAI Model Name (including LLM Version, all model names/owners for the solution or offering)

b. Applications/Product Owner (GenAI powered or driven)

c. Product Description

d. Use Case(s)

e. Intended Information Domain

f. Update procedure

g. Bias Detection: Explain any measures or safeguards implemented to ensure the GenAI system is not adversely affecting decisions that materially impact access to, or approval for, housing or accommodations, education, employment, credit, health care, and criminal justice.

All of the items described in this section are non-negotiable. However, if a manufacturer's specification is used or identified above, then a proposal may include, in sufficient detail, that its proposal contains an equivalent brand.

b. Technical Scorable Criteria

i. Qualifications, Financial Strength, Customer Base, and Company Structure

1. Qualifications and Company Structure

a. A statement of the firm’s experience and qualifications to meet the requirements of the City as outlined herein. Include a general overview and history of your company, number of years in business, number of employees, corporate headquarters location, type of business, names of the firm’s chief officers (include an organizational chart if possible), and where you do business. Offerors may include an annual report or statement of finances, if available, but it shall not substitute for the written narrative requested for this item.

b. Detail Offeror’s experience in providing the services requested herein for five (5) similar customers of similar size, with dates of performance and/or completion, customer name, contact person, and telephone number(s). By providing such references you agree that neither the City nor the clients referenced shall have any liability regarding the provision of such references or the City’s use of such references in making selections under this RFP.

2. Financial Strength

a. What is Offeror’s total annual revenue for the last fiscal year? What is the percentage of revenue growth or decline from the last three years?

b. Describe all merger and acquisition activity (whether you are the acquiring or acquired company) over the last three years and any planned activity (as much as can be disclosed).

c. Please indicate if Offeror has been part of any active or inactive lawsuits / litigation over the last three years.

3. Customer Base

a. Provide Offeror’s total number of active clients. In doing so, call out how many of those clients are using the exact version of the solution being proposed for the City.

b. Identify existing clients using the proposed solution that have similarities in service composition and size to City.

c. What is the total number of new client implementations within the past 24 months (not including client upgrades of the same solution)?

d. How many clients have implemented replacement solutions and left your company as users within the past 24 months?

4. Company Structure

a. What is the total number of employees within your organization? Please provide the breakdown of employees between Implementation Services, Customer Support, Sales, and Research and Development. Within Implementation Services, please also provide a breakdown of the total employees by project management, functional consultants, technical consultants, and training resources.

b. What is your firm’s turnover percentage (# of people who left the department / average count of employees over that period of time) within the Implementation Services staff, Customer Support staff, and Research and Development staff over the past 24 months?

ii. Proposed Staff Members and Staffing Approach

1. Identify proposed staff members who would be involved in providing the services requested herein and submit statements or resumes detailing their qualifications. Your proposal should include information on levels of training received by each staff member and detailed descriptions of the number of years of experience each staff member has implementing the proposed solution.

2. Provide a staffing worksheet that will identify the resources assigned to the project, their level of participation (FTE %), and have this participation represented monthly throughout the major stages of the project. Please indicate the expected split of on-site vs. remote time per resource. Also, indicate if any resources listed on the staffing worksheet are third-party resources.

3. If applicable, identify any of the work that you intend to subcontract to others and identify the proposed subcontractors including names, specific assignments, and the qualifications of the subcontracting firm and its key personnel.

iii. Proposed Solution Description

Provide a high-level narrative of the key functionalities and differentiators of the proposed software solution. Highlight the solution’s ability to meet the specific objectives of the City. In addition to the specific service proposals specified above, identify and/or recommend any additional or innovative services and products provided by Offeror that may be related to or helpful to this project.

1. Technical Requirements: For each question below, provide the following information for Offeror’s proposed SaaS:

i. Network Requirements:

1. Describe the system's network requirements and/or bandwidth requirements.

ii. Security:

1. The system will utilize end-to-end encryption, TLS 1.3.

2. The end-to-end encryption will protect data both in transit and at rest.

3. The system uses 256-bit encryption.

4. As standard process, the vendor provides the system administrator a step-by-step process for initial password setup. Admin must assign a password to the user when creating a user master record. Password must meet the internal requirements set by the system.

5. The system must use SHA-3 (SHA-3 224, SHA-3 256, SHA-3 384, SHA-3 512) for password hashing.

6. Describe how incidents and breaches are detected, how and when customers are notified, insurance coverage, and how incidents and breaches are remediated.

iii. Interface Management:

1. Provide your experience in integration with Systems and Software's enQuesta 6 Customer Information System

iv. Implementation Approach

1. Provide a detailed explanation, work plan and graphic view of the project timeline outlining each required task necessary for completion of the implementation to integrate with System & Software’s enQuesta 6 Customer Information System. The City is open to different approaches regarding implementation; however, all proposed methodologies must include the following implementation services at a minimum. Identify the major risks associated with each phase of this project. For each risk, identify those activities which can be undertaken to reduce, mitigate or eliminate the risk.

a. Planning and Initiation

i. Project Schedule Development

ii. Kickoff

b. Discovery

i. Functional Requirements

ii. Technical Requirements

iii. Interface Management

c. Design

i. Interface Design Documents

d. Testing

i. Test scripts developed from functional requirements that will be tracked against testing processes to ensure delivery of promised scope.

ii. System Integration Testing with interfaces, modifications, converted data, and custom scripts developed from functional requirements, including End to End Business Process Testing

iii. Daily Activity Testing/User Acceptance Testing

iv. System Performance Testing

e. Technical Training

i. Technical architecture of the solution

ii. Training on integration design and Application Programming Interface (“API”) Calls

iii. Security Configuration

iv. Support Tools

f. Project Team Training

i. Product

ii. Process

iii. Configuration

iv. Data Model

g. End-User Training Support

i. Guidance and assistance to City trainers during End-User Training

h. Go-Live Preparation and Support

i. Cutover task list development

ii. Successful completion of a minimum of two (2) mock go lives, including all cutover tasks

iii. On-site assistance through Go-Live weekend

i. 2 Weeks of Post Go Live Support

i. On-site assistance at least two (2) weeks after go live

ii. Continuing issue/incident resolution

iii. Transition to support from the implementation team in the last month of post go live support

2. Project Management

a. Describe Offeror’s project management methodology and explain how it adheres to the Project Management Institute (PMI) standards.

b. Provide background on a recent implementation that is similar in scope and size to City, highlighting the overall implementation success, key success factors, and lessons learned.

c. Describe the expected resources and level of effort required from City to support the implementation.

3. Tools and Resources

a. Describe Offeror’s testing and training methodologies.

b. Provide sample Training Course Lists, and Training Guides for the transfer of service process as Attachments 6-8 with proposal.

c. Describe any tools utilized for project management and environment management.

v. Software Maintenance and Support Services

1. Maintenance and Support

1. Detail your team’s approach to ongoing support: For example: 1) Dedicated Point of Contact (POC), 2) Desired means of contact (phone, email, ticket system), 3) Support availability (hours, time zones, holidays), 4) Prioritization of support requests, and 5) Issue resolution response times.

2. Provide an example Service Level Agreement for ongoing support as Attachment 9 - Service Level Agreement with your proposal.

3. Provide the average timeframe that individual account managers remain assigned to their respective support clients.

4. Describe any self-help tools provided via online guides, training documentation, data dictionaries, entity relationship diagrams, etc. Include information about any existing user group networks that would benefit the City.

2. Releases and Upgrades

1. Describe Offeror’s release management process, including communication, environment management, and planning release cadence with the clients. Please provide a few examples of Release Notes that the City can expect with each release as Attachment 10 - Release Notes with proposal.

2. Describe the effort expected of City staff to implement release updates and upgrades (provide effort in terms of FTE by activity, if possible). Distinguish the effort between minor releases and more complex upgrades.

3. Describe the coordination and amount of flexibility that City can expect in applying releases. For example: 1) Are releases required or optional, 2) If optional, how many releases / versions can the City choose to delay, 3) What are the ramifications if the City surpasses these rules, 4) How much time is allowed for the City to conduct testing and training before applying the release?

4. Provide a roadmap of upcoming releases as well as a history of major past releases while indicating any experienced delays in the intended delivery of these releases.

5. Describe how modifications / customizations to the system are incorporated into the next general release of the system while highlighting how your company effectively manages modifications / customizations from various customers while avoiding individually customized systems per client.

vi. API Approach

Provide a narrative description of Offeror’s proposed solution's approach to APIs. Explain and stress the flexibility and scalability of said approach - i.e., Does the API have a broad feature set of calls and functionality? Does the API allow for customization and extensibility? Can developers add new functionality or endpoints to the API to meet specific needs? Can parameters be customized for specific use cases or scenarios?

vii. Code Management

Provide a narrative of Offeror’s software development lifecycle (“SDLC”) including how customizations/modifications are incorporated into the base product, testing before releasing to customers, maintenance, and secure coding practices.

viii. Cyber Security Incident Response

Provide a narrative of Offeror’s Cyber Security Incident Response Program (“CSIRP”) including how incidents and breaches are detected, how and when customers are notified, insurance coverage, and how incidents and breaches are remediated.

d. Cost Proposal

i. Cost Proposal

Complete and submit Attachment 2: Cost Sheet.

Proposed prices must include all costs associated with the performance of the services specified, including implementation, materials, supervision, labor, insurance, transportation, delivery, fuel or other surcharges, demurrage, and related costs. Charges not listed in the RFP response will not be allowed. All prices and fees must be in U.S. dollars.

ii. Price Guarantee Period

Offeror must guarantee its pricing for the duration of the Agreement.

VIII. PROPOSAL EVALUATION PROCESS

a. Stage 1: Initial Review

In the initial phase of the evaluation process, City will review all proposals timely received. Non-responsive proposals not conforming to RFP requirements or unable to meet the mandatory minimum requirements will be eliminated from further consideration.

b. Stage 2: Technical Proposal And Policy Criteria Evaluation

Responsive proposals will then be evaluated by an evaluation committee appointed by City against the proposal technical scoreable criteria noted in this RFP. Proposals will be evaluated against the technical scoreable criteria as follows:

Technical Category #1 (75 Points): Qualifications, Financial Strength, Customer Base, and Company Structure Technical Category #2 (100 Points): Proposed Staff Members and Staffing Approach Technical Category #3 (125 Points): Proposed Solution Description Technical Category #4 (125 Points): Implementation Approach Technical Category #5 (125 Points): Software Maintenance and Support Services Technical Category #6 (50 Points): API Approach Technical Category #7 (50 Points): Code Management Technical Category #8 (50 Points): Cyber Security Incident Response

Total Technical Points Possible: 700 points

Offerors that achieve minimum score threshold of 420 points will proceed to the final stage. Offerors with a score of less than the minimum required technical points will be ineligible for further consideration.

The evaluation score sheet has been attached to this RFP. The attached evaluation score sheet states the relative weight that will be given to each technical scoreable criteria. The evaluation committee, for this RFP, will tally the final scores for criteria other than cost to arrive at a consensus score by the following method: an average of the individual scores.

c. Final Stage: Cost Proposal Evaluation

The cost proposal will be evaluated independently from the technical proposal.

The Offeror with the lowest total cost will receive 300 points, or 100% of the total cost points. All other Offerors will receive a portion of the total cost points based on what percentage higher their total cost is than the total lowest cost. The formula to compute the points is: Cost Points x (Lowest Proposed Price/Proposed Price).

It is anticipated that this RFP will result in a single contract award to the responsive and responsible Offeror with the highest score justified by the procurement code.

image1.png