BACKGROUND
Traffic management systems (TMSs) are deployed in the United States to improve the efficiency, safety, and reliability of travel on designated portions of the surface transportation network. TMSs are typically large, complex systems, that consist of a number of subsystems (e.g., ramp metering, traffic signal control, dynamic message sign, data, traveler information, communication, software, hardware), as well as a range of components (e.g., dynamic message signs, detection devices/sensors, closed-circuit television cameras, signal heads, controllers, communication switches, servers, video wall, phones).
TMSs capabilities could support different services, functions, tasks, or actions. For example, some TMSs manage only the vehicular traffic on freeways in each region, while others may manage the entire road network, which may include surface streets and freeways. TMSs may also have different roles and responsibilities (e.g., sharing roadway and traveler information) that involve sharing, coordinating, or making information available to other agencies, systems, or service providers (e.g., emergency services, transit).
TMSs range in size (i.e., coverage area), functionality (e.g., incident management, ramp management), services (e.g., traveler information, managing traffic across institutional boundaries), and capabilities (e.g., whether or not the system includes a traffic management center, which can be used for sharing information).
Significant changes have occurred with cloud options available to agencies to store data. TMSs have traditionally been designed with local servers and limited ability to modify or make changes. Technical options are available to support agencies making changes in the design, configuration, and technologies used to support a data subsystem (see Special Note A).
Limited technical information and resources exist to help agencies assess the capabilities and evolving needs for TMSs data subsystems. There are limited resources to support agencies integrating the needs and requirements of data subsystems into the decisions made in planning and programming processes throughout the life cycle of a TMS (e.g., how to plan, design, or procure needed data storage and management capabilities). Agencies face challenges with systematically managing data as part of their TMSs operation. There are limited resources for agencies to use or to assist with data management (e.g., archiving, use, configuration, monitoring use), and issues with receiving, sharing or using data with third-party sources or within an agency (e.g., licenses, proprietary, sensitive information). Research is needed to help agencies better manage data in TMSs.
OBJECTIVE
The objective of this research is to develop two technical reports to support agencies’ decision-making processes and frame the opportunities for agencies to consider when contemplating improvements to data subsystems and data management plans of their TMSs:
- Report No.1, Data Subsystems for TMSs, and
- Report No.2, DMP for TMSs.
Accomplishment of the project objective will require completion of the following tasks.
TASKS
PHASE I – PLANNING
Task 1. Conduct a review of current practice and identify gaps through literature review, surveys, interviews, etc., of agencies on the assessment, benchmarking, planning, design, management, and procurement of TMSs data subsystems. The comprehensive review will focus on identifying effective data management plans and practices appropriate for TMSs and provide insights on how data management practices address issues related to data standards, quality, documentation, and licensing, which are particularly important when external data is involved. This review will build off research and technical resources specific to agencies to use or adapt to meet the needs, requirements (e.g., real-time operation), and constraints for TMSs.
Task 2. Synthesize findings from Task 1 in a white paper (approximately 15 - 20 pages) to identify the knowledge gaps related to the research objective. The white paper is not intended to be a compendium of papers or summary literature review. It should present insights and gaps identified based on the synthesis of findings from literature review, surveys, and interviews. These gaps should be addressed in the final deliverables or the recommended future research as budget permits.
Task 3. Develop draft annotated outlines and review schedule for Reports No. 1 and No. 2. Each annotated outline is intended to provide the foundation, context, and framework for the subject matter in the technical reports to be developed in Task 6. These annotated outlines will include key technical topics, issues, major concepts, current trends and practices, examples, lessons learned, and checklists of issues to consider. The initial annotated outline will be submitted prior to the NCHRP panel meeting as specified in Task 4. The revised annotated outline submitted will address the comments provided prior to developing the two reports in Task 6.
While the contractor has discretion on the structure of the annotated outline, the following specific requirements shall be adhered to:
- The first section of each chapter after the introduction chapter will explicitly state its purpose, objectives, key topics covered in chapter, context for key issues, gaps, how the chapter is organized, how information in chapter builds off of prior chapter, how it will assist the reader with the next chapter, and a list of the remaining sections in the chapter.
- The first chapter of the report will address: purpose, objectives, focus or scope of the report, describe the technical focus and issues addressed in the report, provide the context of these technical issues (e.g., current practices, gaps in practice, challenges agencies are facing, why recommended practices are not used), opportunities for enhancing practices, potential benefits and outcomes from applying recommended practices, framework of technical issues covered in report, examples of practices within the report and context for material, intended audience, how report is structured, and how readers might consider navigating through the material and document.
- The second chapter will provide a technical overview and context for all technical content to be included in this report.
- Each chapter (not including the introduction) is expected to identify list of issues for the reader to consider specific to the chapter (e.g., issues to consider, challenges, policy implications, procedural, technical), current practices, highlight agency practices, and provide graphics reinforcing the objectives and key concepts specific to each chapter.
Report No. 1, Data Subsystems for TMSs, will review and compile information from available resources, offer insights, and synthesize current practices for agencies to consider when assessing, identifying needs, framing options to improve, developing requirements, and reviewing options to incorporate these needs and requirements into improvement projects or planning for the next generation of an agencies TMS’s data subsystems (e.g., performance management system (PeMS), traffic signal control system, traveler information system, ramp metering system). This information will support agencies (i) determining the appropriate factors to consider with assessing the capabilities of their data subsystems, identifying needed enhancements, and reviewing options to consider with making any improvements, and (ii) developing requirements and identifying other issues (e.g., resources, buy, lease, security) to be considered when selecting methods to acquire and implement data subsystems, and resources to store and manage data for current and future TMSs’ improvement.
At a minimum, Report No.1 must consist of the following:
- Introduction
- Definition of data subsystems
- Assessing data subsystems
- Needs for data subsystems
- Requirement for data subsystems (e.g., measure of effectiveness, requirement for functions/action/services)
- Planning for improving data subsystems (e.g., requirement, operation and maintenance, cost, options, deployment, benefits)
- Procuring data subsystems
- Evaluating and selecting data storage options
- Managing and maintaining data subsystems (organization chart, roles/support, positions requirement, contracting)
- Data subsystems design – interoperability and configure legacy storage
- Process (i.e., system engineering process)
- Options to get started with transition to new storage
- Data governance
- Cyber security
Report No. 2, DMP for TMSs, will provide a technical reference for creating holistic lifecycle DMPs to assist agencies managing data to facilitate TMSs collecting, using, or sharing data within their agency, with other systems, or the public. This report will review and compile current practices of data management and techniques appropriate to meet the needs and requirements unique to TMSs (e.g., real-time data collection, multiple systems in different locations, virtual operation). This report will identify issues to consider with developing or updating data management policies, procedures, plans, resource needs, and practices in support of meeting the needs and requirements unique to TMSs.
At a minimum, Report No.2 must consist of the following:
- Introduction
- Definition of DMP
- Elements of DMP
- Assessment and identify data management practices and capabilities of an agency
- Quality assurance/quality control
- Data storage
- Manage use of data (interface)
- Data inventory
- Configuration and maintenance
- Data governance
- Data security
- Decision support (update or restart)
Task 4. Organize a virtual meeting with the NCHRP panel to review and obtain feedback on the two draft annotated outlines developed in Task 3. Revise the draft annotated outlines based on written and oral feedback from the NCHRP panel meeting. Submit revised versions of each annotated outline for NCHRP’s review and approval, prior to the development of each technical report in Task 6.
Task 5. Prepare Interim Report No. 1 documenting the results of Tasks 1 through 4 and provide an updated plan for the remainder of the research. The updated plan must describe the methodology and rationale for the work proposed for Phase II.
PHASE II – EXECUTION
Task 6. Develop Reports No. 1 and No. 2 and submit to the NCHRP panel’s review per the schedule according to the approved Interim Report No.1.
Task 7. Develop two PowerPoint presentations (approximately 30 minutes each) for the two technical reports developed in Task 6. The presentation slides shall specify the research purpose, objectives, key issues addressed, research products developed, and the potential benefit or value of the products. The draft presentations will be reviewed, and comments provided will be addressed in the final versions of the presentations. The contractor is expected to present the project findings in a webinar to be organized by TRB after dissemination of the project deliverables.
Task 8a. Prepare agenda and materials for one workshop with at least 5 representatives from state and local agencies to review and provide feedback on the final draft reports and presentations. The representatives should be from state and local agencies in varying geographic regions and size. Submit workshop materials and proposed attendee list for the NCHRP panel’s review and approval.
Task 8b. Conduct one workshop as approved in Task 8a. Revise the final draft reports, presentations, and other workshop materials taking into account feedback gathered during the workshop and submit for the NCHRP project panel’s review.
Task 9. Prepare the final deliverables including the following:
- A conduct of research report that documents the entire research effort, any lessons learned, and recommendations for future research;
- Final reports;
- Media and communication material (e.g., PowerPoint presentations, two-page executive level flyer for each report, graphics, graphic interchange format (GIF)s, press releases); and
- A stand-alone technical memorandum titled “Implementation of Research Findings and Products.” Additional funding may be available for a follow-up contract on the implementation of the results.
STATUS: Proposals have been received in response to the RFP. The project panel will meet to select a contractor to perform the work.
