Scalable AZTECH data server enhancements for planning and operations: user services requirements study

              Scalable AZTechTM Data Server Enhancements for Planning and Operations:
User Services Requirements Study



Prepared for:



Maricopa County Department of Transportation

Prepared by:



November 8, 1999



Table of Contents 1.0 INTRODUCTION ............................................................................................................................. 1 1.1 Description of the User Services Requirements Study ................................................................. 1 2.2 Project Approach ..........................................................................................................................1 2.0 REVIEW OF EXISTING AZTECHTM DATA ...................................................................................3 2.1 Existing Data Available Through AZTechTM ............................................................................... 3 2.2 Potential Gaps in AZTechTM Server Data.....................................................................................3 . 3.0 STAKEHOLDER INPUT-APPROACH .............................................................................................5 3.1 Stakeholder Identification ............................................................................................................ 5 3.2 Survey Instrument ........................................................................................................................5 3.3 Stakeholder Interviews ................................................................................................................. 7 4.0 RESULTS AND FINDINGS .............................................................................................................. 8 4.1 Survey Results............................................................................................................................. 8 . 4.2 Focus Groups/Existing Meetings/Interviews .............................................................................. 13 4.3 Summary of Findings ................................................................................................................. 14 5.0 CONCLUSIONS ............................................................................................................................. 17 5.1 Lessons Learned .........................................................................................................................17 5.2 Next Steps ................................................................................................................................. 17 Appendix A ..............................................................................................................................................A Appendix B...............................................................................................................................................B . Appendix C...............................................................................................................................................C .



Kimley-Horn and Associates, Inc.



Page i



Scalable AZTechTM Data Server Enhancements for Planning and Operations: User Services Requirements Study



1.0 INTRODUCTION

1.1 Description of the User Services Requirements Study In 1996, the Federal Highway Administration awarded a Model Deployment Initiative grant to the Phoenix Metropolitan Area to assist in the deployment and integration of a model Intelligent Transportation System (ITS). Using funding from both the federal grant and the project partners, a joint public and private partnership worked together under the name AZTechTM to deploy and integrate ITS and provide real time travel information to the public. The AZTechTM project, in addition to the Arizona Department of Transportation (ADOT) Freeway Management System, local cities, fire, police, emergency management and city development services, has been generating data that are relevant to the transportation community. Not all of these data are currently being archived nor are they readily available to planners and many other potential end users. Realizing the need to capture data available though ITS infrastructure, the Maricopa County Department of Transportation (MCDOT) developed the Scalable AZTechTM Data Server Enhancements for Planning and Operations Project. The enhancements will allow data that is currently collected on the AZTechTM data server to be archived. The archived data will then be made available to local agencies for such uses as planning, modeling, or any other need that exists. For the purpose of this study, the enhancements planned for the AZTechTM data server will be referred to as the Regional Archived ITS Data Server (RADS). The long-term goal of the RADS project is to implement hardware and software for storing both AZTechTM and other data as they come on-line, and allow for the data to be accessed, shared, and utilized. All work completed as part of this project will be consistent with the National ITS Architecture. The implementation phase of this project was recommended by the Maricopa Association of Governments (MAG) ITS Committee for inclusion in the region's Transportation Improvement Program and is currently programmed for FY 2000 with federal CMAQ funds. In order to properly plan for and design the data server, MCDOT contracted with the firm of KimleyHorn and Associates, Inc. to conduct a User Services Requirements Study to determine the need for archived data in Maricopa County. The study solicited input from a variety of stakeholders throughout Maricopa County to determine the usefulness of the AZTechTM data to their agencies, as well as their need for additional data not currently available through the AZTechTM server. The data that stakeholders currently archive and the need for additional archived data was documented. The results of the study include comprehensive lists of all archived ITS data needs of the stakeholders in Maricopa County, ranked by various categories. These lists can be used to as a tool to help define the inputs, size, and architecture for the RADS. The User Services Requirements Study is the first phase in a multi-phase project to design, build, and deploy the RADS. 2.2 Project Approach The existing data elements available through the AZTechTM data server were reviewed and documented. These elements along with additional data elements not currently collected through AZTechTM were presented to stakeholders to determine their need for the data. Stakeholders were selected by working with the AZTechTM Data Server User Services Requirements Sub-committee. The selected stakeholders



Kimley-Horn and Associates, Inc.



Page 1



Scalable AZTechTM Data Server Enhancements for Planning and Operations: User Services Requirements Study



represented a broad range of both public and private data users, including traffic engineers, planners, emergency service providers, airports, universities, and private sector participants. To solicit input from as many stakeholders as possible, a four-part input process was developed. Input was gathered through the use of a detailed survey, focus groups, presentations at existing meetings, and one-on-one interviews. Part one of the stakeholder input process consisted of a detailed survey that was developed to allow stakeholders to select exactly the data types they desire as well as provide input on the data format and time increments preferred. The survey included data categories and data elements as defined in the National ITS Architecture Archived Data User Service. Part two consisted of six focus groups used to discuss the data needs of stakeholders. The focus groups allowed interaction between stakeholders to discuss issues concerning the archived data server as well as a chance for stakeholders to express opinions and suggestions for the RADS. Part three of the input process involved presenting the RADS project at existing meetings to stakeholder groups throughout Maricopa County. These groups included the MAG ITS Committee, Valley Metro Operations Meeting, and the AZTechTM Public Safety Communications Committee. Finally, to reach key stakeholders or those that were not able to provide feedback through other methods, direct one-on-one interviews were conducted. This method allowed each interviewed stakeholder to provide a very detailed response to the needs of his or her agency. The finding from these various methods of input have been summarized in Section 4.0 of this report.



Kimley-Horn and Associates, Inc.



Page 2



Scalable AZTechTM Data Server Enhancements for Planning and Operations: User Services Requirements Study



2.0 REVIEW OF EXISTING AZTECHTM DATA

2.1 Existing Data Available Through AZTechTM The enhancements to the AZTechTM Server will allow transportation data to be pulled directly from the server and archived for planning, modeling, and other purposes as needed. The existing data available through the AZTechTM Data Server was reviewed to determine what data stakeholders will have access to initially through the RADS. Existing AZTechTM data is comprised of three primary data categories: � ADOT Freeway Management System Data; � Local Jurisdiction Traffic Signal Data; and � Transit Advanced Automated Vehicle Location Data. Data in these three categories will be made available to stakeholders initially. Future AZTechTM projects will implement additional data collection capability to the AZTechTM Server that could be integrated into the RADS as well. The existing AZTechTM data available on the AZTechTM Server is summarized in Table 2-1. The AZTechTM data was considered in the stakeholder input process to determine user service requirements for archived data. Stakeholders were given an opportunity to comment on the usefulness of this data; their ability to archive and retrieve similar data at the present time, and the time increments and format in which they would like the data archived. 2.2 Potential Gaps in AZTechTM Server Data Although the initial concept of the RADS is to archive only existing AZTechTM data, new data elements will be added to the AZTechTM Server over time that could be incorporated into the RADS. To ensure that proper consideration was given to potential data elements that could be included in the RADS, all currently foreseeable data elements were included in the surveys and interviews of stakeholders. The following data categories not currently being collected by the AZTechTM Server were included in the survey: � � � � Arterial Data; Parking Management Data; Commercial Vehicle Operation Data; and Weather Data.



Stakeholder feedback on the desirability of these data elements will assist MCDOT in prioritizing the types of data collected for future use in the RADS.



Kimley-Horn and Associates, Inc.



Page 3



Scalable AZTechTM Data Server Enhancements for Planning and Operations: User Services Requirements Study



Table 2-1 Existing AZTechTM Server Data Elements

Data Owner /Provider ADOT FMS Source Equipment Variable Message Sign Snapshot count Sign ID Status Message Operator Time-changed ADOT FMS Freeway Ramp Meter Signal Snapshot count Ramp ID State Minimum level Maximum level Mode Meter rate Status Norm volume HOV volume ADOT FMS Traffic Intersection Controller Snapshot count Intersection ID Status Volume Occupancy ADOT FMS Traffic Detector Loop Snapshot count Detector ID Flow level VPH average Occupancy avg. Speed average Lanes [8] Flow level (lane) VPH (lane) Occupancy (lane) Speed (lane) ADOT FMS Incident Management Incident ID Description Time sent Incident info Initiator Responder count Responders Characterization Freeway name Cross street Add location Severity level Lanes blocked Operator Agency Time changed Agency name Device ID Timing plan TP name Action Local Jurisdictions Traffic Signals Snapshot count Traffic Signal ID Status Volume Occupancy Transit AVL AVL Timestamp Bus stops Stop ID Route Bus ID Arrival Scheduled Arrival Message ID Bus Records Record Type Location Data Item Format/Units Table Count Numeric Multiple Character Character Numeric Table Count Numeric Enabled/failed Numeric Numeric Multiple Numeric Multiple Numeric Numeric Table Count Numeric Multiple Numeric Numeric Table Numeric Numeric A thru E Numeric Numeric Numeric Table Numeric Numeric Numeric Numeric Structure Numeric Character Timestamp Structure Structure Count Mult structure Code Character Character Character 1 thru 4 Bit mask Character Character Timestamp Character Numeric Numeric Character Accept/decline Table Count Numeric Multiple Numeric Numeric Table Character Count Numeric Numeric Numeric Numeric Character Numeric Count Status/alarm Lat./Long. Data Freq. 20 seconds Store Freq. Item Description 1 min Number of snapshots in table Snapshot/state of 1 sign Sign status, multiple parameters Message displayed on sign Name of message loader Time message was loaded 20 seconds 1 min Number of snapshots in table Snapshot Meter on/off state Sets metering level of ramp from full green to full red Controls various operating modes Vehicles/minute setting of meter Status of meter subsystems Normal lane volume Carpool lane volume 20 seconds 1 min Number of snapshots in table Snapshot/state of 1 intersection State & timing plan of intersection Vehicle count for this 20 sec frame Detector occupancy time / 20 sec Table of link segment reports Number of links in report Snapshot of 1 link/segment Average flow of all lanes Vehicle per hr - average Loop occupancy - average Speed average all lanes Table of per-lane data Flow for this lane Vehicles per hour this lane Percent time vehicle on detector Speed of this lane Incident number Description of incident Time of incident Specifics of incident Agency & agent reporting incident Number of responding agencies Agencies responding to incident Incident character code Freeway of incident Nearest cross street Additional location information Severity of incident Detail of blocked lanes Reporting operator name Reporting agency name Time change made Changing agency ID number of device ID number of device timing plan Name of device timing plan Acceptance by device's agency 20 seconds 1 min Number of snapshots in table Snapshot/state of 1 intersection State & timing plan of intersection Vehicle count for this 20 sec frame Detector occupancy time/20 sec 1-2 minutes Table time/date stamp Number of stops in table Unique bus stop ID number Route number Bus number Time to anticipated arrival Scheduled arrival time Unique ID of this bus tracking table Number of Busses in table Selects status or alarm message Location of bus



20 seconds



1 min



As Occurs



As Occurs



Kimley-Horn and Associates, Inc.



Page 4



Scalable AZTechTM Data Server Enhancements for Planning and Operations: User Services Requirements Study



3.0 STAKEHOLDER INPUT-APPROACH

3.1 Stakeholder Identification The RADS was initially conceptualized as having a role of archiving only local and regional data. However, it is conceivable that the data server could expand beyond a regional function and serve as a statewide data repository at some time in the future. With that in mind, it was decided that stakeholder input should be gathered primarily from the Maricopa County Region but input from areas outside of the County should also be considered. Eleven initial groups were identified for providing input into user needs. These included the following: � � � � � � � � � � � ADOT; Municipal Metropolitan Planning Organizations; MCDOT; Federal Government; City ITS/Traffic; City Planning; Transit; Emergency Management; Airports; Universities; and Private Sector.



From the above eleven stakeholder groups, a total of 88 stakeholders were identified representing both the Maricopa County Region and other areas of Arizona. For example, the ADOT stakeholders included traffic engineers and planners from Phoenix, as well as a member of the Motor Vehicle Division from southern Arizona and a researcher working on statewide data collection. Municipal Metropolitan Planning Organizations included input from members of both the Maricopa and Pima Associations of Governments. City ITS/Traffic and Planning input came from large cities in Maricopa County as well as small cities such as El Mirage and Avondale. Private sector input came from both AZTechTM partners involved in privatized traffic information dissemination and the American Automobile Association. A complete list of all stakeholders that provided input is included in Appendix A. 3.2 Survey Instrument To allow an analytical analysis of the data needs of the stakeholders, a survey questionnaire was developed and sent to the 88 identified stakeholders. The purpose of the survey was to determine the need for archived transportation data in Maricopa County. Three levels of AZTechTM data were identified: Data Areas, Data Categories, and Data Elements. These are shown inTable 3-1.



Kimley-Horn and Associates, Inc.



Page 5



Scalable AZTechTM Data Server Enhancements for Planning and Operations: User Services Requirements Study



Table 3-1 Survey Data Area, Categories, and Elements

