Lab scale use case deployment with lessons learnt II

Summary

This deliverable outlines the architecture defined for integration activities, a brief overview of the components developed as well as any lessons learnt during the initial integration activitiesin a lab scale environment. It also includes an integration plan for the inter-factoryandintra-factory use casesand a set of recommendations, conclusions and next steps. The first docker server used in the project was deployed by ISMB for lab scale use by the COMPOSITION components. The server was used in the first phase of the project. Whenreal and live data started to be used, the server could not accommodate the project’s needs. A new production server was deployed by FIT, with more resources and able to accommodate the data traffic, calls and requests. All COMPOSITION components now use the production server for deployment and dockerisation.Areference architecture has been successfully developed that is now being used in individual use cases.To date the following components have been developed based on this architecture, where possibleleveraging from commercially available softwaremodules and open source widely used protocols.

  • •Authentication
  • Big Data Analytics
  • BlockChain Connector
  • Commissioning System
  • Deep Learning Toolkit
  • Intrafactory Interoperability Layer
  • Manufacturing Big Data Storage
  • Manufacturing Decision Support System
  • Market Event Broker
  • Matchmaker
  • Real Time Multi-Protocol Event Broker
  • Reputation and Trust Model
  • Requester Agent
  • SIEM (Security Information and Event Management)•Simulation and forecasting tool
  • Supplier Agent

Thedevelopment and dockerisation state of the components have been outlined, along with action plans for use in inter-and intra-factory use cases.At a high level there are two communication mechanisms in the COMPOSITION system: message-based communication over MQTT or AMQP using the Event Broker1, and request-response REST HTTP interfaces (D2.4The COMPOSITION Architecture Specification II). With a few exceptions2, the components are loosely coupled and integrated in the system by conforming to a commoncommunication infrastructure and data schemas. There are dependencies on data generated by other components, but for most of the data, the dependency is not direct as this data is distributed through the event broker, so the direct connection is to this component.