Hillsborough Metropolitan Planning Organization Pilot of the Data Business Plan for State and Local Departments of Transportation: Data Business Plan

1. The MPO needs data to support calculation of Florida DOT performance measures, such as travel time reliability and return on investment for projects.

2. The MPO wants to incorporate national datasets into its Multimodal Transportation Database, such as the National Performance Management Research Data Set (NPMRDS) / HERE (formerly Navteq) data, as well as connected vehicle data to enhance transportation analysis for the region.

3. Need additional travel data, mainly turning movement counts at intersections on a continuous basis.

4. Need to obtain travel time data on more facilities. Specifically SR 60, which was discontinued. It is a main beach access arterial.

5. More origin and destination data would be useful for planning purposes.

6. Pedestrian and bicycle activity data is the most needed.

1. Need to make better use of expanding data sources for performance management.

1. There is a need to assess how data could come from connected vehicles through a Data Business Plan (DBP) environment to support planning in general.

2. Intensive work to set out machine counters, not to mention exposure to traffic, which can be unsafe.

3. There is always room for improvement in data quality/data collection standards for travel time/ speed.

1. If Bluetooth or GPS probe data isn't based on a good sample size, results can be skewed.

2. Knowing whether data collected is continuous or a one-time collection is very important.

3. Travel time and speed data is obtained based on site-specific needs through our GEC. There are no systematic ways for data gathering.

4. Managing and analyzing this data is time intensive. We are currently doing it with the same staffing level as before.

1. Ideally, the MPO would like to attach travel time data to roadway segments in Multimodal Transportation Database. They would like the ability to conduct analysis such as determining the average travel time and standard deviation during the PM peak on a typical weekday, or determining whether there is a correlation between travel time on arterials and fatality rates.

1. Currently, data is not integrated across the region, which limits the MPO's ability to conduct analysis to support performance based planning.

1. The MPO is interested in integrating other datasets (planning for operations, connected vehicle data) into its Multimodal Transportation Database. However, data integration is a challenge and will require improving the structure of the database.

2. It is an interagency mission to incorporate travel time and speed data into the MPO databases and make it available to planning partners.

1. Private vendors are willing to install a device in signal cabinets to gather roadway performance measures. These measures are available to the municipality, but the company may also sell that information to Original Equipment Manufacturers.

2. Data availability is not publicly advertised, so access is limited.

3. Data sharing obstacles include proprietary restrictions and data sharing platform.

1. Access to data is a major issue. If GPS data contains personally identifiable information (PII), agency access is limited unless they obtain a special type of research certification.

2. Limited access to test data was cited as an obstacle.

3. Data size is an obstacle.

1. Technical challenges exist with specialized software needed to access GPS probe data.

2. Although the NPMRDS/HERE data seems to be a good source of travel time data, manipulating the data using traditional database software (e.g., Microsoft Access) is difficult due to file size limitations (e.g., 2 GB).

3. Data from private vendors such as NPMRDS/HERE are difficult to manipulate due to the large file size and network conflation challenges.

4. The MPO would like to make more use of NPMRDS datasets, but it requires specialized software tools such as Statistical Analysis Software (SAS). The MPO has not evaluated this capability.

5. Travel time data in the NPMRDS is associated with the National Highway System, which represents only a portion of the MPO roadway network. The MPO is able to download other files to generate reports in MS Access based on location. The MPO can do light reporting using the travel time data and static table with Traffic Message Channel (TMC) location codes. However, it is challenging to do spatial joins in GIS due to file size.

6. The MPO has a need for more robust tools to handle large datasets.

1. Network testing was cited as an obstacle.

1. Not knowing the owners of data was cited as an obstacle.

1. 45% of survey respondents indicated they do not currently share travel time/speed data with other organizations, but they are willing to do so.

2. The MPO wants to collaborate with regional partner agencies to identify additional sources of mobility data for the database, but they do not know what types of data are available.

3. There is no systematic process or platform in-place for sharing data with partner agencies.

4. Collaboration takes place between individual partner agencies and FDOT, but should be expanded to other regional partners.

