Samar Ammar-Khodja
email: samar.ammar-khodja@irccyn.ec-nantes.fr

Nicolas Perry
email: nicolas.perry@irccyn.ec-nantes.fr

Alain Bernard
email: alain.bernard@irccyn.ec-nantes.fr

PROCESSING KNOWLEDGE TO SUPPORT KNOWLEDGE BASED ENGINEERING SYSTEMS SPECIFICATION

Keywords: Knowledge Based Engineering, Knowledge Processing, Capitalization, MOKA

During design phase, engineering activities typically involve large groups of people from different expertises and disciplines. Engineers who must set up new product cycles deal with important information flow that makes difficult the decision-making. To face these difficulties, a knowledge engineering process is necessary to structure the information and its rush. This paper presents a knowledge capitalization process deployment based on the enrichment of MOKA methodology to support the integration of Process Planning knowledge in a CAD System. Our goal is to help different actors to work collaboratively by proposing them one referential view of the domain, the context and the objectives assuming that it will help them for a better decision-making.

Introduction

In recent years, engineering systems have moved from being information-intensive towards knowledgeintensive systems. These changes are due to the fact that engineering design is a multi-disciplined environment, a highly integrated and integrating process [START_REF] Sainter | Proceedings of DETC'00 ASME 2000 Design Engineering Technical Conference And Computers and Information in Engineering Conference[END_REF]. Designers usually juggle with many and often conflicting constraints to balance aesthetics, manufacturability and functional objectives within a marketable product specification [START_REF] Chapman | Design engineering-a need to rethink the solution using knowledge based engineering[END_REF]. The satisfaction of all these constraints requires the integration and utilisation of information, supplied from many sources both internal and external and in many formats. Adding to that, competitive business time-scales often constrain designers to make critical decisions without exploring alternative strategies, so the designer has to have access to up to date information and the right knowledge at the right time [START_REF] Ishikawa | Activity model for product development/production, CE: The Vision for the Future Generation in Research Applications[END_REF]. The information is thus constantly refined by clarifications, discussions and evaluations, until an optimised or compromised solution is agreed.

Currently, the advance of computer aided design technologies has been brought by the deployment of three generations of CAD systems from the early geometric modelers to the current feature-based design systems [START_REF] Fan | Virtual concept modeling using design knowledge[END_REF]. However, these technologies have been criticised because they rely on information-based schemas rather than knowledge based-ones; For instance, Weber and Deubel [START_REF] Weber | A different view on PDM and its Future Potentials[END_REF] argue that today's PDM and PLM systems provide infrastructures to store and move data, but not retain knowledge about the content and the interrelationships of the data they handle.

The experience of the whole product lifecycle has shown that decisions are made continuously during all along the design process, and the consistency of technical solutions has to be checked by designers and compared with predefined objectives [START_REF] Studer | Knowledge Engineering: Principals and methods[END_REF]. These decisions are usually based upon the designers' intellectual assets that vary from an expert to another. And one method of using and storing this intellectual capital is to use systems such as Knowledge-Based Systems (KBS). The development of such systems relies on the transformation of human informal knowledge into formal knowledge with some support from knowledge engineering techniques.

Knowledge Engineering is a field of Knowledge Management that refers to the developing of methods, techniques and tools, through which organisations can acquire, develop, measure, share and provide a return on their intellectual assets. Its main objective is to transform the ad hoc process of building knowledge based systems into a discipline of engineering, based on methods, languages and specialised tools [START_REF] Studer | Knowledge Engineering: Principals and methods[END_REF].

The purpose of this paper is to introduce an engineering process to structure the transfer of expertise from expert's minds to an automated system in the manufacturing domain. Assuming that capitalizing knowledge consists of working on the knowledge's content and knowledge's form, the proposed process is structured in two major phases: the capture phase and the formalisation phase. Focusing on the first phase, the main objective of this work is to define a capitalization process to support knowledge capture and representation for the specification of a knowledge based engineering (KBE) system, which is a specific type of knowledgebased systems.

To allow a better understanding of what we are proposing, the first sections of this paper will introduce some KBS and KBE definitions. A brief summary of the works that have been done in these areas is also presented.

In the next sections, the USIQUICK project which is the context of this study will be presented. First, we will start by describing its global context and objectives. Secondly, the problem that we are addressing will be presented and the capitalization process we are proposing is explained. This process is based upon the deployment of MOKA methodology. However, the proposed ontology within this methodology didn't allow us to cover all the knowledge we wanted to transfer. In order to make this transfer as efficient and complete as possible, we proposed an enrichment of this ontology. Finally an analysis of the acquired knowledge is done. This analysis aims to prepare the structuring step, and to evaluate the feasibility, of the knowledge integration within the computer.

Knowledge based systems

A knowledge based system can be defined as a computerised system that uses knowledge about some domain to deliver a solution concerning a problem. This solution should essentially be the same as the solution concluded by a person knowledgeable, about the domain of the problem, when confronted with the same problem [START_REF] Fasth | Knowledge Based Engineering for SMEs[END_REF]. Such KBS are software programs designed to capture and apply domain-specific knowledge and expertise in order to facilitate problem solving.

The first generation of knowledge-based system was expert systems. An expert system is a system in which subject knowledge is held as a set of facts and rules that may be interrogated and manipulated to provide and inferred solution or explanation for a given problem [START_REF] Ulengin | Cognitive map-KPDSS integration in transportation planning[END_REF]. This kind of systems is composed of essentially two components: a knowledge base (KB) and an inference engine. The KB is formed by a set of facts and rules that express domain specific knowledge in form of condition-action pairs referred to production rules. The role of the inference engine is to control the order of the rule activation. It applies specific domain knowledge to problem specific data to generate problem specific conclusions [START_REF] Ritchie | Expert systems in transportation engineering[END_REF]. The next KBS generation was the case-based systems. These systems use previous solutions to problems as a guide to solving new problems. Within these systems, knowledge is stored as a set of cases, and when a solution to a new problem needs to be found, the case-based system attempts to adapt the case to create a solution to the new problem by using case-based reasoning [START_REF] Riesbeck | Inside Case Based Reasoning[END_REF]. Following these systems, model-based systems appeared. They are based on the premise that if a good model of a system can be found, then a program reasoning from the model could act as an expert in understanding the system [START_REF] Shrobe | Exploring Artificial Intelligence: Syrvey Talks from The National Conference on artificial Intelligence[END_REF]. In addition, it is possible such a system could be developed more quickly and provides more comprehensive coverage of problem areas [START_REF] Kirtly | Monitoring the health of power Transformers[END_REF].

