State of Oregon

Oregon Department of Transportation Request for Proposal (“RFP”) RFP TITLE: Commercial vehicle information exchange window (“cview”) REPLACEMENT project RFP/Bid Solicitation Number: S-73000-00017493 Date of Issue: See “Available Date” for this RFP in OregonBuys Opening Date and Time: See “Bid Opening Date” and time for this RFP in OregonBuys.

Purchaser/Single Point of Contact: See “Purchaser” and “Info Contact” for this RFP in OregonBuys.

Notes:

· OregonBuys: This RFP is advertised as a “Bid Solicitation” in the OregonBuys web-based eProcurement system (https://oregonbuys.gov/bso/). See RFP section 1.3 – OregonBuys for information regarding vendor registration and terminology used in OregonBuys platform.

· Hyperlinks: This document must be viewed electronically to access files, forms, provisions or other documents provided via hyperlinks within this RFP.

· Accessibility: The Oregon Department of Transportation is committed to complying with all statutory requirements to ensure that it is providing information that is more accessible to people with disabilities, as required by Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d), and 36 C.F.R. 1194 Appendix A. This includes information regarding the solicitation process. Please contact the Single Point of Contact identified in OregonBuys (see “Purchaser” and “Info Contact”) to request reasonable accommodation for access, due to a disability, to information related to this solicitation, or the solicitation process, or both. Accommodation requests must be received by the Purchaser 3 business days prior to the Proposal Submission Deadline (see “Bid Opening Date” and time in OregonBuys).

· Non-Discrimination: ODOT, in accordance with the Title VI of the Civil Rights Act of 1964, 78 Stat. 252. 42 U.S.C. 2000d to 2000d-4 and Title 49, Code of Federal Regulations, Department of Transportation, Subtitle A, Office of the Secretary, Part 21, Nondiscrimination in Federally-Assisted programs of the Department of Transportation issued pursuant to such Act, hereby notifies all Proposers that it will affirmatively ensure that all business enterprises will be afforded full opportunity to submit proposals in response to this solicitation and will not be discriminated against on the grounds of race, color, sex, or national origin in consideration for an award.

RFP/Bid Solicitation S-73000-00017493 CVIEW Replacement Project

DAS Version 4.5 –ODOT Form S011-G050823 Page 4 of 33 Table of Contents

GENERAL INFORMATION

INTRODUCTION

The State of Oregon, acting by and through the Department of Transportation, (“Agency” or “ODOT”), is issuing this Request for Proposal under the provisions of Oregon Revised Statute (“ORS”) 279B.060 to acquire and implement a new Software-as-a-Service (“SaaS”) Commercial Vehicle Information Exchange Window (“CVIEW”) solution to replace ODOT’s legacy CVIEW system.

Additional details on the Scope of the Goods or Services or both are included in Attachment D Sample Statement of Work and Attachment H System Requirements.

ODOT anticipates the award of one Contract from this RFP.

The initial term of the Contract is anticipated to be 10 years with options to renew for additional years at ODOT’s discretion based on ODOT’s needs and funding.

SCHEDULE

The table below represents a tentative schedule of events. All times are listed in Pacific Time. All dates listed are subject to change. N/A denotes that event is not applicable to this RFP.

OREGONBUYS

Registration Requirement; OregonBuys User Guides.

All vendors must be registered in OregonBuys to do business with the state. Registration is free. To create a vendor account, click the blue “Register” button in the top right corner of the OregonBuys website: https://oregonbuys.gov/bso. For registration assistance see vendor registration guidance (https://www.oregon.gov/das/ORBuys/Documents/SupplierRegistrationGuide.pdf). Vendors are responsible for ensuring that their vendor information is current and correct in OregonBuys. ODOT will accept no responsibility for incorrect vendor information.

