attachment-5-rfp-doit-2025-036.pdf
PDF 130 KB Posted
- Attached to
- Traffic Data Management System (TDMS)
- Solicitation number
- RFP DOIT 2025-036
- Issued by
- Rockingham County, New Hampshire
About this file
This is an Appendix C supplemental specification document for RFP DoIT 2025-036 issued by the New Hampshire Department of Transportation for a statewide Traffic Data Management System (TDMS). The RFP seeks a commercial off-the-shelf web-based software solution capable of processing traffic data from 8,500 monitoring stations and supporting 300 authorized users across the state. The system must handle multiple data types including vehicle records, volume, classification, speed, and weigh-in-motion data while integrating with ESRI products and supporting nine regional planning commissions. A mandatory vendor conference is scheduled for January 16, 2025, at 11:00 AM ET in Concord, New Hampshire, with proposals due by May 15, 2025, at 3:00 PM ET. The anticipated contract start date is October 27, 2025, with an initial five-year term extending through November 1, 2030, and potential for two optional two-year extensions.
Appendix C-1.21 specifically addresses Station Links, requiring vendors to demonstrate their system's ability to convert point-based traffic data from collection devices into segment-based Annual Average Daily Traffic (AADT) estimates aligned with the New Hampshire Department of Transportation's Linear Referencing System. Vendors must provide written responses detailing their complete workflow from data collection and processing through AADT modeling, including methodologies for extrapolating data from both short-duration and continuous count sites, handling missing or erroneous data, managing high data volumes across all roadway segments including local roads, harmonizing different data sources, and validating estimated AADT values through ground-truth checks and statistical analysis. The evaluation uses a 1000-point scale with 600 points allocated to technical factors and 400 points to pricing, requiring vendors to demonstrate successful implementation of similar systems for at least two U.S. jurisdictions since January 2022. The system must be FedRAMP or StateRAMP authorized and capable of archiving data for 20 years while storing 1.5 billion continuous count individual vehicle records and 300 million short count records annually.
View the file
Other files
Show all 47
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
STATE OF NEW HAMPSHIRE
DEPARTMENT OF TRANSPORTATION
RFP DoIT 2025-036 PROCUREMENT FOR STATEWIDE
TRAFFIC DATA MANAGEMENT SYSTEM (TDMS)
APPENDIX C SUPPLEMENTAL
Appendix C-1.21
STATION LINKS
1. Summary
The purpose of this Appendix is for the Vendor to provide documenta�on and prove the so�ware’s ability to take point-based data from traffic data collec�on devices and assign the data to segments within the NHDOT Linear Referencing System (LRS). The Vendor shall provide responses as an Appendix to the Proposal.
2. Vendor Response Requirement
The Vendor is required to provide a wri-en response outlining their approach for crea�ng segment-based Annual Average Daily Traffic (AADT) from point-based traffic volume data collec�on, including both short-dura�on counts and con�nuous count sites. This response should at a minimum contain the following:
• The Vendor’s response should cover the complete workflow, from data collec�on and processing to the modeling or es�ma�on of AADT on all roadway segments.
• The Vendor’s response should detail the methodologies and algorithms used for extrapola�ng point-based data to segment-based data, taking into account factors like traffic trends, seasonal varia�ons, and other relevant variables.
• The Vendor’s response should include techniques for handling missing or erroneous data to ensure robust and accurate AADT es�mates.
• The Vendor’s response should demonstrate their Proposed Solu�on’s ability to manage and analyze both short-dura�on and con�nuous count data efficiently.
• The Vendor’s response should explain how their system harmonizes these different data sources and addresses any discrepancies or conflicts that might arise.
• The Vendor’s response should describe their strategy for scaling their Proposed Solu�on to cover all roadway segments, indica�ng how the system will handle the high volumes of data involved and how it will maintain performance and accuracy. The scaling discussion should include the Proposed Solu�on’s ability to include all public roads, including local roadways maintained by others.
• The Vendor’s response should also present their approach to validate the es�mated
AADT values, such as through ground-truth checks, sta�s�cal analysis, or comparison with historical data. This would provide confidence in the reliability and accuracy of the generated segment-based AADT figures.
File details come from the government source that posted it. Updated .