What you stated is pretty much the way I have come to understand the DB process is. In general:
- Owner (state, city, airport, PPP, etc) has an idea of something that needs to be built
- Owner finds funding and usually acquires the land/easements/access to the area
- Owner provides a layout (5% design would be sufficient or even a statement of "I want this railroad to go from here to here") and a specification to meet
- Owner hires a DB- in my experience it is usually a Contractor that hires a designer/design team, sometimes it is a Joint Venture. I am sure there are instances where a designer or Program Manager is hired.
I have never used/heard the term "bridging documents" and I am not sure what a "PDR" is. I have also never been part of the design portion of a design build, but I have been a part of the Project Management from the Owner and Contractors sides.
The intention (IMHO and is purely based on what I have seen/heard, not on books) of DB is twofold:
- Construction can start prior to the design being finished
- Construction expertise can be incorporated in the design to potentially speed up construction
Lately DB has been touted as a "faster way to build something" and a "low risk to the Owner way to build something". While both are true if the DB process is followed correctly, it seems more and more often the phrase is used and the process is not followed.