Analysis of selection criteria for design-builders through the analysis of Request for Proposals (RFPs)

Selecting an appropriate design-builder is critical to the success of DB projects. The objective of this study is to identify selection criteria for design-builders and compare their relative importance by means of a robust content analysis of 94 Request For Proposals (RFPs) for public DB projects. These DB projects had an aggregate contract value of over US$3.5 billion and were advertised between 2000 and 2010. This study summarized twenty-six selection criteria and classified into ten categories, i.e.: price, experience, technical approach, management approach, qualification, schedule, past performance, financial capability, responsiveness to the RFP, and legal status in descending order of their relative importance. The results showed that even though price still remains as the most important selection category, its relative importance declines significantly in the last decade. The categories of qualification, experience, past performance, by contrast, have been becoming more important to DB owners for selecting design-builders. Finally, it is found that the importance weighting of price in large projects is significantly higher than that in small projects. This study provides a useful reference for owners in selecting their preferred design-builders.

Determining the optimal proportion of design in design-build request for proposals (RFPs)

The design-build (DB) system is a popular and effective delivery method of construction projects worldwide. After owners decide to procure their projects through the DB system, they may wish to determine the optimal proportion of design to be provided in the DB request for proposals (RFPs), which serve as solicitations for design-builders and describe the scope of work. However, this presents difficulties to DB owners and there is little, if any, systematic research in this area. This paper reports on an empirical study in the USA entailing both an online questionnaire survey and Delphi survey to identify and evaluate the factors influencing owners’ decisions in determining the proportion of design to include in DB RFPs. Eleven factors are identified, i.e. (1) clarity of project scope; (2) applicability of performance specifications; (3) desire for design innovation; (4) site constraints; (5) availability of competent design-builders; (6) project control requirements; (7) user group involvement level; (8) third party requirements; (9) owner experience with DB; (10) project complexity; and (11) schedule constraints. A statistically significant agreement on the eleven factors was also obtained from the (mainly non-owner) Delphi experts. Although some of the experts hold different opinions on how these factors affect the proportion of design, these findings furnish various stakeholders with a better understanding of the delivery process of DB projects and the appropriate provision of project information in DB RFPs. As the result is mainly industry opinion concerning the optimal proportion of design, in addition and for completeness, future studies should be conducted to obtain a big picture of the optimal proportion of design by means of seeking owners’ inputs.

Request for proposals--visitor center & museum facilities, Gettysburg National Military Park, Gettysburg, Pennsylvania.

Includes bibliographical references (p. 37).

Determining the appropriate proportion of owner-provided design in design-build contracts - a content analysis approach

The Request For Proposal (RFP) with the design‐build (DB) procurement arrangement is a document in which an owner develops his requirements and conveys the project scope to DB contractors. Owners should provide an appropriate level of design in DB RFPs to adequately describe their requirements without compromising the prospects for innovation. This paper examines and compares the different levels of owner‐provided design in DB RFPs by the content analysis of 84 requests for RFPs for public DB projects advertised between 2000 and 2010 with an aggregate contract value of over $5.4 billion. A statistical analysis was also conducted in order to explore the relationship between the proportion of owner‐provided design and other project information, including project type, advertisement time, project size, contractor selection method, procurement process and contract type. The results show that the majority (64.8%) of the RFPs provide less than 10% of the owner‐provided design. The owner‐provided design proportion has a significant association with project type, project size, contractor selection method and contract type. In addition, owners are generally providing less design in recent years than hitherto. The research findings also provide owners with perspectives to determine the appropriate level of owner‐provided design in DB RFPs.

Design-build contractor selection for public sustainable buildings

Design-build (DB) is regarded as an effective means of delivering high performance green buildings, and the selection of DB contractors is of critical importance. The objective of this study is to evaluate the selection of design-builders for public buildings seeking Leadership in Energy and Environmental Design (LEED) certification and compare the selection practices involved with those of non-LEED-seeking DB projects through a robust content analysis of 74 DB request for proposals (RFPs) for public DB projects. The results of the content analysis reveal that the level of LEED certification is the dominant means of conveying the sustainability requirements in RFPs for contractor selection, with the majority of RFPs (60%) including sustainability requirements as part of the contractor evaluation package. With the exception of contractors' past performance, there is no statistically significant difference in the importance weightings of selection criteria between LEED-seeking and non-LEED-seeking buildings, and DB owners tend to place more emphasis on innovative technical solutions rather than the past performance of DB contractors. Additionally, the research findings also indicate that owners of LEED-seeking building projects tend to provide less design decisions in RFPs in order to solicit innovative design alternatives from potential DB contractors. This study provides DB owners with a number of practical implications for selecting appropriate design-builders for green DB projects.

