8-01. RFP Solicitation Information- CV SCMS- AMENDED.doc

I. General Overview and Instructions

AMENDED 2025-07-29

This Request for Proposals (“RFP”) is intended to provide interested offerors with sufficient basic information to submit proposals meeting minimum requirements. It is not intended to limit a proposal's content or exclude any relevant or essential data.

This solicitation is issued in accordance with the State of Utah Procurement Code, Utah Code Annotated (UCA) Chapter 63G-6a, and applicable Administrative Rules found in the Utah Administrative Code (UAC) R33. If any provision of this solicitation conflicts with the UCA or UAC, the UCA or UAC will take precedence.

NOTICE: In this solicitation, if an item is defined through use of a trade name, brand name, or a manufacturer and/or model number, it is intended that the words, “or equivalent” apply; and invites the submission of equivalent products by the Offerors.

CANCELLATION OF PROCUREMENT

The Utah Department of Transportation (the State) reserves the right to cancel this solicitation at any time and not award a contract if such action is determined in writing to be in the best interest of the State (UCA §63G-6a-709).

FUTURE PROCUREMENTS

UDOT reserves the right to reopen this solicitation or create a new solicitation if it determines there may be more need for the procurement item than when the original solicitation was issued.

QUANTITY ESTIMATES

Historical usage may not be representative of forthcoming need, and as such, UDOT does not guarantee to purchase any amount under this contract.

QUESTIONS AND ANSWERS

Questions MUST be submitted through the online bidding system during the designated Question and Answer period. Questions submitted through any other channel will not be answered. Answers disseminated by the State through the online bidding system may modify the specification or requirements of this solicitation and will constitute an addendum to this solicitation.

Questions or notifications to the State of any ambiguity, inconsistency, excessively restrictive requirement, or errors in this solicitation MUST be submitted as a question during the Q&A period.

Issues with the solicitation that have not been previously addressed within the Q&A period of the procurement are not allowed to be addressed within a proposal and may result in the Offeror’s proposal being considered non-responsive.

It is the responsibility of the Offeror to submit their proposal as required by this solicitation, including any requirements contained in an answered question and/or addenda.

Exceptions to the scope of work or other content of the Solicitation not previously addressed within the Q&A period of the procurement may result in the Offeror’s proposal being considered non-responsive.

ADDENDA

Any modification to this procurement will be made by addendum issued by the State. Addenda to this solicitation may be made for the purpose of making changes to the scope of work, the schedule, the qualification requirements, the criteria, the weighting, or other requirements of this solicitation.

Authorized and properly issued addenda shall constitute the official and binding position of the State. Any response to this solicitation which has as its basis any communications or information received from sources other than this solicitation, or related addenda, may be considered non-responsive and be rejected at the sole discretion of the State.

The State accepts no responsibility for a prospective Offeror not receiving solicitation documents and/or revisions to the solicitation. It is the responsibility of the prospective Offeror to monitor the bidding system to obtain addenda or other information relating to the solicitation.

RESTRICTIONS ON COMMUNICATIONS

From the issue date of this solicitation until an award is published, Offerors are prohibited from communications regarding this solicitation with staff, evaluation committee members, or other associated individuals EXCEPT the UDOT procurement officers overseeing this solicitation. Failure to comply with this requirement may result in disqualification.

PROPOSAL SUBMISSION

All materials submitted become the property of the State. Materials may be evaluated by anyone designated by the state as part of the proposal evaluation committee. Materials submitted may be returned only at the State's option.

Proposals must be received by the due date and time (“deadline”). Proposals received after the deadline will be late and ineligible for consideration.

Electronic submission instructions: When submitting a proposal electronically through the online bidding system, please allow sufficient time to complete the online forms and to upload proposal documents. The solicitation will end at the deadline. If an Offeror is in the middle of uploading a proposal when the deadline arrives, the system will stop the upload process and the proposal will not be accepted by the bidding system, and the attempted submission will be considered late and ineligible for consideration.

Electronic proposals may require uploading of electronic attachments. The online bidding system will accept a wide variety of document types as attachments. However, the State is unable to view certain documents. Therefore, DO NOT submit documents that are embedded (zip files), or encrypted. All documents must be uploaded in the bidding system as separate files (system limit for file size is 50 MB).

