MUSIC | MUlti-layers control&cognitive System to drive metal and plastic production line for Injected Components
01-09-2012
-31-08-2016
Projects overview
12 items found
BEinCPPS | Business Experiments in Cyber Physical Production Systems
11-01-2015
-31-10-2018
Show more information
ICT performance characteristics
Result items:
OPC-UA for M2M communication, and NGSI for data publishing on the cloud
General interoperability framework
Integration level interoperability
Result items:
All the information is stored in a single context in the Orion Context Broker.
AUTOWARE | Wireless Autonomous, Reliable and Resilient ProductIon Operation ARchitecture for Cognitive Manufacturing
01-10-2016
-30-09-2019
Show more information
ICT performance characteristics
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
Integration level interoperability
Semantic/information interoperability
Result items:
DIGICOR | Decentralised Agile Coordination Across Supply Chains
01-10-2016
-30-09-2019
Show more information
ICT performance characteristics
Interoperability (ICT)
General interoperability framework
Comment: External applications can communicate with OPC-UA based middleware (subject to authentication etc) to ingest data e.g. from factories
Comment: The communication middleware in the DIGICOR platform will be based on OPC-UA standard. In order to facilitate the flow of data to and from the middleware, the project will develop Data (harmonisation and transformation) Maps. The Data Maps will be offered as microservices to address the semantic and syntactic interoperability issues. In addition, standardised service interfaces will be defined to allow the discovery and enactment of services within the DIGICOR Platform.
Result items:
UPTIME | UNIFIED PREDICTIVE MAINTENANCE SYSTEM
01-09-2017
-28-02-2021
Show more information
ICT performance characteristics
Z-BRE4K | Strategies and Predictive Maintenance models wrapped around physical systems for Zero-unexpected-Breakdowns and increased operating life of Factories
01-10-2017
-31-03-2021
Show more information
ICT performance characteristics
Comment:
Α Web API will return semantic data. The communication interface is through the SPARQL query engine. Z-BRE4K ontology is implemented with the Open Semantic Framework (OSF), an integrated software stack using semantic technologies for knowledge management. Furthermore, JSON formatted data from the shop floor is transferred through a MQTT broker, to be finally stored in I-LiKe machines internal data repository. IDS connectors are used to transform data into the NGSI format, move the data to the ORION context broker to be finally consumed by other applications. Also, the Quality Information Framework (QIF) standard guarantees interoperability since it defines an integrated set of information models that enable the effective exchange of metrology data throughout the entire manufacturing quality measurement process – from product design to inspection planning to execution to analysis and reporting. OpenCPPS (part of AUTOWARE) will provide support for selected mainstream communication protocols and will define the proper interfaces for other communication protocols to be plugged-in.
General interoperability framework
Comment:
Ontology-based data integration is part of the Z-BRE4K solution. Ontology effectively combines data and/or information from multiple heterogeneous sources. The ontology semantics used by SPL program is described through OWL. OWL follows the RDF syntax, so SPARQL is suitable for seamlessly querying the ontology defined by OWL. SPARQL will be used as the transformation language for converting Semantic data to corresponding syntax data. IDS connectors are used in Z-BRE4K to guarantee the interoperability among the various components that are not part of the Industrial Data Space. Part of connectors functionality is to transform data to/from NGSI format data in order to be shared by the ORION context broker.
Comment:
Z-BRE4K ontology contains information about all Z-BRE4K relevant data (metadata), linked in a way described by a controlled, shared vocabulary. The data relationships are part of the data itself, in one self-describing information package that is independent of any information system. In simple terms, this means that data from various sources can be easily harmonised. The shared vocabulary, and its associated links to an ontology, provide the foundation and the capabilities of machine interpretation, inference, and logic.
KYKLOS 4.0 | An Advanced Circular and Agile Manufacturing Ecosystem based on rapid reconfigurable manufacturing process and individualized consumer preferences
01-01-2020
-31-12-2023
SeCoIIA | Secure Collaborative Intelligent Industrial Assets
01-12-2019
-31-05-2022
Show more information
ICT performance characteristics
Interoperability (ICT)
General interoperability framework
Integration level interoperability
Semantic/information interoperability
Result items:
Show more information
ICT performance characteristics
Result items:
ATS Bus - Enabled a single, common service bus for data exchange between the PLCs and other high level components of the system, including a SCADA system. Used a broker-based publish-subscribe approach to decouple the physical sources and destinations of the data to facilitate reconfigurability.
Nservicebus - The underlying technology which enabled the ATS Bus to exchange data.
OPC UA (Kepware) – Many devices could not interface directly with the service bus, so OPC UA was used to extract data and publish it to the service bus.
General interoperability framework
Integration level interoperability
Semantic/information interoperability
Result items:
OPC UA (Kepware) – Many devices could not interface directly with the service bus, so OPC UA was used to extract data and publish it to the service bus.
Show more information
ICT performance characteristics
Result items:
ATS Bus - Enabled a single, common service bus for data exchange between the PLCs and other high level components of the system, including a SCADA system. Used a broker-based publish-subscribe approach to decouple the physical sources and destinations of the data to facilitate reconfigurability.
Nservicebus - The underlying technology which enabled the ATS Bus to exchange data.
OPC UA (Kepware) – Many devices could not interface directly with the service bus, so OPC UA was used to extract data and publish it to the service bus.
General interoperability framework
Integration level interoperability
Semantic/information interoperability
Result items:
OPC UA (Kepware) – Many devices could not interface directly with the service bus, so OPC UA was used to extract data and publish it to the service bus.
Show more information
ICT performance characteristics
General interoperability framework
Integration level interoperability
Semantic/information interoperability
Result items:
Used as the primary date exchange method for the demonstrator. Links items on the shop floor to the SCADA.
Show more information
ICT performance characteristics
General interoperability framework
Integration level interoperability
Semantic/information interoperability
Result items:
Used as the primary date exchange method for the demonstrator. Links items on the shop floor to the SCADA.
OPC_UA has been intensively applied in the Data_driven Digital Twin of existing production line