4.0 SCHEDULE AND RESPONSIBILITY
Table 4-1 shows the timeframe for the the pre- and post-deployment data collection efforts for each of the major UPA projects affecting traffic system data. The majority of the UPA projects are expected to be operational by December 2009. Data collection should continue through November 2011 to provide a full year of post-deployment data following the completion of the HOT lane from I-494 to 46th St., which will be operational by October 2011.
Table 4-1. Time Frame for Pre- and Post-Deployment Data Collection Efforts
| Project Element |
Implementation Date |
Pre-Deployment Data Collection |
Post- Deployment Data Collection |
| HOT Lanes – Burnsville Parkway to I-494 |
10/09 |
10/08 – 10/09 |
10/09 – 11/11 |
| PSDL – 46th St to Downtown |
10/09 |
10/08 – 10/09 |
10/09 – 11/11 |
| Auxiliary Lanes/Collector Ramps |
10/09 |
10/08 – 10/09 |
10/09 – 11/11 |
| HOT Lanes – I-494 to 46th St. |
10/10 |
10/08 – 10/10 |
10/10 – 11/11 |
As described in previous sections, most of the traffic data needed to analyze the effects of the Minnesota UPA projects will be obtained from Mn/DOT's RTMC. These data are continuous and can be analyzed throughout the deployment period. Monthly downloads of the traffic sensor data will be obtained, examined, and analyzed. Due to construction in the I-35W corridor, a historic trend line will be established as part of the post-deployment data collection and analysis. This trend line is needed to account for the different travel conditions experienced during the construction period, which include some traffic lane and ramp closures, and the inoperability of some loop detectors during the construction. To account for this situation, archived loop data will be obtained and examined from 2006 and 2007 to reflect pre-deployment conditions.
Vehicle occupancy data require special data collection studies. It is recommended that these data be collected quarterly. A proposed data collection schedule is shown in Table 4-2. Note that if this data collection schedule is followed, there will be only two data collection efforts that will occur prior to the opening of the first projects.
Table 4-2. Suggested Data Collection Schedule for Continuous and Special Data Collection Efforts
| Type of Data/Data Source |
Data Collection Frequency |
Recommended Months of Data Collection |
| Mn/DOT RTMC Detection System Data |
Continuous |
10/08 – 10/11 |
| Vehicle Occupancy Counts |
Quarterly |
7/09,10/09 (Before) 1/10, 4/10, 7/10, 10/10, 1/11, 4/11, 7/11, 10/11 |
The responsibilities for this test plan include:
- Battelle team members will download the Mn/DOT RTMC detector system data on a monthly basis. The data checks will be performed to identify possible outlier or suspect data. Battelle team members will utilize the on-line City of Minneapolis TCDS to obtain needed arterial traffic counts.
- Mn/DOT will sponsor the vehicle-occupancy counts and will provide the results to the Battelle team.
- Mn/DOT will provide the Battelle team members with the quarterly I-35W HOT lane reports and Battelle team members will analyze the data.
- Battelle team members will analyze the data and will use the data, along with data from the RTMC Incident Logs and FIRST Dispatch Logs collected in the safety test plan, to assess the measures of effectiveness. Battelle team members will presents the results in the interim reports and the final Minnesota UPA national evaluation report.