Knowledge-based systems are widely acknowledged to be the key for enhancing productivity in the industries, but the major bottleneck of their construction is knowledge acquisition, i.e., the process of capturing expertise before implementation in a system [START_REF] Christine | Knowledge modelling techniques for construction of knowledge and databases in industrial applications[END_REF]. To face this problem, several methodologies have been suggested. The methodologies have been aimed at assisting the developers to define and model the problem in question, such as Structured Analysis and Generation of Expert Systems (STAGES) and Knowledge Acquisition Documentation System (KADS) (an acronym that has been redefined many times, e.g. Knowledge Acquisition Documentation System and Knowledge-based system Analysis and Design Support).

Among the proposed methodologies, the most widely known one is perhaps the CommonKADS methodology. It supports project management, organisational analysis, knowledge acquisition, conceptual modelling, user interaction, system integration and design. It describes KBS development both from a project management perspective and a result perspective. The latter views assume KBS development as the continuous improvement of a set of models of various aspects of the KBS and its environment [START_REF] Breuker | Use of models in the interpretation of verbal data[END_REF]. The CommonKADS methodology is large and complex. It can be difficult to learn, and the effort required for its implementation would be disproportionate for small companies and small projects [START_REF] Buchanan | Constructing an expert system[END_REF].

Adding to the methodologies' complexity and the knowledge acquisition issues, the proposed methodologies for KBS development have normally been applied to areas other than the engineering design area, and have not been commercially used for knowledge based engineering (KBE) development.

Knowledge-based engineering sometimes referred to as KBE that deals with processing of engineering knowledge. It is a process of implementing KBS in which domain specific knowledge regarding a part or a process is stored together with other attributes.

Currently, many industries have recognised the value of the KBE technology, this recognition is illustrated by its acceptance as an important and successful tool in the aerospace and automotive sectors among the technologies supporting automated design.

Knowledge Based Engineering

Engineering knowledge tends to be very complex, diverse, and interrelated in many ways. Consequently, knowledge modelling in engineering must be based on a rich and structured representation of this knowledge, and an adequate way of user interaction for modelling and using this knowledge [START_REF] Klein | Knowledge Modelling in Design -the MOKA framework[END_REF]. Due to the complexity of engineering knowledge, knowledge modelling in engineering is a complex task. Many relations and interdependencies have to be taken into account in order to come up with a model that is as precise, generic, consistent and concise as possible [START_REF] Sainter | Proceedings of DETC'00 ASME 2000 Design Engineering Technical Conference And Computers and Information in Engineering Conference[END_REF]. So, each new piece of knowledge, which should be inserted into an existing knowledge model, has to be related in many ways to the already contained knowledge. Thus, during modelling, a maximum of information about the already existing model has to be available and easily accessible by the knowledge engineer.

The other main knowledge related issue in engineering is the application of knowledge-based technologies, i.e., the automatic computer-based processing of knowledge in KBE systems.

The two following paragraphs define the concept of KBE, the most known existing methodologies and mostly used modelling techniques to support such technology.

Definition

KBE has been defined as being an engineering methodology in which knowledge about the product, e.g., the techniques used to design, analyse, and manufacture a product, is stored in a special product model. The product model represents the engineering intent behind the geometric design. It can store information attributes of the physical product such as geometry, material type, functional constraints, etc. as well as process information, the processes by which the product is analysed, manufactured, and tested. The KBE product model can also use information outside its product model environment such as databases and external company programs.

In reality, there is no unambiguous definition of KBE. However, most of them are similar. KBE has been defined as "a computer system that stores and processes knowledge related to and based upon a constructed and computerised product model" [START_REF] Fasth | Knowledge Based Engineering for SMEs[END_REF].

Bermell-García [START_REF] Bermell-García | A KBE System for the design of wind tunnel models using reusable knowledge components[END_REF] defines it as "a special type of Knowledge Based Systems with a particular focus on product engineering design activities such as analysis, manufacturing, production planning, cost estimation and even sales".

Another definition given by Chapman and Pinfold [START_REF] Chapman | Design engineering-a need to rethink the solution using knowledge based engineering[END_REF] describes KBE as "an engineering method that represents a merging of object-oriented programming (OOP), Artificial Intelligence (AI) techniques and computer-aided design technologies, giving benefit to customised or variant design automation solutions".

However, all these definitions agreed on the fact that the basic objectives that have to be supported by KBE are: to solve a particular design problem by a KBE application (short-term), and to retain the domain knowledge required for solving design problems in the same domain (long-term).

Recently, companies realized that product-related activities should start to be considered on a systematic basis [START_REF] Al-Khudair | A system to support configuration version management in a distributed concurrent engineering design environment, CE: The Vision for the Future Generation in Research Applications[END_REF]. KBE has then gradually gained prominence as a major tool to speed up product development. The encoding of design knowledge from domain experts into computer codes, that can generate complex geometric data, has demonstrated significant savings in manpower and time resources for routine design problems [START_REF] Bermell-García | A KBE System for the design of wind tunnel models using reusable knowledge components[END_REF], and has also provided a high degree of design integration and automation in well defined and complex design tasks. Instead of replacing CAD technology, KBE complements it by offering an environment to automate design activities as well as the means to build a structure in which product knowledge is encoded and stored using an advanced programming language. This language is usually based upon the object-oriented knowledge representation paradigm.

There are a number of different methodologies available for KBS systems; however, only few methods are focused on the development of Knowledge-Based Engineering systems. Among them we identified the MOKA 1 and KOMPRESSA 2 methodologies. The MOKA methodology has been proposed to address methodological issues during KBE systems development. It was part of results from the MOKA ESPRIT project 3 , a project that aimed to develop a standard methodology for the development and maintenance of KBE applications. One of the project's aims was to allow the lead-time for the development of an application to be reduced by up to 25% [START_REF] Callot | Proceedings of the Conference on Integration in Manufacturing[END_REF]. This methodology will be presented farther in the paper.

Within another context, KOMPRESSA has been proposed within the REFIT project 4 , at an applicative level, with the principal aim of developing a methodology that is suitable for SMEs, most importantly, this means minimising the time, effort, and expense needed for system development, without scarifying quality and maintainability [START_REF] Lovett | Knowledge-based engineering for SMEs: a methodology[END_REF].

Other research works related to the use of technologies such KBE in specific domain have been done through cases studies. Among them, we can mention those of Chapman [START_REF] Chapman | Design engineering-a need to rethink the solution using knowledge based engineering[END_REF] that reports on the use of KBE technology in the creation of a concept development tool, called DART 5 , to organise information flow as architecture for the effective implementation of rapid design solutions in the automotive industry. There is also the works done by Santiago, within the KBEMOULD project 6 , on the validation of a KBE tool for the automatic and distributed design of plastic injection moulds for the plastic and toy sector; And those of Bermell-García [START_REF] Bermell-García | A KBE System for the design of wind tunnel models using reusable knowledge components[END_REF] reporting on the experience of the development of a KBE system for the design and manufacture of a wind tunnel testing model of an aircraft nacelle.