Files submitted electronically must NOT be password protected or locked in any way.

Cost Proposal submission instructions: Cost Proposals are evaluated independently from the technical proposal, pursuant to the Utah Procurement Code, and as such, must be submitted separately from the technical proposal and as per solicitation requirements. Failure to submit cost or pricing data separately and as directed may result in your proposal being judged as non-responsive and ineligible for contract award.

Sample submission instructions: Offerors may be required to submit product samples to demonstrate whether a procurement item meets the specifications and other requirements set forth in the solicitation.

· Samples must be received prior to the solicitation due date and time and must be furnished free of charge unless otherwise stated in the solicitation.

· Samples must be furnished free of charge unless otherwise stated in the solicitation.

· Samples, if not destroyed by testing, will upon written request within any deadline stated in the solicitation, be returned at the vendor's expense.

· Samples must be labeled or otherwise identified as specified in the solicitation.

All costs incurred by an Offeror in the preparation and submission of a proposal, including any costs incurred during interviews, oral presentations, and/or product demonstrations are the responsibility of the Offeror and will not be reimbursed.

PROTECTED INFORMATION

Portions of a proposal may be protected by submitting a Claim of Business Confidentiality Form. However, an entire proposal cannot be identified as “PROTECTED”, “CONFIDENTIAL” or “PROPRIETARY”, and if so identified, shall be considered non-responsive unless the Offeror removes the designation.

Pricing may not be classified as confidential or protected and will be considered public information after award of the contract.

Process for Requesting Non-Disclosure: Any Offeror requesting that a record be protected must provide with their proposal the following information:

1. Must provide a completed Claim of Business Confidentiality at the time the information (proposal) is provided to the state, and

2. Must include a concise statement of reasons supporting the claim of business confidentiality (UCA § 63G-2-309(1)).

3. Must submit an electronic “redacted” (excluding protected information) copy of the proposal. Copy must clearly be marked “Redacted Version.”

Redacted Copy: If an Offeror submits a proposal that contains information claimed to be business confidential or protected information, the Offeror MUST submit two separate proposals: one redacted version for public release, with all protected business confidential information either blacked-out or removed, clearly marked as "Redacted Version"; and one non-redacted version for evaluation purposes, clearly marked as "Protected Business Confidential."

Offeror acknowledges that its proposal or redacted copy will be made public upon the State’s receipt of a GRAMA request. The Offeror will not be notified of any GRAMA request made to the State for offeror’s proposal. If the offeror submits a redacted copy, then the State will respond to a GRAMA request for offeror’s proposal with offeror’s redacted copy. However, if the offeror fails to submit a redacted copy, then the State will respond to a GRAMA request with offeror’s proposal, which will result in offeror’s protected/proprietary information, if any, being made public. Contractor acknowledges that notations in the header, footer or watermark of the proposal will not be considered sufficient to constitute a request for non-disclosure of protected/proprietary information.

Failure to comply with the requirements regarding Protected Information releases the State from any obligation or liability arising from the inadvertent release of Offeror information.

CORRECTION OR WITHDRAWAL OF PROPOSAL

Proposals may be modified or withdrawn by written or electronic notice received by the procurement officer prior to the established due date.

A decision to permit the correction or withdrawal of a proposal or the cancellation of an award or a contract shall be supported in a written document, signed by the chief procurement officer or head of a procurement unit with independent procurement authority.

The State reserves the right to waive minor informalities as well as minor deviations. The State also reserves the right to seek clarification on any proposal response.

DISCUSSIONS OR CLARIFICATIONS

The State reserves the right to conduct discussions with an Offeror to obtain a more complete understanding of whether the Offeror is responsible, or whether the Offeror’s submitted proposal is responsive. Following discussions, a proposal may be rejected if it is determined that the Offeror is not responsible, or the proposal is not responsive.

INTERVIEWS AND PRESENTATIONS

Interviews and presentations may be held at the option of the State. The State shall establish a date and time for the interviews or presentations and shall notify eligible Offerors of the procedures. Interviews or presentations shall be limited to those Offerors meeting the minimum requirements specified in the RFP. Interviews and presentations will be at the Offeror's expense.

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.

