# Holonic Regineering to Foster Sustainable Cyber-Physical Systems Design in Cognitive Manufacturing
## 3 Proposal for the Reengineering of Sustainable Cognitive Manufacturing
### Technological Mapping of Holonic Cognitive Sustainable Architecture
#### 3.5.1 Architecture Functional Specification Model  
In terms of communication infrastructures, there is a very established tendency towards \"network softwarization\" in which once inflexible communications and services are being replaced by very flexible solutions that involve standard computing equipment, open standards and open source implementation [149]. The technological implementation of Holonic systems resulting from the reengineering of cognitive systems can be carried out using Open Manufacturing Platforms (OMP), or open technologies offered by different manufacturers such as BMW group, Siemens, IBM Watson Analytics or Microsoft Azure. An alternative ad hoc solution from the experience and information technologies that companies have available or wish to acquire. In both cases the specification of the Holonic architecture of a reengineering project in an architecture of microservices associated with cyber-physical holons is a tool or previous step to the implementation in a specific technology or manufacturing platform. Container-based technology presents itself as an opportunity to implement the proposed holonic architecture. Specifically, the Arrowhead Framework [150] architecture is based on the use of containers, allowing the reduction of latency times, scalability, the integration of new components and increased security. To ensure interoperability in IoT, this architecture selects Service Oriented Architecture (SOA). SOA is characterized by a service-based data exchange between a service producing system and a service consuming system. In SOA, two systems do not need to know each other at the time of design to allow real-time data exchange. A new SOA service requires registering in the service registry where it can be detected by any other service on the network. Real-time coupling is initiated by an orchestration mechanism, primarily supported by the authentication and authorization mechanisms supported by an orchestration system that provides the requesting consumer with the endpoint of the selected producer. Each device and software system is responsible for its own data and functionality, and may be independent of other systems. Once a service exchange is established between two systems, this exchange can continue without the additional involvement of any supporting services or functionality. Basic elements of the system that are mandatory to provide the minimum recommended services in a functional unit are described below and showed in Figure 8[150]:  
* Registration system: responsible for registering the services and enabling the discovery of registered services. * Authorization system: is responsible for providing credentials to the systems in the functional unit, allowing system authentication and service exchange authorization. Manage access to specific resources using rules, control external access to specific resources, and publish authorizations. * Orchestration system: it is responsible for providing information on service consumption patterns to the system registered in the local cloud. Manage connection rules for specific services. If necessary, the authorization system is consulted to verify whether the system consuming the service can be authenticated and authorized to consume the requested service. * Gateway manager: helps locate services offered by neighboring containers. Located the service, it is responsible for establishing a secure communication route between client and server. Once the basic elements that a functional unit must have are defined, the system applications (such as consumers and service producers) necessary to guarantee the functionality of the specific unit can be incorporated. An essential requirement between functional units is the ability to communicate with each other.