Data Area Freeway Data Data Category Freeway Traffic Flow Surveillance Data Freeway Variable Message Sign Freeway Ramp Meters Arterial Data Arterial Traffic Flow Surveillance Data Arterial Traffic Signal Phasing Arterial Variable Message Sign Parking Management Data Transit Data Parking Management Transit Usage Transit Route Deviations Transit Schedule Adherence Incident Management and Safety Data Incident Logs Emergency Vehicle Dispatch Records Emergency Vehicle Locations Train Arrivals at Hwy. Rail Intersections Construction and Work Zone ID Commercial Vehicle Operations Data Weigh-In-Motion HazMat Cargo Identifiers Fleet Activity Reports Cargo Identification Border Crossings On-Board Safety Data Weather Data Weather Data Data Elements avg. veh. per hour, avg. speed, etc. sign status, message, etc. ramp ID no., metering rate, etc. volume, occupancy, etc. no. of phases, cycle length, etc. sign status, message, etc. time, available spaces, etc. route no., vehicle boardings, etc. route no., location (lat./long), etc. transit route, actual arrival time at station, etc. incident location, type of incident, etc. dispatch time, arrival time, etc. vehicle ID no., location intersection location, arrival time, etc. work zone location, lanes blocked, etc. WIM location, vehicle weights, etc. type of hazmat, route, etc. motor carrier, citations, etc. cargo type, origin/destination, etc. motor carrier name, cargo type, etc. driver log, subsystem status (e.g. brakes), etc. precipitation, temperature, etc.



The data areas, categories, and elements were determined from the existing data collected by the AZTechTM Data Server and the National ITS Architecture Archived Data User Service specifications. Survey participants were asked to answer five questions for each data element: � � � � � Importance of data to your agency? (Ranked 1 to 5, 1-Not Important, 5-Critical) Is data available to you from your jurisdiction? (Yes/No) Would you like data from other jurisdictions? (Yes/No) Desired time increments of data? (30 sec, 1 min., daily, etc.) Desired format of data? (ASCII, dbase, spreadsheet, etc.)



In addition, space was provided to give a ranking of the overall importance of the data category that summarizes the cumulative importance of the data elements. A section was also provided for additional comments regarding the data elements or categories. An example of the Stakeholder Survey instrument is provided in Appendix B.



Kimley-Horn and Associates, Inc.



Page 6



Scalable AZTechTM Data Server Enhancements for Planning and Operations: User Services Requirements Study



3.3 Stakeholder Interviews In addition to the surveys, input was also solicited from stakeholders through focus groups, presentations at exiting (regularly scheduled) meetings, and one-on-one interviews. Six focus groups were set up and each stakeholder that received a survey was invited to attend. The focus groups were scheduled at various times over a three-week period and held at the offices of MAG, MCDOT, and the ADOT Traffic Operations Center. A brief presentation was provided to explain the User Services Requirements Study and the vision for the RADS. After the presentation and an open question and answer period, feedback was solicited from stakeholders regarding such topics as desired data, methods for disseminating data, other sources of archived data, and value of data to each stakeholder's agency. In additional to the focus groups, several presentations were made at existing meetings within the Maricopa Region to reach stakeholders that were not planning to attend the focus groups. Presentations were given at the following meetings: � MAG ITS Committee; � Valley Metro Operations Meeting (Transit Providers); and � AZTechTM Public Safety Communications Committee. Finally, one-on-one interviews were conducted with key stakeholders that were not able to attend focus groups or existing meetings. These interviews provided an opportunity for the stakeholders to give a more detailed response then the survey allowed, as well as make suggestions on how they would like the RADS to be designed and the interface they would like to use to access the archived data. The findings of the surveys, focus groups, existing meetings and one-on-one interviews are discussed in Section 4.0 of this report.



Kimley-Horn and Associates, Inc.



Page 7



Scalable AZTechTM Data Server Enhancements for Planning and Operations: User Services Requirements Study



4.0 RESULTS AND FINDINGS

4.1 Survey Results A total of 37 survey responses were completed through the stakeholder involvement process. Many of the surveys represented the views of multiple personnel or departments at a single agency. In some cases, Kimley-Horn and Associates completed survey questionnaires, based on interviews conducted with stakeholders. The surveys were compiled to determine which data categories and data elements are most critical to stakeholders. The existing availability of data, desired time increments, and data format were also reviewed to ensure that the RADS provides data that is useful to the stakeholders. Appendix C presents four detailed reports from the survey questionnaire. These reports include: � � � � Data Importance By Category Report; Data Availability By Category Report; Data Storage Time Increment Report; and Desired Data Storage Format by Category Report.



Data Importance By Category Data importance to the stakeholders can be measured through two methods. In Appendix C, the Data Importance By Category Report provides both the number of stakeholders selecting each data element, as well as the average score each data element received based on the 1 to 5 scale presented in the survey. The results of the Data Importance By Category Report are displayed in Figure 4-1. The horizontal bar represents the number of stakeholders selecting at least one data element in the data category (median = 12.5). The number to the right of the horizontal bar represents the average importance score of the data category on a scale of 1 to 5, with 5 representing the highest possible score. Based on the number of stakeholders selecting the data category, Arterial Traffic Flow Surveillance data is the most important data element for the stakeholders. This ranking is consistent with the feedback that was received through the focus groups and interviews. Other critical data categories include Freeway Traffic Flow Surveillance, Transit Usage, and Incident Logs. However, the importance scores of the data categories are different from the category rankings based on the total number of stakeholders selecting data elements in each category. Based on the importance score rankings, Weigh-In-Motion Data, Transit Schedule Adherence, Construction/Work Zone Data, and Border Crossing Data are the most important. These data categories represent data that has been ranked very important by a select number of stakeholders, however there are a smaller number of stakeholders that desire this data compared to the highest ranked data categories by number of stakeholders selecting the category.



Kimley-Horn and Associates, Inc.



Page 8



Scalable AZTechTM Data Server Enhancements for Planning and Operations: User Services Requirements Study



Figure 4-1 Data Category Rankings



Arterial Traffic Flow Surveillance Freeway Traffic Flow Surveillance Transit Usage Incident Logs Parking Management Traffic Signal Phasing Construction/Work Zone ID Weather Data

3.46 3.84 4.1 4 3.69 3.48 3.59 3.51 4.1 (Importance Scale 1 5) 7 3.1 5 3.28 3.35 3.83 4.00 4.1 0 3.20 3.56 3.77 4.1 6 3.88 3.94 3.47



4.07



Data Categories



Freeway Ramp Meters Transit Schedule Adherence Arterial VMS Transit Route Deviations Train Arrivals - Hwy Rail Intersections Freeway VMS Weigh-In-Motion Data Fleet Activity Reports HazMat Cargo Identifiers Cargo Identification Emergency Veh. Locations Emergency Veh. Dispatch Records Border Crossings On-Board Safety 0 5



1 0



1 5



20



25



30



35



40



Numbe r of Stakeholders Responding to Category



To assist in evaluating survey results, Figure 4-2 presents a profile of the type of stakeholders responding to the survey. Stakeholders have been divided into eight categories: Planning, Traffic/ITS, Transit, Aviation, Commercial Vehicle Operations (CVO), Education, Emergency Management, and Private Sector Information Provider. While the large number of transportation planners and traffic/ITS stakeholders responding to the survey may present a bias towards data that is most related to their functions, it should be noted that the people that responded to the survey are also most likely the stakeholders that will eventually be users of the data. By the same token, the low response from the nontraditional stakeholders may indicate that these stakeholders would also be less likely to use the data that will be available from the RADS.



Kimley-Horn and Associates, Inc.



Page 9



Scalable AZTechTM Data Server Enhancements for Planning and Operations: User Services Requirements Study



Figure 4-2 Stakeholder Categories Responding



Transit 8%



Aviation 6%



CVO 8% Education 3% Emergency Mgt. 6%



Planning 31%



Private Sector IP 8%



Traffic/ITS 30%



The previously introduced Figure 4-1 shows the data categories that were selected the most often. To provide a more detailed analysis of the data, Table 4-1 lists the individual data elements that were most often selected by stakeholders as having value to their agencies. In most instances, the data elements that were most selected correspond closely to the most popular data categories. These are the data elements that the stakeholders showed the most interest in obtaining in archived form. The Data Importance By Category Report in Appendix C provides a complete listing of every data element, the number of stakeholders selecting the data element, and the average score of the data element on the 1 to 5 scale.



Kimley-Horn and Associates, Inc.



Page 10



Scalable AZTechTM Data Server Enhancements for Planning and Operations: User Services Requirements Study



Table 4-1 Data Elements Ranked Highest By Stakeholders Stakeholders Responding To Data Element 32 27 25 25 24 21 20 20 20 19 18 18 18 19 18 18 17 17 16 16 16 16 21 21 20 17 17 17 17 16 17 16 16 Average Score 4.13 4.15 3.84 4.16 3.92 3.62 3.60 3.60 3.55 2.63 3.61 3.28 3.22 4.16 4.17 3.83 3.94 3.59 4.19 4.19 4.25 3.69 3.86 4.00 4.10 4.24 4.06 4.18 3.65 3.56 4.24 3.75 3.94



Data Categories Arterial Traffic Flow Surveillance Data



Data Elements Volume Speed Occupancy Location of detection stations Average vehicles per hour Average speed Individual vehicles per hour Vehicle classification Average occupancy Vehicle weight Detector identification number Individual lane occupancy Individual lane speed Severity level Type of incident Lanes blocked Cause Hazmat involved Clearance time Incident begin time Initiator Police accident report reference Origin and destination numbers Route number Vehicle boardings Construction/work zone location Lanes/shoulders blocked Time/date construction Lot location Lot size Signal location Left turn treatment Cycle length/green time



Freeway Traffic Flow Surveillance Data



Incident Logs



Transit Usage



Construction and Work Zone Identification Parking Management Traffic Signal Phasing



Kimley-Horn and Associates, Inc.



Page 11



Scalable AZTechTM Data Server Enhancements for Planning and Operations: User Services Requirements Study



Data Availability By Category The Data Availability By Category Report in Appendix C provides a detailed description of the availability of each data element to stakeholders. In many cases, it was found that stakeholders had access to certain types of data from within their own jurisdictions but did not have access to data from surrounding jurisdictions. Data Storage Time Increments/Desired Data Storage Format by Category Appendix C also includes reports on the Data Storage Time Increments and the Desired Data Storage Format by Category. These reports indicate by each data element the desired time increments and the preferred format for storing the data. Table 4-2 summarizes the desired data storage time increments and format for each data category. The most common time increments and data formats are indicated. Data storage time increments ranged from 30 seconds to daily to 6-months. Typically, it is recommended that data be stored in as small a time increment as practical. Those that desire data in larger increments, such as daily traffic counts instead of 5-minute counts, will be able to easily manipulate the 5-minute data to obtain daily counts. Data formats selected included Microsoft Access, ASCII, spreadsheets, GIS, and Uniform Traffic Database Format (UTDF2). In many cases, stakeholders indicated that they would like the archived data in a database format but did not specify a specific type. This is indicated in Table 4-2 as DBMS Database Management System.



Kimley-Horn and Associates, Inc.



Page 12



Scalable AZTechTM Data Server Enhancements for Planning and Operations: User Services Requirements Study



Table 4-2 Preferred Data Storage Time Increments and Formats

Recommended Time Increment Most Common Time Increments Selected in Survey Arterial Traffic Flow Surveillance 1 min/5 min/ 1 or 5 min increments Data 15 min/daily Arterial Variable Message Sign 5 min/daily Status by 5 minute increments or message information as needed Border Crossings No survey responses No suggested increments Cargo Identification Daily/Monthly Daily or monthly Construction and Work Zone Daily Daily Identification Emergency Vehicle Dispatch 5 min 5 minute increments or record per Records dispatch Emergency Vehicle Locations 5 min 5 min Fleet Activity Reports Daily/annual Update records consistent with time interval new data is entered Freeway Ramp Meters 1 min/15 min/weekly 1 to 15 min increments Freeway Traffic Flow 5 min/15 min/ 5 or 15 min increments Surveillance Data hourly/daily Freeway Variable Message Sign 5 min/daily Status by 5 minute increments or message information as needed HazMat Cargo Identifiers 30 min/daily 30 min to daily Incident Logs 5 min/10 min/1 day Update per incident logged On-board Safety Data daily daily Parking Management 10 min/hourly 5 to 15 min increments Traffic Signal Phasing 15 min/30 min/hourly 15 min increments Train Arrivals at Highway Rail 5 min/1 hour 5 min Intersections Transit Route Deviations 30 sec/3 min/5 min 30 sec to 5 min Transit Schedule Adherence 3 min/5 min 3 to 5 min Transit Usage 3 min/15 min/daily 3 to 15 min Weather Data 10 min/daily 10 to 15 min Weigh-in-Motion (WIM) Data 10 min/daily 10 min to hourly DBMS - Unspecified Database Management System Data Category Most Common Data Format Selected in Survey ASCII/DBMS ASCII/DBMS Spreadsheet ASCII ASCII/DBMS/ Spreadsheet Spreadsheet Spreadsheet Spreadsheet ASCII/DBMS ASCII/DBMS ASCII/DBMS Spreadsheet Spreadsheet Spreadsheet ASCII/DBMS ASCII/DBMS DBMS ASCII/DBMS ASCII/DBMS ASCII/DBMS ASCII ASCII/Spreadsheet



4.2 Focus Groups/Existing Meetings/Interviews Focus groups, interviews, and presentations at existing meetings were used in addition to the surveys to gather input to determine user services requirements. The following issues were common among the various stakeholders: � Adequate methods for ensuring the integrity of the data that is fed into the RADS must be developed to ensure that the data available to stakeholders is usable. � A decision needs to be made early on whether the public will have access to the data as it may affect the way data is formatted on the RADS. � A graphical interface to the data would be useful, especially for obtaining traffic counts and signal phasing.