See OregonBuys User Guides located on OPO’s Contracting with ODOT page (https://www.oregon.gov/odot/Business/Procurement/Pages/HowTo.aspx) for quick reference information regarding common questions from vendors when using OregonBuys.

Crosswalk of Terms used In OregonBuys

RFP ATTACHMENTS

In addition to the provisions set forth and linked within this RFP, this RFP incorporates by this reference the information published or linked on the OregonBuys Bid Solicitation page for this RFP, including but not limited to:

· Details entered in the Header Information section;

· “Amendments” (if any); and

· Any other files linked in the File Attachments and Form Attachments subsections, including:

Attachment A – Sample Contract Attachment B – Disclosure Exemption Certification Attachment C – Proposal Information and Certification Sheet Attachment D – Sample Statement of Work Attachment E – Price Proposal Form Attachment F – Acronyms and Definitions Attachment G – Responsibility Inquiry Attachment H – System Requirements Attachment I – Oregon Standards Spreadsheet

PURCHASER/SINGLE POINT OF CONTACT

The single point of contact for this RFP is identified as the “Purchaser” along with Purchaser’s “Info Contact” in OregonBuys.

AUTHORITY, OVERVIEW, AND SCOPE

AUTHORITY AND METHOD

ODOT is issuing this RFP under the authority of the Department of Administrative Services (“DAS”) delegation 1095-20 (as amended), DAS Tiered Delegation Agreement.

ODOT is using the Competitive Sealed Proposal method, pursuant to ORS 279B.060 and OAR 125-247-0260. ODOT may use a combination of the methods for Competitive Sealed Proposals, including optional procedures: a) Competitive Range; b) Discussions and Revised Proposals; c) Revised Rounds of Negotiations; d) Negotiations; e) Best and Final Offers; and f) Multistep Sealed Proposals.

DEFINITION OF TERMS

For the purposes of this RFP, capitalized words are defined in OAR 125-246-0110 or as defined in Attachment F Acronyms and Definitions and in RFP section 1.3.2 - Crosswalk of Terms used In OregonBuys.

OVERVIEW AND PURPOSE

Agency Overview and Background ODOT Commerce and Compliance Division (“CCD”) regulates commercial motor carriers and rail systems to ensure safety, enforce size and weight laws, and collect taxes. CCD operates weigh stations, conducts roadside inspections, manages the Weight-Mile Tax (“WMT”) program, and verifies motor carrier authority for safety compliance. These functions are carried out in partnership with the U.S. Department of Transportation (“U.S. DOT”) and peer states across the country.

