Mobile Commercial Vehicle Inspection Trailer for - OSHP (LCS Section)

BACKGROUNDThe Ohio Department of Public Safety’s Ohio State Highway Patrol (OSHP) Licensing and Commercial Standards (LCS) Section has a strong record of reducing commercial motor vehicle (CMV) crashes through focused, data‑driven enforcement strategies. Recent high‑visibility CMV enforcement operations across major Ohio interstates led to a 63% reduction in CMV crashes, with inspections increasing by more than 341% compared to the prior year. These efforts align with OSHP’s mission to provide unbiased, professional public safety services through innovation, collaboration, and statewide traffic safety initiatives. To further expand proactive enforcement capabilities, OSHP secured grant funding through the Public Utilities Commission of Ohio (PUCO) and the Federal Motor Carrier Safety Administration’s (FMCSA) Motor Carrier Safety Assistance Program (MCSAP). With grant funding authorized through September 30, 2027, OSHP is initiating an open and competitive procurement process to acquire mobile commercial vehicle screening trailers that support continuous, unattended roadside screening in high‑crash corridors.OVERVIEWThe State seeks to procure a turnkey, solar‑powered Mobile CMV Screening Trailer and Imaging System capable of: Automated roadside detection of tire, brake, bearing, over‑height, hazmat, seat‑belt, and distraction violations Real‑time data transfer and alerting Seamless integration with the following systems including, but not limited to, SafeSpect, Safety and Fitness Electronic Record (SAFER), Performance and Registration Information Systems Management (PRISM), Motor Carrier Management Information System (MCMIS), Commercial Vehicle Information Exchange Window (CVIEW), and Weigh-In-Motion (WIM). Operation in remote areas without on-site personnel Rapid deployment, relocation, and unattended monitoring OBJECTIVES. ODPS has the following objectives that it wants this Work to fulfill, and it will be the Contractor’s obligation to ensure that the personnel the Contractor provides are qualified to perform their portions of the Work.The selected Contractor will provide a complete system and qualified personnel to support OSHP in: Enhancing crash prevention through upstream detection of unsafe vehicles Increasing enforcement efficiency and focusing inspections on high‑risk CMVs Strengthening operational intelligence through integrated roadside data Enabling OSHP to monitor, screen, and assess vehicles well before they reach an enforcement point
Round #2 - Amended to add Data Security & Privacy Terms and Supplement A. Also to extend solicitation close date for 10 business days. Request for Proposal (RFP): Offerors must review the attached "SRC0000039960 Mobile Commercial Vehicle Inspection Trailer RFP" document. Each Offeror must submit a Technical Proposal and a Cost Proposal as part of its Proposal package. Proposals must be submitted as two separate components (Technical Proposal and Cost Proposal) in separate electronic envelopes.Technical Proposal: The Technical Proposal is to be submitted as a single searchable PDF document indexed as required in Attachment Two.Cost Proposal: The Offeror must submit a separate cost section of its Proposal in the required format described in Attachment Two and as appears in OhioBuys Item grid.Each section must be submitted in its own separate, electronic submission as indicated by the solicitation questionnaire. The submission with the Technical Proposal will be electronically sealed and contain a signed Technical Proposal, and the submission with the Cost Proposal also will be electronically sealed.OHIOBUYS TRAINING MATERIALSOhioBuys training materials can be located at this site https://procure.ohio.gov/bidders-and-suppliers/resources/03_Using+OhioBuysTo participate or submit an inquiry for this RFx, you need to be registered in the OhioBuys Supplier Portal. Suppliers are not required at this time to be registered in OAKS. If you have a need to seek technical support, clearly specify you need access to an active Ohio Buys solicitation.Technical Support 1-877-644-6771If there is a need for technical support during your proposal submission in the last 48 hours prior to the submissions, contact 614-466-5090. This number is for OhioBuys solicitation technical questions only; there will not be any questions answered regarding the solicitation.Note:Chrome is the preferred browser for OhioBuys.Only have a single window open that is logged into OhioBuys, having multiple windows opened to a single user can create an error when trying to submit your proposal.
Equipment inspection service
Items 1 | Required Item | Mobile Prescreen Inspection Trailer | Estimated usage: 9.00000 | Unit: Each
Inquiries Inquiry 94492 | Could OHSP describe the unattended operating scenario? Will officers monitor detections in real time from another downstream location, and will the system be used to support post-event or retrospective enforcement? | Answer: The system will operate unattended, deployed on the shoulder of an interstate or state route and self‑sustained in that location. It will capture vehicle data from passing traffic in the adjacent lanes and transmit this information for review either at the deployment site or from a remote location. The system will identify potential vehicle violations or concerns based solely on its fixed roadside position. Collected data will support analytical assessments and crash‑reduction initiatives; it is not intended for real‑time enforcement beyond monitoring detections remotely. | Answered: 8/14/2026 Inquiry 94495 | Are all technical requirements mandatory at initial acceptance for a proposal to be responsive, or may an Offeror propose equivalent alternative approaches, phased delivery, or future enhancements? If alternatives are permitted, please identify the requirements that are mandatory at initial acceptance and the evaluation criteria for proposed alternatives. | Answer: All technical requirements are mandatory at initial acceptance unless the solicitation expressly allows alternate, phased, or equivalent approaches. Any flexibility must be defined in the RFP, including which requirements may be met through alternatives and how those alternatives will be evaluated. | Answered: 8/14/2026 Inquiry 94498 | What is the primary operational use case and expected officer workflow for the combined mobile capabilities listed in Section III? | Answer: The primary use case is roadside data collection to provide inspectors with real‑time visibility into vehicle activity at the deployment point. The system gathers inspection and vehicle data to support both immediate awareness and historical analysis, enabling informed decisions on resource allocation and enforcement strategies based on documented evidence. | Answered: The primary use case is roadside data collection to provide inspectors with real‑time visibility into vehicle activity at the deployment point. The system gathers inspection and vehicle data to support both immediate awareness and historical analysis, enabling informed decisions on resource allocation and enforcement strategies based on documented evidence. Inquiry The primary use case is roadside data collection to provide inspectors with real‑time visibility into vehicle activity at the deployment point. The system gathers inspection and vehicle data to support both immediate awareness and historical analysis, enabling informed decisions on resource allocation and enforcement strategies based on documented evidence. Inquiry 94501 | Please identify each location where tire-anomaly screening is required and confirm whether the State will provide existing in-road sensors at those locations. If not, should Offerors include the procurement and installation of all required sensors in their cost proposals? | Answer: Tire‑anomaly screening will be performed using onboard trailer‑mounted thermal cameras. The State will not provide in‑road sensors at these locations. Any additional sensor equipment or integration beyond the onboard thermal capability is outside the scope of this requirement and should not be included in cost proposals | Answered: 8/14/2026 Inquiry 94504 | Please confirm if the thermal imaging capability for inspecting the brakes and bearings is required on both sides of each vehicle. | Answer: Thermal imaging for brake and bearing inspection is only required on the side of the vehicle facing the deployed trailer. | Answered: 8/14/2026 Inquiry 94507 | Does Section III.C require measurement of vehicle length, width, and overall height, or only detection of vehicles exceeding a defined height threshold? | Answer: Section III.C requires measurement of vehicle length, width, and overall height, including detection of vehicles exceeding defined height thresholds. | Answered: Section III.C requires measurement of vehicle length, width, and overall height, including detection of vehicles exceeding defined height thresholds. Inquiry Section III.C requires measurement of vehicle length, width, and overall height, including detection of vehicles exceeding defined height thresholds. Inquiry 94510 | Does the 3,500-pound Gross Vehicle Weight Rating (GVWR) limit apply to the base trailer alone, or does it represent the total maximum operating weight including all integrated equipment (e.g., solar panels, battery bank, and satellite communications equipment referenced in Sections V.A and VI.A)? | Answer: The 3,500‑pound GVWR limit applies to the trailer and all installed equipment | Answered: 8/14/2026 Inquiry 94513 | May Offerors use supplemental charging methods or alternative power sources in addition to solar power, provided the solution meets all required operating duration, mobility, safety, and performance requirements? | Answer: Supplemental or alternative power sources may be used prior to deployment. Once deployed by roadside, the trailer must remain fully self‑sustained for the duration of the deployment | Answered: 8/14/2026 Inquiry 94516 | Please clarify the primary and backup communications requirements: (1) must both connections and all related equipment be integrated into the trailer, or may backup equipment be located in the towing vehicle; and (2) will two independent cellular carriers satisfy the redundancy requirement, or is a satellite connection mandatory? | Answer: All primary communications capability must be integrated into the trailer. Backup communications may include satellite as a more reliable option. Two independent cellular carriers may be used if they meet required reliability, but satellite can be added to enhance redundancy | Answered: 8/14/2026 Inquiry 94519 | For the required WIM integration, please specify: (1) whether the solution must support fixed-site WIM, portable/virtual WIM, or both; (2) the required data formats, interface protocols, connection methods, and security requirements (e.g., direct hardwired connectivity or local/remote wireless protocols). | Answer: The solution must support remote WIM connectivity with ODOT’s system through the existing API. The trailer’s software must be capable of ingesting the transmitted WIM data. Specific implementation details and integration methods should be defined by the trailer manufacturer. | Answered: 8/14/2026 Inquiry 94522 | How many WIM locations are in the integration scope? For each location, can OHSP provide the WIM manufacturer and sensor model/technology type? | Answer: There are 22 known WIM locations currently in scope, and the system is still under development. The specific WIM manufacturers and sensor types for these sites are not yet known. | Answered: 8/14/2026 Inquiry 94525 | Who are the intended user groups for the analytics data? | Answer: The intended user group for the analytics data is law enforcement, supporting efforts to reduce crash‑causing violations and identify high‑risk carriers. | Answered: 8/14/2026 Inquiry 94528 | Could OSHP identify the specific data elements, metrics, and reports the analytics capability must provide to support enforcement strategy and crash prevention, and provide representative examples of each? | Answer: Each sensor must produce a searchable report containing its collected data. Representative data elements include truck counts, vehicle types, DOT‑related violations, driver information, hazardous‑material classifications and frequency, size violations, and tire‑related violations. | Answered: 8/14/2026 Inquiry 94531 | Please confirm that the ownership and license provisions apply only to deliverables developed specifically for the State under this contract and do not transfer ownership of, or grant broader rights in, an Offeror's pre-existing or independently developed software, SaaS platform, hardware designs, tools, documentation, updates, enhancements, derivative works, or other proprietary materials. If not, please specify the rights the State requires in each category and whether exceptions or mutually agreed limitations may be proposed. | Answer: State ownership applies only to custom‑developed deliverables produced under this contract. All pre‑existing or independently developed intellectual property, including software, SaaS platforms, tools, documentation, hardware designs, updates, enhancements, and derivative works, remains the Offeror’s property. | Answered: 8/14/2026 Inquiry 94534 | Hazmat placard recognition with automatic classification: Please clarify the required classification outputs - for example, DOT hazard class/division, placard type, and UN/NA identification number - and specify any minimum detection accuracy, vehicle-speed range, operating conditions, and acceptance-testing criteria that the proposed system must satisfy. | Answer: The Hazmat placard reader must capture the placard details, including hazard class and UN number, and pair this information with the vehicle image, DOT data, registration information, driver compliance, and other collected data. The user interface should present this information in a format consistent with scale bypass vehicle‑inspection systems commonly used in Ohio and neighboring states. | Answered: 8/14/2026