Combining Product Information and Process Information to Build Virtual Assembly Situations for Knowledge Acquisition

2011 ◽  
Author(s):  
N. Madhusudanan ◽  
Amaresh Chakrabarti
Keyword(s):  
Knowledge Acquisition ◽  
Development Process ◽  
Product Information ◽  
Expert Knowledge ◽  
Situation Model ◽  
Virtual Assembly ◽  
Product Development Process ◽  
Specific Context ◽  
Ongoing Research ◽  
Knowledge Based

Assembly is an important part of the product development process. To avoid potential issues during assembly in specialized domains such as aircraft assembly, expert knowledge to predict such issues is helpful. Knowledge based systems can act as virtual experts to provide assistance. Knowledge acquisition for such systems however, is a challenge, and this paper describes one part of an ongoing research to acquire knowledge through a dialog between an expert and a knowledge acquisition system. In particular this paper discusses the use of a situation model for assemblies to present experts with a virtual assembly and help them locate the specific context of the knowledge they provide to the system.

Introducing Knowledge-Based Engineering Into an Interconnected Product Development Process

1999 ◽  
Author(s):  
Daniel E. Whitney ◽  
Qi Dong ◽  
Jared Judson ◽  
Gregory Mascoli
Keyword(s):  
Development Process ◽  
Product Development Process ◽  
System Level ◽  
Knowledge Based ◽  
Design Structure ◽  
Engine Component ◽  
Level Information ◽  
Tightly Coupled ◽  
Knowledge Based Engineering ◽  
Knowledge Content

Abstract Recently, a large automobile company implemented a Knowledge-based Engineering (KBE) application to help design an engine component. While the KBE developers aimed to facilitate a single engineer’s ability to design this component using only the KBE application, it can be shown that in fact this component’s design is tightly coupled to that of several others. Can KBE handle situations like this? How common are they? To address these and other questions, Design Structure Matrix (DSM) models were made of this component at three levels: system interactions, assembly of the component, and individual parts. The size, row names, and internal entries of these matrices were compared to matrices constructed from several conventional written design guides and a flowchart of the KBE application. In each case, the DSM contained more rows or more matrix entries per row, especially at the system interaction level. Since the DSMs were constructed by interviewing experienced engineers, one implication is that while low-aggregation information may be documented, system level information at this company mostly resides in people’s heads. An informal measure of “knowledge content” based on the number of matrix entries per row was shown to be consistent with similar measurements made on DSMs obtained by several other researchers. These results indicate some of the scope and complexity challenges that KBE faces.

A Field Study of the Product Development Process as a First Step in the Design of a System to Support Concurrent Engineering

1996 ◽  
Vol 40 (15) ◽  
pp. 781-790 ◽  
Author(s):  
Melroy E. D'Souza ◽  
Joel S. Greenstein
Keyword(s):  
Product Development ◽  
Development Process ◽  
Research Study ◽  
Product Development Process ◽  
Controlled Study ◽  
Ongoing Research ◽  
Storage And Retrieval ◽  
Ethnographic Approach ◽  
Efficient Storage ◽  
Computer Based

This paper reports the results of the first phase of an ongoing research study undertaken at a real-world production facility. The purpose of this phase was to use a context-based, ethnographic approach to understand and identify issues relevant to the design of a system to support the product development process. The results of this study yielded information that could not have been obtained by a formal, controlled study in a laboratory setting. In general, the results suggest a need for more efficient storage and retrieval of critical information, for increased communication of that information, and for alternative media to supplement paper-based communication. It appears that a computer-based system could be designed to support a more responsive, more collaborative approach to the product development process.

Rapid development of knowledge-based systems via integrated knowledge acquisition

2003 ◽  
Vol 17 (3) ◽  
pp. 221-234 ◽  
Author(s):  
HAO XING ◽  
SAMUEL H. HUANG ◽  
J. SHI
Keyword(s):  
Knowledge Acquisition ◽  
Knowledge Base ◽  
Fuzzy Inference ◽  
Expert Knowledge ◽  
Traditional Approach ◽  
Rapid Development ◽  
Real Life ◽  
Knowledge Based Systems ◽  
Knowledge Based ◽  
Linguistic Rules

