In order to achieve the intended functionality we focus on three crucial points of research interest. First, the requirements of the functional level and the knowledge contents of the local expert systems are specified. Second, a high-level problem-specific representation language for constituting the expertise of IMCOD is developed. Third, techniques that realize the design phase under the paradigm of comprehensive problem-solving with central management are expounded.
A local expert-in the form of an existing expert system-makes its contribution to the overall solution by assessing the current state from its isolated point of view. In order to enable IMCOD to incorporate the information in its model some requirements, concerning the represented domain knowledge and the problem-solving capabilities of the local experts, are specified [Bob91]. In consequence, the local experts are regarded as black boxes obeying some standards whose functional behavior can be controlled through a well-defined interface. Its produced output not only contains syntactic items but also meta-knowledge of how the solution was found and on which model it is based. The specification of these standards is an important research topic in the IMCOD project.
The expertise represented in IMCOD includes various facets:
Consequently, the system that realizes these facets is located anywhere in-between a decision support system, purely based on a model of decision theory, and an expert system with full understanding of the domain [Ric88]. A high-level, problem-specific representation language which closely integrates the various facets of IMCOD's expertise is developed.
In addition to the decision making functionality of IMCOD, regarding it as the central manager for the problem-solving phase, it serves as a
Since these functionalities describe the behavior of IMCOD during the problem-solving phase it is in fact a run-time model of what was previously defined as the expertise of IMCOD. Techniques that realize these tasks are developed such that the overall behavior of the system reflects the design phase in the given domain.