Integrated Delivery of SHRP 2 Renewal Research Projects (2014)

Below is the uncorrected machine-read text of this chapter, intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text of each book. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

76 Chapter 4 Conceptualized Integration Tool Introduction In order to apply the renewal research program results in a systematic and integrated fashion, the ability of transportation agencies to apply rapid renewal could be enhanced through development of a Project Builder Application (PBA) tool. The concept for this tool is a web-based application that would assist agency users in determining which renewal products might be suitable for their agency’s needs. The framework for the PBA tool is based on assessing technical user needs in order to provide guidance in matching appropriate research products with specific infrastructure renewal projects. Alternatively, agency staff focused on rapid renewal at an administrative or program level can use the tool to evaluate the renewal research program results more broadly and to determine which, if any, of the products should be considered for adoption by the agency. By interacting with the user through a series of simple questions and menu options, the PBA will determine precisely what products are most relevant to the user’s needs. Although the tool is still a conceptualized model, its elements are described below in sufficient detail to allow its development as a working software application. Framework/Model Description In designing the framework for the PBA tool, the primary focus is on getting users connected to the relevant product information from the renewal research program. This model requires that the tool analyze user needs and interests and determine what subset of products could assist with those needs. Because of the variety of products available, it is appropriate to consider that different groups of users will be interested in different aspects of the overall program, depending on their roles and responsibilities. By tailoring the approach to each group of users, the PBA tool framework will be able to gather user input in a way that allows the tool to tailor its results to the individual user. As illustrated in Figure 4.1, defining the user audience helps the PBA tool focus on the strategic objectives that are most important to that group. Based on these objectives, the tool can interact with the user to determine his or her specific requirements. To facilitate this, the PBA tool framework incorporates a number of user requirements into its design, which should cover many of the potential use cases for the renewal research program results. The interaction allows the tool to narrow down the user requirements and translate them into functional requirements for the application. Implementing the functional requirements takes the user to a customized set of results covering specifically those research products most relevant to the user’s needs.

77 Figure 4.1. Outline of the PBA tool framework. User Audiences The PBA tool framework is designed to serve user audiences across multiple levels of agency organizations and with varying areas of responsibility. At administrative and program-oriented levels, it can be a resource for agency executives and directors to evaluate research products for adoption within their agencies. For agency personnel at the functional or technical level, such as designers and engineers, the PBA can identify specific products to help with an upcoming project or resolve a current problem. The user audience roles in this framework are meant to be descriptive and may correspond to different titles within an agency’s organizational structure. The subsequent analysis with respect to strategic objectives and user requirements will help the tool validate that the results it provides are appropriate to individual users in their specific roles. Strategic Objectives For each audience, the PBA framework was developed by identifying strategic objectives to reflect the high-level outcomes that group of users would need from the tool. The strategic objectives indicate which benefits the user might expect to achieve from the renewal research program results. In addition, the objectives help the PBA guide its interaction with the user and better refine the requirements to be addressed. User Requirements The user requirements within the PBA framework expand on the strategic objectives to more precisely define needs according to the user’s job function. A different set of requirements may apply based on the type of need (project-level, network-level, or program-level), the agency infrastructure involved (pavements, bridges, tunnels, etc.), and the phase of project development (scoping and preliminary design, final design, or contracting and construction). Many of these requirements correspond closely to the user needs identified in Chapter 3. The PBA framework builds on the user needs categories to align these requirements with the related strategic objectives. Functional Requirements In the PBA framework, the functional requirements describe how the tool gathers the information necessary to identify a specific user’s requirements and match these to the appropriate research products. Based on user responses to specific questions and selection of different options, the tool will filter through all of the renewal research program results. Using an automated flexible algorithm, the PBA then sorts out specific product options for consideration by the user. User Audiences Strategic Objectives User Requirements Functional Requirements

78 Together with user input, the functional requirements determine the output of the PBA tool. This framework calls for output in the form of a custom guide or implementation kit, which presents the user with product recommendations and indicates what needs could be addressed with each product. The tool display should include information on the format in which the products are available, such as specifications, software, testing equipment, or training courses, as well as including links to additional resources and to the products themselves. Features and Functionality Using the outline of the PBA framework, the features and functionality of the tool are described in more detail in Tables 4.1 through 4.20. Each user audience, ranging from a general user to an upper-management director to a particular technical professional, has one or more strategic objectives identified, together with a set of user and functional requirements within each objective. Table 4.1. Strategic Objectives and Tool Requirements for the General User User Requirements Functional Requirements Strategic Objective 1: Identify tools and research products that support the application of rapid renewal to agency infrastructure.  Design concepts and treatment selection processes to support rapid renewal projects.  Guidance for application of innovative tools in a rapid renewal context.  Collect input to indicate focus areas of particular agency need on a program or project level. Based on this input, recommend information from SHRP 2 Renewal projects to include, corresponding to focus areas for pavements, bridges, utilities and railroads, nondestructive testing, and project delivery strategies.  Collect input regarding agency experience with rapid renewal and existing design approaches. Based on this input, recommend appropriate design concepts from SHRP 2 R02, R04, R05, R19A, and R21. Strategic Objective 2: Support implementation of new project strategies relevant to the assets and systems involved in a rapid renewal project.  Reference specifications, model procedures, and other best practices related to construction of rapid renewal projects.  Tools for risk management and fatigue mitigation on rapid renewal projects with innovative approaches and accelerated schedules.  Collect input to determine need for model specifications and construction procedures in renewal focus areas. Recommend appropriate resources from SHRP 2 R02, R04, R05, R06C, R19A, and R21.  Collect input regarding approach to risk management and construction scheduling. Recommend appropriate resources from SHRP 2 R03 and R09.

