Enterprise-in-Environment Adaptation

Author(s):  
James S. Lapalme ◽  
Donald W. de Guerre

Enterprise Architecture (EA) is a consulting practice and discipline intended to improve the management and functioning of complex organizations. The various approaches to EA can be classified by how they define what is to be architected and what, as a result, is the relevant environment. Traditionally, management has been understood as “Planning, Organizing, Command, Coordinating, and Controlling” (POCCC), that is, the role is bounded within the organization. The corresponding EA approach suggests architecting IT systems to support management, with the implicit environment being members of the organization as well as partner organizations. As the objective of EA practice expands to include organizational members, technical systems, and a wider set of stakeholders, so too does the complexity it must address. This results in an enlarged domain of issues and concerns. Finally, if the objective of EA is a sustainable enterprise, then physical, societal, and ecological environments radically increase the complexity of actualizing this goal. Corresponding to this increase in scope is a parallel shift in the scope of management concerns. With the goal of pushing EA towards concerns regarding enterprise sustainability, an open socio-technical system design perspective of EA, which we have named Enterprise-in-Environment Adaptation (EiEA), is discussed. EiEA offers a comprehensive approach to respond to the demands for complexity management that arise when working towards enterprise sustainability; yet, it requires that organisations also embrace deep culture changes, such as participative design, worker empowerment, as well as shared accountability and responsibility, to name a few.

2015 ◽  
Vol 807 ◽  
pp. 247-256 ◽  
Author(s):  
Lena C. Altherr ◽  
Thorsten Ederer ◽  
Philipp Pöttgen ◽  
Ulf Lorenz ◽  
Peter F. Pelz

Cheap does not imply cost-effective -- this is rule number one of zeitgeisty system design. The initial investment accounts only for a small portion of the lifecycle costs of a technical system. In fluid systems, about ninety percent of the total costs are caused by other factors like power consumption and maintenance. With modern optimization methods, it is already possible to plan an optimal technical system considering multiple objectives. In this paper, we focus on an often neglected contribution to the lifecycle costs: downtime costs due to spontaneous failures. Consequently, availability becomes an issue.


2020 ◽  
Vol 68 (7) ◽  
pp. 529-540
Author(s):  
Tobias Kleinert ◽  
Frederik Zahn ◽  
Veit Hagenmeyer

AbstractThe class of hybrid systems describes most technical systems in great detail. However, the respective models and their behavior tend to be very complex. Recently, a new subclass of hybrid automata has been introduced, the Flat Hybrid Automata (FHA) that relies on the concepts of differential flatness for the continuous parts, and strongly connected automaton graphs for the discrete event part, in order to deal with the complexity from a design perspective. Therefore, we introduce in the present paper an approach to reduce the automaton graph of an FHA in a systematic way by removing edges from the adjacency matrix. The main contribution of the paper is twofold: Firstly, based on practical considerations we develop a heuristic algorithm to reduce the automaton graph. Secondly, we present possible ways to include knowledge about the system in the reduction.


Author(s):  
Mara Nikolaidou ◽  
Nancy Alexopoulou

System design is an important phase of system engineering, determining system architecture to satisfy specific requirements. System design focuses on analyzing performance requirements, system modeling and prototyping, defining and optimizing system architecture, and studying system design tradeoffs and risks. Modern enterprise information systems (EIS) are distributed systems usually built on multitiered client server architectures, which can be modeled using well-known frameworks, such as Zachman enterprise architecture or open distributed processing reference model (RM-ODP). Both frameworks identify different system models, named views, corresponding to discrete stakeholder’s perspectives, specific viewpoints, and could serve as a basis for model-based system design. The main focus of this chapter is to explore the potential of model-based design for enterprise information systems (EIS). To this end, the basic requirements for model-based EIS design are identified, while three alternative approaches are discussed based on the above requirements, namely, rational unified process for systems engineering (RUP SE), UML4ODP and EIS design framework.


2013 ◽  
Vol 393 ◽  
pp. 579-585
Author(s):  
Harald Anacker ◽  
Roman Dumitrescu ◽  
Jürgen Gausemeier ◽  
Cheng Yee Low

Recently, mechatronics as a self-contained discipline has undoubtedly shaped the development of technical systems. Mechatronics stands for the close interaction of mechanics, electronics, control engineering and software engineering. Due to the advancement of information and communication technologies, the functionality of mechatronic systems will go far beyond current standards. The increasing complexity requires a consistent comprehension of the tasks between all the developers involved. Especially during the early design phases, the communication and cooperation between the engineers is necessary to design a first overall system model. In addition, reusing of once successfully implemented solution knowledge is becoming increasingly important related to the overall context of the triangle of tension formed by time, cost and quality. In our work, we will present an approach for the identification of reusable controller strategies for the system design of advanced mechatronic systems.


IEEE Access ◽  
2017 ◽  
Vol 5 ◽  
pp. 27091-27102 ◽  
Author(s):  
Ngoc Duy Nguyen ◽  
Thanh Nguyen ◽  
Saeid Nahavandi

Sign in / Sign up

Export Citation Format

Share Document