BEST AND FINAL OFFER

A Best and Final Offer (BAFO) may be issued if it is determined to be necessary. The Best and Final Offer process is a formal request for offerors to amend specific portions of the technical proposal or cost proposal.

Under the Utah Procurement Code, a Best and Final Offer may be requested if:

(i) no single proposal adequately addresses all the specifications stated in the request for proposals;

(ii) all proposals are unclear or deficient in one or more respects;

(iii) all cost proposals exceed the identified budget or the procurement unit’s available funding; or

(iv) two or more proposals receive an identical evaluation score that is the highest score.

PROPOSAL EVALUATION

All responsive and responsible proposals that have not been disqualified from consideration under the provisions of Part 7 of Utah Code 63G-6a, using the criteria established in this RFP will be evaluated by an evaluation committee in accordance with the Utah Procurement Code, Administrative Rules, policies, and the evaluation criteria set forth in this solicitation.

All proposals shall remain valid for a minimum of 120 calendar days after the Proposal Due Date to allow adequate time for evaluation.

AWARD

A solicitation award does not constitute a contract. Any award made through the bid system, notifications received from the bid system, email notifications received directly from the procurement unit, documents received by the vendor, or documents posted in the bid system, DO NOT constitute or create a contract. Only a fully executed Purchase Order (PO) or a fully executed contract constitutes a binding contract.

Between the notification of award and the receipt of a fully executed PO or contract, the procurement unit may cancel the award and/or the solicitation in full, or in part in accordance with UCA 63G-6a-902 and 63G-6a-120.

If awarded, vendor(s) may not begin work, purchase materials, or enter into subcontracts relating to this solicitation until they receive a fully executed PO or contract.

After the evaluation and final scoring of proposals is completed, the State shall award the contract as soon as practicable, provided the solicitation is not canceled without awarding a contract.

PROTEST PROCESS

Offerors are directed to Utah Code Part 16 and Utah Administrative Code Rule R33-16 for available appeal processes.

CONTRACT TERMS AND CONDITIONS, EXCEPTIONS, AND NEGOTIATIONS

Any contract resulting from this solicitation will include, but not be limited to the following:

· Scope of Work Specifications, Requirements, and Instructions.

· Any addendums to the solicitation as issued through the bidding system.

· Attachment A- State of Utah Standard Terms and Conditions.

· Attachment B- State of Utah IT Standard Terms and Conditions Exceptions and/or additions to the Standard Terms and Conditions are strongly discouraged. Any requested exceptions and/or additions to the Standard Terms and Conditions must be submitted with the proposal. Exceptions and/or additions submitted after the date and time for receipt of proposals will not be considered. Offerors may not submit requests for exceptions and/or additions by reference to a vendor's website or URL.

The State 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 Attorney General'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.

In a multiple award situation, the State reserves the right to negotiate exceptions and/or additions to terms and conditions in a manner resulting in expeditious resolutions. This process may include beginning negotiations with the Offeror having the least number of exceptions and/or additions and conclude with the Offeror submitting the greatest number of exceptions and/or additions. Contracts may be executed and become effective as negotiations are completed.

Offerors must provide all documents in Microsoft Word format with redline editing. Offerors must also provide the name, contact information, and access to the person(s) that will be directly involved in legal negotiations.

Any mandatorily required acceptance of an Offeror’s terms and conditions may result in the proposal being determined to be non-responsive.

An award resulting from this solicitation is subject to successful contract terms and conditions negotiation (if required). The State, at its sole discretion, will determine when contract terms and conditions negotiations become unproductive and will result in termination of award to that Offeror and the State may move to the next eligible Offeror.

NOTE: Please also note the provision in the IT T&Cs (Item 28 paragraphs d and k) that all state data must be maintained in data centers in the United States and all vendor services involving access to state data shall be performed within the United States.

PERFORMANCE EVALUATION

Contracts resulting from this solicitation are subject to performance evaluations. Continuous negative performance evaluations and documented feedback from end users may impact on a vendor’s ability to participate in future solicitations. Performance evaluations may include end user surveys, performance audits, reports, interviews, or other reasonable methods of performance evaluation. Vendors will be notified of any negative performance evaluations or end user feedback collected.

