R1: a rule-based configurer of computer systems
TL;DR: R1 is a program that configures VAX-11/780 computer systems and uses Match as its principal problem solving method; it has sufficient knowledge of the configuration domain and of the peculiarities of the various configuration constraints that at each step in the configuration process, it simply recognizes what to do.
About: This article is published in Artificial Intelligence.The article was published on 1982-09-01. It has received 1001 citations till now. The article focuses on the topics: Configuration Management (ITSM) & Knowledge-based configuration.
Citations
More filters
01 Mar 1987
TL;DR: The paper examines the work of Dr. Gary A. Wicklund and doctoral student Ms. Roberta M. Roth of the University of Iowa in the development and implementation of an insurance underwriting expert system for a Midwestern insurance company.
Abstract: The paper examines the work of Dr. Gary A. Wicklund and doctoral student Ms. Roberta M. Roth of the University of Iowa in the development and implementation of an insurance underwriting expert system for a Midwestern insurance company. The underwriting function reviews applicant data for determination of insurability. The feasibility of utilizing an expert system in this area was examined and determined to be practical, and development of a prototype was initiated.The authors began a broad search for and examination of available expert system tools for a personal computer environment. The review of six expert system software packages narrowed the field to two viable candidates. The Ml package from Teknowledge was selected for the first prototyping stage. The prototype was quickly developed with a very limited set of rules to provide a simple demonstration of the applicability of an expert system in this area. The demonstration of the expert system concepts through the prototype to upper management and underwriting management at a local insurance company was well accepted and authorization to build the expert system was given.The host mainframe at the sponsoring insurance company proved incompatible with the M1 software, which was replaced by RuleMaster from Radian. The prototyping work was transferred to RuleMaster, which proved to be beneficial beyond the compatibility concerns. RuleMaster is a modular system as opposed to the inference network approach used in M1, which more closely resembles LISP or PROLOG in structure. With the modular structure, knowledge and rule base building and modifications proved much easier from a programming standpoint.The interviewing of the domain expert was very valuable for future reference in the next domain to be prototyped. Because of the inexperience of the parties, the interviews were unstructured and the knowledge acquisition was a laborious task for the knowledge engineer and the expert. The next interviews were videotaped and replayed later to allow the knowledge engineer closer scrutiny of the responses and adequate time for formulation of additional inquiries. The domain expert and knowledge engineer reviewed sample applicant data to determine key fields and values in those fields which triggered thought processes in the domain expert. By using this approach, the programming of the modular system was simplified, as the software also uses key fields and values which interact with rules for treatment of possible values and provides classification of these values. This also aided the domain expert in understanding how his reactions would be utilized and assisted him in his responses regarding his thought processes.After the initial prototyping and knowledge and rule base building, the system began its refinement stage. During this period the system ran identical data with the domain expert, for comparison with the conclusions which were reached. Discrepancies between the system and the domain expert identified shortcomings and areas for refinement. RuleMaster again proved beneficial in that it provides reasoning for the conclusions reached, which could then be more closely examined by the domain expert and knowledge engineer for modification. Another programming asset of RuleMaster is its ability to induce rules from examples and their treatment which are entered in a simple table by the knowledge engineer. These tables can be easily modified and all changes are immediately reflected in RuleMaster. The sponsoring insurance company also requested that the conclusions include a conclusion strength factor (in this case numeric) which would be highly recognizable to the user as an additional supporting measurement of the conclusion reached. The sponsor will soon begin to run the system parallel with its entire underwriting staff for further analysis and as the first step toward implementation.
2Â citations
01 Jan 1996
TL;DR: Providing active support for the designer can help to ensure that constraints are not overlooked, and the detailed design generates a range of outputs such as parts lists and cost breakdown.
Abstract: Engineering design is a complex process requiring solutions that meet the customer’s requirements within the constraints of design rules and cost The initial phase of the design process usually requires a combination of creativity and expertise to translate the requirements into a technically feasible solution While it would be extremely difficult to build creativity into a tool, providing active support for the designer can help to ensure that constraints are not overlooked Later, the detailed design generates a range of outputs such as parts lists and cost breakdown These tasks are laborious and potentially error-prone and thus suited to automation
2Â citations
TL;DR: This paper provides a historical perspective on the evolution of practical artificial intelligence by presenting the important techniques underlying modern AI application systems, discussing some of the important issues that must be confronted by any practical AI system, and showing where the various papers in the special issue fit in the spectrum of practical AI.
Abstract: In this paper we give context for the special issue by providing a historical perspective on the evolution of practical artificial intelligence (AI), presenting the important techniques underlying modern AI application systems, discussing some of the important issues that must be confronted by any practical AI system, and showing where the various papers in the special issue fit in the spectrum of practical AI.
2Â citations
01 Jan 2016
2Â citations
12 Jun 1988
TL;DR: Factors affecting successful implementation of management information systems/decision support systems (MIS/DSS) are analyzed as to how they may affect the development of business-oriented expert systems (ES).
Abstract: Factors affecting successful implementation of management information systems/decision support systems (MIS/DSS) are analyzed as to how they may affect the development of business-oriented expert systems (ES). The usefulness of some of the classical approaches for successful implementation of MIS/DSS is also questioned as to their applicability to ES. New factors affecting ES implementation success are delineated and hypothesized. Recommendations for safer knowledge engineering are provided. >
2Â citations
References
More filters
TL;DR: The Rete Match Algorithm is an efficient method for comparing a large collection of patterns to a largeCollection of objects that finds all the objects that match each pattern.
2,562Â citations
TL;DR: The MYCIN system has begun to exhibit a high level of performance as a consultant on the difficult task of selecting antibiotic therapy for bacteremia and issues of representation and design for the system are discussed.
619Â citations
Proceedings Article•
22 Aug 1977TL;DR: Some of the issues that bear on the design of production system languages are explored and the adequacy of OPS is tried to show for its intended purpose.
Abstract: It has been claimed that production systems have several advantages over other representational schemes. These include the potential for general self-augmentation (i.e., learning of new behavior) and the ability to function in complex environments. The production system language, OPS, was implemented to test these claims. In this paper we explore some of the issues that bear on the design of production system languages and try to show the adequacy of OPS for its intended purpose.
173Â citations
01 Jan 1978
TL;DR: In this article, the authors explore the role of conflict resolution in providing support for production systems designed to function and grow in environments that make large numbers of different, sometimes competing, and sometimes unexpected demands.
Abstract: Production systems designed to function and grow in environments that make large numbers of different, sometimes competing, and sometimes unexpected demands require support from their interpreters that is qualitatively different from the support required by systems that can be carefully hand crafted to function in constrained environments. In this chapter we explore the role of conflict resolution in providing such support Using criteria developed here, we evaluate both individual conflict resolution rules and strategies that make use of several rules.
102Â citations
TL;DR: The role of conflict resolution in providing support for production systems designed to function and grow in environments that make large numbers of different, sometimes competing, and sometimes unexpected demands is explored.
Abstract: Production systems designed to function and grow in environments that make large numbers of different, sometimes competing, and sometimes unexpected demands require support from their interpreters that is qualitatively different from the support required by systems that can be carefully hand crafted to function in constrained environments. In this paper we explore the role of conflict resolution in providing such support. Using criteria developed in the paper, we evaluate both individual conflict resolution rules and strategies that make use of several rules.
102Â citations