Specifications include, but are not limited to: Task 1 – Data Integration Needs Identify the work needed to be performed by Portland State University to further integrate the Clark County traffic data streams into active Portal database usage that could be used for reports, queries, and visualizations. The deliverable includes but is not limited to evaluation of hours of work, and potential costs to integrate different sets of the county’s traffic data. The county data includes, but is not limited to: A. Bluetooth B. High resolution Purdue data C. Traffic Count Stations for counts, occupancy, and signal timing information D. Count data from Wavetronix matrix and advance E. Connected vehicle Task 2 – Develop Scope of Work for Portland State University Work with Clark County and Portland State University to generate a scope for various reports that Portal would summarize and process using these data streams. This would allow presentation of reports using the data streams from task one. A primary feature to be included is to create user login to the Portal system, where a person or agency would be able to have standard report templates saved by user login where the reports can be repeated frequently without having to re-generate the parameters. A second feature will be for reports to include common performance measures that can be identified graphically and in table format that can be exported as a graphic or as tables for use in external reports. Common data results and performance measurements in the reports could include the following: A. Travel time with comparisons for before and after studies or for events B. Travel time reliability graphs with graphics at percentiles such as 20%, 50%, 80%, 95% with cumulative frequency C. Volume D. Travel Speed both as a spot speed at a count station and along a corridor. E. Occupancy F. Vehicle Classification G. Percent Arrival on Green H. Red Occupancy Ratio / Green Occupancy Ratio (Split Failure) I. Statistical output with graphs J. Origin-destination data K. Alerts for potentially bad data so we can determine if equipment is operating properly. For both task one and two, we envision a list of work products that PSU could complete for us with itemized costs and development timelines for each product. This list would then allow the county to choose some or all of the tasks that would be within a budget and schedule for implementation as part of a scope of work immediately after this RFP. Task 3 – Systems Engineering Documentation and Process Verification Creating FHWA Systems Engineering documentation, as described in the WSDOT Design Manual Chapter 1050, Clark County design and contractor construction expansion the county’s Bluetooth data collection locations. This document will explain the data sharing links currently between county field devices and Portland State University’s Portal interface including continuing use of the regional data clearing house for an expansion of data feeds and data processing and new reporting features with this project as described in tasks one and two. The Systems Engineering document will include verification processes in the Systems Engineering objectives once task one and two are complete to include the creation of a Concept of Operations document.