79 Table 4.2. Strategic Objectives and Tool Requirements for the Director/Administrator User Requirements Functional Requirements Strategic Objective 1: Evaluate innovative tools and approaches to rapid renewal projects for potential agency adoption.  Information to support further evaluation of research products being considered for adoption by a highway agency.  Collect input regarding focus areas where the agency is seeking improvements, such as pavements, bridges, utilities and railroads, nondestructive testing, and project delivery strategies. Based on this input, include or exclude information from SHRP 2 Renewal projects for those areas. Strategic Objective 2: Enable implementation of new procedures and facilitate change by encouraging agency personnel through transition.  Training materials and best practices to provide agency staff with the resources necessary to implement new research products into existing business processes.  Master agreements and coordination strategies for collaborating with other stakeholders on rapid renewal projects.  Assess agency program interests to include or exclude consideration of products related to accelerated bridge construction, PCP/modular pavement, composite pavements, and preservation treatments for high-volume roads. Based on this input, recommend appropriate webinars and training materials from SHRP 2 R04, R05, R21, and R26.  Collect input regarding agency use of performance specifications, 5- dimensional project management, risk management processes, roadway project impact assessment, and utility conflict management. Based on this input, recommend appropriate webinars and training materials from SHRP 2 R07, R09, R10, R11, and R15B.  Collect input regarding existing processes for highway agency- railroad interactions. Recommend master agreements and best practices for interaction from SHRP 2 R16 and R16A. Table 4.3. Strategic Objectives and Tool Requirements for Research/Information Technology User Requirements Functional Requirements Strategic Objective 1: Develop criteria to evaluate innovative devices and tools for rapid renewal projects.  Geoconstruction technologies selection process/tool (GEOTECH TOOLS Selection and Guidance System) that can be considered for adoption (or further evaluated) by a highway agency.  Long-life rehabilitation treatment selection process/tool (Guidelines for Long-Life Pavement Renewal scoping tool) that can be considered for adoption (or further evaluated) by a highway agency.  Preservation treatment/strategy selection process (i.e., evaluation criteria, selection matrices, life-cycle costing, etc.) for high-volume roads that can be considered for adoption (or further evaluated) by a highway agency.  Collect input regarding geoconstruction technology selection process and include or exclude tools from SHRP 2 R02.  Collect input regarding long-life rehabilitation treatment selection process and include or exclude tool from SHRP 2 R23.  Collect input regarding preservation treatment selection process and include or exclude recommendations from SHRP 2 R26. Strategic Objective 2: Identify changes required in existing systems and new processes that require integration into those systems.  Information on new technologies that can be considered for adoption by a highway agency and  Collect input on nondestructive testing devices/tools agency would consider adopting and provide information

80 require technical support for integration into agency systems.  Recommended changes in procedures that impact technical workflows or affect existing information architectures. regarding technical capabilities from SHRP 2 R06A, R06B, R06C, R06E, R06F, and R06G.  Collect input regarding approach to bridge renewal and include or exclude technical considerations for accelerated bridge construction (ABC) technology from SHRP 2 R04.  Collect input regarding agency experience with PCP/modular pavement and provide information about design and production technology from SHRP 2 R05. Table 4.4. Strategic Objectives and Tool Requirements for Project Managers User Requirements Functional Requirements Strategic Objective 1: Improve and accelerate decision-making on rapid renewal projects.  Strategies, tools, and procedures for managing complex roadway projects.  Collect input regarding factors being included in project management, such as cost, schedule, and quality. Based on inclusion of context and financing factors, evaluate project complexity and need for 5- dimensional project management from SHRP 2 R10. Strategic Objective 2: Develop appropriate construction schedules while mitigating risks.  Procedures for performing a risk assessment of schedules and identifying alternatives that provide the lowest levels of risk while still maintaining the desired project schedule.  Fatigue mitigation strategies, tools, and practices that can be put into place on a rapid renewal highway project that uses a construction scheduling approach with increased risk of worker fatigue.  Evaluate aggressiveness of construction schedule and collect input regarding anticipated construction closures. Recommend potential to add fatigue training and countermeasures based on SHRP 2 R03.  Collect input on construction crew work shifts and provide schedule guidance for night shifts, extended work, and irregular shifts based on SHRP 2 R03. Table 4.5. Strategic Objectives and Tool Requirements for Project Designers/Engineers User Requirements Functional Requirements Strategic Objective: Apply risk management methods to project development process.  Risk register and procedures for identification, assessment, and analysis of project risk involved in a roadway project.  Procedures for risk management and contingency planning.  Establish project baseline assumptions in order to proceed with risk identification and management based on information from SHRP 2 R09.  Collect project risk factors to include for analysis using SHRP 2 R09. Table 4.6. Strategic Objectives and Tool Requirements for Traffic/Safety Engineers. User Requirements Functional Requirements Strategic Objective 1: Reduce traffic disruption and mitigate road user impacts from rapid renewal projects.  Tools to assess impacts of a roadway project on corridors/networks.  Performance measures and decision support systems to evaluate the impacts of work zones in a roadway project.  Collect input on construction closures and work zone impacts. To analyze corridor and network effects, identify

