Over the past few decades, not only have systems continued to increase in complexity, but they are expected to be delivered in the same timeframe and cost range. Technology has advanced us into what some refer to as the 4th Industrial Revolution. Digital is becoming the expectation in all areas of people's lives. Model-Based Systems Engineering (MBSE) represents the transition of systems into this new digital age, promising many improvements over the previous Document-Based Systems Engineering. This transition, however, is not simple. MBSE is a major paradigm shift for systems engineers, especially for those who have been in this field for many years. In order to work as intended, MBSE requires the participation of many different disciplines and functionalities in an organization. Gaining this level of organizational collaboration, however, is no easy task. Organizational structure and culture have intuitively been believed to be critical barriers to the successful adoption of MBSE, but little work has been done to discover what the impacts of these organizational factors are. The purpose of this research is to further explore the MBSE adoption process in the context of the organization. There were three research objectives designed to address the research question: how does organizational structure influence the adoption and implementation of MBSE? Research objective one was: relate organizational structure characteristics to MBSE adoption and implementation measures. Research objective two was: discover how organizational factors contribute to decisions made and other aspects of the MBSE adoption process. Research objective three was: connect different organizational structure and adoption variables together to derive critical variables in the adoption process. Research objective one was carried out using a survey as the instrument. The objective of the survey was to examine what the effects of organizational structure are on MBSE adoption and implementation. Organizational structure was represented by seven variables: Size, Formalization, Centralization, Specialization, Vertical Differentiation, Flexibility, and Interconnectedness. These are different characteristics of organizational structure that can be measured on a scale. MBSE adoption and implementation was represented by one adoption and three implementation variables. These include Adoption Process, Maturity of MBSE, Use of MBSE, and Influence on organizational outcomes. A total of 51 survey responses were received that met the inclusion criteria. Factor analysis was done for variables with multi-item measures. The factors were then analyzed using pairwise correlations to determine which relationships were significant. Formalization, Flexibility, and Interconnectedness were found to have positive correlations with adoption and implementation variables. Size and Vertical Differentiation had a negative correlation with Use of MBSE (implementation). Centralization was found to have negative correlations with adoption and implementation. Specialization did not have any significant correlations. Research objective two utilized semi-structured interviews as the main instrument. Survey participants had the opportunity to provide more detailed explanations of their organizations' experiences in the form of follow-up interviews. Eighteen survey participants agreed to this follow-up interview focused on MBSE adoption. Two of the participants shared failed adoption experiences, with the rest were at various stages of the adoption process. One of the most emergent themes out of the interviews was the idea of integration. Integration needs to occur at the organizational level, and the technical level. The technical level refers to the fact that tools, models, and/or data repositories need to be linked together in some way. Integration also has to occur at the organizational level, because a lot of different functional areas need to come together for MBSE. The way that organizations can address the issue of integration is through coordination mechanisms. The ultimate goal is to achieve implicit coordination through the use of connected models, but getting to that point will require coordination between different subunits. Interview responses were evaluated for coordination mechanisms, or situations that showed a distinct lack of a coordination mechanism. The lack of coordination mechanisms largely consists of a lack of standardization, lack of communication between subunits, and issues of authority. The final research objective of this work was carried out through a causal analysis using the data obtained from the survey and interviews. The purpose of this analysis was to visualize and better understand the adoption process. According to the calculated measures of centrality, the important nodes in this model are Improved organizational outcomes, Coordination between subunits, Projects use tools/methods, and People willing to use tools. Improved organizational outcomes is part of a key loop in the causal model. Improved organizational outcomes contributes to leaders and employees' willingness to support and use MBSE methods and tools, which contribute to actual use of tools and methods. This creates more Improved organizational outcomes, completing the loop. The survey results showed that Formalization, Decentralization, Flexibility, and Interconnectedness all have positive correlations with the Influence on organizational outcomes. So these organizational structure components are external factors that can be used to positively impact the adoption loop. Overall, this work provided several contributions to the field regarding the MBSE adoption process in an organizational setting. Organizational structure was shown to have significant correlations with adoption and implementation of MBSE. Coordination mechanisms were identified as a method to achieve integration across different functional areas of the organization. Improved organizational outcomes was shown to be a critical variable in the adoption process as an avenue for organizational structure factors to have a positive effect on the adoption process. / Doctor of Philosophy / Over the past few decades, not only have systems continued to increase in complexity, but they are expected to be delivered in the same timeframe and cost range. Technology has advanced us into what some refer to as the 4th Industrial Revolution. Digital is becoming the expectation in all areas of people's lives. Model-Based Systems Engineering (MBSE) represents the transition of systems into this new digital age, promising many improvements over the previous Document-Based Systems Engineering. This transition, however, is not simple. MBSE is a major mindset change for systems engineers, especially for those who have been in this field for many years. In order to work as intended, MBSE requires the participation of many different disciplines and functionalities in an organization. Gaining this level of organizational collaboration, however, is no easy task. Organizational structure and culture have intuitively been believed to be critical barriers to the successful adoption of MBSE, but little work has been done to discover what the impacts of these organizational factors are. This research looks into how organizational structure may have an impact on MBSE adoption and implementation. This research was carried out with the use of three different methods: an online survey, semi-structured interviews, and a causal analysis. The data obtained from the survey and interviews was used to construct a causal model depicting the MBSE adoption process. Overall, this work provided several contributions to the field regarding the MBSE adoption process in an organizational setting. Organizational structural variables were shown to have significant correlations with adoption and implementation of MBSE. Formalization, Flexibility, and Interconnectedness were found to have positive correlations with adoption and implementation variables, while Centralization had negative correlations with adoption and implementation. Coordination mechanisms were identified as a method to achieve integration across different functional areas of the organization. Interview responses were evaluated for coordination mechanisms, or situations that showed a distinct lack of a coordination mechanism. The lack of coordination mechanisms largely consists of a lack of standardization, lack of communication between subunits, and issues of authority. The causal analysis showed that Improved organizational outcomes, Coordination between subunits, Projects use tools/methods, and People willing to use tools were the critical variables in the MBSE adoption process.