The Federal Motor Carrier Safety Administration (“FMCSA"), a component of U.S. DOT, enforces safety regulations for commercial trucks and buses to reduce crashes and fatalities. FMCSA’s Innovative Technology Deployment (“ITD”) program is a state partnership program that provides funding and technical support to help states deploy advanced electronic tools for commercial vehicle screening, data sharing, and safety enforcement. Oregon participates in the ITD program and is required to maintain federal system certifications as a condition of that participation.

CVIEW is Oregon’s state-level data aggregation and display system for commercial motor vehicle safety and credential information. CVIEW ingests and consolidates data from FMCSA’s national SAFER system and Oregon source systems, including the International Registration Plan (“IRP”), International Fuel Tax Agreement (“IFTA”), Weight-Mile Tax (“WMT”), and related credential programs, and makes that consolidated data available to enforcement officers, credentialing staff, auditors, and downstream enforcement systems. CVIEW does not hold authoritative data; source systems remain the systems of record for all data domains.

By consolidating carrier, vehicle, credential, and safety information into a single access point, CVIEW enables enforcement officers to make faster and more informed decisions during roadside inspections, supports back-office credentialing and audit functions across CCD programs, and provides downstream enforcement systems, including ODOT’s Enforcer and Green Light platforms, with real-time access to consolidated commercial vehicle data.

Current State and Need for Modernization The legacy CVIEW system reflects changes made over time to accommodate federal data exchange requirements and additional data sources. The environment includes legacy platforms, scheduled batch processing, and limited real-time integrations, including SAFER data refreshed through nightly downloads and on-demand PRISM queries. This creates significant operational and compliance limitations:

· CVIEW is used daily across enforcement, credentialing, tax, and audit functions, but was designed as a simple informational lookup system, not as an operational decision-support tool, creating a growing gap between user expectations and system capability.

· The system provides no visibility into data currency or source attribution, making it difficult for users to assess the reliability of information during time-sensitive enforcement and credentialing activities.

· Source system integrations are implemented as direct linked-table queries to mainframe Db2 databases, creating tight coupling that limits the ability to modify either CVIEW or source systems independently.

· No API layer exists; all integration is via direct database access with no versioning, authentication standards, rate limiting, or monitoring.

· Federal data ingestion is fragmented across multiple disconnected components with no single authoritative ingestion point and no visibility into processing outcomes or error conditions.

· The system spans multiple aging technology components, including mainframe COBOL, VB6, and ColdFusion, each representing a separate maintenance dependency and decommissioning risk.

· Sustaining the current environment requires ongoing internal IT resources with specialized legacy knowledge, and the architecture provides no path to reduce that burden without fundamental modernization.

These limitations collectively constrain the legacy CVIEW system's ability to meet evolving federal certification expectations, fully support CCD operational needs, and sustain the system at acceptable cost and risk.

Project Overview, Background and Purpose ODOT, through CCD, is seeking to procure and implement a modernized CVIEW system. The solution is to be a vendor-hosted, cloud-based platform SaaS solution. The primary purpose of the contract resulting from this RFP is to retain a Contractor to provide software licensing, implementation, integration, configuration, training, support, and ongoing maintenance of the modernized CVIEW system across three implementation phases. The modernized system must replace Oregon’s legacy CVIEW system, achieve ITD Core and PRISM Full certification, and serve the operational needs of CCD enforcement, credentialing, audit, and tax staff and partner systems over the life of the contract.

Project Objectives The CVIEW Replacement Project is intended to achieve the following objectives:

· Establish CVIEW as Oregon’s central federal data hub. Replace the current distributed integration model with a single authoritative ingestion point for FMCSA SAFER and PRISM data and modernize data exchange with federal systems to meet current certification requirements.

· Modernize source system integration. Transition ODOT source system connections from linked-table queries to API-based integrations, enabling real-time data availability across IRP, IFTA, WMT, and related credentials.

· Deliver comprehensive commercial vehicle e-screening. Provide enforcement and operations staff with a consolidated, real-time view of carrier, vehicle, and credential compliance status across all federal indicators and Oregon credential programs to support roadside and back-office screening decisions.

· Provide a modern, accessible user interface. Replace the current hybrid web/CICS interface with a unified, mobile-friendly display platform that supports enforcement, credentialing, audit, and tax staff across ODOT programs with role-appropriate views and lookup capabilities.

· Expand and standardize data sharing. Enable consistent, API-based data distribution to downstream consumers, including enforcement systems, clearinghouses, and the ODOT data lakehouse, replacing direct database dependencies with documented, versioned interfaces.

· Support operational reporting and compliance. Provide standard operational reports, data export capability, and federal compliance reporting to meet FMCSA certification requirements and support ODOT program oversight.

· Implement enterprise-grade security and access control. Ensure the modernized system meets Oregon security requirements, including role-based access control, SSO integration, audit logging, and U.S. data residency obligations.

· Reduce operational cost and dependency on legacy infrastructure. Transition to a vendor-hosted, cloud-based SaaS platform that eliminates ODOT’s reliance on aging mainframe-dependent architecture and frees internal technical staff from system maintenance obligations.

SCOPE OF WORK/SPECIFICATIONS

See Attachment D Sample Statement of Work and Attachment H System Requirements.

1.1 PROJECT PHASES

Phased Implementation The CVIEW Replacement Project will be delivered across three phases. The phased approach allows ODOT to prioritize federal compliance and core platform deployment, transition source system integrations incrementally, and retire the legacy CVIEW environment in a controlled sequence. The legacy CVIEW system will remain in operation in parallel during Phases 1 and 2 to preserve continuity for enforcement, credentialing, and tax workflows until all functions are fully transitioned.

Phase 1 – Core CVIEW Deployment (Target: Q4 2027) Phase 1 establishes the core modernized CVIEW platform and prioritizes federal data ingestion and compliance certification. The selected Contractor will deploy the foundational system, implement SAFER carrier and vehicle snapshot ingestion (T0030 and T0028 files), enable carrier-level PRISM target logic, and deliver a roadside compliance user interface. Phase 1 also establishes CVIEW’s initial role in the ODOT data lakehouse as the authoritative source for federal carrier and safety data. The legacy CVIEW system continues full operation during Phase 1 as the system of record for credential data while the new platform is validated.

Phase 2 – ODOT Credential and Permit Integration (Target: July 1, 2029) Phase 2 integrates CVIEW with Oregon’s credentialing source systems and expands enforcement capabilities to the vehicle level. The Contractor will implement interfaces with IFTA, IRP, WMT, and the new CVR system; enable VIN-to-USDOT linkage to support vehicle-level PRISM target logic; and deploy the Carrier Account Reconciliation Hub and initial Transponder Management capabilities. The modernized CVIEW becomes the authoritative source for vehicle-to-carrier targeting and credential status during this phase, and the legacy system begins phased retirement of IRP and vehicle data functions.

Phase 3 – External Data Exchange and Ecosystem Completion (Target: Q4 2030) Phase 3 completes the modernization by integrating enforcement screening and data quality tools. The Contractor will implement the E-Screening and Weigh-In-Motion (“WIM”) integration module, connect ORION for permitting and size and weight compliance, enable the Inspection and Violation Feedback Loop, and complete Transponder Management capabilities. Upon successful completion of Phase 3, the legacy CVIEW system will be fully decommissioned. The modernized platform will serve as the system of record for all CVIEW services, including ITD Core certification, PRISM Full certification, enforcement dashboards, Green Light and WIM integration, and advanced analytics support.

PROCUREMENT REQUIREMENTS

MINIMUM QUALIFICATIONS

To be considered for evaluation, Proposer must:

· Be a registered vendor in OregonBuys, and

· Have implemented a commercially available, cloud-hosted CVIEW or comparable commercial vehicle information and credential display system currently in production with a minimum of two public sector transportation agencies.

MINIMUM SUBMISSION REQUIREMENTS

Proposal Submissions To be considered for evaluation, Proposal must contain each of the following elements (further detailed in Proposal Requirements section below) and must be organized as follows:

Section A

· Cover page (optional)(not to exceed 2 pages)

· Attachment C Proposer Information and Certification Sheet Attachment B Disclosure Exemption Certification (if applicable; see section 3.2.3 Proposal Format below) Section B Key Persons and Resumes (see section 3.3.4) Technical Proposal (see section 3.3.5) Attach as separate files:

Attachment E Price Proposal Form (in .docx format; see section 3.3.3) Attachment H System Requirements (in .xlsx format; see section 3.3.5) Attachment I Oregon Standards Spreadsheet (in .xlsx format; see section 3.3.6) See RFP section 5.3 for submittal requirements of the selected firm after award notice.

Redacted versions submitted in addition to the above per section 3.2.2 may be in PDF format. Submit redacted versions, if any, as separate files uploaded via the Attachments tab for this RFP in OregonBuys.

Proposal Page Limits Proposal is limited to 60 pages. Any pages exceeding this limit will not be provided to the evaluation committee or considered in the evaluation. The following items do not count toward the page limit:

Attachment B Disclosure Exemption Certification Attachment C Proposer Information and Certification Sheet with Appendix I References Redlined version of Attachment D Statement of Work (if applicable, see section 3.10.2.5) Attachment E Price Proposal Attachment H System Requirements Attachment I Oregon Standards Spreadsheet Proposal Format Proposal should follow the format and reference the sections listed in section 3.3 Proposal Requirements. Responses to each section and subsection should be labeled to indicate the item being addressed.

All required submittal items must be submitted via OregonBuys in Adobe Acrobat (pdf), Microsoft Word (docx) or Excel (.xlsx) format.

If Proposer believes any of its Proposal is exempt from disclosure under Oregon Public Records Law (ORS 192.311 through 192.478), Proposer shall submit a completed and signed Attachment B Disclosure Exemption Certification and a fully redacted version of its Proposal, clearly identified as the redacted version.

Electronic Submittal Provisions

PROPOSAL REQUIREMENTS

Proposal must address each of the items listed in this section and all other requirements set forth in this RFP. Proposer shall describe the Goods to be provided or the Services to be performed or both. A Proposal that merely offers to provide the Goods or Services as stated in this RFP may be considered Non-responsive to this RFP and will not be considered further.

Proposal should not include extensive artwork, unusual printing or other materials not essential to the utility and clarity of the Proposal. Do not include marketing or advertising material in the Proposal, unless requested. Proposal should be straightforward and address the requests of the RFP. Proposal containing unsolicited marketing or advertising material may receive a lower evaluation score if required information is difficult to locate.

Content incorporated by reference (for example, references to websites and links) will not be considered and will be redacted.

Proposer Information and Certification Sheet Proposer shall complete and submit Attachment C Proposer Information and Certification Sheet, with the “APPROVED” checkbox marked to certify approval of the Proposal and compliance with Oregon Tax Laws by a duly authorized representative empowered to bind the Proposer. Failure to demonstrate compliance with Oregon Tax Laws may result finding the Proposer non-Responsible (see OAR 137-047-0640(1)(b)(F).

Also mark the appropriate box for item 10 regarding Conflict of Interest (“COI”) disclosures. If disclosures are required for Proposer or any subs, use COI Disclosure Form(s) linked on Attachment C to make the disclosures.

References Provide three references from current or former client firms for similar projects performed within the last three years. List the reference contact information in Appendix 1 of Attachment C. References must be able to verify the quality of previous, related Work.

ODOT may check to determine if references provided support Proposer’s ability to comply with the requirements of this RFP. ODOT may use references to obtain additional information, or verify any information needed. ODOT may contact any reference (submitted or not) to verify Proposer’s qualifications.

Price Proposal Submit a detailed price proposal using Attachment E Price Proposal as a separate file uploaded via the Attachments tab for this RFP in OregonBuys.

Price Proposals will be available to the Evaluation Committee for reference during each round of competition.

Key Persons and their Resumes Specify the key persons to be assigned to this project, and include a current resume (not to exceed 2 pages each) for each key person that demonstrates the person’s qualifications and experience for the Work described in this RFP.

Technical Proposal The Technical Proposal is Proposer’s response to section 4.10.2. Proposer shall provide written responses to section 4.10.2 and its subsections, including a redlined Attachment D Statement of Work (see section 4.10.2.5) and a completed Attachment H System Requirements (see section 4.10.2.4.) Responses to each Evaluation Criteria in section 4.10.2 must be labeled to indicate the item being addressed.

Submit Attachment H System Requirements as a separate Excel file (.xlsx) uploaded via the Attachments tab for this RFP in OregonBuys.

Oregon Standards Spreadsheet Proposer shall follow the instructions found in the Attachment I Oregon Standards Spreadsheet and submit it as a separate Excel file (.xlsx) uploaded via the Attachments tab for this RFP in OregonBuys. The Proposer must provide responses to both the ‘Solutions Description’ tab (Column B) and the ‘Standards’ tab (specifically Columns D through L under the header ‘Phase 1 Bid Response’).

SOLICITATION PROCESS

PUBLIC NOTICE

The RFP and attachments are published in the OregonBuys eProcurement system (https://oregonbuys.gov/bso). RFP documents will not be mailed to prospective Proposers.

Modifications, if any, to this RFP will be made by written Addenda published in OregonBuys. Prospective Proposer is solely responsible for checking OregonBuys to determine whether or not any Addenda have been issued. Addenda are incorporated into the RFP by this reference.

PREPROPOSAL CONFERENCE

A Pre-Proposal conference will not be held for this RFP.

QUESTIONS / REQUESTS FOR CLARIFICATIONS

All inquiries, whether relating to the RFP process, administration, deadline or method of award, the intent or technical aspects of the RFP, contractual requirements, or any other provision must:

Be submitted in writing via email to the Purchaser identified in OregonBuys for this RFP. The email must include the RFP number and identify Proposer’s name and contact information;

Refer to the specific area of the RFP being questioned (i.e. page, section and paragraph number); and Be received by the due date and time for Questions/Requests for Clarification identified in the Schedule, RFP section 1.2.

SOLICITATION PROTESTS

Protests to RFP Prospective Proposer may submit a written protest of anything contained in this RFP, including but not limited to, the RFP process and Attachments. This is prospective Proposer’s only opportunity to protest the provisions of the RFP, except that Proposer may protest Addenda as provided below.

Protests to Addenda Prospective Proposer may submit a written protest of anything contained in the respective Addendum. Protests to Addenda, if issued, must be submitted by the date/time specified in the respective Addendum, or they will not be considered. Protests of matters not added or modified by the respective Addendum will not be considered.

Requirements for Protests All Protests must:

Be delivered via email to the Purchaser identified in OregonBuys for this RFP;

Reference the RFP number;

Identify prospective Proposer’s name and contact information;

Be sent by an authorized representative;

State the reason for the protest, including:

the grounds that demonstrate how the Procurement Process is contrary to law, Unnecessarily Restrictive, legally flawed, or improperly specifies a brand name; and evidence or documentation that supports the grounds on which the protest is based State the proposed changes to the RFP provisions or other relief sought;

Protests to the RFP must be received by the due date and time identified in the Schedule, RFP section 1.2;

Protests to Addenda must be received by the due date identified in the respective Addendum.

PROPOSAL SUBMITTAL VIA OREGONBUYS

Proposer is solely responsible for ensuring its Proposal and all required submittal items are submitted through OregonBuys in accordance with the RFP requirements before the Bid Opening Date. Proposals submitted by any other means will be rejected.

ODOT is not responsible for any delays by transmission errors or delays, or for any misdelivery for any reason. Additional information may be found in the OregonBuys Terms of Use.

PROPOSAL MODIFICATION OR WITHDRAWAL

If a Proposer wishes to withdraw or modify a submitted Proposal, Proposer must do so using the “Withdraw Quote” button in OregonBuys prior to the Bid Opening Date and time for this RFP in OregonBuys. Proposal withdrawals and modifications must be in conformance with requirements set forth in OAR 125-247-0440.

PROPOSAL DUE

A Proposal (including all required submittal items) must be received in OregonBuys on or before the Bid Opening Date and time for this RFP specified in OregonBuys.

A Proposal received after the Bid Opening Date and time is considered LATE and will NOT be accepted for evaluation.

PUBLIC OPENING

There will be no public Opening of Proposals. Proposals received will not be available for inspection until after the evaluation process has been completed and the Notice of Intent to Award is issued pursuant to OAR 137-047-0630. However, ODOT will record and make available the identity of all Proposers after Opening.

PROPOSAL REJECTION

ODOT may reject a Proposal for any of the following reasons:

Proposer fails to substantially comply with all prescribed RFP procedures and requirements.

Proposer has liquidated and delinquent debt owed to the State or any department or ODOT of the State.

Proposer fails to meet the responsibility requirements of ORS 279B.110.

Proposer makes any contact regarding this RFP with State representatives such as State employees or officials other than the Purchaser or persons authorized by the Purchaser, or makes inappropriate contact with the Purchaser.

Proposer attempts to influence a member of the Evaluation Committee.

Proposal is conditioned on ODOT’s acceptance of any other terms and conditions or rights to negotiate any alternative terms and conditions that are not reasonably related to those expressly authorized for negotiation in the RFP or Addenda.

EVALUATION PROCESS

Responsiveness and Responsibility Determination Responsiveness Determination A Proposal received prior to the Bid Opening Date for this RFP will be reviewed to determine if it is Responsive to all RFP requirements including compliance with Minimum Qualifications section and Minimum Submission Requirements section. If the Proposal is unclear, the Purchaser may request clarification from Proposer. However, clarifications may not be used to rehabilitate a Non-responsive proposal. If the Purchaser finds the Proposal Non-responsive, the Proposal may be rejected; however, ODOT may waive mistakes in accordance with OAR 125-247-0470.

Responsibility determination ODOT will determine if an apparent successful Proposer is Responsible prior to award and execution of the Contract. Selected Proposer shall submit a signed Attachment G Responsibility Inquiry form following receipt of Intent to Award notice as required in RFP section 5.3.4.

At any time prior to award, ODOT may reject a Proposer found to be not Responsible.

Evaluation Criteria Each Proposal meeting all Responsiveness requirements will be independently evaluated by members of an Evaluation Committee. Evaluation Committee members may change and ODOT may have additional or fewer evaluators for optional rounds of competition. Evaluators will assign a score for each evaluation criterion listed below in this section up to the maximum points available listed for each scored item.

Purchaser may request further clarification to assist the Evaluation Committee in gaining additional understanding of a Proposal. A response to a clarification request may only clarify or explain portions of the already submitted Proposal and may not contain new information not included in the original Proposal.

Proposer’s Technical Proposal must include written responses to sections 4.10.2.1, 4.10.2.2, 4.10.2.4, 4.10.2.5, and 4.10.2.6.

Evaluation Item 1 – Proposer Qualification Max Points: 25 Proposers must provide three references from public-sector transportation or motor carrier state ODOT clients that are current users of the system offered in this proposal. References must collectively demonstrate both the production status of the system and the Proposer's minimum three years of service to qualifying agencies.

Demonstrate relative experience and qualifications regarding the quality, delivery, and performance of the projects:

· Briefly describe the reference projects in Attachment C, Appendix 1, and indicate whether the services were accomplished within Proposer’s original estimated budget and schedule. If the original estimated budget or schedule needed revision, explain why.

· Summary of services provided for implementation, integration, configuration, training, support, and ongoing maintenance of the CVIEW system.

· Include resumes for key personnel, not to exceed 2 pages per key person. Describe the experience and qualifications of all proposed Project team members. Identify whether each individual is an employee or a subcontractor.

Evaluation Item 2 – Essay Response Max Points: 30 Describe how the proposed system and the Proposer's implementation approach will meet the items listed in this section. Pages exceeding the limit will be removed prior to distribution to the evaluation committee.

· Describe how the proposed system is designed to support Oregon's ITD Core and PRISM Full certification requirements, including how the system will maintain certification-required data exchanges and processing during the transition from the legacy CVIEW system, and how your support model addresses FMCSA-driven changes to certification requirements over the contract period.

· Describe how the proposed system supports API-based integration with ODOT source systems (IRP, IFTA, WMT, CVR) and downstream consumers (Green Light, WIM, ORION, ODOT data lakehouse), replacing current direct database dependencies with documented, versioned interfaces.

· Describe system capabilities relevant to CVIEW's operational users, including enforcement officers, credentialing staff, audit staff, and tax staff. Include how the system supports role-appropriate views, mobile-friendly access, and the notes capability required for enforcement workflows.

Evaluation Item 3 – Conformity with Requirements Pass/Fail Proposer must complete Attachment H System Requirements. The contents of this section will be used as a reference for the product evaluation and testing if ODOT elects to conduct additional round(s) of competition.

ODOT’s requirements are identified with an ‘M’ for MANDATORY and ‘D’ for DESIRABLE under the Required column.

For each requirement listed in Attachment H System Requirements, Proposers must provide a self-assessment score using the scale below. Scores must reflect the capability of the proposed system as offered, without assuming future development commitments.

0 - Not Available 1 - Requires database & application layer customization 2 - Requires minor customization to the application layer 3 - Available: Vendor makes configuration changes 4 - Available: ODOT makes configuration changes 5 - Available out of the box ODOT will use self-assessment scores in combination with the written explanations and reference checks to evaluate the completeness and credibility of each Proposer's response.

A requirement marked as 0 (or no response) for a MANDATORY item will be considered a Fail for this evaluation criteria and the Proposal will be rejected.

Evaluation Item 4 – System Requirements Max Points: 100 Describe how the proposed system meets the requirements set forth in Attachment H System Requirements. Responses to each category are worth the points defined below.

Evaluation Item 5 – Implementation Plan and SOW Max Points: 40

· Describe your intended implementation plan across all three phases, including your project schedule, approach and methodology to plan, design, configure, integrate, test, deploy, and support the modernized CVIEW system as described in this RFP.

· Describe your approach to parallel operation between the legacy and modernized CVIEW systems during Phases 1 and 2, including how you will maintain data consistency, manage user transition, and coordinate legacy decommissioning upon Phase 3 completion.

· Describe how you will manage a phased engagement in which individual phases may be subject to separate funding authorizations, schedule gaps between phases, or competing ODOT priorities, including how staffing, scope, and contractual obligations are structured to accommodate those conditions.

· Describe any changes to Attachment D Statement of Work that you propose to support your implementation plan, including any assumptions about ODOT responsibilities, source system availability, or federal system access that underpin your proposed approach.

· Describe your approach to API delivery and support, including how APIs will be documented, versioned, and made available to ODOT and its source system partners, and how you will identify, triage, and resolve issues that arise during ODOT-led integration and testing activities.

· Describe your approach to federal system changes that may occur during the contract period, including SAFER schema updates, PRISM API version changes, and new FMCSA certification requirements, and how those changes are absorbed within the standard support model versus treated as out-of-scope work.

Evaluation Item 6 – Viable Additional Features Max Points: 10 Describe capabilities or services offered by the Proposer that this RFP does not explicitly require, but that would add operational value to ODOT's CVIEW program. Responses should be grounded in the CVIEW operating context and may address areas such as advanced analytics or anomaly detection on commercial vehicle data, expanded e-screening capabilities beyond the required credential set, data quality monitoring and alerting for federal data ingestion, integration capabilities relevant to future ITD Expanded certification, or enhanced reporting tools for CCD operational and compliance staff. Describe each capability, how it would benefit ODOT operations, and whether it is included in the proposed pricing or available at additional cost.

Evaluation Item 7 – Clarity of Proposal Max Points: 5 Proposers do not need to provide a written response to this criterion.

The proposal must be organized using the headings in the Evaluation Criteria section (i.e., list the bullet point Proposal is responding to). Proposals will be scored by evaluators on the following factors: Proposal format; ease of finding clear, concise responses that correlate with the order of evaluation criteria in this RFP; and Proposers ability to follow instructions.

PRICE EVALUATION Max Points: 30 Following scoring and ranking of Proposals based on the qualifications-based criteria, the Purchaser will conduct the price evaluation. The Purchaser will award a price score to each Price Proposal based upon the percentage of the proposed price as compared to the lowest Proposer’s price using the following formula:

price being scored

ODOT reserves the right to negotiate pricing and billing rates with the successful Proposer.

POINT AND SCORE CALCULATIONS

Scores, except scores for Price Proposals, are the points assigned by each evaluator. The maximum points possible for each evaluation item are listed in the table below. The Purchaser will average all scores for each evaluation criterion. The score for each Price Proposal is calculated by the Purchaser as stated in section 4.10.3 Price Evaluation.

Fractions will be rounded to the nearest whole number.

TOTAL POINTS POSSIBLE: 240

RANKING OF PROPOSERS

The Purchaser will average the scores for each Proposal in a given round of competition (calculated by totaling the points awarded by each Evaluation Committee member and dividing by the number of members).

The Purchaser will combine the average score for each Proposal with Proposer’s Price Proposal score.

After any applicable preference has been applied, the Purchaser will determine the rank of each Proposal, with the highest score receiving the highest rank, and successive rank order determined by the next highest score.

ODOT may, in ODOT’s sole discretion, determine an apparent successful Proposer with no additional rounds of competition. If additional rounds are conducted, ODOT will rank advancing Proposers at the conclusion of each subsequent round and may determine an apparent successful Proposer at any time during the solicitation process.

NEXT STEP DETERMINATION

At the conclusion of a round of competition, ODOT may choose to conduct one or more additional round(s) of competition as described in section 4.14 if, in ODOT’s sole discretion, it is in the best interest of the State.

Competitive Range Determination If ODOT, in its sole discretion, determines that one or more additional rounds of competition is necessary, it will select a Competitive Range to indicate the Proposers that will be invited to participate in a subsequent round. The Competitive Range will, to the greatest extent practicable, consist of the three highest ranked Proposers. ODOT, in its sole discretion, may increase or decrease the number of Proposers selected for the Competitive Range if there is a natural break in the scores. ODOT will post a notice in OregonBuys of its Competitive Range Determination and provide details about the process and schedule for the subsequent round.

Competitive Range Protest Proposers excluded from a round may submit a written protest of Competitive Range. Protests must:

Be emailed to the Purchaser;

Reference the RFP number;

Identify Proposer’s name and contact information;

Be sent by an authorized representative;

State the reason for the protest; and Be received within 7 calendar days after issuance of the Notice of the Competitive Range unless a different due date and time is specified in such notice.

ODOT will address all protests within a reasonable time and will issue a written decision to the respective Proposer. Protests that do not include the required information may not be considered by ODOT.

ADDITIONAL ROUNDS (Optional at ODOT’s discretion) Interviews/Follow-up Questions If ODOT determines interviews or follow-up questions, or both, are necessary, Proposers in the Competitive Range will be invited to participate and the following will apply:

· The interviews and follow-up questions will have a maximum score of 50 points each.

· Interviews may be in person at a location determined by ODOT; however, ODOT may elect to conduct interviews via teleconference or video conference.

· As an alternative to interviews, ODOT may elect to send follow-up questions via email to Proposers in the Competitive Range. ODOT must receive Proposers’ responses to the follow-up questions by the deadline set forth in the email to Proposers. ODOT may conduct face-to-face interviews if determined necessary after conducting written follow-up questions.

· Further details regarding interviews or follow-up questions will be included with Notice of Competitive Range.

Best and Final Offers Proposers in the Competitive Range may be invited by the Purchaser to submit Best and Final Offers. The written Best and Final Offer (“Revised Proposal”) must be submitted on or before the due date and time set forth in the notice of Competitive Range. LATE REVISED PROPOSALS WILL NOT BE ACCEPTED.

If Proposer elects not to submit a Revised Proposal, Proposer’s initial Proposal will be accepted as the Best and Final Offer and evaluated accordingly.

Best and Final Offers must be submitted in Writing in the form of an amendment to the Proposer’s initial Proposal. Best and Final Offers must comply with the following requirements and specifications:

· Identify Proposer’s business name and reference the RFP number for this solicitation; and

· Submit an electronic copy of the revised Proposal signed by Proposer’s authorized representative; and

· Clearly identify the information included in Proposer’s initial Proposal that Proposer intends to amend or replace in terms of the page, section and paragraph of Proposer’s initial Administrative, Technical or Price Proposal; and

· Include a Best and Final Offer letter, signed by Proposer’s authorized representative, which summarizes the Proposal aspects amended by the Best and Final Offer and states that the information included in the Best and Final Offer supersedes the corresponding information included in Proposer’s Proposal submitted on or before the date provided in the notice of competitive range; and

· Include all information requested in the Best and Final Offer letter.

Product Demonstrations Proposers in the Competitive Range may be invited to participate in product demonstrations. The primary purpose of product demonstrations is to provide an opportunity for ODOT to observe and verify the functions and features of the proposed System. Proposers will be required to demonstrate their proposed solutions in detail and validate the functionality of the proposed software.

ODOT will notify Proposers in advance (approximately two weeks) of the demonstration schedule and requirements. ODOT anticipates that demonstrations will require a half-day for each Proposer in the Competitive Range. Demonstrations may be held in-person or via video conference, or both.

Either the proposed project manager or lead analyst must participate in the demonstration; it is ODOT’s preference that both project team members participate. A significant portion of the demonstration should be given by the proposed project manager or lead analyst.

ODOT will provide Proposers with instructions in advance of the demonstration. All Proposers will be provided the same instructions and will be asked to discuss the same issues.

During the demonstration, ODOT expects Proposers to demonstrate the standard implementation without demonstration-specific development. Ideally, ODOT should be able to replicate the results shown using the Proposer’s standard software configuration tools.

If the demonstration does include demonstration-specific development, Proposer must clearly explain what portions of the demonstration utilize demonstration-specific development and the reason it is required.

Product demonstrations are worth a maximum of 100 points. Fractions will be rounded to the nearest whole number.

SCORING AND RANKING OF PROPOSERS FOR SUBSEQUENT ROUNDS

If ODOT conducts two or more rounds of competition, the rounds will be scored independently. Once the ranking from a previous round is complete and a Competitive Range has been determined, Proposers participating in a subsequent round will compete on an equal basis – scores from the previous round will be set aside and will not carry over.