attachment_13_RFP DOIT 2025-036 Pre-Proposal Vendor Conference Slides.pptx
PPTX presentation 22 MB Posted
- Attached to
- Traffic Data Management System (TDMS)
- Solicitation number
- RFP DOIT 2025-036
- Issued by
- Rockingham County, New Hampshire
About this file
This document is a pre-proposal vendor conference presentation for the New Hampshire Department of Transportation's (NHDOT) Traffic Data Management System (TDMS) Request for Proposal (RFP DOIT 2025-036). The procurement seeks a comprehensive, web-based traffic data management software solution to support statewide traffic monitoring, with requirements including support for 150-200 automated traffic volume sites, 25-50 automated classification sites, 5-20 weigh-in-motion sites, and 3,000-6,000 coverage count locations. The mandatory pre-proposal vendor conference is scheduled for January 16, 2025, at 11:00 AM ET, with proposal submissions due by May 15, 2025, at 3:00 PM ET. The anticipated contract start date is October 27, 2025, with an initial 5-year term through November 1, 2030, and potential for two optional 2-year extensions.
The evaluation will use a 1000-point scale, with 600 points for technical factors and 400 points for pricing, requiring a minimum technical score of 400 to proceed to cost evaluation. Vendors must demonstrate a Traffic Data Management System used in at least two U.S. jurisdictions since January 1, 2022. Key technical requirements include FedRAMP authorization, ability to store 1.5 billion continuous count and 300 million short count individual vehicle records annually, compatibility with ESRI GIS systems, and compliance with Federal Highway Administration (FHWA) Traffic Monitoring Guide requirements. The system must support 300 concurrent authorized users, provide web-based access, and integrate with existing traffic data collection infrastructure. While no specific budget is disclosed, the RFP indicates comprehensive pricing categories covering implementation, operations, and ongoing maintenance.
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
Traffic Data Management System (TDMS) RFP 2025 - 036 Pre-Proposal Vendor Conference January 16, 2025
Introductions NHDOT Primary Point of Contact Mike O’Donnell, P.E., Chief of Traffic Engineering Michael.T.ODonnell@dot.nh.gov NHDOT Secondary Point of Contact Stuart Thompson, P.E., Traffic Monitoring & Research Engineer Gordon.S.Thompson@dot.nh.gov All correspondence shall include both Mike and Stuart
Consultant Support (VHB) Mark Suennen, P.E., PTOE Dan Schandel, PE, RSP1
1/23/2025
TDMS RFP DOIT 2025-036
Project Background All RFP Documents are available on the New Hampshire DAS Website:
https://apps.das.nh.gov/bidscontracts/bids.aspx NHDOT current Traffic Data Management System is available on its website:
https://nhdot.public.ms2soft.com/tcds/tsearch.asp?loc=Nhdot&mod=TCDS
NHDOT is seeking Proposals from Qualified Vendors to provide and maintain TDMS Software A Qualified Vendor: Has a Traffic Data Management System that has been in use in at least two jurisdictions in the United States since 1/1/2022 1/23/2025
Purpose of the TDMS Traffic Monitoring System (TMS)
- Title 23, CFR Part 500
- Defined by FHWA 2022 Traffic Monitoring Guide (TMG) National Highway System (NHS) Highway Performance Monitoring System (HPMS)
- Title 23, CFR Part 490 Shall encompass traffic volume, vehicle classification, traffic speed and weight data.
Data shall be accessible 24/7/365 throughout the contract period
1/23/2025
Existing TDMS Data Currently Collected
- Traffic Volumes
- Classification
- Speeds
- Vehicle Weights Current Infrastructure
- 59 Continuous Count Stations
- 24 Continuous Vehicle Classification Stations
- 5 Weigh-In-Motion Stations
- 6,000 Short Count Stations
- Ramp Counting System
- Supports Autopolling and Manual Upload Current Vendor is MS2 1/23/2025
Project Goals Support the following Infrastructure:
- 150-200 Automated Traffic Volume Sites
- 25-50 Automated Classification Sites
- 5-20 Weigh-In-Motion Sites
- 3,000-6,000 Coverage Count (Short Count) Locations
- 100-250 Turning Movement Count locations per year
- 1,200-1,800 Manual Classification locations
- Micromobility Counts
- Vehicle count program for all public roads
- Integrate NHDOT GIS map data
- Web-Based User Interface for continuous access
- Permissions-based authorization for varying levels
RFP Overview Section 1 - Overview Prohibited Technologies List & FCC Covered List Scope of Work RFP Schedule (Schedule of Events)
Section 2 – Proposal Submission Technical Proposal: Six (6) Physical copies + USB Drive Price Proposal: One (1) Original + Two (2) Physical copies Requires Electronic Proposals as well (see Section 2.1.2) Vendor Inquiries – Addressed to Mike and Stuart with Subject Line:
RFP DoIT 2025-036 Statewide TDMS Procurement Inquiry
1/23/2025
Section 3 – Proposal Organization Technical Proposal – 7 Required Sections + Appendices See RFP Appendices B, C, and D for details on Sections III, IV, V, and VI Shall submit a completed Table B-2.1 for Section III Shall submit a completed Table B-3 for Section III Shall address all Topics for Mandatory Responses for Section IV Price Proposal – 8th Section (Sealed Separately from Technical) See Appendix E for details on Section VIII Shall submit completed Tables E-1.1 and E-1.3 through E-1.7 Shall submit completed Tables E-2.1 and E-2.2 (NHDOT informational only)
Section 4 - Proposal Evaluation 1000 Point Scale – 600 Points Technical / 400 Points Cost Will evaluate Proposal, Oral Interviews and Product Demonstrations A minimum score of 400 of 600 on the Technical is required before Cost is opened 1/23/2025
Section 5 – Terms and Conditions of RFP Any Addendums will be published to the NH DAS website
Section 6 – Contract Terms and Conditions Proposed 5-Year Contract with up to two 2-Year extensions Contract will follow State of New Hampshire General Provisions and Exhibits (P-37 document is Appendix I, available independent of the RFP)
Appendices Appendix A – This Vendor Conference Appendix B – Requirements Appendix C – Topics for Mandatory Responses (note page count limits) Appendix D – Vendor Qualifications Appendix E – Pricing Appendix F – DoIT Infrastructure and Security Appendix I – P-37 State Contract Template 1/23/2025
Requirements Overview Table B-2.1 – Spreadsheet to be completed by Vendors 1/23/2025
TDMS RFP DOIT 2025-036
Criticality M = Mandatory – 100% should be met by the Proposed Solution E = Expected – 80% should be met by the Proposed Solution O = Optional – See Appendix E-2 for discussion of pricing Optional Requirements
- Business
- Software
- Testing
- Support and Maintenance
- Training
- Project Management
- System Monitoring and Data Migration
- Functional
- GIS and Mapping
- Application
- (IT) Testing
- (IT) Hosting-Cloud
- (IT) Project Management
Selected Key Requirements Web-based, scalable COTS application with 100% availability on all commonly used browsers Shall provide tools to analyze, query, access, and use traffic data Allow concurrent use by 300 Authorized Users and unlimited read-only users Shall meet the requirements of a TMS Shall generate reporting for the TMAS Shall generate reporting for the HPMS Shall create standard and ad hoc reports Shall be hosted by the Vendor throughout the Contract Period Three environments: Development, Testing, Production
1/23/2025
Selected Key Requirements (continued) Shall meet all DoIT security/cybersecurity requirements Shall migrate and store all legacy data, maintaining NHDOT’s Location ID numbers Shall support several traffic data types, some in IVR format Shall support all current traffic data collection systems Shall include automated, comprehensive, and configurable rule-based data validation and quality checking for all new traffic data Shall use the NHDOT LRS snapshot to update AADT per segment Shall include on-call technical support Shall include Initial Roll-Out Training and continuing support training
1/23/2025
Important Changes from Existing TDMS There are several important changes from the existing TDMS
New DoIT Security Requirements and Restrictions FedRAMP Authorized data storage Shall accommodate Individual Vehicle Records (IVRs) Minimum of 1.5 Billion Continuous Count IVRs annually Minium of 300 Million Short Count IVRs annually Shall incorporate NHDOT GIS Mapping Support the current release of ArcGIS Roads and Highway in ArcGIS 11.1 Shall include HPMS Integration Create the HPMS Vehicle Summaries Table as required in the HPMS Field Manual
1/23/2025
Individual Vehicle Records (IVRs)
TDMS RFP DOIT 2025-036
| Requirement Number | Requirement Description | Criticality |
| B1.6.6 | The Proposed Solution shall have the ability to export Individual Vehicle Records (IVRs). | Mandatory |
| C5.8 | The Proposed Solution shall provide access to raw data in the form of IVRs where available. | Expected |
| C6.2.2 | The Proposed Solution shall include report functions to create monthly reports for speed, micromobility, and IVRs. | Expected |
| F1.7 | The Proposed Solution shall support IVR Data Collection | Mandatory |
| F1.24 | The Proposed Solution shall provide storage for a minimum of 1.5 Billion Continuous Count IVRs annually. | Mandatory |
| F1.25 | The Proposed Solution shall provide storage for a minimum of Three Hundred Million Continuous Count IVRs annually. | Mandatory |
| F10.10.1 | The Proposed Solution shall accept and store IVRs. | Mandatory |
| F10.10.2 | The Proposed Solution shall produce IVR exports in formats accepted by the TMAS published by FHWA | Expected |
| F10.10.3 | The Proposed Solution shall parse and store the IVRs in the TMG format, including the 5-digit code. | Mandatory |
GIS Mapping
TDMS RFP DOIT 2025-036
| Requirement Number | Requirement Description | Criticality |
| G1.1 | The Proposed Solution shall provide the ability to link count stations to the State’s road network segments. | Mandatory |
| G1.2 | The Proposed Solution shall have the ability to geographically view data collection equipment on the map. | Expected |
| G1.3 | The Proposed Solution shall include access to the NHDOT Traffic Flow Map in GIS Format. | Expected |
| G1.5 | The Proposed Solution shall accept references to all ESRI file types from web services originating from ArcGIS 10.8.1 or higher. | Mandatory |
| G1.6 | The Vendor is alerted that NHDOT uses ESRI’s Enterprise GIS and is exploring a transition to ESRI’s Roads and Highways. The Vendor will not be required to directly interface with the Roads and Highways Program but shall provide GIS data outputs which are compatible with Roads and Highways for smooth future transition. These requirements of compatibility include: | Mandatory |
| G1.6.1 | The Vendor’s GIS data outputs shall preserve spatial location attributes and information of collected data, including: | Mandatory |
| G1.6.2 | Shall retain precision of data attributes containing identifying location such as latitude and longitude of points and vertices of polylines or polygons. | Mandatory |
| G1.6.3 | Shall retain precision for data containing linear referencing system attributes such as roadway ID, beginning or ending milepost. | Mandatory |
| G1.6.4 | ||
| The Vendor’s GIS data outputs shall provide collected data in a format that is readable directly by ESRI’s GIS software and is in a compatible format for inclusion in ESRI Roads and Highways. | Mandatory |
Highway Performance Monitoring System
TDMS RFP DOIT 2025-036
| Requirement Number | Requirement Description | Criticality |
| B1.6 | The Proposed Solution must conform to the current edition of FHWA TMG requirements, American Association of State Highway Officials (AASHTO) guidelines for Traffic Data Programs, and FHWA Highway Performance Monitoring System (HPMS). | Mandatory |
| K1.13 | The Initial Roll Out Training shall be completed prior to NHDOT users needing to operate the Proposed Solution to submit any HPMS materials to FHWA. | Expected |
| F1.11 | The Proposed Solution shall create a snapshot of all data loaded as of a user specified date and produce annual statistics, including all HPMS required statistics, for all sites based on this data set. | Mandatory |
| F3.1 | The Proposed Solution shall be capable of creating the HPMS Vehicle Summaries table and all traffic-relevant items required within the HPMS Field Manual Road Event Collection Methods (formerly Metadata) table. | Mandatory |
| F4.4 | The Proposed Solution shall calculate percent vehicles in the Design Hour per FHWA's latest memorandum (dated January 13, 2022) describing changes for the 2022 HPMS Data Submission. | Mandatory |
| F6.2 | The Proposed Solution shall produce the vehicle classification by functional system report for the yearly submission to HPMS from continuous classification, WIM, and short-term classification count stations in accordance with Table 3.11, Table 3.18, and selected Traffic items within Table 3.19 within the HPMS December 2016 Field Manual, HPMS November 2020 Field Manual Errata Sheet, and per FHWA's January 13, 2022 memorandum describing changes for the 2022 HPMS Data Submission. | Mandatory |
| F6.3 | The Proposed Solution shall output AADT and year data was most recently collected, single unit Truck and Bus AADT, percent design hour single unit Trucks and Buses, combination Truck AADT, percent design hour combination Trucks, K-Factor, Directional Factor, and 20 Year Forecast AADT to enable electronic transfer of data to HPMS submittal software per guidance within the HPMS December 2016 Field Manual Section 2.4, Table 2.1, for Items 21 to 28; and with respect to FHWA's January 13 and December 16 memorandums describing changes for the 2022 and 2023 HPMS Data submissions. | Mandatory |
Schedule
| Schedule of Events | |
| Event | Date & Time |
| RFP Released to Vendors / Inquiry Period Begins (on or about)/ | December 17, 2024 |
| Notification of the Number of Representatives Attending the Pre-Proposal Vendor Conference and/or Request for Teleconference Invitation(s) (Mandatory) | January 13, 2025, 3:00 PM ET |
| Mandatory Pre-Proposal Vendor Conference | January 16, 2025, 11:00 AM ET |
| Vendor Request for One-on-One Conference Deadline | January 22, 2025, 3:00 PM ET |
| Early Vendor Inquiry Deadline (Inquiry Period continues) | January 30, 2025, 3:00 PM ET |
| State Responses to Early Vendor Inquiries | February 13, 2025 |
| One-on-One Vendor Conferences | February 18-21, 2025 |
| Confidential Vendor Inquiry Deadline (following One-on-One Vendor Conferences | March 5, 2025, 3:00 PM ET |
| State Reponses to Confidential Vendor Inquiries | March 20, 2025 |
| Vendor Inquiry Period Ends (Final Inquiries due) | April 22, 2025, 3:00 PM ET |
| Final State Responses to Vendor Inquiries | May 5, 2025 |
| Final Date and Time for Proposal Submission | May 15, 2025, 3:00 PM ET |
| Invitations for Oral Presentations and Software Demonstrations | June 10, 2025 |
| Vendor Presentations and Software Demonstrations (Mandatory) | Week of July 14, 2025 |
| Estimated Date of Vendor Selection | July 24, 2025 |
| Anticipated Governor and Council Approval | October 22, 2025 |
| Anticipated Effective Contract Date | October 27, 2025 (estimated initial 5-year term ending November 1, 2030) |
Questions or Comments
Contacts:
Michael O’Donnell, PE | NHDOT | Michael.T.ODonnell@dot.nh.gov | 603.271.1581 Stuart Thompson, PE | NHDOT | Gordon.S.Thompson@dot.nh.gov | 603.271.0391
1/23/2025
TDMS RFP DOIT 2025-036
Responses to any questions raised during this Vendor Conference will be provided in writing on the NH DAS website by February 13, 2025.
image1.jpeg image2.png image3.png image4.png image5.jpg image6.png image7.png image8.png
File details come from the government source that posted it. Updated .