Kimley-Horn and Associates, Inc.



Page 13



Scalable AZTechTM Data Server Enhancements for Planning and Operations: User Services Requirements Study



� It was generally agreed that an interface through the Internet would be most useful. As the amount of data grows, storing older data on a medium such as a CD-ROM would be feasible. � There is a desire to archive not only existing traffic counts, but traffic projections for future years. Many stakeholders were interested in finding a method for storing past traffic projections that they could refer back to and check the accuracy of past models. � There are cases where the data from one agency may conflict with data from another agency. There is concern that the RADS, by archiving one agency's data, may be endorsing that data. � Many stakeholders felt that they needed to check their data and make adjustments to account for anomalies, such as loop detectors that fail. There was concern that making this raw data available through the RADS may mean a loss of credibility for those agencies. � The ALISS database, maintained by ADOT, provides much of the incident crash data that Emergency Services personnel require. In general, many of the stakeholders expressed that they were comfortable with the ALISS database and did not see a need to archive incident data that is available through this system. � Storage of existing roadway features would add usefulness to the data stored. � Stakeholders liked the idea of linking a RADS web page to other web pages of data providers in the region. Even if the RADS can not provide all archived transportation data, using the data server as a means for directing people to the correct location to retrieve data will be very useful. � Some local jurisdictions expressed a desire to make the RADS open to the public so that citizens could obtain traffic volumes directly from the RADS. Many cities spend time gathering traffic data at the request of citizens and would like to be able to direct them to a location on the Internet where this information can be obtained. � A record of past special events that may have affected traffic, such as sporting events or severe weather, may help stakeholders interpret data from the RADS more accurately. � There is a common concern among stakeholders over who will operate and maintain the RADS. Questions often arose regarding whether there would be a cost to access data from the RADS. 4.3 Summary of Findings The following presents a brief summary of the stakeholders' responses gathered through this study. Supporting detailed information is provided in the Appendices. As a high-level overview, Table 4-3 lists the highest-scoring data categories based on four different selection criteria. The data storage time increments were summarized previously in Table 4-2. It should be noted again that archiving data in the smallest time increment practical for that data element (as is usually determined by the agency collecting the data) may be the lowest maintenance approach that would also accommodate the largest group of archived data users. Data stored in small time increments can be post-processed by the end user to the desired level of aggregation, thus reducing the burden of additional data processing from the RADS.



Kimley-Horn and Associates, Inc.



Page 14



Scalable AZTechTM Data Server Enhancements for Planning and Operations: User Services Requirements Study



Table 4-3 Highest Scoring Data Categories CRITERIA

Most Desired Data Category, based on total number of stakeholders responding within the category (above the median total of 12.5 stakeholders responding within the category)



RANK

1 2 3 4 5 6 7 8 9 10 11 1 2 3 4 5 6 7 8 9 10 11 1 2 3 4 5 6 7 8 9 10 11 1 2 3 4 5 6 7 8 9 10 11



DATA CATEGORY

Arterial Traffic Flow Surveillance Freeway Traffic Flow Surveillance Transit Usage Incident Logs Construction/Work Zone ID Traffic Signal Phasing Parking Management Transit Schedule Adherence Freeway Ramp Meters Weather Data Arterial VMS Weigh-In-Motion Data Construction/Work Zone ID Transit Schedule Adherence Border Crossings Arterial Traffic Flow Surveillance Emergency Veh. Dispatch Records Transit Usage Incident Logs Freeway Ramp Meters Emergency Veh. Locations Traffic Signal Phasing Traffic Signal Phasing Incident Logs Arterial Traffic Flow Surveillance Data Freeway Traffic Flow Surveillance Data Transit Usage Transit Schedule Adherence Construction and Work Zone Identification Freeway Ramp Meters Freeway Variable Message Sign Weather Data Weigh-in-Motion (WIM) Data Incident Logs Freeway Traffic Flow Surveillance Data Traffic Signal Phasing Arterial Traffic Flow Surveillance Data Freeway Ramp Meters Transit Usage Freeway Variable Message Sign Transit Schedule Adherence Arterial Variable Message Sign Parking Management Weigh-in-Motion (WIM) Data



Most Important Data Category, based on the total score of data elements within the category (above the median score of 3.73)



Data Availability from Stakeholders'Jurisdition (above the median score of 16 votes within a category)



Data Most Desired from Other Agencies (above median score of 26 votes within a category)



Kimley-Horn and Associates, Inc.



Page 15



Scalable AZTechTM Data Server Enhancements for Planning and Operations: User Services Requirements Study



The responses indicating the most desired archived data storage formats converge on three primary formats: ASCII, DBMS, and spreadsheet. It is highly recommended that no spreadsheet data be stored on the RADS as the management of such format is highly difficult and prone to error. It is envisioned that the storage format will be dictated to the large degree by the system software and will be a DBMS-based; however, many of data elements that are now or will be in the future collected by the AZTechTM server, are provided natively in ASCII format and should be made available to the end user in the same format. As a result, ASCII and DBMS appear to be the preferred storage formats. It should be noted that a number of users expressed interest in geo-referenced data, i.e., data elements that can retried and located by their geographic coordinates. It is reasonable to expect that such requirements can be accommodated by the RADS, if not initially then as a the future enhancement. Many of today' DBMS used in data warehousing, such as OracleTM database, can easily accommodate nons visual and visual spacial queries on properly attributed data and thus should be considered as an option in the development of the RADS.



Kimley-Horn and Associates, Inc.



Page 16



Scalable AZTechTM Data Server Enhancements for Planning and Operations: User Services Requirements Study



5.0 CONCLUSIONS

5.1 Lessons Learned Stakeholder Participation This study once again put into perspective the difficulties one faces when attempting to conduct a survey of a representative sample of stakeholder population. One major difficulty lied in enticing a sufficient number of stakeholders to participate in focus groups specially organized for this study. It was found that it is much easier to obtain stakeholder participation and input through regularly scheduled meetings which they were already scheduled to attend and through one-on-one interviews. Data Desired through RADS As the summary reports indicate, there is a need to include data elements outside of what is currently available through the AZTechTM server in the RADS archived data distribution. In addition, as the RADS is put into use, it would be worthwhile to include end user feedback forms within the data access interface to allow for further input on what additional data elements may become desirable in the future. While each data element was scored based directly on the stakeholders' scores, it is clear that further attention should be directed towards the number of stakeholder "votes" for each data element and data category. This will help to develop a better understanding about the total end user population that is likely to be looking for those data types once the RADS system comes on-line. Data Formats The survey responses clearly indicate that a significant number of end users do not fully understand the issues related to available and practical data storage formats. This should be taken into consideration when making archived data available to the end users, to minimize the level of difficultly associated with accessing and post-processing of the archived data. Agency Participation A data distribution system is only as good as the data that it makes available to the user. A number of the stakeholders interviewed indicated that there may be perceived or real issues of liability and credibility associated with the data that the various agencies in Maricopa County would end up providing to the RADS system. These issues should be addressed by the RADS project. Access to RADS Most stakeholders who expressed their opinion on this subject indicated that the RADS system should be accessible to the public at large, primarily to alleviate the agencies' burden associated with data distribution on individual basis. 5.2 Next Steps The results and recommendations of this study should be incorporated into the conceptual design of the RADS system to the degree practical. Any long-term recommendations should be taken into account in the system expansion planning process.



Kimley-Horn and Associates, Inc.



Page 17



Scalable AZTechTM Data Server Enhancements for Planning and Operations: User Services Requirements Study



APPENDIX A - Stakeholder Input List



Kimley-Horn and Associates, Inc.



Page A



Scalable AZTechTM Data Server Enhancements for Planning and Operations: User Services Requirements Study



Regional Archived ITS Data Server Stakeholder Input Status

STAKEHOLDERS Agency State ADOT ADOT ADOT ADOT ADOT ADOT ADOT MPO MAG MAG MAG PAG PAG PAG County MCDOT MCDOT MCDOT MCDOT MCDOT MCDOT MCDOT Cities (ITS/Traffic) City of Chandler City of Chandler City of Glendale City of Mesa City of Scottsdale City of Tempe City of Tucson Cities (Planning/Public Works) City of Peoria City of Scottsdale City of Tempe Town of Gilbert City of Phoenix City of El Mirage City of Avondale Federal FHWA US Customs Office of Motor Carriers Tucson Eric John Ice O'Reilly a a Planning Planning Planning Planning Street Transportation Department of Public Works Department of Public Works Chad Jorie Robert Scott Don Marty Bill Daines Bresnahan Yabes Anderson Herps Nana Bates a a a a a a a a ITS/Traffic ITS/Traffic ITS/Traffic ITS/Traffic ITS/Traffic ITS/Traffic Traffic Ty Brian Richard Jerry Michelle Jim Richard Hofflander Latte Janke O'Farrell Kogl Decker Nassi a a a a a a a a a Planning Engineering Division ITS/Traffic ITS Planning Planning Planning Chris Dave Bob Scott Ed Amy Bob Plumb Wolfson Steele Nodes Fritz Carathers Woodring a a a a a a a Modeling GIS ITS ITS Planning Planning Mark Rita Sarath Paul Charles Richard Schlappi Walton Joshua Casertano Hodges Corbett a a a a a a a a Planning ATRC Motor Vehicle Division Traffic Operations Center Transportation Tech. Group Traffic Engineering Traffic Engineering Bob Estomih George Dottie Tim Tom Mohamed Pike Kombe Bays Shoup Wolfe Parlante Youssef a a a a a a a a a a Department First Name Last Name DATA COLLECTION METHOD Focus Group or Existing Mtg Personal Interview Survey



STAKEHOLDERS Agency Transit Valley Metro Phoenix Transit RPTA RPTA ADOT Transit Emergency Management Chandler Fire MCDOT Airports Phoenix Sky Harbor Airport Williams Gateway Airport Universities Arizona State University Private Sector AAA ECOTEK Computran (HCRS, RCRS) ETAK TranSmart Total Number of People Planning Project Manger Project Manager Vice President/Project Mgr. Project Manager David John Tomas Larry Connie Cowley Reimers Guerra Sweeney Li 51 Planning Dept. Mary Kihl Planning Planning Richard Art Traill Allen Planning Incident Management Coordinator Gordon Chuck Barton Manuel Planning Planning Director of Grants and Contracting Planning Transit Coordinator Scott Dale Bryan Paul Thalia Miller Hardy Jungwirth Hodgins Pratt Department First Name Last Name



DATA COLLECTION METHOD Focus Group or Existing Mtg a a a a a a a a a a a a Personal Interview Survey



a a



a a a a



a a a a a



19



10



38



APPENDIX B - Example Survey



Kimley-Horn and Associates, Inc.



Page B



Scalable AZTechTM Data Server Enhancements for Planning and Operations: User Services Requirements Study



Stakeholder Survey - Regional Archived ITS Data Server

Sponsored by the Maricopa County Department of Transportation

Introduction The AZTechTM Model Deployment Initiative Project has been putting features in place that are generating considerable amounts of transportation data. In addition, the ADOT Freeway Management System, local cities, fire, police, emergency management and city development services also generate data that are relevant to the transportation community. These data are not currently being archived and are not readily available to planners and other potential end users. The purpose of this survey is to determine the need for data from potential stakeholders. The long-term goal of this T project is to implement hardware and software for storing both AZTech M and other data as they come on-line, and allow for it to be accessed and put to use. All work completed on this assignment will be consistent with the National Intelligent Transportation System Architecture. Instructions Thank you for participating in this survey to determine the need for data to be archived in the region. In order to understand the data needs of stakeholders, we ask that you complete the attached survey. For each category of data listed, please rank the overall importance of the data to the function your agency performs. In addition to general data categories, specific data elements are also listed. Please indicate the importance of these data elements as well as current availability of the data, desired time increments of the data, desired format of the data, and any other comments you may have. Space is provided at the end of each data category to add additional data elements. If a data category has not been included in this form that would be important to your agency, please provide the data category and data elements in the space at the end of the survey. Please return completed surveys to Tom Fowler by fax at 602-944-7423, or mail to Kimley-Horn and Associates, Inc., 7600 N. 15th Street, Suite 250, Phoenix, Arizona 85020 no later than July 23, 1999. Stakeholder Information Name _____________________________________ Title ______________________________________ Agency ____________________________________ Address ___________________________________ ___________________________________ Telephone _________________________________ Fax ______________________________________ E-mail ____________________________________ Please describe your position and the function of your agency:

_________________________________________________________________________________________________________ _________________________________________________________________________________________________________



Which of the following best describes the area in which you are primarily involved: ___ Transportation Planning ___ Air Quality ___ Transit ___ Commercial Vehicles ___ Emergency Response ___ Aviation ___ Traffic Engineering ___ Intelligent Transportation Systems ___ Private Sector Information Provider Other ________________________________________



Please indicate the name of anyone else in your agency that you feel may be interested in completing this survey: Name______________________________ Title___________________________ Telephone_____________________________________



Address_______________________________________________________________________________________________________________________________________________



Regional Archived ITS Data Server Page 1



Survey Questions

Regional Archived Data Server

Importance of data to your agency? Data Element

Not Needed Desirable Critical



1



2



3



