![]() |
![]() ![]() ![]() |
![]() |
![]() |
Hillsborough Metropolitan Planning Organization Pilot of the Data Business Plan for State and Local Departments of Transportation: Data Business PlanChapter 4. Data Governance FrameworkIt is recommended that the region establish a data governance framework for mobility data in the region. This includes adopting core data principles, implementing a data governance model, defining roles and responsibilities for managing mobility data, and developing supporting documents such as a Data Governance Manual, Data Catalog, Business Terms Glossary, and Data Sharing Agreements. Data PrinciplesAll mobility data related decisionmaking should be guided by the following set of core data principles2: Principle 1—VALUABLE: Data is an asset. Data is a core business asset that has value and is managed accordingly. Principle 2—AVAILABLE: Data is open, accessible, transparent, and shared. Access to data is critical to performing duties and functions. Data must be open and usable for diverse applications and open to all. Principle 3—RELIABLE: Data quality and extent is fit for a variety of applications. Data quality is acceptable and meets the needs for which it is intended. Principle 4—AUTHORIZED: Data is secure and compliant with regulations. Data is trustworthy and is safeguarded from unauthorized access, whether malicious, fraudulent, or erroneous. Principle 5—CLEAR: There is a common vocabulary and data definitions. Data dictionaries are developed and metadata established to maximize consistency and transparency of data across systems. Principle 6—EFFICIENT: Data is not duplicated. Data is collected once and used many times for many purposes. Principle 7—ACCOUNTABLE: Decisions maximize the benefit of data. Timely, relevant, high quality data are essential to maximize the utility of data for decisionmaking. Data Governance ModelA data governance model depicts the relationship between mobility data programs, the various individuals/agencies responsible for implementing data governance, and the users/stakeholders for the data programs. The model diagram in figure 4 proposes a formal structure for mobility data governance in the Hillsborough region. The following components are depicted in the model diagram:
It is recommended that the Hillsborough, Pasco, and Pinellas Metropolitan Planning Organizations (MPOs) formally designate a Regional ITS Committee (A) to coordinate the planning, programming, engineering, and implementation of intelligent transportation systems projects in the tri-county region. This regional ad hoc working group would meet quarterly or biannually as needed to discuss topics related to:
The Regional Intelligent Transportation System (ITS) Committee would designate a Mobility Data Task Force (B) to coordinate on mobility data collection, data acquisitions, and crosscutting data management issues (e.g., data quality, standards, metadata, data privacy, and security). The Task Force would not meet separately, but conduct business during the Regional ITS Committee meetings. A regular agenda item to discuss the Data Business Plan should be added to the Regional ITS Committee meeting. The Task Force would consist of designated individuals from Regional ITS Committee member agencies and other MPO partner agencies who are responsible for the oversight of mobility data programs to support the business functions of their agencies. Potential Task Force members are shown in figure 4. The Mobility Data Task Force should be supported by an Executive Group (C), which consists of senior level managers from member agencies. The Executive Group would not meet formally, but would provide executive level support for mobility data governance activities, including dedicating resources as needed and establishing memorandums of understanding for data sharing with other partner agencies. An example data sharing agreement is provided in appendix E. Mobility data governance champions from within the Hillsborough MPO, Pinellas MPO, and Pasco MPO should tri-chair the Mobility Data Task Force. These individuals would also liaison with the Regional ITS Committee (A). Mobility data stewards (D) within partner agencies would ensure mobility data that is collected, maintained, and used by their agency is managed according to policies established by the Mobility Data Task Force. Mobility data users and stakeholders (E) would not be involved in data governance activities but would benefit from improved coordination and data management practices resulting from the governance framework. ![]() Figure 4. Flow chart. Data governance model. Roles and ResponsibilitiesThe following data governance roles are defined for the region:
Table 7 defines the roles and responsibilities for supporting the governance framework. These roles/responsibilities should be vetted with members of the Mobility Data Task Force. It is recognized that the organization structure of individual partner agencies are all different. The roles and responsibilities listed are job functions and not necessarily job titles.
Rules of EngagementThe Regional ITS Committee should develop and approve a Charter related to Data Business Plan implementation to set forth the purpose, goals, membership, roles, and responsibilities and "rules of engagement" regarding collaboration and coordination for the group. Potential rules of engagement could include the following:
An example charter is provided in appendix F. Governance DocumentationOnce the Regional ITS Committee has formally approved a Charter, the group should also develop and approve the following supporting documents to define policies, standards, and procedures for data governance in the region:
2 AASHTO Subcommittee on Data, Data Subcommittee Efforts on Core Data Principles Web site, https://data.transportation.org/aashto-core-data-principles/. [ Return to Note 2 ] 3 NCHRP 666: Target-Setting Methods and Data Management to Support Performance-Based Resource Allocation by Transportation Agencies, Volume II: Guide for Target-Setting and Data Management, 2010. [ Return to Note 3 ] 4 Data Governance, Standards, and Knowledge Management, Alaska Department of Transportation and Public Facilities (ADOT&PF), 2009, appendix B—Kansas Department of Education Roles and Responsibilities and appendix C—Data Governance Manual. [ Return to Note 4 ] |
![]() |
||
![]() |
United States Department of Transportation - Federal Highway Administration |