81  Strategies for roadway projects to minimize disruption due to work zone impacts.  Operational scenarios and mitigation strategies for work zone impacts. decision support system using software tools from SHRP 2 R11. Table 4.7. Strategic Objectives and Tool Requirements for Bridge/Structure Designers User Requirements Functional Requirements Strategic Objective 1: Design bridge systems for extended service life (beyond 100 years).  Design concepts, details, considerations, and procedures for systematically designing new and existing bridge systems (and their various elements, subsystems, and components) for service life and durability.  Identification of suitable bridge system alternatives that satisfy project requirements and selection of optimum alternative based on assessment of cost-effectiveness (LCCA), performance, and other factors.  Procedures associated with construction of long-life bridges and the various elements, subsystems, and components.  Collect input regarding bridges that are included in project, if any.  Collect bridge characteristics related to components such as deck joints, columns, and piles. Recommend consideration of service life factors based on information from SHRP 2 R19A.  For existing bridges, recommend preservation strategies and activities based on SHRP 2 R19A. Strategic Objective 2: Apply accelerated bridge construction (ABC) techniques to rapid renewal projects.  Design concepts, details, considerations, and guidance for a variety of ABC technologies (prefabricated bridge elements/systems and corresponding bridge movement techniques and equipment) for possible use in accelerated renewal of existing bridges (40- to 130-ft spans).  Sample standard plans and detail sheets that can be adapted for use in the construction plans of a bridge renewal project that will incorporate ABC technologies.  Reference specification (recommended AASHTO-formatted) information that can be used in developing LRFD design specifications for ABC elements and systems.  Reference specification (recommended AASHTO-formatted) information that can be used in developing LRFD construction specifications for ABC elements and systems.  Procedures associated with ABC construction, including fabrication of elements, subsystems, and components off alignment and movement of the system into place using proper equipment.  Collect input regarding project schedule and bridge characteristics to identify potential bridge replacements that could benefit from ABC based on SHRP 2 R04.  Collect input regarding renewal of existing bridges and apply guidelines for decision making on whether to consider ABC approach using SHRP 2 R04.  Collect concepts for existing bridge components and recommend appropriate ABC design plans and construction specifications using SHRP 2 R04. Strategic Objective 3: Identify tools and procedures to evaluate concrete bridge deck deterioration.  Identification of suitable NDT devices/tools for evaluating/detecting concrete bridge deck deterioration (specific distresses [e.g., delamination, corrosion, vertical cracking, concrete degradation] and overall condition), based on device/tool performance ratings for accuracy, repeatability, speed, ease of use, and cost.  Procedures and illustrations for using various NDT devices/tools to evaluate concrete bridge deck deterioration.  Collect project input regarding concrete bridge decks and recommend tools for evaluating bridge deck condition using SHRP 2 R06A.