4



5



Is data available Would you like to you from Desired time your data from other jurisdiction? jurisdictions? increments of data? Desired format? Yes/No Yes/No (e.g., 30 sec, 1 min, (e.g., ASCII, dbase, daily, etc.) spreadsheet, etc.)



Other comments?



FREEWAY DATA Freeway Traffic Flow Surveillance Data (possible uses: AADT, volumes and speeds for traffic forecasting models, congestion monitoring) Overall 1 2 3 4 5 __Yes __No __Yes __No detector identification number 1 2 3 4 5 __Yes __No __Yes __No _____________ _____________ _____________ _____________ average vehicles per hour 1 2 3 4 5 __Yes __No __Yes __No average occupancy 1 2 3 4 5 __Yes __No __Yes __No _____________ _____________ average speed 1 2 3 4 5 __Yes __No __Yes __No _____________ _____________ individual lane vehicles per hour 1 2 3 4 5 __Yes __No __Yes __No _____________ _____________ individual lane occupancy 1 2 3 4 5 __Yes __No __Yes __No _____________ _____________ individual lane speed 1 2 3 4 5 __Yes __No __Yes __No _____________ _____________ _____________ _____________ vehicle classification 1 2 3 4 5 __Yes __No __Yes __No vehicle weight 1 2 3 4 5 __Yes __No __Yes __No _____________ _____________ other ________________________________ 1 2 3 4 5 __Yes __No __Yes __No _____________ _____________ other ________________________________ 1 2 3 4 5 __Yes __No __Yes __No _____________ _____________ o NOT INTERESTED IN THIS DATA CATEGORY Freeway Variable Message Sign (possible uses: record of sign usage, review of incident response actions) Overall 1 2 3 4 5 __Yes __No __Yes __No sign identification number/location 1 2 3 4 5 __Yes __No __Yes __No sign status 1 2 3 4 5 __Yes __No __Yes __No message 1 2 3 4 5 __Yes __No __Yes __No name of message initiator 1 2 3 4 5 __Yes __No __Yes __No time message was initiated 1 2 3 4 5 __Yes __No __Yes __No other ________________________________ 1 2 3 4 5 __Yes __No __Yes __No other ________________________________ 1 2 3 4 5 __Yes __No __Yes __No o NOT INTERESTED IN THIS DATA CATEGORY



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________



_____________ _____________ _____________ _____________ _____________ _____________ _____________



_____________ _____________ _____________ _____________ _____________ _____________ _____________



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________



Freeway Ramp Meters (possible uses: volumes and ramp metering rates for microscopic traffic simulation models) Overall 1 2 3 4 5 __Yes __No __Yes __No ramp identification number 1 2 3 4 5 __Yes __No __Yes __No _____________ ramp metering begin time 1 2 3 4 5 __Yes __No __Yes __No _____________ ramp metering end time 1 2 3 4 5 __Yes __No __Yes __No _____________ metering rate 1 2 3 4 5 __Yes __No __Yes __No _____________ normal lane volume 1 2 3 4 5 __Yes __No __Yes __No _____________ HOV lane volume 1 2 3 4 5 __Yes __No __Yes __No _____________ ramp metering pre-emption time 1 2 3 4 5 __Yes __No __Yes __No _____________ other ________________________________ 1 2 3 4 5 __Yes __No __Yes __No _____________ other ________________________________ 1 2 3 4 5 __Yes __No __Yes __No _____________ o NOT INTERESTED IN THIS DATA CATEGORY



_____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________



Regional Archived ITS Data Server Page 2



Importance of data to your agency? Data Element

Not Needed Desirable Critical



1



2



3



4



5



Is data available Would you like to you from Desired time your data from other jurisdiction? jurisdictions? increments of data? Desired format? Yes/No Yes/No (e.g., 30 sec, 1 min, (e.g., ASCII, dbase, daily, etc.) spreadsheet, etc.)



Other comments?



ARTERIAL DATA Arterial Traffic Flow Surveillance Data (possible uses: AADT, volumes and speeds for traffic forecasting models) Overall 1 2 3 4 5 __Yes __No __Yes __No location of detection station 1 2 3 4 5 __Yes __No __Yes __No volume 1 2 3 4 5 __Yes __No __Yes __No occupancy 1 2 3 4 5 __Yes __No __Yes __No speed 1 2 3 4 5 __Yes __No __Yes __No other ________________________________ 1 2 3 4 5 __Yes __No __Yes __No other ________________________________ 1 2 3 4 5 __Yes __No __Yes __No o NOT INTERESTED IN THIS DATA CATEGORY Traffic Signal Phasing (possible uses: data for traffic simulation models) Overall 1 2 3 4 5 signal location 1 2 3 4 5 number of phases 1 2 3 4 5 cycle length/green time 1 2 3 4 5 signal coordination settings 1 2 3 4 5 signal pre-emption settings 1 2 3 4 5 left turn treatment 1 2 3 4 5 delay settings 1 2 3 4 5 actuated/pretimed settings 1 2 3 4 5 minimum pedestrian green 1 2 3 4 5 clearance interval 1 2 3 4 5 other ________________________________ 1 2 3 4 5 other ________________________________ 1 2 3 4 5 o NOT INTERESTED IN THIS DATA CATEGORY



_____________ _____________ _____________ _____________ _____________ _____________



_____________ _____________ _____________ _____________ _____________ _____________



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________



__Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes



__No __No __No __No __No __No __No __No __No __No __No __No __No



__Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes



__No __No __No __No __No __No __No __No __No __No __No __No __No



_____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________



_____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________



Arterial Variable Message Sign (possible uses: record of sign usage and review of incident response actions) Overall 1 2 3 4 5 __Yes __No __Yes __No sign identification number/location 1 2 3 4 5 __Yes __No __Yes __No sign status 1 2 3 4 5 __Yes __No __Yes __No message 1 2 3 4 5 __Yes __No __Yes __No name of message initiator 1 2 3 4 5 __Yes __No __Yes __No time message was initiated 1 2 3 4 5 __Yes __No __Yes __No other ________________________________ 1 2 3 4 5 __Yes __No __Yes __No other ________________________________ 1 2 3 4 5 __Yes __No __Yes __No o NOT INTERESTED IN THIS DATA CATEGORY PARKING MANAGEMENT DATA Parking Management (possible uses: parking utilization and needs studies) Overall 1 2 3 4 5 time of data collection 1 2 3 4 5 lot location 1 2 3 4 5 lot size 1 2 3 4 5 available spaces 1 2 3 4 5 other ________________________________ 1 2 3 4 5 other ________________________________ 1 2 3 4 5 o NOT INTERESTED IN THIS DATA CATEGORY



_____________ _____________ _____________ _____________ _____________ _____________ _____________



_____________ _____________ _____________ _____________ _____________ _____________ _____________



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________



__Yes __Yes __Yes __Yes __Yes __Yes __Yes



__No __No __No __No __No __No __No



__Yes __Yes __Yes __Yes __Yes __Yes __Yes



__No __No __No __No __No __No __No



_____________ _____________ _____________ _____________ _____________ _____________



_____________ _____________ _____________ _____________ _____________ _____________



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________



Regional Archived ITS Data Server Page 3



Importance of data to your agency? Data Element

Not Needed Desirable Critical



1



2



3



4



5



Is data available Would you like to you from Desired time your data from other jurisdiction? jurisdictions? increments of data? Desired format? Yes/No Yes/No (e.g., 30 sec, 1 min, (e.g., ASCII, dbase, daily, etc.) spreadsheet, etc.)



Other comments?



TRANSIT Transit Usage (possible uses: route planning, ridership reporting) Overall 1 2 3 bus identification number 1 2 3 route number 1 2 3 vehicle boardings 1 2 3 origin and destination numbers 1 2 3 other ________________________________ 1 2 3 other ________________________________ 1 2 3 o NOT INTERESTED IN THIS DATA CATEGORY



4 4 4 4 4 4 4



5 5 5 5 5 5 5



__Yes __Yes __Yes __Yes __Yes __Yes __Yes



__No __No __No __No __No __No __No



__Yes __Yes __Yes __Yes __Yes __Yes __Yes



__No __No __No __No __No __No __No



_____________ _____________ _____________ _____________ _____________ _____________



_____________ _____________ _____________ _____________ _____________ _____________



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________



Transit Route Deviations (possible uses: transit route planning, review of incidents which cause route deviations) Overall 1 2 3 4 5 __Yes __No __Yes __No time of data collection 1 2 3 4 5 __Yes __No __Yes __No bus identification number 1 2 3 4 5 __Yes __No __Yes __No route number 1 2 3 4 5 __Yes __No __Yes __No location (latitude/longitude) 1 2 3 4 5 __Yes __No __Yes __No other ________________________________ 1 2 3 4 5 __Yes __No __Yes __No other ________________________________ 1 2 3 4 5 __Yes __No __Yes __No o NOT INTERESTED IN THIS DATA CATEGORY Transit Schedule Adherence (possible uses: transit schedule planning) Overall 1 2 3 4 bus stop id number 1 2 3 4 bus identification number 1 2 3 4 transit route 1 2 3 4 scheduled arrival time at station 1 2 3 4 actual arrival time at station 1 2 3 4 other ________________________________ 1 2 3 4 other ________________________________ 1 2 3 4 o NOT INTERESTED IN THIS DATA CATEGORY



_____________ _____________ _____________ _____________ _____________ _____________



_____________ _____________ _____________ _____________ _____________ _____________



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________



5 5 5 5 5 5 5 5



__Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes



__No __No __No __No __No __No __No __No



__Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes



__No __No __No __No __No __No __No __No



_____________ _____________ _____________ _____________ _____________ _____________ _____________



_____________ _____________ _____________ _____________ _____________ _____________ _____________



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________



Regional Archived ITS Data Server Page 4



Importance of data to your agency? Data Element

Not Needed Desirable Critical



1



2



3



4



5



Is data available Would you like to you from Desired time your data from other jurisdiction? jurisdictions? increments of data? Desired format? Yes/No Yes/No (e.g., 30 sec, 1 min, (e.g., ASCII, dbase, daily, etc.) spreadsheet, etc.)



Other comments?



INCIDENT MANAGEMENT AND SAFETY Incident Logs (possible uses: incident response evaluations, safety reviews, change in incident rates) Overall 1 2 3 4 5 __Yes __No __Yes incident location 1 2 3 4 5 __Yes __No __Yes incident begin time 1 2 3 4 5 __Yes __No __Yes dispatch time 1 2 3 4 5 __Yes __No __Yes arrival time 1 2 3 4 5 __Yes __No __Yes clearance time 1 2 3 4 5 __Yes __No __Yes departure time 1 2 3 4 5 __Yes __No __Yes initiator (agency/person reporting incident) 1 2 3 4 5 __Yes __No __Yes responder (agency responding to incident) 1 2 3 4 5 __Yes __No __Yes type of incident 1 2 3 4 5 __Yes __No __Yes severity level 1 2 3 4 5 __Yes __No __Yes lanes blocked 1 2 3 4 5 __Yes __No __Yes hazmat involved 1 2 3 4 5 __Yes __No __Yes police accident report reference 1 2 3 4 5 __Yes __No __Yes cause 1 2 3 4 5 __Yes __No __Yes other ________________________________ 1 2 3 4 5 __Yes __No __Yes other ________________________________ 1 2 3 4 5 __Yes __No __Yes o NOT INTERESTED IN THIS DATA CATEGORY Emergency Vehicle Dispatch Records (possible uses: emergency management route planning) Overall 1 2 3 4 5 __Yes __No dispatch time 1 2 3 4 5 __Yes __No arrival time 1 2 3 4 5 __Yes __No clearance time 1 2 3 4 5 __Yes __No departure time 1 2 3 4 5 __Yes __No origin/destination 1 2 3 4 5 __Yes __No route 1 2 3 4 5 __Yes __No other ________________________________ 1 2 3 4 5 __Yes __No other ________________________________ 1 2 3 4 5 __Yes __No o NOT INTERESTED IN THIS DATA CATEGORY Emergency Vehicle Locations (possible uses: emergency management route planning) Overall 1 2 3 4 5 __Yes time of data collection 1 2 3 4 5 __Yes location 1 2 3 4 5 __Yes vehicle identification number 1 2 3 4 5 __Yes vehicle type 1 2 3 4 5 __Yes other ________________________________ 1 2 3 4 5 __Yes other ________________________________ 1 2 3 4 5 __Yes o NOT INTERESTED IN THIS DATA CATEGORY



__No __No __No __No __No __No __No __No __No __No __No __No __No __No __No __No __No



_____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________



_____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________



__Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes



__No __No __No __No __No __No __No __No __No



_____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________



_____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________



__No __No __No __No __No __No __No



__Yes __Yes __Yes __Yes __Yes __Yes __Yes



__No __No __No __No __No __No __No



_____________ _____________ _____________ _____________ _____________ _____________



_____________ _____________ _____________ _____________ _____________ _____________



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________



Regional Archived ITS Data Server Page 5