The overall works presented lead us to state that the common aim of all these works consists in proposing structures for both knowledge capturing and knowledge modelling. The most used modelling techniques are introduced in the following section.

Knowledge modelling approach in KBE

As mentioned above, the aim with the KBE system is to solve a problem that can be solved by a human expert in the domain. This means that the knowledge that the expert processes have to be translated so that the computer can use them. To reach this purpose, engineering knowledge has to be correctly structured in KBE application codes. In terms of developing KBE applications, this structuring process involves the configuration of the objects that model the engineering design environment and the rules that control the behaviour of the objects [START_REF] Sainter | Proceedings of DETC'00 ASME 2000 Design Engineering Technical Conference And Computers and Information in Engineering Conference[END_REF]. This constitutes a process of abstraction that in the KBE environment can be stated as follows: "The process in which the engineering knowledge is analysed for being represented in As it has been reported by Bench-Capon [START_REF] Bench-Capon | Knowledge representation: an approach to Artificial Intelligence[END_REF] the combination of both paradigms results in a powerful knowledge representation strategy by combining the flexibility of rules with the capabilities for modelling real problems of object-oriented data structures. And the adoption of both knowledge representation paradigms has been widely recognised as highly effective to exploit the benefits of CAD and the featurebased geometric modelling approach [START_REF] Bermell-García | A KBE System for the design of wind tunnel models using reusable knowledge components[END_REF].

4 USIQUICK: a KBE system development project

-The project context

The works presented here are part of the output from an industrial project, called USIQUICK 7 , financed by the French Ministry of Industry. The project was started with the aim of developing a knowledge-based engineering system to help experts to define the process planning for mechanical parts.

The project focuses on the definition of milling process plans in aircraft manufacturing with a high amount of re-engineering and this implies particular geometries and processes.

In order to optimise the information flow from design to production, a three-step method is proposed [START_REF] Candlot | Deployment of an Innovative Resource Choice Method for Process Planning[END_REF]:

• Transformation phase: an analysis of the part to compute a maximum of information registered in an appropriate level of feature. In this phase computer assesses the machinability of faces. • Preparation phase: the synthesis templates of the previous phase are presented to the user. Then with appropriate tools, the process plan skeleton can be built and constrained.

• Automation phase: the unconstrained choices are automatically optimized and a complete documentation is proposed by the system. These phases would become the three major modules of the engineering tool based on the formalisation and the integration of expert knowledge.

The project involves eight partners:

• An aircraft manufacturer who was in charge of specifying the expected results. Some of its manufacturing specialists proposed his expertise on complex part design and on process planning. • A CAD/CAM development leader who plans the industrialization of outputs in its software solution.

• Five laboratories having the responsibilities of ensuring the scientific coherence of the project and proposing innovative solutions to solve strategic locks.

• A French-government institute analyses the possible use of the project results in other fields and proposes extra test cases and tool databases.

The different partners started working together in a same setting domain with different cultures, contexts, goals and backgrounds. These differences led to different:

• Viewpoints

• Assumptions

• Needs Furthermore, they used different jargons and terminologies sometimes diverging or overlapping, generating then confusions.

Our role in the project is to propose solutions to allow these people from different organizations to effectively cooperate on the same objective despite the mentioned differences, and to reduce the communication gap between the domain expert and the developer. To make this cooperation possible we

proposed to put at their disposal contextualised and structured information, in form of knowledge, to help them for having a shared understanding of the domain, the context and the goals.

However, to develop a KBE system, we need first to acquire, represent, reason and then communicate the intent of the design process. The problem is first understood at a conceptual level, and then decomposed into understandable working objects, developed further through an iterative process until a satisfactory outcome is reached. Then, product and process development are defined as a logical sequence of stages or activities, which may be documented, disseminated and understood by all the actors [START_REF] Al-Khudair | A system to support configuration version management in a distributed concurrent engineering design environment, CE: The Vision for the Future Generation in Research Applications[END_REF].

One of the project's challenges is to translate knowledge that has been expressed in form of legacy specifications for the development of the system into a computerised form so that the computer can use it.

The difficulty is thus to select the right methods and tools for supporting and structuring such transfer. One solution could be to structure the knowledge within a knowledge base (KB) (figure 1-a). The building of this KB implies the deployment of a capitalization process to help and guide the knowledge treatments.

Capitalizing knowledge consists in processing and treating knowledge to prepare it for management activities. This capitalization will enable knowledge to be shared through a specific form making it understandable by each actor of the project.

The next section details the definition of such process and highlights its major steps. This definition represents an introduction for the process we are proposing (following section). An overview describing MOKA methodology principals and ontology will be presented.

-Knowledge capitalization

Knowledge capitalization is the process of capturing and formalising expertise before its implementation in a system. This process can be refined into four major stages:

• Knowledge elicitation, also known as acquisition, the process of obtaining knowledge from an expert; • Knowledge analysis, the process of making sense of the information collected in the first step;

• Knowledge structuring, the process of expressing the analysed knowledge in an understandable and usable form, for enhancing communication between the expert and the knowledge engineer, and for validation purposes; • Knowledge representation, the process of rearranging and expressing knowledge in a format that facilitates its encoding and thus its handling by a computer.

The aim of knowledge capitalization is to develop methods and tools that make the task of capturing and validating knowledge experts as efficient and effective as possible. Experts tend to be important and busy people; hence it is vital that the methods used minimise the time each expert spends off the job taking part in knowledge acquisition sessions [START_REF] Fasth | Knowledge Based Engineering for SMEs[END_REF].

To reach the multi-experts collaboration, the knowledge sharing and reuse within the USIQUICK context, we propose to capitalize the knowledge in two major phases: a capture phase and a formalisation phase.

The capture phase gathers the elicitation, the analysis and the structuring stages, while the formalisation phase is the representation stage. In the following sections, only the capture phase will be detailed.

Methods 1 and tools 1 Méthodes 2 et outils 2 Methods 2 and tools 2

Customer specifications KBE application Knowledge Base

Methods 1 and tools 1 Methods 1 and tools 1 Methods 1 and tools 1 Méthodes 2 et outils 2 Methods 2 and tools 2 Methods 2 and tools 2

Customer specifications KBE application

Capitalization process proposal

According to the KBE systems development principle, knowledge must be identified, acquired, analysed, structured and formalised in a way that it could be accessible and reusable by each one. However, this principle does not allow any distinction between the activities handling the knowledge content (this means knowledge its self) and those handling its form.

What we are proposing in this paper is not completely different or contradictory with KBE development principle. Our aim is to structure all these activities according to the knowledge aspect addressed at each stage of the capitalization process. This structuring consists in separating the activities that handle the knowledge itself form those handling its form. This distinction tends to help knowledge engineers during capitalization activities deployment.