82 Table 4.8. Strategic Objectives and Tool Requirements for Pavement Designers User Requirements Functional Requirements Strategic Objective 1: Identify and evaluate structural design considerations and select appropriate options for design concepts and procedures.  Suitability of using performance specifications on a particular rapid renewal project.  Collect input regarding agency use of method specifications or performance specifications. Provide framework for assessing viability of performance specifications for project from SHRP 2 R07. Strategic Objective 2: Determine the suitability of modular pavement systems for preservation, rehabilitation, and reconstruction projects.  Suitability of PCP/modular pavement as a preservation/rehabilitation treatment (i.e., intermittent application) for an existing concrete pavement.  Suitability of PCP/modular pavement as a rehabilitation/reconstruction treatment (i.e., continuous application) for an existing concrete or asphalt pavement.  Structural design (thickness, joints, reinforcement, etc.) for PCP/modular pavement used as a preservation/rehabilitation treatment (i.e., intermittent application) for an existing concrete pavement.  Structural design (thickness, joints, reinforcement, etc.) for PCP/modular pavement used as a rehabilitation/reconstruction treatment (i.e., continuous application) for an existing concrete or asphalt pavement.  Collect input regarding agency experience with PCP/modular pavement and provide design guidelines based on SHRP 2 R05.  Collect input regarding agency experience with PCP/modular pavement and provide design guidelines based on SHRP 2 R05.  Collect project design requirements and recommend decision-making process to evaluate whether project is a suitable candidate for PCP/modular pavement using SHRP 2 R05.  Collect project design requirements and recommend decision-making process to evaluate whether project is a suitable candidate for PCP/modular pavement using SHRP 2 R05. Strategic Objective 3: Design new composite pavements to increase performance and achieve long life.  Feasibility and cost-effectiveness of HMA/PCC or PCC/PCC composite pavement as a long-life pavement option on a new roadway project or roadway reconstruction project.  Structural design (thickness, joints, reinforcement, etc.) for a proposed long-life HMA/PCC or PCC/PCC composite pavement (new or reconstructed roadway).  Collect input for project life-cycle cost analysis and evaluate potential for composite pavement as the preferred alternative. Recommend guidelines for comparing conventional pavements with composite pavements from SHRP 2 R21.  Collect project design requirements and recommend suitable composite pavement designs if appropriate based on SHRP 2 R21. Strategic Objective 4: Identify renewal approaches to achieve long life that use existing pavements in place.  Preliminary/approximate structural design (thickness primarily) of different long-life rehabilitation options (including reconstruction [i.e., remove/replace]) for an existing asphalt, concrete, or composite pavement, as a basis for rehabilitation type selection.  Suitable long-life rehabilitation options (including reconstruction [i.e., remove/replace]) for an existing asphalt, concrete, or composite pavement.  Guide specification information that can be used in developing material and/or construction specifications for the long-life rehabilitation option (including  Collect input regarding condition of existing pavement and identify whether it can be used in place based on SHRP 2 R23.  Collect project design requirements and evaluate potential for long-life pavement designs using existing pavement in place. Recommend narrowing down specific designs using scoping tool from SHRP 2 R23.

83 reconstruction [i.e., remove/replace]) selected for an existing asphalt, concrete, or composite pavement. Table 4.9. Strategic Objectives and Tool Requirements for ROW Engineers. User Requirements Functional Requirements Strategic Objective 1: Coordinate activities related to utilities, railroads, and other features within the project right-of-way.  Communication and coordination of utility conflict information with stakeholders (utility owners, one-call providers).  Coordination of activities for a roadway project that will cross a railroad right-of-way.  Collect input regarding availability of utility location information and coordination with utility stakeholders. Recommend decision support tool and best practices based on SHRP 2 R01 and R01A.  Collect input on agency practices for utility conflict management. Recommend appropriate tools and best practices such as a utility conflict matrix based on SHRP 2 R15B.  Collect project information to include or exclude involvement of railroad right-of-way. Based on this input, recommend appropriate model agreements based on SHRP 2 R16. Table 4.10. Strategic Objectives and Tool Requirements for Utilities Engineers. User Requirements Functional Requirements Strategic Objective 1: Locate and track utility installations located within a rapid renewal project.  Identification of utility-locating/characterizing technology for use in a roadway project.  Procedures for tracking and evaluating utility installation data for a roadway project.  Procedures for providing notification of changes in utility information or status within the right-of-way.  Collect input regarding availability of utility location information and recommend decision support tool to select utility-locating methods from SHRP 2 R01.  Collect information on existing utility tracking practices and recommend utility database model based on SHRP 2 R01A. Strategic Objective 2: Manage and resolve utility conflicts as part of project activities.  Tools for management of utility conflicts and relocation.  Procedures for tracking utility conflict resolution and milestones.  Communication and coordination of utility conflict information with stakeholders (utility owners, one-call providers).  Collect input on agency practices for utility conflict management. Recommend appropriate tools and best practices, such as a utility conflict matrix based on SHRP 2 R15B. Table 4.11. Strategic Objectives and Tool Requirements for Railroad Liaisons User Requirements Functional Requirements Strategic Objective: Facilitate relationships and agreements related to roadway projects that impact railroads.  Master project agreement between railroad and highway agency for roadway project that involves railway.  Preliminary engineering agreement for reviews of  Collect project information to include or exclude involvement of railroad right-of-way. Based on this input, recommend appropriate model agreements based on SHRP 2 R16.

84 roadway project that will cross a railroad right-of-way.  Model project agreements for typical areas where roadway projects impact railroads (resurfacing, highway overpass, warning devices, pipe and wire).  Coordination of activities for a roadway project that will cross a railroad right-of-way.  Collect input regarding project coordination between agency and railroad. Provide guidelines for best practices based on SHRP 2 R16A. Table 4.12. Strategic Objectives and Tool Requirements for Environmental Engineers User Requirements Functional Requirements Strategic Objective: Expedite approvals required on rapid renewal projects.  Identification of project agreements that may contain environmental requirements.  Coordination of project plans and activities that may be subject to environmental review.  Collect project information to include or exclude involvement of railroad right-of-way and provide review of appropriate model agreements based on SHRP 2 R16. Table 4.13. Strategic Objectives and Tool Requirements for Geotechnical Engineers User Requirements Functional Requirements Strategic Objective: Evaluate and specify geoconstruction technology options for projects dealing with unstable soils.  Expected cost of a geoconstruction technology as a candidate for a roadway project.  Design details and procedures for a geoconstruction technology selected for a roadway project involving embankment construction over unstable soils or working platform improvement.  Geoconstruction technologies that are the best options for a roadway project involving embankment construction over unstable soils or working platform improvement.  Reference specification (existing or example) information that can be used in developing material, system, and/or constructions specifications for a geoconstruction technology selected for a roadway project.  Construction procedures for a geoconstruction technology selected for a roadway project and QC/QA methods typically used for the technology.  Collect input regarding project activities involving construction over unstable soils, working platform stabilization, or widening and expansion of existing roadways. Based on this input, include or exclude appropriate geoconstruction technology options from SHRP 2 R02.  Collect input parameters for project dimensions and calculate expected costs for geoconstruction technology based on parameters and information from SHRP 2 R02.  Identify project mitigation strategies for dealing with unfavorable subsurface conditions and recommend guidance for design and specifications based on SHRP 2 R02.