Is data available Would you like to you from Desired time your data from other Not Needed Desirable Critical Data Element jurisdiction? jurisdictions? increments of data? Desired format? 1 2 3 4 5 Yes/No Yes/No (e.g., 30 sec, 1 min, (e.g., ASCII, dbase, daily, etc.) spreadsheet, etc.) Train Arrivals at Highway Rail Intersections (possible uses: grade crossing safety and operational studies) Overall 1 2 3 4 5 __Yes __No __Yes __No intersection location 1 2 3 4 5 __Yes __No __Yes __No _____________ _____________ _____________ _____________ begin time (time train arrives at intersection) 1 2 3 4 5 __Yes __No __Yes __No end time (time train departs from intersection) 1 2 3 4 5 __Yes __No __Yes __No _____________ _____________ _____________ _____________ other ________________________________ 1 2 3 4 5 __Yes __No __Yes __No other ________________________________ 1 2 3 4 5 __Yes __No __Yes __No _____________ _____________ o NOT INTERESTED IN THIS DATA CATEGORY Importance of data to your agency? Construction and Work Zone Identification (possible uses: correlate with congestion and safety data) Overall 1 2 3 4 5 __Yes __No __Yes time/date of construction 1 2 3 4 5 __Yes __No __Yes construction/work zone location 1 2 3 4 5 __Yes __No __Yes lanes/shoulders blocked 1 2 3 4 5 __Yes __No __Yes other ________________________________ 1 2 3 4 5 __Yes __No __Yes other ________________________________ 1 2 3 4 5 __Yes __No __Yes o NOT INTERESTED IN THIS DATA CATEGORY



Other comments?



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________



__No __No __No __No __No __No



_____________ _____________ _____________ _____________ _____________



_____________ _____________ _____________ _____________ _____________



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________



COMMERCIAL VEHICLE OPERATORS Weigh-in-Motion (WIM) Data (possible uses: identification of areas needing overweight vehicle enforcement, vehicle weight studies) Overall 1 2 3 4 5 __Yes __No __Yes __No date of count 1 2 3 4 5 __Yes __No __Yes __No _____________ WIM location 1 2 3 4 5 __Yes __No __Yes __No _____________ vehicle weights 1 2 3 4 5 __Yes __No __Yes __No _____________ vehicle classification (by axle) 1 2 3 4 5 __Yes __No __Yes __No _____________ o NOT INTERESTED IN THIS DATA CATEGORY HazMat Cargo Identifiers (possible uses: HazMat route planning) Overall 1 2 3 type of hazmat 1 2 3 motor carrier name 1 2 3 route 1 2 3 time/date of trip 1 2 3 other ________________________________ 1 2 3 other ________________________________ 1 2 3 o NOT INTERESTED IN THIS DATA CATEGORY



_____________ _____________ _____________ _____________



__________________________________ __________________________________ __________________________________ __________________________________



4 4 4 4 4 4 4



5 5 5 5 5 5 5



__Yes __Yes __Yes __Yes __Yes __Yes __Yes



__No __No __No __No __No __No __No



__Yes __Yes __Yes __Yes __Yes __Yes __Yes



__No __No __No __No __No __No __No



_____________ _____________ _____________ _____________ _____________ _____________



_____________ _____________ _____________ _____________ _____________ _____________



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________



Fleet Activity Reports (possible uses: commercial vehicle safety studies) Overall 1 2 3 4 5 motor carrier name 1 2 3 4 5 citations 1 2 3 4 5 accidents 1 2 3 4 5 inspection results 1 2 3 4 5 other ________________________________ 1 2 3 4 5 other ________________________________ 1 2 3 4 5 o NOT INTERESTED IN THIS DATA CATEGORY



__Yes __Yes __Yes __Yes __Yes __Yes __Yes



__No __No __No __No __No __No __No



__Yes __Yes __Yes __Yes __Yes __Yes __Yes



__No __No __No __No __No __No __No



_____________ _____________ _____________ _____________ _____________ _____________



_____________ _____________ _____________ _____________ _____________ _____________



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________



Regional Archived ITS Data Server Page 6



Importance of data to your agency? Data Element

Not Needed Desirable Critical



1



2



3



4



5



Is data available Would you like to you from Desired time your data from other jurisdiction? jurisdictions? increments of data? Desired format? Yes/No Yes/No (e.g., 30 sec, 1 min, (e.g., ASCII, dbase, daily, etc.) spreadsheet, etc.) __Yes __Yes __Yes __Yes __Yes __Yes __No __No __No __No __No __No __Yes __Yes __Yes __Yes __Yes __Yes __No __No __No __No __No __No



Other comments?



Cargo Identification (possible uses: freight movement studies) Overall 1 2 3 motor carrier name 1 2 3 cargo type 1 2 3 origin/destination 1 2 3 other ________________________________ 1 2 3 other ________________________________ 1 2 3 o NOT INTERESTED IN THIS DATA CATEGORY



4 4 4 4 4 4



5 5 5 5 5 5



_____________ _____________ _____________ _____________ _____________



_____________ _____________ _____________ _____________ _____________



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________



Border Crossings (possible uses: freight movement studies, port efficiency studies) Overall 1 2 3 4 5 __Yes motor carrier name 1 2 3 4 5 __Yes time/date of trip 1 2 3 4 5 __Yes counts by vehicle type 1 2 3 4 5 __Yes cargo type 1 2 3 4 5 __Yes origin/destination 1 2 3 4 5 __Yes other ________________________________ 1 2 3 4 5 __Yes other ________________________________ 1 2 3 4 5 __Yes o NOT INTERESTED IN THIS DATA CATEGORY On-board Safety Data (possible uses: commercial vehicle operations safety studies) Overall 1 2 3 4 5 __Yes motor carrier name 1 2 3 4 5 __Yes vehicle type 1 2 3 4 5 __Yes cumulative mileage 1 2 3 4 5 __Yes driver log (hours of service) 1 2 3 4 5 __Yes subsystem status (e.g., brakes) 1 2 3 4 5 __Yes other ________________________________ 1 2 3 4 5 __Yes other ________________________________ 1 2 3 4 5 __Yes o NOT INTERESTED IN THIS DATA CATEGORY Weather Weather Data (possible uses: monitoring of flooding, monitoring of high winds) Overall 1 2 3 4 5 time of data collection 1 2 3 4 5 location of monitoring device 1 2 3 4 5 precipitation 1 2 3 4 5 temperature 1 2 3 4 5 wind conditions 1 2 3 4 5 o NOT INTERESTED IN THIS DATA CATEGORY



__No __No __No __No __No __No __No __No



__Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes



__No __No __No __No __No __No __No __No



_____________ _____________ _____________ _____________ _____________ _____________ _____________



_____________ _____________ _____________ _____________ _____________ _____________ _____________



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________



__No __No __No __No __No __No __No __No



__Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes



__No __No __No __No __No __No __No __No



_____________ _____________ _____________ _____________ _____________ _____________ _____________



_____________ _____________ _____________ _____________ _____________ _____________ _____________



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________



__Yes __Yes __Yes __Yes __Yes __Yes



__No __No __No __No __No __No



__Yes __Yes __Yes __Yes __Yes __Yes



__No __No __No __No __No __No



_____________ _____________ _____________ _____________ _____________



_____________ _____________ _____________ _____________ _____________



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________



Regional Archived ITS Data Server Page 7



Importance of data to your agency? Data Element

Not Needed Desirable Critical



1 OTHER DATA NOT LISTED ABOVE Data Category __________________________ data element ___________________________ data element ___________________________ data element ___________________________ data element ___________________________ data element ___________________________ data element ___________________________ Data Category __________________________ data element ___________________________ data element ___________________________ data element ___________________________ data element ___________________________ data element ___________________________ data element ___________________________ Data Category __________________________ data element ___________________________ data element ___________________________ data element ___________________________ data element ___________________________ data element ___________________________ data element ___________________________



2



3



4



5



Is data available Would you like to you from Desired time your data from other jurisdiction? jurisdictions? increments of data? Desired format? Yes/No Yes/No (e.g., 30 sec, 1 min, (e.g., ASCII, dbase, daily, etc.) spreadsheet, etc.) __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __No __No __No __No __No __No __No __No __No __No __No __No __No __No __No __No __No __No __No __No __No __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __Yes __No __No __No __No __No __No __No __No __No __No __No __No __No __No __No __No __No __No __No __No __No _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________ _____________



Other comments?



1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1



2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2



3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3



4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4



5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5



__________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________



Regional Archived ITS Data Server Page 8



APPENDIX C - Survey Questionnaire Reports



Kimley-Horn and Associates, Inc.



Page C



Scalable AZTechTM Data Server Enhancements for Planning and Operations: User Services Requirements Study



Data Importance by Data Category

Archived Data Server - Stakeholder Survey Results



DATA CATEGORY DATA Arterial Traffic Flow Surveillance Data

location of detection station Average Importance of location of detection station: 4.16 Number of responses for location of detection station: 25 occupancy Average Importance of occupancy: 3.84 Number of responses for occupancy: 25 speed Average Importance of speed: 4.15 Number of responses for speed: 27 vehicle headway Average Importance of vehicle headway: 4.00 Number of responses for vehicle headway: 1 volume Average Importance of volume: 4.13 Number of responses for volume: 32 Average Importance of Arterial Traffic Flow Surveillance Data: 4.07 Number of responses for Arterial Traffic Flow Surveillance Data: 110



Arterial Variable Message Sign

message Average Importance of message: 3.85 Number of responses for message: 13 name of message initiator Average Importance of name of message initiator: 3.45 Number of responses for name of message initiator: 11 sign identification number/location Average Importance of sign identification number/location: 3.83 Number of responses for sign identification number/location: 12 sign status Average Importance of sign status: 3.73 Number of responses for sign status: 11 time message was initiated Average Importance of time message was initiated: 3.58 Number of responses for time message was initiated: 12 Average Importance of Arterial Variable Message Sign: 3.69 Number of responses for Arterial Variable Message Sign: 59



Border Crossings

cargo type



Friday, September 10, 1999



Page 1 of 11



Archived Data Server - Stakeholder Survey Results



DATA CATEGORY



DATA

Average Importance of cargo type: 3.67 Number of responses for cargo type: 6 counts by vehicle type Average Importance of counts by vehicle type: 4.17 Number of responses for counts by vehicle type: 6 motor carrier name Average Importance of motor carrier name: 4.40 Number of responses for motor carrier name: 5 origin/destination Average Importance of origin/destination: 4.17 Number of responses for origin/destination: 6 time/date of trip Average Importance of time/date of trip: 4.17 Number of responses for time/date of trip: 6



Average Importance of Border Crossings: 4.10 Number of responses for Border Crossings: 29



Cargo Identification

cargo type Average Importance of cargo type: 3.33 Number of responses for cargo type: 6 motor carrier name Average Importance of motor carrier name: 3.20 Number of responses for motor carrier name: 5 origin/destination Average Importance of origin/destination: 3.50 Number of responses for origin/destination: 6 Average Importance of Cargo Identification: 3.35 Number of responses for Cargo Identification: 17



Construction and Work Zone Identification

construction/work zone location Average Importance of construction/work zone location: 4.24 Number of responses for construction/work zone location: 17 lanes/shoulders blocked Average Importance of lanes/shoulders blocked: 4.06 Number of responses for lanes/shoulders blocked: 17 time/date of construction Average Importance of time/date of construction: 4.18 Number of responses for time/date of construction: 17 Average Importance of Construction and Work Zone Identification: 4.16 Number of responses for Construction and Work Zone Identification: 51



Friday, September 10, 1999



Page 2 of 11



Archived Data Server - Stakeholder Survey Results



DATA CATEGORY DATA Emergency Vehicle Dispatch Records

arrival time Average Importance of arrival time: 4.00 Number of responses for arrival time: 6 clearance time Average Importance of clearance time: 4.00 Number of responses for clearance time: 6 departure time Average Importance of departure time: 4.00 Number of responses for departure time: 6 dispatch time Average Importance of dispatch time: 4.00 Number of responses for dispatch time: 6 origin/destination Average Importance of origin/destination: 4.00 Number of responses for origin/destination: 6 Average Importance of Emergency Vehicle Dispatch Records: 4.00 Number of responses for Emergency Vehicle Dispatch Records: 30



Emergency Vehicle Locations

location Average Importance of location: 3.83 Number of responses for location: 6 time of data collection Average Importance of time of data collection: 3.83 Number of responses for time of data collection: 6 vehicle identification number Average Importance of vehicle identification number: 3.83 Number of responses for vehicle identification number: 6 vehicle type Average Importance of vehicle type: 3.83 Number of responses for vehicle type: 6 Average Importance of Emergency Vehicle Locations: 3.83 Number of responses for Emergency Vehicle Locations: 24



Fleet Activity Reports

accidents Average Importance of accidents: 3.25 Number of responses for accidents: 8 citations Average Importance of citations: 3.00 Number of responses for citations: 6 inspection results

Friday, September 10, 1999 Page 3 of 11



Archived Data Server - Stakeholder Survey Results



DATA CATEGORY



DATA

Average Importance of inspection results: 2.83 Number of responses for inspection results: 6 motor carrier name Average Importance of motor carrier name: 3.43 Number of responses for motor carrier name: 7



Average Importance of Fleet Activity Reports: 3.15 Number of responses for Fleet Activity Reports: 27



Freeway Ramp Meters

