A FRAMEWORK FOR WORK ZONE EVENT DATA COLLECTION …...A FRAMEWORK FOR WORK ZONE EVENT DATA COLLECTION AND MANAGEMENT : 2 : Work zones vary widely across the nation and the number of

WORK ZONE DATA INITIATIVE

A FRAMEWORK FOR WORK ZONE EVENT DATA COLLECTION AND MANAGEMENT

VERSION 4

FEBRUARY 28, 2020

FHWA-HOP-20-019

Notice

This document is disseminated under the sponsorship of the U.S. Department of Transportation in the interest of information exchange. The U.S. Government assumes no liability for the use of the information contained in this document.

The U.S. Government does not endorse products or manufacturers. Trademarks or manufacturers' names appear in this report only because they are considered essential to the objective of the document.

Quality Assurance Statement

The Federal Highway Administration (FHWA) provides high-quality information to serve Government, industry, and the public in a manner that promotes public understanding. Standards and policies are used to ensure and maximize the quality, objectivity, utility, and integrity of its information. FHWA periodically reviews quality issues and adjusts its programs and processes to ensure continuous quality improvement.

Technical Report Documentation Page

1. Report No. FHWA-HOP-20-2019

2. Government Accession No.

3. Recipient’s Catalog No.

4. Title and Subtitle A Framework For Standardizing and Communicating Work Zone Event Data (WZED) (Version 4)

5. Report Date Feb. 28, 2020 6. Performing Organization Code

7. Authors Dr. Denny Stephens, Vital Assurance; Dr. Jeremy Schroeder, Athey Creek; Ms. Rachel Ostroff, ICF

8. Performing Organization Report No.

9. Performing Organization Name and Address 10. Work Unit No. (TRAIS)

ICF Incorporated, L.L.C. 1725 Eye Street, NW Washington, DC 20006

11. Contract or Grant No.

12. Sponsoring Agency Name and Address U.S. Department of Transportation Federal Highway Administration 1200 New Jersey Avenue, SE Washington, DC 20590

13. Type of Report and Period Covered 14. Sponsoring Agency Code

15. Supplementary Notes Todd Peterson (TOCOR), Harry Crump (COR) 16. Abstract This document describes a framework to assist transportation agencies and the work zone stakeholder community in establishing a standardized approach for digitally describing work zones and for communicating work zone event data (WZED) with contractors, neighbor agencies, third-party data consumers, and other key stakeholders. This framework has three main components. It provides an introduction for a WZED dictionary which standardizes digital descriptions of work zone activities that enable and support transportation agencies and third-party providers to describe and communicate work zone-related information to agency, private sector, and public users timely and seamlessly across multiple jurisdictions and regions. Secondly, this framework provides a conceptual architecture for a WZED warehouse and for work zone data systems (WZDS) for collecting, storing, using, and communicating WZED. Lastly, this framework provides an introductory guide for implementation of standardized WZED and WZDS for those agencies considering their adoption. 17. Key Words Work Zone Event Data, WZED, WZED Warehouse, Work Zone Data Systems, WZDS

18. Distribution Statement

19. Security Classification (of this report) Unclassified

20. Security Classification (of this page) Unclassified

21. No. of Pages 188

22. Price N/A

Form DOT F 1700.7 (8-72) Reproduction of completed page authorized


A FRAMEWORK FOR WORK ZONE EVENT DATA COLLECTION AND MANAGEMENT i

TABLE OF CONTENTS

1. Introduction and Overview ........................................................................................ 1

1.1. Framework Document Purpose and Overview ................................................. 1

1.1.1. Intended Audience ............................................................................. 2

1.1.2. Framework Development and Organization ....................................... 3

1.1.3. Related Project Documents ............................................................... 4

1.2. Key Terms and Concepts ................................................................................ 4

1.2.1. Work Zone Event Data (WZED) ......................................................... 4

1.2.2. WZED Dictionary ............................................................................... 5

1.2.3. WZED Warehouse ............................................................................. 6

1.2.4. Work Zone Data Systems (WZDS) .................................................... 6

1.2.5. WZDS Conceptual Architecture ......................................................... 6

1.3. FHWA’s Work Zone Data Initiative ................................................................... 7

2. Motivations and Needs for Standardized WZED and WZDS ................................... 9

2.1. Current and Emerging Needs .......................................................................... 9

2.2. Benefits of Implementing Standardized WZED and WZDS ............................ 10

2.3. Challenges of Implementation ....................................................................... 11

3. WZED Content – How we Describe Work Zones .................................................... 14

4. WZED Life Cycle Stages – How WZED Evolves During Construction ................. 17

5. WZED Stakeholders – Who Owns, Maintains, and Consumes WZED .................. 19

6. Stakeholder WZED Needs – Uses for WZED .......................................................... 24

6.1. Overview ........................................................................................................ 24

6.2. Prioritization and Incremental Implementation Of Stakeholder Needs ........... 29

7. WZED Use Cases – Describing WZDS Functions That Satisfy Stakeholder Needs ................................................................................................................................... 30

7.1. What Is a Use Case? ..................................................................................... 30

7.2. WZED Use Case Summary Descriptions ....................................................... 30

7.2.1. Prioritization and Incremental Implementation Of Use Cases .......... 45

8. Conceptual WZDS Architecture For Collecting, Storing, Using, and Communicating WZED ............................................................................................. 46

8.1. Simplified WZDS Hub-and-Spoke Conceptual Architecture ........................... 47


A FRAMEWORK FOR WORK ZONE EVENT DATA COLLECTION AND MANAGEMENT ii

8.1.1. WZED Warehouse Enables Consistent Data Management and Maintenance ................................................................................................. 47

8.1.2. Hub-and-Spoke Conceptual Architecture Simplifies WZED Communication ............................................................................................ 48

8.1.3. WZED and Communications Partitioning by Life Cycle Stage ......... 48

8.2. Expanded WZDS Conceptual Architecture with WZED Tools and Interfaces 49

8.2.1. Data Communication Interfaces and WZED Processing Tools ........ 50

8.2.2. Prioritization and Incremental Implementation Of WZED Warehouse Interfaces ..................................................................................................... 51

8.2.3. WZED Processing Tools Also Use Data From Other Sources ......... 51

8.3. Comprehensive View of the WZDS Conceptual Architecture ......................... 52

8.4. Exploring Details of Each of the WZDS Tools and Interfaces ........................ 59

8.4.1. Planning and Design Stage.............................................................. 59

8.4.1.1 Work Zone Events ............................................................ 60

8.4.1.2 WZED and WZDS Uses ................................................... 61

8.4.1.3 WZED Warehouse Interfaces ........................................... 61

8.4.2. Construction Operations – Active Construction and Maintenance Events 62

8.4.2.1 Work Zone Events ............................................................ 63



8.4.3. Construction Operations – Traveler Information ............................... 66

8.4.3.1 Work Zone Events ............................................................ 67



8.4.4. Construction Operations – WZED Two-Way Interfaces with Smarter Work Zones and CAVs ................................................................................. 69

8.4.4.1 Work Zone Events ............................................................ 70



8.4.5. Performance Analysis Tools and Interfaces ..................................... 71

8.4.5.1 Work Zone Events ............................................................ 72




A FRAMEWORK FOR WORK ZONE EVENT DATA COLLECTION AND MANAGEMENT iii

9. Agency Policies and Constraints Affecting Implementation of WZED and WZDS ................................................................................................................................... 76

9.1. Operational Policies ....................................................................................... 76

9.2. Constraints .................................................................................................... 77

9.3. IT Support Environment and TSMO ............................................................... 78

Appendix A. Description of WZED Use Cases and Data Flows .................................... 79 Introduction to this Appendix ...................................................................................... 79

Use Case Structure ...................................................................................... 79

WZED Warehouse Interfaces and WZED Data Flows ................................................ 80

Use Case Descriptions ............................................................................................... 85

Category 1 - Work Zone Planning and Project Coordination ........................ 85

Category 2 - Work Zone Impact Analysis ................................................... 108

Category 3 - Construction and Maintenance Contract Monitoring .............. 117

Category 4 - Real-Time Management and Traveler Information Provision . 135

Category 5 - Safety and Mobility Performance Measurement ..................... 146

Category 6 - Law Enforcement and Emergency Service Providers ............ 162

Category 7 - CAV Hardware Needs and System Readiness to Accommodate ................................................................................................................... 175


A FRAMEWORK FOR WORK ZONE EVENT DATA COLLECTION AND MANAGEMENT iv

LIST OF TABLES

Table 1. Candidate WZED Descriptors ............................................................................... 14 Table 2. Details of WZED Characteristics for Each Life Cycle Stage .................................. 18 Table 3. Description of WZED Stakeholder Groups ............................................................ 20 Table 4. WZED Stakeholder Needs by Use Category ........................................................ 25 Table 6. WZED Use Case Descriptions and Examples ...................................................... 32 Table 7. Illustration of WZED and Communication Partitioning by Life Cycle Stage ........... 48 Table 5. Use Case Component Details ............................................................................... 79 Table 8. WZED Warehouse Interfaces and WZED Data Flows .......................................... 82

LIST OF FIGURES

Figure 1. Illustration of the process used for development of this Framework. ..................... 3 Figure 2. Overview of the WZED Characteristics for Each Life Cycle Stage. ...................... 17 Figure 3. Use Case Categories Organized by Work Zone Life Cycle Stages...................... 24 Figure 4. Simplified Illustration of WZDS Hub-and-Spoke Conceptual Architecture ............ 47 Figure 5. Expanded Illustration of WZDS Conceptual Architecture with WZED Tools and Interfaces. ........................................................................................................................... 50 Figure 6. Illustration of Work Zone Planning and Design integrating WZED and Data from Other Sources .................................................................................................................... 51 Figure 7. Comprehensive view of WZDS Conceptual Architecture ..................................... 53 Figure 8. Work Zone Planning and Design WZDS Tools and Interfaces ............................. 60 Figure 9. Construction Operations WZED Warehouse Tools and Interfaces for Construction and Maintenance Events .................................................................................................... 63 Figure 10. Construction Operations WZED Warehouse Interfaces for Traveler Information Dissemination ..................................................................................................................... 67 Figure 11. Active Operations WZED Warehouse Interfaces for Smart Work Zones and CAVs .................................................................................................................................. 70 Figure 12. Planned and Actual WZED Archive Interfaces for Post Work Zone Analysis ..... 72 Figure 13. Comprehensive View of the WZDS Conceptual Architecture ............................. 81

https://icfonline-my.sharepoint.com/personal/51433_icf_com/Documents/FHWA/WZMP-WZDIx/Products/Reports_Updated/Task_3_Framework/WZAD%20FRAMEWORK%20(DRAFTV4.6.1)%20-%204Print_Feb2020.docx#_Toc33798227





A FRAMEWORK FOR WORK ZONE EVENT DATA COLLECTION AND MANAGEMENT v

LIST OF ACRONYMS

ATMS Advanced Traffic Management System

CAV Connected Automated Vehicle or Connected and Automated Vehicle

CCTV Closed Circuit Television

DMS Dynamic Message Sign

DOT Department of Transportation

FHWA Federal Highway Administration

IT Information Technology

ITS Intelligent Transportation System

MPO Metropolitan Planning Organizations

RCRS Road Condition Reporting System

SDO Standards Development Organizations

TMC Traffic Management Center

TMP Transportation Management Plan

TSMO Transportation Systems Management and Operations

TTC Temporary Traffic Control

WZED Work Zone Event Data

WZDI Work Zone Data Initiative

WZDS Work Zone Data System

A FRAMEWORK FOR WORK ZONE EVENT DATA COLLECTION AND MANAGEMENT 1

1. INTRODUCTION AND OVERVIEW

Transportation agencies are working to increase the information they share with neighbor agencies and with the traveling public about their roadway conditions and operations to help improve traffic flow and roadway safety. One example is the national emphasis on Transportation Systems Management and Operations (TSMO) information sharing and operational coordination between agencies to implement corridor and regional traffic management solutions, rather than rely on siloed single agency projects. Furthermore, external stakeholders, such as third-party traveler information systems and automated vehicle systems, desire to obtain roadway operations data currently collected by transportation agencies as well as data that agencies don’t currently capture, to improve traveler awareness and decision making. Information describing work zones is particularly important because work zones directly and significantly impact both traffic mobility and traffic safety.

Work zone information is one of the most problematic data sharing challenges for transportation agencies because work zones can change rapidly and because there are many stakeholders, inside and outside the agency, who influence work zones. Furthermore, there is currently no reference or standard which defines how to digitally describe and communicate dynamic work zone event data between stakeholders consistently and unambiguously. In response, the Federal Highway Administration (FHWA) launched the work zone data initiative (WZDI) to help systematize the collection and use of work zone event data (WZED) in work zone data systems (WZDS), locally, regionally, and nationally.

1.1. FRAMEWORK DOCUMENT PURPOSE AND OVERVIEW The purpose of this document is to provide a framework to assist transportation agencies and the work zone stakeholder community in establishing a standardized approach for digitally describing work zones and for communicating WZED to contractors, neighbor agencies, third-party data consumers, and other key stakeholders. The document also provides a conceptual WZDS architecture for collecting, storing, using, and communicating WZED.

Source. TTI

There is currently no reference or standard which defines how to digitally describe and communicate dynamic work zone activity data between stakeholders consistently and unambiguously.


Work zones vary widely across the nation and the number of potential users of work zone data is sizable. While a few like-minded jurisdictions could readily establish a common language for communicating work zone data, it is much more difficult to establish a standard structure to support regional, and national needs for communicating WZED. This document is intended to help work zone stakeholders understand how to organize and structure their work zone data and work zone data systems to seamlessly share data locally, regionally and nationally. It provides over 50 examples of current and potential work zone data usage by agencies. Agencies may select from these example use cases that best describe their own needs and implementation priorities, as well as develop their own use cases.

This Framework provides the following key information for agencies desiring to standardize and communicate their WZED:

• Motivation and Needs for Standardized WZED • WZED Content – How We Describe Work Zones • WZED Life Cycle Stages – How WZED Evolves During Construction • WZED Stakeholders – Who Owns, Maintains and Consumes WZED • Stakeholder WZED Needs – Uses for WZED • WZED Use Cases – Describing WZDS Functions to Meet Stakeholder Needs • Conceptual WZDS Architecture for Collecting, Storing, Using, and Communicating

WZED • Agency Policies and Constraints Affecting Implementation of WZED and WZDS • Approaches for Agency Implementation of WZED and WZDS • Appendix A. Description of WZED Use Cases and Data Flows

This Framework introduces the reader to the companion WZED Dictionary (1) (FHWA-HOP-20-020). The dictionary standardizes the digital description of work zones. These descriptions enable transportation agencies and third-party providers to communicate work zone-related information to agency, private sector, and public users efficiently and seamlessly across multiple jurisdictions and regions.

1.1.1. Intended Audience The intended audience of this document is the broad stakeholder network of WZED providers and users, such as construction managers, planners, programmers, and operators responsible for collecting, storing, using, and Source. TTI

This document is intended to help stakeholders understand how to organize and structure their work zone data and data systems in a way that can be shared locally, regionally and nationally. It provides resources that an organization may pick and choose from to develop a strategy that best suits their implementation needs.

https://collaboration.fhwa.dot.gov/wzmp/Data%20DictionaryDocuments/Forms/AllItems.aspx


communicating WZED and for implementing WZDS. Stakeholders also include government, industry, academia, and the traveling public; agencies with responsibility for optimizing work zone safety, mobility, and constructability; and analysts leveraging big-data solutions to develop better solutions for traffic control. Other stakeholders are vendors and manufacturers that develop connected hardware to facilitate vehicle-to-infrastructure networks and private-sector traveler information services that track real-time event data in map applications.

1.1.2. Framework Development and Organization This Framework document was developed using system engineering principles and provides some system engineering resources typically found in concept of operations and system architecture documents, as well as other information relevant to implementation of a standardized WZED and WZDS. The process used for development of the Framework is illustrated in Figure 1.

Describing a framework for WZED and WZDS is challenging for both the author and the reader. Although the material contained in this document corresponds to components of

Figure 1. Illustration of the process used for development of this Framework.

Compile Framework Document

Develop Implementation Guidelines

Collaborate on development of WZED Dictionary

Develop WZDS Conceptual Architecture

Develop WZED Use Cases with WZED Contents

Identify Stakeholder Needs for WZED and WZDS

Interview Stakeholders


system engineering resources, this Framework was organized more for readability and accessibility for the non-system engineer, than for system engineers and developers.

1.1.3. Related Project Documents Detailed technical descriptions of WZED content are provided in the companion Work Zone Event Data (WZED) – Data Dictionary Report (FHWA-HOP-20-020).(1) A detailed description of findings from stakeholder interviews and meetings can be found in the Work Zone Event Data (WZED) Needs and Opportunities Report (FHWA-HOP-20-018).(2) For approaches for agency implementation of WZED and WZDS, refer to the Work Zone Event Data Collection and Management Implementation Guide (FHWA-HOP-20-021).(3)

1.2. KEY TERMS AND CONCEPTS Following are brief introductions to new terms and concepts relative to standardizing WZED and WZDS that are likely to be new to the reader. Each introduction provides a link to more in depth discussion of the topic.

1.2.1. Work Zone Event Data (WZED) WZED are digital data descriptions of when, where, and how work zones are deployed. These descriptions, when shared with stakeholders, enable effective coordination of work zone events and help to manage and maintain safety and mobility in and around work zones. Standardized WZED meet content, structure, and format requirements that ensure accurate interpretation when communicated to other jurisdictions and stakeholders.

Examples of WZED include: Name of roadway where work zone is located Begin location of work zone End location of work zone Start date/time of work zone End date/time of work zone Total number of lanes Number of lanes to be closed

Which lanes to be closed Expected effect on travel

time/delay/queuing Reduced speed limit Warning notifications Detour route information

Note that WZED may include references to, but do not include the content of, the following types of information that are stored in other agency data systems:

Design documents Procurement documents Crash or other safety data Traffic and speed data Law enforcement data

What is Work Zone Activity Data? Digital data descriptions of when, where, and how work zones are deployed.


When implemented, standardized WZED support and enable:

Coordination of work zones between neighboring agencies to maintain traffic flow Analysis of likely work zones impacts on traffic safety and mobility Monitoring of contractor

compliance with contractual requirements and performance-based safety and mobility specifications

Communicating work zone information with travelers and third-party traveler information providers

Coordination of enforcement activities with law enforcement agencies

Assessment and enhancement of work zone safety and mobility nationally

Communicating work zone information with connected and automated vehicles (CAVs)

WZED are described in more detail in Chapter 3, WZED Content – How we Describe Work Zones.

1.2.2. WZED Dictionary Generally speaking, a data dictionary is a document that describes the content and attributes of data in a specified format. FHWA’s WZED dictionary defines the contents, format, and structure of WZED to streamline the communication of the data among stakeholders. It also describes data concepts which includes data elements, frames, business rules, and some hierarchical relationship between data. The dictionary consists of a conceptual model that supports the Framework use cases including data semantics,

general structure and relationship among data. This dictionary is intended to be used by agencies to standardize their WZED. It may also serve as a resource for standards development organizations working to establish recommended practices or standards for WZED.

The companion data dictionary may be obtained at WZED dictionary (1) (FHWA-HOP-20-020).

What is a WZED Dictionary? A document that defines, unambiguously, work zone activity data content, format and structure.

Components of a Temporary Traffic Control Zone

