Attachment AA_Web-Hosting Traffic Data and FHWA Data Preparation.docx
DOCX document 24 KB Posted
- Solicitation number
- 25-494DOT-FINAD-B-45654
- Issued by
- Illinois
About this file
This is a mandatory requirements document from the Illinois Department of Transportation (IDOT) outlining technical specifications for a web-hosted traffic data collection and management system. The requirements detail the need for a platform capable of uploading, displaying, and managing traffic data from various counter types including MHCorbin HiStar, MioVision, TRS recorders, TIRTL recorders, and GRIDSMART recorders. The system must support both short-term (24 or 48 hours) and continuous count traffic data, provide mapping capabilities using Google or Bing maps, and enable data display in various formats. The platform must also support FHWA's Travel Monitoring Analysis System (TMAS) monthly submittal requirements and maintain at least two years of historical data.
The document specifies security requirements including public access for volume data but restricted access for speed and classification data. Technical support must be available during IDOT's standard business hours (8:00 am - 4:30 pm CDT). Vendors must provide three references from government agencies that have used their services for similar traffic data collection web applications. The requirements also mandate data migration protocols upon contract termination, ensuring all data is returned to the agency in an exportable tabular format with technical assistance for transition to new systems.
View the file
Other files
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
Attachment AA - Mandatory Requirements
Upload Traffic Data
|_| Met |_| Not Met
| 1. Web hosting site must be able to upload short term (24 or 48 hours) lane specific traffic data (volume, classification, speed) from the MHCorbin HiStar traffic counter catalogs and also upload the short term data provided in EXCEL output files (volume and classification) from MioVision video traffic counting equipment. |
| Vendor Narrative: |
| 2. The web hosting site must be able to upload standard daily files containing volume, classification, and speed data from the different traffic recording equipment types used at the continuous count traffic sites. These equipment types include TRS recorders (.PRN format), TIRTL recorders (.CSV format) Ver. 2 and Ver. 3 and GRIDSMART recorders (.xls format). |
| Vendor Narrative: |
| 3. During the year a temporary web location must be created (a copy of the production site) to establish the thousands of new, short-term count locations based on data provided by IDOT. The temporary site must have the capability for IDOT to upload traffic data from the short-term traffic counters to review and delete traffic data prior to the entire year’s counts being moved to the production web hosting site making them available for the general public. |
| Vendor Narrative: |
Displaying traffic data on the web hosting site
| 4. The web hosting site must be able to display IDOT count locations on a common map background such as Google or Bing maps and have standard geographical tools available (zoom, pan, identify, etc.). |
| Vendor Narrative: |
| 5. The web hosting site must be able to search for specific IDOT traffic locations and display the raw traffic data by lane, direction, or centerline in a tabular format including 15 minute or 1 hour increments (depending on the collection interval). Individual count location traffic data must be available for export in an EXCEL spreadsheet format. |
| Vendor Narrative: |
| 6. The web hosting site should have the capability to display at least the last two (2) years of individual daily traffic data from continuous count sites provided by IDOT for viewing by the general public. |
| Vendor Narrative: |
| 7. The web hosting site must provide search capability by station type (short term location or continuous location), county and city at a minimum. |
| Vendor Narrative: |
FHWA Traffic TMAS (Travel Monitoring Analysis System) monthly submittal
| 8. The web hosting site must be able to run similar edits as the FHWA TMAS software to check the QA/QC of the continuous count traffic data prior to preparing the data for the TMAS submittal. Mechanisms must be in place to remove continuous count stations not passing the TMAS edits from the TMAS submittal file. |
| Vendor Narrative: |
| 9. The web hosting site must be able to generate the monthly Volume, Classification, and Speed TMAS submittal in a format acceptable to FHWA’s TMAS web application. |
| Vendor Narrative: |
| 10. The web hosting site must provide the ability to add inventory data on the continuous count traffic sites to meet the TMAS station inventory items required by FHWA and have the capability to add customized IDOT station inventory fields. |
| Vendor Narrative: |
| 11. The web hosting site must have the feature to generate the station location file as required by FHWA’s TMAS application. |
| Vendor Narrative: |
Security
| 12. The web hosting site must be able to display volume traffic data to the general public without a specific login, however a higher level of security using a login is required to view the speed and classification traffic data. |
| Vendor Narrative: |
| 13. The web hosting site must provide administrative controls using logins and passwords to limit the capability of uploading data to the site and preparing the TMAS submittal. |
| Vendor Narrative: |
Back Up
| 14. The web hosting site must provide the capability of special login and password security to extract backup files of the IDOT short term and continuous traffic data that is residing on the site. |
| Vendor Narrative: |
| 15. The Vendor must provide field and file specifications of the backup formats from the site so IDOT can import the traffic data into an ACCESS database. |
| Vendor Narrative: |
Support
16. Technical support must be provided during normal IDOT hours (8:00 am – 4:30 pm CDT) during the duration of the contract.
Vendor Narrative:
| 17. The Vendor must provide support for batch uploads of IDOT location data, batch deletes or changes of traffic data based on IDOT provided files during the duration of the contract. |
| Vendor Narrative: |
18. Should the contract be terminated, all data associated with the services provided must be returned by the Vendor to the Agency.
(a) Transfer of Data Back to Agency – Prior to completion or termination of the contract, Vendor must take all necessary measures to assure that all data maintained in the hosted environment has been migrated back to the Agency in exportable tabular format specified by the Agency, including a data dictionary.
(b) Migration of Data to Another Vendor – Vendor must provide technical assistance transferring the data to a new or replacement system.
Vendor Narrative:
Administrative
|_| Met |_| Not Met
| 19. Supplied three (3) instances from Governmental Agencies stating that they have utilized your services for providing and maintaining an externally hosted traffic data collection web application that provides data into the FHWA TMAS format and for displaying traffic count data. |
| Vendor Narrative: |
File details come from the government source that posted it. Updated .