A Design of the Resilient Enterprise: A Reference Architecture for Emergent Behaviors Control

Abstract

The sooner disruptive emergent behaviors are detected, the sooner preventive measures can be taken to ensure the resilience of business processes execution. Therefore, organizations need to prepare for emergent behaviors by embedding corrective control mechanisms, which help coordinate organization-wide behavior (and goals) with the behavior of local autonomous entities. Ongoing technological advances, brought by the Industry 4.0 and cyber-physical systems of systems paradigms, can support integration within complex enterprises, such as supply chains. In this paper, we propose a reference enterprise architecture for the detection and monitoring of emergent behaviors in enterprises. We focus on addressing the need for an adequate reaction to disruptions. Based on a systematic review of the literature on the topic of current architectural designs for understanding emergent behaviors, we distill architectural requirements. Our architecture is a hybrid as it combines distributed autonomous business logic (expressed in terms of simple business rules) and some central control mechanisms. We exemplify the instantiation and use of this architecture by means of a proof-of-concept implementation, using a multimodal logistics case study. The obtained results provide a basis for achieving supply chain resilience “by design”, i.e., through the design of coordination mechanisms that are well equipped to absorb and compensate for the effects of emergent disruptive behaviors.

A Measurement Instrument for Enterprise Architecture Resilience Research: A Pilot Study on Digital Transformation

“…Bemthuis et al [20], present another view on EA resilience by studying it from the perspective of cyberphysical systems of systems and emergent behaviors. Additionally, the authors coin the term Enterprise resilience as a type of resilience that can be facilitated by designing EA models.…”

Enterprise Architecture Resilience by Design: A Method and Case Study Demonstration

“…However, the long-term impact of this rapid digital transformationon the economy and society is not yet known. Thus, instead of reactively responding to disruptions, organizations should consider designing resilience measures in their processes and infrastructure in order to anticipate and adapt to disturbances by reorganizing, changing, and learning from past events [4].…”

What Method is to Achieve the Purposes of Systems-of-Systems Having Different Boundaries as System-of-Systems for Each Organization?

“…Thus, each position cannot understand the difference between how to use and boundaries of each SoS which is established a combination of the above common IT systems and each position's specific IT systems. The reason why each position cannot understand the difference between how to use and boundaries of each SoS is that organizations have become complex socio-technical systems of heterogeneous systems (e.g., system of systems) that pursue their ownsometimes conflicting-goals, behaviors, functions, and requirements [9]. The behavior executed by such local autonomous entities may, however, conflict with the system-wide goals [9].…”

“…The reason why each position cannot understand the difference between how to use and boundaries of each SoS is that organizations have become complex socio-technical systems of heterogeneous systems (e.g., system of systems) that pursue their ownsometimes conflicting-goals, behaviors, functions, and requirements [9]. The behavior executed by such local autonomous entities may, however, conflict with the system-wide goals [9]. Despite these occasionally conflicting behaviors and goals, enterprises should have the ability to cope with emerging threats and to adapt to turbulent environments, while satisfying stakeholders' needs [9].…”

“…The behavior executed by such local autonomous entities may, however, conflict with the system-wide goals [9]. Despite these occasionally conflicting behaviors and goals, enterprises should have the ability to cope with emerging threats and to adapt to turbulent environments, while satisfying stakeholders' needs [9]. Therefore, we used the above situation which will lead the stakeholders (sales department and the parts department and systems engineers and designers) to misunderstand or not consider other departments in this case, in designing the SoS for achieving two or more purposes simultaneously.…”