Source. ATTSA (adapted from MUTCD Section

https://collaboration.fhwa.dot.gov/wzmp/Data%20DictionaryDocuments/Forms/AllItems.aspx


1.2.3. WZED Warehouse In implementing digitized WZED, agencies will need to establish a data repository that supports collecting, storing, using, and communicating WZED over the work zone life cycle (i.e., planning, design, construction operations, and performance analysis). The data repository is referred to here as a WZED warehouse. A WZED warehouse may represent a single data warehouse for all of an agency’s WZED, or it may represent multiple databases, each of which stores WZED during a different stage of the work zone life cycle.1 The WZED warehouse is described in more detail in Section 8.1.1, WZED Warehouse Enables Consistent Data Management and Maintenance.

1.2.4. Work Zone Data Systems (WZDS) In addition to the WZED warehouse, an agencies’ WZDS incorporate all of the tools agencies use for planning, design, construction operations, and performance assessment of work zones and which share work zone information through the WZED warehouse. They also include WZED warehouse interfaces through which WZED are communicated to stakeholders. WZDS are described in more detail in Section 8.2, Expanded WZDS Conceptual Architecture with WZED Tools and Interfaces.

1.2.5. WZDS Conceptual Architecture The WZDS conceptual architecture described in this Framework is a graphical depiction of the WZED warehouse, data communication interfaces, tools, staff and other resources needed for comprehensive WZED usage and management. It helps agencies and stakeholders understand how to organize WZED and WZDS to meet their needs. The architecture provides the reader with a potential structure for clearly and consistently communicating WZED between the WZED warehouse and other agency data systems and across stakeholder groups throughout the work zone life cycle. It supports communication in both traditional agency workflows and in emerging agency functions, such as support for CAVs.

1 For clear and unambiguous WZED management, individual WZED should not be stored in more than one location.

What is a WZED Warehouse? Data repository used for collecting, storing, disseminating, managing, maintaining, and archiving work zone activity data.

What is a WZDS Conceptual Architecture?

A graphical depiction of the WZED warehouse, data communication interfaces, tools, staff and other resources needed for comprehensive work zone activity data management.


The WZDS conceptual architecture described here was developed to support all the user needs and use cases described in this document. The WZDI has demonstrated that there are many providers and users that need to communicate WZED, and need to do so across many data interfaces. Development of this

framework document has identified at least 17 different WZED warehouse interfaces that may be needed to support all of the potential uses identified here. However, an agency desiring to implement standardized WZED and WZDS does not need to implement all user needs, use cases, or interfaces. Each agency is encouraged to identify those use cases most important in the near term and implement the necessary interfaces in a manner consistent with the conceptual architecture. Then the agency may add interfaces to support additional use cases as the need arises and the resources become available.

The WZDS Conceptual Architecture is described in more detail in Chapter 8, Conceptual WZDS Architecture For Collecting, Storing, Using, and Communicating WZED.

1.3. FHWA’S WORK ZONE DATA INITIATIVE Many transportation agencies have long faced the challenge of how to best gather and communicate information about their work zone events. While once the sole purview of transportation agencies, information on work zone event has become a topic of interest among an evolving ecosystem of stakeholders, including those developing assistive technologies for work zone management. In response, FHWA launched the Work Zone Data Initiative (WZDI), the largest effort to tackle the data problem to date.

There isn’t one particular approach for structuring WZED in a database, each agency must design its own WZDS architecture to support its information exchange needs.

Source. TTI


The program’s mission is broad and forward-looking, and it has significant implications beyond the traditional stakeholders of highway construction. The data initiative is considering how work zone event is defined and how this contributes to improved performance measurement, forecasting, real-time operations, and programmatic decision making. It is also exploring how data are generated, shared, and used between various stakeholders.

The most significant outcome and benefit of the WZDI is the creation of a nationally consistent WZED dictionary and a framework to assist transportation agencies and the work zone stakeholder community in establishing a consistent approach for communicating WZED with contractors, neighbor agencies, third-party data consumers, and other key stakeholders. It will facilitate better harmonization of WZED for current and future uses, resulting in real-time, accurate, and comprehensive data in a standard format that allows for seamless data communications across jurisdictional boundaries.

The effort also includes stakeholder participation in a pilot exchange of open-source data on work zone events. The initiative will culminate in a series of publications documenting recommended practices for implementing data management specifications and business processes for work zone events.

Work Zone Data Initiative Goals • Develop a recommended practice for managing work zone data • Create a consistent language for communicating information on work

zone activity across jurisdictional and organizational boundaries

The most significant outcome and benefit of the WZDI is the creation of a nationally consistent WZED dictionary and a framework to assist transportation agencies and the work zone stakeholder community in establishing a consistent approach for communicating WZED with contractors, neighbor agencies, third-party data consumers, and other key stakeholders.

Source. TTI


2. MOTIVATIONS AND NEEDS FOR STANDARDIZED WZED AND WZDS

2.1. CURRENT AND EMERGING NEEDS Information about work zones is a key need for current and future data-driven transportation system management and operations (TSMO) efforts. To date, several efforts have been undertaken to encourage agencies to gather work zone data and to establish and use performance metrics. (4, 5, 6) These efforts consistently point to the need for data that describe when, where, and how work zones are deployed – work zone event data. These efforts also indicate that the collection and use of WZED has many potential benefits, including enhancing project planning and coordination efforts, improved public- and private-sector traveler information dissemination, and the successful deployment and operation of connected and automated vehicles (CAVs).(7)

The types and completeness of WZED available varies dramatically by region and agency, as does its storage and utilization. Many agencies do not collect or use WZED in a systematic manner, due to struggles to identify exactly what they want or need to collect, as well as in determining how they will benefit from such efforts and costs. Further, there are substantial differences among agencies that have taken steps to obtain and use WZED. For instance, when considering planned and current lane closure information, states using electronic WZED databases each use a different data format. Other states document work events on paper stored in hard copy record files.

Based on the current state of the practice, two key steps are needed to capture and share work zone information. First a data dictionary needs to be established that defines the data elements and data structures necessary to describe and communicate when, where, and how work zones are deployed. By standardizing this information, the ability of agencies and third-party providers to exchange critical work zone-related information with their peers and users seamlessly across jurisdictions and regions is greatly enhanced. Additionally, the ability of CAVs to operate across jurisdictional boundaries will depend on the existence of real-time, accurate, and comprehensive WZED accessible in a standard format everywhere such vehicles are operating. A national approach to defining WZED will also be useful to FHWA and other entities concerned with work zone management effectiveness at a national level. Not only would a national approach to WZED be useful, it is likely to have uses and applications not being considered today. The second step to capture and communicate work zone information is to establish

Source. TTI

Implementation of WZED will require time and funding resources and a commitment to make the changes necessary for success.


data system(s) within an agency (i.e., WZDS) that support collecting, storing, using, and communicating standardized WZED over the work zone life cycle.

2.2. BENEFITS OF IMPLEMENTING STANDARDIZED WZED AND WZDS The availability of WZED for planned, active, and completed work zones in the WZED warehouse can enhance existing practices for a variety of users and purposes.

Work Zone Planning and Project Coordination. Implementation will enhance agency abilities to strategically prioritize and coordinate the timing and location of planned projects and minimize cumulative impacts to motorists. For example, agency staff will identify projects occurring on parallel routes to be programmed at different times and may coordinate two projects next to one another on the same route to occur simultaneously. While these events currently occur on some level, the proposed structure will facilitate this process in greater detail, allowing more projects and individual phases to be tracked. This should result in fewer impacts to motorists by reducing the number of lane closures, capacity restrictions, and general disruptions on a roadway segment and alternate routes. In addition, standardized WZED can facilitate the coordination of and oversize vehicle approvals for permitting offices.

Work Zone Impact Analyses. Agencies will be able to better estimate the mobility and safety impacts of one or more proposed work zones based on outcomes of similar work zones with specific characteristics. Agencies will be able to better analyze different alternatives regarding work times, lane widths, and whether work zone Intelligent Transportation Systems (ITS) are needed.

Construction and Maintenance Contract Monitoring. Agencies will have a better data source to monitor when contractors are active in a work zone. This will aid them in tracking compliance with contract specifications or restrictions, including performance-based safety and mobility specifications, and in assessing potential penalties for violation of those specifications. The standardized WZED will also provide a way to track field modifications to project plans and the availability of assets such as ITS infrastructure during the active work zone.

Benefits include: • Reduced impacts to traveling

public due to better internal coordination.

• Improved impact analyses based on similar archived information.

• Enhanced contractor monitoring to ensure compliance with contract requirements.

• Verified data for real-time traveler information dissemination.

• Improved performance management practices.

• Improved dispatching and law enforcement practices.

• Verified data for CAV use.


Real-Time System Management/Traveler Information. Traveler information provided by agencies via 511, traveler information websites, dynamic message signs (DMS), and third-party websites and applications can provide additional active work zone information given the accurate and verified data within the proposed WZED structure.

Safety and Mobility Performance Measurement. Agencies and researchers can generate better performance measures for exposure and to identify characteristics and treatments that improve work zone mobility and safety. The proposed system will also allow for better comparison of estimated versus actual mobility impacts on the project, at a regional or programmatic level.

Law Enforcement and Emergency Service Providers. Law enforcement can improve dispatching and enforcement practices by (1) identifying locations where an active work zone may warrant additional presence, and (2) having a database to validate cited conditions of traffic violations. For example, citations about reduced speed limits based on worker presence or posted variable speed limits may sometimes be disputed. The WZED warehouse will also help agencies identify the need for law enforcement when contractors are active, help to deter theft, and aid in verifying law enforcement presence that may be paid by DOT funds. First responders can also modify trip routes based on known work zones that may impede mobility or access to an incident or emergency.

CAV Hardware Needs and System Readiness. Drivers and CAVs will have a verified source of information to navigate active work zones area in the case of changed alignments, lane shifts, or road closures.

2.3. CHALLENGES OF IMPLEMENTATION Implementation will require changing and restructuring existing agency procedures and practices. As a result, it is likely to produce numerous broad effects on agency resources and policies.

Staffing and staff skill levels for deployment. Agencies will require additional funding and operational support to deploy these systems in effective and meaningful ways that could significantly alter existing business processes for all work zone stages. Creating and maintaining the WZED warehouse may require transportation agencies to hire additional trained in-house staff or consultants to program, install, and integrate the necessary hardware and software for establishing the WZED warehouse and the user interfaces. Additional efforts may be needed to tailor specific capabilities for users

Challenges may include: • Skillsets and amount of

available agency staff to operate and maintain data systems

• Existing agency policies around data management

• Amount of financial resources available for data management

• Lack of national WZED deployment mandate

• Potential for inconsistency across agencies regarding data elements and use cases deployed

• Competing priorities and events for agency staff


to access the WZED from external agencies or on mobile devices in the field, for example. Implementation of a new WZED warehouse may require additional skills or staff members to operate and maintain the systems.

Agency policy or agency contracts. To be effective and useful, the agency must ensure all required WZED is entered into WZED warehouse in a timely and accurate manner. This may require changes to agency policy or agency contracts to integrate the entry of WZED to existing business processes or transition staff away from existing practices and documentation methods that the new systems may replace. Training and education may be required to ensure that agency staff and contractors are fully aware of needed data, how to access the WZED, when and how to enter information, and the benefits of doing so.

Required investment. The implementation of standardized data and associated data systems will require funding and investment by USDOT and state and local transportation agencies. Given current spending constraints, agencies may have difficulty identifying sufficient funding and resources to develop the WZED warehouse, either in its entirety as proposed or in part. Additional funding will be required for staff training and time required to collect and input WZED to the WZED warehouse.

Lack of mandate or specific policy directive for national deployment. Without a federal directive, transportation agencies may not be motivated to prioritize the development and implementation of standardized data.

Potential for inconsistency. Because of the flexibility intentionally incorporated into WZED warehouse, implementing agencies will likely deploy variations that contain different data elements for different use cases. This would mostly affect external users who are interested in using WZED from multiple agencies for comprehensive, comparative analyses, including USDOT, researchers, third-party providers, and contractors. Agencies may also choose to expand or modify existing systems using data elements or formats that are inconsistent with the proposed WZED.

Time of project completion. The timing for the completion of this effort and subsequent promotional activities could influence the success of the proposed WZED. For example, delays in completion could lead to waning stakeholder interest, particularly for those who are currently engaged but need to shift their focus to other efforts. Similarly, promotional activities are unlikely to be successful during the construction season when agency staff are less available to dedicate time to supplemental activities.

Source. TTI


Required construction operations staff effort. As already noted, significant staff time and resources may be required to develop and implement the proposed WZED and to conduct required training. This could mean a significantly increased level of effort required on a daily basis for agency or contractor staff to collect, input, and ensure the accuracy of WZED.

Additional staff time and resources to maintain the WZED in the WZED warehouse. Additional staff time and resources will be required to gather, input, and maintain the WZED within the WZED warehouse. Although some existing agency practices for documentation or data collection would be streamlined, new data will have to be gathered and logged. These additional roles and responsibilities may require new, dedicated staff to perform these duties. Alternatively, agencies may require contractors to perform some of the data gathering and logging events to maintain the WZED within the WZED warehouse as part of new construction contracts or on-site support contracts.

In order to overcome most or all of these disadvantages and limitations, agencies will need to present a compelling case for investment in staff time and resources to successfully implement the WZED dictionary. One justification might be that a WZED warehouse to input and store WZED may result in efficiencies and improved processes for a positive benefit-to-cost ratio.

For successful implementation, agencies will need to present a compelling case for resource investments.

Source. TTI

Source. TTI



3. WZED CONTENT – HOW WE DESCRIBE WORK ZONES

In the process of developing this Framework, the WZDI team interviewed stakeholders (2) to understand and characterize their needs and goals for use of WZED. The team developed Use Cases, summarized in Section 7, WZED Use Cases – Describing WZDS Functions to Meet Stakeholder Needs, which describe how WZDS would function to meet those needs. At the core of each of these use cases was a list of the candidate WZED descriptors that are desired by stakeholders to uniquely and unambiguously describe and communicate their work zone events. This effort found that WZED contents should, in general, include:

• Project and work zone descriptors including phase descriptions, and project, event, and subevent identifiers,

• Work zone beginning and end location descriptors, • Start and stop time and date descriptors by project, event, and subevent, and • Event descriptors such as lane closure, speed limit, and temporary traffic control

(TTC) descriptors

Table 1 expands this list further into a summary of candidate WZED elements. Detailed technical descriptions of these candidate WZED content required for stakeholder communications are detailed in the WZED Dictionary.(1) This dictionary defines the components of a work zone project a follows:

• A Work Zone Project is composed of one or more Phases. • A Phase may be composed of one or more WZ-Tasks (or events). • A WZ-Task may be composed of zero or more WZ-Subtasks (or subevents) or WZ-

Lane Event(s). • A WZ-Subtask may be composed of zero or more WZ-Lane Event(s).

Table 1. Candidate WZED Descriptors Project and Work Zone Descriptors • Owner agency • Owner agency project manager • Contractor/subcontractors • Funding allocation status • Expected number of phases

• Actual number of phases • Expected phase durations • Project ID • Event ID • Subevent ID

Work Zone Beginning and End Location Descriptors • Name of roadway where event/subevent is located • Roadway classification of roadway where

event/subevent is located • Facility type of roadway where event/subevent is

located • Direction of travel of event/subevent

• Planned begin location of event/subevent

• Planned end location of event/subevent • Actual begin location of event/subevent • Actual end location of event/subevent


Table 1. Candidate WZED Descriptors Start and Stop Time and Date Descriptors • Planned start date/time of event/subevent • Planned end date/time of event/subevent • Planned project duration • Indicator for level of confidence in expected start

date • Recurring flag

• Actual start date/time of event/subevent • Actual end date/time of event/subevent • Status • Date/time advance notice received

Event Descriptors • General description of event/subevent • General description about TTC approach • Expected geometrics associated with each event/subevent • Expected traffic control device(s) associated with each event/subevent • Actual geometrics associated with each event/subevent • Actual traffic control device(s) associated with each event/subevent • Indication that the TTC requires coordination between the projects • Reference to projects that need to be coordinated with • Planned number of lanes to be closed • Description of planned lanes to be closed • Total number of lanes • Planned number of lanes to be open • Planned number of short-term lane closures • Actual number of lanes to be closed • Description of actual lanes to be closed • Expected effect on travel time/delay/queuing • Lane closure permit number • Indicator that the work involves cutting or otherwise affecting the pavement • Temporary restrictions in place • Reduce speed limit • Feature that is modified relative to project plans • Change made to feature • TTC used to make feature change • Devices affected • Indicator that signal timing has changed • Description of signal timing change • Detour route information • Warning notifications • List of changes to notify travelers • Enforcement presence • Number of events requiring law enforcement support or flag indicating event/subevent needs law

enforcement support Metadata Descriptors • Indicator that a change to an event/subevent entry has been made


What Is Not Included in WZED?

It is also important to identify what is not included in WZED, because trying to store too much information can degrade database performance. Capturing data that is duplicated elsewhere can also create serious data maintenance and version control challenges.

WZED captures data elements that are unique to work zones and data that are not easily accessible from other sources. For example, although work zones affect traffic flow and mobility, detailed traffic and mobility data are not included in WZED. WZED can be correlated and cross-referenced with external data primarily on the basis of work zone location and date/time independent parameters. Traffic and mobility data are captured in other agency databases and may be correlated with WZED by location and time, when needed.

WZED includes data elements unique to work zones and not easily accessible from other sources.

Source. TTI



4. WZED LIFE CYCLE STAGES – HOW WZED EVOLVES DURING CONSTRUCTION

Work zones are dynamic and the WZED that describe them will evolve over the life of the road construction projects that they support. For the purposes of this Framework, the life cycle of a work zone and of WZED is divided into three stages:

• Planning and Design • Construction Operations • Performance Analysis

The WZED usage and level of detail and accuracy are different for each stage. The WZED characteristics for each life cycle stage are illustrated in Figure 2 and described in Table 2. Agencies may choose to expand this list according to their individual practices and procedures.

Figure 2. Overview of the WZED Characteristics for Each Life Cycle Stage.

Table 2 describes each of the life cycle phases and the characteristics of WZED for each, including the type of WZED, how rapidly WZED changes, and the WZED level of detail and accuracy required. Note that the three types of WZED, Planning and Design WZED, Active Operational WZED, and Planned and Actual WZED correspond to the three life cycle stages.


Table 2. Details of WZED Characteristics for Each Life Cycle Stage Life Cycle Stage and

Description Type of WZED

Used Rate of WZED

Updates WZED Level of Detail and

Accuracy Planning and Design. Includes initial concept of construction and anticipated lane closures, detailed planning and coordination, detailed design, through to construction and work zone bid and contracting.

• Planning and design WZED

• Evolves relatively slowly

• May be updated whenever there is an update to construction plans, from monthly to annually.

• Planning uses approximate location and approximate schedule.

• Design details location specifics and provides approximate schedule.

• Bid and contracting details location and schedule specifics to support contract monitoring and incentives.

Construction Operations. Includes dynamic work zone operations during all phases of construction.

• Active Operational WZED

• Highly dynamic • May need to be

updated daily or even hourly.

• Digital output to travelers may be updated by the minute.

• Actual detailed WZED location and schedule data are captured and communicated to stakeholders.

Performance Analysis. Includes post construction analysis of WZED and other relevant data sources to assess work zone impacts on safety and mobility and to provide input for future work zone planning and design. Also includes analysis of contractor performance and compliance.

• Planned and actual WZED archive

• Archived • Static

• Work zone performance analysis may use either detailed WZED (for example, contract monitoring and law enforcement records) or summary performance parameters.



5. WZED STAKEHOLDERS – WHO OWNS, MAINTAINS, AND CONSUMES WZED

WZED stakeholders are agency and non-agency individuals and groups who produce, maintain, or use WZED. Stakeholder interviews and review of current agency practices demonstrated that there are a large number of potential stakeholders who have a vested interest in obtaining and using WZED. Table 3 details this list of stakeholders, their work zone responsibilities, examples of WZED they need, and their role as owner, maintainer, or consumer of WZED. It is expected that the state or local agency that manages and maintains the roadway and controls or approves the deployment of work zones will also “own” the WZED and the WZED warehouse. Although they are external to the agency, construction contractors typically manage the work zones on a daily basis, and, correspondingly, will be authorized by the agency to “maintain” WZED by entering, updating, managing, and maintaining the data as work zones evolve throughout a project. Other external stakeholders are typically WZED “consumers” who receive WZED from the agency, but don’t contribute updates.(2)

It is assumed that the agency and contractors maintaining the work zones will also manage the WZED and WZDS.



Table 3. Description of WZED Stakeholder Groups

WZED Stakeholder Work Zone Responsibilities Type of WZED Needed WZED role (i.e. owner, maintainer or consumer)

Agency Work Zone Planning and Coordination

• Preliminary planning, scheduling and coordinating of construction and work zone events.

• Assess interaction of work zones across different agencies and to collaborate to minimize and mitigate impacts on regional mobility and safety.

• Analyze current and past work zones to assess past performance and to anticipate future impacts of work zones on safety and mobility.

• Planned location and schedule of roadway construction and work zones.

.

• WZED Owner actively controlling WZED by entering, updating, managing, and maintaining the data.

Agency Design and Engineering

• Design, detailed scheduling and coordinating of construction and work zone events.

• Assess interaction of work zones across different agencies and collaborate to minimize and mitigate impacts on regional mobility and safety.


• Detailed description of construction and traffic management (TTC plan).

• Criteria for monitoring contractor performance.


Agency Work Zone Data Systems Development and Operations

• Manage and maintain WZED warehouse that capture, communicate, store, maintain, and archive all agency WZED.

• Maintain WZED warehouse that contains all WZED.

• WZED Owner, maintaining the integrity of all WZED and WZED communications with internal and external stakeholders.

Agency Construction Operations Manager and Inspector

• Oversee and manage construction and work zones during active construction operations.

• Actual location and schedule of roadway construction and work zones.

• Daily update on work zone configuration.





Agency Roadway Maintenance Manager Function

• Planning, scheduling, coordinating and managing roadway maintenance and corresponding work zone events.

• Actual location and schedule of roadway maintenance and work zones.


Utilities Construction Work Zone Coordination

• Coordinate roadway and work zone events during utility construction operations.

• Location and schedule of utility construction and maintenance events affecting roadways and work zones.

• WZED Owner actively controlling utilities construction WZED by entering, updating, managing, and maintaining the data.

Law Enforcement Coordination

• Coordinate law enforcement activities and support during construction.

• Location and schedule of work zones for coordination of law enforcement support.

• WZED Consumer

ATMS Operator Function • Manage safe and efficient traffic flow during active construction operations.

• Actual, near real-time location and schedule of roadway construction and work zones.

• WZED Consumer

ITS/DMS/Traveler Information Systems

• Communicate work zone information to travelers and external traveler information systems to support safe and efficient traffic flow during construction.

• Near real-time details of work zone roadway geometry and configuration.

• WZED Consumer

Agency Congestion and Performance Manager


• Traffic and safety impacts of past and planned work zones.

• WZED Consumer

Agency Oversize/Overweight Permitting Function

• Routing and permitting of oversize/overweight vehicles traversing agency roadways.

• Actual location and schedule of roadway construction and work zones.

• WZED Consumer

Neighbor and Regional Partner Agencies

• Assess interaction of work zones across different agencies

• Collaborate to minimize and mitigate impacts on regional mobility and safety.

• Planned and actual schedule and location of construction and maintenance work zones.

• Collaborate with agency staff in coordinating work zone events and maintaining their respective WZED. WZED remains under agency control.




Construction Contractors • Responsible for implementing and managing work zones.

• Detailed design of construction and work zones.

• Criteria for contractor performance.

• WZED Maintainer. When authorized by the agency, they actively maintain WZED by entering, updating, and managing the data.

Third-Party Traveler Information Providers

• Capture and communicate relevant WZED to travelers to support their travel planning and safe traversal of work zones.

• Near real-time details of work zone roadway geometry and configuration.

• Consumer of WZED

Utilities • Coordinate utility construction with agency planning, design, and construction operations staff to minimize cost and disruption.

• Location and schedule of utility construction and maintenance events impacting roadways and work zones.

• Collaborate with agency staff in coordinating work zone events. WZED are maintained by agency staff. WZED remains under agency control.

Law Enforcement • Plan and manage law enforcement during operations and provide documentation to support enforcement actions.

• Location and schedule of work zones for coordination of law enforcement support.

• WZED Consumer

Travelers • Receive work zone information provided by agency and third-party traveler information systems and use it to plan their routes to safely navigate work zones.

• Actual schedule and location of construction and maintenance work zones.

• WZED Consumer

Connected and Automated Vehicles

• Capture relevant WZED in real-time • Provide relevant navigation and safety

information to drivers.


• WZED Consumer

Freight Haulers • Companies and drivers use work zone information to better plan their routes to reduce the impact on freight delivery and, at the same time, reduce congestion and traffic delays in work zones.


• WZED Consumer




State and Federal Transportation Agencies

• Capture archived work zone information for use in past performance assessment and future impact planning on a state and federal level.

• Traffic and safety impacts of past and planned work zones.

• WZED Consumer


6. STAKEHOLDER WZED NEEDS – USES FOR WZED

6.1. OVERVIEW A stakeholder WZED need is an event, process, or application which uses WZED as a core component. Three examples of stakeholder WZED needs are:

• Strategic coordination of agency TTC during planning and design to ensure travel path continuity.

• Third-party dissemination of information to travelers and others. • Compute/monitor performance measures at a project level.

Twenty seven stakeholder WZED needs, grouped into 7 categories, were found from stakeholder interviews and industry practice assessments. Figure 3 identifies the 7 categories of WZED needs, organized by WZED life cycle stage. Table 4 describes the categories in more detail and delineates the 27 stakeholder needs found, broken down by category.

Figure 3. Use Case Categories Organized by Work Zone Life Cycle Stages


Table 4. WZED Stakeholder Needs by Use Category Category Life Cycle Stage Summary Need

No. Need Description

Category 1 – Work Zone Planning and Project Coordination

Planning and Design

WZED is used to determine what work zone elements are expected to adversely affect travel on a route or within a corridor or network for one of two types of coordination (1) day-to-day coordination and (2) strategic coordination. Currently, both types are primarily occurring within organizations and do not often include inter-organizational events.

1.1 Strategic coordination of agency TTC during planning and design to ensure travel path continuity.

1.2 Strategic coordination of regional TTC during planning and design to ensure travel path continuity.

1.3 Strategic coordination of capacity-reducing projects during construction operations, at both agency and regional levels.

1.4 Coordinate work zones to avoid multiple capacity restrictions at the same time.

1.5 Reduce the number of lane closure disruptions over time on a roadway segment.

1.6 Permitting office coordination of oversize vehicle routes.

Category 2 – Work Zone Impact Analyzes

Performance Analysis

WZED is used to estimate work zone impacts for planned events in order to determine mitigation strategies. Given limited data available for work zone impact analyses, pre-analysis may use general assumptions and general roadway characteristics. While data from larger work zones may be archived for use in post-construction analysis, data is generally not collected or analyzed for short-duration work zones.

2.1 Estimate expected impacts for a single work zone.

2.2 Estimate expected combined impacts of multiple work zones.




Category 3 – Construction and Maintenance Contract Monitoring

Construction Operations

WZED provides information to track specification compliance, assess current compliance, compare past performance, and resolve contract disputes. Although some WZED are tracked fairly well in current agency contract management systems and procedures (albeit often significantly after the fact), other WZED are not tracked well, even when requirements are specifically included in the contract. WZED can provide objective data to enhance contractor performance reviews, both during the active project and during close-out reviews.

3.1 Monitor contractor compliance with contractual WZED-related requirements.

3.2 Monitor contractor compliance to performance-based safety and mobility specifications.

3.3 Identify field modifications to project plans.

3.4 Document changes in infrastructure asset location, availability due to work events.

Category 4 – Real-Time System Management/Traveler Information Provision


WZED is used for real-time system management by agencies and is directly consumable by travelers and others, including freight companies and third-party information providers. At present, work zones are not always reported to traffic management center (TMC) staff to communicate to traveler information systems and the traveling public, particularly for shorter duration and/or mobile work zones. This current state of practice often results in limited or general information available for real-time system management and traveler information.

4.1 TMCs/agencies management of facility operations.

4.2 Third-party dissemination of information to travelers and others.

4.3 Dissemination of WZED provided by Smart Work Zone equipment.




Category 5 – Safety and Mobility Performance Measurement

Performance Analysis

WZED is used to determine when and where exposure, mobility, and safety data should be extracted and used to assess work zone effects. Using the Work Zone Rule (8) as a foundation, agencies develop performance measures using a variety of data sources. Agencies can use real-time performance measures for performance-based specifications (PB-specs), although this has been limited, and to identify adjustments that can be made to reduce work zone impacts. Historic performance measures are used to track work zone impacts over time, identify areas for improvement, and assess the effectiveness of mitigation strategies. Surrogate, objective, or subjective (e.g., “feeling safe”) measures are often developed and used in place of potentially more meaningful and detailed performance measures due to a lack of resources or available consistent data.

5.1 Compute/monitor performance measures at a project level.

5.2 Compute/monitor performance measures at a regional/programmatic level.

5.3 Assess and enhance performance at the national level.

Category 6 – Law Enforcement and Emergency Service Providers


WZED is used to collaborate with or provide direct documentation support to various enforcement functions and activities. Documentation of worker presence or work activity now occurs as part of the citation issuance process. Additionally, when there is an incident typically police note whether or not a crash is in a work zone and possibly the speed limit but not much more.

6.1 Validate cited condition(s) of traffic violation.

6.2 Enforcement of lane closure/right-of-way access approval process.

6.3 Monitor and document Law Enforcement use on projects.

6.4 Monitor work zone Law Enforcement needs.

6.5 Support Law Enforcement monitoring of work site activities to deter theft.

6.6 Support first responder emergency route planning.




Category 7 – CAV Hardware and System Readiness


WZED would be used to inform drivers and CAV of temporary changes to the roadway. The current state for CAV systems is primarily in the research stage with limited test cases.

7.1 Alert and inform CAV of presence of work zones.

7.2 CAV trip navigation planning and execution

7.3 CAV safe speed and travel lane guidance


6.2. PRIORITIZATION AND INCREMENTAL IMPLEMENTATION OF STAKEHOLDER NEEDS

The list of stakeholder WZED needs can help agencies consider their specific needs and goals in the short- and long-term and provide a starting place for planning their implementation of WZED and WZDS. Each agency will not likely need to support all 27 stakeholder needs identified here, at least in the near term. Rather, they will likely have immediate priorities, among this list that they desire to pursue immediately and have other, medium- to long-term priorities that they will pursue when the needs become more urgent, when benefits become apparent, and when resources become available.

It is critically important however, that when agencies implement standardized WZED, they architect their WZED warehouse to enable straightforward expansion and evolution as more stakeholder needs are supported. This Framework was developed to outline a conceptual architecture (in Chapter 8, Conceptual WZDS Architecture For Storing, Using, and Disseminating WZED) for WZED and WZDS that will support a comprehensive list of needs. While agencies may begin by exchanging WZED with just one or two users, they will likely want to organize their WZED and design their WZED warehouse to support growth and evolution of WZED communications, and avoid having to redesign and revise their system later for new use cases. The challenge for agencies is to organize their WZED and design their WZED warehouse to manage and maintain WZED effectively and efficiently for the long-term, as well as the near-term.

To avoid future redesign, agencies may choose to structure their data systems to support the growth and evolution of data communications.


7. WZED USE CASES – DESCRIBING WZDS FUNCTIONS THAT SATISFY STAKEHOLDER NEEDS

After an agency has identified and prioritized its needs for WZED, the agency needs to develop use cases that describe its needs to WZDS developers and how its WZDS should function. Developers rely on use cases to develop requirements, architecture, and design of the WZED warehouse and WZDS. System testing confirms that user needs, as defined by use cases, are satisfied.

7.1. WHAT IS A USE CASE? Use cases describe the stakeholder events that use WZED and the collection, storage, usage, and communication functions that support these events. Use cases explain how the WZED should flow and how WZDS should function from a stakeholder’s point of view. Use cases are the means by which agencies describe their needs to WZED warehouse and WZDS developers and how their warehouse and WZDS should function.

Analysis of the stakeholder needs from the previous chapter by the WZDI team resulted in the development of 50 potential WZED use cases. These use cases are summarized in Table 6. Detailed descriptions of each use case are cataloged in APPENDIX A, Description of WZED Use Cases and Data Flows. The detailed descriptions in the appendix describe the following for each use case:

• Category • Stakeholder Need • Use Case Number and Title • Work Zone Life Cycle Stage • Use Case Description • Use Case Examples • WZED User(s) • WZED Flow Illustration • WZED User Objective • WZED Content • WZED Content Update Frequency • External Data Needed for User Objective • WZED Warehouse Interface Type

7.2. WZED USE CASE SUMMARY DESCRIPTIONS Table 6 summaries the 50 WZED use cases and provides examples to assist the reader. These use cases are organized by category and by user need (Chapter 6, Stakeholder

Why are Uses Cases Important? Use cases explain to WZDS developers how the WZDS should function from a user’s point of view. Developers rely on use cases to create requirements, architecture, and the design of the WZDS. System testing then confirms that user needs are satisfied.


WZED Needs – Uses for WZED). Detailed information for each use case can be found in APPENDIX A, Description of WZED Use Cases and Data Flows. A.


Table 5. WZED Use Case Descriptions and Examples Use Case Description Examples

CATEGORY 1 – WORK ZONE PLANNING AND PROJECT COORDINATION

Stakeholder Need 1.1 – Strategic Coordination During Project Initiation and Planning and Project Development (Agency)

1.1.1 – Agency Project Initiation and Planning Coordination

Agency coordinates plans for multiple projects along a particular facility to ensure travel path continuity.

Agency has list of capital improvement construction projects (new construction or reconstruction/widening), and/or a list of 3R projects (resurfacing, restoration, rehabilitation) to prioritize and coordinate (which ones to complete first, which ones should not happen at the same time because they affect the same motorists, etc.).

1.1.2 – Agency Project Design Coordination

Agency coordinates project designs for multiple projects along a particular facility to ensure travel path continuity.

Project plans (including TTC) are developed and finalized for the bidding process. The goal continues to be to coordinate when agency projects are occurring on various roadway sections in a way that minimizes overall impacts to travelers but now includes coordination of specific phases that may create conflicts and issues.

Stakeholder Need 1.2 – Strategic Coordination During Project Initiation and Planning and Project Development (Regional)

1.2.1 – Regional Project Initiation and Planning Coordination

Multiple agencies coordinate plans for multiple projects along a particular facility to ensure travel path continuity.

Multiple agencies in a region have lists of capital improvement construction projects (new construction or reconstruction/widening), and lists of 3R projects (resurfacing, restoration, rehabilitation) to prioritize and coordinate (which ones to complete first, which ones should not happen at the same time because they affect the same motorists, etc.).

1.2.2 – Regional Project Design Coordination

Multiple agencies coordinate project designs for multiple projects along a particular facility to ensure travel path continuity.

Regional project plans (including TTC) are developed and finalized for the bidding process. The goal continues to be to coordinate when regional projects are occurring on various roadway sections in a way that minimizes overall impacts to travelers (including coordination of specific phases that may create conflicts and issues).



Stakeholder Need 1.3 – Strategic Coordination During Active Work Zone Operations

1.3.1 – Agency Lane Construction Coordination

Agency sequences capacity-reducing projects in their domain to ensure that sufficient alternative route capacity is available to travelers at all times.

Sometimes an agency has multiple projects (rehabilitation or reconstruction/widening) occurring simultaneously next to one another on the same facility. During active work zone operations, the agency must keep the projects synchronized to ensure that the phasing for each project connects from a motorist travel path standpoint. Reasons for, and types of, synchronization may vary (e.g., lane shifts at end of one project need to align with lanes from adjacent projector; an agency may not want to open up new lanes in a segment until adjacent segments can also open up their new lanes).

1.3.2 – Regional Alternative Route Coordination During Construction

Multiple agencies sequence capacity-reducing projects in their region to ensure that sufficient alternative route capacity is available to travelers at all time.

An agency may have a project that involves the closure of an exit ramp during one of its phases that will likely divert traffic to an alternative ramp where another agency has work ongoing on the cross street. Strategic coordination between agencies during project development and construction would be initiated to ensure that the cross street work is completed before the exit ramp closure phase begins, but would continue into the active work operations stage.

Stakeholder Need 1.4 – Day-to-Day Operational Coordination to Avoid Multiple Capacity Restrictions at the Same Time

1.4.1 – Agency Capacity Restriction Coordination

Agency coordinates construction and maintenance events to minimize traffic impact.

During day-to-day operations within an agency, multiple needs may exist for periodic short-term or short-duration lane closures (could also be ramp, intersection, or shoulder closures). These could be for multiple construction contracts on the same roadway or maintenance work needed upstream or downstream of a construction contract. The desire is to coordinate all of the lane closures so they do not create excessive cumulative delays for motorists.


Table 5. WZED Use Case Descriptions and Examples Use Case Description Examples 1.4.2 – Agency Maintenance Contract Coordination

Agency coordinates maintenance contract events to minimize traffic impact.

An agency has a maintenance contract to repair various items on various roadways (guardrail repair, striping, etc.) under its jurisdiction. The contract is set up to allow contractor to group required events in the region so that one trip can be made to take care of multiple maintenance items. The contractor would submit its plans to do those events in general terms (such as during one or two days in an upcoming week, the actual days to be determined the day before).

1.4.3 – Agency Vertical Construction Coordination

Agency coordinates vertical construction closures, agency construction, and maintenance to minimize traffic impact.

An agency grants permission to a vertical construction contractor who submits a request to close a lane (long-term or short-term) on an urban arterial. The agency wants to coordinate the vertical construction lane closure with other planned lane closures by the agency (construction or maintenance) or other vertical construction lane closures on the segment, so that multiple entities are not closing lanes at the same time.

Stakeholder Need 1.5 – Day-to-Day Operational Coordination to Reduce the Number of Lane Closure Disruptions Over Time on a Roadway Segment

1.5.1 – Agency Maintenance, Construction, and Utility Schedule Coordination (Planning/Design)

Agency coordinates maintenance, utility, and construction contracts in a region on a given road segment to minimize traffic impact.

Agency maintenance crews sometimes need to close a lane for work a short distance upstream or downstream of a planned construction lane closure. The maintenance crew coordinates with the contractor to do the maintenance work on the same day as the contractor, and simply extend the lane closure upstream or downstream of the construction lane closure location.

1.5.2 – Pavement Cut Coordination

Agency coordinates maintenance, utility, and construction contracts in a region on a given roadway segment to minimize pavement cuts.

In situations where all work cannot be accomplished at the same time, the goal is to have all work involving pavement cuts (due to utilities, signal work, maintenance, etc.) accomplished before a planned resurfacing effort by the owner agency is performed.



Stakeholder Need 1.6 – Day-to-Day Operational Coordination with Permitting Office of Oversize Vehicle Approvals

1.6.1 – Oversize/Overweight Vehicle Route Coordination

Agency coordinates with permitting office about planned work zone events that impact oversize/overweight vehicles.

An owner agency permitting office needs to be able to determine whether an oversize/overweight permit request for a particular route can be approved for a given time period (or restricted for a given time period) based on roadway characteristics within the work zone.

CATEGORY 2 – WORK ZONE IMPACT ANALYSES

Stakeholder Need 2.1 – Estimating Expected Impacts for a Single Work Zone

2.1.1 – Work Zone Mobility Impact Assessment

Agency analysis of expected mobility impacts of a single work zone.

An agency may desire to analyze a proposed work zone to determine the delays to be expected (e.g., total hours or delay per person or per vehicle) over the entire project, during a particular time period or set of conditions for that project (e.g., during peak hours or hours of short-term lane closures), and/or for a particular upcoming specific period (such as an upcoming weekend lane closure).

2.1.2 – Work Zone Safety Impact Assessment

Agency analysis of expected safety impacts of a single work zone.

An agency may desire to assess the expected safety impacts of a particular work zone configuration (e.g., using narrowed lanes, adding temporary concrete barrier, or altered lane use assignments).

2.1.3 – Assessment of Expected Effects of Alternative TMP Mitigation Strategies

Agency analysis to compare the expected safety and mobility benefits of alternative TMP strategies.

An agency may want to estimate the safety effects of alternative TMP strategies, such as the trade-offs of using narrowed lanes to reduce the total duration of the project versus maintaining full-width lanes but increasing the overall project duration.

Stakeholder Need 2.2 – Estimating Expected Combined Impacts of Multiple Work Zones

2.2.1 – Corridor Mobility Impact Assessment

Regional analysis of expected mobility impacts along a corridor with multiple work zones.

An agency may want to estimate the total cumulative delay of a trip along a corridor for a motorist traveling through multiple work zones.


Table 5. WZED Use Case Descriptions and Examples Use Case Description Examples 2.2.2 – Network Mobility Impact Assessment

Regional analysis of expected mobility on a transportation network with multiple work zones.

An agency may want to estimate the expected changes in travel times due to the work zones for various travel paths through the network, or compute aggregate network-based measures such as the total cumulative increase in vehicle-hours of travel time in the network (or similar measures).

CATEGORY 3 –CONSTRUCTION AND MAINTENANCE CONTRACT MONITORING

Stakeholder Need 3.1 – Monitor Compliance with Contractual WZED-Related Requirements

3.1.1 – Short-Term Lane Closure Advance Notice Monitoring

Track compliance with short-term lane closure advance notice requirements.

An agency may have either construction or contract maintenance contracts that specify that a minimum number of days’ advance notice be given before initiating a short-term lane closure on certain roadways (could also be a shoulder closure, intersection closure, ramp closure, etc.). An agency may want to track compliance with that requirement and may eventually want to track accuracy of advance notice requests (i.e., how often the request changed and/or did the short-term lane closure take place when requested).

3.1.2 – Short-Term Lane Closure Allowable Hours Monitoring

Track compliance with short-term lane closure allowable hours requirements.

An agency may establish allowable hours for short-term lane closures for a project, along with penalty clauses for having a lane closure in place outside of those hours. The contract may also specify multiple levels of allowable closure times (e.g., one lane can be closed starting at 9 p.m. and two lanes starting at 11 p.m.). The agency may also want to track actual closure times against those allowable times.

3.1.3 – Allowable Lane Closures Monitoring

Track compliance with allowable lane closure requirements.

An agency may specify an allowable number of short-term lane closures for a project (or full-road closures, weekend closures, or duration of ramp closures). The agency desires to keep a running total of number of those events used to date.



Stakeholder Need 3.2 – Monitor Compliance to Performance-Based Safety and Mobility Specifications

3.2.1 – Travel Delay Performance Incentive

Track travel delay performance for incentive.

An agency could establish travel time or delay performance thresholds for contractors to maintain during a project. Contractor incentives could be reduced each time travel is delayed beyond the threshold.

3.2.2 – Traffic Safety Performance Incentive

Track traffic safety performance for incentive.

An agency could establish crash safety-based performance incentives, based upon the number of and/or severity of crashes (over the duration of the project, during a particular phase, or during particular events, such a short-term lane closures).

3.2.3 – Coordination Performance Requirements

Track compliance with coordination performance requirements.

An agency may incorporate a specification into a contract to coordinate events with another project. For example, an agency might have a project that involves the closure of an exit ramp during one of its phases that will likely divert traffic to an alternative ramp where another agency has work ongoing on the cross street. The schedules of both projects were initially coordinated to have the cross-street work completed before the exit ramp closure phase begins. Language in one or both of the contracts was included to ensure they remain in sequence.

Stakeholder Need 3.3 – Identifying Field Modifications to Project Plans

3.3.1 – Documenting Field Modifications to Project Plans

Documenting field modifications to project plans.

Project staff (agency and contractor) often agree to modify an element of the TTC plan or a temporary geometric feature because of field conditions or to address a traffic safety or operational issue that has developed within the project limits.



Stakeholder Need 3.4 – Document Changes in Infrastructure Asset Location, Availability Due to Work Events

3.4.1 – Document Changes in Infrastructure Asset Location, Availability Due to Work Events

Document changes in infrastructure asset location and availability due to work events.

Work zones often require temporary changes to the location or available roadway infrastructure assets. For example, contractor staff working on a freeway reconstruction project may have to turn off the power or fiber optic communications in the project section during certain work events (such as digging around power lines). This disrupts nighttime overhead lighting and operation of field ITS devices (e.g., dynamic message signs [DMS], ramp meters, closed circuit TV [CCTV], or traffic sensors).

3.4.2 – Document Traffic Signal Timing Changes

Document traffic signal timing changes.

Work zones may require temporary changes to the operations of certain roadway infrastructure assets. During an intersection reconstruction project, the agency might allow temporary closures of the left-turn lane and change signal timing to eliminate the left-turn phase on that approach.

CATEGORY 4 – REAL-TIME SYSTEM MANAGEMENT AND TRAVELER INFORMATION PROVISION

Stakeholder Need 4.1 – Use by TMCs/Agencies to Manage Facility Operations

4.1.1 – Advance and Real-Time ITS and DMS Lane Closure Traveler Information

Agency communicates advance lane closure traveler information.

An agency wants to post advance notification messages on its DMS and on its website about an upcoming lane closure, and possibly the expected delays or travel time impacts of that closure. The agency also wants to update the messages as the work actually begins and when it actually ends.

4.1.2 – Advance and Real-Time ITS and DMS Detour Traveler Information

Agency communicates advance traveler detour information.

An agency wants to post advance notification messages on its DMS and on its website about work zones that require travelers to follow a detour. For example, an upcoming freeway closure due to roadwork (overhead sign bridge installation) could require all traffic to exit, travel through the signalized cross-street intersection, and return to the freeway. Estimated travel time delays expected to occur during the closure, and the anticipated hours that the delays will be present, might also be available.



Stakeholder Need: 4.2 Third-Party Dissemination of Information to Travelers and Others

4.2.1 – Work Zone Plan Dissemination to Third-Party Data Providers

Agency communicates advance traveler information to third-party traveler information providers.

The same data that the agency uses to communicate its own information (Stakeholder Need 4.1) will be of interest and use to third-party data providers.

4.2.2 – Work Zone Plan Dissemination to Public

Agency communicates long-term work zone traveler information with several temporary changes to lane usage, turning movement prohibitions, reduced speed limits, etc.

An agency wants to notify public via its own website or data feed to third-party data providers of temporary changes to lane usage, turning movement prohibitions, reduced speed limits, etc.

Stakeholder Need – 4.3 Smart Work Zone Deployment and Operation

4.3.1 – Adjustments to Smart Work Zone Deployment

Deployment locations of equipment and the algorithms governing the operation of a smart work zone system may be altered as work progresses.

WZED (such as a change to the next phase of a project or an analysis of potential impacts during a particular activity that warrant a change in the deployment) from agency construction and contractor work zone operations staff/tools could trigger the need to deploy or reconfigure and re-calibrate the smart work zone devices and operation.

4.3.2. – Incorporation of Smart Work Zone Deployment Information Outputs Into Agency and Third-Party Traveler Information Efforts

Smart work zones are often self-contained systems that collect, process, and communicate information to travelers. That information dissemination could be broadened through existing agency and third-party traveler information systems.

Messages being displayed on portable changeable message signs that are part of the smart work zone system would be input into the WZED warehouse. Agency and third-party traveler information systems would extract those messages from the WZED warehouse and relay them through their dissemination mechanisms.



CATEGORY 5 – SAFETY AND MOBILITY PERFORMANCE MEASUREMENT

Stakeholder Need 5.1 – Computing/Monitoring Performance Measures at a Project Level

5.1.1 – Work Zone Mobility Performance Assessment

Agency analysis of individual work zone mobility performance.

Agencies would like to compute delay and queuing metrics occurring during an active project and/or after the project is complete for various periods (e.g., during peak periods, during work activity periods, during times of short-term lane closures, and during full weekend road closures). An agency could compare estimated traffic impact measures (from planning) and actual traffic impact measures to assess the accuracy of the initial estimates.

5.1.2 – Work Zone Safety Performance Assessment

Agency analysis of individual work zone safety performance.

Agencies would like to determine the change in crash risk that occurs during an active project and/or during a past project for various periods. The determination could include comparing estimated safety measure computed during impact analyses to actual measures occurring during the work zone in order to assess the quality of the initial estimates.

5.1.3 – Work Zone Mitigation Strategy Effectiveness Assessment

Agency analysis of the effect of implementing a particular strategy to address a specific mobility or safety issue (such as excessive speeding).

Agencies often desire to evaluate the effectiveness of a particular strategy or device implemented to address a specific issue. For example, an agency may decide to implement electronic speed limit signs to be able to post reduced regulatory speed limits within a project when work crews are on site and then raise them back up when crews leave the site. The agency may want to compute speed-related metrics for the project over time to measure whether speeds do change in response to changes in the speed limit.



Stakeholder Need 5.2 – Computing/Monitoring Performance Measures at a Regional/Programmatic Level

5.2.1 – Regional Assessments of Work Zone Mobility Performance Targets

Agency analysis of collective compliance of multiple work zones in a region to established mobility performance target thresholds.

An agency would assess the collective performance of work zones on its roadways in the region relative to established performance targets, such as the number or percent of work zones with delays and queues exceeding specified thresholds (e.g., duration of congestion, maximum or average delays, etc.) in the region.

5.2.2 – Computing Average Work Zone Safety Performance Measures by Region, Type of Project, Roadway Type, or Other Stratification

Agency analysis of collective work zone safety performance for specific types of projects in a region.

An agency would strive to determine typical or average values or increases in crash risk in work zones by region, type of work zone project, or other measures.

5.2.3 – Computing Regional Crash Modification Factors for Specific Work Zone Features, Events, or Strategies

Agency analysis to determine a crash modification factor for a specific work zone feature.

An agency would perform analyses of specific features or strategies implemented at projects across the region to develop a crash modification factor (or approximation thereof) for a specific work zone feature or strategy (lane closure, use of positive projection, etc.).

Stakeholder Need 5.3 – Assessing and Enhancing Performance at the National Level

5.3.1 – Developing National Work Zone Safety and Mobility Improvement Guidance

Guidelines for improving local, regional, and national safety and mobility performance.

The FHWA Work Zone Management Program may want to use local, regional, and national WZED to develop guidelines for improving local, regional, and national safety and mobility performance measures.

5.3.2 – Developing Reports of Regional and National Work Zone Safety and Mobility Performance

Reporting of regional and national safety and mobility performance.

FHWA and other USDOT agencies may want to compute regional and national safety and mobility performance measures for specific stationary work zone types, projects on certain roadway types, or other measures.



CATEGORY 6 – LAW ENFORCEMENT AND EMERGENCY SERVICE PROVIDERS

Stakeholder Need 6.1 – Validate Cited Conditions of Traffic Violation

6.1.1 – Worker Present in Work Zone Documentation

Agency documents and archives when workers are present in work zones to support contested citations.

Many states have laws that increase fines “when workers are present” or similar wording. Documentation that work activity was occurring at the time of the citation could be useful if citations are contested.

6.1.2 – Posted Speed Limits in Work Zones Documentation

Agency documents and archives posted speed limits in work zones to support contested citations.

Some agencies have established policies and procedures to change the posted speed limit during certain work events, and return them to the regular posted speed limit when those work events are not occurring. A few agencies are pursuing variable speed limit systems that tailor speed limits to specific traffic conditions and locations using electronic speed limit signs.

Stakeholder Need 6.2 – Enforcement of Lane Closure/Right-of-Way Access Approval Process

6.2.1 – Enforcement of Lane Closure/Right-of-Way Access Approval

Law enforcement verifies approval of lane closures they encounter.

Some agencies rely on enforcement personnel to help ensure that entities and companies do not implement lane closures or other work zones on their facilities without obtaining approval first.

Stakeholder Need 6.3 – Monitor and Document Law Enforcement Use on Projects

6.3.1 – Monitor Law Enforcement Use on Projects

Agency documents and archives when law enforcement used at work zones.

Agencies (particularly those with a memorandum of understanding [MOU] with law enforcement for work zone enforcement support) may want to keep track of when and where enforcement efforts occur.

6.3.2 – Law Enforcement Work Zone Effectiveness

Agency analysis of the effectiveness of law enforcement in work zones.

Agencies that use law enforcement on work zone projects may want to keep track of when and where enforcement efforts occur to evaluate effectiveness.



Stakeholder Need 6.4 – Facilitate Law Enforcement Work Zone Planning

6.4.1 – Facilitate Law Enforcement Work Zone Planning

Law enforcement monitoring upcoming work zones to help plan enforcement needs.

Law enforcement agencies may want information about upcoming work zones in a region so that they can better plan for law enforcement needs for those work zones.

Stakeholder Need 6.5 – Law Enforcement Monitor Activity at Work Site (to deter theft)

6.5.1 – Law Enforcement Monitor Activity at Work Site (to deter theft)

Law enforcement monitor activity at work site (to deter theft).

Law enforcement wants to know what contracts/subcontractors are working on each job to help them monitor who should and should not be on site. For example, general patrols that pass by worksites after hours want to be able to identify suspicious vehicles/events that do not belong (e.g., a different or bogus company truck used to steal copper wire).

Stakeholder Need 6.6 – Restricted Access to Incidents

6.6.1 – First Responder Emergency Route Planning

Inform first responders of work zones to enable advance emergency route planning.

Emergency service providers and law enforcement could find better routes to incidents or plan for incident response if they are aware of work zone locations that restrict normal access.

CATEGORY 7 – CAV HARDWARE NEEDS AND SYSTEM READINESS TO ACCOMODATE

Stakeholder Need 7.1 – Alert/Inform CAV of Presence of Work Zones

7.1.1 – Dissemination of Work Zone Driver Beginning and End to CAV

Dissemination of work zone, beginning and end advisory and warning data to CAV for display to driver. (Assumes driver will control CAV through work zone.)

Due to the dynamic nature of work zones, CAVs may initially use work zone data elements similar to those conveyed through traveler information systems (i.e., when, where, and what is different about the roadway) and require driver intervention.



Stakeholder Need 7.2 – CAV Navigation (information to plan and execute trip)

7.2.1 – CAV Route Navigation Selection

CAV systems and staff use work zone information to plan and recommend routes.

CAV systems and staff use WZED to plan and recommend routes to drivers through and around work zones to optimize CAV travel.

Stakeholder Need 7.3 – CAV Lane Guidance (safe speed and travel path guidance)

Use Case 7.3.1 – CAV Lane Guidance

CAV systems and staff use work zone information to plan and recommend travel lanes and path.

Public and private CAV systems and staff use WZED to plan and recommend lane-level advisories and warnings necessary to support their safe navigation through a work zone.


7.2.1. Prioritization and Incremental Implementation Of Use Cases As with stakeholder needs, the list of WZED use cases can help agencies consider their specific goals in the short- and long-term and provide a starting place for planning their implementation of WZED and WZDS. Each agency will not likely need to support all 50 use cases. Rather, they will likely have immediate priorities, among this list that they desire to pursue immediately and have other, medium- to long-term priorities that they will pursue when the priorities become more urgent, when benefits become apparent, and when resources become available.


8. CONCEPTUAL WZDS ARCHITECTURE FOR COLLECTING, STORING, USING, AND COMMUNICATING WZED

The previous chapters of this Framework illustrate the large number of agency stakeholders who need WZED for planning, design, construction operations, and performance assessment and who need to communicate their results to other stakeholders. Organizing WZED to support these many uses is challenging because of the large number of stakeholders and because their needs are wide ranging. While very basic communications between two or three stakeholders for one task, such as planning, may be straightforward for an agency to support, these communications become much more complex when agencies try to share data with more than just a few stakeholders for more than a single task. The entire process is further complicated if stakeholders each keep and maintain their own WZED database for each task, resulting in numerous redundant and potentially inconsistent descriptions of what is transpiring in a work zone.

This section of the Framework describes a conceptual WZDS architecture with a centralized WZED storage warehouse that supports consistent control and maintenance of WZED. The WZED warehouse is the hub in a hub-and-spoke communications architecture that supports simple stakeholder WZED communications as well as easy addition of new stakeholder interfaces, as agency WZED needs and uses grow. The conceptual architecture provides a graphical depiction of the WZED warehouse, WZDS tools for planning, design, construction operations, and performance assessment, and WZED communication interfaces needed to share WZED effectively and efficiently. The architecture was developed to provide agencies with a conceptual structure for clearly and consistently communicating WZED between internal and external data systems and across stakeholder groups throughout the work zone life cycle. As shown in later sections of the document, the architecture supports the WZED communication needs for all use cases described in this document. The conceptual architecture supports communication in both traditional agency workflows and in emerging agency functions, such as support for CAVs. Finally, the conceptual architecture supports growth and evolution of WZED communications over the long-term and can help avoid the need for major WZED warehouse and communication redesign and revision when new use cases must be supported.

The conceptual WZDS architecture provides a graphical depiction of the WZED warehouse, WZDS tools for planning, design, construction operations, and performance assessment, and WZED communication interfaces needed to share WZED effectively and efficiently.


8.1. SIMPLIFIED WZDS HUB-AND-SPOKE CONCEPTUAL ARCHITECTURE Figure 4 illustrates the basic concept of storing WZED in a “hub and spoke” architecture. WZED are stored and managed in a centralized data warehouse or series of databases. Work Zone events such as planning, design, construction management, and performance assessment are performed by a series of stakeholders with WZED processing tools interfaced to the warehouse. Each stakeholder and tool interfaces to the warehouse to obtain the WZED needed. The tool applies the WZED in its process (i.e. planning, design, construction management, or performance assessment) and then returns updated WZED to the warehouse for other stakeholders to view and process as needed. The WZED warehouse and the WZED processing tools interfaced to the warehouse comprise an agencies’ WZDS.

8.1.1. WZED Warehouse Enables Consistent Data Management and Maintenance When an agency first begins to store WZED digitally, it may be fairly easy for staff to manage a different spreadsheet or database for each work zone and/or each stage of the life cycle. However, as the electronic communication of WZED grows, storage of WZED across multiple redundant databases spread throughout an agency will rapidly become

Figure 4. Simplified Illustration of WZDS Hub-and-Spoke Conceptual Architecture


confusing, making it difficult to know which database has the most recent and correct version of the WZED. Decentralized storage of WZED will become more prone to error as the use of WZED grows in an agency.

The conceptual WZDS architecture highlights collection and control of WZED in a single data warehouse or collection of databases to reduce complexity and likelihood of errors. In the long run, centralized storage and management of agency WZED enables better WZED security, integrity, and consistency as well as improved operational efficiency and reduced costs.

8.1.2. Hub-and-Spoke Conceptual Architecture Simplifies WZED Communication In the hub-and-spoke conceptual architecture in Figure 4, all data communication interfaces are between the WZED warehouse and a stakeholder interface or stakeholder tool. There are no point-to-point communications between stakeholders. This strategy enables more consistent control and management of WZED. Each stakeholder has a single interface to the WZDS, rather that employing a separate interface to every other stakeholder.

This “hub and spoke” architectural model also supports simpler expansion and addition of stakeholders. Addition of a stakeholder, requires the addition of a single interface to the WZED warehouse, rather than adding a series of new interfaces for the new stakeholder to communicate with each of the other stakeholders.

8.1.3. WZED and Communications Partitioning by Life Cycle Stage While WZED are centralized, agencies may choose to partition WZED warehouse and WZDS stakeholder interfaces according to how WZED are accessed and used at each life cycle stage, as illustrated in Figure 4 and Table 7.

Table 6. Illustration of WZED and Communication Partitioning by Life Cycle Stage During this Life Cycle Stage: WZDS communicates this

type of WZED: With these groups of stakeholders:

Planning and Design

Planning/Design WZED

• Local and Regional Work Zone Planning and Design Staff

Construction Operations Active operational WZED • Construction, Maintenance, and Utility Work Zone Operations Staff

• TMC/ATMS/RCRS/ITS and Traveler Information Services

• Smart Work Zone and Connected and Automated Vehicle

Work Zone Performance Analysis

Planned and actual WZED archive

• Work Zone Inspection, Performance and Impact Analysis Staff


WZED attributes at each stage will reflect similar levels of WZED location and schedule accuracy, frequency of updates, and need for stakeholder access, as discussed in Section 4, WZED Life Cycle Stages – How WZED Evolves During Construction.

8.2. EXPANDED WZDS CONCEPTUAL ARCHITECTURE WITH WZED TOOLS AND INTERFACES

Figure 5 expands the hub-and-spoke architecture from Figure 4, detailing 17 unique data communication interfaces and tools for WZED communication and processing identified in development of the Framework and described further below.

The WZDI team analyzed the Use Cases summarized in Section 7.2, WZED Use Case Summary Descriptions, and described in APPENDIX A, Description of WZED Use Cases and Data Flows and assessed the potential data communications interface needs for WZDS stakeholders. The team identified 17 candidate WZDS interfaces, illustrated by the arrows in Figure 5, for stakeholders, their data systems, and their planning, design, and analysis tools. Again, these arrows are digital communications interface through which stakeholders enter, update, manage, and maintain the WZED. Each interface represents a different stakeholder type with unique needs for accessing and using WZED, and likely unique security access controls.


8.2.1. Data Communication Interfaces and WZED Processing Tools The term staff/tools in Figure 5 represents the spectrum of possible tools that may be used by agencies as they implement WZED now and as WZED use cases evolves in the future. The arrows between the WZED warehouse box and the tools represent data communications interface through which the stakeholders enter and retrieve WZED from the warehouse. As one potential example, construction operations staff may have a web page interface in which they may directly view, update, manage, and maintain agency WZED daily during construction. As another example, planning and design staff may have computer aided design systems which have a digital interface to the WZED warehouse that automatically uploads planning and design WZED after each major update. The Agency Smart Work Zone Interface and the Agency Connected and Automated Vehicles Interface boxes represent specialized

Within the WZDS, the term “Staff/Tools” represents the spectrum of manual or automated tools used to implement WZED now and in the future.

Figure 5. Expanded Illustration of WZDS Conceptual Architecture with WZED Tools and Interfaces.


interfaces which translate data from these other systems and verify their integrity and their consistency with existing WZED before uploading new information from these smart systems. In the case of Work Zone Performance, analysts may have data systems which obtain planned and actual WZED archives from the WZED warehouse and integrate it with data from traffic, weather and other systems and perform assessments on work zone impacts.

Some arrows are one way outward, indicating WZED is sent to stakeholder entities, but those entities do not have access to enter or revise WZED. Two way arrows represent those entities that both use and modify WZED over the course of the life cycle.

8.2.2. Prioritization and Incremental Implementation Of WZED Warehouse Interfaces

It is important to reiterate that agencies do not need to implement all interfaces in the WZED warehouse. Initially, one or two may be sufficient to support the agencies initial stakeholder use cases, and then add new interfaces as the needs arise. The key is for agencies to keep this interface “big picture” in mind in the initial architecting of their WZDS so that it can expand to support evolving needs as WZED communications gain in importance and grow.

8.2.3. WZED Processing Tools Also Use Data From Other Sources Figure 5 illustrates tools that interface directly to the WZED warehouse. Many of these tools will require external information, in addition to WZED, to perform their processing tasks. This concept is illustrated in Figure 6, which provides a more detailed view of the agency planning and design interface (Interface 1).

Figure 6. Illustration of Work Zone Planning and Design integrating WZED and Data from Other Sources


It is expected that initially, agency planning and design staff will have a direct interface into the WZED warehouse for viewing, entering, updating, managing, and maintaining agency planning and design WZED. These staff will be responsible for ensuring this information is up-to-date throughout this life cycle stage. As WZDS evolve, the agency may choose to interface construction planning and design software programs directly to the warehouse to update planning and design WZED automatically, when plans and designs are updated.

Figure 6 illustrates that the planning and design processes, whether manual or digital, will access and use data from other sources. For example, when planning and designing work zones and TTC, agency staff are expected to review the traffic and crash performance in past work zones. They use past performance to estimate the impacts of work zones and selected TMP on future work zones. These processes are illustrated in Figure 6 by the dotted lines from Traffic and Crash Performance/Impact Analysis Staff/Tools to the Agency Work Zone Planning and Design Staff/Tools box. As will be shown later in Section 8.4.5, Performance Analysis Tools and Interfaces, the traffic and crash performance/impact analysis is derived from the WZED archive along with traffic and crash data from other sources.

Figure 6 illustrates that agency planning staff will consult with neighbor agency staff. A major feature of the conceptual WZDS architecture is support for coordination with neighbor agencies of schedule, lane closures, TTC, and other work zone events throughout work zone planning, design, and operations. This enables the agency and its neighbor agencies to analyze plans and identify and avoid potential bottlenecks and conflicts. These work zone coordination events are performed by staff and tools and occur “outside” the WZED warehouse. WZED updates are performed by agency planning and design staff.

8.3. COMPREHENSIVE VIEW OF THE WZDS CONCEPTUAL ARCHITECTURE Figure 7 provides a comprehensive view of the WZDS conceptual architecture, showing all WZED warehouse and tool interfaces in a single diagram for reference purposes. While this perspective of the WZDS architecture appears rather daunting in size and scope, agencies will not need to implement the entire structure as shown, nor implement all the interfaces in their first implementation. However, keeping this broad perspective in mind during their initial implementation will ensure that future enhancements can more easily support broader, long-term needs.

Often analysis will require WZED and non-WZED from both the WZED warehouse and other external resources.


Figure 7. Comprehensive view of WZDS Conceptual Architecture


8.4. EXPLORING DETAILS OF EACH OF THE WZDS TOOLS AND INTERFACES The following sections take a deeper dive into the comprehensive WZDS by describing the events and interfaces within the WZDS during each stage of the WZED life cycle. Within each section, diagrams are provided for clarity. In these diagrams the following shapes and arrows are used to illustrate the staff, tools, and interfaces present.

Light colored boxes represent staff/tools owned and maintained by the agency

White colored boxes represent staff/tools owned and maintained by others

Dark colored arrows represent interfaces directly with agency WZED warehouse, through which WZED flow. Two-way arrows represent both read and write access to WZED in the warehouse. Depending upon the agency and stakeholder, arrows may represent:

• Direct staff interfaces to the WZED warehouse, allowing authorized agency staff to enter, edit, manage, and maintain WZED in the WZDS

• System-to-system digital interfaces defined by industry standards such as NTCIP, IEEE, or SAE standards (such as in the case of third-party traveler information systems and CAV systems)

Dark colored one-way arrows represent read-only access to the WZED warehouse for agency and non-agency stakeholders

Light colored arrows represent interfaces with other entities outside the WZED warehouse

Dotted line arrows represent use of past performance data for predicting future performance and impact

White circles with numbers are reference numbers that uniquely identify each interface between the WZED warehouse and stakeholders and their tools.

The nature of each interface will depend upon the specific needs of the agency. Although the WZDS design is expected to vary by agency, WZED definitions are intended to be standardized to enable the communications summarized in Figure 7.

8.4.1. Planning and Design Stage This section describes the work zone events, data use, and interfaces occurring in the WZDS during the planning and design stage. This information is graphically illustrated in Figure 8.

WZDS interfaces are expected to vary by agency; however, the WZED is intended to be standard across organizations.


Figure 8. Work Zone Planning and Design WZDS Tools and Interfaces

8.4.1.1 Work Zone Events

Agency planning staff determine when and where construction events will take place. During that process general plans for work zone events are developed, including type of work zone, lane closures, and beginning and end locations and times.

During the roadway construction design process, agency design and engineering stakeholders develop detailed engineering specifications for work zones. Work zone designers write agency performance specifications and are involved with the development or review of work zone traffic management plans (TMPs). These stakeholders are also responsible for establishing the contractor performance monitoring plans by which contractors will be evaluated and potentially incentivized or penalized. These plans are documented in both requests for proposals and, ultimately, the construction and maintenance contracts.

Strategic coordination of work zones takes place during the planning and design life cycle stage, identifying overlaps and or conflicts in work zone location and time. The agency coordinates the schedules and events of its own work zones to ensure traffic flow is maintained. The agency will also coordinate with its peers at neighbor agencies and regional planning entities to maintain traffic flow and minimize impacts on multi-agency highways and corridors within its jurisdiction.


8.4.1.2 WZED and WZDS Uses

During planning and design, staff will use the WZED warehouse as the key repository for managing, maintaining, and communicating the planning of WZED and updates to users and stakeholders as plans evolve. Internal and external stakeholders can obtain the latest work zone planning information at any time from the warehouse.

Agency planning and design staff will be responsible for entering and maintaining up-to-date work zone WZED in the warehouse during the planning and design life cycle stage.

8.4.1.3 WZED Warehouse Interfaces

Three primary stakeholder groups participate in the work zone planning and design life cycle stage and corresponding interface to the WZDS:

• Interface 1: Agency Work Zone Planning and Design Staff/Tools • Interface 2: Neighbor Agency Work Zone Planning and Design Staff/Tools • Interface 3: Regional Work Zone Planning Staff/Tools

Interface 1: Agency Work Zone Planning and Design Staff/Tools

The primary WZED warehouse interface during this life cycle stage is Interface 1: Agency Work Zone Planning and Design Staff/Tools, as shown in Figure 8.. Agency planning and design staff will have a direct interface for direct viewing, entering, updating, managing, and maintaining agency planning and design WZED. They will be responsible for ensuring this information is up-to-date throughout this life cycle stage. Other agency staff can access the latest schedule, plans, and design information from the WZDS.

When planning and designing work zones and TTC, agency staff review the traffic and crash performance in past work zones. They use past performance to estimate the impacts of work zones and selected TMP on future work zones. These processes are illustrated in Figure 8 by the dotted lines from Traffic and Crash Performance/Impact Analysis Staff/Tools to the Agency Work Zone Planning and Design Staff/Tools box. As will be shown later in Section 8.4.5, Performance Analysis Tools and Interfaces, the traffic and crash performance/impact analysis is derived from the WZED archive along with traffic and crash data from other sources.

During the planning stage, the WZED warehouse is used for managing, maintaining, and communicating planned WZED and corresponding updates.


Interface 2: Neighborhood Agency Work Zone Planning and Design Staff/Tools

To support coordination, neighbor agency planning and design staff may have read-only interfaces to the agency WZED warehouse to obtain the latest agency planning and design schedules for use in coordinating events to minimize impacts on traffic flow along multi-agency corridors and highways. Similarly, the agency may have access to the WZED warehouse of its neighbor agencies.

Interface 3: Regional Work Zone Planning and Design Staff/Tools

Regional work zone coordination staff are responsible for coordination of construction and maintenance work zone lane closures and traffic restrictions spanning multiple agency jurisdictions during work zone planning, design, and operations life cycle stages. This function may be performed by peers at adjoining agencies, by Metropolitan Planning Organizations (MPOs), or by regional and state agencies. These stakeholders may also have read-only interfaces to the agency WZED warehouse to obtain the latest agency planning and design schedules for use in coordinating events. These stakeholders will collect and integrate construction and maintenance work zone lane closure and traffic restriction WZED from multiple agencies and work with agencies to maintain traffic flow and minimize congestion on contiguous roadways and regional networks. They will be responsible for collecting and integrating up-to-date schedule and lane closure WZED during the planning, design, and operations life cycle stages.

8.4.2. Construction Operations – Active Construction and Maintenance Events This section describes the interfaces needed to support communication of WZED construction and maintenance operations events. This information is graphically illustrated in Figure 9.


Figure 9. Construction Operations WZED Warehouse Tools and Interfaces for Construction and Maintenance Events


During active operations, work zones are fully operational and dynamic, changing as needed to support construction and maintenance events and to protect on-site workers.

Agency construction operations and contractor staff:

• Monitor day-to-day impacts on affected traffic and safety and adjust work zone events as needed

• Coordinate work zone events with other internal agency staff, with neighbor agencies, and with utility work zones to maintain traffic flow and minimize traffic delay as much as possible

Agency staff supporting maintenance work zone operations:

• Manage short-term and mobile work zones during roadway maintenance • Coordinate their maintenance and work zone events with roadway construction and

other roadway operations.


During operations, WZED are expected to change frequently, perhaps daily, and even throughout a day. Stakeholders need accurate and up-to-date WZED during construction operations to ensure mobility and safety in the work zone and affected areas. During agency construction and maintenance operations, operations and contractor staff actively update and maintain WZED to

During this phase, accurate and up-to-date WZED is needed to ensure mobility and safety in and around work zones.


communicate to travelers and other agency systems and staff current work zone events and status. WZED updates may be used to alert agency and neighbor agency stakeholders of potential imminent bottlenecks and conflicts that require immediate engagement and coordination. Utility work zone events must also be examined to identify potential conflicts or opportunities for coordination efficiencies. WZED updates may also inform work zone inspectors and contractor performance monitors of contract compliance issues.


Six WZDS interfaces are included in this stage for managing, maintaining, and coordinating work zone events:

• Interface 4: Agency Construction Work Zone Operations Staff/Tools • Interface 5: Agency Maintenance Work Zone Operations Staff/Tools • Interface 6: Contractor Work Zone Operations Staff/Tools • Interface 7: Neighbor Agency Work Zone Operations Staff/Tools • Interface 8: Agency-to-Utilities Work Zone Coordination Staff/Tools • Interface 9: Agency-to-Law Enforcement Work Zone Coordination Staff/Tools

Interface 4: Agency Construction Work Zone Operations Staff/Tools

During this life cycle stage, agency construction work zone operations staff will have an interface for direct viewing, entering, updating, managing and maintaining agency operations WZED. They will be responsible for ensuring this information is up-to-date throughout this life cycle stage. Other agency staff can access the latest schedule, plans, and operations information from the warehouse. These agency stakeholders will review WZED to monitor work zone day-to-day traffic data and traffic impacts and identify and implement changes that may be needed to improve performance and reduce mobility impacts, such as adjusted construction times or schedules or to calibrate ITS devices.

Agency construction work zone operations staff may also have a read-only interface to neighbor WZED warehouse to obtain the latest neighbor agency work zone operations schedules for use in coordinating events to minimize impacts on traffic flow along multi-agency corridors and highways.


Interface 5: Agency Maintenance Work Zone Operations Staff/Tools

During this life cycle stage, agency maintenance work zone operations staff will also have a direct interface for direct viewing, entering, updating, managing and maintaining agency operations WZED. They will be responsible for entering and maintaining up-to-date WZED pertaining to maintenance planning, and maintenance operations.

Interface 6: Contractor Work Zone Operations Staff/Tools

Construction contractors perform the work events in a work zone, but, depending on the contracting mechanism employed, may also be involved with proposing or developing work zone TMPs and installing ITS devices to help manage impacts to traffic. Contractors have an interface for viewing the latest WZED entered by agency construction and maintenance operations staff. When authorized, contractors may also have direct interface for direct viewing, entering, updating, managing and maintaining agency operations WZED. These stakeholders may collaborate with agency construction operations manager and inspector staff in frequently entering up-to-date actual WZED into the WZED warehouse and maintaining that data for their ongoing use and for reporting to other stakeholders. These staff will monitor WZED to identify and implement changes that may be needed to improve their own (contractor) performance and comply with contractual performance specifications.

Interface 7: Neighbor Agency Construction Work Zone Operations Staff/Tools

Neighbor agency staff will have the same responsibilities, in their own jurisdiction, as agency construction work zone operations management. To support coordination, neighbor agency work zone operations staff/tools may have a read-only interface to the agency


WZED warehouse to obtain the latest agency operations schedules for use in coordinating events to minimize impacts on traffic flow along multi-agency corridors and highways.

Interface 8: Agency-to-Utilities Work Zone Coordination Staff/Tools

Utilities may need to perform construction or maintenance events that impact roadways and roadway operations either directly, such as burial under roadways, or indirectly, when utility construction or maintenance requires a lane closure. WZED describing utility work zones are expected to be managed by agency staff responsible for coordinating with utilities. These agency staff will have an interface to the WZED warehouse that supports direct viewing, entering, updating, managing and maintaining utility operations WZED (as opposed to agency operations WZED) to support the ongoing tactical coordination of work zones. These staff will enter, manage and maintain up-to-date WZED relevant to utility work impacting roadways.

Interface 9: Agency-to-Law Enforcement Work Zone Coordination Staff/Tools

Law enforcement personnel will require information about upcoming events to plan traffic management, staffing, and law enforcement events related to work zones. Staff responsible for coordinating law enforcement support at work zones may have an interface to the agency WZED warehouse to obtain the latest agency operations schedules for use in coordinating law enforcement events.

8.4.3. Construction Operations – Traveler Information This section describes the interfaces needed to support communication of WZED output for travelers and other real-time traffic mobility and safety information users. These interfaces are graphically illustrated in Figure 10.


Figure 10. Construction Operations WZED Warehouse Interfaces for Traveler Information Dissemination


One of the primary beneficiaries of the implementation of WZED and WZDS will be the traveling public. In Figure 10 the “active operational” WZED represents output to travelers and other real-time traffic mobility and safety information users. Agency traffic management staff will use the data to update traffic management strategies and update ITS with the latest information for travelers. Travelers and the public will use up-to-date information to adjust travel plans and to safely traverse work zones.


A driving force for implementing WZED and WZDS is communication of up-to-date WZED to agency traffic management staff, travelers, and the public in real-time. Raw WZED will be output to different agency systems such as TMC, Advanced Traffic Management System (ATMS), Road Condition Reporting System (RCRS), ITS, and traveler information and message systems, which will integrate it with other relevant data and deliver traffic information to agency and traveler devices in traveler useable format.


Although there may be multiple physical interfaces, this broad category is represented architecturally by a single interface:

• Interface 10: Agency TMC/ATMS/RCRS/ITS Traveler Information and Message Systems,


Interface 10: Agency TMC/ATMS/RCRS/ITS Traveler Information and Message Systems

This interface represents a digital interface that outputs active operational WZED to agency digital systems, which include:

• Advanced Traffic Management System. ATMS and staff are responsible for controlling the various TMC systems used to manage traffic. These stakeholders will use WZED to increase roadway network mobility situational awareness and to take actions in real-time to minimize the impact of work zones, lane closures, and traffic congestion.

• Intelligent Transportation/Dynamic Message Signs/Traveler Information Systems. These systems and staff inform travelers about events impacting traffic, including work zones and temporary lane closures. This function will include dissemination of relevant WZED to third-party traveler information systems and to specific classes of travelers, such as freight haulers.

• Road Condition Reporting System (RCRS). The central clearinghouse of information behind the traveler information system is often an RCRS, although this varies by agency. An RCRS typically fuses data and information from various sources, providing one comprehensive source to feed a number of information dissemination mechanisms. An RCRS can include both planned and active work zone or maintenance events and closures. ATMS and traveler information systems generally interface with the RCRS.

The Agency TMC/ATMS/RCRS/ITS Traveler Information and Message Systems deliver relevant work zone information to a range of users including travelers, freight haulers, third-party traveler information systems, first responder emergency route planners, and oversize/overweight truck route permitting.

• Travelers. Travelers include the traveling public at large, as well as other specific consumers of WZED-generated information. While they will not interface directly with the WZED warehouse, they will receive WZED information provided by agency and third-party traveler information systems. They will use this information to plan their routes and in real-time to safely navigate work zones.


• Freight Haulers. Commercial vehicle freight haulers are some of the heaviest users of regional and national highway networks. Work zone congestion can slow the delivery of goods. Also, commercial vehicles contribute to traffic slowdowns and congestion in work zones. Freight hauler companies and individual commercial vehicle drivers can use reliable WZED information from agency traveler information systems to better plan their routes to reduce the impact on freight delivery and, at the same time, reduce congestion and traffic delays in work zones.

• Third-Party Traveler Information Providers. Private sector information service providers collect and communicate traffic information using their own systems. These stakeholders will collect and use WZED provided by agency traveler information systems to enhance the work zone travel information they provide to their customer base.

• First Responder Emergency Route Planners. When crashes and other traffic-blocking events occur in and near work zones, it is imperative that first responders have up-to-date information on work zone events to enable rapid access and support rerouting of traffic as necessary. First responder staff responsible for routing can use reliable WZED information from agency traveler information systems to best plan their routes through and around work zones to reach crash sites and those needing emergency assistance.

• Agency Oversize/Overweight Permitting Functions. These agency stakeholders are responsible for routing oversize and overweight trucks across the agency jurisdiction. In most cases, these vehicles would be routed around work zones. These agency stakeholders work with construction operations and maintenance work zone schedules to identify continuous routes around work zones with adequate capacity to support the payload and travel requirements of oversize and overweight vehicles.

8.4.4. Construction Operations – WZED Two-Way Interfaces with Smarter Work Zones and CAVs

This section describes the interfaces needed to support the exchange of WZED information with smart work zones and CAVs. This information is graphically illustrated in Figure 11.


Figure 11. Active Operations WZED Warehouse Interfaces for Smart Work Zones and CAVs


Implementing standardized WZED and a WZED warehouse will enable agencies to provide up-to-date work zone information to smart work zones and to CAVs. Importantly, these systems can return updated information on work zone performance back to the WZED warehouse in real-time, supporting better and faster delivery of information to agency and contractor staff, as well as to travelers.


As illustrated in Figure 11, the agency WZED warehouse will have interface systems that translate raw WZED into wireless data streams and messages useable by smart work zones and CAVs. These interface systems will verify work zone information from smart work zones and CAVs, and then translate them into WZED and enter them into the WZED warehouse for use by other users. These interfaces must also ensure the cybersecurity of such interactions.


Two interfaces illustrate these communications:

• Interface 11: Agency Smart Work Zone • Interface 12: Agency CAV


Interface 11: Agency Smart Work Zone

Smart work zone systems have been in development that are designed to predict travel time, delays, or speed in a work zone, on a real-time basis. These systems are intended to better inform motorists, encourage them to take alternate routes, reduce their frustrations, reduce freeway congestion, and enhance safety for motorists and workers. These systems can be used to provide real-time information to motorists during incidents, temporary closures, or any unexpected conditions on the freeway.(10)

Interface 12: Agency CAV

CAVs are both users and providers of work zone information. Anticipating the deployment of infrastructure-to-vehicle communications, the vehicles themselves will have onboard computer systems that can ingest work zone information from agency interface systems and use them to issue relevant work zone speed and lane closure advisories and alerts to vehicle drivers. In return, the basic safety messages they broadcast can be used by agency systems to assess traffic flow and other real-time work zone status information.

8.4.5. Performance Analysis Tools and Interfaces This section describes the interfaces needed for performance analysis, that will typically use archived WZED. Planned and actual archived WZED represents output to work zone performance and impact analysis users, including traffic impact, crash impact, contractor performance and compliance, law enforcement impact, and state and federal performance analysis. This information is graphically illustrated in Figure 12.


Figure 12. Planned and Actual WZED Archive Interfaces for Post Work Zone Analysis


For the purposes of this framework, performance analysis is defined as analysis conducted during and after construction and maintenance to understand actual safety and mobility performance after the fact. Impact analysis is conducted during planning and design, using past performance, to predict the likely impacts of planned future work zones, and perform trade-off comparisons to select the most suitable work zone design strategy.

Capturing and archiving WZED will enable agencies and regional and national stakeholders to conduct more detailed and comprehensive assessments of work zone mobility and safety performance. Better work zone performance assessments will enable more accurate prediction of future work zone impacts on traffic and safety, thereby improving work zone design and future performance.

Archived WZED includes the results of inspection of contractor work zone events to monitor contractor performance and compliance with contractual requirements.


Planned and actual WZED and contractor inspection results are archived throughout the planning, design, and operational life cycle stages of agencies work zones. Agencies separately capture traffic and safety performance data on their roads and highways. Correlation of WZED with traffic and safety data enables the agencies to perform work zone performance and pre-work zone impact analyses.



Five WZED Warehouse interfaces are shown in the conceptual architecture to illustrate work zone performance analyses:

• Interface 13: Law Enforcement Performance Analysis Staff/Tools • Interface 14: State and Federal Performance Analysis Staff/Tools • Interface 15: Agency Work Zone Inspection and Performance Monitoring • Interface 16: Crash Performance/Impact Analysis Staff/Tools • Interface 17: Traffic Performance/Impact Analysis Staff/Tools

Interface 13: Law Enforcement Performance Analysis Staff/Tools

Law enforcement officers may periodically operate in or near work zones to slow traffic and enhance worker safety by their presence and by issuing citations. Agency staff may assess the effects of these law enforcement efforts to help guide current and future requests for law enforcement support and coordination. These assessments rely on planned and actual WZED archive data integrated with law enforcement resources identifying when law enforcement was present and when citations were issued.

Interface 14: State and Federal Performance Analysis Staff/Tools

Implementation of standardized WZED will support the desire by state and federal transportation agencies to collect and analyze planned and actual WZED archives and relevant safety and mobility data for use in regional, state, and national performance assessments and in developing guidelines for improving safety and mobility in and around work zones.


Interface 15: Agency Work Zone Inspection and Performance Monitoring

Agency construction operations staff may inspect work zones and compare planned and actual WZED to assess and track contractor performance and contract compliance. Staff responsible for monitoring contractor performance and compliance may have an interface that meets their needs for monitoring agency work zone events. This will include entering and assessing results of work zone inspections as well as monitoring planned and actual WZED entered by agency work zone construction operations staff and contractors.

Agencies may choose to offer incentives for improvements in traffic mobility or crash safety performance during work zone operations, and/or penalties for worsening performance. Staff responsible for monitoring contractor performance and compliance may obtain traffic and crash safety performance data from agency performance analysis staff to assess contractor achievement.

Interface 16: Crash Performance/Impact Analysis Staff/Tools

Standardized WZED will enhance an agency’s ability to assess the crash safety performance on its roads and highways and apply what it learns to improve future work zone safety. Agency performance analysis staff conduct analyses and reviews of available historical crash data, including WZED, and apply the results to improving safety and developing performance measures. These stakeholders integrate safety data with WZED to assess the safety impacts of work zones. These stakeholders may assist in the development of work zone TTC and performance requirements that might be applied to work zones to improve safety in the future. For example, crash data from other sources are compared with work zone geometry to assess safety of different work zone designs. While agencies may assess the safety of specific work zone designs under their


jurisdictions, their WZED may be integrated with WZED from other agencies to provide broader regional and national assessments of safety of specific work zone designs.

Interfaces 17: Traffic Performance/Impact Analysis Staff/Tools

Similar to crash safety performance, standardized WZED will enhance an agency’s ability to assess the traffic mobility performance on its roads and highways and apply what it learns to improve future work zone mobility. Agency performance analysis staff conduct analyses and reviews of available historical traffic and congestion data, including WZED, and apply the results to minimizing congestion and developing performance measures. These stakeholders integrate mobility data with WZED to assess the mobility impacts of work zones. These stakeholders may assist in the development of work zone TTC and performance requirements that might be applied to work zones to minimize congestion in the future. For example, mobility analyses compare upstream traffic flows against work zone lane closures to assess the impacts of the closure on mobility. While agencies may assess the mobility of specific work zone designs under their jurisdictions, their WZED may be integrated with WZED from other agencies to provide broader regional and national assessments of safety and mobility of specific work zone designs.


9. AGENCY POLICIES AND CONSTRAINTS AFFECTING IMPLEMENTATION OF WZED AND WZDS

Agencies have a wide variety of operational policies and constraints that could impact the implementation of the proposed WZED and WZDS. Those policies and constraints listed below generally illustrate the anticipated environment for implementing standardized WZED.

9.1. OPERATIONAL POLICIES

• TSMO-Centric Organizational Structure.(9) Because of the nature of the proposed WZDS, a TSMO-centric organizational structure for transportation agencies is desired. TSMO can help orient an agency toward a common goal by placing work zone stakeholders of the various work zone life cycle stages into a common group or organization with common goals. This would facilitate the communication of data and information, as well as collaboration in the collection of WZED and dedication of resources to develop a common WZED warehouse to house WZED in an efficient manner.

• Work Zone Safety and Mobility Rule. The federal Work Zone Safety and Mobility Rule requires agencies to collect work zone data for the development of performance measures.(8) The Rule can provide an impetus for agencies to expand the collection of WZED.

• Local, Regional, State, and National Policies. A wide variety of national, state, regional, and local policies influence how WZED are collected and used. These policies may require modification as the proposed WZED approach and WZDS are developed and implemented in order to facilitate and clarify the business processes, roles, and responsibilities for collecting, storing, using, and communicating WZED.

• Internal Agency Practices. Policies for WZED should address internal and external agency stakeholders and concerns related to user access and administration; data quality, accuracy, and integrity; and security in order to develop trust and confidence in the developed system. These new policies should be incorporated into existing construction manuals, agency procedures, and procurement documentation wherever possible to facilitate adoption and consistent implementation of the WZDS. Procurement documents may have to specify what WZED will be collected and input by the contractor, and how it may be used in contract monitoring, for example. These policies should create business processes for WZED collection, use, and management to facilitate institutionalization.

• Data Systems Development and Operations Support. Agencies will require data systems staff support for developing, implementing, operating, and maintaining the WZED warehouse, which stores and shares WZED during all stages of the work zone

Factors influencing implementation may include: • Organizational structure • Local, Regional, State, and

National Policies • Internal and external

stakeholder practices • Staff training and education • Level of available resources • Agency champions • Agency culture


life cycle. This function may vary widely, depending on the warehouse implementation model selected by the agency. This may be a single internal information systems organization responsible for a centralized warehouse. It could also be distributed throughout the agency with different agency stakeholders responsible for operating, maintaining, and communicating different life cycle data components of WZED. For example, construction WZED may be managed by a separate group from maintenance WZED.

• External Stakeholder Practices. Separate policies may be considered by external stakeholders, including law enforcement entities who are also expected to interface with the WZED warehouse, to input and use WZED, and for proper use within private vehicles. These policies should be compatible with existing national policies.

• Existing Agency Processes. Deployment of the proposed WZED should be done in a way that is compatible with and complementary to existing agency processes. For example, there may be limitations on the collection of law enforcement citations, or restrictions on communicating this data with some personnel. The WZED warehouse should be developed with security protocols and user access restrictions in place to protect WZED that may require additional permissions or not be required for various stakeholders.

• Staff Training. Policies and procedures should be considered for training new and existing staff on proper collection, storage, and use of the WZED, as well as on access and security protocols for the WZED warehouse. These policies and procedures may consist of training for all existing staff, plus training sessions for all new hires and recurring refresher courses for existing staff. An online training course may be developed for use by external stakeholders including contractor, utility, and law enforcement staff who are expected or required to use the WZED warehouse.

9.2. CONSTRAINTS

• Available Resources. There are financial and resource constraints related to the purchase and implementation of a comprehensive WZED warehouse that can collect, process, and communicate WZED. Funding and leadership support are needed to implement a WZED warehouse, and re-orient an agency to a TSMO-based approach that simplifies stakeholder collaboration across all work zone life cycle stages.

• Champions. Strong internal champions will be needed to help secure the funding and support necessary to develop the WZED warehouse. Champions provide stakeholders with a clear mandate to develop the WZED warehouse and will also help to ensure appropriate staffing and resources are allocated to support the ongoing collection and management of WZED. While a strong business case and vision will be needed to justify the upfront investment, clear and measured benefits can provide justification for ongoing dedicated resources.

• Agency Culture. Agency culture could be a major constraint for successfully implementing the proposed WZED warehouse given the risk of general resistance to change among internal and external stakeholders. Stakeholders need to understand not only how the WZED warehouse works, but the benefits and reasons to adapt their current processes and take the time to conduct these events. Internal and external stakeholders are already tasked with a variety of responsibilities and there may be


resistance to adding new tasks that are viewed as secondary, instead of complementary. The time required to comprehensively collect WZED and enter it into the WZED warehouse will be significant. Agency management will therefore need to make a strong case, and provide support and additional resources, to encourage widespread adoption and use of WZED, as well as ongoing operations and maintenance of the WZED warehouse. Strong relationships and collaboration will be needed to encourage adoption by external stakeholders such as utilities and law enforcement.

• Future Needs and Technologies. A constraint with the proposed WZED is predicated in uncertainty over future needs and technologies. The CAV environment, technology advances, and even availability of predictive data, for example, may enable or require additional WZED that are currently not possible. The WZED warehouse must therefore be developed so it can be expanded to accommodate future WZED needs.

9.3. IT SUPPORT ENVIRONMENT AND TSMO The nature of the WZED warehouse and WZDS and its support environment is expected to vary from agency to agency depending on the deployed WZDS implementation model. For example, a single internal information systems organization could be responsible for a centralized WZED warehouse within a TSMO-oriented agency, or these functions could be distributed throughout the agency with different agency stakeholders responsible for operating, maintaining, and communicating different data components of WZED. While this latter approach is doable and resembles the disparate nature of most WZED that are collected today, the result is likely to be a less cohesive and comprehensive WZED warehouse. It would increase the potential for differing stakeholder priorities and challenges with identifying funding, gaining consensus, and identifying an agency champion across multiple groups.

Alternatively, some agencies are organizing around a TSMO framework to remove the barriers that silo various functions within an agency, including work zones. This support environment would best support a comprehensive database with WZED across all 7 use categories (see Section 6, Stakeholder WZED Needs – Uses for WZED. A collaborative environment would allow a common owner within the agency to secure funding and staffing for the development and maintenance of a WZED warehouse that facilitates stakeholder access to WZED throughout all work zone life cycle stages. An agency with a TSMO-centric organizational structure will also support interfaces to a variety of external systems, particularly those supported by groups outside of the work zone enterprise.

Source. TTI


APPENDIX A. DESCRIPTION OF WZED USE CASES AND DATA FLOWS

INTRODUCTION TO THIS APPENDIX This section of the Framework document provides more detailed resource and reference material for agencies considering implementing standardized WZED and WZDS. A key purpose of the use cases detailed here is to provide practical illustrations to agency stakeholders of how to use WZED to improve their day-to-day work zone operations, as well as to improve mobility and safety.

This appendix provides a description of the data flows across these WZED warehouse interfaces and the Use Cases. It provides a more detailed description of the WZED Use Cases, summarized earlier in Section 7.2, WZED Use Case Summary Descriptions . There are a total of 50 Use Cases identified in this document. More detailed technical description of the WZED itself is provided in the Data Dictionary Report.(1)

Use Case Structure The use cases are organized by the use case categories and stakeholder need subcategories described in Chapter 6, Stakeholder WZED Needs – Uses for WZED. Table 5 describes the information provided for each use case.

Table 7. Use Case Component Details Component Description

Category Use categories, described in Chapter 6, Stakeholder WZED Needs – Applications for WZED, used to group and categorize use cases.

Stakeholder Need Subcategories, corresponding to user needs in Chapter 6, Stakeholder WZED Needs – Applications for WZED, used to further sort use cases by user needs.

Use Case Number and Title Reference number and brief descriptive title.

Work Zone Life Cycle Stage

Life cycle stage, described in Chapter 4, WZED Life Cycle – How WZED Evolves During Construction during which this use case occurs.

Use Case Description Summary description of stakeholder usage of WZED. Use Case Examples Example of stakeholder usage of WZED in the particular use case. WZED User(s) Stakeholder or user that obtains and applies the WZED.

WZED Flow Illustration Graphic, corresponding to the conceptual architecture described in Section 8.3, Comprehensive View of the WZDS Conceptual Architecture, of the flow of WZED between WZED warehouse and stakeholders and users.

WZED User Objective Purpose or objective of WZED user application of WZED. WZED Content Candidate WZED elements communicated and used in the use case. WZED Content Update Frequency

Frequency that WZED changes and is updated in the WZED warehouse for the use case.

External Data Needed for User Objective

Complementary data to which WZED is correlated to achieve the user objective (e.g., WZED are correlated with external traffic data to assess work zone traffic congestion performance).


Table 7. Use Case Component Details

WZED Warehouse Interface Type

Type of interface through which the WZED user inputs and outputs WZED from the WZED warehouse. This is typically through agency staff interface for direct viewing, updating, managing, and maintaining agency WZED, or through system-to-system digital interfaces.

WZED WAREHOUSE INTERFACES AND WZED DATA FLOWS The Use Cases describe the flow of WZED to and from the WZED warehouse, across the interfaces shown in Figure 13 (repeat of Figure 7). Table 8 provides a description of the WZED flows across these warehouse interfaces, for reference by the reader and agency staff considering implementation of a WZED warehouse. The table summarizes:

• Interface Number • Staff, Tool or Component Interfacing to WZED warehouse • Type of Interface • Type of WZED Sent from WZED warehouse to Staff, Tools, or Component • Type of WZED sent by Staff, Tools, or Component to WZED warehouse, where

applicable • Applicable Use Cases


Figure 13. Comprehensive View of the WZDS Conceptual Architecture


Table 8. WZED Warehouse Interfaces and WZED Data Flows

Interface No

Staff, Tools, or Component

Interfacing to WZED Warehouse

Type of Interface

Type of WZED Sent from Warehouse to


Type of WZED sent by Staff, Tools, or

Component to Warehouse

Applicable Use Case(s)

1 Agency WZ Planning & Design Staff/Tools

Internal WZED warehouse agency staff interface for direct viewing, updating, managing and maintaining agency Planning and Design WZED.

Agency Planning and Design WZED

Planning and Design WZED Updates

1.1.1, 1.1.2, 1.2.1, 1.2.2, 2.1.1, 2.1.2, 2.1.3, 2.2.1, 2.2.2, 3.3.1, 3.4.1, 3.4.2, 5.1.1, 5.1.2

2 Neighbor Agency WZ Planning & Design Staff/Tools

External Interface to Export Planning and Design WZED to Other Agencies.

Agency Planning and Design WZED

NA 1.2.1, 1.2.2, 1.3.2

3 Regional WZ Planning & Design Staff/Tools

External Interface to Export Planning and Design WZED to Regional Entities.

Agency Planning WZED NA 1.3.2, 2.2.1, 2.2.2

4 Agency Construction WZ Operations Staff/Tools

Internal WZED warehouse Agency staff interface for direct viewing, updating, managing and maintaining agency Active Operational WZED.

Active Operational WZED

Active Operational WZED Updates

1.3.1, 1.3.2, 1.4.1, 1.4.3, 1.5.1, 1.5.2, 1.6.1, 3.1.1, 3.1.2, 3.1.3, 3.2.1, 3.2.2, 3.2.3, 3.3.1, 3.4.1, 3.4.2, 4.1.1, 4.1.2, 4.2.1, 4.2.2, 4.3.1, 6.1.1, 6.1.2, 6.2.1, 6.3.1, 6.3.2, 6.4.1, 6.5.1, 6.6.1, 7.1.1, 7.2.1, 7.3.1

5 Agency Maintenance WZ Operations Staff/Tools

Internal WZED warehouse agency staff interface for direct viewing, updating, managing and maintaining agency Active Operational WZED.



1.4.1, 1.4.2, 1.4.3, 1.5.1, 1.5.2

6 Contractor WZ Operations Staff/Tools

External Interface for Contractor direct viewing, updating, managing and maintaining agency Active Operational WZED.



1.3.1, 1.3.2, 1.4.1, 1.4.2, 1.4.3, 1.5.1, 1.5.2, 1.6.1, 3.1.1, 3.1.2, 3.1.3, 3.2.1, 3.2.2, 3.2.3, 3.3.1, 3.4.1, 3.4.2, 4.1.1, 4.1.2, 4.2.1, 4.2.2, 4.3.1, 6.1.1, 6.1.2, 6.2.1, 6.3.1, 6.3.2, 6.4.1, 6.5.1, 6.6.1, 7.1.1, 7.2.1, 7.3.1



Interface No



Type of Interface






7 Neighbor Agency WZ Operations Staff/Tools

External Interface to Export Active Operational WZED to Other Agencies.


NA 1.3.2

8 Agency-to-Utilities WZ Coordination Staff/Tools

Internal WZED warehouse agency staff interface for direct viewing, updating, managing and maintaining agency Active Operational WZED for coordination with Utilities.



1.5.1, 1.5.2

9 Agency-to-Law Enforcement Coordination Staff/Tools

Internal WZED warehouse agency staff interface for direct viewing, updating, managing and maintaining agency Active Operational WZED for coordination with Law Enforcement.



6.2.1, 6.4.1, 6.5.1

10 Agency TMC/ATMS/RCRS/ITS Information/Traveler Information & Message Systems

Internal Interface to Export Active Operational WZED to TMC/ATMS/RCRS/ITS.


NA 1.6.1, 4.1.1, 4.1.2, 4.2.1, 4.2.2, 4.3.2, 6.6.1

11 Agency Smart Work Zone Interface

Internal Interface to Tool which translates WZED into information required by Smart Work Zones and which filters and translates Smart Work Zones information into WZED



4.3.2

12 Agency Connected & Automated Vehicles Interface

Internal Interface to Tool which translates WZED into information required by CAVs and which filters and translates CAV information into WZED



7.1.1, 7.2.1, 7.3.1



Interface No



Type of Interface






13 Law Enforcement Performance Analysis Staff/Tools

Internal Interface to Export Planned and Actual WZED Archive to Law Enforcement Performance/Impact Analysis.

Planned and Actual WZED Archive

NA 6.1.1, 6.1.2, 6.3.1, 6.3.2

14 State and Federal Performance Analysis Staff/Tools

External Interface to Export Planned and Actual WZED Archive to Other Agencies.


NA 5.3.1, 5.3.2

15 Agency WZ Inspection & Performance Monitoring

Internal Interface to Export Active Operational WZED to Inspection and Performance Monitoring Staff/Tools.


NA 3.1.1, 3.1.2, 3.1.3, 3.2.1, 3.2.2, 3.2.3, 3.3.1

16 Crash Performance/ Impact Analysis Staff/Tools

Internal Interface to Export Planned and Actual WZED Archive to Traffic Impact/ Performance Analysis Staff/Tools.


NA 2.1.2, 2.1.3, 3.2.2, 5.1.2, 5.1.3, 5.2.1, 5.2.2, 5.2.3, 5.3.1, 5.3.2

17 Traffic Performance/ Impact Analysis Staff/Tools

Internal Interface to Export Planned and Actual WZED Archive to Traffic Impact/ Performance Analysis Staff/Tools.


NA 2.1.1, 2.2.1, 2.2.2, 3.2.1, 3.4.1, 3.4.2, 5.1.1, 5.1.3, 5.2.1, 5.2.2, 5.2.3, 5.3.1, 5.3.2


USE CASE DESCRIPTIONS

CATEGORY 1 – WORK ZONE PLANNING AND PROJECT COORDINATION

Stakeholder Need: 1.1 Strategic Coordination during Project Initiation and Planning/design and Project Development (Agency) Use Case 1.1.1 – Agency Project Initiation and Planning TTC Coordination

WZ Life Cycle Stage: Planning and Design

Description: Agency coordinates plans for multiple projects along a particular facility to ensure travel path continuity.

Examples: Agency has list of capital improvement construction projects (new construction or reconstruction/widening), and/or a list of 3R projects (resurfacing, restoration, rehabilitation) to prioritize and coordinate (which ones to complete first, which ones should not happen at the same time because they affect the same motorists, etc.).

WZED User(s):

• Agency WZ Planning and Design Staff/Tools

WZED Flow Illustration: (Interface 1)

1. Agency WZ Planning & Design Staff/Tools develop initial plan for work zone and enter initial WZED Location, Time, Impact and Metadata into WZED warehouse.

2. When updating plans, Agency WZ Planning & Design Staff/Tools obtain the latest planning WZED Location, Time, Impact and Metadata from WZED warehouse.

3. Agency WZ Planning & Design Staff/Tools revise and update work zone plans. 4. Agency WZ Planning & Design Staff/Tools update planning WZED in WZED

warehouse.

WZED User Objective:

• Agency WZ Schedule Coordination • Agency WZ Temporary Traffic Control Planning

Agency WZ Planning &

Design Staff/Tools

AGENCY WZED

WAREHOUSE

Latest Planning WZED

Planning WZED Updates

1

2

3

Initial Planning WZED

4


WZED Content:

• Owner agency • Funding allocation • Project ID • Event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Time - Planned start date/time of event/subevent • Time - Planned project duration • Time - Indicator for level of confidence in expected start date • Time - Status • Activity - General description of event/subevent • Metadata - Indicator that a change to an event/subevent entry has been made

WZED Content Update Frequency: Agency Planning and Design Updates

External Data Needed for User Objective: NA

WZED Warehouse Interface Type: WZED warehouse Agency staff interface for direct viewing, updating, managing and maintaining agency WZED.

Use Case 1.1.2 – Agency Project Design Coordination


Description: Agency coordinates project designs for multiple projects along a particular facility to ensure travel path continuity.

Examples: Project plans (including Temporary Traffic Control plans) are developed and finalized for the bidding process. The goal continues to be to coordinate when agency projects are occurring on various roadway sections in a way that minimizes overall impacts to travelers but now includes coordination of specific phases that may create conflicts and issues.

WZED User(s):



WZED Flow Illustration: (Interface 1)

1. Agency WZ Planning & Design Staff/Tools obtain the latest design WZED Location, Time, Impact and Metadata from WZED Warehouse.

2. Agency WZ Planning & Design Staff/Tools revise and update work zone design. 3. Agency WZ Planning & Design Staff/Tools update design WZED in WZED

Warehouse.


• Agency WZ Schedule Coordination • Agency WZ Temporary Traffic Control Design

WZED Content:

• Owner agency • Funding allocation • Expected number of phases • Expected phase durations • Project ID • Event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Time - Planned start date/time of event/subevent • Time - Planned project duration • Time - Indicator for level of confidence in expected start date • Time - Status • Event - General description of event/subevent • Event - General description about TTC approach • Metadata - Indicator that a change to an event/subevent entry has been made



Agency WZ Planning &

Design Staff/Tools

AGENCY WZED

WAREHOUSE

Design WZED

Design WZED Updates

1

2 3


WZED Warehouse Interface Type: WZED warehouse Agency Design staff interface for direct viewing, updating, managing and maintaining agency WZED.

Stakeholder Need: 1.2 Strategic Coordination during Project Initiation and Planning and Project Development (Regional) Use Case 1.2.1 - Regional Project Initiation and Planning Coordination


Description: Multiple agencies coordinate plans for multiple projects along a particular facility to ensure travel path continuity.

Examples: Multiple agencies in a region have lists of capital improvement construction projects (new construction or reconstruction/widening), and/or a list of 3R projects (resurfacing, restoration, rehabilitation) to prioritize and coordinate (which ones to complete first, which ones should not happen at the same time because they affect the same motorists, etc.).

WZED User(s):

• Agency WZ Planning and Design Staff/Tools • Neighbor Agency WZ Planning and Design Staff/Tools

WZED Flow Illustration: (Interfaces 1 and 2)

Case A, Agency does not have access to Neighbor Agency WZED warehouse

1. Agency and Neighbor Agency WZ Planning & Design Staff/Tools obtain the latest planning WZED Location, Time, Impact and Metadata from the Agency and Neighbor Agency WZED warehouse.

2. Agency and Neighbor Agency Staff share, analyze, and coordinate work zone plans. 3. Agency and Neighbor Agency WZ Planning & Design Staff/Tools revise and update

their respective work zone plans. 4. Agency and Neighbor Agency WZ Planning & Design Staff/Tools update their

planning WZED in their respective WZED warehouse.


Case B, Agency has access to neighbor agency WZED warehouse (read only)

1. Agency and Neighbor Agency WZ Planning & Design Staff/Tools obtain the latest Agency and Neighbor Agency planning WZED Location, Time, Impact and Metadata from the Agency and Neighbor Agency WZED warehouse.

2. Agency and Neighbor Agency Staff analyze and coordinate work zone plans. 3. Agency and Neighbor Agency WZ Planning & Design Staff/Tools revise and update

their respective work zone plans. 4. Agency and Neighbor Agency WZ Planning & Design Staff/Tools update their

planning WZED in their respective WZED warehouse.


• Regional WZ Schedule Coordination • Regional WZ Temporary Traffic Control Planning Coordination

WZED Content:

• Owner agency • Owner agency Project Manager • Contractor/subcontractors • Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Planned start date/time of event/subevent • Time - Planned end date/time of event/subevent • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Event - General description of event/subevent • Event - Indication that the TTC requires coordination between the projects


• Event - Reference to projects that need to coordinated with (Project IDs?) • Metadata - Indicator that a change to an event/subevent entry has been made


External Data Needed for User Objective:

• Neighbor Agency WZ Schedules • Neighbor Agency Temporary Traffic Control Designs

WZED Warehouse Interface Type: Interface to External Tool for integrating WZED from regional agencies for viewing, updating, managing and maintaining regional WZED.

Use Case 1.2.2 – Regional Project Design Coordination


Use Case Description: Multiple agencies coordinate project designs for multiple projects along a particular facility to ensure travel path continuity.

Use Case Examples: Regional project plans (including Temporary Traffic Control plans) are developed and finalized for the bidding process. The goal continues to be to coordinate when regional projects are occurring on various roadway sections in a way that minimizes overall impacts to travelers (including coordination of specific phases that may create conflicts and issues).

WZED User(s):

• Agency WZ Planning and Design Staff/Tools • Neighbor Agency WZ Planning and Design Staff/Tools


Case A, Agency does not have access to Neighbor Agency WZED warehouse

1. Agency and Neighbor Agency WZ Planning & Design Staff/Tools obtain their latest respective design WZED Location, Time, Impact and Metadata from the Agency and Neighbor Agency WZED warehouse.

2. Agency and Neighbor Agency Staff share, analyze, and coordinate work zone design.

3. Agency and Neighbor Agency WZ Planning & Design Staff/Tools revise and update their respective work zone design.

4. Agency and Neighbor Agency WZ Planning & Design Staff/Tools update their design WZED in their respective WZED warehouse.


Case B, Agency has access to neighbor agency WZED warehouse (read only)

1. Agency and Neighbor Agency WZ Planning & Design Staff/Tools obtain latest Agency and Neighbor Agency design WZED Location, Time, Impact and Metadata from the Agency and Neighbor Agency WZED warehouse.

2. Agency and Neighbor Agency Staff analyze and coordinate work zone design. 3. Agency and Neighbor Agency WZ Planning & Design Staff/Tools revise and update

their respective work zone design. 4. Agency and Neighbor Agency WZ Planning & Design Staff/Tools update their design

WZED in their respective WZED warehouse.


• Regional WZ Schedule Coordination • Regional WZ Temporary Traffic Control Design Coordination

WZED Content:

• Owner agency • Owner agency Project Manager • Contractor/subcontractors • Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Planned start date/time of event/subevent • Time - Planned end date/time of event/subevent • Time - Actual start date/time of event/subevent


• Time - Actual end date/time of event/subevent • Time - Status • Event - General description of event/subevent • Event - Indication that the TTC requires coordination between the projects • Event - Reference to projects that need to coordinated with (Project IDs?) • Metadata - Indicator that a change to an event/subevent entry has been made



• Neighbor Agency WZ Schedules • Neighbor Agency Temporary Traffic Control Plans


Stakeholder Need: 1.3 Strategic Coordination during Active Work Zone Operations Use Case 1.3.1 – Agency Lane Construction Coordination

WZ Life Cycle Stage: Active Work Zone Operations

Description: Agency sequences capacity-reducing projects in their domain to ensure that sufficient alternative route capacity is available to travelers at all times.

Examples: Sometimes an agency has multiple projects (rehabilitation or reconstruction/widening) occurring simultaneously next to one another on the same facility. During active work zone operations, the agency must keep the projects synchronized to ensure that the phasing for each project connects together from a motorist travel path standpoint. Reasons for, and types of, synchronization may vary (e.g., lane shifts at end of one project need to align with lanes from adjacent projector an agency may not want to open up new lanes in a segment until adjacent segments can also open up their new lanes).

WZED User(s):

• Agency Construction WZ Operations Staff/Tools • Contractor WZ Operations Staff/Tools



1. Agency WZ Construction Operations Staff/Tools obtain the latest Active Operational WZED Location, Time, Impact and Metadata from WZED warehouse.

2. Agency WZ Construction Operations Staff/Tools revise and update work zone deployment and operations.

3. Agency WZ Construction Operations Staff/Tools update Active Operational WZED in WZED warehouse.

4. Contractor WZ Construction Operations Staff/Tools obtain the latest, updated Active Operational WZED Location, Time, Impact and Metadata from WZED warehouse.

WZED User Objective: Agency Construction WZ Schedule Coordination

WZED Content:

• Owner agency • Contractor/subcontractors • Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Time - Planned start date/time of event/subevent • Time - Planned end date/time of event/subevent • Time - Status • Event - Planned number of lanes to be closed • Event - Description of planned lanes to be closed

AGENCY WZED WAREHOUSE

Contractor WZ Operations Staff/Tools

Agency Construction

WZ OperStaff/Tools

Activ

e O

pera

tiona

l W

ZED

Activ

e O

pera

tiona

l W

ZED

Upd

ates

Activ

e O

pera

tiona

l W

ZED

1

2

3

4


• Event - Total number of lanes • Event - Planned number of lanes to be open • Event - Expected effect on travel time/delay/queuing • Metadata - Indicator that a change to an event/subevent entry has been made

WZED Content Update Frequency: Agency Construction WZ Operations Schedule Updates


WZED Warehouse Interface Type:

• WZED warehouse Agency staff interface for direct viewing, updating, managing and maintaining agency WZED.

• WZED warehouse Contractor staff interface for direct viewing, updating, managing and maintaining agency WZED

Use Case 1.3.2 – Regional Alternative Route Coordination during Construction


Description: Multiple agencies sequence capacity-reducing projects in their region to ensure that sufficient alternative route capacity is available to travelers at all time.

Examples: An agency may have a project that involves the closure of an exit ramp during one of its phases that will likely divert traffic to an alternative ramp where another agency has work ongoing on the cross street. Strategic coordination between agencies during project development and construction would be initiated to ensure that the cross-street work is completed before the exit ramp closure phase begins, but would continue in to the active work operations stage.

WZED User(s):

• Agency Construction WZ Operations Staff/Tools • Contractor WZ Operations Staff/Tools


WZED Flow Illustration: (Interfaces 2, 3, 4, 6, and 7)

1. Agency and Neighbor Agency WZ Construction Operations Staff/Tools obtain latest Active Operational WZED Location, Time, Impact and Metadata from the Agency and Neighbor Agency WZED warehouse.

2. Agency and Neighbor Agency Staff analyze and coordinate work zone deployment and operations.

3. Agency and Neighbor Agency WZ Construction Operations Staff/Tools revise and update their respective work zone deployment and operations.

4. Contractor WZ Operations Staff/Tools obtain the latest, updated Active Operational WZED Location, Time, Impact and Metadata from WZED warehouse.

WZED User Objective: Regional Construction WZ Schedule Coordination

WZED Content:

• Contractor/subcontractors • Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located


• Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Planned start date/time of event/subevent • Time - Planned end date/time of event/subevent • Time - Recurring flag • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Event - General description of event/subevent • Metadata - Indicator that a change to an event/subevent entry has been made

WZED Content Update Frequency: Agency Construction WZ Operations Schedule Updates

External Data Needed for User Objective: Neighbor Agency Construction & WZ Operations Schedules


Stakeholder Need: 1.4 Day-to-Day Operational Coordination to Avoiding Multiple Capacity Restrictions at the Same Time Use Case 1.4.1 – Agency Capacity Restriction Coordination


Description: Agency coordinates construction and maintenance activities to minimize traffic impact.

Examples: During day-to-day operations within an agency, multiple needs may exist for periodic short-term or short-duration lane closures (could also be ramp, intersection, or shoulder closures). These could be for multiple construction contracts on the same roadway or maintenance work needed upstream or downstream of a construction contract. The desire is to coordinate all of the lane closures such that they do not create excessive cumulative delays for motorists.

WZED User(s):

• Agency Construction WZ Operations Staff/Tools • Agency Maintenance WZ Operations Staff/Tools • Contractor WZ Operations Staff/Tools


WZED Flow Illustration: (Interfaces 4, 5, and 6)

1. Agency WZ Construction Operations and Maintenance WZ Operations Staff/Tools obtain latest Active Operational WZED Location, Time, Impact and Metadata from the Agency WZED warehouse.

2. Agency and Neighbor Agency Staff analyze and coordinate work zone deployment and operations.

3. Agency and Neighbor Agency WZ Construction Operations Staff/Tools revise and update their respective work zone deployment and operations.

4. Contractor WZ Operations Staff/Tools obtain the latest, updated Active Operational WZED Location, Time, Impact and Metadata from WZED warehouse.


• Agency WZ Traveler Schedule Coordination • Agency Maintenance WZ Schedule Coordination • Agency Construction WZ Schedule Coordination

WZED Content:

• Contractor/subcontractors • Event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Planned start date/time of event/subevent • Time - Planned end date/time of event/subevent


• Time - Recurring flag • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Event - Planned number of lanes to be closed • Event - Description of planned lanes to be closed • Event - Total number of lanes • Event - Planned number of lanes to be open • Event - Lane closure permit number • Metadata - Indicator that a change to an event/subevent entry has been made

WZED Content Update Frequency:

• Agency Construction WZ Operations Schedule Updates • Agency Maintenance WZ Schedule Updates





Use Case 1.4.2 – Agency Maintenance Contract Coordination


Description: Agency coordinates maintenance contract activities to minimize traffic impact.

Examples: An agency has a maintenance contract to repair various items on various roadways (i.e., guardrail repair, striping, etc.) under its jurisdiction. The contract is set up to allow contractor to group required activities in the region so that one trip can be made to take care of multiple maintenance items. The contractor would submit its plans to do those activities in general terms (such as during one or two days in an upcoming week, the actual days to be determined the day before).

WZED User(s):

• Agency Maintenance WZ Operations Staff/Tools • Contractor WZ Operations Staff/Tools



1. Agency Maintenance and Contractor WZ Operations Staff/Tools obtain latest Active Operational WZED Location, Time, Impact and Metadata from the Agency WZED warehouse.

2. Agency Maintenance and Contractor WZ Operations Staff analyze and coordinate work zone deployment and operations.

3. Agency Maintenance and Contractor WZ Operations Staff/Tools revise and update their respective work zone deployment and operations.

4. Agency Maintenance WZ Operations Staff/Tools update the Active Operational WZED in the Agency WZED warehouse.


• Agency WZ Traveler Schedule Coordination • Agency Maintenance WZ Schedule Coordination

WZED Content:

• Owner agency • Contractor/subcontractors • Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Time - Planned start date/time of event/subevent


• Time - Planned end date/time of event/subevent • Time - Status • Event - Planned number of lanes to be closed • Event - Description of planned lanes to be closed • Event - Total number of lanes • Event - Planned number of lanes to be open • Event - Expected effect on travel time/delay/queuing • Metadata - Indicator that a change to an event/subevent entry has been made

WZED Content Update Frequency: Agency Maintenance WZ Schedule Updates


WZED Warehouse Interface Type: WZED warehouse Agency staff interface for direct viewing, updating, managing and maintaining agency WZED.

Use Case 1.4.3 – Agency Vertical Construction Coordination


Description: Agency coordinates vertical construction closures, agency construction, and/or maintenance to minimize traffic impact.

Examples: An agency grants permission to a vertical construction contractor who submits a request to close a lane (long-term or short-term) on an urban arterial. The agency wants to coordinate the vertical construction lane closure with other planned lane closures by the agency (construction or maintenance) or other vertical construction lane closures on the segment, so that multiple entities are not closing lanes at the same time.

WZED User(s):

• Agency Construction WZ Operations Staff/Tools • Agency Maintenance WZ Operations Staff/Tools • Contractor WZ Operations Staff/Tools



1. Agency Construction WZ, Maintenance WZ, and Contractor WZ Operations Staff/Tools obtain latest Active Operational WZED Location, Time, Impact and Metadata from the Agency WZED warehouse.

2. Agency Construction WZ, Maintenance WZ, and Contractor WZ Operations Staff analyze and coordinate work zone deployment and operations.

3. Agency Construction WZ, Maintenance WZ, and Contractor WZ Operations Staff/Tools revise and update their respective work zone deployment and operations.

4. Agency Construction WZ Operations Staff/Tools update the Active Operational WZED in the Agency WZED warehouse.


• Agency WZ Traveler Schedule Coordination • Agency Maintenance WZ Schedule Coordination • Agency Construction WZ Schedule Coordination

WZED Content:

• Owner agency • Contractor/subcontractors • Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent


• Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Time - Planned start date/time of event/subevent • Time - Planned end date/time of event/subevent • Time - Status • Event - Planned number of lanes to be closed • Event - Description of planned lanes to be closed • Event - Total number of lanes • Event - Planned number of lanes to be open • Event - Expected effect on travel time/delay/queuing • Event - Indicator that the work involves cutting or otherwise affecting the pavement • Metadata - Indicator that a change to an event/subevent entry has been made







Stakeholder Need: 1.5 Day-to-Day Operational Coordination to Reduce the Number of Lane Closure Disruptions over Time on a Roadway Segment Use Case 1.5.1 – Agency Maintenance, Construction, and Utility Schedule Coordination (Planning/Design)


Description: Agency coordinates maintenance, utility, and construction contracts in a region on a given roadway segment to minimize traffic impact.

Examples: Agency maintenance crews sometimes need to close a lane for work a short distance upstream or downstream of a planned construction lane closure. The maintenance crew coordinates with the contractor to do the maintenance work on the same day as the contractor, and simply extend the lane closure upstream or downstream of the construction lane closure location.

WZED User(s):

• Agency Construction WZ Operations Staff/Tools


• Agency Maintenance WZ Operations Staff/Tools • Contractor WZ Operations Staff/Tools • Agency Utilities WZ Operations Staff/Tools

WZED Flow Illustration: (Interfaces 4, 5, 6, and 8)

1. Agency Construction WZ, Maintenance WZ, Contractor WZ and Utilities WZ Operations Staff/Tools obtain latest Active Operational WZED Location, Time, Impact and Metadata from the Agency WZED warehouse.

2. Agency Construction WZ, Maintenance WZ, Contractor WZ and Utilities WZ Operations Staff analyze and coordinate work zone deployment and operations.

3. Agency Construction WZ, Maintenance WZ, Contractor WZ and Utilities WZ Operations Staff/Tools revise and update their respective work zone deployment and operations.



• Agency WZ Traveler Schedule Coordination • Agency Maintenance WZ Schedule Coordination • Agency Construction WZ Schedule Coordination • Utility WZ Schedule Coordination

WZED Content:

• Owner agency • Event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located


• Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Time - Planned start date/time of event/subevent • Time - Planned end date/time of event/subevent • Time - Status • Event - Temporary restrictions in place




• Utility Construction & Maintenance schedule


• External Interface for integrating Utility Construction and Maintenance Schedule with Agency WZED for coordinating construction, maintenance, and work zones.


• WZED warehouse Contractor staff interface for direct viewing, updating, managing and maintaining agency WZED.

Use Case 1.5.2 – Pavement Cut Coordination


Description: Agency coordinates maintenance, utility, and construction contracts in a region on a given roadway segment to minimize pavement cuts.

Examples: In situations where all work cannot be accomplished at the same time, the goal is to have all work involving pavement cuts (due to utilities, signal work, maintenance, etc.) accomplished before a planned resurfacing effort by the owner agency is performed.

WZED User(s):

• Agency Construction WZ Operations Staff/Tools • Agency Maintenance WZ Operations Staff/Tools • Contractor WZ Operations Staff/Tools • Agency Utilities WZ Operations Staff/Tools



1. Agency Construction WZ, Maintenance WZ, Contractor WZ and Utilities WZ Operations Staff/Tools obtain latest Active Operational WZED Location, Time, Impact and Metadata from the Agency WZED warehouse.

2. Agency Construction WZ, Maintenance WZ, Contractor WZ and Utilities WZ Operations Staff analyze and coordinate work zone deployment and operations.

3. Agency Construction WZ, Maintenance WZ, Contractor WZ and Utilities WZ Operations Staff/Tools revise and update their respective work zone deployment and operations.



• Agency WZ Traveler Schedule Coordination • Agency Maintenance WZ Schedule Coordination • Agency Construction WZ Schedule Coordination • Utility WZ Schedule Coordination

WZED Content:

• Owner agency • Contractor/subcontractors • Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located


• Location - Direction of travel of event/subevent • Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Time - Planned start date/time of event/subevent • Time - Planned end date/time of event/subevent • Time - Status • Event - Planned number of lanes to be closed • Event - Description of planned lanes to be closed • Event - Total number of lanes • Event - Planned number of lanes to be open • Event - Expected effect on travel time/delay/queuing • Event - Indicator that the work involves cutting or otherwise affecting the pavement • Metadata - Indicator that a change to an event/subevent entry has been made




• Utility Construction & Maintenance schedule

WZED Warehouse Interface Type: Interface to External Tool for integrating Utility Construction and Maintenance Schedule with Agency WZED for coordinating construction, maintenance, and work zones.

Stakeholder Need: 1.6 Day-to-Day Operational Coordination with Permitting Office Coordination of Oversize Vehicle Approvals Use Case 1.6.1 – Oversize/Overweight Vehicle Route Coordination


Use Case Description: Agency coordinates with permitting office about planned work zone activities that impact oversize/overweight vehicles.

Use Case Examples: An owner agency permitting office needs to be able to determine whether an oversize/overweight permit request for a particular route can be approved for a given time period (or restricted for a given time period) based on roadway characteristics within the work zone.

WZED User(s):

• Agency Construction WZ Operations Staff/Tools • Contractor WZ Operations Staff/Tools • Agency TME/ATMS/RCRS/IT'S/Traveler Information & Message Systems • Oversize/Overweight Route Permitting



1. Agency Construction WZ and Contractor WZ Operations Staff/Tools update the latest Active Operational WZED to the Agency WZED warehouse.

2. Agency TMC/ATMS/RCRS/ITS Information Integration & Output Staff/Tools obtain the latest Active Operational WZED to the Agency WZED warehouse.

3. Agency TMC/ATMS/RCRS/ITS Information Integration & Output Staff/Tools analyze the WZED and provide relevant WZ vehicle size and weight limit information to the Oversize/Overweight Route Permitting agency.

WZED User Objective: Agency OSOW Route Analysis

WZED Content:

• Owner agency • Event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Time - Planned start date/time of event/subevent • Time - Planned end date/time of event/subevent • Time - Status • Event - Temporary restrictions in place



External Data Needed for User Objective: Agency OSOW Routing Plans

WZED Warehouse Interface Type: Agency OSOW Route Analysis Staff use Agency Staff interface to assess WZs for support of OSOW vehicles.


CATEGORY 2 – WORK ZONE IMPACT ANALYSES

Stakeholder Need: 2.1 Estimating Expected Impacts for a Single Work Zone Use Case 2.1.1 – Work Zone Mobility Impact Assessment


Use Case Description: Agency analysis of expected mobility impacts of a single work zone

Use Case Examples: An agency may desire to analyze a proposed work zone to determine the delays to be expected (e.g., total hours or delay per person or per-vehicle) over the entire project, during a particular time period or set of conditions for that project (e.g., during peak hours or hours of short-term lane closures), and/or for a particular upcoming specific period (such as an upcoming weekend lane closure).

WZED User(s):

• Agency WZ Planning and Design Staff/Tools • Agency Traffic Performance/Impact Analysis Staff/Tools


1. Agency WZ Planning & Design Staff/Tools obtain the latest planning WZED Location, Time, Impact and Metadata from WZED warehouse.

2. Agency Traffic Impact/ Performance Analysis Staff/Tools obtain the latest planning WZED Location, Time, Impact and Metadata and relevant historical Planned and Actual WZED from WZED warehouse.

3. Agency Traffic Impact/ Performance Analysis Staff/Tools analyze plans and provide traffic impact assessments to Agency WZ Planning & Design Staff/Tools.

4. Agency WZ Planning & Design Staff/Tools revise and update work zone plans.


5. Agency WZ Planning & Design Staff/Tools update planning WZED in WZED warehouse.

WZED User Objective: Work Zone mobility and travel delay impact analysis

WZED Content:

• Owner agency • Expected number of phases • Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Time - Planned start date/time of event/subevent • Time - Planned end date/time of event/subevent • Time - Status • Event - Expected geometrics associated with each event/subevent • Event - Expected traffic control device(s) associated with each event/subevent

WZED Content Update Frequency: Agency Construction Plan Updates


• WZ Mobility Performance History Analysis • Pre-Construction Mobility Data

WZED Warehouse Interface Type: Interface to external tool for Mobility and Travel Delay Impact Analysis which integrates agency traffic resources and post work zone mobility performance data to assess potential mobility impact of work zones.

Use Case 2.1.2 – Work Zone Safety Impact Assessment


Use Case Description: Agency analysis of expected safety impacts of a single work zone

Use Case Examples: An agency may desire to assess the expected safety impacts of a particular work zone configuration (e.g., using narrowed lanes, adding temporary concrete barrier, altered lane use assignments, etc.)

WZED User(s):



• Agency Crash Performance/Impact Analysis Staff/Tools



2. Agency Crash Impact/ Performance Analysis Staff/Tools obtain the latest planning WZED Location, Time, Impact and Metadata and relevant historical Planned and Actual WZED from WZED warehouse.

3. Agency Crash Impact/ Performance Analysis Staff/Tools analyze plans and provide crash impact assessments to Agency WZ Planning & Design Staff/Tools.


warehouse.

WZED User Objective: Work Zone safety impact analysis

WZED Content:

• Owner agency • Expected number of phases • Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Time - Planned start date/time of event/subevent • Time - Planned end date/time of event/subevent • Time - Status




• WZ Safety Performance History Analysis • Pre-Construction Safety Data

WZED Warehouse Interface Type: Interface to external tool for Safety Impact Analysis which integrates agency safety resources and post work zone safety performance data to assess potential safety impact of work zones.

Use Case 2.1.3 – Assessment of Expected Effects of Alternative TMP Mitigation Strategies


Use Case Description: Agency analysis to compare the expected safety and/or mobility benefits of alternative TMP strategies.

Use Case Examples: An agency may want to estimate the safety effects of alternative TMP strategies, such as the trade-offs of using narrowed lanes to reduce the total duration of the project versus maintaining full-width lanes but increasing the overall project duration.

WZED User(s):

• Agency WZ Planning and Design Staff/Tools • Agency Crash Performance/Impact Analysis Staff/Tools





3. Agency Crash Impact/ Performance Analysis Staff/Tools analyze plans and provide traffic impact assessments to Agency WZ Planning & Design Staff/Tools.


warehouse.

WZED User Objective: Work Zone safety impact analysis

WZED Content:

• Owner agency • Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Time - Planned start date/time of event/subevent • Time - Planned end date/time of event/subevent • Time - Status • Event - Planned number of lanes to be closed • Event - Description of planned lanes to be closed • Event - Total number of lanes • Event - Planned number of lanes to be open • Event - Planned number of short-term lane closures • Event - Expected effect on travel time/delay/queuing



• WZ Safety Performance History Analysis • Pre-Construction Safety Data

WZED Warehouse Interface Type: Interface to external tool for Safety Impact Analysis which integrates agency safety resources and post work zone safety performance data to assess potential safety impact of work zones.

Stakeholder Need: 2.2 Estimating Expected Combined Impacts of Multiple Work Zones


Use Case 2.2.1 –Corridor Mobility Impact Assessment


Use Case Description: Regional analysis of expected mobility impacts along a corridor with multiple work zones.

Use Case Examples: An agency may want to estimate the total cumulative delay of a trip along a corridor for a motorist traveling through multiple work zones.

WZED User(s):

• Agency WZ Planning and Design Staff/Tools • Agency Traffic Performance/Impact Analysis Staff/Tools • Neighbor Agency WZ Planning and Design Staff/Tools • Neighbor Agency Traffic Performance/Impact Analysis Staff/Tools • Regional WZ Coordination Staff/Tools


1. Agency, Neighbor Agency, and Regional WZ Planning & Design Staff/Tools obtain the latest planning WZED Location, Time, Impact and Metadata from WZED warehouse.

2. Agency, Neighbor Agency, and Regional Traffic Impact/ Performance Analysis Staff/Tools obtain the latest planning WZED Location, Time, Impact and Metadata and relevant historical Planned and Actual WZED from Agency and Neighbor Agency WZED warehouse.

3. Agency, Neighbor Agency, and Regional Traffic Impact/ Performance Analysis Staff/Tools analyze plans and provide traffic impact assessments to Agency, Neighbor Agency, and Regional WZ Planning & Design Staff/Tools.

4. Agency, Neighbor Agency, and Regional WZ Planning & Design Staff/Tools revise and update work zone plans.

5. Agency and Neighbor Agency WZ Planning & Design Staff/Tools update planning WZED in WZED warehouse.


WZED User Objective: Regional corridor work zone mobility and travel delay impact analysis

WZED Content:

• Owner agency • Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Time - Planned start date/time of event/subevent • Time - Planned end date/time of event/subevent • Time - Status • Event - Indication that the TTC requires coordination between the projects • Event - Reference to projects that need to coordinated with (Project IDs?)




WZED Warehouse Interface Type: Interface to external tool for Mobility and Travel Delay Impact Analysis which integrates agency traffic resources and post work zone mobility performance data to assess potential mobility impact of work zones.

Use Case 2.2.2 –Network Mobility Impact Assessment


Use Case Description: Regional analysis of expected mobility on a transportation network with multiple work zones

Use Case Examples: An agency may want to estimate the expected changes in travel times due to the work zones for various travel paths through the network, or compute aggregate network-based measures such as the total cumulative increase in vehicle-hours of travel time in the network (or similar measures).

WZED User(s):



• Neighbor Agency WZ Planning and Design Staff/Tools • Neighbor Agency Traffic Performance/Impact Analysis Staff/Tools • Regional WZ Coordination Staff/Tools


1. Agency, Neighbor Agency, and Regional WZ Planning & Design Staff/Tools obtain the latest planning WZED Location, Time, Impact and Metadata from WZED warehouse.

2. Agency, Neighbor Agency, and Regional Traffic Impact/ Performance Analysis Staff/Tools obtain the latest planning WZED Location, Time, Impact and Metadata and relevant historical Planned and Actual WZED from Agency and Neighbor Agency WZED warehouse.

3. Agency, Neighbor Agency, and Regional Traffic Impact/ Performance Analysis Staff/Tools analyze plans and provide traffic impact assessments to Agency, Neighbor Agency, and Regional WZ Planning & Design Staff/Tools.

4. Agency, Neighbor Agency, and Regional WZ Planning & Design Staff/Tools revise and update work zone plans.

5. Agency and Neighbor Agency WZ Planning & Design Staff/Tools update planning WZED in WZED warehouse.

WZED User Objective: Regional network work zone mobility and travel delay impact analysis

WZED Content:

• Owner agency • Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent


• Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Time - Planned start date/time of event/subevent • Time - Planned end date/time of event/subevent • Time - Status • Event - Indication that the TTC requires coordination between the projects • Event - Reference to projects that need to coordinated with (Project IDs?)




WZED Warehouse Interface Type: Interface to external tool for Mobility and Travel Delay Impact Analysis which integrates agency traffic resources and post WZ mobility performance data to assess potential mobility impact of work zones.


CATEGORY 3 – CONSTRUCTION AND MAINTENANCE CONTRACT MONITORING

Stakeholder Need: 3.1 Monitor Compliance with Contractual WZED-Related Requirements

Use Case 3.1.1 – Short-term Lane Closure Advance Notice Monitoring


Use Case Description: Track compliance with Short-term Lane Closure Advance Notice requirements

Use Case Examples: An agency may have either construction or contract maintenance contracts that specify that a minimum number of days advance notice be given before initiating a short-term lane closure on certain roadways (could also be a shoulder closure, intersection closure, ramp closure, etc.). An agency may want to track compliance with that requirement and may eventually also want to track accuracy of advance notice requests (i.e., how often request changed and/or did the short-term lane closure take place when requested).

WZED User(s):

• Agency Construction WZ Operations Staff/Tools • Contractor WZ Operations Staff/Tools • Agency WZ Inspection and Performance Monitoring Staff




2. Agency Inspection and Performance Monitoring Staff/Tools obtain the latest Active Operational WZED from the Agency WZED warehouse.

3. Agency Inspection and Performance Monitoring Staff/Tools analyze the WZED and assess compliance with Short-term Lane Closure Advance Notice Requirements.

WZED User Objective: Monitoring and analysis of contractual requirements versus actual delivery

WZED Content:

• Project ID • Event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Time - Status

WZED Content Update Frequency: Daily


• Construction Plan • Construction RFP • Construction Contracts


WZED Warehouse Interface Type: WZED warehouse Agency contracting staff interface which integrates bid/contract requirements WZED for direct viewing, updating, managing and maintaining Compliance Monitoring WZED.

Use Case 3.1.2 – Short-term Lane Closure Allowable Hours Monitoring


Use Case Description: Track compliance with Short-term Lane Closure Allowable Hours requirements

Use Case Examples: An agency may establish allowable hours for short-term lane closures for a project, along with penalty clauses for having a lane closure in place outside of those hours. The contract may also specify multiple levels of allowable closure times (e.g., one lane can be closed starting at 9 pm and two lanes starting at 11 pm). The agency may also want to track actual closure times against those allowable times.

WZED User(s):






3. Agency Inspection and Performance Monitoring Staff/Tools analyze the WZED and assess compliance with Short-term Lane Closure Allowable Hours Requirements.


WZED Content:

• Contractor/subcontractors • Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status





Use Case 3.1.3 – Allowable Lane Closures Monitoring


Use Case Description: Track compliance with Allowable Lane Closures requirements

Use Case Examples: An agency may specify an allowable number of short-term lane closures for a project (or full-road closures, weekend closures, or duration of ramp closures). The agency desires to keep a running total of number of those events used to date.

WZED User(s):






3. Agency Inspection and Performance Monitoring Staff/Tools analyze the WZED and assess compliance with Allowable Lane Closures Requirements.


WZED Content:

• Contractor/subcontractors • Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent


• Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status





Stakeholder Need: 3.2 Monitor Compliance to Performance-Based Safety and Mobility Specifications

Use Case 3.2.1 – Travel Delay Performance Incentive


Use Case Description: Track Travel Delay Performance for Incentive

Use Case Examples: An agency could establish travel time or delay performance thresholds for contractors to maintain during a project. An incentive pool could be established that would be deducted against every time travel delays through the project exceeded a threshold.

WZED User(s):

• Agency Construction WZ Operations Staff/Tools • Contractor WZ Operations Staff/Tools • Agency Traffic Performance/Impact Analysis Staff/Tools • Agency WZ Inspection and Performance Monitoring Staff



1. Agency Construction WZ and Contractor WZ Operations Staff/Tools update the latest Active Operational WZED to the Agency WZED warehouse throughout the project.

2. Agency Traffic Impact Performance Analysis Tools Staff/Tools and Agency Inspection and Performance Monitoring Staff/Tools obtain relevant Planned and Actual WZED from the WZED warehouse.

3. Agency Traffic Impact Performance Analysis Tools Staff analyze traffic impact results and provide the information to Agency Inspection and Performance Monitoring Staff/Tools.

4. Agency Performance Monitoring Staff/Tools analyze the traffic impact results and assess Travel Delay Performance for Incentive.

WZED User Objective: Monitoring and analysis of contractual incentive requirements versus actual delivery

WZED Content:



• Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status





Use Case 3.2.2 – Traffic Safety Performance Incentive


Use Case Description: Track Traffic Safety Performance for Incentive

Use Case Examples: An agency could establish a traffic safety-based performance specification for a particular project that provided an incentive payment if the number and/or severity of crashes over the duration of the project, during a particular phase, or during particular activities such a short-term lane closures did not exceed some threshold.

WZED User(s):

• Agency Construction WZ Operations Staff/Tools • Contractor WZ Operations Staff/Tools • Agency Crash Performance/Impact Analysis Tools/Staff • Agency WZ Inspection and Performance Monitoring Staff




2. Agency Crash Impact Performance Analysis Tools Staff/Tools and Agency Inspection and Performance Monitoring Staff/Tools obtain relevant Planned and Actual WZED from the WZED warehouse.

3. Agency Crash Impact Performance Analysis Tools Staff analyze crash impact results and provide the information to Agency Inspection and Performance Monitoring Staff/Tools.

4. Agency Inspection and Performance Monitoring Staff/Tools analyze the crash impact results and assess Traffic Safety Performance for Incentive.


WZED Content:



• Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status





Use Case 3.2.3 – Coordination Performance Requirements


Use Case Description: Track Compliance with Coordination Performance Requirements

Use Case Examples: An agency may incorporate a specification into a contract to coordinate activities with another project. For example, an agency might have a project that involves the closure of an exit ramp during one of its phases that will likely divert traffic to an alternative ramp where another agency has work ongoing on the cross street. The schedules of both projects were initially coordinated to have the cross-street work completed before the exit ramp closure phase begins. Language in one or both of the contracts were included to ensure they remain in sequence.

WZED User(s):

• Agency Construction WZ Operations Staff/Tools • Contractor WZ Operations Staff/Tools • Agency WZ Inspection and Performance Monitoring Staff • Neighbor Agency Construction WZ Operations Staff/Tools • Neighbor Agency Contractor WZ Operations Staff/Tools • Neighbor Agency WZ Inspection and Performance Monitoring Staff



1. Agency and Neighbor Agency WZ Construction Operations, Contractor WZ, and Inspection and Performance Monitoring Staff/Tools obtain latest Active Operational WZED Location, Time, Impact and Metadata from the Agency and Neighbor Agency WZED warehouse.

2. Agency and Neighbor Agency WZ Construction Operations, Contractor WZ, and Inspection and Performance Monitoring Staff/Tools analyze and coordinate work zone deployment and operations.

3. Agency and Neighbor Agency WZ Construction Operations, and Contractor WZ Staff/Tools update their Active Operational WZED in their respective WZED warehouse.


WZED Content:

• Owner agency • Owner agency Project Manager • Contractor/subcontractors • Project ID • Event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Time - Status


• Event - Indication that the TTC requires coordination between the projects • Event - Reference to projects that need to coordinated with (Project IDs?)





Stakeholder Need: 3.3 Identifying Field Modifications to Project Plans

Use Case 3.3.1 – Documenting Field Modifications to Project Plans


Use Case Description: Documenting Field Modifications to Project Plans

Use Case Examples: Project staff (agency and contractor) often agree to modify an element of the Temporary Traffic Control plan or a temporary geometric feature because of field conditions or to address a traffic safety or operational issue that has developed within the project limits.

WZED User(s):

• Agency Work Zone Planning and Design Staff/Tools • Agency Construction WZ Operations Staff/Tools • Contractor WZ Operations Staff/Tools • Agency WZ Inspection and Performance Monitoring Staff



1. Agency WZ Planning and Design Staff/Tools update the latest planning and design WZED to the Agency WZED warehouse throughout the project.


3. Planning, design, and active operational WZED are stored throughout the project in a Planning and Actual WZED Archive.

4. Agency Inspection and Performance Monitoring Staff/Tools obtain relevant Planned and Actual WZED Archive information.

5. Agency Inspection and Performance Monitoring Staff/Tools analyze the information to assess Field Modifications to Project Plans.

WZED User Objective: Revised WZ Plan for comparison to actual delivery

WZED Content:

• Contractor/subcontractors • Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent


• Location - Actual end location of event/subevent • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Event - Feature that is modified relative to project plans • Event - Change made to feature • Event - TTC used to make feature change





Stakeholder Need: 3.4 Document Changes in Infrastructure Asset Location, Availability due to Work Activities

Use Case 3.4.1 – Document Changes in Infrastructure Asset Location, Availability Due to Work Activities


Use Case Description: Document Changes in Infrastructure Asset Location, Availability Due to Work Activities.

Use Case Examples: During a freeway reconstruction project, work zones often require temporary changes to the location or availability roadway infrastructure assets. For example, contractor staff working on a freeway reconstruction project may have to turn off the power and/or fiber optic communications in the project section during certain work activities (such as digging around power lines). This disrupts nighttime overhead lighting and operation of field ITS devices (e.g., Dynamic Message Signs (DMS), ramp meters, Closed Circuit Television (CCTV), or traffic sensors).

WZED User(s):








5. Agency Inspection and Performance Monitoring Staff/Tools analyze the information to assess Changes in Infrastructure Asset Location, Availability Due to Work Activities.

WZED User Objective: Document power interruptions for Post Closure Analysis

WZED Content:

• Contractor/subcontractors • Project ID • Event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent


• Location - Actual end location of event/subevent • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Event - Devices affected





Use Case 3.4.2 – Document Traffic Signal Timing Changes

WZ Life Cycle Stage:

• Construction Operations • Post WZ Performance Analysis

Use Case Description: Document Traffic Signal Timing Changes

Use Case Examples: Similarly, work zones may require temporary changes to the operations of certain roadway infrastructure assets. For example, during an intersection reconstruction project, the agency night allow the temporarily closures of the left-turn lane and changes signal timing to eliminate the left-turn phase on that approach.

WZED User(s):








5. Agency Inspection and Performance Monitoring Staff/Tools analyze the information to assess Traffic Signal Timing Changes.

WZED User Objective: Document Signal Timing changes for Post Closure Analysis

WZED Content:

• Contractor/subcontractors • Project ID • Event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Actual start date/time of event/subevent


• Time - Actual end date/time of event/subevent • Time - Status • Event - Indicator that signal timing has changed • Event - Description of signal timing change






CATEGORY 4 – REAL-TIME SYSTEM MANAGEMENT AND TRAVELER INFORMATION PROVISION

Stakeholder Need: 4.1 Use by TMCs/Agencies to Manage Facility Operations

Use Case 4.1.1 – Advance and Real-time ITS and DMS Lane Closure Traveler Information


Use Case Description: Agency communicates advance lane closure traveler information.

Use Case Examples: An agency wants to post advance notification messages on its DMS and on its website about an upcoming lane closure, and possibly the expected delays or travel time impacts of that closure. The agency also wants to update the messages as the work actually begins and when it actually ends.

WZED User(s):

• Agency Traffic Management Center • Agency Traveler Information Systems



2. Agency TMC/ATMS/RCRS/ITS/Traveler Information and Message Systems obtain the latest Active Operational WZED to the Agency WZED warehouse.

3. Agency TMC/ATMS/RCRS/ITS/Traveler Information and Message Systems analyze the WZED and provide relevant Traveler Information to Travelers approaching the work zone.

WZED User Objective: Inform TMC and Travelers of upcoming short-term lane closure


WZED Content:

• Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Planned start date/time of event/subevent • Time - Planned end date/time of event/subevent • Time - Recurring flag • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Event - Planned number of lanes to be closed • Event - Description of planned lanes to be closed • Event - Actual number of lanes to be closed • Event - Description of actual lanes to be closed • Event - Expected effect on travel time/delay/queuing • Event - Temporary restrictions in place • Metadata - Indicator that a change to an event/subevent entry has been made

WZED Content Update Frequency: Near real time


WZED Warehouse Interface Type: Agency internal system-to-system interface which shares WZED with Agency Traffic Management Center, Agency Traveler Information Systems.

Use Case 4.1.2 – Advance and Real-time ITS and DMS Detour Traveler Information


Use Case Description: Agency communicates advance detour traveler information

Use Case Examples: An agency wants to post advance notification messages on its DMS and on its website about work zones that require travelers to follow a detour path. For example, an upcoming freeway closure due to roadwork (overhead sign bridge installation) could require all traffic to exit, travel through the signalized cross-street intersection, and


return to the freeway. Estimated travel time delays expected to occur during the closure and the anticipated hours that the delays will be present might also be available.

WZED User(s):

• Agency Traffic Management Center • Agency Traveler Information Systems




3. Agency TMC/ATMS/RCRS/ITS/Traveler Information and Message Systems analyze the WZED and provide relevant Traveler Information to Travelers approaching the work zone.

WZED User Objective: Inform TMC and Travelers of upcoming freeway closure

WZED Content:

• Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Planned start date/time of event/subevent


• Time - Planned end date/time of event/subevent • Time - Recurring flag • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Event - Planned number of lanes to be closed • Event - Description of planned lanes to be closed • Event - Actual number of lanes to be closed • Event - Description of actual lanes to be closed • Event - Expected effect on travel time/delay/queuing • Event - Detour Route information • Metadata - Indicator that a change to an event/subevent entry has been made



WZED Warehouse Interface Type: Agency internal system-to-system interface which shares WZED with Agency Traffic Management Center, Agency Traveler Information Systems.

Stakeholder Need: 4.2 Third Party Dissemination of Information to Travelers and Others

Use Case 4.2.1 – Work Zone Plan Dissemination to Third Party Data Providers


Use Case Description: Agency communicates advance traveler information to third party traveler information providers

Use Case Examples: The same data that the agency uses to communicate its own information (Stakeholder Need 4.1) will be of interest and use to third-party data providers.

WZED User(s):

• Third Party Traveler Information Providers





3. Agency TMC/ATMS/RCRS/ITS/Traveler Information and Message Systems analyze the WZED and provide relevant Traveler Information to 3rd Party Traveler Information Systems.

WZED User Objective: Inform Third Party Providers of WZ Plans and WZ Changes

WZED Content:

• Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Planned start date/time of event/subevent • Time - Planned end date/time of event/subevent • Time - Recurring flag • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Event - Planned number of lanes to be closed • Event - Description of planned lanes to be closed


• Event - Actual number of lanes to be closed • Event - Description of actual lanes to be closed • Event - Expected effect on travel time/delay/queuing • Event - Detour Route information • Event - Warning notifications • Metadata - Indicator that a change to an event/subevent entry has been made



WZED Warehouse Interface Type: Agency external system-to-system interface which shares WZED with Third Party Traveler Information Systems.

Use Case 4.2.2 – Work Zone Plan Dissemination to Public


Use Case Description: Agency communicates long-term work zone traveler information with several temporary changes to lane usage, turning movement prohibitions, reduced speed limits, etc.

Use Case Examples: An agency wants to notify public via its own website or data feed to third-party data providers of temporary changes to lane usage, turning movement prohibitions, reduced speed limits, etc.

WZED User(s):

• Agency Traffic Management Center • Agency Traveler Information Systems • Third Party Traveler Information Providers





3. Agency TMC/ATMS/RCRS/ITS/Traveler Information and Message Systems analyze the WZED and provide relevant Traveler Information to Travelers and 3rd Party Traveler Information Systems.

WZED User Objective: Inform TMC and Travelers of long-term work zone

WZED Content:

• Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Planned start date/time of event/subevent • Time - Planned end date/time of event/subevent • Time - Recurring flag • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Event - List of changes to notify travelers • Metadata - Indicator that a change to an event/subevent entry has been made



WZED Warehouse Interface Type: Agency internal system-to-system interface which shares WZED with Agency Traffic Management Center, Agency Traveler Information Systems. Agency external system-to-system interface which shares WZED with Third Party Traveler Information Systems.

Stakeholder Need: 4.3 Smart Work Zone DEPLOYMENT AND OPERATION

Use Case 4.3.1 – Adjustments to Smart Work Zone Deployment



Use Case Description: Deployment locations of equipment and the algorithms governing the operation of a smart work zone system may be altered as work progresses.

Use Case Examples: WZED (such as a change to the next phase of a project or an analysis of potential impacts during a particular event that warrant a change in the deployment) from Agency Construction and Contractor Work Zone Operations Staff/Tools could trigger the need to deploy or reconfigure and re-calibrate the smart work zone devices and operation.

WZED User(s):

• Agency Smart Work Zone Interface


1. Agency Construction WZ and Contractor WZ Operations Staff/Tools obtain the latest Active Operational WZED from the Agency WZED warehouse.

2. Operational rules established within the Agency Construction WZ and Contractor WZ Operations Staff/Tools trigger an alert to the personnel responsible for maintaining the operations of the smart work zone system of the need to deploy or reconfigure and re-calibrate the smart work zone devices and operation. Responsible staff make those changes.

3. Agency Construction WZ and Contractor WZ Operations Staff/Tools update the Active Operational WZED reflecting the changes.

WZED User Objective: Initiate or modify the smart work zone deployment to best meet needs of the traveling public.

WZED Content:

• Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located


• Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Recurring flag • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Event - Actual number of lanes to be closed • Event - Description of actual lanes to be closed • Event - Expected effect on travel time/delay/queuing • Event - Temporary restrictions in place • Metadata - Indicator that a change to an event/subevent entry has been made

WZED Content Update Frequency: Daily or during periodic inspection of work zone status


WZED Warehouse Interface Type:.



Use Case 4.3.2 – Incorporation of Smart Work Zone Deployment Information Outputs into Agency and 3rd Party Traveler Information Efforts


Use Case Description: Smart work zones are often self-contained systems that collect, process, and communicate information to travelers. That information dissemination could be broadened through existing agency and 3rd party traveler information systems

Use Case Examples: Messages being displayed on portable changeable message signs that are part of the smart work zone system would be input into the WZED warehouse. Agency and 3rd party traveler information systems would extract those messages from the WZED warehouse and relay them through their dissemination mechanisms.

WZED User(s):

• Agency Smart Work Zone Interface



1. Agency Smart Work Zone Interface obtains up-to-date relevant work zone information from the Smart Work Zone components.

2. Agency Smart Work Zone Interface filters and translates Smart Work Zone information into WZED and submits it to the WZED warehouse.

3. Agency TMC/ATMS/RCRS/ITS/Traveler Information and Message Systems obtain the latest Active Operational WZED from the Agency WZED warehouse.

4. Agency TMC/ATMS/RCRS/ITS/Traveler Information and Message Systems analyze the WZED and provide relevant Traveler Information to Travelers and 3rd Party Traveler Information Systems.

WZED User Objective: Expand the dissemination of traveler information being generated by the smart work zone system.

WZED Content:

• Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Recurring flag • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Event - Actual number of lanes to be closed • Event - Description of actual lanes to be closed • Metadata - Indicator that a change to an event/subevent entry has been made




WZED Warehouse Interface Type: Information messages sent from the smart work zone to the WZED warehouse


CATEGORY 5 – SAFETY AND MOBILITY PERFORMANCE MEASUREMENT

Stakeholder Need: 5.1 Computing/Monitoring Performance Measures at a Project Level

Use Case 5.1.1 – Work Zone Mobility Performance Assessment

WZ Life Cycle Stage: Work Zone Performance Analysis

Use Case Description: Agency analysis of individual work zone mobility performance

Use Case Examples: Agencies would like to compute delay and queuing metrics occurring during an active project and/or after the project is complete for various periods (e.g., during peak periods, during work activity periods, during times of short-term lane closures, and during full weekend road closures). An agency could also desire to compare estimated measures developed during impact analyses to actual measures occurring during the work zone to assess the accuracy quality of the initial estimates.

WZED User(s):




2. Agency Traffic Performance/Impact Analysis Staff/Tools obtain the latest planning WZED Location, Time, Impact and Metadata and relevant historical Planned and Actual WZED from WZED warehouse.


3. Agency Traffic Performance/Impact Analysis Staff/Tools analyze plans and provide traffic impact assessments to Agency WZ Planning & Design Staff/Tools.


warehouse.

WZED User Objective: Computing delay and queuing metrics of a project over time for various conditions.

WZED Content:

• Owner agency • Contractor/subcontractors • Actual number of phases • Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Actual geometrics associated with each event/subevent • Actual traffic control device(s) associated with each event/subevent

WZED Content Update Frequency: Post Work Zone Completion Archive

External Data Needed for User Objective: Corresponding local and regional traffic data

WZED Warehouse Interface Type: Agency system-to-system interface to Agency tool which integrates WZED with other travel metrics databases for post Construction WZ performance analysis.

Use Case 5.1.2 – Work Zone Safety Performance Assessment


Use Case Description: Agency analysis of individual work zone safety performance.

Use Case Examples: Agencies would like to determine the change in crash risk that occurs during an active project and/or during a past project for various periods. The determination could include comparing estimated safety measure computed during impact analyses to


actual measures occurring during the work zone in order to assess the quality of the initial estimates.

WZED User(s):

• Agency WZ Planning and Design Staff/Tools • Agency Crash Performance/Impact Analysis Staff/Tools




3. Agency Crash Impact/ Performance Analysis Staff/Tools analyze plans and provide crash impact assessments to Agency WZ Planning & Design Staff/Tools.


warehouse.

WZED User Objective: Determining the change in crash risk that occurred during a project and/or during certain phases or activities.

WZED Content:

• Owner agency • Contractor/subcontractors • Actual number of phases • Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located


• Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Actual geometrics associated with each event/subevent • Actual traffic control device(s) associated with each event/subevent



• Corresponding local and regional traffic data • Corresponding local and regional crash data

WZED Warehouse Interface Type: Agency system-to-system interface to Agency tool which integrates WZED with other travel metrics databases for post Construction WZ performance analysis.

Use Case 5.1.3 – Work Zone Mitigation Strategy Effectiveness Assessment


Use Case Description: Agency analysis of the effect of implementing a particular strategy to address a specific mobility or safety issue (such as excessive speeding).

Use Case Examples: Agencies often desire to evaluate the effectiveness of a particular strategy or device implemented to address a specific issue. For example, an agency may decide to implement electronic speed limit signs to be able to post reduced regulatory speed limits within a project when work crews are on site and then raise them back up when crews leave the site. The agency may want to compute speed-related metrics for the project over time to measure whether speeds do change in response to changes in the speed limit.

WZED User(s):

• Agency Work Zone Planning and Design Staff/Tools • Neighbor Agency Work Zone Planning and Design Staff/Tools • Regional WZ Coordination Staff/Tools



1. Agency Crash Performance/Impact Analysis Staff/Tools obtain the relevant Agency Planned and Actual WZED Archive from WZED warehouse.

2. Traffic Impact Performance Analysis Staff/Tools obtain the relevant Agency Planned and Actual WZED Archive from WZED warehouse.

3. Agency Crash Performance/Impact Analysis Staff/Tools analyze history and provide crash impact assessments to Agency WZ Planning & Design Staff/Tools.

4. Agency Traffic Performance/Impact Analysis Staff/Tools analyze history and provide traffic impact assessments to Agency, Neighbor Agency, and Regional WZ Planning & Design Staff/Tools.

5. Agency WZ Planning & Design Staff/Tools assess results and apply them in future work zone planning and design.

WZED User Objective: Computing speed-related metrics of a project over time.

WZED Content:

• Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Event - Reduce Speed Limit




WZED Warehouse Interface Type: Agency system-to-system interface to Regional tool which integrates WZED with other travel metrics databases for post-construction WZ performance analysis.

Stakeholder Need: 5.2 Computing/Monitoring Performance Measures at a Regional/Programmatic Level

Use Case 5.2.1 – Regional Assessments of Work Zone Mobility Performance Targets


Use Case Description: Agency analysis of collective compliance of multiple work zones in a region to established mobility performance target thresholds. Use Case Examples: An agency would assess the collective performance of work zones on its roadways in the region relative to established performance targets, such as the number or percent of work zones with delays and queues exceeding specified thresholds (e.g., duration of congestion, maximum or average delays, etc.) in the region.

WZED User(s):




1. Agency, Neighbor Agency, and Regional Crash Performance/Impact Analysis Staff/Tools obtain the relevant Agency and Neighbor Agency Planned and Actual WZED Archive from WZED warehouse.

2. Traffic Impact Performance Analysis Staff/Tools obtain the relevant Agency and Neighbor Agency Planned and Actual WZED Archive from WZED warehouse.

3. Agency, Neighbor Agency, and Regional Crash Performance/Impact Analysis Staff/Tools analyze history and provide crash impact assessments to Agency, Neighbor Agency, and Regional WZ Planning & Design Staff/Tools.

4. Agency, Neighbor Agency, and Regional Traffic Performance/Impact Analysis Staff/Tools analyze history and provide traffic impact assessments to Agency, Neighbor Agency, and Regional WZ Planning & Design Staff/Tools.

5. Agency, Neighbor Agency, and Regional WZ Planning & Design Staff/Tools assess the collective performance of work zones on its roadways in the region relative to established performance targets, such as the number or percent of work zones with delays and queues exceeding specified thresholds (e.g., duration of congestion, maximum or average delays, etc.) in the region..

WZED User Objective: Computing performance of work zones on its roadways in the region relative to established performance targets.

WZED Content:

• Project ID


• Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Event - Reduce Speed Limit



• Regional WZED • Corresponding regional traffic data • Corresponding regional crash data


Use Case 5.2.2 – Computing Average Work Zone Safety Performance Measures by Region, Type of Project, Roadway Type, or Other Stratification


Use Case Description: Agency analysis of collective work zone safety performance for specific types of projects in a region.

Use Case Examples: An agency would strive to determine typical or average values or increases in crash risk in work zones by region, type of work zone project, or other means of stratification.

WZED User(s):




1. Agency, Neighbor Agency, and Regional Crash Impact Performance Analysis Staff/Tools obtain the relevant Agency and Neighbor Agency Planned and Actual WZED Archive from WZED warehouse.


3. Agency, Neighbor Agency, and Regional Crash Impact/ Performance Analysis Staff/Tools analyze history and provide crash impact assessments to Agency, Neighbor Agency, and Regional WZ Planning & Design Staff/Tools.

4. Agency, Neighbor Agency, and Regional Traffic Impact/ Performance Analysis Staff/Tools analyze history and provide traffic impact assessments to Agency, Neighbor Agency, and Regional WZ Planning & Design Staff/Tools.

5. Agency, Neighbor Agency, and Regional WZ Planning & Design Staff/Tools determine typical or average values or increases in crash risk in work zones by region, type of work zone project, or other means of stratification..

WZED User Objective: Determine the average increase in crash risk by work zone category and facility type across multiple work zones.

WZED Content:

• Owner agency


• Contractor/subcontractors • Actual number of phases • Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Actual geometrics associated with each event/subevent • Actual traffic control device(s) associated with each event/subevent



• Regional WZED • Corresponding Regional traffic data • Corresponding Regional crash data


Use Case 5.2.3 – Computing Regional Crash Modification Factors for Specific Work Zone Features, Activities, or Strategies


Use Case Description: Agency analysis to determine a crash modification factor for a specific work zone feature.

Use Case Examples: An agency would perform analyses of specific features or strategies implemented at projects across the region to develop a crash modification factor (or approximation thereof) for a specific work zone feature or strategy (e.g., lane closure, use of positive projection, etc.)

WZED User(s):




1. Agency, Neighbor Agency, and Regional Crash Impact Performance Analysis Staff/Tools obtain the relevant Agency and Neighbor Agency Planned and Actual WZED Archive from WZED warehouse.


3. Agency, Neighbor Agency, and Regional Crash Impact/ Performance Analysis Staff/Tools analyze history and provide crash impact assessments to Agency, Neighbor Agency, and Regional WZ Planning & Design Staff/Tools.

4. Agency, Neighbor Agency, and Regional Traffic Impact/ Performance Analysis Staff/Tools analyze history and provide traffic impact assessments to Agency, Neighbor Agency, and Regional WZ Planning & Design Staff/Tools.

5. Agency, Neighbor Agency, and Regional WZ Planning & Design Staff/Tools develop a crash modification factor (or approximation thereof) for a specific work zone feature or strategy.

WZED User Objective: Determine a crash modification factor for a specific work zone feature across a sample of work zones.

WZED Content:

• Owner agency • Contractor/subcontractors • Actual number of phases


• Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Actual geometrics associated with each event/subevent • Actual traffic control device(s) associated with each event/subevent



• Regional WZED • Corresponding regional traffic data • Corresponding regional crash data


Stakeholder Need: 5.3 Assessing and Enhancing Performance at the National Level

Use Case 5.3.1 – Developing National Work Zone Safety and Mobility Improvement Guidance

WZ Life Cycle Stage: Post Work Zone Performance Analysis

Use Case Description: Guidelines for improving local, regional, and national safety and mobility performance.

Use Case Examples: The FHWA Work Zone Management Program may want to use local, regional, and national WZED to develop guidelines for improving local, regional, and national safety and mobility performance measures.

WZED User(s):

• National Work Zone Safety and Mobility Staff/Tools



1. Crash Impact Performance Analysis Staff/Tools obtain the relevant Agency and Neighbor Agency Planned and Actual WZED Archive from WZED warehouse.


3. Crash Impact/ Performance Analysis Staff/Tools analyze history and provide crash impact assessments to National WZ Safety and Mobility Guidelines Staff/Tools.

4. Traffic Impact/ Performance Analysis Staff/Tools analyze history and provide traffic impact assessments to National WZ Safety and Mobility Guidelines Staff/Tools.

5. National WZ Safety and Mobility Guidelines Staff/Tools assess results and apply them to develop guidelines for improving local, regional, and national safety and mobility performance measures.

WZED User Objective: Develop guidelines for improving local, regional, and national safety and mobility performance measures.

WZED Content:

• Owner agency • Contractor/subcontractors • Actual number of phases • Project ID • Event ID • Sub-event ID


• Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Actual geometrics associated with each event/subevent • Actual traffic control device(s) associated with each event/subevent



• National WZED • Corresponding local, regional, and national safety and mobility performance data

WZED Warehouse Interface Type: Agency system-to-system interface to National tool which integrates WZED with other travel metrics databases for post-construction WZ performance analysis.

Use Case 5.3.2 – Developing Reports of Regional and National Work Zone Safety and Mobility Performance


Use Case Description: Reporting of regional and national safety and mobility performance

Use Case Examples: FHWA and other agencies of the USDOT may want to compute regional and national safety and mobility performance measures for specific stationary work zone types, projects on certain roadway types, or other stratifications.

WZED User(s):

• National Work Zone Safety and Mobility Staff/Tools



1. Crash Impact Performance Analysis Staff/Tools obtain the relevant Agency and Neighbor Agency Planned and Actual WZED Archive from WZED warehouse.


3. Crash Impact/ Performance Analysis Staff/Tools analyze history and provide crash impact assessments to National WZ Safety and Mobility Guidelines Staff/Tools.

4. Traffic Impact/ Performance Analysis Staff/Tools analyze history and provide traffic impact assessments to National WZ Safety and Mobility Performance Measures Staff/Tools.

5. National WZ Safety and Mobility Guidelines Staff/Tools assess results and apply them in computing regional and national safety and mobility performance measures for specific stationary work zone types, projects on certain roadway types, or other stratifications. .

WZED User Objective: Regional and national safety and mobility performance reporting for specific stationary work activities that reduce capacity or access

WZED Content:

• Owner agency • Contractor/subcontractors • Actual number of phases • Project ID


• Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Actual geometrics associated with each event/subevent • Actual traffic control device(s) associated with each event/subevent



• National WZED • Corresponding local, regional, and national safety and mobility performance data

WZED Warehouse Interface Type: Agency system-to-system interface to National tool which integrates WZED with other travel metrics databases for post-construction WZ performance analysis.


CATEGORY 6 – LAW ENFORCEMENT AND EMERGENCY SERVICE PROVIDERS

Stakeholder Need: 6.1 Validate Cited Condition(s) of Traffic Violation

Use Case 6.1.1 – Worker Present in Work Zones Documentation


Use Case Description: Agency documents and archives when workers are present in work zones to support contested citations.

Use Case Examples: Many states have laws that increase fines “when workers are present” or similar wording. Documentation that work activity was occurring at the time of the citation could be useful if citations are contested.

WZED User(s):

• Law Enforcement Performance Analysis Staff/Tools



2. Agency Law Enforcement Performance/Impact Analysis Staff/Tools obtain the relevant Planned and Actual WZED from the Agency WZED warehouse.


3. Agency Law Enforcement Performance/Impact Analysis Staff/Tools analyze the WZED and assess when workers are present in Work Zones to support contested citations.

WZED User Objective: Validate Cited Condition(s) of Traffic Violation

WZED Content:

• Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status

WZED Content Update Frequency: Daily Construction Plan Updates

External Data Needed for User Objective: Law Enforcement Citations

WZED Warehouse Interface Type: Agency system-to-system interface to Agency tool which integrates WZED with Law Enforcement databases for post-construction WZ Law Enforcement performance analysis.

Use Case 6.1.2 – Posted Speed Limits in Work Zones Documentation


Use Case Description: Agency documents and archives posted speed limits in work zones to support contested citations.

Use Case Examples: Some agencies have established policies and procedures to change the posted speed limit during certain work activities and return them to the regular posted speed limit when those work activities are not occurring. A few agencies are pursuing variable speed limit systems that tailor speed limits to specific traffic conditions and locations using electronic speed limit signs.

WZED User(s):






3. Agency Law Enforcement Performance/Impact Analysis Staff/Tools analyze the WZED and assess posted speeds in Work Zones to support contested citations.

WZED User Objective: Validate Cited Condition(s) of Traffic Violation

WZED Content:

• Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Event - Reduce Speed Limit



External Data Needed for User Objective: Law Enforcement Citations


Stakeholder Need: 6.2 Enforcement of Lane Closure/Right-of-Way Access Approval Process

Use Case 6.2.1 – Enforcement of Lane Closure/Right-of-Way Access Approval


Use Case Description: Law enforcement verifies approval of lane closures they encounter.

Use Case Examples: Some agencies rely on enforcement personnel to help ensure that entities and companies do not implement lane closures or other work zones on their facilities without obtaining approval first.

WZED User(s):

• Agency-to-Law Enforcement Work Zone Coordination Staff/Tools



2. Agency-to-Law Enforcement Work Zone Coordination Staff/Tools obtain the relevant Active Operational WZED from the Agency WZED warehouse.

3. Agency-to-Law Enforcement Work Zone Coordination Staff/Tools analyze the WZED and help Law Enforcement verify approval of work zone operations.

WZED User Objective: Enforcement of Lane Closure/Right-of-Way Access Approval Process

WZED Content:


• Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status


External Data Needed for User Objective: Lane Closure/Right-of-Way Access Approval

WZED Warehouse Interface Type: Agency interface (direct or system-to-system) which shares WZED with Law Enforcement Agencies and staff.

Stakeholder Need: 6.3 Monitor and Document Law Enforcement Use on Projects

Use Case 6.3.1 – Monitor Law Enforcement Use on Projects


Use Case Description: Agency documents and archives when law enforcement used at work zones.

Use Case Examples: Agencies (particularly those with a memorandum of understanding [MOU] with law enforcement for work zone enforcement support) with an MOU with Law Enforcement for work zone enforcement support may want to keep track of when and where enforcement efforts occur.

WZED User(s):






3. Agency Law Enforcement Performance/Impact Analysis Staff/Tools analyze the WZED to assist in tracking work zone enforcement support.

WZED User Objective: Monitor and Document Law Enforcement Use on Projects

WZED Content:

• Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Event - Enforcement presence

WZED Content Update Frequency: Daily Law Enforcement Updates



• Law Enforcement WZ enforcement support MOU • Law Enforcement Citation Database


Use Case 6.3.2 – Law Enforcement Work Zone Effectiveness


Use Case Description: Agency analysis of the effectiveness of law enforcement in work zones.

Use Case Examples: Agencies that use law enforcement on work zone projects may want to keep track of when and where enforcement efforts occur to evaluate effectiveness.

WZED User(s):




2. Agency Law Enforcement Performance Analysis Staff/Tools obtain the relevant Planned and Actual WZED from the Agency WZED warehouse.


3. Agency Law Enforcement Performance Analysis Staff/Tools obtain the relevant Traffic Performance Data from Traffic Performance/Impact Analysis Staff/Tools.

4. Agency Law Enforcement Performance Analysis Staff/Tools obtain the relevant Crash Performance Data from Crash Performance/Impact Analysis Staff/Tools.

5. Agency Law Enforcement Performance/Impact Analysis Staff/Tools analyze and effects of law enforcement support on work zone mobility and safety.

WZED User Objective: Monitor and Document Law Enforcement Use on Projects

WZED Content:

• Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Event - Enforcement presence

WZED Content Update Frequency: Daily Law Enforcement Updates


• Law Enforcement WZ enforcement support MOU • Law Enforcement Citation Database


Stakeholder Need: 6.4 Facilitate Law Enforcement Work Zone Planning

Use Case 6.4.1– Facilitate Law Enforcement Work Zone Planning


Use Case Description: Law enforcement monitoring upcoming work zones to help plan enforcement needs.

Use Case Examples: Law enforcement agencies may desire information about upcoming work zones in a region so that they can better plan for law enforcement needs on those work zones.


WZED User(s):





3. Agency-to-Law Enforcement Work Zone Coordination Staff/Tools analyze the WZED to Inform Law Enforcement of upcoming work zone plans.

WZED User Objective: Law Enforcement Monitor Work Zone Law Enforcement Needs

WZED Content:

• Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Time - Planned start date/time of event/subevent • Time - Planned end date/time of event/subevent • Time - Status


• Event - Number of activities requiring Law Enforcement support OR flag indicating event/subevent needs Law Enforcement support



• Daily Construction Plan Updates • Law Enforcement WZ enforcement support MOU


Stakeholder Need: 6.5 Law Enforcement Monitor Activity at Work Site (to deter theft)

Use Case 6.5.1– Law Enforcement Monitor Activity at Work Site (to deter theft)


Use Case Description: Law enforcement monitor activity at work site (to deter theft)

Use Case Examples: Law enforcement wants to know what contracts/subcontractors are working on each job to help them monitor who should and shouldn’t be onsite. For example, general patrols that pass by worksites after hours want to be able to identify suspicious vehicles/activities that do not belong (e.g., a different or bogus company truck used to steal copper wire).

WZED User(s):






3. Agency-to-Law Enforcement Work Zone Coordination Staff/Tools analyze the WZED to Inform Law Enforcement of planned activity at work site to deter theft.

WZED User Objective: Law Enforcement Monitor Contractors and Subcontractors approved onsite

WZED Content:

• Contractor/subcontractors • Project ID • Event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status




• Daily Construction Plan Updates • Law Enforcement WZ enforcement support MOU


Stakeholder Need: 6.6 First Responder Emergency Route Planning

Use Case 6.6.1– Restricted Access to Incidents


Use Case Description: Inform first responders of work zones to enable advance emergency route planning

Use Case Examples: Emergency service providers and law enforcement could better route to incidents or plan for incident response if they are aware of work zone locations that restrict normal access.

WZED User(s):

• First Responder Emergency Route Planning



2. Agency TMC/ATMS/RCRS/ITS Information Integration & Output Staff/Tools and Agency Traveler Information Systems obtain the latest Active Operational WZED from the Agency WZED warehouse.

3. Agency TMC/ATMS/RCRS/ITS Information Integration & Output Staff/Tools and Agency Traveler Information Systems analyze the WZED and provide relevant emergency route information to First Responder emergency route planners.



• Predetermine best routes to access incidents in Work Zone • Predetermine best route around WZ to access incidents

WZED Content:

• Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Planned begin location of event/subevent • Location - Planned end location of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Planned start date/time of event/subevent • Time - Planned end date/time of event/subevent • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status



WZED Warehouse Interface Type: Agency interface (direct or system-to-system) which shares WZED with First Responder Agencies and staff.


CATEGORY 7 – CAV HARDWARE NEEDS AND SYSTEM READINESS TO ACCOMODATE

Stakeholder Need: 7.1 Alert/Inform CAV of Presence of Work Zones

Use Case 7.1.1 – Dissemination of Work Zone Driver Beginning and End to CAV


Use Case Description: Dissemination of work zone, beginning, end, advisory and warning data to CAV for display to driver. (Assumes driver will control CAV through work zone.)

Use Case Examples: Due to the dynamic nature of work zones, CAV may initially use work zone data elements similar to those conveyed through traveler information systems (i.e., when, where, and what is different about the roadway) and require driver intervention. At mid-level vehicle automation, similar WZED could be used by the vehicle to determine if human control is required.

Dissemination of Work Zone, Beginning, End, Advisory and Warning Data to CAV for display to driver.

WZED User(s):

• Agency Connected & Automated Vehicles Interface



2. Agency Interface to Connected & Automated Vehicles obtains the latest Active Operational WZED to the Agency WZED warehouse.


3. Agency Interface to Connected & Automated Vehicles analyze the WZED and provides Relevant Work Zone Information to Connected & Automated Vehicles.

4. Connected & Automated Vehicles analyze the Relevant Work Zone Information and returns updated Work Zone Information they capture as they traverse the work zone.

5. Agency Interface to Connected & Automated Vehicles analyze the updated Work Zone Information from Connected & Automated Vehicle and updates Active Operational WZED in the WZED warehouse.


• Inform Connected and Automated Vehicle tools of unmapped WZ, requiring driver intervention

• Issue WZ Advisories and warnings to drivers of connected and automated vehicles

WZED Content:

• Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Recurring flag • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Event - Actual number of lanes to be closed • Event - Description of actual lanes to be closed • Event - Expected effect on travel time/delay/queuing • Event - Temporary restrictions in place • Metadata - Indicator that a change to an event/subevent entry has been made


External Data Needed for User Objective: Agency or third-party connected vehicle and automated vehicle systems (in the cloud)

WZED Warehouse Interface Type: Agency system-to-system interface to agency or third-party connected vehicle and automated vehicle system (in the cloud) which shares relevant WZED for WZ navigation.

Stakeholder Need: 7.2 CAV Navigation (Information to plan and execute trip)


Use Case 7.2.1 – CAV Route Navigation Selection


Use Case Description: Connected and Automated Vehicle Systems/Staff use work zone information to plan and recommend route.

Use Case Examples: Connected and Automated Vehicle Systems/Staff use WZED to plan and recommend routes to drivers through and around work zones to optimize connected and automated vehicle travel

WZED User(s):








WZED User Objective: Plan and recommend routes to drivers through and around work zones to optimize connected and automated vehicle travel

WZED Content:


• Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Recurring flag • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status • Event - Actual number of lanes to be closed • Event - Description of actual lanes to be closed • Event - Expected effect on travel time/delay/queuing • Event - Temporary restrictions in place • Metadata - Indicator that a change to an event/subevent entry has been made


External Data Needed for User Objective: Agency or third-party connected vehicle and automated vehicle systems (in the cloud)

WZED Warehouse Interface Type: Agency system-to-system interface to agency or third -arty connected vehicle and automated vehicle system (in the cloud) which shares relevant WZED for WZ navigation.

Stakeholder Need: 7.3 CAV Lane Guidance (safe speed and travel path guidance)

Use Case 7.3.1 – CAV Lane Guidance


Use Case Description: Connected and Automated Vehicle Systems/Staff use work zone information to plan and recommend travel lanes and path.

Use Case Examples: Public and Private Connected and Automated Vehicle Systems/Staff use WZED to plan and recommend lane level advisories and warnings necessary to support their safe navigation through a work zone.

WZED User(s):









WZED User Objective: Plan and recommend travel lanes and path to drivers through work zones.

WZED Content:

• Project ID • Event ID • Sub-event ID • Location - Name of roadway where event/subevent is located • Location - Roadway classification of roadway where event/subevent is located • Location - Facility type of roadway where event/subevent is located • Location - Direction of travel of event/subevent • Location - Actual begin location of event/subevent • Location - Actual end location of event/subevent • Time - Recurring flag • Time - Actual start date/time of event/subevent • Time - Actual end date/time of event/subevent • Time - Status


• Event - Actual number of lanes to be closed • Event - Description of actual lanes to be closed • Event - Expected effect on travel time/delay/queuing • Event - Temporary restrictions in place • Metadata - Indicator that a change to an event/subevent entry has been made


External Data Needed for User Objective: Agency or Third party connected vehicle and automated vehicle systems (in the cloud)

WZED Warehouse Interface Type: Agency system-to-system interface to agency or Third party connected vehicle and automated vehicle system (in the cloud) which shares relevant WZED for WZ navigation.



ACKNOWLEDGMENTS

The WZED Framework development team would like to thank the industry stakeholders who provided valuable input, identified needs, and participated in the framework development workshops in the spring and fall of 2018. We would also like to acknowledge the timely and high-quality support provided by the U.S. Department of Transportation.



REFERENCES

1. P. Okunieff, Work Zone Event Data (WZED) – Data Dictionary Report (FHWA-HOP-20-020) Task 4 report Federal Highway Administration (FHWA) Work Zone Data Initiative (WZDI) project.

2. J. Ullman and M. Finley, Work Zone Event Data (WZED) Needs and Opportunities (FHWA HOP-20-018) Task 2 report Federal Highway Administration (FHWA) Work Zone Data Initiative (WZDI) project.

3. J. Schroeder, Work Zone Event Data Collection and Management Implementation Guide (FHWA-HOP-20-021) Task 7 report Federal Highway Administration (FHWA) Work Zone Data Initiative (WZDI) project.

4. Best Practices in Work Zone Assessment, Data Collection, and Performance Evaluation. Scan Team Report, NCHRP 20-68A Scan 08-04. Transportation Research Board of the National Academies, Washington, DC. March 2011.

5. G.L. Ullman, G. Pesti, and R. Klein. Guidance on Data Needs, Availability, and Opportunities for Work Zone Performance Measures Report No. FHWA-HOP-13-011. FHWA, U.S. Department of Transportation, Washington, DC. March 2013.

6. G.L. Ullman, T.J. Lomax, F. Ye, and T. Scriba. Work Zone Performance Measures Pilot Test. Report No. FHWA-HOP-11-022. FHWA, U.S. Department of Transportation, Washington, DC. April 2011.

7. L. Theiss, G. Ullman and A. Moinet. Guide to Project Coordination for Minimizing Work Zone Mobility Impacts. Report No. FHWA-HOP-16-013. FHWA, U.S. Department of Transportation, Washington, DC. April 2016.

8. U.S. Code of Federal Regulations, Title 23, Chapter 1, Section 101a.

9. Additional information on TSMO can be found on the FHWA website: https://ops.fhwa.dot.gov/plan4ops/focus_areas/tsmo/what_is_tsmo.htm

10. 23 CFR 630.1088(c). P.D. Pant, Smart Work Zone Systems, https://ops.fhwa.dot.gov/wz/workshops/accessible/Pant_paper.htm

https://ops.fhwa.dot.gov/plan4ops/focus_areas/tsmo/what_is_tsmo.htm

https://ops.fhwa.dot.gov/plan4ops/focus_areas/tsmo/what_is_tsmo.htm

https://ops.fhwa.dot.gov/wz/workshops/accessible/Pant_paper.htm

U.S. Department of Transportation Federal Highway Administration

Office of Operations 1200 New Jersey Avenue, SE

Washington, DC 20590

Office of Operations Web Site https://ops.fhwa.dot.gov

January 2020

FHWA-HOP-02-019