bdawe wrote: ↑Fri Apr 10, 2020 11:13 am
the problems with design build are that you degrade the in-house capabilities of your agency, leaving it up to consultants who benefit by spending more public money in the long run, and you create a fairly small market of large general contractors who have the capacity to manage whole projects (while you don't anymore) and charge according to their market power.
The places-with-cheap-infrastructure costs don't do design build.
I think it's a balancing act. When we have customers, especially government customers, the specifications usually have both loopholes big enough to drive a bus through and also present value engineering opportunities to genuinely save the public lots of money.
Your position also assumes that agencies have the engineering back bench to write and manage specifications adequately in the first place. My experience is that they do not. Most of the times when a medium-size project is done, they pull out an old spec and doctor it. After 20-30 years, the spec has been doctored so many times that it contradicts itself horribly and refers to technologies long out of date, thus creating the loopholes I mentioned above. Then they bring in a consulting engineering firm to update it, and the firm may or may not be expert on the project. Often all they do is create bigger loopholes.
On a recent Amtrak project I was on the consulting engineering firm did a great job of managing this and we saved the public a boat load of money. On a much older USAF project, we were required to build to spec (whatever that meant) and then rework it on change orders after things went awry, despite written warnings of problems projected.
The new Acela: It's not Aveliable.