STABILITY OF VENDOR

The State reserves the right to request financial and other information it deems relevant as necessary to evaluate a vendor’s stability and capability of completing the Scope of Work.

SUBCONTRACTORS

Some elements of this work may be subcontracted, not exceeding Thirty (30) percent of the total monetary value of the work.

The planned use of any and all subcontractors must be clearly explained in the Executive Summary. The Offeror, if awarded the contract, shall be responsible for all costs and contract performances if subcontractors are used. The State reserves the right to review and approve all subcontractors, review services conducted by subcontractors, and refuse payment on projects where subcontractors are used without foreknowledge or approval by the State.

Subcontractors must be authorized to do business in the State of Utah. Subcontractors must include information, in the same detail as the prime contractor or offeror, of any and all personnel and companies who are not in the direct employ of the Contractor. Freelance/contracted labor may not be billed above the prevailing labor rate in the contract and is not considered a reimbursable expense. The prime Offeror shall be responsible for all costs and contract performances by subcontractors if used.

Joint Bids: Joint bids must be submitted on a prime/subcontractor basis rather than as a joint venture. The State intends to contract with a single firm or multiple firms, but not with multiple firms doing business as a joint venture.

TECHNOLOGY MODIFICATIONS

Pursuant to Utah Administrative Rule R33-12-502 the awarded contract(s) may be modified to incorporate new technology or technological upgrades associated with the procurement item being solicited, including new or upgraded:

(i) systems;

(ii) apparatuses;

(iii) modules;

(iv) components; and

(v) other supplementary items.

Further, a maintenance or service agreement associated with the procurement item under the resulting contract(s) may be modified to include any new technology or technological upgrades.

Any contract modification incorporating new technology or technological upgrades will be specific to the procurement item being solicited and substantially within the scope of the original procurement or contract.

UDOT assumes that the SCMS System will be hosted in a cloud environment operated by the vendor. Any costs for hosting the system shall be included on the Vendor Pricing Sheet. If the vendor’s solution involves an on-premises server at a UDOT site, vendor shall fully describe that solution and the hardware which will be needed along with an estimate of the cost and effort needed to maintain that on-prem system. UDOT has an account with GCP. If the vendor’s solution involves any implementation on UDOT’s GCP instance, vendor shall describe that implementation and include the cost in their estimate of cost in the Vendor Pricing Sheet.

Any solutions that include cloud services, IaaS, PaaS, SaaS, MaaS, CaaS & XaaS, etc. are preferred to be implemented using the existing State of Utah Department of Technology Services (DTS) accounts for those hosted services, where possible. DTS has accounts with most major cloud producers (AWS, GCP, Azure, etc.).

NOTE: UDOT relies primarily on GCP, and it is UDOT’s preference that hosting remain with UDOT’s instance of GCP. That preference does not preclude a vendor from offering a different approach, including their own cloud instance, but the vendor must provide estimates of the cost for that implementation It is expected that State of Utah data reside on the DTS-managed accounts for these and all providers. If applicable, please ensure that the solicitation response incorporates the use of these DTS accounts and that the pricing quoted does not include vendor hosting costs as costs would be paid directly to the hosting providers through DTS's existing accounts.

If it is not possible to utilize the DTS cloud services accounts, please provide the reasoning why to the solicitation’s Q&A board so as to allow the State to amend this solicitation requirement if appropriate.

IT procurements may be subject to third-party review and additional reference checks as a matter of course.

BACKGROUND CHECKS

The State reserves the right to require any Contractor (employees, subcontractor, or others associated with the vendor) with access to secure state facilities, sensitive data, or technology to complete a background check.

Contractor agrees to notify the State immediately if an arrest or conviction of any employee or subcontractor that has access to secure state facilities, sensitive data, or technology occurs during the performance of a contract resulting from this solicitation.

Contractor shall not permit any of its employees or subcontractors who have been convicted of a felony or misdemeanor to have access to secure state facilities, sensitive data, or technology.

The State reserves the right to determine what state facilities, sensitive data, or technology applies to the background and disclosure/notification requirements.

