Ribeiro, F L (1999) A case-based reasoning framework in value engineering. In: Hughes, W (ed.) Proceedings of 15th Annual ARCOM Conference, 15-17 September 1999, Liverpool, UK.
Abstract
Value Engineering (VE) is the title given to a set of value techniques applied during the design or 'engineering' phases of a construction project that has its origins in the US manufacturing industry. Currently, value engineers attempt to infer design rationale information from drawings and specifications for carrying out the value engineering analysis. Access to design rationales can help value engineers in different ways. Case-based reasoning is a technology for problem solving based on recall and reuse of specific experiences. Case-based reasoning offers techniques for representing and managing complex design rationale cases, augmenting a set of specific design experiences with generalized knowledge and formalizing a typically informal body of knowledge. Agent-based systems technology offers modularity and techniques for handling human-agent interaction, managing and searching information. This paper describes the utility of design rationales in value engineering. It examines the combination of case-based reasoning and agent-based technology to support value engineering analysis. Finally, it proposes a case-based framework in value engineering during design phase.
| Item Type: | Conference Paper (Paper) |
|---|---|
| Uncontrolled Keywords: | case-based reasoning; design rationale; value engineering |
| Index terms: | construction project, problem solving, design phase, agent, body of knowledge, interaction, specification, case-based reasoning, value engineer, value engineering, manufacturing industry, modularity, drawing |
| Subjects: | practitioner, value management, technical documentation, professional practice, knowledge management, decision-making and reasoning, production management, contractual condition, cognitive psychology, design flexibility, industry analysis, behavioral psychology |
| Topics: | Contract Administration, Design Practice, Roles and Professions, Information Management, Research Practice, Project Management, Cost Management |
| Descriptive scope: | 3 PCT |
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