Transportation Data Management System RFP
The system must manage traffic count locations, schedule and track counts, upload and validate raw data, automate data integration from local partners, generate required traffic statistics (including AADT, CAADT, PAADT), provide map-based access to data, support FHWA reporting (including MAP-21 compliance), and integrate with Esri Roads and Highways. It must accept data directly from third-party traffic counting equipment, support mobile field data collection (iOS and Android), and be adaptable to future federal reporting changes. The solution must also include HPMS processing, count planning and scheduling, task lifecycle management, quality control and manual review, traffic analytics and statistics, non-motorized data management, LRS location referencing, ESRI R&H synchronization, local agency data intake, roles and security, and dashboards and reports. The contractor must migrate data from the existing Microsoft SQL Server database (approximately 9 TB, 68 billion rows across 900 tables) and provide training, documentation, and transition services.
We post new professional & consulting services opportunities in Michigan as agencies publish them. Get them in one email — free, and unsubscribe whenever.
Most Michigan work asks for the two below, and the solicitation documents are where it’s stated. One prequalification covers both — on this bid and the next.
A surety’s written statement that it expects to bond you up to a stated amount, subject to final underwriting. It’s what an agency asks to see before they take your bid seriously.
Source: Michigan SIGMA VSS (solicitation RFP-171-260000002471-2), retrieved via the Michigan SIGMA Vendor Self Service portal. View the official posting, and always confirm requirements and deadlines with the issuing agency.