Projects overview

Sort by

Toggle all information

FAR-EDGE | Factory Automation Edge Computing Operating System Reference Implementation

01-10-2016

-

31-10-2019

Show more information
ICT performance characteristics
Interoperability (ICT)
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.
Result items:
CPS Data Model Architecture - M24 release
CPS Data Model Architecture - M24 release
General interoperability framework
Application level interoperability
Open APIs and Communication Protocols
Comment: The Plaform defines its own Open API

Daedalus | Distributed control and simulAtion platform to support an Ecosystem of DigitAL aUtomation developerS

01-10-2016

-

30-09-2019

Show more information
ICT performance characteristics
Interoperability (ICT)
Comment: CPS interface: Extension of automation objects to include/interface with behavioral models. HW/SW wrapping of legacy and/or proprietary systems
General interoperability framework
Application level interoperability
Comment: Integrating "digital" applications running in other platform into the real-time automation engineering environment is a very interesting use-case
Open APIs and Communication Protocols
Comment: IEC-61499 is open and interoperable by design. From within IEC-61499, interfaces to other platforms can be developed in C++ to generate specific APIs. Other platforms wanting to interact over an IEC-61499 communication bus can easily implement the protocols without changing their internal programming.

DIGICOR | Decentralised Agile Coordination Across Supply Chains

01-10-2016

-

30-09-2019

Show more information
ICT performance characteristics
Interoperability (ICT)
General interoperability framework
Application level interoperability
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
Open APIs and Communication Protocols
Comment: Communication with middleware is supported by open data model to be developed.

SAFIRE | Cloud-based Situational Analysis for Factories providing Real-time Reconfiguration Services

01-10-2016

-

30-09-2019

Show more information
ICT performance characteristics
Interoperability (ICT)
General interoperability framework
Application level interoperability
Comment: Each SAFIRE service will be developed as own docker container, to allow easy distribution and scalability of whole SAFIRE solution in the cloud
Open APIs and Communication Protocols
Comment: Publish / Subscribe message system Apache Kafka will be used for communication in SAFIRE

NIMBLE | Collaboration Network for Industry, Manufacturing, Business and Logistics in Europe

01-10-2016

-

31-03-2020

Show more information
ICT performance characteristics
Interoperability (ICT)
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.
General interoperability framework
Application level interoperability
Open APIs and Communication Protocols
Comment: NIMBLE Task 2.3 OpenAPI for the NIMBLE Platform

vf-OS | Virtual Factory Open Operating System

01-10-2016

-

31-10-2019

Show more information
ICT performance characteristics
Interoperability (ICT)
General interoperability framework
Application level interoperability
Open APIs and Communication Protocols
Comment: Middleware providing messaging and Pub/Sub Services to all components. Virtual Factory Devices Drivers and Open APIs, a set of modules that provide interfaces to physical assets (eg, Sensors) and virtual assets (eg, ERP systems and data) and ease their use in vf-OS

AUTOWARE | Wireless Autonomous, Reliable and Resilient ProductIon Operation ARchitecture for Cognitive Manufacturing

01-10-2016

-

30-09-2019

Show more information
ICT performance characteristics
Interoperability (ICT)
Comment: Goal: AUTOWARE will establish and push forward an open CPPS ecosystem, allowing SMEs to access all the different components in order to develop digital automation cognitive solutions for their manufacturing processes. . Leveraging reference heterogeneous communications and networking architecture to support connectivity & data management in CPPS. To allow the interaction and interworking of the heterogeneous communications and networking technologies necessary to support the ubiquitous connectivity of CPPS.
General interoperability framework
Application level interoperability
Open APIs and Communication Protocols
Wireless communication protocols
Comment: 5G, WirelessHart

COMPOSITION | Ecosystem for Collaborative Manufacturing Processes _ Intra- and Interfactory Integration and Automation

01-09-2016

-

31-08-2019

Show more information
ICT performance characteristics
Interoperability (ICT)
Comment: Interoperability between installed equipment and infrastructure (machines, environment, people) is critical to capture and process data for the COMPOSITION IIMS components.
Result items:
Interoperability for M2M & HMI in factory environments II
Interoperability for M2M & HMI in factory environments II
General interoperability framework
Application level interoperability
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
Open APIs and Communication Protocols
Comment: Integrated Digital Factory Model for Intra-Factory & MarketPlace Open Reference Data Model for Inter-Factory Support (bids, offers and transactions, etc.)
Wireless communication protocols
Comment: Cyber-physical systems usually come with heterogeneous communication protocols, many of them widely used like KNX, ZigBee, ModBus, etc. All the different field buses are integrated in the BMS for data collection and, afterwards, the information is forwarded though the local WLAN. Scalability, re-configurability and inter-operability with existing infrastructure will be a key decision factor in installing such CPS.

Z-Fact0r | Zero-defect manufacturing strategies towards on-line production management for European factories

01-10-2016

-

31-03-2020

Show more information
ICT performance characteristics
Interoperability (ICT)
Comment:

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.

General interoperability framework
Application level interoperability
Comment:

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.

Open APIs and Communication Protocols
Comment:

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:

  1. GET call by the component to initiate communication
  2. The component is authenticated by the iLike machine
  3. The iLike machine appoints the respective topics for the components to publish or subscribe to them
  4. A component published data to a topic and another subcribes to the topic to receive the data

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.
 

Wireless communication protocols
Comment:

Wireless communication of the Z-Fact0r solution was based on Wi - Fi protocol.

QU4LITY | Digital Reality in Zero Defect Manufacturing

01-01-2019

-

31-07-2022

Show more information
ICT performance characteristics
Interoperability (ICT)
Result items:
Connectivity Technologies for Autonomous Quality (Version 1)
Connectivity Technologies for Autonomous Quality (Version 1)
D2.11 Reference Architecture and Blueprints (Version 1)
D2.11 Reference Architecture and Blueprints (Version 1)
Library of Integrated, Interoperable Digital Enablers (Version 1)
Library of Integrated, Interoperable Digital Enablers (Version 1)
Standards Compliance and Interoperability Specification (Final version)
Standards Compliance and Interoperability Specification (Final version)
General interoperability framework
Application level interoperability
Open APIs and Communication Protocols
Wireless communication protocols
IEEE 802.15.4-2020 - IEEE Standard for Low-Rate Wireless Networks
Comment: Associated to QU4LITY Reference Architecture: Network

Details: Connectivity requirements: Specifications (models) for low-data-rate wireless connectivity with fixed, portable, and moving devices with no battery or very limited battery consumption requirements

Powered by Chris Decubber BV