What do information reuse and automated processing require in engineering design? Semantic process
<p><strong>Purpose: </strong>The purpose of this study is to characterize, analyze, and demonstrate machine-understandable semantic process for validating, integrating, and processing technical design information. This establishes both a vision and tools for information reuse and s...
| Main Authors: | , , , , , , , , , , |
|---|---|
| Format: | Article |
| Language: | English |
| Published: |
OmniaScience
2011-12-01
|
| Series: | Journal of Industrial Engineering and Management |
| Subjects: | |
| Online Access: | http://www.jiem.org/index.php/jiem/article/view/329 |
| _version_ | 1811301568067141632 |
|---|---|
| author | Ossi Nykänen Jaakko Salonen Mikko Markkula Pekka Ranta Markus Rokala Matti Helminen Vänni Alarotu Juha Nurmi Tuija Palonen Kari T Koskinen Seppo Pohjolainen |
| author_facet | Ossi Nykänen Jaakko Salonen Mikko Markkula Pekka Ranta Markus Rokala Matti Helminen Vänni Alarotu Juha Nurmi Tuija Palonen Kari T Koskinen Seppo Pohjolainen |
| author_sort | Ossi Nykänen |
| collection | DOAJ |
| description | <p><strong>Purpose: </strong>The purpose of this study is to characterize, analyze, and demonstrate machine-understandable semantic process for validating, integrating, and processing technical design information. This establishes both a vision and tools for information reuse and semi-automatic processing in engineering design projects, including virtual machine laboratory applications with generated components.</p><p><strong>Design/methodology/approach:</strong> The process model has been developed iteratively in terms of action research, constrained by the existing technical design practices and assumptions (design documents, expert feedback), available technologies (pre-studies and experiments with scripting and pipeline tools), benchmarking with other process models and methods (notably the RUP and DITA), and formal requirements (computability and the critical information paths for the generated applications). In practice, the work includes both quantitative and qualitative components.</p><p><strong>Findings: </strong>Technical design processes may be greatly enhanced in terms of semantic process thinking, by enriching design information, and automating information validation and transformation tasks. Contemporary design information, however, is mainly intended for human consumption, and needs to be explicitly enriched with the currently missing data and interfaces. In practice, this may require acknowledging the role of technical information or knowledge engineer, to lead the development of the semantic design information process in a design organization. There is also a trade-off between machine-readability and system complexity that needs to be studied further, both empirically and in theory.</p><p><strong>Research limitations/implications:</strong> The conceptualization of the semantic process is essentially an abstraction based on the idea of progressive design. While this effectively allows implementing semantic processes with, e.g., pipeline technologies, the abstraction is valid only when technical design is organized into reasonably distinct tasks.</p><p><strong>Practical implications:</strong> Our work points out a best practice for technical information management in progressive design that can be applied on different levels.</p><p><strong>Social implications:</strong> Current design processes may be somewhat impaired by legacy practices that do not promote information reuse and collaboration beyond conventional task domains. Our work provides a reference model to analyze and develop design activities as formalized work-flows. This work should lead into improved industry design process models and novel CAD/CAM/PDM applications, thereby strengthening industry design processes.</p><p><strong>Originality/value:</strong> While extensively studied, semantic modeling in technical design has been largely dominated by the idea of capturing design artifacts without a clear rationale why this is done and what level of detail should be favored in models. In the semantic process presented in this article, the utility and the chief quality criteria of semantic models (of technical information and artifacts) are explicitly established by the semantic processing pipeline(s). This constructively explains the significance of semantic models as communication and information requirement interfaces, with concrete use cases.</p> |
| first_indexed | 2024-04-13T07:11:01Z |
| format | Article |
| id | doaj.art-4f7fb4d5423b4b5a9d5b6c5d643c5f89 |
| institution | Directory Open Access Journal |
| issn | 2013-8423 2013-0953 |
| language | English |
| last_indexed | 2024-04-13T07:11:01Z |
| publishDate | 2011-12-01 |
| publisher | OmniaScience |
| record_format | Article |
| series | Journal of Industrial Engineering and Management |
| spelling | doaj.art-4f7fb4d5423b4b5a9d5b6c5d643c5f892022-12-22T02:56:52ZengOmniaScienceJournal of Industrial Engineering and Management2013-84232013-09532011-12-014466969810.3926/jiem.329108What do information reuse and automated processing require in engineering design? Semantic processOssi Nykänen0Jaakko Salonen1Mikko Markkula2Pekka Ranta3Markus Rokala4Matti Helminen5Vänni Alarotu6Juha Nurmi7Tuija Palonen8Kari T Koskinen9Seppo Pohjolainen10Tampere University of Technology, Department of MathematicsTampere University of Technology, Department of MathematicsTampere University of Technology, Department of Intelligent Hydraulics and AutomationTampere University of Technology, Department of MathematicsTampere University of Technology, Department of Intelligent Hydraulics and AutomationTampere University of Technology, Department of Intelligent Hydraulics and AutomationTampere University of Technology, Department of Intelligent Hydraulics and AutomationTampere University of Technology, Department of MathematicsTampere University of Technology, Department of Intelligent Hydraulics and AutomationTampere University of Technology, Department of Intelligent Hydraulics and AutomationTampere University of Technology, Department of Mathematics<p><strong>Purpose: </strong>The purpose of this study is to characterize, analyze, and demonstrate machine-understandable semantic process for validating, integrating, and processing technical design information. This establishes both a vision and tools for information reuse and semi-automatic processing in engineering design projects, including virtual machine laboratory applications with generated components.</p><p><strong>Design/methodology/approach:</strong> The process model has been developed iteratively in terms of action research, constrained by the existing technical design practices and assumptions (design documents, expert feedback), available technologies (pre-studies and experiments with scripting and pipeline tools), benchmarking with other process models and methods (notably the RUP and DITA), and formal requirements (computability and the critical information paths for the generated applications). In practice, the work includes both quantitative and qualitative components.</p><p><strong>Findings: </strong>Technical design processes may be greatly enhanced in terms of semantic process thinking, by enriching design information, and automating information validation and transformation tasks. Contemporary design information, however, is mainly intended for human consumption, and needs to be explicitly enriched with the currently missing data and interfaces. In practice, this may require acknowledging the role of technical information or knowledge engineer, to lead the development of the semantic design information process in a design organization. There is also a trade-off between machine-readability and system complexity that needs to be studied further, both empirically and in theory.</p><p><strong>Research limitations/implications:</strong> The conceptualization of the semantic process is essentially an abstraction based on the idea of progressive design. While this effectively allows implementing semantic processes with, e.g., pipeline technologies, the abstraction is valid only when technical design is organized into reasonably distinct tasks.</p><p><strong>Practical implications:</strong> Our work points out a best practice for technical information management in progressive design that can be applied on different levels.</p><p><strong>Social implications:</strong> Current design processes may be somewhat impaired by legacy practices that do not promote information reuse and collaboration beyond conventional task domains. Our work provides a reference model to analyze and develop design activities as formalized work-flows. This work should lead into improved industry design process models and novel CAD/CAM/PDM applications, thereby strengthening industry design processes.</p><p><strong>Originality/value:</strong> While extensively studied, semantic modeling in technical design has been largely dominated by the idea of capturing design artifacts without a clear rationale why this is done and what level of detail should be favored in models. In the semantic process presented in this article, the utility and the chief quality criteria of semantic models (of technical information and artifacts) are explicitly established by the semantic processing pipeline(s). This constructively explains the significance of semantic models as communication and information requirement interfaces, with concrete use cases.</p>http://www.jiem.org/index.php/jiem/article/view/329semantic process, design process, engineering design, engineering information management, pipeline data processing |
| spellingShingle | Ossi Nykänen Jaakko Salonen Mikko Markkula Pekka Ranta Markus Rokala Matti Helminen Vänni Alarotu Juha Nurmi Tuija Palonen Kari T Koskinen Seppo Pohjolainen What do information reuse and automated processing require in engineering design? Semantic process Journal of Industrial Engineering and Management semantic process, design process, engineering design, engineering information management, pipeline data processing |
| title | What do information reuse and automated processing require in engineering design? Semantic process |
| title_full | What do information reuse and automated processing require in engineering design? Semantic process |
| title_fullStr | What do information reuse and automated processing require in engineering design? Semantic process |
| title_full_unstemmed | What do information reuse and automated processing require in engineering design? Semantic process |
| title_short | What do information reuse and automated processing require in engineering design? Semantic process |
| title_sort | what do information reuse and automated processing require in engineering design semantic process |
| topic | semantic process, design process, engineering design, engineering information management, pipeline data processing |
| url | http://www.jiem.org/index.php/jiem/article/view/329 |
| work_keys_str_mv | AT ossinykanen whatdoinformationreuseandautomatedprocessingrequireinengineeringdesignsemanticprocess AT jaakkosalonen whatdoinformationreuseandautomatedprocessingrequireinengineeringdesignsemanticprocess AT mikkomarkkula whatdoinformationreuseandautomatedprocessingrequireinengineeringdesignsemanticprocess AT pekkaranta whatdoinformationreuseandautomatedprocessingrequireinengineeringdesignsemanticprocess AT markusrokala whatdoinformationreuseandautomatedprocessingrequireinengineeringdesignsemanticprocess AT mattihelminen whatdoinformationreuseandautomatedprocessingrequireinengineeringdesignsemanticprocess AT vannialarotu whatdoinformationreuseandautomatedprocessingrequireinengineeringdesignsemanticprocess AT juhanurmi whatdoinformationreuseandautomatedprocessingrequireinengineeringdesignsemanticprocess AT tuijapalonen whatdoinformationreuseandautomatedprocessingrequireinengineeringdesignsemanticprocess AT karitkoskinen whatdoinformationreuseandautomatedprocessingrequireinengineeringdesignsemanticprocess AT seppopohjolainen whatdoinformationreuseandautomatedprocessingrequireinengineeringdesignsemanticprocess |