This structuring can also be considered as working on the knowledge's state. Indeed, working on the knowledge content consists in transforming its state from a raw state (independently of being explicit or tacit) to a structured one. And working on the form, deals with the representation of the knowledge to go from a structured state to a formalised state, and further toward an automated one.

The transition between the two phases is based on the design of a knowledge base. This base constitutes a knowledge repository that can be accessible and which will be the knowledge reference for the whole involved partners (figure 1-b).

Knowledge Capture Phase

Knowledge capture is the process that tries to transform the human experts' knowledge into a formulated knowledge that can be used directly by an expert system or by a computer system.

As defined in the previous section, this process can be refined in three major steps: the elicitation step, the analysis step and the structuring step.

-Elicitation step

The terms "knowledge elicitation" mean "how to obtain (or collect or acquire) knowledge from an expert".

Diaper [START_REF] Diaper | Knowledge elicitation: principles, techniques and applications[END_REF] has expended this definition to include elicitation from other sources, such as documents, existing computer systems and the physical or the social environment.

A lot of elicitation techniques exist depending on knowledge source's type. The most common way to elicit knowledge from an expert is interviews. These interviews can be structured or unstructured depending on their context and on the knowledge engineer's strategy. On the other hand, eliciting knowledge from documents can be done by data mining techniques resulting from the artificial intelligence.

Within the USIQUCK project, the elicitation had to be done from documents that represent legacy specifications for the development of the final system. Among the existing methodologies for KBS and KBE development, the only one that can meet our needs is MOKA. This is because it offers the possibilities of eliciting knowledge from documents within engineering domains through its ontology. An ontology is a set of different interrelated concepts that describe a given domain [START_REF] Diaper | Knowledge elicitation: principles, techniques and applications[END_REF]. However, this does not mean that MOKA does not allow eliciting knowledge from expert by using the proposed ontology.

To do so, we chose to deploy the proposed ontology within MOKA in order to identify the concepts that should be acquired from the specifications we got. But before explaining this deployment, we will present MOKA.

-MOKA methodology

MOKA, for Methodology and software tools Oriented to Knowledge Engineering Applications, describes in terms of rules, processes, modelling techniques and definitions the necessary stages for the specification of KBE systems. MOKA provides a framework both for capturing and for representing knowledge. This framework works at two levels: informal level and formal level. The first one is relatively simple and oriented to represent and formalize knowledge in language that can be understood by experts without being specialist in formalization languages. The advantage of this level is that it makes the validation of the acquired knowledge possible. This level makes also the communication between the expert, the knowledge engineer and the software developer easier.

The second level is more formal and aims to represent and store knowledge in an encoding forming in order to plug it into computers.

The MOKA spirit is not different from the approaches proposed within the other knowledge management methodologies, the difference lies in the deployment strategy.

The other point that differentiates it from the other methods is the concepts it proposes to analyse the application domain. MOKA proposes five generic knowledge object types and relations among them to describe the domain. These objects are also defined as well as their use constraints. These object's types are:

• Illustrations representing comments, past experiences, specific cases and complex explanations;

• Constraints describing the product's or its component's limitations;

• Activities to describe problems' resolution stages;

• Rules to describe knowledge that directs the choices in the activities;

• Entities to represent knowledge elements that describe the product, its components, its assemblies, parts and features. An entity can be structural or functional.

Starting from this ontology, our first step was the identification of the knowledge objects. The identification step is a preliminary domain investigation and analysis that aims to recognise the knowledge elements or objects that must be acquired. The specifications we got consist of texts, tables, and images in MS Word format. The domain library, which approximates domain ontology, consists of technical sentences condensed from legacy specifications.

The use of the MOKA ontology allowed us to identify a great number of knowledge objects. However, there is some knowledge related to, for example, resources, functions that have been missed.

The insufficiency of the ontology in this case study is due to the fact that in our context the final product is a process planning which is a process. The object's types become then not reusable as they are proposed. For example, if considering the structural entity it describes a physical component of the product but within our context the product is not a set of physical components but a set of activities that consist in geometry recognition, manufacturing mode identification, manufacturing operations definition and organization, etc.

They represent domain activities. This implies that we have two types of activities, those related to the domain and those related to the reasoning that allows definition of the process planning. The reasoning activities represent the design process and each one covers one or several domain activities. This insufficiency led to a need for the ontology enrichment.

-MOKA ontology enrichment

Facing this insufficiency, we propose to define the concept of resource to encapsulate knowledge about the different tools and machines used by manufacturing processes (or operations) to realize geometries. Hence, this object should be considered at the same level as the entity and the activity. It should also be related to both of them.

We also propose to define a concept of function to identify what is the objective of the reasoning activities.

During the design of the system, some reasoning activities that have to be encoded aim to list results or to check if some parameters values are correct or not. This kind of activity should be attached to the concept of function to allow the differentiation of the activities related to a problem solving from those related to the presentation of the solution. It will be linked to the activity. The concept of entity in our context will represent the manufacturing features to be realized. We also distinguished the representation constraints from the product constraints and also the expert rules from the domain rules.

The representation constraints describe the constraints related to the presentation of the knowledge to the end user, and the product constraints allow defining all the constraints related to the product and its design.

The domain rules cover generic rules defined in the domain and the expert rules describe rules, applied by a specific expert that can vary from an expert to another.

According to this new object types, we propose ICARREF ontology to cover the manufacturing domain, in this case study, and for capturing knowledge about a product that is a process considering that these object types are generic. The figure 2 illustrates the whole object types and their interrelations. This figure also shows the ICARREF forms to fill in, and the ways to navigate within the knowledge base.

At this stage the knowledge to be kept has been identified and the elicitation can be done completely by an extraction strategy. The extraction consists of recognizing a subset of knowledge objects and their relationships, and then associating them with applicable fragments of the specifications (figure 3-a). The eventual output of extraction can be in plain text, in XML, or in Excel form, depending on the application of the supported software. In this example the output is in plain text.

Once the knowledge extracted it must be analysed. This analysis has two objectives: its structuring and its evaluation. Due to the diversity of the engineering knowledge and the complexity of building KBE systems, it is difficult for the actors to evaluate if all the knowledge that should be automated has been taken into account, because a traditional development systems approach is based upon the realization of digital mock-ups. But, by separating the activities of the capture phase from those of the formalisation phase, they could have at their disposal a first structured knowledge model and thus compare the two models. This need of comparison introduces the need of knowledge traceability. This means that the capitalization process has to take into account the organizational aspect of the project in addition to the product and the process aspects.

To consider this new aspect an analysis of the developed algorithms has been done. The objective was to establish the correspondence between the algorithms and the design process activities in order to determine which activities have been effectively developed and, for each activity, which was the percentage of domain activities that have been automated (figure 4-a).

