<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="client.xsl" type="text/xsl"?>
<article article-type="other">
<front>
<journal-meta>
<journal-id/>
<issn/>
<banner>
<href>banner.jpg</href>
<size width="100%"/>
</banner>
</journal-meta>
<article-meta>
<doi>/ISEC.res.2017.34</doi>
<title-group>
<article-title>DESIRED VERSUS REALIZED BENEFITS OF<br/>
ALTERNATIVE CONTRACTING METHODS ON<br/>
EXTREME VALUE HIGHWAY PROJECTS</article-title>
</title-group>

<author>DOUGLAS ALLEMAN<sup>1</sup>, ARTHUR ANTOINE<sup>1</sup>, DEAN PAPAJOHN<sup>2</sup>, and KEITH<br/>
MOLENAAR<sup>1</sup></author>

<aff><sup>1</sup>Dept of Civil, Environmental and Architectural Engineering, University of Colorado Boulder,<br/>
Boulder, USA<br/>
<sup>2</sup>Dept of Civil Engineering and Engineering Mechanics, University of Arizona, Tucson, USA</aff>


</article-meta></front>
<body>
<abstract>
<title>ABSTRACT</title>
<p>Highway agencies choose alternative contracting methods (ACMs) to for a wide variety
of reasons, primarily their potential for superior cost and schedule performance. Most
literature focuses on these two factors by analyzing aggregate datasets covering a wide-
ranging contract values. These analyses create two voids that this paper attempts to
explore: (1) ACMs provide a wide variety of benefits, which cost and schedule
performance alone do not identify; and (2) projects of differing contract values benefit
differently. This paper investigates the selection criteria for ACMs and why US agencies
chose ACMs for projects at the extreme ends of the cost spectrum (defined as projects at
the upper and lower 10th percentiles for each delivery method) and what benefits are
realized, above and beyond cost and schedule performance. These findings are presented
through a survey of 291 US projects, interviews of sixteen US agency representatives,
literature review, agency ACM manual content analysis.</p>
<p><italic>Keywords: </italic>Decision variables, Performance.</p>
</abstract>
<fpdf>
<href>pdflogo.jpg</href>
<hpdf>CPM-15</hpdf>
</fpdf>
</body>
</article>