II. Solicitation Specifics NOTICE: The electronic bidding system’s Event Number must be referred to on all proposals, correspondence, and documentation relating to this solicitation.

PURPOSE OF REQUEST FOR PROPOSAL (RFP)

The purpose of this Request for Proposal (RFP) is to enter into contracts with qualified vendors to provide a comprehensive solution for a Connected Vehicle Security Certificate Management System (CV SCMS). This system will enable secure enrollment, issuance, management, and validation of digital certificates for connected vehicles, ensuring secure communication and data exchange within the vehicle-to-everything (V2X) network. The solution should ensure compliance with industry standards and regulatory requirements related to vehicle cybersecurity.

UDOT’s current V2X security certificates are provided by Integrity Security Services (ISS) through a contract with Panasonic of North America. The contract with Panasonic is expiring, so UDOT is seeking a direct contract with an SCMS provider to replace that service.

BACKGROUND

See document titled “SCOPE OF WORK.CV SCMS”.

BUDGET ESTIMATE

UDOT has budgeted approximately $200,000 for the first year of operation of this system, including licensing, installation, integration, set-up, and training. Beyond the first year, UDOT anticipates costs of less than $100,000 per year for certificates, certificate management, licensing, management portals, operation and maintenance of the system. These budget values are a general guideline.

CONTRACT AWARD INTENT

It is anticipated that this solicitation will result in multiple contract awards.

LENGTH OF CONTRACT AND PRICING GUARANTEE

The contract(s) resulting from this solicitation will be for a period of Five (5) years with the option of 5 (five) 1-year renewal options. Contract has a potential maximum length of 10 years.

All pricing must be guaranteed for 6 months. Following the guarantee period, any request for price adjustment must be for an equal guarantee period and must be made at least 30 days prior to the effective date. Requests for price adjustment must include sufficient documentation supporting the request (ie through Federal commodity indices) and demonstrating a logical mathematical link between the current price and the proposed price.

Price adjustments may occur no more frequently than pricing guarantee period. An "Exception" will be considered if there is a net change in price of five (5) percent or more based on a change in the index(es). If a price adjustment is granted earlier than the price guarantee period, that adjustment must be in effect for a full price guarantee period unless there is a subsequent Exception.

Any adjustment or amendment to the contract will not be effective unless approved by the State. The State will be given the immediate benefit of any decrease in the market, or allowable discount.

In a multiple award situation, any adjustment made by one contractor may result in the necessity of providing the same opportunity to all other contracted vendors to adjust pricing on the same item(s).

ANTICIPATED SCHEDULE

The following is the anticipated schedule for this procurement. The State of Utah reserves the right to alter these dates. All deadlines are prevailing Daylight Mountain Time.

III. Scope of Work and Associated Requirements All Scope of Work Requirements MUST be demonstrably met by an Offeror in order for their response to be considered. Any breach of requirements once the Contract has been awarded constitutes breach of Contract by the vendor and the Contract may be terminated immediately.

The Scope of Work is subject to change based on the awarded contract(s).

DETAILED SCOPE OF WORK AND ASSOCIATED REQUIREMENTS

See document titled “SCOPE OF WORK.CV SCMS”.

IV. Required Proposal Submission Information

PROPOSAL RESPONSE

All offerors must submit proposals that detail their experience and qualifications in the requested areas (each area must be addressed. Do not list “not applicable”).

For ease of evaluation, the submitted proposals must provide a point-by-point response, addressing in detail each area of the evaluation criteria. The criteria are not intended to limit a proposal's content or exclude any relevant or essential data. Offerors are at liberty and are encouraged to expand upon the criteria to demonstrate the Offeror’s capability to provide the State with a solution.

Offerors bear sole responsibility for providing evidence in their response that they are capable of performing the requested Scope of Work.

PROPOSAL FORMAT and RESPONSE REQUIREMENTS Proposals should be concise, straightforward, and prepared simply and economically. Expensive displays, bindings or promotional materials are neither desired nor required. However, there is no intent in these instructions to limit a proposal’s content or to exclude any relevant or essential data.

Proposals should be organized and titled using each of the following specific headings:

1.

