This Solicitation opportunity from Oregon was posted on September 3, 2025. The submission period has ended. Browse the details below for market research, or find similar active opportunities.
HighAI Summary for 00011625 CDSR RFP Attachment H - Sample SOW: A sample Statement of Work (SOW) for the CDSR RFP, detailing ten primary tasks including project management, requirements gathering, environment configuration, data migration, software testing/UAT, installation, training, cutover, and warranty/maintenance support.
DOCX
DOCX, High priority: read this first2 pages · rfp
HighAI Summary for Attachment D - Proposer References Submission Form for RFP Section 3.3.2: This document is Attachment D of a Request for Proposal (RFP) and provides instructions for proposers to submit three client references as required by RFP section 3.3.2. Each reference entry requires detailed information including the reference firm/client name, project title, proposing firm’s project manager contact details, project location, a brief description of the project and the proposing firm’s role, contract and work order numbers, contract start and completion dates, client budget, contract amount, and client point of contact information. The purpose of this attachment is to verify the proposer’s past performance and experience relevant to the contract opportunity.
DOCX
DOCX, High priority: read this first2 pages · rfp
HighAI Summary for Attachment E - Solution Pricing Form for RFP Evaluation: Attachment E provides the required format and instructions for proposers to submit their solution pricing for the agency's RFP. It specifies an all-inclusive licensing model with a single price for COTS software licenses regardless of user, server, or CPU count. The pricing form includes detailed cost categories such as implementation services, software costs, hosting costs, licensing, support and maintenance for up to five years, and other potential costs like solution enhancements. Proposers must populate a price table aligned with tasks described in the Sample Statement of Work (Attachment H), including all labor, overhead, profit, and direct expenses. Supporting information must accompany the pricing, preferably as fixed price line items, detailing project planning, fit/gap analysis, configuration, data migration, testing, and training. Licensing details should specify license types by user, PC, or server. The agency estimates 100 internal users and unlimited external users for the solution. This attachment will be used to inform the RFP evaluation criteria related to value assessment.
DOCX
DOCX, High priority: read this first2 pages · rfp
HighAI Summary for Attachment K - Key Person Resumes for RFP S-73000-00011625: This document is Attachment K to RFP S-73000-00011625 and requires submission of resumes for up to four key personnel proposed for the project. It provides a structured format to detail each individual's name, title, relevant project experience, firm affiliation (if subcontractor), role on the project, active professional registration status in Oregon including discipline, education, and years of experience in the proposed role. The attachment supports evaluation of personnel qualifications as part of the proposal submission.
DOCX
DOCX, High priority: read this first83 pages · contract-document
HighAI Summary for Oregon DOT IT Professional Services Contract for Crash Data System Replacement: This document is a professional services contract between the State of Oregon Department of Transportation (ODOT) and a contractor for the Crash Data System Replacement (CDSR) project. It formalizes the agreement following a successful RFP process, outlining the contractor's responsibilities to deliver a commercial off-the-shelf crash data system solution, including professional services and knowledge transfer. The contract specifies terms such as the effective date, duration, scope of services, performance standards aligned with PMI and ISO methodologies, and compliance with Oregon DAS IT policies. It details the delivery and acceptance process for project deliverables, including timelines for review, acceptance criteria, and remedies for non-acceptance. The contract also addresses cooperation requirements between contractor, agency, and third parties, as well as provisions for delays or cost increases caused by the agency's failure to provide necessary resources. Overall, this contract governs the execution, delivery, and acceptance of IT services critical to replacing the state's crash data system.
DOCX
DOCX, High priority: read this first2 pages · rfp
HighAI Summary for Proposer Information and Certification Sheet for RFP Submission: This document is the Proposer Information and Certification Sheet attached to a Request for Proposal (RFP). It requires the proposer to provide legal and contact information and certify understanding and acceptance of the RFP requirements and contract terms. The proposer affirms compliance with tax laws, non-discrimination policies, wage equality, and conflict of interest disclosures. It also certifies that the proposer and its associates are not debarred or suspended and have no conflicts of interest. The document includes certifications against collusion, fraud, and false claims under Oregon law. The authorized representative must approve and sign the form, binding the proposer to the stated certifications and commitments. This sheet is critical for validating proposer eligibility and compliance prior to contract award.
DOCX
DOCX, High priority: read this first3 pages · other
HighAI Summary for Responsibility Inquiry Form for Contractor Evaluation Prior to Award: This document is a Responsibility Inquiry form used by the Agency to assess a firm's responsibility before awarding and executing a contract. It requires the firm to provide detailed information about its financial status, resources, past contract performance, legal and tax compliance, licensing, and other relevant factors. The Agency may request additional documentation such as financial statements, bonding capacity, and performance records. Failure to provide requested information or demonstrate responsibility may result in rejection of the offer. The form includes specific questions about financial distress, contract defaults, criminal charges related to contracts, bankruptcy, tax delinquencies, licensing, and pay equity certification. It also requests information about warranty service representatives if the contract involves equipment sales. The form must be signed by an authorized representative certifying the accuracy and completeness of the responses.
XLSX
XLSX, High priority: read this firstspecifications
HighAI Summary for RFP S-73000-00011625 Crash Data System Replacement (CDSR) - Attachment I: Attachment I - Solution Requirements for the Crash Data System Replacement (CDSR) project under RFP S-73000-00011625. This document is a technical requirements matrix (worksheet) for vendors to indicate compliance with 78 total requirements across 14 sections, including General, Audit and Event Logs, Installation, Integration, and Security. It includes specific mandatory and desired technical specifications and instructions for proposer completion.
DOCX
DOCX, High priority: read this firstamendment
HighAI Summary for S-73000-00011625 Addendum #1 - Crash Data System Replacement (CDSR): Issued September 22, 2025, this addendum modifies RFP #S-73000-00011625 for the Crash Data System Replacement (CDSR). Key changes include the addition of supplemental technical information links in the Scope of Work, updates to proposal submission requirements (making the cover letter optional), an increase in the Technical Proposal page limit from 35 to 45 pages, and refined formatting and evaluation criteria for essay responses.
DOCX
DOCX, High priority: read this firstamendment
HighAI Summary for S-73000-00011625 Addendum #2 - Crash Data System Replacement: Addendum #2 dated September 25, 2025, for RFP #S-73000-00011625 (Crash Data System Replacement). The primary purpose of this amendment is to extend the Bid Opening Date and time in OregonBuys to October 20, 2025, at 8:00 AM PST.
DOCX
DOCX, Medium priority4 pages · other
MediumAI Summary for Attachment L - Abbreviations and Definitions for Oregon DOT RFP S-73000-00011625: This document, Attachment L, provides a comprehensive list of abbreviations and definitions used throughout the Oregon Department of Transportation's Request for Proposal (RFP) #S-73000-00011625 and its associated Sample Contract. It clarifies terminology related to the Crash Data System (CDS) replacement project, including key terms such as Active Directory, Agency, Deliverables, Milestones, Service Level Agreement (SLA), and various organizational units and technical terms. The definitions ensure consistent understanding of contract terms, roles, processes, and technical components among all parties involved in the RFP and resulting contract. This attachment supports clear communication and interpretation of the contract documents but does not itself contain solicitation or contractual requirements.
DOCX
DOCX, Medium priority3 pages · other
MediumAI Summary for Disclosure Exemption Certification for Oregon RFP Proposal: This document is a Disclosure Exemption Certification signed by an authorized representative of a proposer responding to a Request for Proposals (RFP) issued by the State of Oregon. It certifies the proposer's awareness of the RFP and the proposal contents, and asserts that certain information within the proposal, detailed in an attached Exhibit A, is exempt from public disclosure under Oregon's Public Records Law and the Uniform Trade Secrets Act. The exempt information includes trade secrets or proprietary data that provide a competitive business advantage and are subject to confidentiality protections. The certification acknowledges that disclosure decisions may ultimately depend on official or judicial rulings.
DOCX
DOCX, Medium priority24 pages · other
MediumAI Summary for State of Oregon Government Contract Solicitation Document: This document appears to be a government contract-related publication from the State of Oregon. It includes the State of Oregon logo and extensive text, likely describing contract requirements, terms, or related information. However, the content provided is largely an image placeholder and a lengthy encoded string, with no clear solicitation type, deadlines, or response instructions explicitly stated. Due to the lack of explicit solicitation or contract award details, the document is classified as 'other' with medium priority for response, pending further clarification or additional documentation.
DOCX
DOCX, Low priority5 pages · other
LowAI Summary for ODOT Enterprise Technology Infrastructure Standards for Vendors and RFPs v1.7: This document outlines the Oregon Department of Transportation (ODOT) Enterprise Technology Infrastructure Standards intended as a reference for vendors proposing solutions to RFPs. It covers network protocols, security requirements including compliance with Statewide Security Standards and Oregon's Identity Protection Act, software and hardware standards, database management systems, backup procedures, and general implementation guidelines. Vendors are advised to align with ODOT's standards to minimize risk and cost, including using Microsoft Active Directory, standard operating systems, and approved development languages. The document emphasizes security controls, data classification, user permissions, and system compliance verification. No response is required from vendors as this is a guidance document to support RFP proposals.
DOCX
DOCX, Low priorityq-and-a
LowAI Summary for S-73000-00011625 Crash Data System Replacement (CDSR) Q&A Vol. 1: This document contains ODOT's responses to vendor questions (Volume 1) regarding RFP S-73000-00011625 for the Crash Data System Replacement (CDSR), dated September 22, 2025. It provides clarifications on the implementation timeline (summer 2028), submission requirements for Attachment D, technical specifications for bulk data updates, geospatial query examples, data retention, and security/SSO standards.
DOCX
DOCX, Low priorityq-and-a
LowAI Summary for S-73000-00011625 Crash Data System Replacement (CDSR) Q&A Vol. #2: This document contains the second volume of official responses from the ODOT Procurement Office to questions submitted by interested parties regarding RFP S-73000-00011625 for the Crash Data System Replacement (CDSR). Dated September 23, 2025, it provides clarifications on data collection methods, current manual entry percentages, validation rule references, and links to sample crash report forms.
AI Contract Breakdown
Uniform Contract Format
Sign up to view the full breakdown with detailed analysis of each section.
Timeline
1 update
PhaseClosed
Posted
Solicitation
Deadline changed
Response deadline changed from Oct 20, 2025 to Oct 8, 2025.
Response Deadline
Deadline has passed
Submission Closed
Find active opportunities like this
Get full access to discover similar active contracts, track opportunities, and build proposals with AI assistance.
This Request for Proposal is for a commercial off the shelf (COTS) Crash Data System (CDS). Agency is seeking a replacement for its current in-house developed system, CDS. The primary purpose of the Contract resulting from this RFP is to retain a Contractor to provide Goods and Services related to the integration, configuration, implementation, hosting, and maintenance of a new, fully integrated CDS system (the Solution). Refer to RFP Sections 2.3 and 2.4 for more information.
More opportunities from Oregon Department of Transportation
