Product and Systems Engineering/CA* Tool Chains

Paetzold, Kristin

doi:10.1007/978-3-319-56345-9_2

Cited by 18 publications

(7 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…MMT concerns the manual transfer of engineering data/ models between engineering tools [12,27]. This approach requires only capabilities for exchanging data files and organizational rules to coordinate the data exchange.…”

Section: Model Architecture Typesmentioning

confidence: 99%

“…Line 4 indicates the expression for which element type in an XML documents the mapping is applicable (cf. mechanical-import-data.xml 27 ). Specifically, these mappings describe which artefact elements map to which AML concept, in the example a particular systemUnitClassPath (line 5).…”

Section: Feasibility Studymentioning

confidence: 99%

“…com/ tuw-qse/ tmvmt-resou rces/ main/ uc-screw_ dashb oard/ trans form/ input/ mecha nical-import-config. yml 27. mechanical-import-data.xml: https:// raw.…”

mentioning

confidence: 99%

See 2 more Smart Citations

Traceable Multi-view Model Integration: A Transformation Pipeline for Agile Production Systems Engineering

et al. 2023

View full text Add to dashboard Cite

Purpose. Agile Production Systems Engineering (PSE) is characterised by parallel and iterative engineering of several disciplines. This multi-view engineering requires capabilities for tracing changes to support configuration management of PSE assets. Yet, traditional model transformation approaches in PSE do not preserve local views and hierarchies on concepts of PSE assets, such as plans and configurations. Thus, tracing multi-view changes to PSE assets is challenging. Method. Following the Design Science approach, we (i) elicit requirements for tracing multi-view changes to PSE assets from a domain analysis in automotive manufacturing; (ii) introduce and evaluate the Traceable Multi-view Model Transformation (TMvMT) process; and (iii) propose the TMvMT pipeline architecture to provide traceable model integration capabilities for agile PSE. Results. In a feasibility study on robot cell models, we evaluate the TMvMT process and architecture regarding the requirements for traceability compared to traditional approaches. Conclusion. The proposed TMvMT approach provides traceability of changes in multi-view modelling as a basis through the separation of modelling transformation steps and provision of clear input and output artefacts to achieve traceable configuration management and validation of system designs for production system assets in agile PSE.

show abstract

Section: Model Architecture Typesmentioning

confidence: 99%

Section: Feasibility Studymentioning

confidence: 99%

See 1 more Smart Citation

Traceable Multi-view Model Integration: A Transformation Pipeline for Agile Production Systems Engineering

et al. 2023

View full text Add to dashboard Cite

show abstract

“…The micro-level process supports every speci c design phase and individual process steps where individual designers can structure design sub-tasks and proceed and react in unforeseen situations. c. Alignment of the system and the process viewpoints: This alignment challenge describes the need for support methods for system design and to control the system's complexity (Paetzold, 2017). This challenge lays in the 'close interplay between the design structure (system architecture) and the related organization of tasks involved in the design process' (Braha & Bar-Yam, 2007).…”

Section: Generalized Complexity Challengesmentioning

confidence: 99%

Engineering Complexity beyond the surface: Discerning the viewpoints, the drivers, and the challenges

Morales

Nizamis

Bonnema

2022

Preprint

View full text Add to dashboard Cite

Complexity is often regarded as a “problem” to solve. Instead of yet again attempting to solve complexity, we follow systems engineering practices and switch back to the problem domain. A major obstacle in the problem domain is the impossibility to universally define complexity. As a workaround, we explored complexity characterization and identified shortcomings of the existing characterizations. The shortcomings include lack of standardization, inconsistent semantics, system-centricity, insufficiently transparent reasoning, and lack of validation. To address these shortcomings, we proposed a framework to characterize complexity by adapting three questions (who, why, what) from the Five Ws information-gathering method. The answer to the WHO-question proposed four complexity viewpoints; the answer to the WHY-question proposed a two-dimensional structure to identify complexity drivers; and the answer to the WHAT-question derived generalized complexity challenges. We used a systematic mapping study (SMS) to validate the framework. In general, our findings suggest that papers with complexity solutions do not frame their research within the complexity problem domain, hindering the contribution evaluation. Through the viewpoints, we identified general research gaps of six solution directions. From the drivers, we noted three observations in the discourse of complexity origins: 1) a system-driven tendency, 2) a preference for concreteness vs. abstraction, and 3) an unclear distinction between origins and effects. Through the challenges’ findings we supported two hypotheses: 1) a system-centric preference; and 2) a solution-oriented vision. This application of our framework exemplifies its potential to facilitate and structure future research, both in the problem and solution domains.

show abstract

“…In PSE, engineers create various types of engineering artifacts and models [5], [14]. However, the used formats and tools have traditionally been optimized for a single discipline, and while engineers are well connected within their domains, there is often an insufficient interdisciplinary exchange.…”

Section: A Production Systems Engineeringmentioning

confidence: 99%

Patterns for Reuse in Production Systems Engineering

Meixner¹

2021

Proceedings of the 33rd International Conference on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

In Production Systems Engineering (PSE), domain experts aim at reusing production processes implemented as Industry 4.0 assets and software. However, the knowledge on reusable assets is often scattered on multi-disciplinary engineering artifacts and domain experts, making it hard to find suitable reusable assets and map them to requirements. In this paper, we (i) identify challenges and requirements for reuse in PSE based on a domain analysis; (ii) introduce the Industry 4.0 Asset Network (I4AN) that integrates multi-disciplinary dependencies between the assets and exposes recurring patterns; and (iii) present four patterns for reuse in PSE that aim at improving reuse efficiency and risk. We evaluate the I4AN with reuse scenarios in a feasibility study. The study results indicate that the I4AN model satisfies the elicited requirements and enables PSE domain experts to identify patterns for reuse in their contexts.

show abstract

Product and Systems Engineering/CA* Tool Chains

Cited by 18 publications

References 19 publications

Traceable Multi-view Model Integration: A Transformation Pipeline for Agile Production Systems Engineering

Traceable Multi-view Model Integration: A Transformation Pipeline for Agile Production Systems Engineering

Engineering Complexity beyond the surface: Discerning the viewpoints, the drivers, and the challenges

Patterns for Reuse in Production Systems Engineering

Contact Info

Product

Resources

About