HOV lane volume Average Importance of HOV lane volume: 4.08 Number of responses for HOV lane volume: 13 metering rate Average Importance of metering rate: 3.83 Number of responses for metering rate: 12 normal lane volume Average Importance of normal lane volume: 4.00 Number of responses for normal lane volume: 14 ramp identification number Average Importance of ramp identification number: 3.67 Number of responses for ramp identification number: 12 ramp metering begin time Average Importance of ramp metering begin time: 3.77 Number of responses for ramp metering begin time: 13 ramp metering end time Average Importance of ramp metering end time: 3.77 Number of responses for ramp metering end time: 13 ramp metering pre-emption time Average Importance of ramp metering pre-emption time: 3.83 Number of responses for ramp metering pre-emption time: 12 traffic control device preemptions Average Importance of traffic control device preemptions: 3.67 Number of responses for traffic control device preemptions: 9 Average Importance of Freeway Ramp Meters: 3.84 Number of responses for Freeway Ramp Meters: 98



Freeway Traffic Flow Surveillance Data

average occupancy Average Importance of average occupancy: 3.55 Number of responses for average occupancy: 20 average speed Average Importance of average speed: 3.62 Number of responses for average speed: 21



Friday, September 10, 1999



Page 4 of 11



Archived Data Server - Stakeholder Survey Results



DATA CATEGORY



DATA

average vehicles per hour Average Importance of average vehicles per hour: 3.92 Number of responses for average vehicles per hour: 24 detector identification number Average Importance of detector identification number: 3.61 Number of responses for detector identification number: 18 individual lane occupancy Average Importance of individual lane occupancy: 3.28 Number of responses for individual lane occupancy: 18 individual lane speed Average Importance of individual lane speed: 3.22 Number of responses for individual lane speed: 18 individual lane vehicles per hour Average Importance of individual lane vehicles per hour: 3.60 Number of responses for individual lane vehicles per hour: 20 vehicle classification Average Importance of vehicle classification: 3.60 Number of responses for vehicle classification: 20 vehicle weight Average Importance of vehicle weight: 2.63 Number of responses for vehicle weight: 19



Average Importance of Freeway Traffic Flow Surveillance Data: 3.47 Number of responses for Freeway Traffic Flow Surveillance Data: 178



Freeway Variable Message Sign

message Average Importance of message: 3.73 Number of responses for message: 11 name of message initiator Average Importance of name of message initiator: 3.22 Number of responses for name of message initiator: 9 sign identification number/location Average Importance of sign identification number/location: 3.55 Number of responses for sign identification number/location: 11 sign status Average Importance of sign status: 3.60 Number of responses for sign status: 10 time message was initiated Average Importance of time message was initiated: 3.40 Number of responses for time message was initiated: 10 Average Importance of Freeway Variable Message Sign: 3.51 Number of responses for Freeway Variable Message Sign: 51



Friday, September 10, 1999



Page 5 of 11



Archived Data Server - Stakeholder Survey Results



DATA CATEGORY DATA HazMat Cargo Identifiers

motor carrier name Average Importance of motor carrier name: 3.25 Number of responses for motor carrier name: 8 route Average Importance of route: 3.38 Number of responses for route: 8 time/date of trip Average Importance of time/date of trip: 3.38 Number of responses for time/date of trip: 8 type of hazmat Average Importance of type of hazmat: 3.13 Number of responses for type of hazmat: 8 Average Importance of HazMat Cargo Identifiers: 3.28 Number of responses for HazMat Cargo Identifiers: 32



Incident Logs

arrival time Average Importance of arrival time: 3.56 Number of responses for arrival time: 16 cause Average Importance of cause: 3.94 Number of responses for cause: 17 clearance time Average Importance of clearance time: 4.19 Number of responses for clearance time: 16 departure time Average Importance of departure time: 3.86 Number of responses for departure time: 14 dispatch time Average Importance of dispatch time: 3.57 Number of responses for dispatch time: 14 hazmat involved Average Importance of hazmat involved: 3.59 Number of responses for hazmat involved: 17 incident begin time Average Importance of incident begin time: 4.19 Number of responses for incident begin time: 16 incident location Average Importance of incident location: 4.25 Number of responses for incident location: 16 initiator



Friday, September 10, 1999



Page 6 of 11



Archived Data Server - Stakeholder Survey Results



DATA CATEGORY



DATA

Average Importance of initiator: 3.53 Number of responses for initiator: 15 lanes blocked Average Importance of lanes blocked: 3.83 Number of responses for lanes blocked: 18 police accident report reference Average Importance of police accident report reference: 3.69 Number of responses for police accident report reference: 16 responder Average Importance of responder: 3.67 Number of responses for responder: 15 severity level Average Importance of severity level: 4.16 Number of responses for severity level: 19 type of incident Average Importance of type of incident: 4.17 Number of responses for type of incident: 18



Average Importance of Incident Logs: 3.88 Number of responses for Incident Logs: 227



On-board Safety Data

cumulative mileage Average Importance of cumulative mileage: 3.20 Number of responses for cumulative mileage: 5 driver log (hours of service) Average Importance of driver log (hours of service): 3.20 Number of responses for driver log (hours of service): 5 motor carrier name Average Importance of motor carrier name: 3.20 Number of responses for motor carrier name: 5 subsystem status (e.g., brakes) Average Importance of subsystem status (e.g., brakes): 3.20 Number of responses for subsystem status (e.g., brakes): 5 vehicle type Average Importance of vehicle type: 3.20 Number of responses for vehicle type: 5 Average Importance of On-board Safety Data: 3.20 Number of responses for On-board Safety Data: 25



Parking Management

available spaces Average Importance of available spaces: 3.60 Number of responses for available spaces: 15



Friday, September 10, 1999



Page 7 of 11



Archived Data Server - Stakeholder Survey Results



DATA CATEGORY



DATA

lot location Average Importance of lot location: 3.65 Number of responses for lot location: 17 lot size Average Importance of lot size: 3.56 Number of responses for lot size: 16 time of data collection Average Importance of time of data collection: 3.40 Number of responses for time of data collection: 15



Average Importance of Parking Management: 3.56 Number of responses for Parking Management: 63



Traffic Signal Phasing

actuated settings Average Importance of actuated settings: 3.71 Number of responses for actuated settings: 14 clearance interval Average Importance of clearance interval: 3.71 Number of responses for clearance interval: 14 cycle length/green time Average Importance of cycle length/green time: 3.94 Number of responses for cycle length/green time: 16 delay settings Average Importance of delay settings: 3.57 Number of responses for delay settings: 14 left turn treatment Average Importance of left turn treatment: 3.75 Number of responses for left turn treatment: 16 minimum pedestrian green Average Importance of minimum pedestrian green: 3.62 Number of responses for minimum pedestrian green: 13 number of phases Average Importance of number of phases: 3.88 Number of responses for number of phases: 16 pre-timed settings Average Importance of pre-timed settings: 3.70 Number of responses for pre-timed settings: 10 signal coordination settings Average Importance of signal coordination settings: 3.71 Number of responses for signal coordination settings: 14 signal location Average Importance of signal location: 4.24 Number of responses for signal location: 17

Friday, September 10, 1999 Page 8 of 11



Archived Data Server - Stakeholder Survey Results



DATA CATEGORY



DATA

signal pre-emption settings Average Importance of signal pre-emption settings: 3.53 Number of responses for signal pre-emption settings: 15



Average Importance of Traffic Signal Phasing: 3.77 Number of responses for Traffic Signal Phasing: 159



Train Arrivals at Highway Rail Intersections

begin time Average Importance of begin time: 3.55 Number of responses for begin time: 11 end time Average Importance of end time: 3.55 Number of responses for end time: 11 intersection location Average Importance of intersection location: 3.67 Number of responses for intersection location: 12 Average Importance of Train Arrivals at Highway Rail Intersections: 3.59 Number of responses for Train Arrivals at Highway Rail Intersections: 34



Transit Route Deviations

bus identification number Average Importance of bus identification number: 3.50 Number of responses for bus identification number: 10 location Average Importance of location: 3.50 Number of responses for location: 12 route number Average Importance of route number: 3.55 Number of responses for route number: 11 time of data collection Average Importance of time of data collection: 3.36 Number of responses for time of data collection: 11 Average Importance of Transit Route Deviations: 3.48 Number of responses for Transit Route Deviations: 44



Transit Schedule Adherence

actual arrival time at station Average Importance of actual arrival time at station: 4.15 Number of responses for actual arrival time at station: 13 bus identification number Average Importance of bus identification number: 4.00 Number of responses for bus identification number: 11 bus stop id number



Friday, September 10, 1999



Page 9 of 11



Archived Data Server - Stakeholder Survey Results



DATA CATEGORY



DATA

Average Importance of bus stop id number: 4.17 Number of responses for bus stop id number: 12 scheduled arrival time at station Average Importance of scheduled arrival time at station: 4.15 Number of responses for scheduled arrival time at station: 13 transit route Average Importance of transit route: 4.21 Number of responses for transit route: 14



Average Importance of Transit Schedule Adherence: 4.14 Number of responses for Transit Schedule Adherence: 63



Transit Usage

bus identification number Average Importance of bus identification number: 3.75 Number of responses for bus identification number: 16 origin and destination numbers Average Importance of origin and destination numbers: 3.86 Number of responses for origin and destination numbers: 21 route number Average Importance of route number: 4.00 Number of responses for route number: 21 vehicle boardings Average Importance of vehicle boardings: 4.10 Number of responses for vehicle boardings: 20 Average Importance of Transit Usage: 3.94 Number of responses for Transit Usage: 78



Weather Data

location of monitoring device Average Importance of location of monitoring device: 3.50 Number of responses for location of monitoring device: 14 precipitation Average Importance of precipitation: 3.50 Number of responses for precipitation: 14 temperature Average Importance of temperature: 3.50 Number of responses for temperature: 14 time of data collection Average Importance of time of data collection: 3.31 Number of responses for time of data collection: 13 wind conditions Average Importance of wind conditions: 3.50 Number of responses for wind conditions: 14



Friday, September 10, 1999



Page 10 of 11



Archived Data Server - Stakeholder Survey Results



DATA CATEGORY



DATA



Average Importance of Weather Data: 3.46 Number of responses for Weather Data: 69



Weigh-in-Motion (WIM) Data

date of count Average Importance of date of count: 4.10 Number of responses for date of count: 10 vehicle classification (by axle) Average Importance of vehicle classification (by axle): 4.00 Number of responses for vehicle classification (by axle): 10 vehicle weights Average Importance of vehicle weights: 4.00 Number of responses for vehicle weights: 11 WIM location Average Importance of WIM location: 4.09 Number of responses for WIM location: 11 Average Importance of Weigh-in-Motion (WIM) Data: 4.05 Number of responses for Weigh-in-Motion (WIM) Data: 42



Friday, September 10, 1999



Page 11 of 11



Data Availability By Data Category

Archived Data Server - Stakeholder Survey Results



CATEGORY



DATA

location of detection station



AVAIL. FROM STAKEHOLDER'S JURISDICTION



DESIRED FROM OTHER JURISDICTIONS



Arterial Traffic Flow Surveillance Data

12 18 16 18 1 20 73



occupancy

10



speed

10



vehicle headway

1



volume

21 TOTAL FOR Arterial Traffic Flow Surveillance Data: 54



Arterial Variable Message Sign

message

1 6 5 6 5 5 27



name of message initiator

1



sign identification number/location

1



sign status

1



time message was initiated

1 TOTAL FOR Arterial Variable Message Sign: 5



Border Crossings

cargo type

2 4 5 4 5 4 22



counts by vehicle type

2



motor carrier name

2



origin/destination

2



time/date of trip

2 TOTAL FOR Border Crossings: 10



Cargo Identification

Friday, September 10, 1999 Page 1 of 8



Archived Data Server - Stakeholder Survey Results



CATEGORY



DATA

cargo type



AVAIL. FROM STAKEHOLDER'S JURISDICTION



DESIRED FROM OTHER JURISDICTIONS



1



3 3 3 9



motor carrier name

1



origin/destination

1 TOTAL FOR Cargo Identification: 3



Construction and Work Zone Identification

construction/work zone location

7 8 8 8 24



lanes/shoulders blocked

6



time/date of construction

7 TOTAL FOR Construction and Work Zone Identification: 20



Emergency Vehicle Dispatch Records

arrival time

2 4 4 4 4 3 19



clearance time

2



departure time

2



dispatch time

2



origin/destination

1 TOTAL FOR Emergency Vehicle Dispatch Records: 9



Emergency Vehicle Locations

location

2 3 3 3 3 12



time of data collection

2



vehicle identification number

2



vehicle type

2 TOTAL FOR Emergency Vehicle Locations: 8



Fleet Activity Reports

accidents

1 Friday, September 10, 1999 5 Page 2 of 8



Archived Data Server - Stakeholder Survey Results



CATEGORY



DATA

citations



AVAIL. FROM STAKEHOLDER'S JURISDICTION



DESIRED FROM OTHER JURISDICTIONS



4



inspection results

1 4 4 17



motor carrier name

1 TOTAL FOR Fleet Activity Reports: 3



Freeway Ramp Meters

HOV lane volume

2 8 8 9 8 9 9 8 6 65



metering rate

2



normal lane volume

3



ramp identification number

2



ramp metering begin time

3



ramp metering end time

3



ramp metering pre-emption time

2



traffic control device preemptions

2 TOTAL FOR Freeway Ramp Meters: 19



Freeway Traffic Flow Surveillance Data

average occupancy

7 13 14 17 11 9 9 10



average speed

8



average vehicles per hour

10



detector identification number

3



individual lane occupancy

3



individual lane speed

3



individual lane vehicles per hour

4



vehicle classification



Friday, September 10, 1999



Page 3 of 8