For this analysis the attribute "State" has been attached to each knowledge object to identify its state at a given time.

The state can have one of the four following values:

• In progress: the encoding of the knowledge is not completely done,

• Implemented: it indicates that knowledge objects are integrated,

• Dismissed (ruled out): the implementation of the object is not envisaged,

• Not treated: the study and the deployment of the object are scheduled later in the project.

The values of this attribute allow having an overview of the progress of the automation activities at different times in the project. An example of an overview is illustrated in figure 4-b.

This can be one way to manage knowledge project while managing product and process knowledge.

By analyzing the coverage of the activities and rules, some rules have been identified as crucial and then must be implemented. So the encoding schedule has been reconsidered and the priorities have been redefined.

Figure 4-c illustrates the automatic semantic enrichment of surfaces that will be machined. The type of these surfaces (colors identification) depends on the rules and constrains linked to the tools access, machining strategy, settings, etc. The automatic proposal and selection of tools and machining parameters will be generated in accordance with the process of the expert's decision coded in the knowledge-based system. The user can access to the contextual information and the selected rules and reasoning process, in order to justify the proposed solution. Confidence into the system and its proposals increases. Moreover, if any changes or new elements have to be implemented, all the structure and procedure already exists. All the maintenance and life of the knowledge-based systems is then available for the knowledge base or the software development. Most KBE applications have been developed for solving large design problems in the aerospace and automotive industries where the main concern is the functionality to automate a complex design problem, rather than the reusability of engineering knowledge by the human expert.

PLC

However, to get such result, disparate know-how and heterogeneous viewpoints have to be managed, integrated and stored in different forms that should be easily accessible, usable and maintainable. Ontology's approaches can propose solutions that could give some helps to integrate knowledge in KBE environments.

The USIQUICK experience has shown that considering the two knowledge aspects separately, the content and the form, helps to decrease the complexity of knowledge based engineering system development. The capitalization process we propose aims to structure knowledge engineering activities deployment.

It aims also to help the knowledge engineer to capture the whole knowledge he has to capitalize, to facilitate the communication between the different experts (or actors) and to have indicators regarding the project's lifecycle.

Figure 1 :

 1 Figure 1: knowledge transfer possibility (a) and the knowledge capitalisation phases (b)

Figure 2 :Figure 3 :

 23 Figure 2: ICARREF conceptual model (a), form to fill in and reading interface (b)

Figure 4 :

 4 Figure 4: Knowledge implementation monitoring and traceability (a: domain analysis, b: implementation evaluation, c: user interface for solution justification)

  Knowledge modelling has been extensively researched and different representation schemas have been proposed such as logical formalisms, semantic networks, frame-based structures, rule-based representations and object oriented representations. Current KBE systems are based upon a combination of the production rules and the object-oriented knowledge representation. Both elements together offer an automated way to introduce design requirements, model design constraints and provide a product description.

1

Methodology and tools Oriented to Knowledge based engineering Applications 2 Knowledge-Oriented Methodology for the Planning and Rapid Engineering of Small-Scale Applications 3 http://web1.eng.coventry.ac.uk/moka

4

Revitalisation of Expertise in Foundries using Information Technology, carried out at the Knowledge-Knowledge Engineering and Management (KEM) Centre at Coventry University.

5

Design Analysis Response Tool 6 http://cordis.europa.eu/fetch?ACTION=D&CALLER=PROJ_IST&QM_EP_RCN_A=54076 terms of objects and Engineering Rules (ERs) in a computer understandable language"

[START_REF] Fan | Virtual concept modeling using design knowledge[END_REF]

.

www.usiquick.com

-Knowledge analysis

The analysis step is the most difficult step among the stages in the Knowledge capture process because the belief is that a "magical one-to-one correspondence" between the expert's verbal comment and the real items of knowledge is misleading [START_REF] Buchanan | Constructing an expert system[END_REF]. Data and information obtained from manuals, textbooks, experts, and even users need to be converted into knowledge before they can be used.

The intermediate step of knowledge analysis is important, because its result will allow building a first knowledge model of the domain and the reasoning. It consists, first, of identifying the interrelated knowledge components, and after, on defining the right relation for each linked components.

Different relation types can be defined, for example: has constraint to link entities to constraints, has function between functions and activities, etc.

Once the interrelations and the relations defined, the knowledge should be structured.

-Knowledge structuring

The structuring step will be achieved using trees and diagrams according to the MOKA approach.

Knowledge objects having the same type are linked using trees with "Is a" and/or "Is composed of" relation types. Knowledge objects having different types are linked using diagrams (figure 3-b). For diagrams building the relations are defined according to the objects they link. It can be "Has a rule", "Has a constraint", "Has a function", etc. At this stage, the three steps of the capture phase have been done and a first representation of the knowledge is built. This representation will enable the evaluation of the knowledge.

The evaluation consists in analyzing the knowledge according to two criteria: completeness and feasibility.

The completeness indicates if, as transmitted by the expert in the specifications, this knowledge is enough to define the process planning for specified geometries. It allows also identifying if for specified utilisation of the application, context for each knowledge object is well described. This criterion highlights the additional knowledge to capture or to explain more that it has already been done. Each one knows that there is a gap between the "real world" and the "computer's world". The analysis of the feasibility aims to point out the knowledge that cannot be coded as specified by the expert and that requires to develop additional algorithms to make its automation possible.


Nicolas Perry

Samar Ammar-Khodja

Kbe Application

A knowledge engineering based on software engineering methods for Knowledge-based system specifications

Keywords: Knowledge-based Engineering, Knowledge Processing, Capitalization, MOKA 1 Knowledge Base Information Corpus Data Model Class Diagrams

Engineering activities involve large groups of people from different domains and disciplines. They often generate important information flows that are difficult to manage. To face these difficulties, a knowledge engineering process is necessary to structure the information and its use. This paper presents a deployment of a knowledge capitalization process based on the enrichment of MOKA methodology to support the integration of Process Planning knowledge in a CAD System. Our goal is to help different actors to work collaboratively by proposing one referential view of the domain, the context and the objectives assuming that it will help them in better decision-making.

Introduction

In recent years, engineering systems have moved from being information-intensive towards knowledgeintensive systems [START_REF] Sainter | Proceedings of DETC'00 ASME 2000 Design Engineering Technical Conference And Computers and Information in Engineering Conference[END_REF] [START_REF] Ishikawa | Activity model for product development/production, CE: The Vision for the Future Generation in Research Applications[END_REF]. The information is thus constantly refined by clarifications, discussions and evaluations, until an optimised or compromised solution is agreed. In the framework of Product design and manufacturing, Weber [START_REF] Weber | A different view on PDM and its Future Potentials[END_REF] argue that today's PDM and PLM systems provide infrastructures to store and move data, but not retain knowledge about the content and the interrelationships of the data they handle. But, decisions are based upon the designers' intellectual assets and vary from one expert to another.

