Design review checking system with corporate lessons learned

Soibelman, L; Liu, L Y; Kirby, J G; East, E W; Caldas, C H and Lin, K Y (2003) Design review checking system with corporate lessons learned. Journal of Construction Engineering and Management, 129(5), pp. 475-484. ISSN 0733-9364

Abstract

Design reviews are critical to the success of a construction project. They eliminate costly rework and conflicts, and promote creative and innovative design and construction. This paper discusses a unique way to improve design reviews by gathering and including direct corporate experience that can be used company- and industry-wide. The Design Review Checking System (DrChecks) and the system called Corporate Lessons Learned (CLL) were developed by the U.S. Army Construction Engineering Research Laboratory to collect personal experiences and lessons learned on projects and incorporate these data into corporate knowledge, expressly for the design review process. DrChecks provides a framework for a standardized review process. Typically, exchanges of personal experience and knowledge have occurred informally by word of mouth. With DrChecks and CLL, direct personal experience can be collected into a database while the design review process is on-going. Lessons learned, success stories, and good work practices, which can be identified easily by experienced staff members, can then be shared throughout the organization. DrChecks and CLL both take advantage of the Internet and facilitate the management of design review process and the collection and reuse of corporate lessons learned asynchronously and remotely.

Item Type: Article
Uncontrolled Keywords: construction management; data collection; design; internet
Index terms: construction engineering, design and construction, internet, database, construction project, work practice, lessons learned, word-of-mouth, laboratory, rework
Subjects: research management, data management, professional development, production management, engineering methods, management, contractual arrangements, operations management, computing systems
Topics: Organizational Design, Digital Applications, Procurement, Research Practice, Project Management, Information Management, Engineering Principles, Business Strategy
Descriptive scope: 2 PC

N.B. Descriptive scope is a count of how many of the five facets of empirical research are indicated by the words used in title, abstract and keywords. It is not intended as a judgement on the research; merely a count of the kind of word we would expect to indicate Phenomenon, Concepts, Theoretical framing, Empirical techniques, Analytical techniques. If all five are present, then a code of “5 PCTEA” will indicate this. If you feel the coding for this record is questionable, we welcome discussion around the terms we matched or the way we categorized them. The facet you would expect may not be coded, or a facet may be coded inappropriately. This can also bear on a larger question, of which facets should be treated as defining in construction management research. Please get in touch, and we will look at it. More details here