## 4 Emergent Configurations in the IIoT
### Architectural Description of an EC Process Management  
An architecture for the IoT process management consists of seven core components which can be used to describe the core components of an ECM. These components of an EC architecture include; _goal manager_, _adaptation manager_, _context manager_, _enactment engine_, _business rules_, _domain ontology_ and _system KB_[61; 63; 64; 65]. The responsibilities of these components are explained subsequently.  
Figure 3: Illustration of the physical and logical layers of an EC.  
Firstly, the primary role of the goal manager according to Figure 4 is to interpret the goals of the user and then specify suitable goal location boundaries. The goal manager is also responsible for analyzing available IoT objects/services while making efforts to exploit the functionalities of these objects towards the actualization of user goals. Furthermore, the goal manager is responsible for suggesting relevant and alternative services to the user in order to enable the user to achieve his/her goals, while also deriving subgoals for the EC to meet user needs. Moreover, the goal manager is responsible for connecting and coordinating the available IoT connected devices for the actualization of the user's expectations.  
Secondly, the adaption manager is responsible for managing the MAPE-K loop which involves _monitoring_ of changes in the context, for instance, discovery of new connected devices and faulty devices by dynamically configuring and updating the EC system to meet the user goals. The adaptation manager also _analyses_ the effects of the system changes for the satisfaction of user goals while _planning_ all changes to the subgoal model of the EC. Other roles of the adaption manager according to the MAPE-K loop involves _execution_ of the planned changes by communicating with the enactment engine as depicted in Figure 4.  
The context of the EC such as _system KB update_ and _detection of dynamic events_ in the environment is managed and maintained by the context manager. The primary context (which is the _raw data_) that made available from sensing is as well maintained by the context manager while inferring new business rules based on the context.  
It is attention-worthy to mention that the primary responsibility of the enactment engine is to give instructions to IoT connected devices while coordinating their activities and ensuring effective collaboration between the devices in order to satisfy user needs. The business rules component, on the other hand, is a central location that consists of domain related and theorize rules which are based on the context changes whereas the domain ontology host a classification of Semantic information about domains that are employed for the derivation of the EC subgoals for example, \"a smart room\". Finally, the system KB is a container that houses information of the EC context.  
The architecture of an EC process is refined in [62] as diagrammatically illustrated in Figure 5. A detailed description is as well presented for all components in the refined architecture for realizing EC in the IoT (Eco-IoT), in addition to their interaction with the IoT platform. A first prototype is developed using Java programming language, while performance is evaluated to validate the feasibility of EC in some key components of the refined architecture. Interested readers are referred to [62], for more information on the refined Eco-IoT architecture.  
Figure 4: An architecture of an EC management process.