It becomes crucial to develop a method for take the benefit of this intellectual capital. The Knowledge-Based Systems (KBS) are one solution. Their development relies on the transformation of human informal knowledge into formal knowledge with some support from knowledge engineering techniques [START_REF] Studer | Knowledge Engineering: Principals and methods[END_REF].

The purpose of this paper is to introduce an engineering process to structure the transfer of expertise from experts' minds to an automated system in the manufacturing domain. Assuming that capitalizing knowledge consists of working on the content and form of the knowledge, the proposed process is structured in two major phases: the capture phase and the formalisation phase. Focusing on the first phase, the main objective of this work is to define a capitalization process to support knowledge capture and Product Development in a collaborative environment, Hermes Ed°, ISSN 1246-0125. (sous presse) representation for the specification of a knowledge-based engineering (KBE) system, which is a specific type of knowledge-based systems.

This study is based on the USIQUICK project which. First, we will start by describing its global context and objectives. Then, the problematic will be presented before developing the capitalization process proposed.

Knowledge-based methods and tools

A knowledge-based system can be defined as a computerised system that uses knowledge about some domain in order to deliver a solution concerning a problem [START_REF] Fasth | Knowledge-based Engineering for SMEs[END_REF]. The first generation of knowledge-based systems was expert systems using a set of facts and rules [START_REF] Ulengin | Cognitive map-KPDSS integration in transportation planning[END_REF]. This kind of systems is composed of essentially two components: a knowledge base (KB) and an inference engine. It applies specific domain or domain-specific knowledge to problem-specific data to generate problem-specific conclusions [START_REF] Ritchie | Expert systems in transportation engineering[END_REF]. The next KBS generation was the case-based systems. These systems use previous solutions to problems as a guide to solving new problems. Knowledge-based systems are widely acknowledged to be the key for enhancing productivity in industry, but the major bottleneck of their construction is knowledge acquisition, i.e. the process of capturing expertise before implementation in a system [START_REF] Christine | Knowledge modelling techniques for construction of knowledge and databases in industrial applications[END_REF]. Some methodologies assist the developers in defining and modelling the problem in question, such as Structured Analysis and Generation of Expert Systems (STAGES) and Knowledge Acquisition Documentation System (KADS) (an acronym that has been redefined many times, e.g. Knowledge Acquisition Documentation System and Knowledge-based system Analysis and Design Support). Moreover, these approaches get enriched in order to take into account the project management, organisational analysis, knowledge acquisition, conceptual modelling, user interaction, system integration and design [14] [15].

Consequently, knowledge modelling in engineering must be based on a rich and structured representation of this knowledge, and an adequate way of user interaction for modelling and using this knowledge [START_REF] Klein | Knowledge Modelling in Design -the MOKA framework[END_REF].

Due to the complexity of engineering knowledge, knowledge modelling in engineering is a complex task.

KBE has been defined as being an engineering methodology in which knowledge about the product, e.g.

the techniques used to design, analyse, and manufacture a product, is stored in a special product model.

The product model represents the engineering intent behind the geometric design. The KBE product model can also use information outside its product model environment such as databases and external company programs. KBE has been defined as "a computer system that stores and processes knowledge related to and based upon a constructed and computerised product model" [START_REF] Fasth | Knowledge-based Engineering for SMEs[END_REF]. The encoding of design knowledge from domain experts into computer codes that can generate complex geometric data, has demonstrated significant savings in manpower and time resources for routine design problems [START_REF] Bermell-García | A KBE System for the design of wind tunnel models using reusable knowledge components[END_REF], and has also provided a high degree of design integration and automation in well-defined and complex design Product Development in a collaborative environment, Hermes Ed°, ISSN 1246-0125. (sous presse)

tasks. The MOKA methodology has been proposed to address methodological issues during KBE systems development for our case study.

The modelling approach in KBE has to structure the engineering knowledge. In terms of developing KBE applications, this structuring process involves the configuration of the objects that model the engineering design environment and the rules that control the behaviour of the objects [START_REF] Sainter | Proceedings of DETC'00 ASME 2000 Design Engineering Technical Conference And Computers and Information in Engineering Conference[END_REF]. Current KBE systems are based upon a combination of the production rules and the object-oriented knowledge representation. Both elements together offer an automated way to introduce design requirements, model design constraints and provide a product description.

Knowledge base project: USIQUICK

Engineering knowledge tends to be very complex, diverse, and interrelated in many ways. Consequently, knowledge modelling in engineering must be based on a rich and structured representation of this knowledge, and an adequate way of user interaction for modelling and using this knowledge [START_REF] Klein | Knowledge Modelling in Design -the MOKA framework[END_REF]. Still, due to the complexity of engineering knowledge, knowledge modelling in engineering is a complex task.

Many relations and interdependencies have to be taken into account in order to come up with a model that is as precise, generic, consistent and concise as possible [START_REF] Sainter | Proceedings of DETC'00 ASME 2000 Design Engineering Technical Conference And Computers and Information in Engineering Conference[END_REF]. So, each new piece of knowledge, which should be inserted into an existing knowledge model, has to be related in many ways to the already contained knowledge. Thus, during modelling, a maximum of information about the already existing model has to be available and easily accessible by the knowledge engineer.

The other main knowledge-related issue in engineering is the application of knowledge-based technologies, i.e. the automatic computer-based processing of knowledge in KBE systems.

The following two sections define the concept of KBE, the most well-known methodologies and mostwidely-used modelling techniques to support such technology.

a. Context

The works presented are part of the output from an industrial project (USIQUICK [25]). The project aimed at developing a knowledge-based engineering system to help experts during the process planning for mechanical parts. The project involves eight partners. An aircraft manufacturer is the final user and the initial expert. He specified the expected results and its manufacturing expertise on complex part design and on process planning. A CAD/CAM developer supported the industrialization in its software solution.

Five laboratories ensured the scientific coherence, enriched and solved the strategic keystones of the project. A French-government institute helped to switch these project results in other area of mechanical manufacturing. The partners started working together in a same setting domain with different cultures, contexts, goals and backgrounds. These differences led to different viewpoints, assumptions and needs. In order to optimise the information flow from design to production, a three-step method is proposed [START_REF] Candlot | Deployment of an Innovative Resource Choice Method for Process Planning[END_REF]:

-Transformation phase: an analysis of the part to compute a maximum of information registered at an appropriate level of feature. In this phase computer assesses the machinability of faces.

-Preparation phase: the synthesis templates of the previous phase are presented to the user. Then with appropriate tools, the process plan skeleton can be built and constrained.

-Automation phase: the unconstrained choices are automatically optimized and a complete documentation is proposed by the system.

