28.10.2014 Views

CDOT Performance Data Business Plan - Cambridge Systematics

CDOT Performance Data Business Plan - Cambridge Systematics

CDOT Performance Data Business Plan - Cambridge Systematics

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>CDOT</strong> <strong>Performance</strong> <strong>Data</strong> <strong>Business</strong> <strong>Plan</strong><br />

relative to similar facilities. <strong>CDOT</strong> incorporates safety components into a<br />

project’s design when its location has been identified as a viable safety candidate<br />

through the SPF analysis. This targeted approach and the leveraging of projects<br />

implemented through non-safety programs has enabled <strong>CDOT</strong> to achieve<br />

significant safety improvements over the past decade. Given the success of this<br />

approach, it would be beneficial to understand the relationship between<br />

additional funding and expected future performance. However, a cost/benefit<br />

curve for these funds would be very difficult to develop because the projects<br />

implemented with them are driven by prioritization processes that largely<br />

consider non-safety factors, and the expected impacts of the safety strategies are<br />

largely location and project specific.<br />

Given the focus on incorporating safety into non-safety motivated projects and<br />

the difficulty in modeling the implications of this strategy at the network level, it<br />

is recommended that <strong>CDOT</strong> not develop the type of cost/benefit curve<br />

illustrated in Figure 6.1 for safety. Instead, it is recommended that <strong>CDOT</strong> assess<br />

safety costs and benefits at the project level. For example, by evaluating the<br />

relationship between the incremental costs of modifying the scope of a nonsafety<br />

motivated project to address safety and the expected impact on safety of<br />

the modification. In addition, if not done so already, <strong>CDOT</strong> should consider<br />

systematically inflating unit costs for preservation projects to account for safety<br />

strategies and updating existing preservation cost/benefit curves based on these<br />

updated costs. This would require developing historic estimates for the cost of<br />

safety related scope changes. Updating the costs would change the shape of the<br />

cost/benefit curves because a portion of the overall funding would go to safety<br />

related work rather than to preservation activities.<br />

6.2 MOBILITY<br />

<strong>CDOT</strong>’s Fiscal Year 2010 <strong>Performance</strong> Report indicates that approximately eight<br />

percent of Colorado’s lane miles are considered highly congested. Congestion is<br />

defined as peak traffic exceeding eighty-five percent of a highway’s design<br />

capacity. The Annual <strong>Performance</strong> Report provides a map that shows that the<br />

congested segments are largely concentrated in the Denver region. In major<br />

urban areas such as Denver, increasing highway capacity through capital<br />

projects (for example, adding lanes to an existing highway or building a new<br />

corridor) can be cost prohibitive, leading agencies to focus on a relatively small<br />

set of strategic expansion projects. In these cases, highway operations strategies<br />

provide an alternative means for achieving significant performance<br />

improvements.<br />

Throughout the course of this project, <strong>CDOT</strong> staff confirmed that the situation<br />

described above holds true for Colorado. Achieving significant mobility through<br />

capital improvements does not appear to be a viable option. Therefore, a<br />

meaningful cost/benefit curve would need to focus on potential operations<br />

strategies.<br />

<strong>Cambridge</strong> <strong>Systematics</strong>, Inc. 6-3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!