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.
Comment: Refrain from proprietary formats; if necessary, build adapters that go both ways (import/export).
Platform-independent micro-service architecture (micro-services are designed to be independent of Bluemix stack (but can use it if it’s there))
Standards compliance for product categorisation (eClass), business process specification (UBL), oneM2M for manufacturing interoperation.
Comment: Each SAFIRE service will be developed as own docker container, to allow easy distribution and scalability of whole SAFIRE solution in the cloud
Comment: According to the RAMI 4.0 architecture, the “standard” way for Industrie 4.0 platforms to integrate legacy equipment (or any other kind of legacy “object”, including software components) into will be to encapsulate them inside an ad-hoc Administration Shell wrapper, which will expose them as I4.0 Components. The I4.0 interface specification has not been published yet, but a key enabling technology will probably be OPC UA, used as both a communication protocol and a data meta-model. In FAR-EDGE, OPC UA will be one of the field communication technology supported.
Comment: DIGICOR applications are developed as standalone plug-and-play tools with dedicated interfaces. External applications (e.g. production planning, schedulling, workflow management etc) can also be deployed on DIGICOR toolstore
Comment: Interoperability between installed equipment and infrastructure (machines, environment, people) is critical to capture and process data for the COMPOSITION IIMS components.
Comment: Log-Oriented Architecture through Blockchain Implementation for providing Audit Trail for Manufacturing & Supply Chain data, Matchmaking services (including semantic queries) as part of the Open Marketplace
Comment: CPS interface: Extension of automation objects to include/interface with behavioral models. HW/SW wrapping of legacy and/or proprietary systems
Comment: Integrating "digital" applications running in other platform into the real-time automation engineering environment is a very interesting use-case
Comment: IEC-61499 is modular and OO in its approach to real-time automation. Moreover, it allows to "encapsulate" interfaces to other platform coherently with this OO approach.
Comment: HORSE is an open platform where heterogeneous robots and other automation equipment, as well as new software modules can be integrated via OSGi and managed.