Este trabalho desenvolve um método para a comparação de soluções logísticas de armazenamento e recuperação, com aplicações em centros de distribuição, depósitos, armazéns e demais estruturas equivalentes. Tais soluções podem implicar desde o uso de paleteiras manuais e empilhadeiras contra-balanceadas, até em arranjos mais complexos, envolvendo trans-elevadores operando em corredores de prateleiras com vários metros de altura. A literatura existente para o design e a escolha de tais soluções ressalta o prevalecimento de métodos proprietários e ad-hoc, auxiliados por ferramentas de software demasiadamente genéricas. Assim, o método aqui proposto é elaborado seguindo os princípios da Engenharia de Sistemas Baseada em Modelos (MBSE), sendo expresso através da linguagem OMG SysMLTM, e montado com o auxílio de ferramenta de software CASE (computer aided systems engineering) disponível comercialmente. Utilizando-se das técnicas mencionadas, este trabalho demonstra o passo-apasso da construção do método proposto, incluindo a formulação de um template de requisitos e de um modelo de referência, orientado a objetos, para sistemas logísticos de armazenamento e recuperação. Concluída a apresentação do método, o mesmo é aplicado em dois exemplos de estudos de viabilidade (trade-studies) que determinam soluções ótimas para um dado conjunto de requisitos de negócio. No primeiro exemplo tem-se como fator limitante o no de endereços de armazenamento, e no segundo a área disponível para construção do armazém. O principal resultado obtido com esse trabalho é capacidade de simular, em um único ambiente, escolhas de soluções logísticas de armazenamento que consideram parâmetros do sistema como um todo, e não apenas de seus sub-sistemas isoladamente. Isto tornou possível mensurar como alterações nas especificações de um dado ponto de vista, como o estrutural, impactam na satisfação dos requisitos de outros pontos de vista, como o dinâmico ou financeiro. A MBSE, entretanto, ainda não pode ser considerada uma disciplina madura. As ferramentas de software que a ela dão suporte, bem como as listas de melhores práticas de suas aplicações estão em constante evolução e aprimoramento. Dessa forma, a aplicação dos princípios da MBSE no design e seleção de soluções logísticas de armazenamento, com adoção da orientação a objetos, pode ser tida como uma ideia inovadora. / This work presents a method for warehouse storage solutions comparison. The existing research regarding the design and selection of such logistic solutions highlights the predominance of ad-hoc procedures, as well as the use of generic software tools. Therefore, the method herein presented shall be developed according to the model-based systems engineering (MBSE) principles, being describe through the system modeling language (SysML), and built inside a computer-aided system engineering (CASE) software tool, commercially available. The method\'s steps shall be thoroughly detailed, including the creation of a reference model for warehouse storage systems, and its further use in trade studies execution. Once the method is properly described, its validation is demonstrated through two case studies designed to compare storage solutions according to the number of pallet-positions oered, and its dimensional footprint. This work\'s main achievement is the possibility to simulate, in a single environment, warehouse storage solution\'s options that take into account parameters of the system as a whole, and not only its sub-systems separately. With that, it is possible to measure how changes in the specifications of a given view point, such as structural, impact the requirement\'s satisfaction of other view points, such as dynamic or financial. The MBSE, however, still can not be considered a mature discipline. The software tools that support it, as well as the lists of best practices of its applications are constantly evolving and improving. Thus, the application of MBSE\'s principles in the design, and comparison, of warehouse storage solutions, with the adoption of object orientation, can be considered an innovative idea.

