The National Academies Press

Currently Skimming:

Pages 76-99

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.

From page 76... ... 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. Read the entire page →
From page 77... ... 77 Figure 4.1. Outline of the PBA tool framework. Read the entire page →
From page 78... ... 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. Read the entire page →
From page 79... ... 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. Read the entire page →
From page 80... ... 80 require technical support for integration into agency systems.  Recommended changes in procedures that impact technical workflows or affect existing information architectures. Read the entire page →
From page 81... ... 81  Strategies for roadway projects to minimize disruption due to work zone impacts.  Operational scenarios and mitigation strategies for work zone impacts. Read the entire page →
From page 82... ... 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. Read the entire page →
From page 83... ... 83 reconstruction [i.e., remove/replace] Read the entire page →
From page 84... ... 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) Read the entire page →
From page 85... ... 85 Table 4.14. Strategic Objectives and Tool Requirements for Plan Specifications and Engineering (PS&E) Read the entire page →
From page 86... ... 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. Read the entire page →
From page 87... ... 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. Read the entire page →
From page 88... ... 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. Read the entire page →
From page 89... ... 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. Read the entire page →
From page 90... ... 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. Read the entire page →
From page 91... ... 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) Read the entire page →
From page 92... ... 92 Figure 4.4. Sample PBA tool interface for identifying user requirements. Read the entire page →
From page 93... ... 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. Read the entire page →
From page 94... ... 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. Read the entire page →
From page 95... ... 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. Read the entire page →
From page 96... ... 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. Read the entire page →
From page 97... ... 97 Table 4.21. Read the entire page →
From page 98... ... 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. Read the entire page →
From page 99... ... 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 Read the entire page →

From page 76...

... 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.