2014
DOI: 10.1016/j.procir.2014.03.149
|View full text |Cite
|
Sign up to set email alerts
|

Exchange of Knowledge in Customized Product Development Processes

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
8
0

Year Published

2015
2015
2023
2023

Publication Types

Select...
5
2
1

Relationship

3
5

Authors

Journals

citations
Cited by 11 publications
(8 citation statements)
references
References 9 publications
0
8
0
Order By: Relevance
“…Originally, the approach has been developed as a formal extension of SysML, to facilitate a formal and neutral representation of engineering knowledge independent from any KBE related framework. KbeML aims to capture codified knowledge, such as rules and equations [23], [24]. KbeML objectives are:…”
Section: ) Knowledge Based Engineeringmentioning
confidence: 99%
See 1 more Smart Citation
“…Originally, the approach has been developed as a formal extension of SysML, to facilitate a formal and neutral representation of engineering knowledge independent from any KBE related framework. KbeML aims to capture codified knowledge, such as rules and equations [23], [24]. KbeML objectives are:…”
Section: ) Knowledge Based Engineeringmentioning
confidence: 99%
“…Additional elements have been defined to describe the linkage between PUI and design knowledge [23], [25]. These elements support the idea that usage related information can be mapped directly to design related elements such as equations or rules.…”
Section: ) Knowledge Based Engineeringmentioning
confidence: 99%
“…KBE seeks to automate repetitive and non-creative tasks, however, leaving more difficult decisions to (human) designers. The principles behind the automation of repetitive design tasks is often facilitated by the use of Ontologies, semantic connection of knowledge and a framework of independent formalization of knowledge [ 93 ]. Criticism towards current KBE approaches include their mostly case-based nature, black-box application, lack of knowledge re-use, lack of quantitative assessment of cost and benefits and thus the lack of a quantitative framework to judge the value-add of KBE development [ 13 ].…”
Section: Fundamental Technologies and Concepts: A Literature Reviementioning
confidence: 99%
“…In accordance with [12], from 2000 to 2010, knowledge was represented as knowledge, skills, and attitudes accepted and applied by investment professionals worldwide. Furthermore, in [13] it is mentioned that knowledge was often written in a specific language with rules and algorithms that are not compatible with other Knowledge-Based Information Technology (KBE-IT) frameworks.…”
Section: Introductionmentioning
confidence: 99%