Archived Data Server - Stakeholder Survey Results



CATEGORY



DATA

vehicle weight



AVAIL. FROM STAKEHOLDER'S JURISDICTION



DESIRED FROM OTHER JURISDICTIONS



6 4 TOTAL FOR Freeway Traffic Flow Surveillance Data: 48



10 7 100



Freeway Variable Message Sign

message

4 8 7 8 6 8 37



name of message initiator

3



sign identification number/location

4



sign status

4



time message was initiated

4 TOTAL FOR Freeway Variable Message Sign: 19



HazMat Cargo Identifiers

motor carrier name

1 5 5 5 5 20



route

1



time/date of trip

1



type of hazmat

1 TOTAL FOR HazMat Cargo Identifiers: 4



Incident Logs

arrival time

3 6 9 6 5 5 8 8 Page 4 of 8



cause

5



clearance time

4



departure time

3



dispatch time

3



hazmat involved

5



incident begin time

6 Friday, September 10, 1999



Archived Data Server - Stakeholder Survey Results



CATEGORY



DATA

incident location



AVAIL. FROM STAKEHOLDER'S JURISDICTION



DESIRED FROM OTHER JURISDICTIONS



6



8 7 10 7 7 9 8 103



initiator

4



lanes blocked

4



police accident report reference

4



responder

6



severity level

5



type of incident

5 TOTAL FOR Incident Logs: 63



On-board Safety Data

cumulative mileage

2



driver log (hours of service)

3



motor carrier name

3



subsystem status (e.g., brakes)

3



vehicle type

3 TOTAL FOR On-board Safety Data: 14



Parking Management

available spaces

2 6 7 7 7 TOTAL FOR Parking Management: 6 27



lot location

2



lot size

2



time of data collection



Traffic Signal Phasing

actuated settings

5 6



Friday, September 10, 1999



Page 5 of 8



Archived Data Server - Stakeholder Survey Results



CATEGORY



DATA

clearance interval



AVAIL. FROM STAKEHOLDER'S JURISDICTION



DESIRED FROM OTHER JURISDICTIONS



6



6 8 7 7 6 8 5 7 8 7 75



cycle length/green time

7



delay settings

6



left turn treatment

7



minimum pedestrian green

6



number of phases

8



pre-timed settings

6



signal coordination settings

7



signal location

8



signal pre-emption settings

6 TOTAL FOR Traffic Signal Phasing: 72



Train Arrivals at Highway Rail Intersections

begin time

1 6 6 7 19



end time

1



intersection location

1 TOTAL FOR Train Arrivals at Highway Rail Intersections: 3



Transit Route Deviations

bus identification number

4 6 7 6 6 25



location

4



route number

5



time of data collection

2 TOTAL FOR Transit Route Deviations: 15



Transit Schedule Adherence

Friday, September 10, 1999 Page 6 of 8



Archived Data Server - Stakeholder Survey Results



CATEGORY



DATA

actual arrival time at station



AVAIL. FROM STAKEHOLDER'S JURISDICTION



DESIRED FROM OTHER JURISDICTIONS



4



6 6 6 6 7 31



bus identification number

4



bus stop id number

4



scheduled arrival time at station

5



transit route

5 TOTAL FOR Transit Schedule Adherence: 22



Transit Usage

bus identification number

8 10 14 13 12 49



origin and destination numbers

6



route number

8



vehicle boardings

6 TOTAL FOR Transit Usage: 28



Weather Data

location of monitoring device

4 4 4 4 5 4 21



precipitation

3



temperature

4



time of data collection

4



wind conditions

4 TOTAL FOR Weather Data: 19



Weigh-in-Motion (WIM) Data

date of count

4 7 7 7



vehicle classification (by axle)

4



vehicle weights

4



Friday, September 10, 1999



Page 7 of 8



Archived Data Server - Stakeholder Survey Results



CATEGORY



DATA

WIM location



AVAIL. FROM STAKEHOLDER'S JURISDICTION



DESIRED FROM OTHER JURISDICTIONS



5 TOTAL FOR Weigh-in-Motion (WIM) Data: 17



6 27



Grand Total



447



816



Friday, September 10, 1999



Page 8 of 8



DATA STORAGE TIME INCREMENT VOTES - SUMMARY

CATEGORY DATA 30SEC 1MIN 3MIN 5MIN 10MIN 15MIN 20MIN 30MIN 1HR 1DAY 1YR 1WK 1MO 6MO PKHR WKEND



Arterial Traffic Flow Surveillance Data

density

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



location of detection station

0 1 0 2 0 1 0 1 0 2 1 0 0 1 0 0



occupancy

0 2 0 2 0 2 0 2 0 2 0 0 0 0 1 0



speed

0 2 0 2 0 1 0 3 0 0 0 0 0 0 0 0



Traffic control device preemptions

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



Traffic control device queue detection

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



vehicle classification

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



vehicle headway

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



volume

0 1 0 2 0 3 0 2 1 3 1 0 0 0 0 0



TOTAL FOR: Arterial Traffic Flow Surveillance Data 0 6



0



8



0



7



0



8



1



7



2



0



0



1



1



0



Arterial Variable Message Sign

message

0 0 0 1 0 0 0 1 0 1 0 0 0 0 0 0



name of message initiator

0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0



sign identification number/location

0 0 0 1 0 0 0 0 0 0 0 0 0 1 0 0



sign status

0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0



time message was initiated

0 TOTAL FOR: Arterial Variable Message Sign 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0



0



0



5



0



0



0



1



0



4



0



0



0



1



0



0



Border Crossings

Friday, September 10, 1999 Page 1 of 9



CATEGORY



DATA



30SEC



1MIN



3MIN



5MIN 10MIN 15MIN 20MIN 30MIN



1HR



1DAY



1YR



1WK



1MO



6MO



PKHR WKEND



cargo type

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



counts by vehicle type

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



motor carrier name

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



origin/destination

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



time/date of trip

0 TOTAL FOR: Border Crossings 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



Cargo Identification

cargo type

0 0 0 0 0 0 0 0 0 1 0 0 1 0 0 0



motor carrier name

0 0 0 0 0 0 0 0 0 1 0 0 1 0 0 0



origin/destination

0 TOTAL FOR: Cargo Identification 0 0 0 0 0 0 0 0 0 3 0 0 3 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1 0 0 0



Construction and Work Zone Identification

construction/work zone location

0 0 0 0 1 0 0 0 2 3 0 0 0 0 0 0



lanes/shoulders blocked

0 0 0 0 1 0 0 0 0 2 0 0 0 0 0 0



time/date of construction

0 0 0 0 1 0 0 0 0 2 0 0 0 0 0 0



TOTAL FOR: Construction and Work Zone Identification 0 0 0



0



3



0



0



0



2



7



0



0



0



0



0



0



Emergency Vehicle Dispatch Records

arrival time

0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0



clearance time

0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0



departure time

0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0



dispatch time

Friday, September 10, 1999 Page 2 of 9



CATEGORY



DATA



30SEC



1MIN



3MIN



5MIN 10MIN 15MIN 20MIN 30MIN



1HR



1DAY



1YR



1WK



1MO



6MO



PKHR WKEND



0



0



0



2



0



0



0



0



0



0



0



0



0



0



0



0



origin/destination

0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0



route

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



TOTAL FOR: Emergency Vehicle Dispatch Records 0 0



0



6



0



0



0



0



0



0



0



0



0



0



0



0



Emergency Vehicle Locations

location

0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0



time of data collection

0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0



vehicle identification number

0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0



vehicle type

0 TOTAL FOR: Emergency Vehicle Locations 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0



0



0



5



0



0



0



0



0



0



0



0



0



0



0



0



Fleet Activity Reports

accidents

0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0



citations

0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0



inspection results

0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0



motor carrier name

0 TOTAL FOR: Fleet Activity Reports 0 0 0 0 0 0 0 0 4 1 1 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 0 0 0 0



Freeway Ramp Meters

HOV lane volume

0 1 0 0 0 1 0 1 0 0 0 1 0 0 0 0



metering rate

0 0 0 0 0 1 0 1 1 1 0 1 0 0 0 0



normal lane volume

0 1 0 0 0 1 0 1 1 0 0 1 0 0 0 0



ramp identification number



Friday, September 10, 1999



Page 3 of 9



CATEGORY



DATA



30SEC



1MIN



3MIN



5MIN 10MIN 15MIN 20MIN 30MIN



1HR



1DAY



1YR



1WK



1MO



6MO



PKHR WKEND



0



1



0



1



0



1



0



0



0



0



0



1



0



1



0



0



ramp metering begin time

0 1 0 0 0 1 0 1 0 1 0 1 0 0 0 0



ramp metering end time

0 1 0 0 0 1 0 1 0 1 0 1 0 0 0 0



ramp metering pre-emption time

0 2 0 0 0 1 0 1 0 0 0 1 0 0 0 0



traffic control device preemptions

0 TOTAL FOR: Freeway Ramp Meters 0 8 0 1 0 8 0 6 2 3 0 8 0 1 0 0 1 0 0 0 1 0 0 0 0 0 1 0 0 0 0



Freeway Traffic Flow Surveillance Data

average occupancy

0 1 0 1 0 2 0 1 0 1 0 0 0 0 1 0



average speed

0 1 0 1 0 2 0 1 0 1 0 0 0 0 1 0



average vehicles per hour

0 0 0 1 1 4 0 2 1 4 0 0 0 0 1 0



detector identification number

0 1 0 1 0 2 0 2 0 1 0 0 0 0 1 0



individual lane occupancy

0 1 0 1 0 2 0 1 0 1 0 0 0 0 0 0



individual lane speed

0 1 0 1 0 1 0 1 0 0 0 0 0 0 0 0



individual lane vehicles per hour

0 0 0 1 1 2 0 2 0 1 0 0 0 0 0 0



vehicle classification

0 0 0 2 0 1 0 1 0 2 0 0 0 0 0 0



vehicle weight

0 0 0 2 0 1 0 1 0 1 0 0 0 0 0 0



TOTAL FOR: Freeway Traffic Flow Surveillance Data 0 5



0



11



2



17



0



12



1



12



0



0



0



0



4



0



Freeway Variable Message Sign

message

0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0



name of message initiator

0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0



sign identification number/location

Friday, September 10, 1999 Page 4 of 9



CATEGORY



DATA



30SEC



1MIN



3MIN



5MIN 10MIN 15MIN 20MIN 30MIN



1HR



1DAY



1YR



1WK



1MO



6MO



PKHR WKEND



0



0



0



1



0



0



0



0



0



0



0



0



0



1



0



0



sign status

0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0



time message was initiated

0 TOTAL FOR: Freeway Variable Message Sign 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0



2



0



3



0



0



0



0



0



4



0



0



0



1



0



0



HazMat Cargo Identifiers

motor carrier name

0 0 0 0 0 0 0 1 0 1 1 0 1 0 0 0



route

0 0 0 0 0 0 0 1 0 1 0 0 0 0 0 0



time/date of trip

0 0 0 0 0 0 0 1 0 1 0 0 0 0 0 0



type of hazmat

0 TOTAL FOR: HazMat Cargo Identifiers 0 0 0 0 0 0 0 4 0 4 1 0 1 0 0 0 0 0 0 0 0 0 1 0 1 0 0 0 0 0 0



Incident Logs

arrival time

0 0 0 2 1 0 0 0 0 1 0 0 1 0 0 0



cause

0 0 0 1 1 0 0 0 0 1 0 0 1 0 0 0



clearance time

0 0 0 1 1 0 0 0 0 1 0 1 0 0 0 0



departure time

0 0 0 1 1 0 0 0 0 1 0 0 0 0 0 0



dispatch time

0 0 0 1 1 0 0 0 0 1 0 0 0 0 0 0



hazmat involved

0 0 0 1 1 0 0 0 0 1 0 1 0 0 0 0



incident begin time

0 0 0 1 1 0 0 0 0 1 0 0 0 0 0 0



incident location

0 0 0 1 1 0 0 0 0 1 0 0 0 0 0 0



initiator

0 0 0 1 1 0 0 0 0 1 0 0 0 0 0 0



lanes blocked

Friday, September 10, 1999 Page 5 of 9



CATEGORY



DATA



30SEC



1MIN



3MIN



5MIN 10MIN 15MIN 20MIN 30MIN



1HR



1DAY



1YR



1WK



1MO



6MO



PKHR WKEND



0



0



0



1



1



0



0



0



0



1



0



0



1



0



0



0



police accident report reference

0 0 0 1 1 0 0 0 0 1 0 0 0 0 0 0



responder

0 0 0 1 1 0 0 0 0 1 0 0 0 0 0 0



severity level

0 0 0 1 1 0 0 0 0 1 0 1 1 0 0 0



type of incident

0 TOTAL FOR: Incident Logs 0 0 0 15 14 0 0 0 0 14 0 4 6 0 0 0 0 0 1 1 0 0 0 0 1 0 1 2 0 0 0



On-board Safety Data

cumulative mileage

0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0



driver log (hours of service)

0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0



motor carrier name

0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0



subsystem status (e.g., brakes)

0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0



vehicle type

0 TOTAL FOR: On-board Safety Data 0 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0



Parking Management

available spaces

0 0 0 0 2 0 0 0 1 1 0 0 0 0 2 1



lot location

0 0 0 0 2 0 0 0 1 0 1 0 1 0 0 0



lot size