85 Table 4.14. Strategic Objectives and Tool Requirements for Plan Specifications and Engineering (PS&E) Engineers User Requirements Functional Requirements Strategic Objective 1: Develop effective specifications for rapid renewal projects for various pavement types and different contracting scenarios (design-build, design-bid-build, etc.).  Suitability of using performance specifications on a particular rapid renewal project.  Guide specification information that can be used in developing a performance specification for HMA pavement (design [if applicable], materials, and construction) as part of a design-bid-build, design-build, or warranty type project.  Guide specification information that can be used in developing a performance specification for PCC pavement (design [if applicable], materials, and construction) as part of a design-bid-build, design-build, or warranty type project.  Guide specification information that can be used in developing a performance specification for precast/modular concrete pavement (materials, fabrication, and installation) as part of a design-bid-build project.  Guide specification information that can be used in developing a performance specification for pavement (design, materials, construction, maintenance, and handback) as part of a design- build-operate-maintain project.  Guide specification information that can be used in developing a performance specification for pavement foundation (embankment fill, subgrade, subbase) (equipment and construction) using roller-integrated compaction monitoring technology.  Collect input regarding agency use of method specifications or performance specifications. Provide framework for assessing viability of performance specifications for project from SHRP 2 R07.  Identify project delivery approach, such as design-build, design-bid-build, design-build- operate-maintain. Recommend suitable performance specification elements and risk allocation based on SHRP 2 R07.  Collect input on project parameters and construction requirements. Recommend guidance for identifying parameters critical to performance based on SHRP 2 R07.  Collect project-specific information to include or exclude elements such as HMA or PCC pavement, concrete bridge decks, embankment or pavement foundation, precast/modular pavement, and work zone traffic control. Provide corresponding performance specification templates from SHRP 2 R07.  Guide specification information that can be used in developing a performance specification for PCC bridge deck (design [if applicable], materials, and construction) as part of a design-bid-build or design-build project.  Guide specification information that can be used in developing a performance specification for work zone traffic control (traffic management plan and construction sequence) (design, materials, and construction) as part of a rapid renewal project.  Strategic Objective: Identify and allocate risks of performance specifying to all parties, including project owner, contractor, and suppliers.  Risk register and procedures for identification, assessment, and analysis of project risk involved in a roadway project.  Procedures for risk management and contingency planning.  Collect base project description and recommend risk management planning tools based on SHRP 2 R09.  Collect input on project objectives. Suggest contracting and risk allocation methods based on information from SHRP 2 R09.

86 Table 4.15. Strategic Objectives and Tool Requirements for Contract/Construction Managers User Requirements Functional Requirements Strategic Objective 1: Identify tools to reduce costs for rapid renewal projects.  Risk register and procedures for identification, assessment, and analysis of project risk involved in a roadway project.  Procedures for risk management and contingency planning.  Strategies, tools, and procedures for managing complex roadway projects.  Collect input regarding project risks. Recommend appropriate risk management forms and templates from SHRP 2 R09.  Collect input regarding project cost drivers and constraints. Identify tools for managing cost uncertainty and quantifying contingencies from SHRP 2 R10. Strategic Objective 2: Implement desired project schedule while mitigating risks.  Procedures for performing a risk assessment of schedules and identifying alternatives that provide the lowest levels of risk while still maintaining the desired project schedule.  Fatigue mitigation strategies, tools, and practices that can be put into place on a rapid renewal highway project that uses a construction scheduling approach with increased risk of worker fatigue.  Evaluate aggressiveness of construction schedule and collect input regarding anticipated construction closures. Recommend potential to add fatigue training and countermeasures based on SHRP 2 R03.  Collect input on construction crew work shifts and provide schedule guidance for night shifts, extended work, and irregular shifts based on SHRP 2 R03.

87 Table 4.16. Strategic Objectives and Tool Requirements for Construction Engineers User Requirements Functional Requirements Strategic Objective 1: Apply model specifications and procedures for projects involving modular pavements.  Model specification information that can be used in developing material, panel fabrication, and panel installation specifications for PCP/modular pavement technology selected for preservation/rehabilitation (i.e., intermittent application) of an existing concrete pavement.  Model specification information that can be used in developing material, panel fabrication, and panel installation specifications for PCP/modular pavement technology selected for rehabilitation/reconstruction (i.e., continuous application) of an existing concrete or asphalt pavement.  Procedures associated with constructing (fabricating panels at the plant and installing them at the jobsite) PCP/modular pavement technology selected for preservation/rehabilitation (i.e., intermittent application) of an existing concrete pavement.  Procedures associated with constructing (fabricating panels at the plant and installing them at the jobsite) PCP/modular pavement technology selected for rehabilitation/reconstruction (i.e., continuous application) of an existing concrete or asphalt pavement.  Collect input regarding agency experience with PCP/modular pavement. Recommend model specifications and procedures from SHRP 2 R05.  Collect existing agency practices for PCP/modular pavement and provide fabrication and installation guidelines from SHRP 2 R05. Strategic Objective 2: Apply model specifications and procedures for long-life composite pavements.  Guide specification information that can be used in developing material and/or construction specifications for long-life HMA/PCC or PCC/PCC composite pavement selected for a new roadway or roadway reconstruction project.  Procedures associated with constructing a long-life HMA/PCC or PCC/PCC composite pavement selected for a new roadway or roadway reconstruction project.  Collect project design requirements and recommend suitable composite pavement designs if appropriate based on SHRP 2 R21.  Collect input regarding available composite pavement materials. Recommend performance models, specifications, and software programs from SHRP 2 R21. Strategic Objective 3: Identify tools for real-time monitoring of the quality of HMA paving mats.  Identification of a suitable NDT device/tool for real- time monitoring of the quality of HMA paving mats, either immediately after mat placement (measurement of localized cold spots) and/or during mat compaction (measurement of density).  Procedures and illustrations for using various NDT devices/tools to measure and evaluate in real time the quality of HMA paving mats.  Model specification information that can be used in developing quality control (QC) and/or quality assurance (QA) specifications for the Pave-IR thermal profile measurement system.  Model specification information that can be used in  Collect input regarding processes for evaluating uniformity of HMA during paving operations and recommend devices/tools for collecting measurements from SHRP 2 R06C.  Collect input on framework for project QC/QA of density for HMA paving mats. Provide guidelines for integrating NDT devices/tools that measure quality and uniformity into specifications based on SHRP 2 R06C.