Section Title: UDOT Vendor Setup Form.

UDOT’s Vendor Setup Form fully completed and signed by the offeror.

See document titled “Submittal Form- Vendor Setup Form.pdf”.

2.

Section Title: Cover Letter.

Include a one-page cover letter that identifies the name and primary contact information of the person who will be authorized to execute an agreement with the State of Utah on behalf of the Offeror.

3.

Section Title: Business Confidential/Protected Information.

All protected/proprietary information must be indicated by submitting a completed Claim of Business Confidentiality form.

If offeror’s proposal contains protected/proprietary information (please refer to the Protected Information section of this solicitation for additional information) then offeror must also submit a redacted copy of the proposal at the same time as the offeror submits its proposal. The redacted copy of the offeror’s proposal must be submitted in compliance with the other sections of this solicitation.

If there is no protected information, check the “None” box on the submittal form.

Failure to comply with this Section releases the State from any obligation or liability arising from the inadvertent release of Offeror information.

See document titled “Submittal Form- Business Confidentiality- check fields.doc”.

4.

Section Title: Potential Conflicts of Interest.

Offerors must identify any conflict, or potential conflict of interest, that might arise during the contract.

If no conflicts are identified or expected, write “None” in this section.

5.

Section Title: Exceptions and/or Additions to the Standard Terms and Conditions.

Proposed exceptions and/or additions to the Standard Terms and Conditions must be submitted in this section. Offeror must provide all proposed exceptions and/or additions, including an Offeror’s terms and conditions in Microsoft Word redline format. Offerors must also provide the name, contact information, and access to the person(s) that will be directly involved in terms and conditions negotiations.

If there are no exceptions and additions to the Standard Terms and Conditions, check the “No” box on the submittal form.

See documents titled “Submittal Form- Attachment A- Utah Standard Terms and Conditions- with check fields.docx”, and ” Submittal Form- Attachment B- Utah IT Standard Terms and Conditions- with check fields.docx.

6. Section Title: Mandatory Minimum Requirements/Qualifications (Pass/Fail Criteria).

Offerors must provide the required evidence and/or documentation/narratives demonstrating compliance with the stated Mandatory Minimum Requirements/Qualifications. An Offeror’s failure to meet any one of the mandatory requirements will result in the proposal being classified as non-responsive and will be rejected under the provisions of the Utah Procurement Code.

Vendors should review the scope of work and/or specifications in the files before submitting their responses to the mandatory minimum requirements.

All of the items described as mandatory minimums are non-negotiable. If it is determined that a response does not meet the mandatory minimum requirements, at any time during the solicitation process, it will be deemed non-responsive and disqualified from further consideration.

Offerors must provide sufficient evidence and/or documentation demonstrating that the offeror is compliant with the Mandatory Minimum Requirements:

See document titled “Submittal form- VENDOR RESPONSE SHEET.CV SCMS”.

7.

Section Title: Detailed Technical Proposal (Scored Criteria).

This section should constitute the major portion of the proposal and must be a concise overview of the Offeror's assessment of the work to be performed, the Offeror’s ability and approach, and the resources necessary to fulfill the requirements. This section should demonstrate the Offeror's understanding of the desired overall performance expectations, deliverables, if any, and outcomes. Clearly indicate any options or alternatives proposed. In any case wherein the Offeror cannot comply with a provision outlined in the “Detailed Scope of Work”, such inability must be stated in response to the applicable requirement. Offerors should reference the Scope of Work in their response.

For ease of evaluation, the Detailed Technical Proposal Section must be a specific point-by-point response, addressing in detail each of the Technical Evaluation Criteria.

The offeror bears sole responsibility for the items included or not included within their submitted. Each area of the evaluation criteria must be addressed in detail in the response. The criteria are not intended to limit a response's content or exclude any relevant or essential data. Vendors are at liberty and are encouraged to expand upon the criteria to demonstrate the vendor’s capability to provide the State with a solution.

Offerors must provide a detailed narrative demonstrating their capability, capacity, depth of experience, and prior accomplishments:

See document titled “Submittal form- VENDOR RESPONSE SHEET.CV SCMS”.