Este trabalho desenvolve um método para a comparação de soluções logísticas de armazenamento e recuperação, com aplicações em centros de distribuição, depósitos, armazéns e demais estruturas equivalentes. Tais soluções podem implicar desde o uso de paleteiras manuais e empilhadeiras contra-balanceadas, até em arranjos mais complexos, envolvendo trans-elevadores operando em corredores de prateleiras com vários metros de altura. A literatura existente para o design e a escolha de tais soluções ressalta o prevalecimento de métodos proprietários e ad-hoc, auxiliados por ferramentas de software demasiadamente genéricas. Assim, o método aqui proposto é elaborado seguindo os princípios da Engenharia de Sistemas Baseada em Modelos (MBSE), sendo expresso através da linguagem OMG SysMLTM, e montado com o auxílio de ferramenta de software CASE (computer aided systems engineering) disponível comercialmente. Utilizando-se das técnicas mencionadas, este trabalho demonstra o passo-apasso da construção do método proposto, incluindo a formulação de um template de requisitos e de um modelo de referência, orientado a objetos, para sistemas logísticos de armazenamento e recuperação. Concluída a apresentação do método, o mesmo é aplicado em dois exemplos de estudos de viabilidade (trade-studies) que determinam soluções ótimas para um dado conjunto de requisitos de negócio. No primeiro exemplo tem-se como fator limitante o no de endereços de armazenamento, e no segundo a área disponível para construção do armazém. O principal resultado obtido com esse trabalho é capacidade de simular, em um único ambiente, escolhas de soluções logísticas de armazenamento que consideram parâmetros do sistema como um todo, e não apenas de seus sub-sistemas isoladamente. Isto tornou possível mensurar como alterações nas especificações de um dado ponto de vista, como o estrutural, impactam na satisfação dos requisitos de outros pontos de vista, como o dinâmico ou financeiro. A MBSE, entretanto, ainda não pode ser considerada uma disciplina madura. As ferramentas de software que a ela dão suporte, bem como as listas de melhores práticas de suas aplicações estão em constante evolução e aprimoramento. Dessa forma, a aplicação dos princípios da MBSE no design e seleção de soluções logísticas de armazenamento, com adoção da orientação a objetos, pode ser tida como uma ideia inovadora. / This work presents a method for warehouse storage solutions comparison. The existing research regarding the design and selection of such logistic solutions highlights the predominance of ad-hoc procedures, as well as the use of generic software tools. Therefore, the method herein presented shall be developed according to the model-based systems engineering (MBSE) principles, being describe through the system modeling language (SysML), and built inside a computer-aided system engineering (CASE) software tool, commercially available. The method\'s steps shall be thoroughly detailed, including the creation of a reference model for warehouse storage systems, and its further use in trade studies execution. Once the method is properly described, its validation is demonstrated through two case studies designed to compare storage solutions according to the number of pallet-positions oered, and its dimensional footprint. This work\'s main achievement is the possibility to simulate, in a single environment, warehouse storage solution\'s options that take into account parameters of the system as a whole, and not only its sub-systems separately. With that, it is possible to measure how changes in the specifications of a given view point, such as structural, impact the requirement\'s satisfaction of other view points, such as dynamic or financial. The MBSE, however, still can not be considered a mature discipline. The software tools that support it, as well as the lists of best practices of its applications are constantly evolving and improving. Thus, the application of MBSE\'s principles in the design, and comparison, of warehouse storage solutions, with the adoption of object orientation, can be considered an innovative idea.

Yes / The process of generating FMEA following document-centric approach is tedious and susceptible to human error. This paper presents preliminary methodology for robotic manufacturing process modelling in MBSE environment with a scope of automating multiple steps of the modelling process using ontology. This is followed by the reasoning towards automatic generation of process FMEA from the MBSE model. The proposed methodology allows to establish robust and self-synchronising links between process-relevant information, reduce the likelihood of human error, and scale down time expenses.