1. Gaps in travel time/speed data, turning movement counts at intersections, origin/destination data, pedestrian/bicycle activity data, and data to support calculation of return on investment.

2. Assess how connected vehicle data could be incorporated into the Multimodal Transportation Database and used for planning purposes.

3. Improved data quality/data collection standards for travel time/speed data.

4. Define data standards for Bluetooth/GPS probe data.

5. Make better use of expanding data sources for performance management.

6. Develop/formalize business processes for the following:
   1. Systematics process to gather travel time/speed data from partner agencies.
   2. Procedures for managing and analyzing mobility data.
   3. Procedures for attaching travel time data to roadway segments in the Multimodal Transportation Database.
   4. Procedures for analysis such as determining the average travel time and standard deviation during the PM peak on a typical weekday, or determining whether there is a correlation between travel time on arterials and fatality rates.

7. Define a Method for data integration.

8. Improve the structure of the Multimodal Transportation Database to support data integration.

9. Develop data sharing platform to support external partner agency access to the Multimodal Transportation Database.

10. Address proprietary and personally identifiable information (PII) data restrictions.

11. Address data storage issues associated with data size.

12. Use more robust analysis tools to handle large datasets.

13. Perform staff training on use of analysis tools.

14. Address network conflations issues associated with NPMRDS/HERE data.

15. Address network testing issue.

16. Improved collaboration among partner agencies to increase awareness of mobility data availability.

17. Have a formal governance or collaboration program.

18. Define systematic process for sharing data with partner agencies.

1. Data Collection/ Acquisition

1. Incorporate traffic count data from other local agencies into the Multimodal Transportation Database. Initial efforts should focus on short-term count data from Hillsborough and Pinellas MPOs.

2. Address gaps in travel time/speed data, turning movement counts at intersections, origin/destination data, pedestrian/bicycle activity data, and data to support calculation of return on investment.

3. Address data gaps to meet requirements of the MAP-21/FAST Act Performance Management regulations.

4. Utilize NPMRDS travel time data and combine it with regional traffic volume data.

5. Archive travel time/volume data and make it available to support MAP-21 requirements.

6. Develop specifications for collecting, updating, maintaining, and archiving mobility data in the Multimodal Transportation Database and assign responsibility for these activities.

7. Develop systematic process to gather/update travel time/speed data from partner agencies.

8. Identify opportunities for collaboration between connected vehicle data capture activities and existing data programs.

9. Conduct annual review of regional mobility data programs to identify duplicate data collection and storage activities. Eliminate and replace with single source of data for specific data programs to ensure data is collected once and used many times.

10. Identify applications that use expanding data sources, such as Strava.

2. Data Quality

1. Develop policy to define responsibilities for data quality assurance, including accuracy, timeliness, completeness, validity, coverage, and accessibility.

2. Adopt data quality standards for collection, processing, use, and reporting of mobility data.

3. Require metadata for mobility data systems.

4. Document quality control procedures, including instructions on how to process data errors.

5. Develop validation rules and allowable values for coded fields and incorporate these rules into data systems and data repositories. Use established validation rules to the greatest extent possible.

3. Data Standards

1. Develop and enforce data quality standards for travel time/speed data. Ideally, enforcement should be a collaborative effort whereby participants agree on holding each other accountable.

2. Develop standard data template format to foster joint usage and collaboration on mobility data.

3. Develop minimum regional standards for Bluetooth/GPS probe data

4. Ensure coordination with applicable national data standards.

5. Develop policy to define responsibilities for supplying metadata, data dictionaries, and descriptive information for mobility data systems to facilitate the understanding, characteristics, and usage of data.

6. Develop metadata guidelines to indicate data name, size, data type, where data is located, data ownership, update frequency, age of data, and how data can be used or integrated with other data sources.

4. Data Integration and Expandability

1. Leverage the Regional Integrated Transportation Information System (RITIS) as a tool for data integration. RITIS is available through FDOT District 7, so no procurement purchase is required. The MPO should facilitate the RITIS implementation effort from planning through fruition.