8. Section Title: Cost Proposal. All costs are to be enumerated on the Cost Proposal Form (see Response Form- Proposal Item Price List).

NOTICE: Cost Proposal Evaluation will only be done on those responses that meet or exceed the Stage 2 threshold.

Pursuant to Utah Procurement Code requirements, Cost Proposals are evaluated independently from the Technical Proposal, and as such, must be submitted as an independent and separate document (Cost Form) from the Technical Proposal. Inclusion of any cost or pricing data within the Technical Proposal will result in the proposal being judged as non-responsive.

Offerors must provide the following:

See document titled “Submittal form- VENDOR PRICING SHEET.CV SCMS”.

NOTICE: Offerors may not change/modify the format of the Price Response Form and must submit pricing in the exact format requested for a fair comparison of pricing among all offerors. Altering the format or conditioning the cost on acceptance of additional/conflicting terms or limitations may result in a finding that your proposal is non-responsive.

The cost proposal must address all costs associated with the services described in the RFP over the life of the project. The cost of this project should be defined according to the specific tasks or steps to be taken.

V. Proposal Evaluation and Contract Award

PROPOSAL EVALUATION PROCESS

All responses submitted in response to this solicitation will be evaluated in a manner consistent with the Utah Procurement Code, Administrative Rules, policies and the evaluation criteria in this solicitation.

This solicitation will be evaluated under a Multiple Stage process.

Stage 1: Determination of Responsiveness In Stage One of the evaluation process, all proposals timely received will be reviewed for responsiveness to solicitation requirements. Proposals not conforming to solicitation requirements or unable to meet the Mandatory Requirements (Pass/Fail) will not proceed on to Stage 2 Technical Proposal Evaluation.

Stage 2: Technical Response Evaluation (Scored: 225 points possible) Stage Two will consist of an evaluation committee conducting a detailed Technical Evaluation of each responsive and responsible proposal that has not been previously disqualified or rejected.

Responsive proposals will be evaluated against the Technical Evaluation Criteria. The evaluation committee will tally the final scores for the Technical Criteria to arrive at a consensus score by an average of the individual scores.

Only those Proposals that obtain 50% (112.5 points) or more of the 225 possible Total Technical points (Technical Categories A, B, and C) will be eligible to proceed on to Stage 3: Virtual System Demonstrations. Proposals with a score of less than the minimum required technical score will be deemed non-responsive and ineligible for further consideration.

Stage 3: Virtual System Demonstration (Scored: 50 points possible) Stage Three will consist of a Virtual System Demonstration to the evaluation committee by each responsive and responsible proposal that has not been previously disqualified or rejected.

In the virtual demonstration, vendors should demonstrate that their system meets the requirements of this RFP, be prepared to discuss potential modifications and enhancements, and be prepared to respond to questions and clarifications about their proposed system.

Vendors will be assigned a specific date and block of time for the Demonstration.

Stage 4: Cost Proposal Evaluation (55 points possible) Stage Four will consist of the Cost Proposal Evaluation of each responsive and responsible proposal that has not been previously disqualified or rejected.

Cost Proposals will be evaluated as follows:

The offeror with the lowest Total Cost will receive the maximum available Cost points. All other offerors will receive points as determined by the ratio* of their cost to the lowest offered cost. Final cost scores will be calculated based on the following:

*Ratio Calculation: The Cost Points assigned to each Offeror’s Cost Proposal will be based on the lowest Overall Total Cost. The Offeror with the lowest Overall Total Cost will receive 100% of the cost points. All other Offerors will receive a portion of the total cost points based on what percentage higher their Proposed Overall Total Cost is than the Lowest Proposed Overall Total Cost.

The formula to compute the points is: Cost Points x (Lowest Proposed Overall Cost/Proposed Overall Total Cost)

Stage 5: Determination of Contract Award Multiple Award:

In regards to this solicitation, UDOT has determined to enter into Multiple contracts.

The proposal with the Highest Total Combined Score, and all those proposals within 50% of the Highest Scoring proposal, will be eligible for award.

After the evaluation and final scoring of proposals is completed, the State shall award the contracts as soon as practicable, provided the RFP is not canceled in accordance with Utah Procurement Code requirements.

RFP Document