88 developing QC and/or QA specifications for the GPR density measurement system. Strategic Objective 4: Identify tools and procedures for real-time measurement of PCC pavement smoothness.  Procedures for using various non-contact, real-time profile measuring systems to measure the profile and compute the smoothness of new PCC pavement.  Model specification information that can be used in developing QC specifications (as part of a quality management plan [QMP]) for non-contact, real-time profile measuring systems for concrete paving.  Collect project PCC pavement smoothness requirements. Recommend guidelines and specifications for smoothness from SHRP 2 R06E.  Collect input regarding PCC pavement smoothness measurement processes and recommend real-time smoothness measurement technologies based on SHRP 2 R06E. Table 4.17. Strategic Objectives and Tool Requirements for Materials Engineers User Requirements Functional Requirements Strategic Objective 1: Reduce quality assurance burden during rapid renewal projects.  Identification of suitable NDT devices/tools for real- time measurement and evaluation of construction materials.  Procedures and model specification information that can be used in developing QC/QA specifications involving various NDT devices/tools.  Collect project input regarding concrete bridge decks and recommend tools for evaluating bridge deck condition using SHRP 2 R06A.  Collect input on procedures for monitoring quality of HMA paving mats. Provide guidelines and recommend tools that measure quality and uniformity based on SHRP 2 R06C.  Collect input on procedures for monitoring smoothness of PCC pavements. Provide guidelines and recommend tools for real-time measurement based on SHRP 2 R06E. Strategic Objective 2: Apply spectroscopy to analyze the chemical composition of complex mixtures.  Standard of practice for identifying chemical admixtures in fresh PCC using the Attenuated Total Reflectance Fourier Transform Infrared (ATR-FTIR) spectroscopy device, and procedures for operating the ATR-FTIR spectroscopy device in the field.  Standard of practice for determining titanium content in traffic paints using the X-ray fluorescence (XRF) spectroscopy device, and procedures for operating the XRF spectroscopy device in the field.  Collect information regarding use of chemical admixtures in PCC and the need to verify concentrations. Recommend including or excluding spectroscopy for identification of admixtures based on SHRP 2 R06B.  Collect information regarding quality control process for traffic paints and testing of metal content. Recommend including or excluding spectroscopy for fingerprinting of paints based on SHRP 2 R06B.

89 Table 4.18. Strategic Objectives and Tool Requirements for Maintenance/Preservation Engineers User Requirements Functional Requirements Strategic Objective 1: Evaluate pavement structural condition and identify candidates for preservation or rehabilitation.  Procedures and illustrations for using high-speed continuous deflection equipment to collect deflection data and to analyze the data to support network-level pavement management activities (e.g., identifying structurally deficient/weak areas that can be investigated further at the project level, calculating a “structural health index” that can be incorporated into a pavement management system [PMS]).  Determine availability of pavement condition screening data for project and recommend continuous deflection-measurement technology for investigation from SHRP 2 R06F. Strategic Objective 2: Identify pavement preservation strategies for application on high-traffic-volume roadways.  Suitability of pavement preservation as a life- extending activity (functional and/or structural) for an existing asphalt, concrete, or composite pavement on a high-traffic road.  Suitability and cost-effectiveness of different preservation treatments as a life-extending activity (functional and/or structural) for an existing asphalt, concrete, or composite pavement on a high-traffic road (also, identification of the preferred treatment).  Collect input regarding pavement condition and potential for preservation treatments. Recommend best practices for preservation based on SHRP 2 R26.  Describe project selection process and provide guidelines for identifying suitable treatments when project is a good candidate for preservation using SHRP 2 R26.

90 Table 4.19. Strategic Objectives and Tool Requirements for Asset Managers User Requirements Functional Requirements Strategic Objective 1: Assess impacts of rapid renewal projects at the corridor and network level.  Tools to assess impacts of a roadway project on corridors/networks.  Performance measures and decision support systems to evaluate the impacts of work zones in a roadway project.  Strategies for roadway projects to minimize disruption due to work zone impacts.  Operational scenarios and mitigation strategies for work zone impacts.  Collect input on construction closures and work zone impacts. To analyze corridor and network effects, identify decision support system using software tools from SHRP 2 R11. Strategic Objective 2: Assess the condition of tunnel linings.  Identification of suitable NDT devices/tools for conducting condition assessments of tunnel linings, based on device/tool performance ratings for accuracy, detection depth, deterioration mechanisms detected (e.g., moisture intrusion, delaminations and spalling, voids), and tunnel lining types).  Procedures and illustrations for using various NDT devices/tools to evaluate tunnel linings.  Collect project tunnel characteristics and recommend tools to assess tunnel linings based on SHRP 2 R06G. Table 4.20. Strategic Objectives and Tool Requirements for Planners User Requirements Functional Requirements Strategic Objective 1: Expedite planning in order to keep rapid renewal projects on schedule.  Procedures for performing a risk assessment of schedules and identifying alternatives that provide the lowest levels of risk while still maintaining the desired project schedule.  Tools to assess impacts of a roadway project on corridors/networks.  Collect input regarding anticipated construction closures and evaluate aggressiveness of construction schedule based on SHRP 2 R03.  Collect input on work zone impacts and identify software tools to analyze corridor and network effects using SHRP 2 R11. Visualized Applications To illustrate how the Project Builder Application (PBA) tool would operate, high-level visualized examples of the application input screens were created. These examples indicate how a user might interact with the tool through a sequence of steps. At each step, the tool would gather information according to the PBA framework that helps the user identify which research products to implement or investigate further. To begin with, the PBA tool would request general information to identify which audience role(s) to assign the user (see Figure 4.2). From this starting point, the tool would determine whether the user is likely to focus on project-level information or prefer a broader program-oriented approach. To follow up, the tool looks to narrow down which aspects of infrastructure assets are most relevant to the user (see Figure 4.3).

