| description abstract | Project‐specific knowledge is the rationale behind the project data and specifications. Currently, only the results of the planning, design, construction, and operation decisions are captured on paper or in computer data bases. Design decisions may be based on many factors: basic data from outside the project, previously defined project data and project specifications, domain knowledge, general knowledge, and other design decisions. Capture and communication of the project‐specific knowledge supporting these decisions can facilitate design verification, speed redesign, reduce errors in design and construction, aid facility management, simplify rehabilitation and retrofitting, and provide a knowledge base of experience for future projects. To make effective use of project‐specific knowledge in the architecture‐engineering‐construction (AEC) industry, we must solve formidable problems in knowledge acquisition during the design, knowledge representation, and automated explanation. Key steps for research consist of locating the sources of project‐specific knowledge, categorizing the knowledge, finding the likely users of the knowledge, and identifying the knowledge flows that can provide the greatest benefits when captured and communicated effectively. The paper includes some examples from past projects to illustrate sources, categories, and users of project‐specific knowledge. | |