How public owners communicate the sustainability requirements of green design-build projects

The design-build (DB) system is regarded as an effective means of delivering sustainable buildings. Specifying clear sustainability requirements to potential contractors is of great importance to project success. This research investigates the current state-of-the-practice for the definition of sustainability requirements within the public sectors of the U.S. construction market using a robust content analysis of 49 DB requests for proposals (RFPs). The results reveal that owners predominantly communicate their desired level of sustainability through the LEED certification system. The sustainability requirement has become an important dimension for the best-value evaluation of DB contractors with specific importance weightings of up to 25%. Additionally, owners of larger projects and who provide less design information in their RFPs generally allocate significantly higher importance weightings to sustainability requirements. The primary knowledge contribution of this study to the construction industry is the reveal of current trend in DB procurement for green projects. The findings also provide owners, architects, engineers, and constructors with an effective means of communicating sustainability objectives in solicitation documents.

Enabling Sensor* Interoperability, Portland, Maine, October 16-18 2006: workshop proceedings

The ACT workshop "Enabling Sensor Interoperability" addressed the need for protocols at the hardware, firmware, and higher levels in order to attain instrument interoperability within and between ocean observing systems. For the purpose of the workshop, participants spoke in tern of "instruments" rather than "sensors," defining an instrument as a device that contains one or more sensors or actuators and can convert signals from analog to digital. An increase in the abundance, variety, and complexity of instruments and observing systems suggests that effective standards would greatly improve "plug-and-work" capabilities. However, there are few standards or standards bodies that currently address instrument interoperability and configuration. Instrument interoperability issues span the length and breadth of these systems, from the measurement to the end user, including middleware services. There are three major components of instrument interoperability including physical, communication, and application/control layers. Participants identified the essential issues, current obstacles, and enabling technologies and standards, then came up with a series of short and long term solutions. The top three recommended actions, deemed achievable within 6 months of the release of this report are: A list of recommendations for enabling instrument interoperability should be put together and distributed to instrument developers. A recommendation for funding sources to achieve instrument interoperability should be drafted. Funding should be provided (for example through NOPP or an IOOS request for proposals) to develop and demonstrate instrument interoperability technologies involving instrument manufacturers, observing system operators, and cyberinfrastructure groups. Program managers should be identified and made to understand that milestones for achieving instrument interoperability include a) selection of a methodology for uniquely identifying an instrument, b) development of a common protocol for automatic instrument discovery, c) agreement on uniform methods for measurements, d) enablement of end user controlled power cycling, and e) implementation of a registry component for IDS and attributes. The top three recommended actions, deemed achievable within S years of the release of this report are: An ocean observing interoperability standards body should be established that addresses standards for a) metadata, b) commands, c) protocols, d) processes, e) exclusivity, and f) naming authorities.[PDF contains 48 pages]

Propostas técnicas para obras de edificações: estudos de caso.

A Proposta Técnica é uma documentação cuja elaboração é uma atividade frequente nas empresas prestadoras de serviço e fornecedoras de produtos, que envolve um time multidisciplinar de profissionais e consome quantidade significativa de recursos financeiros e tempo, tanto das empresas proponentes quanto das empresas contratantes, que analisarão seu conteúdo e por fim selecionarão a proposta a ser aceita. A proposta desempenha vários papeis, funcionando como um material de comunicação da empresa que representa, ao explicitar sua capacidade para realização do trabalho proposto, e também como anexo contratual da transação comercial, passando por servir de fonte de informações para a orçamentação do Projeto e sugerir novas soluções às problemáticas apresentadas pelo cliente. O presente trabalho explorará a importância da Proposta Técnica nas negociações comerciais, assim como seu processo de elaboração em empresas construtoras de edifícios comerciais para iniciativa privada no Brasil, utilizando-se a metodologia de estudo de caso. Por meio de análise da documentação e de entrevistas com os profissionais envolvidos tanto na elaboração quanto na classificação das propostas, são discutidos os pontos essenciais no processo de produção de uma Proposta Técnica.