91 The initial input from the user suggests what user requirements may be appropriate. At this point, the tool asks for further input to validate those requirements as it displays for review the assumptions that took it there (see Figure 4.4). Figure 4.2. Sample PBA tool interface for identifying the user audience role. Figure 4.3. Sample interface showing user interaction with PBA tool.

92 Figure 4.4. Sample PBA tool interface for identifying user requirements. After analyzing and validating the user input, the tool generates a customized recommendation (see Figure 4.5). This may include specific products to consider for implementation as well as resources for further investigation. Figure 4.5. Sample PBA tool interface showing recommendation based on user requirements.

93 Benefits of Integration Tool The PBA tool provides a number of potential benefits to agencies and individual users. It is designed to offer a simple, streamlined process through which users can identify the products that are relevant to their specific needs and interests. The tool does not assume that the user will need to bring significant prior knowledge related to the research, gather information not readily available, perform complex calculations, or engage in other preparations in advance. Instead, the framework builds off the user’s existing knowledge to provide results that should make sense intuitively to the user. By integrating all of the renewal research program results under a single framework, the PBA facilitates packaging multiple products together. It helps users discover relationships between products and identify ways in which they might complement each other to the benefit of the agency. The integration and packaging is further supported by maintaining the simplicity of the framework; by filtering out superfluous results, the tool focuses attention on those products that are most likely to address user needs. The PBA tool also maintains the integrity of the products by including support materials and resources in the recommendation provided to the user. This ensures that implementation does not happen without the education necessary for success. It can also provide the agency with knowledge of delivery strategies and demonstration projects that may be needed to make the case for implementation. Barriers to Implementation of Integration Tool Implementation of the PBA tool can be expected to face certain barriers and challenges during the development process. These include ensuring user adoption, maintaining the relevance of the tool, providing real value, and having institutional support. Important considerations for each of these aspects include the following:  User Adoption: The impact of the tool depends on growing a significant user population. This requires that the tool have attention-grabbing capability to stimulate interest initially, while also providing a user-friendly experience to convert that interest into ongoing engagement.  Tool Relevance: If the tool is released but not properly maintained, its usefulness is likely to have a short shelf life. Key features should include dynamic updating capabilities and real-time access so that users have all of the latest information available to them.  Providing Value: The tool needs to demonstrate that it provides a valuable resource by integrating the renewal research program results. It will not succeed if it lacks products that can really address user needs.  Institutional Support: Successful development of the PBA tool will require additional resources dedicated to the project. The integration tool cannot move forward without a committed owner or host agency.

94 Recommended Program Format In order to deal with these potential barriers, the recommended format for implementing the Project Builder Application is a web-based system, which would make the tool accessible from any location at any time. The technical requirements for providing access involve web hosting in an environment that can provide 24/7 uptime. Cross-platform support for mainstream browsers is required to make the tool accessible on multiple devices and multiple operating systems. At the user level, the program needs to provide a secure, personalized environment with support for a connected environment in which users can share information from the tool. The initial recommendation assumes a desktop environment in which the user has a laptop or personal computer and an available Internet connection. However, a version 2.0 of the tool should be considered with additional features to support mobile devices. For example, this would need to include enabling a responsive web design front-end with interface snap points so that the tool display is visually scalable from large computer monitors to the smaller screens on mobile devices. To provide a personalized environment, the PBA will support individual user accounts with a configurable dashboard that can be personalized by the user. The technical requirements for this include a front-end business logic to provide a configurable user interface and a back-end database to store user account information. Data from the front-end interface will be saved to the back-end database system on an account-level basis. For security, the PBA implementation entails a system of secure user account access while enabling a mixture of open content areas and secure content areas. To provide encrypted user login pages, this system requires a 128-bit Secure Sockets Layer (SSL) protocol, with account information stored in database tables representing username and MD5-encrypted password values. Support for SSL also involves installing an SSL certificate issued by a recognized certificate authority on the web server. Additional security requirements include role- based access control (RBAC) with an interface for the site administrator to manage user roles and set site policy. The RBAC will maintain secure content by checking user permissions whenever the user requires access. Sharing of information will require features such as giving users the ability to e-mail reports to others when the report content is secure and not openly accessible. Technical requirements for this include: (1) enabling a simple mail transfer protocol (SMTP) mail server in a hosted environment, (2) creating unique tokens that can be e-mailed to grant access to the recipient of the report, (3) ability for the user to specify whether the token should expire after a single use or multiple uses, and (4) database tables to store and manage token attributes. Ongoing operation of the PBA means that the implementation must be scalable and provide for the tool to be maintained. In order to accommodate growth in tool demand, the implementation needs to allow for both user growth and bandwidth increases in a scalable fashion. Technical requirements to support scalability include: (1) implementing a horizontal central processing unit (CPU) scaling strategy so that additional servers can be added and load- balanced and (2) enabling a network scaling schema that provides additional network throughput to meet bandwidth needs.