2. Use common linear network to facilitate data sharing and integration.

3. Develop procedures for attaching travel time data to roadway segments in the Multimodal Transportation Database.

4. Determine improvements needed to the structure of the Multimodal Transportation Database to support data integration.

5. Data Storage and Access

1. Understand stakeholders' business needs for mobility data access and sharing.

2. Develop policy to define responsibilities for data storage, hosting, data retention/archival, and disposal.

3. Develop policy to define data ownership and dissemination rights.

4. Implement standard data sharing agreement with internal and external stakeholders.

6. Business Analysis Tools

1. Explore use of tools to integrate data from other systems and to enhance data sharing among regional stakeholders. These could include use of XML formats for sharing data, GPS technology for collecting and geocoding data location, and GIS tools for geographical display of data.

2. Share published data in a centralized location such as the Multimodal Transportation Database, SharePoint, or open data portal that is accessible to internal and external stakeholders.

3. Involve network/database administrators from partner agencies in development of shared data portal.

4. Develop procedures for conducting analyses such as determining the average travel time and standard deviation during the PM peak on a typical weekday, or determining whether there is a correlation between travel time on arterials and fatality rates.

5. Develop and implement training program on use of analysis tools.

7. Data Governance

1. Implement a formal governance or collaboration framework.

2. Identify and assign governance roles and responsibilities.

3. Develop, maintain, and enforce a Data Governance Manual.

4. Develop and publish a Data Catalog to increase awareness of mobility data availability.

5. Develop and publish a Business Terms Glossary to define standard terminology for how mobility data is defined and used across the agency.

6. Hold a Data Summit or conference to engage regional stakeholders and share ideas.

7. Identify resource needs.

8. Collaboration

1. Identify datasets that can be openly shared.

2. Determine which stakeholders are willing to engage in a data sharing agreement.

3. Develop contract language for vendors to ensure data can be shared with other agencies.

9. Data Privacy and Security

1. Establish and maintain security standards to secure data and protect privacy of individuals and contributing agencies.

2. Clearly document policies, standards, and procedures and distribute to all staff responsible for collecting, maintaining, or distributing mobility data.

3. With respect to accessing and using data with personal identifiable information (PII), stakeholders should be aware of the applicable privacy protections and are encouraged to seek further legal guidance with their attorneys.

4. Further explore Privacy by Design as a way to address privacy concerns.

10. Performance Measures

1. Define performance indicators and implement a monitoring program to measure the success of the governance program. Performance indicators should measure program activities (i.e., outputs) and confirm the governance program is delivering results (i.e., outcomes). Output indicators quantify the activities of the Mobility Data Task Force and reflect the level of effort expended or scale/scope of activities. Outcome indicators quantify the effectiveness of the Coordination Group in terms of meeting its mission and stated goals. Example output and outcome indicators are provided in the Example Data Governance Manual in appendix G. Document the adopted measures in the Data Governance Manual.

"Note this reference to performance measures is not related to performance management requirements that are being implemented as pursuant to several rules codified in 23CFR part 490. In no way does this substitute for compliance under that rule. See FHWA TPM website for details related to 23CFR part 490."

2. Establish a communication protocol and plan for communicating performance measure results to executive level staff, Mobility Data Task Force, and data users/stakeholders.

11. Risk Assessment

1. Conduct risk assessment to identify regional mobility data programs and current and potential risks associated with these programs (e.g., what would happen if there was a loss of data or data quality issues). A risk assessment matrix can be used to determine: 1) how much data is needed; 2) how accurate data should be; 3) what the refresh rate of the data should be; 4) who should have access to the data; and 5) potential risks of data loss.

2. Develop Risk Management Plan to address risks if they occur. Risk management practices should include disaster recovery procedures.

12. Knowledge Management

1. Develop and implement a Knowledge Management system for organizing, storing, and archiving knowledge regarding mobility data sets and workflow processes. This ensures lessons learned and experiences pertaining to mobility data are retained and archived as staff retire or leave the organization.