Z-Fact0r | Zero-defect manufacturing strategies towards on-line production management for European factories
01-10-2016
-31-03-2020
Calltopic: FoF.2016.03
Z-Fact0r middleware platform and components Result description The integration of the middleware with the multi sensor/actuator cloud will be achieved through the Device Managers which will allow an interoperable communication mechanism based on standardized protocols
Connectivity & network interoperability – communication protocols Taxon title Connectivity & network interoperability – communication protocols
AAA - Access, Authorisation and Authentication Taxon description Unauthorized access could be someone who has been able to access the network from the outside, performing actions that have not been authorized and cannot be justified.
Data communication and interoperability Comments 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.
- Load test
- Stress test
- Spike test
- Endurance test
- Scalability test
- Volume test
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.
The Incremental Integration Strategy (IIS) provides a unified framework for all the EU distributed partners, to work on common principles. By following the IIS, we try to ensure that the integration will be successfully executed in a timely manner. It defines a number of factors to monitor and steps to execute.
The IIS manifests that the components are integrated and tested incrementally and tested to ensure smooth interaction among them. Every component is combined incrementally, i.e., one by one till all components are integrated logically to make the required application, instead of integrating the whole system at once and then performing testing on the end product. Integrated components are tested as a group to ensure successful integration and data flow between components. The process is repeated until all components are combined and tested successfully. The tests included in the IIS are:
During the integration phase the same communication protocols were used: HTTP and AMQP for the data exchange. Also there is Wi - Fi connection for integration the various components and their updates on premises or on cloud during the integration process of the system. Finally, FTP was used during the integration phase for quick transfer of files on the shop floor premises.