Technische Änderungen sind im Produktentstehungsprozess allgegenwärtig und beanspruchen einen hohen Anteil an vorhandenen Forschungs- und Entwicklungskosten. Gleichzeitig wird ca. ein Drittel aller technischen Änderungen aufgrund der hohen Systemkomplexität als kritisch eingestuft. Für den Umgang mit hoher Systemkomplexität werden Ansätze des Model-Based Systems Engineering (MBSE) als vielversprechend gesehen. MBSE stellt einen formalisierten Ansatz zur Erstellung und Analyse von domänenübergreifenden Systemmodellen dar, die u.a. in den Bereichen Anforderungsmanagement, Verifikation und Validierung sowie Analyse und Synthese unterstützen können. Die Entwicklung von technischen Systemen erfolgt in Generationen. Mit Hilfe des Beschreibungsmodells der Systemgenerationsentwicklung - SGE nach ALBERS können u.a. technische und ökonomische Risiken von technischen Änderungen auf Basis der Herkunft von Referenzsystemelementen sowie der Übernahme- und Neuentwicklungsanteilen eingeschätzt werden. Es existieren zudem viele weitere Ansätze im technischen Änderungsmanagement, die sich auf einzelne Aspekte der Ausbreitungs- und Auswirkungsanalyse fokussieren. Die modellbasierte Methodik AECIA - Advanced Engineering Change Impact Approach bietet eine ganzheitliche Unterstützung im technischen Änderungsmanagement. Erste Veröffentlichungen untersuchen insbesondere Aktivitäten zur Prüfung der Validität sowie die Modellierung und Analyse der Ausbreitung von technischen Änderungen. Ziel dieser Veröffentlichung ist es die AECIA-Methodik um ein Vorgehen zur Bewertung von technischen Änderungen zu erweitern und dieses am Beispiel einer Sondermaschine anzuwenden und zu evaluieren.

Mechatronic design is an enigma. On the one hand, mechatronic products promise enhanced functionality, and better performance at reduced cost. On the other hand, optimizing mechatronic design concepts is a major challenge to overcome during the design process. In the past, less attention has been paid to the life phases of a mechatronic product, and it was assumed that modifications in electronics and software will ensure that the product performs to expectation throughout its life time. However it has been realized that introducing design changes in mechatronics is not easy, since it is difficult to assess the consequences of a design decision, both during the design process of a new product, and during a design modification. It is also realized that there is a strong need to consider the product's life phases during the early phases of product development. Furthermore, it is rather difficult to perform a design optimization since it requires introducing changes across different domains, which is not well supported by the methods and tools available today. This thesis investigates the topic of mechatronic design and attacks some of the major challenges that have been identified regarding the design of mechatronic products. The goal is to provide support to the designers to facilitate better understanding of the consequences of their design choices as early as possible. The work also aims to provide support for assessing alternative design concepts, and for optimizing a design concept based on requirements, constraints and designer preferences at the time of design. The thesis highlights three main challenges related to mechatronic product development: the need for a common language during conceptual design; the inadequate information transfer between engineering domains; and the difficulty in assessing the properties of competing mechatronic concepts. A model-based integration approach is presented, and these key challenges are considered in relation to an integrated modeling and design infrastructure. The approach is illustrated through the design of two mechatronic systems- a two degrees-of-freedom robot, and a hospital bed propulsion system. Initial results provide evidence of good potential for information transfer across mechatronic domains. Although SysML was used for the case studies, some important questions were raised about its suitability as a common language for mechatronics. Suggestions for future work are: to utilize the developed infrastructure and incorporate a capability to model and assess consequences of competing design concepts; provide support for optimizing these concepts; and evaluate the usefulness of the developed infrastructure in a real-world design setting. These efforts should provide ample information to the designer for making adequate decisions during the design process. / QC 20110629

Ein wesentliches Ziel während der Produktentwicklung ist die frühzeitige Absicherung der Produkteigenschaften auf Basis der definierten Produktmerkmale unter Beachtung der äußeren Randbedingungen. Digitale Modelle und Methoden unterstützen den Produktentwickler bei der frühzeitigen virtuellen Evaluation des Produktes. [...] In diesem Beitrag wird eine Methodik präsentiert, die mit Hilfe der SysML-Modelle eine Simulation in VR ermöglicht. Die SysML-Beschreibung wird als Kern der Simulation dienen und das gesamte Simulationsmodell steuern. Weiterhin wird erläutert, wie die SysML-Beschreibung mit einem VR-Tool und einem Physikberechnungstool verbunden werden kann. Die in CAVE und HMD durchgeführten Simulationen wurden im Rahmen von Usability Tests evaluiert. Aus diesen Tests werden Ergebnisse präsentiert, die sich mit Verwendungsschwerpunkten in VR und der Zufriedenheit bei der Beurteilung von Produkten in VR beschäftigt haben. Schlussendlich wird ein Beispiel-Simulationsszenario in der CAVE-VR und einem Head Mounted Display (HMD) diskutiert. [... aus der Einleitung]