This Solicitation opportunity from Virginia was posted on November 4, 2026. The submission period has ended. Browse the details below for market research, or find similar active opportunities.
CAT INTELLIGENT TRANSPORTATION SYSTEM (ITS)
Contract Overview
Solicitation details, issuing organization, response deadlines, documents, and interested companies for this government contract opportunity.
Active Opportunities Like This One
AI Contract Overview
Charlottesville Area Transit (CAT) is soliciting proposals under RFP 27-17 for a term contract to purchase, deliver, install, and maintain a comprehensive Intelligent Transportation System (ITS), specifically focusing on Computer-Aided Dispatch (CAD) and Automatic Vehicle Location (AVL) systems. The project aims to modernize transit operations for a fleet of 47 vehicles, improving real-time operational management and rider information through GTFS/GTFS-Realtime integration. The contract structure consists of an initial one-year base term with four optional one-year renewals. The scope includes full system implementation, cloud-based hosting, software licensing, and staff training, with a mandatory six-week acceptance testing period following system go-live. The procurement allows for partial-component proposals, though preference is given to integrated, complete solutions. Key technical requirements include the replacement of most existing ITS hardware, such as interior LED signage and cellular routers, while retaining the AngelTrax surveillance system and existing PA systems. The City prefers integration with Microsoft Entra ID for single sign-on and multifactor authentication. While the existing UTA automatic passenger-counting equipment will not be mandatorily replaced, vendors are encouraged to propose integration or optional replacement. Evaluation is based on a weighted scale: proposed systems and technical approach (35%), qualifications and experience (25%), implementation and project management (20%), and price (20%). Compliance with Federal Transit Administration (FTA) clauses and Build America, Buy America (BABA) standards is required. Additionally, the contractor must maintain cyber liability insurance of 5 million dollars. Proposals must be submitted electronically via the OpenGov portal by November 9, 2026, and must include a total proposed cost for the full potential five-year term, itemizing one-time implementation fees versus recurring annual costs.
General Info
Place of Performance
VA, USASet-Aside
Documents
13AI Contract Breakdown
Uniform Contract FormatSign up to view the full breakdown with detailed analysis of each section.
View Full BreakdownThis one is closed. Find the next one like it.
Open contracts like this one, right now:
- Cybersecurity Maturity Model Certification (CMMC) Program ServicesOpen now
- CIT01277069_System Implementation ServicesOpen now, due in 28 days
Ask CLEATUS
I've read this contract. Ask me anything.
Timeline
Submission Closed
Organization & Contact Information
Interested Companies (46)
See All 46 Interested Companies
Get full access to view all interested companies, their contact details, and full contractor profiles.
Full Description
Addendum #1: 1. Section V – Statement of Needs C. Transit CAD, AVL and ITS Components – 1. Project Overview and Components The component table has been revised to remove the vehicle quantity columns and associated component applicability designations. The revised table identifies the ITS components requested under this solicitation. Offerors shall refer to the revised "CAT Fleet of Vehicles" attachment for current fleet inventory and vehicle quantities when preparing their proposals. All other requirements under this subsection remain unchanged. 2. Revised CAT Fleet of Vehicles Attachment The "CAT Fleet of Vehicles" attachment has been revised to reflect CAT's current fleet of forty-seven (47) vehicles. The revised attachment supersedes and replaces the previously issued "CAT Fleet of Vehicles" attachment. Offerors shall use the revised attachment when preparing their proposals. 3. Other Terms and Conditions Except as expressly modified by this addendum, all other terms, conditions, specifications, and requirements of RFP 27-17 remain unchanged.
Addendum #2: Clarification of Component Proposals and Evaluation Criteria: 1. Section V - Statement of Needs C. Transit CAD, AVL and ITS Components - 1. Project Overview and Components Will CAT accept proposals for one or more ITS components, including proposals addressing only a portion of an individual component? Yes Offerors shall clearly identify the components, services, and functionality included in their proposals, along with any exclusions, limitations, and integration requirements. While partial-component proposals will be accepted, preference will be given to proposals offering complete components that satisfy all applicable requirements identified in the Statement of Needs. CAT's overall preference is to obtain a complete, integrated ITS solution that meets the requirements of this solicitation. 2. Section VII – Evaluation and Award Criteria Criterion 1 – Proposed Systems, Services and Technical Approach CAT will evaluate the proposed systems, services, and technical approach based on the offeror's ability to meet the requirements identified in the Statement of Needs. Consideration will be given to the number and range of components offered, the completeness of each proposed component, system integration capabilities, and the offeror's ability to provide a complete ITS solution. Proposals offering complete components will receive greater consideration than proposals offering only partial functionality.Preference will be given to proposals offering a complete, integrated ITS solution. Partial-component proposals will remain eligible for consideration but will not receive the same preference as proposals offering complete components. 3. Clarification of Pricing Evaluation Pricing will be evaluated in accordance with the established evaluation criteria and in relation to the scope of components and services proposed. CAT will consider the overall value of each proposal, including the completeness of the proposed solution, integration capabilities, implementation costs, licensing, maintenance, support, and other applicable costs. A proposal offering additional components or a more complete solution will not automatically be selected solely on that basis. Pricing and all other applicable evaluation criteria will be considered in determining the proposal that provides the best overall value to CAT. 4. Other Terms and Conditions Except as expressly modified by this addendum, all other terms, conditions, specifications, and requirements of RFP 27-17 remain unchanged.
Addendum #3: The purpose of this Addendum is to clarify CAT's requirements regarding the replacement of existing Intelligent Transportation System (ITS) equipment, the removal and handling of existing equipment, and integration with equipment designated to remain in service. This Addendum modifies Section V – Statement of Needs 1. AMENDMENT TO SECTION V.C.1 – PROJECT OVERVIEW AND COMPONENTS Section V.C.1 of the Statement of Needs is hereby amended by replacing the introductory paragraphs preceding the component table with the following: 1. PROJECT OVERVIEW AND COMPONENTS CAT is seeking to procure a Computer-Aided Dispatch/Automatic Vehicle Location (CAD/AVL) system and Intelligent Transportation System (ITS) components to support efficient and effective transportation operations. The components may be procured individually or as part of a complete solution. Offerors may submit proposals for one or more of the components identified below. For each component proposed, offerors shall provide a complete solution that meets the applicable requirements of the solicitation. Offerors shall identify any dependencies or compatibility requirements necessary for their proposed components to function properly with other ITS components. Equipment replacement and retention requirements are identified in Section V.C.3 – CAT Technology Overview. Questions related to each component are provided in the attachment titled "Component Requirements Questions and Details." Offerors shall provide a complete response to all applicable questions and describe how their proposed solution meets or exceeds the requirements and addresses the identified objectives. 2. AMENDMENT TO SECTION V.C.3 – CAT TECHNOLOGY OVERVIEW Section V.C.3 of the Statement of Needs is hereby deleted in its entirety and replaced with the following: 3. CAT TECHNOLOGY OVERVIEW CAT currently utilizes various technology systems and equipment to support its transit operations. A detailed listing of CAT's existing ITS technologies, systems, and vendors is provided in the attachment titled "CAT Technology Overview." CAT intends to replace all existing ITS equipment associated with the components identified in this solicitation, except for equipment specifically identified below as remaining in place. Offerors shall review the CAT Technology Overview attachment to understand CAT's existing technology environment and the equipment subject to replacement. Equipment Replacement Requirements Equipment subject to replacement includes, but is not limited to: Automatic Passenger Counter (APC) equipment, including the existing UTA system. CAT is not committing to replacing its existing APC equipment at this time but is interested in reviewing the options vendors offer. Replacement may be considered in the future. Vendors should describe compatibility with CAT's existing APC equipment and identify any proposed replacement options and associated costs separately. Interior LED signage. Exterior destination signs, including existing Luminator equipment. Onboard monitors and infotainment displays. Cellular routers and associated connectivity hardware. Computer-Aided Dispatch/Automatic Vehicle Location (CAD/AVL) equipment. Other existing ITS equipment associated with the components being proposed. The successful offeror shall furnish and install all new equipment, hardware, software, and associated components necessary to provide a complete and fully operational solution for each ITS component awarded. Removal and Installation Requirements The successful offeror shall be responsible for removing existing ITS equipment designated for replacement and furnishing, installing, configuring, integrating, and testing all new equipment necessary to provide a complete and operational solution for each ITS component awarded. All equipment removed shall remain the property of the City of Charlottesville unless otherwise authorized in writing by the City. CAT shall determine which removed equipment will be retained and which equipment will be disposed of. The successful offeror shall coordinate with CAT regarding the handling, storage, transfer, and disposal of removed equipment. No equipment shall be disposed of without prior written authorization from the City. The successful offeror shall ensure that removal and installation activities do not damage or interfere with existing equipment designated to remain in place. All costs associated with equipment removal, handling, installation, configuration, integration, and testing shall be included in the offeror's proposed pricing. Existing Equipment to Remain The following existing equipment shall remain in place and shall not be removed or replaced: AngelTrax Surveillance Camera System: The existing AngelTrax surveillance camera system shall remain in place. Integration is not mandatory; however, CAT would prefer the systems to integrate so operators can use a single login across the onboard systems. Vendors should describe their ability to support this functionality and identify any associated requirements and costs. Interior and Exterior Speakers and Public Address (PA) Systems: Existing interior and exterior speakers and PA systems shall remain in place. Proposed ITS equipment shall integrate with these existing systems as necessary to meet the requirements of the solicitation. Partial-Component Proposals Offerors may submit proposals for one or more ITS components as permitted under Section V.C.1. Equipment replacement, removal, installation, and associated requirements shall apply to the ITS components included in each offeror's awarded scope. The successful offeror shall be responsible for coordinating any necessary integrations with other ITS components to ensure compatibility and proper system functionality. 3. EXTENSION OF PROPOSAL SUBMISSION DEADLINE The City of Charlottesville hereby extends the proposal submission deadline for RFP 27-17 – CAT Intelligent Transportation System (ITS). Original Proposal Due Date: November 2, 2026, at 2:00 PM Eastern Time. Revised Proposal Due Date: November 9, 2026, at 2:00 PM Eastern Time. All proposals must be submitted electronically through OpenGov by the revised deadline. All other terms, conditions, specifications, and requirements of the solicitation remain unchanged unless specifically modified by this Addendum.
Addendum #4: Clarifications and Revisions to Solicitation Requirements 1. Purpose The purpose of this addendum is to clarify and revise certain requirements of RFP 27-17 relating to destination sign hardware, authentication and identity management, accessibility and third-party integrations, existing automatic passenger-counting equipment, acceptance testing, system availability, service-level credits and remedies, contract pricing, and application and content escrow. The revisions contained herein supersede conflicting provisions of the original solicitation or previously issued addenda only to the extent expressly stated herein. 2. Destination Sign Hardware Requirements A. Revision to Section V.C.3 – CAT Technology Overview Section V.C.3 is hereby amended to include the following clarification: CAT will consider the furnishing and installation of new exterior destination sign hardware as a separately priced optional item. Offerors shall describe their proposed solution's compatibility with CAT's existing destination signs and identify any associated integration requirements, limitations, dependencies, or costs. Offerors proposing new exterior destination sign hardware shall separately itemize all associated equipment, installation, integration, and related costs. B. Modification to Addendum No. 3 This addendum supersedes the portion of Addendum No. 3 requiring replacement of existing exterior destination sign hardware. Replacement of existing exterior destination sign hardware is no longer mandatory as part of the base proposal. All other equipment replacement requirements established by Addendum No. 3 remain unchanged unless expressly modified herein. C. Continued System Requirements The proposed solution shall continue to satisfy all applicable requirements of Section V – Statement of Needs, including automated vehicle announcements (AVA), onboard passenger information, and applicable system integration requirements. This revision does not eliminate or modify the requirements for new interior LED signage or onboard infotainment displays. 3. Authentication and Identity Management CAT prefers proposed systems that support single sign-on (SSO) and City-managed multifactor authentication (MFA) through Microsoft Entra ID. Integration with the City's existing identity management environment is preferred but is not mandatory. Offerors shall describe their proposed authentication capabilities, including available SSO and MFA functionality, supported Microsoft Entra ID integrations, and any associated technical requirements or costs. 4. Accessibility and Third-Party Integrations CAT requires accessible passenger information in accordance with the applicable provisions of Section V – Statement of Needs, including audible and visual onboard announcements and accessible public-facing passenger information services. Offerors shall describe the accessibility features included in their proposed solutions and identify supported integrations with existing onboard equipment, passenger information services, and other third-party systems. Offerors shall clearly distinguish between functionality included in the base proposal and optional integrations, including any associated equipment, licensing, subscription, integration, or third-party dependencies and costs. 5. Existing Automatic Passenger-Counting Equipment and Integration A. Existing UTA Passenger-Counting System CAT's existing automatic passenger-counting (APC) system is provided through Urban Transportation Associates (UTA). CAT's vehicles are equipped with Hella Aglaia APS-B (UTA) automatic passenger-counting sensors. A CalAmp LMU5541LW telematics communications device has also been identified among CAT's existing onboard equipment. CAT is not requiring replacement of its existing UTA APC equipment under this procurement. Offerors shall describe the compatibility of their proposed solutions with CAT's existing APC equipment and identify any applicable technical requirements, limitations, dependencies, or costs. Offerors may propose replacement APC equipment as a separately priced optional item. B. Optional Integration with UTA CAT is interested in evaluating the ability of proposed CAD/AVL solutions to integrate with its existing UTA passenger-counting system. The purpose of potential integration is to improve the accuracy, completeness, and timeliness of passenger-count and ridership reporting. Integration with the existing UTA system is preferred but is not mandatory as part of the base proposal. Offerors shall describe any available UTA integration capabilities, including supported data exchanges, technical requirements, dependencies, limitations, and associated costs. Offerors shall identify whether such functionality is included in the base proposal or offered as an optional item. C. Existing Data Exchange and Hosting CAT does not currently transmit CAD/AVL data to UTA for passenger-count processing. UTA hosts its passenger-counting software, and CAT contracts directly with UTA. These details are provided to assist offerors in understanding CAT's existing technology environment and evaluating potential integration approaches. D. Continued Reporting Requirements The optional nature of UTA integration does not eliminate or reduce the mandatory reporting, data collection, data retention, and system functionality requirements established in Section V – Statement of Needs. All other applicable APC and system integration requirements remain unchanged unless expressly modified herein. 6. Acceptance Testing Period Section V.B.1 – Full Implementation of the Statement of Needs establishes a six-week acceptance-testing period following system go-live. Attachment A – Terms and Conditions for Cloud/Software as a Service, Section 9.B, is hereby amended to establish an acceptance-testing period of six (6) weeks following system go-live, rather than thirty (30) days. The six-week acceptance-testing period established in Section V.B.1 shall govern in the event of any conflict concerning the duration of acceptance testing. Any deemed-acceptance provision in Attachment A, Section 9.B, shall not operate to shorten the six-week acceptance-testing period. All other acceptance procedures remain in effect to the extent they do not conflict with this revision. 7. System Availability Exclusions and Emergency Security Maintenance Revision to Attachment A – Terms and Conditions for Cloud/Software as a Service, Sections 4.A.d–f Attachment A is hereby amended to clarify the following: A. System Availability Exclusions Outages caused solely by cellular carrier networks or City-managed networks and equipment outside the Contractor's responsibility shall be excluded from the system availability calculation. These exclusions shall not apply to failures involving equipment or services the Contractor is responsible for supplying, configuring, managing, or maintaining. The Contractor shall document the cause, duration, and affected functions of any excluded outage and shall continue providing troubleshooting and restoration support. These exclusions shall not waive the Contractor's obligations regarding offline functionality, data retention, or synchronization following restoration of connectivity. B. Emergency Security Maintenance Emergency security patches may be applied outside scheduled maintenance windows when necessary to: Remediate a critical security vulnerability. Address an active or imminent security threat. Comply with a vendor-issued security advisory where delaying remediation would create a material security risk. The Contractor shall comply with all applicable emergency maintenance notification requirements. C. Remaining Requirements All other system availability, maintenance, security, and performance requirements remain unchanged unless expressly modified herein. 8. Service-Level Credits and Remedies Revision to Attachment A – Terms and Conditions for Cloud/Software as a Service, Sections 4.A.g, 12.A, and 12.D The above provisions are hereby amended to establish the following requirements: A. Noncumulative Service Credits Service-level credits arising from the same availability event shall not be applied cumulatively or result in duplicative recovery for that event. To the extent Sections 4.A.g, 12.A, or 12.D provide duplicative service-level credits for the same availability event, the noncumulative requirement established herein shall govern. B. Calculation of Service Credits Service-level credits shall be calculated using recurring fees attributable to the affected hosted service. One-time implementation, installation, hardware, training, and other nonrecurring charges shall be excluded from the calculation of service-level credits. C. Reservation of Contractual Remedies Service-level credits shall not constitute the City's sole or exclusive remedy. The City retains all applicable contractual rights and remedies for other contractual failures, including material breaches, security incidents, data loss, repeated service-level failures, and failure to perform contractual obligations. All other provisions of Attachment A remain unchanged unless expressly modified herein. 9. Contract Term and Pricing Requirements Revision to Section VI.B.D – Price Proposal and Clarification of Section XIII – Pricing For pricing and evaluation purposes, offerors shall provide the total proposed cost for the full potential five-year contract term, consisting of an initial one-year term and four (4) optional one-year renewals. Offerors shall separately identify and itemize the following: One-time implementation, equipment, installation, and associated costs. First-year recurring costs, including hosting, licensing, maintenance, and support. Recurring costs for each of the four (4) optional renewal years. Any proposed annual price increases or adjustments. The total proposed cost for the full potential five-year contract term. All pricing shall clearly distinguish one-time charges from recurring charges and identify any separately priced optional equipment, software, integrations, or services. Optional items shall be separately identified from the required base proposal. The City's evaluation of the full potential five-year cost does not obligate the City to exercise any renewal options. All other provisions governing the contract term and renewal options remain unchanged. 10. Application and Content Escrow Requirements Revision to Attachment A – Terms and Conditions for Cloud/Software as a Service, Section 14 The application and content escrow requirements established in Section 14 are hereby waived for fully hosted, cloud-based Software as a Service (SaaS) solutions proposed under RFP 27-17. In lieu of application and content escrow, the Supplier shall provide the City, upon request or upon contract termination or expiration, a complete export of City data in a documented, industry-standard, nonproprietary format. The export shall include applicable metadata, configuration information, and documentation reasonably necessary to facilitate the City's transition to another solution. Application and content escrow establishment, maintenance, and verification requirements shall not apply to qualifying fully hosted SaaS solutions under this procurement. All other applicable data protection, cybersecurity, business continuity, disaster recovery, data ownership, and transition requirements remain in effect unless expressly modified by this addendum. 11. Acknowledgment and Remaining Terms Except as expressly modified by this addendum, all other terms, conditions, specifications, and requirements of RFP 27-17 and previously issued addenda remain unchanged and in full force and effect. In the event of a conflict between this addendum and the original solicitation or previously issued addenda, the provisions of this addendum shall govern to the extent of the conflict. Offerors shall acknowledge receipt of Addendum No. 4 in accordance with the solicitation requirements.
Addendum #5: Clarifications and Revisions to Insurance and Liability Requirements 1. Purpose The purpose of this addendum is to clarify and revise certain insurance and liability requirements of RFP 27-17, including cyber liability insurance, limitation of liability, and subcontractor insurance requirements. The revisions contained herein supersede conflicting provisions of the original solicitation or previously issued addenda only to the extent expressly stated. 2. Cyber Liability Insurance Requirements Revision to Section XI.P.F – Cyber Liability Insurance The cyber liability insurance requirement established in Section XI.P.F is hereby amended from $1,000,000 to $5,000,000. The required coverage may be satisfied through a combination of primary and excess insurance policies, provided the combined coverage meets or exceeds the required $5,000,000 limit. This revision supersedes the conflicting $1,000,000 cyber liability insurance requirement in Section XI.P.F and aligns the required coverage amount with Attachment A – Terms and Conditions for Cloud/Software as a Service, Section 13. All other applicable cyber liability insurance requirements remain unchanged unless expressly modified herein. 3. Limitation of Liability Clarification to Attachment A – Terms and Conditions for Cloud/Software as a Service, Section 18.A The City will consider an annual aggregate limitation of liability in lieu of a single aggregate liability cap covering the full potential contract term. Any approved annual aggregate limitation shall apply separately to each contract year and shall not carry forward or reduce the liability limit applicable to subsequent contract years. The applicable liability limit and any proposed exceptions shall be subject to City review and approval. All other provisions of Attachment A, Section 18.A, remain unchanged unless expressly modified herein. 4. Subcontractor Insurance Requirements Clarification to Section XI.P – Insurance Requirements, Note C The City may consider adjustments to subcontractor insurance requirements on a case-by-case basis, taking into account the nature and scope of the subcontractor's work and the associated risks. Subcontractors performing limited-scope services, including hardware suppliers without on-site installation responsibilities, may be considered for adjusted insurance requirements where appropriate. Offerors requesting adjustments shall identify the applicable subcontractor, describe the work to be performed, and specify the proposed insurance coverage and any requested exceptions. All proposed adjustments are subject to City review and written approval. Unless an exception is expressly approved in writing by the City, the insurance requirements established in the solicitation shall remain applicable. 5. Acknowledgment and Remaining Terms Except as expressly modified by this addendum, all other terms, conditions, specifications, and requirements of RFP 27-17 and previously issued addenda shall remain unchanged and in full force and effect. In the event of a conflict between this addendum and the original solicitation or previously issued addenda, the provisions of this addendum shall govern to the extent of the conflict. Offerors shall acknowledge receipt of Addendum No. 5 in accordance with the solicitation requirements.
More opportunities from Virginia → Charlottesville Area Transit
Same awarding agency
Find Active Opportunities Like This
Get AI-powered intelligence on the opportunities still open
Every page of the solicitation package shredded into a compliance breakdown
AI-powered matching based on your capabilities and past performance
Competitor and incumbent history on the requirement
Automated alerts on amendments, Q&A deadlines, and award
Join 750+ contractors already using CLEATUS
