Concrete Strength Required to Open to Traffic
Freeseman, Katelyn
Hoegh, Kyle
Khazanovich, Lev
Hoegh, Kyle
Khazanovich, Lev
2016-01
Loading...
View/Download File
Persistent link to this item
Statistics
View StatisticsJournal Title
Journal ISSN
Volume Title
Title
Concrete Strength Required to Open to Traffic
Published Date
2016-01
Publisher
Center for Transportation Studies, University of Minnesota
Type
Report
Abstract
The current empirical methods for determining traffic-opening criteria can be overly conservative causing unnecessary construction delays and user costs. The research described here recommends innovative mechanistic based procedures for monitoring concrete early age development and evaluating the effect of early traffic opening on long-term damage accumulation. The procedure utilizes recent developments in nondestructive testing to optimize traffic opening timing without jeopardizing pavement longevity. These tasks were achieved via extensive field and laboratory experiments allowing for the analysis of variables such as curing condition and loading type with respect to the effect of early loading of concrete. The results of these efforts culminated in the development of a program that analyzes the effect of design and opening time decisions on pavement damage. The deliverable can be utilized by transportation agencies to make more informed decisions.
Description
Related to
Replaces
License
Collections
Series/Report Number
;MnDOT 2016-01
Funding information
Isbn identifier
Doi identifier
Previously Published Citation
Other identifiers
Suggested citation
Freeseman, Katelyn; Hoegh, Kyle; Khazanovich, Lev. (2016). Concrete Strength Required to Open to Traffic. Retrieved from the University Digital Conservancy, https://hdl.handle.net/11299/177641.
Content distributed via the University Digital Conservancy may be subject to additional license and use restrictions applied by the depositor. By using these files, users agree to the Terms of Use. Materials in the UDC may contain content that is disturbing and/or harmful. For more information, please see our statement on harmful content in digital repositories.