A4BLUE | Adaptive Automation in Assembly For BLUE collar workers satisfaction in Evolvable context
01-10-2016
-30-09-2019
01-10-2016
-30-09-2019
01-09-2012
-31-08-2016
01-01-2015
-31-12-2017
01-12-2014
-30-11-2018
01-01-2015
-31-12-2017
01-01-2015
-31-12-2018
01-10-2016
-30-09-2019
01-10-2016
-30-09-2019
11-01-2015
-31-07-2020
10-01-2015
-30-09-2018
01-11-2015
-31-10-2017
01-01-2019
-31-07-2022
01-06-2022
-31-05-2025
01-10-2016
-31-03-2020
01-10-2016
-30-09-2019
01-09-2016
-31-08-2019
01-10-2016
-31-10-2019
01-10-2016
-30-09-2019
01-10-2016
-31-10-2019
01-10-2016
-31-03-2020
Data communication between components is essential for the project. End users create data on their shop floor with embedded sensors on the machines, new integrated sensors developed for the project. All these data is propagated in the system with data communication protocols, such as HTTP and AMQP, creating a data stream process in the system. Interoperability between the data communication protocolos and brockers is crucial for a successful result of the data communication of the system. Various data sources work together and use different communication protocols. As a result, all these components and protocols should seamlessly work and their interoperability is what helps them. A message brocker was developed for the project, based on AMQP for data communication. In the initial phases of the project, there were also RESTful APIs that helped in the initial development of the components.
Z-Fact0r components were developed by different technical providing partners as mostly standalone components. The result was that on each shop floor worked many different components individually. An interoperability level was necessary for the Z-Fact0r system to be a solution to work as a whole. Various integration processes and extensive planning took place during the project and created an integrated system as a final product. The interoperability between the components was the first essential characteristic for the integration process. The components were desinged in the system, in a way that allowed them to operate together without conflicts during data streaming and operation.
Z-Fact0r architecture was based on the modular design of the components and then the integration of the components to a complete system. For each component a specific architecture was followed by the responsible technology providing partner, base on the use cases, scenarios, end user requirements and technical requirements. The desing for each component was documented in the respective deliverable. Each component also followed the technological trends of their fields and exploited the state of the art of the field. An overall ontology of the Z-Fact0r system was created to include all possible actors, functions, assets etc. All components were initially deployed as standalone applications and then an integration plan was implemented. Z-Fact0r project followed the Incremental Integration Strategy (IIS) where the components were deployed on the shop floors and integrated as one.
The Z-Fac0r project followed the AMQP and MQTT protocols for the communication between the components. A message brocker was develope by HOLONIX and was called iLike. The iLike implemented the publish/subscribe mechanism for all components which connected to it. The components were authorised in the iLike brocker and repository with a Bearer Token and then used the mechanism to publish or receive the data. An open API was used to create REST GET calls in order to initiate the communicatio between the component and the brocker. The communication steps between the component and the brocker were:
The data from the iLike machines are sent into the cloud to a broker using MQTT protocol (a lightweight protocol that transports messages between devices), it stores the data as messages, so the subscribers can get the values.
MQTT broker can easily scale from a single device to thousands, manage and tracks all client connection state and permit secure connections.
01-10-2016
-31-03-2021
01-10-2016
-30-09-2019
01-09-2017
-28-02-2021
01-11-2017
-28-02-2021
01-05-2017
-31-10-2020
INFLATE protocol