This paper presents a novel approach, which is based on integrated (automatic/interactive) knowledge acquisition, to rapidly develop knowledge-based systems. Linguistic rules compatible with heuristic expert knowledge are used to construct the knowledge base. A fuzzy inference mechanism is used to query the knowledge base for problem solving. Compared with the traditional interview-based knowledge acquisition, our approach is more flexible and requires a shorter development cycle. The traditional approach requires several rounds of interviews (both structured and unstructured). However, our method involves an optional initial interview, followed by data collection, automatic rule generation, and an optional final interview/rule verification process. The effectiveness of our approach is demonstrated through a benchmark case study and a real-life manufacturing application.

Product Information Modeling and Organization with MBD

2012 ◽  
Vol 163 ◽  
pp. 221-225 ◽  
Author(s):  
Fang Liu ◽  
Li Hong Qiao
Keyword(s):  
Development Process ◽  
Product Information ◽  
Information Modeling ◽  
Product Development Process ◽  
Time To Market ◽  
Design And Manufacturing ◽  
Critical Issues ◽  
Data Content ◽  
Proper Solutions ◽  
Reduced Time

Model-based definition (MBD) promises reduced time-to-market and improved product quality. Adopting MBD concept in product development process seems to be the next reasonable step. However, some existent critical issues related to data content and presentation need to be overcome. To offer proper solutions from the standpoint of design and manufacturing integration, MBD concept was firstly introduced in order to describe its characteristics and capabilities. Then the answers to the following questions were given: what data are necessary for design and manufacturing integration, how data should be semantically organized and presented based on solid model and CATIA PPR (Product Process & Resource) tree.

scholarly journals INTEGRATING SALES AND DESIGN: APPLYING CAD CONFIGURATORS IN THE PRODUCT DEVELOPMENT PROCESS

2020 ◽  
Vol 1 ◽  
pp. 345-354
Author(s):  
L. P. Poot ◽  
C. Wehlin ◽  
M. Tarkian ◽  
J. Ölvander
Keyword(s):  
Product Development ◽  
Design Automation ◽  
Development Process ◽  
Product Development Process ◽  
Lead Times ◽  
Design Processes ◽  
Complex Products ◽  
Knowledge Based ◽  
Knowledge Based Engineering ◽  
Engineer To Order

AbstractWith industries striving towards increased customisation of complex products through engineer-to-order, methods are continuously sought to rationalise the product development process. To this end, a framework is proposed using CAD configurators, utilising design automation and knowledge-based engineering to integrate sales and design processes in product development. The application of this framework to the design of spiral staircases is described and analysed, with results showing decreased lead-times and a decreased risk for design errors.

Seamless Structured Knowledge Acquisition

2011 ◽  
pp. 1720-1726
Author(s):  
Päivikki Parpola
Keyword(s):  
Expert System ◽  
Knowledge Acquisition ◽  
Expert Knowledge ◽  
Rule Base ◽  
Requirements Definition ◽  
Knowledge Based ◽  
Building Adaptation ◽  
Phases Of Development ◽  
Structured Knowledge ◽  
Analysis Design

Some parts of this text, namely “Co-operative Building, Adaptation, and Evolution of Abstract Models of a KB” and most subsections in “Performing Reasoning in SOOKAT According to a KB”, have appeared in an article (DOI:10.1007/s10115-004-0181-6) published in the ‘Knowledge And Information Systems’ journal (Parpola, 2004). A knowledge base (KB) contains data and instructions for using it (e.g., as a rule base). A KB containing knowledge possessed by experts can be used in an expert system. It can solve problems requiring expert knowledge, explain its decisions and deal with uncertainty. An expert system can be used as a basis for a larger system, called a knowledge-based system (KBS). Knowledge acquisition (KA) that is the development and maintenance of KBs, (e.g. an expert system), can be divided into several phases, performed sequentially and iteratively. Some phases may be performed in parallel with other phases. The most commonly recognised phases are requirements definition, analysis, design, and implementation. Disintegration, or the gap between phases of development, especially between abstract and executable descriptions, was recognised during the early stages of KA (Marcus, 1988a; Motta, Rajan and Eisenstadt, 1988). It complicates the development of KBs and hinders traceability between parts of abstract and executable descriptions.

Sign in / Sign up

Export Citation Format

Share Document