0 0 0 0 2 0 0 0 0 0 1 0 0 0 0 0



time of data collection

0 TOTAL FOR: Parking Management 0 0 0 0 8 0 0 0 3 1 2 0 1 0 2 1 0 0 0 2 0 0 0 1 0 0 0 0 0 0 0



Traffic Signal Phasing

actuated settings



Friday, September 10, 1999



Page 6 of 9



CATEGORY



DATA



30SEC



1MIN



3MIN



5MIN 10MIN 15MIN 20MIN 30MIN



1HR



1DAY



1YR



1WK



1MO



6MO



PKHR WKEND



0



0



0



0



0



0



0



1



1



0



0



0



0



0



0



0



clearance interval

0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0



cycle length/green time

0 0 0 0 0 1 0 1 0 1 0 0 0 0 0 0



delay settings

0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0



left turn treatment

0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0



minimum pedestrian green

0 1 0 0 0 0 0 1 0 0 0 0 0 0 0 0



number of phases

0 0 0 0 0 1 0 1 0 1 0 0 0 0 0 0



pre-timed settings

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



signal coordination settings

0 0 0 0 0 1 0 1 1 0 0 0 0 0 0 0



signal location

0 0 0 1 0 1 0 0 0 0 0 0 0 1 0 0



signal pre-emption settings

0 TOTAL FOR: Traffic Signal Phasing 0 1 0 1 0 4 0 9 6 2 0 0 0 1 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0



Train Arrivals at Highway Rail Intersections

begin time

0 0 1 1 0 0 0 0 1 0 0 0 0 0 0 0



end time

0 0 1 1 0 0 0 0 1 0 0 0 0 0 0 0



intersection location

0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 0



TOTAL FOR: Train Arrivals at Highway Rail Intersections 0 0 2



3



0



0



0



0



3



0



0



0



0



0



0



0



Transit Route Deviations

bus identification number

0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0



location

1 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0



route number

Friday, September 10, 1999 Page 7 of 9



CATEGORY



DATA



30SEC



1MIN



3MIN



5MIN 10MIN 15MIN 20MIN 30MIN



1HR



1DAY



1YR



1WK



1MO



6MO



PKHR WKEND



0



0



1



0



0



0



0



0



0



0



0



0



0



0



0



0



time of data collection

0 TOTAL FOR: Transit Route Deviations 1 0 4 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0



Transit Schedule Adherence

actual arrival time at station

0 1 1 1 0 0 0 0 0 1 0 0 0 0 1 1



bus identification number

0 0 1 2 0 0 0 0 0 0 0 0 0 0 0 0



bus stop id number

0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0



scheduled arrival time at station

0 0 1 1 0 0 0 0 0 1 0 0 0 0 0 0



transit route

0 TOTAL FOR: Transit Schedule Adherence 0 1 5 6 0 0 0 0 0 3 0 0 0 0 1 1 0 1 1 0 0 0 0 0 1 0 0 0 0 0 0



Transit Usage

bus identification number

0 0 1 1 0 1 1 0 0 0 0 0 0 0 0 0



origin and destination numbers

0 0 1 0 0 0 1 0 0 3 0 0 0 0 1 1



route number

0 0 1 0 0 1 1 0 0 1 0 0 0 0 0 0



vehicle boardings

0 TOTAL FOR: Transit Usage 0 0 4 1 0 3 4 0 0 6 0 0 0 0 1 1 0 1 0 0 1 1 0 0 2 0 0 0 0 0 0



Weather Data

location of monitoring device

0 0 0 0 1 0 0 0 1 1 0 0 0 0 0 0



precipitation

0 0 0 0 1 0 0 1 0 1 0 0 0 0 0 0



temperature

0 0 0 0 1 0 0 1 0 1 0 0 0 0 0 0



time of data collection



Friday, September 10, 1999



Page 8 of 9



CATEGORY



DATA



30SEC



1MIN



3MIN



5MIN 10MIN 15MIN 20MIN 30MIN



1HR



1DAY



1YR



1WK



1MO



6MO



PKHR WKEND



0



0



0



0



1



0



0



1



0



1



0



0



0



0



0



0



wind conditions

0 TOTAL FOR: Weather Data 0 0 0 0 5 0 0 4 1 5 0 0 0 0 0 0 0 0 0 1 0 0 1 0 1 0 0 0 0 0 0



Weigh-in-Motion (WIM) Data

date of count

0 0 0 0 0 0 0 0 1 0 0 0 1 0 0 0



vehicle classification (by axle)

0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0



vehicle weights

0 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0



WIM location

0 TOTAL FOR: Weigh-in-Motion (WIM) Data 0 0 0 0 2 0 0 0 1 2 0 0 1 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0



Friday, September 10, 1999



Page 9 of 9



DESIRED DATA STORAGE FORMAT BY CATEGORY

CATEGORY DATA MS ACCESS ASCII OTHER DBMS SPREADSHEET GIS-ENABLED UTDF2



Arterial Traffic Flow Surveillance Data

density

0 0 3 2 2 0 0 0 0 3 10 0 2 1 1 0 0 0 0 3 7 0 1 1 1 0 0 0 0 2 5 0 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 1 4



location of detection station

0



occupancy

0



speed

0



Traffic control device preemptions

0 0



Traffic control device queue detection vehicle classification

0



vehicle headway

0



volume

0 TOTAL FOR DATA CATEGORY: 0



Arterial Variable Message Sign

message

0 1 1 1 1 1 5 1 1 3 1 1 7 1 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0



name of message initiator

0



sign identification number/location

0



sign status

0



time message was initiated

0 TOTAL FOR DATA CATEGORY: 0



Border Crossings

cargo type

0 0 0 0 0 1 1 0 0 0 0



counts by vehicle type

0



Friday, September 10, 1999



Page 1 of 8



CATEGORY



DATA

motor carrier name



MS ACCESS



ASCII OTHER DBMS



SPREADSHEET



GIS-ENABLED



UTDF2



0



0 0 0 0



0 0 0 0



1 1 1 5



0 0 0 0



0 0 0 0



origin/destination

0



time/date of trip

0 TOTAL FOR DATA CATEGORY: 0



Cargo Identification

cargo type

0 2 2 2 6 0 0 0 0 1 1 1 3 0 0 0 0 0 0 0 0



motor carrier name

0



origin/destination

0 TOTAL FOR DATA CATEGORY: 0



Construction and Work Zone Identification

construction/work zone location

0 1 1 1 3 2 1 1 4 1 1 1 3 0 0 0 0 0 0 0 0



lanes/shoulders blocked

0



time/date of construction

0 TOTAL FOR DATA CATEGORY: 0



Emergency Vehicle Dispatch Records

arrival time

0 0 0 0 0 0 0 0 0 0 0 1 0 0 1 1 1 1 1 1 0 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0



clearance time

0



departure time

0



dispatch time

0



origin/destination

0



route

0 TOTAL FOR DATA CATEGORY: 0



Emergency Vehicle Locations

location

Friday, September 10, 1999 Page 2 of 8



CATEGORY



DATA

time of data collection



MS ACCESS

0 0



ASCII OTHER DBMS

0 0 0 0 0 0 1 0 0 1



SPREADSHEET

1 1 1 1 4



GIS-ENABLED

0 0 0 0 0



UTDF2

0 0 0 0 0



vehicle identification number

0



vehicle type

0 TOTAL FOR DATA CATEGORY: 0



Fleet Activity Reports

accidents

0 0 0 0 1 1 1 0 0 0 1 2 2 2 2 8 1 0 0 0 1 0 0 0 0 0



citations

0



inspection results

0



motor carrier name

0 TOTAL FOR DATA CATEGORY: 0



Freeway Ramp Meters

HOV lane volume

0 2 3 3 4 3 3 3 2 23 2 2 2 2 2 2 2 1 15 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



metering rate

0



normal lane volume

0



ramp identification number

0



ramp metering begin time

0



ramp metering end time

0



ramp metering pre-emption time

0



traffic control device preemptions

0 TOTAL FOR DATA CATEGORY: 0



Freeway Traffic Flow Surveillance Data

average occupancy

0 4 4 2 0 0



average speed

Friday, September 10, 1999 Page 3 of 8



CATEGORY



DATA



MS ACCESS

0



ASCII OTHER DBMS

4 5 5 3 3 4 3 3 34 4 5 4 2 2 3 3 2 29



SPREADSHEET

2 3 2 1 1 2 2 1 16



GIS-ENABLED

0 0 0 0 0 0 0 0 0



UTDF2

0 0 0 0 0 0 0 0 0



average vehicles per hour

0



detector identification number

0



individual lane occupancy

0



individual lane speed

0



individual lane vehicles per hour

0



vehicle classification

0



vehicle weight

0 TOTAL FOR DATA CATEGORY: 0



Freeway Variable Message Sign

message

0 1 1 1 1 1 5 1 1 2 1 1 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



name of message initiator

0



sign identification number/location

0



sign status

0



time message was initiated

0 TOTAL FOR DATA CATEGORY: 0



HazMat Cargo Identifiers

motor carrier name

0 0 0 0 0 0 0 0 0 0 0 2 2 2 2 8 0 0 0 0 0 0 0 0 0 0



route

0



time/date of trip

0



type of hazmat

0 TOTAL FOR DATA CATEGORY: 0



Incident Logs

arrival time

Friday, September 10, 1999 Page 4 of 8



CATEGORY



DATA

cause



MS ACCESS

0 0



ASCII OTHER DBMS

1 1 1 1 1 1 1 2 1 1 1 1 1 1 15 3 2 1 1 1 1 1 1 1 2 1 1 2 2 20



SPREADSHEET

3 3 2 2 2 2 2 2 2 3 2 2 3 3 33



GIS-ENABLED

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



UTDF2

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



clearance time

0



departure time

0



dispatch time

0



hazmat involved

0



incident begin time

0



incident location

0



initiator

0



lanes blocked

0



police accident report reference

0



responder

0



severity level

0



type of incident

0 TOTAL FOR DATA CATEGORY: 0



On-board Safety Data

cumulative mileage

0 0 0 0 0 0 0 0 0 0 0 0 0 2 2 2 2 2 10 0 0 0 0 0 0 0 0 0 0 0 0



driver log (hours of service)

0



motor carrier name

0



subsystem status (e.g., brakes)

0



vehicle type

0 TOTAL FOR DATA CATEGORY: 0



Parking Management

Friday, September 10, 1999 Page 5 of 8



CATEGORY



DATA

available spaces



MS ACCESS



ASCII OTHER DBMS



SPREADSHEET



GIS-ENABLED



UTDF2



0



1 1 1 1 4



2 1 1 1 5



0 0 0 0 0



0 0 0 0 0



0 0 0 0 0



lot location

0



lot size

0



time of data collection

0 TOTAL FOR DATA CATEGORY: 0



Traffic Signal Phasing

actuated settings

0 1 1 1 1 1 1 1 0 1 1 1 10 1 1 1 1 1 1 1 0 1 2 1 11 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 0 1 1 0 4



clearance interval

0



cycle length/green time

0



delay settings

0



left turn treatment

0



minimum pedestrian green

0



number of phases

0



pre-timed settings

0



signal coordination settings

0



signal location

0



signal pre-emption settings

0 TOTAL FOR DATA CATEGORY: 0



Train Arrivals at Highway Rail Intersections

begin time

0 2 2 2 1 1 1 2 1 1 0 0 0 0 0 0



end time

0



intersection location

0



Friday, September 10, 1999



Page 6 of 8



CATEGORY



DATA

TOTAL FOR DATA CATEGORY:



MS ACCESS

0



ASCII OTHER DBMS

6 3



SPREADSHEET

4



GIS-ENABLED

0



UTDF2

0



Transit Route Deviations

bus identification number

0 1 1 1 1 4 2 2 2 3 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



location

1



route number

0



time of data collection

0 TOTAL FOR DATA CATEGORY: 1



Transit Schedule Adherence

actual arrival time at station

0 2 2 2 2 2 10 2 3 2 2 2 11 2 1 1 1 1 6 0 0 0 0 0 0 0 0 0 0 0 0



bus identification number

0



bus stop id number

0



scheduled arrival time at station

0



transit route

0 TOTAL FOR DATA CATEGORY: 0



Transit Usage

bus identification number

0 3 3 3 2 11 4 5 4 4 17 1 2 2 2 7 0 1 0 0 1 0 0 0 0 0



origin and destination numbers

0



route number

0



vehicle boardings

0 TOTAL FOR DATA CATEGORY: 0



Weather Data

location of monitoring device

0 1 1 1 0 0 0 0 0 0 0



precipitation

0



temperature

Friday, September 10, 1999 Page 7 of 8



CATEGORY



DATA

time of data collection



MS ACCESS

0 0



ASCII OTHER DBMS

1 1 1 5 0 0 0 1



SPREADSHEET

0 0 0 0



GIS-ENABLED

0 0 0 0



UTDF2

0 0 0 0



wind conditions

0 TOTAL FOR DATA CATEGORY: 0



Weigh-in-Motion (WIM) Data

date of count

0 1 1 2 2 6 158 0 0 0 0 0 148 2 1 1 1 5 123 0 0 0 0 0 2 0 0 0 0 0 8



vehicle classification (by axle)

0



vehicle weights

0



WIM location

0 TOTAL FOR DATA CATEGORY: Grand Total 0 1



Friday, September 10, 1999



Page 8 of 8