These phases would become the three major modules of the engineering tool based on the formalisation and the integration of expert knowledge.

We play a role in the project in order to propose solutions to allow to effectively cooperate on the same objective despite the mentioned differences, and to reduce the communication gap between the domain expert and the developer. Contextualised and structured information was shared, in the form of knowledge, to help all the actors to have a same understanding of the domain, the context and the goals.

However, to develop a KBE system, we need first to acquire, represent, reason and then communicate the intent of the design process. The problem is first understood at a conceptual level, and then decomposed into understandable working objects, developed further through an iterative process until a satisfactory outcome is reached. Then, product and process development are defined as a logical sequence of stages or activities, which may be documented, disseminated and understood by all the actors [START_REF] Al-Khudair | A system to support configuration version management in a distributed concurrent engineering design environment, CE: The Vision for the Future Generation in Research Applications[END_REF].

One of the project's challenges is to translate knowledge that has been expressed in the form of legacy specifications for the development of the system into a computerised form so that the computer can use it.

The difficulty is thus to select the right methods and tools for supporting and structuring such a transfer.

One solution could be to structure the knowledge within a knowledge base (KB) (figure 1-a). The building of this KB implies the deployment of a capitalization process to help and guide the knowledge treatments.

Capitalizing knowledge consists in processing and treating knowledge to prepare it for management activities. This capitalization will enable knowledge to be shared through a specific form making it understandable by each actor of the project.

The next section details the definition of such a process and highlights its major steps. This definition represents an introduction to the process we are proposing (following section). An overview describing MOKA methodology principals and ontology will be presented.

b. Knowledge capitalization

Knowledge capitalization is the process of capturing and formalising expertise before its implementation in a system. This process can be refined into four major stages:

-Knowledge elicitation, also known as acquisition, the process of obtaining knowledge from an expert; -Knowledge analysis, the process of making sense of the information collected in the first step;

-Knowledge structuring, the process of expressing the analysed knowledge in an understandable and usable form, for enhancing communication between the expert and the knowledge engineer, and for validation purposes;

-Knowledge representation, the process of rearranging and expressing knowledge in a format that facilitates its encoding and thus its handling by a computer.

The aim of knowledge capitalization is to develop methods and tools that make the task of capturing and validating experts' knowledge as efficiently and effectively as possible. Experts tend to be important and busy people; hence it is vital that the methods used minimise the time each expert spends off the job taking part in knowledge acquisition sessions [START_REF] Fasth | Knowledge-based Engineering for SMEs[END_REF].

To reach the multi-experts collaboration, the knowledge sharing and reuse within the USIQUICK context, we propose to capitalize the knowledge in two major phases: a capture phase and a formalisation phase.

The capture phase gathers the elicitation, the analysis and the structuring stages, while the formalisation phase is the representation stage. In the following sections only the capture phase will be detailed.

Capitalization process proposal

According to the KBE systems development principle, knowledge must be identified, acquired, analysed, structured and formalised in such a way that it could be accessible and reusable by each one. However, this principle does not allow any distinction between the activities handling the knowledge content (this means knowledge itself) and those handling its form.

What we are proposing in this paper is not completely different from or contradictory to the KBE development principle. Our aim is to structure all these activities according to the knowledge aspect addressed at each stage of the capitalization process. This structuring consists in separating the activities that handle the knowledge itself from those handling its form. This distinction tends to help knowledge engineers during capitalization activities deployment.

This structuring can also be considered as working on the state of the knowledge. Working on the knowledge content consists in transforming its state from a raw state (independently of being explicit or tacit) to a structured one. Working on the form, deals with the representation of the knowledge in order to go from a structured state to a formalised state, and onwards toward an automated one.

The transition between the two phases is based on the design of a knowledge base. This base constitutes a knowledge repository that can be accessible and which will be the knowledge reference for all the partners involved (figure 1-b).

Knowledge Capture Phase

Knowledge capture is the process that tries to transform the human experts' knowledge into a formulated knowledge that can be used directly by an expert system or by a computer system.

As defined in the previous section, this process can be broken down into three major steps: the elicitation step, the analysis step and the structuring step.

a. Elicitation step

The terms "knowledge elicitation" mean "how to obtain (or collect or acquire) knowledge from an expert". Diaper [START_REF] Diaper | Knowledge elicitation: principles, techniques and applications[END_REF] has extended this definition to include elicitation from other sources, such as documents, existing computer systems and the physical or the social environment.

Many elicitation techniques exist depending on the type of the knowledge source. The most common way to elicit knowledge from an expert is interviews. These interviews can be structured or unstructured depending on their context and on the knowledge engineer's strategy. On the other hand, eliciting knowledge from documents can be done by data mining techniques resulting from artificial intelligence.

Within the USIQUCK project, the elicitation had to be done from documents that represent legacy specifications for the development of the final system.

Among the existing methodologies for KBS and KBE development, the only one that can meet our needs is MOKA. This is because it offers the possibilities of eliciting knowledge from documents within engineering domains through its ontology. Ontology is a set of different interrelated concepts that describe a given domain [START_REF] Gruber | A translation approach to portable ontologies[END_REF]. However, this does not mean that MOKA does not allow the eliciting of knowledge from experts by using the proposed ontology.

To do so, we chose to deploy the proposed ontology within MOKA in order to identify the concepts that should be acquired from the specifications we obtained. However, before explaining this deployment, we will present MOKA.

MOKA methodology

MOKA, for Methodology and software tools Oriented to Knowledge Engineering Applications, describes in terms of rules, processes, modelling techniques and definitions, the necessary stages for the specification of KBE systems. MOKA provides a framework both for capturing and for representing knowledge. This framework works at two levels: informal level and formal level. The first one is relatively simple and oriented to represent and formalize knowledge in language that can be understood by experts without being a specialist in formalization languages. The advantage of this level is that it makes the validation of the acquired knowledge possible. This level also facilitates the communication between the expert, the knowledge engineer and the software developer.

The second level is more formal and aims to represent and store knowledge in an encoding form in order to plug it into computers.

The MOKA spirit is not different from the approaches proposed within the other knowledge management methodologies, the difference lies in the deployment strategy.

The other point that differentiates it from the other methods is the concepts it proposes to analyse the application domain. MOKA proposes five generic knowledge object types and relations among them to describe the domain. These objects as well as their use constraints are also defined. These object types are:

• Illustrations representing comments, past experiences, specific cases and complex explanations;

• Constraints describing the product's or its component's limitations;

• Activities to describe problems resolution stages;

• Rules to describe knowledge that directs the choices in the activities;

• Entities to represent knowledge elements that describe the product, its components, its assemblies, parts and features. An entity can be structural or functional.

