A Transparent Design System for Iterative Product Development

Abstract

Automated systems for variant design can be used for design iterations in order to guide the designer towards solutions that are optimized with respect to weight, cost, lead time, or other vital properties. In this work such a system for computational design problems is presented together with examples of its application. The system performs design computations, computed aided design model configuration, production process planning, and cost estimation. The design rules and algorithms are captured in knowledge “chunks,” which are human readable as well as computer executable. The workflow governing the execution of these rules and algorithms is created using a dependency structure matrix (DSM) which is included in the system. Particular attention has been given to the need for transparency, modularity, and longevity of the system, which is a prerequisite for such a system to become a viable tool in industrial applications. Experiences from the proposed system indicate that the DSM workflow manager in combination with a human readable and modularized knowledge base provides clarity and transparency for both developer and user of the system.

The documentation of product configuration systems: A framework and an IT solution

“…Rask [35] addresses documentation and maintenance requirements by emphasising the importance of traceability, verification and versioning. Application of the Dependency Structure Matrix (DSM) method could provide natural and transparent documentation of the 'knowledge base' [36]. Multiple IT tools have been developed to assist with documentation in IT and PCS projects.…”

“…Even in the earliest stages, documentation must be adequate to serve its primary communications purpose. Agility and avoidance of duplicate knowledge are essential in software documentation [36,46]. The UML state chart shown in Fig.…”

Capturing, Structuring, and Accessing Design Rationale Across Product Design and FEA

“…Design process is an important element in PLM because making proper decisions at this early stage could optimize the development process and support the organizations to deliver their business initiatives and strategic goals. Design work encompasses a wide range of methodological approaches in order to solve different technical problems that require different solution strategies [2]. Regarding the time-intensive nature of many design tasks, up to 80% of design time is spent on routine tasks [3] such as modifying, adapting or redesigning already existing and proven solutions.…”

An ontology framework for developing platform-independent knowledge-based engineering systems in the aerospace industry

“…Existing KBE methodologies are subjected to improvement and alternatives are required to be developed (Mendikoa et al 2006;Ruschitzka, Suchodolski, and Wróbel 2010;Sandberg 2003;Verhagen et al 2012). Additionally, transparency of KBE applications is required in order to move away from black-box KBE applications to more user-friendly, adaptable, structured and reusable knowledge bases (Fan and Bermell-Garcia 2008;Sunnersjöet al 2006). In a recent critical review (Agyapong-Kodua et al 2013) of semantic modelling approaches and technologies, it was identified that KBE frameworks should clarify pre-development and postdevelopment phases for KBE development which is often not well specified in KBE systems that uses ontologies as the basis.…”