A new approach to master complexity in model driven Systems Engineering Jan Vollmar Siemens AG Corporate Technology, Erlangen, Germany Jan.vollmar@siemens.com Copyright © held by the author. ABSTRACT By combining the two viewpoints (i.e. tasks, interests) a Companies in the Engineer-To-Order (ETO) business are ‘core model matrix’ is created as a consistent view on the facing various challenges [1][2]. The competitive pressure is system. At the intersection (matrix cell) of an interest and a rising, new competitors are emerging, and customers call for task, the specific requirements/impacts are described. higher flexibility and global presence of ETO companies. As a result, potential contradictions between requirements Engineering [3]is a core activity of the ETO business, defining can be systematically detected, analyzed and resolved still in 50-60% [4]of the total life-cycle cost of the produced solutions, the problem space. The matrix representation also allows for yet causing just 5-15% [5]of the internal delivery costs, precisely recognizing for which of the tasks which interest has engineering is the starting point to tackle complexity. to be considered in which way (i.e. interest only influences Siemens has started an internal initiative “Integrated specific tasks). The complexity of the system architecture to be Systems Development” in which proven systems engineering defined later can therefore be substantially reduced. approaches and new practices are merged to master complexity Furthermore tasks and interest can be prioritized in order to in ETO and large development projects. An essential part of ensure focus and enable trade-off analysis. The overall model this approach is the so-called ‘core model’ [6] that is a can also be communicated in a structured way and a common minimal, comprehensible description of the challenge to be understanding across all participating stakeholders can be solved which is created in a joint approach with the achieved. involvement of all relevant stakeholders. In the next step, the transition from the problem space to A core model characterizes the system of interest in two the solution space must be accomplished. This can happen in major aspects, the relevant user and their purposes/ tasks that parallel and can be continuously reviewed for target are associated with the system (e.g. start moving, perform achievement with the defined ‘core’. The core model approach acceptance test) and the interests of relevant stakeholders (e.g. provides also guidance for the architecture model as a suitable reduce processing time, ensure compliance to customer component structure can be obtained by weighing up tasks and standards). This core is also forming the core for other models interests and by balancing out conflicts from the core model to (i.e. requirement model, architecture model and test model). the best possible extent. Complex systems can be modeled by applying this model in a recursive approach on identified Just like any other systems engineering method, core subsystem or component if necessary. modeling must resolve the dilemma of supplying an adequately complete description on the one hand (all necessary This approach has been piloted in different industrial requirements that are needed for the following steps and domains and examples from these projects will be shown to decisions) but, on the other hand, remaining transparent and illustrate the implementation of this new method. communicable and also feasible in terms of scope and effort Core modeling has proved to be helpful in practice as a when creating it. The needed focus is achieved by the highly efficient and target oriented method. This approach following characteristics: showed in the pilot projects, that an improved and common understanding of the overall system, fewer inconsistencies in  The core model only contains content from the problem communication thanks to a common basis, faster and more space; comprehensible decision making and continuous review of  The core model only contains content at a commonly target achievement could be realized. The possibility to model agreed abstraction level, i.e. all descriptions are at the the system on different, but well defined, levels of abstraction same level of detail; helps to manage and even to reduce the complexity. As the core model is situated in the problem space, the creativity of  The core model only contains content that is relevant to finding new solutions is strongly supported. economic success or a necessary prerequisite for implementation or boosts internal benefit (e.g. reducing Above and beyond system development, core modeling production efforts). also offers portfolio strategy advantages. Products can be aligned to the tasks to be performed, several products in one domain are delimited from one another in relation to their [4] Percivall, G. (1992): Systems Engineering in the automotive industry. purpose and in a clearly communicable manner, and In: Proceedings of the 2nd Annual Conference INCOSE, S. 501–508. unnecessary overlaps and product complexity (i.e. variants) are [5] Gepp, M. (2014), Standardization programs as an approach for efficiency improvements in industrial plant engineering,’ Phd thesis, reduced and last but not least customer satisfaction can be Nueremberg: Dr. Kovac improved as the products are addressing the ‘real’ user purpose [6] Kochseder, R. et al (2016), ‘Komplexität beherrschen mit Core and support them in fulfilling their tasks. Modelling” The linking between the core model and other relevant models (e.g. requirements model, test model), as well as the AUTHOR BIOGRAPHY tool support for the core model and the implementation in Jan Vollmar is Principal Engineer at Corporate existing tool landscape will be a topic for future research. Technology of Siemens AG. He is responsible for improving and developing internal engineering organizations. He is REFERENCES managing consulting projects focusing on engineering strategy development, Systems Engineering implementation and global [1] Large Industrial Plant Manufacturer’s Group (VDMA) (2015), ‘Staying competitive in a volatile environment’ Status Report 2013/2014, engineering collaboration. In international research project his Frankfurt. focus is on improving and developing new methods for [2] Gepp, M. et. al (2013), ‘Assessment of engineering performance in Systems Engineering. Before joining Corporate Technology industrial plant business,’ IEEE IEEM 2013. Jan Vollmar has been senior project manager within Siemens [3] Hicks, C.; Earl, C.F; McGovern, T. (2000), ‘An analysis of company plant building business in the automobile industry. He has structure and business processes in the capital goods industry in the UK. studied mechanical engineering at the Karlsruhe Institute of In: IEEE Transactions on engineering management’, pp. 414–423. Technology.