Starting from this ontology, our first step was the identification of the knowledge objects. The identification step is a preliminary domain investigation and analysis that aims to recognise the knowledge elements or objects that must be acquired. The specifications we obtained consisted of texts, tables, and images in MS Word format. The domain library, which approximates domain ontology, consists of technical sentences condensed from legacy specifications.

The use of the MOKA ontology enabled us to identify a great number of knowledge objects. However, there is some knowledge related to, for example, resources and functions that have been missed.

The insufficiency of the ontology in this case study is due to the fact that in our context the final product is a process planning which is a process. The object's types do not become reusable as proposed. For example, if we consider the structural entity, it describes a physical component of the product but within our context the product is not a set of physical components but a set of activities that consist in geometry recognition, manufacturing mode identification, manufacturing operations definition and organization, etc.

They represent domain activities. This implies that we have two types of activities, those related to the domain and those related to the reasoning that allows definition of the process planning. The reasoning activities represent the design process and each one covers one or several domain activities. This insufficiency led to a need for ontology enrichment.

MOKA ontology enrichment

Facing this insufficiency, we propose to define the concept of resource to encapsulate the knowledge of the different tools and machines used by manufacturing processes (or operations) to realize geometries.

Hence, this object should be considered at the same level as the entity and the activity. It should also be related to both of them.

We also propose to define a concept of function to identify what is the objective of the reasoning activities. During the design of the system, some reasoning activities that have to be encoded aim to list results or to check if some parameters values are correct or not. This kind of activity should be attached to the concept of function to allow the differentiation of the activities related to a problem solving from those related to the presentation of the solution. It will be linked to the activity. The concept of entity in our context will represent the manufacturing features to be realized. We also distinguished the representation constraints from the product constraints and also the expert rules from the domain rules.

The representation constraints describe the constraints related to the presentation of the knowledge to the end user, and the product constraints enable the definition of all the constraints related to the product and its design.

The domain rules cover generic rules defined in the domain and the expert rules describe rules, applied by a specific expert that can vary from one expert to another.

According to these new object types, we propose ICARREF ontology to cover the manufacturing domain, in this case study, and for capturing knowledge about a product that is a process considering that these object types are generic. Figure 2 illustrates all object types and their interrelations. This figure also shows the ICARREF forms to fill in, and the ways to navigate within the knowledge base.

ICARREF Form

Knowledge Base reading interface Once the knowledge is extracted it must be analysed. This analysis has two objectives: its structuring and its evaluation.

b. Knowledge analysis

The analysis step is the most difficult step in the Knowledge-capture process because the belief is that a "magical one-to-one correspondence" between the expert's verbal comment and the real items of knowledge is misleading [START_REF] Buchanan | Constructing an expert system[END_REF]. Data and information obtained from manuals, textbooks, experts, and even users need to be converted into knowledge before they can be used.

The intermediate step of knowledge analysis is important, because its result will enable the building of a first knowledge model of the domain and the reasoning. It consists, first, of identifying the interrelated knowledge components, and after, on defining the right relation for each linked components.

Different relation types can be defined, for example: has constraint to link entities to constraints, has function between functions and activities, etc.

Once the interrelations and the relations have been defined, the knowledge should be structured.

c. Knowledge structuring

The structuring step will be achieved using trees and diagrams according to the MOKA approach.

Knowledge objects having the same type are linked using trees with "Is a" and/or "Is composed of" relation types. Knowledge objects having different types are linked using diagrams (figure 3-b). For diagram building, the relations are defined according to the objects they link. It can be "Has a rule", "Has a constraint", "Has a function", etc.

At this stage, the three steps of the capture phase have been done and a first representation of the knowledge is built. This representation will enable the evaluation of the knowledge.

The evaluation consists in analyzing the knowledge according to two criteria: completeness and feasibility.

The completeness indicates if, as transmitted by the expert in the specifications, this knowledge is enough to define the process planning for specified geometries. It also allows identification if, for a specified utilisation of the application, the context for each knowledge object is well described. This criterion highlights the additional knowledge to capture or to explain further if this has already been done.

Each one knows that there is a gap between the "real world" and the "computer world". The analysis of the feasibility to point out the knowledge that cannot be coded as specified by the expert and that requires the development of additional algorithms to make its automation possible. This need of comparison introduces the need of knowledge traceability. This means that the capitalization process has to take into account the organizational aspect of the project in addition to the product and the process aspects.

Knowledge completeness

To consider this new aspect an analysis of the developed algorithms has been done. The objective was to establish the correspondence between the algorithms and the design process activities in order to determine which activities have been effectively developed and, for each activity, the percentage of domain activities that has been automated (figure 4-c).

For this analysis the attribute "State" has been attached to each knowledge object to identify its state at a given time. The state can have one of the four following values: in progress, implemented, dismissed (ruled out: the implementation of the object is not envisaged), not treated.

Conclusion

Most KBE applications have been developed for solving large design problems in the aerospace and automotive industries where the main concern is the functionality to automate a complex design problem, rather than the reusability of engineering knowledge by the human expert.

However, to get such a result, disparate know-how and heterogeneous viewpoints have to be managed, integrated and stored in different forms that should be easily accessible, usable and maintainable.

Ontology approaches can propose solutions that could help integrate knowledge in KBE environments.

The USIQUICK experience has shown that considering the two knowledge aspects separately, the content and the form, helps to decrease the complexity of knowledge-based engineering system development. The capitalization process we propose aims to structure knowledge engineering activities deployment.

It also aims to help the knowledge engineer capture all the knowledge he has in order to capitalize and to facilitate the communication between the different experts (or actors) and to have indicators regarding the project's lifecycle.

Furthermore, they used

  different jargons and terminologies sometimes diverging or overlapping, generating and becoming unclear. Product Development in a collaborative environment, Hermes Ed°, ISSN 1246-0125. (sous presse)

Figure 1 :

 1 Figure 1 : knowledge transfer possibility (a) and the knowledge capitalisation phases (b)

Figure 2 :

 2 Figure 2: ICARREF conceptual model and working interface At this stage the knowledge to be kept has been identified and the elicitation can be done completely by an extraction strategy. The extraction consists of recognizing a subset of knowledge objects and their relationships, and then associating them with applicable fragments of the specifications (figure 3-a). The eventual output of extraction can be in plain text, in XML, or in Excel form, depending on the application of the supported software. In this example the output is in plain text.

Figure 3 :

 3 Figure 3: Knowledge acquisition (a) and structuring (b) step

Figure 4 Figure 4 :

 44 Figure4illustrates the automatic semantic enrichment of surfaces that will be machined. The type of these surfaces (colour identification in 4.a) depends on the rules and constraints linked to the tools access, machining strategy, settings, etc. The automatic proposal and selection of tools and machining parameters will be generated in accordance with the process of the expert's or experts' decision coded in the knowledge-based system. The user can access the contextual information and the selected rules and