95 Maintaining the PBA also involves keeping the tool content up to date. In following a versioning approach to development, the program anticipates that subsequent releases will be able to add content, such as a new pilot project or implementation case study. Content can also be provided by tool users depending on their role. At the technical level, this could involve features such as creating a “what you see is what you get” (WYSIWYG) interface for users to author content, or a document-tagging scheme to allow easy references to relevant sections of research documentation. The RBAC will allow the site administrator to control which users can add or modify content, creating the potential for a constantly improving information resource. As a web-based program, this system may also incur additional technical requirements in order to meet federal web guidelines. Availability for individuals with disabilities will involve compliance with Section 508 in order to satisfy accessibility requirements. A search function and links to additional information regarding privacy and web records will need to be provided. Component Architecture The system architecture of the PBA tool includes the following components:  User interface  Web server  Application server  Database server As shown in Figure 4.6, these components create a connected system that allows the user to interact with the tool to send and request data via the Internet. The selection of components provides a number of options, as each component is available in a number of technology implementations. Various combinations of these technology options can be implemented together as part of the stack that supports the web application, providing additional options and flexibility. In addition, the server operating system must be selected. Popular server operating systems include Linux, Microsoft Windows Server, and BSD, each of which is available in different “flavors” catering to preferences such as a particular user interface or method of installing software packages. User Interface On the client side, the user interface for a traditional web-based application renders the user’s view into the tool capabilities. This view is provided via a web browser that displays information transmitted from the tool servers via hypertext transfer protocol (HTTP) and hypertext transfer protocol secure (HTTPS) protocols. Popular web browsers include Internet Explorer, Chrome, Safari, and Firefox (see Table 4.21). Common client-side scripting languages include Javascript and XML.

96 Web Server The web server is software that handles HTTP and HTTPS requests from client-side web browsers and provides responses as determined by the tool. The response may include returning static information to the user, such as static HTML pages and Cascading Style Sheets, as well as requesting dynamic information, such as data-driven content from the application servers. Popular web servers include Apache, Nginx, and Microsoft IIS (Internet Information Services) (see Table 4.22). Figure 4.6. Schematic representation of PBA component architecture.

97 Table 4.21. U.S. Market Share of Common Web browsers (StatCounter 2013) Browser Market Share (as of Sept. 2013) Internet Explorer 40.81% Chrome 27.98% Safari 14.34% Firefox 13.94% Table 4.22. U.S. Market Share of Web Servers on Active Sites (Netcraft 2013) Web Server Market Share (as of Sept. 2013) Apache 52.3% Nginx 12.86% Microsoft 10.62% Database Server The database server handles requests made by the application server’s business logic for structured information stored in the database. This allows the web application to use and display dynamic content stored in the database. The database also allows the application to save information in a structured manner. Popular database servers include MySQL, PostgreSQL, Oracle, SQL Server, DB2, and Sybase. Stack Options When taken together, the number of options for each component creates a large number of possible permutations for the stack, which is the combination of technologies underlying the web application. The most popular combinations, which provide the predominant environment for web applications running today, include the LAMP stack, the WISA stack, and the Java stack. The LAMP stack is based on open source technology and consists of the following components:  Operating system: Linux  Web server/Application server: Apache  Database server: MySQL  Scripting language: PHP The WISA stack uses proprietary technology from Microsoft and consists of the following components:  Operating system: Windows  Web server/Application server: IIS

98  Database server: SQL Server  Scripting language: ASP.NET The Java stack is based on open source technology and consists of the following components:  Operating system: Linux or Solaris  Web server/Application server: Apache Tomcat  Database server: SQL  Scripting language: JSP Minimum User System Requirements For successful deployment of the PBA tool, certain baselines need to be instituted in terms of minimum user system requirements. These ensure that users of the tool will interact with the application successfully and have a system that is fully capable of utilizing all essential tool features. The basic requirements include system hardware, operating system, and web browser. Hardware System hardware components that affect tool performance include CPU, memory, and screen resolution. In addition, a pointing device is needed for the user to navigate the tool interface. Minimum hardware requirements for the PBA tool include the following:  CPU: at least 1 GHz  Memory: at least 1 GB of system memory  Screen resolution: at least 1024x768 (until development of version 2.0 responsive web design for mobile devices)  Pointing device: 2-button mouse or emulator Operating System The initial design of the PBA framework is for desktop operating systems, with the potential to support mobile devices in version 2.0. Operating systems to be supported for the PBA include the following:  Windows XP, Vista, Windows 7, or Windows 8  OS X 10.4 or later In a version 2.0, mobile operating systems to be supported include the following:  Android 4.0 or later  iOS 6 or later

99 Browser Minimum requirements for web browsers refer to the installed version of the browser on the user’s operating system. Anticipated minimum requirements for the most common web browsers include the following:  Internet Explorer 7 or later  Chrome 28 or later  Safari 3.1 or later  Firefox 22 or later