A4BLUE | Adaptive Automation in Assembly For BLUE collar workers satisfaction in Evolvable context
01-10-2016
-30-09-2019
Projects overview
34 items found
PreCoM | Predictive Cognitive Maintenance Decision Support System
01-11-2017
-28-02-2021
ROSSINI | RObot enhanced SenSing, INtelligence and actuation to Improve job quality in manufacturing
01-10-2018
-31-03-2022
SatisFactory | A collaborative and augmented-enabled ecosystem for increasing SATISfaction and working experience in smart FACTORY environments
01-01-2015
-31-12-2017
Show more information
ICT performance characteristics
Interoperability (ICT)
General interoperability framework
Integration level interoperability
Result items:
ReCaM | Rapid Reconfiguration of Flexible Production Systems through Capability-based Adaptation, Auto-configuration and Integrated tools for Production Planning
11-01-2015
-31-10-2018
Show more information
ICT performance characteristics
Interoperability (ICT)
General interoperability framework
Integration level interoperability
Result items:
TWIN-CONTROL | Twin-model based virtual manufacturing for machine tool-process simulation and control
10-01-2015
-30-09-2018
Show more information
ICT performance characteristics
Result items:
General interoperability framework
Integration level interoperability
INCLUSIVE | Smart and adaptive interfaces for INCLUSIVE work environment
01-10-2016
-30-09-2019
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
Comment: IISF based access control framework to allow integration of additional external components into SAFIRE. OPC-UA plug-in for the data ingestion. External systems can ingest data into SAFIRE solutio by either using pre-developed plug-ins (e.g. OPC-UA) or by developing own plug-in modules
I-MECH | Intelligent Motion Control Platform for Smart Mechatronic Systems
01-06-2017
-31-05-2020
Show more information
ICT performance characteristics
Interoperability (ICT)
General interoperability framework
Integration level interoperability
Comment: Service Oriented Architecture (SOA) concepts will be used to achieve a high degree of configurability, scalability and interoperability of the individual components, while maintaining the reliability, safety, certifiability and time-to-market benefits of off the shelf solutions.
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.
EFPF (European Factory Platform) | European Connected Factory Platform for Agile Manufacturing
01-01-2019
-31-12-2022
Show more information
ICT performance characteristics
Result items:
General interoperability framework
Integration level interoperability
Connectivity & network interoperability – communication protocols
Comment: Associated to EPFP Reference Architecture: Cybersecurity
Details: AMQP, MQTT and JSON are essential standards for application integration and core context to the building blocks of the EFPF Data Spine and platform. The uptake, interoperability and/or alignment of these standards will be carried out in the tasks dealing with message exchange in EFPF e.g. (T3.2 - Data Spine). Considering the cross-platform data model, EFPF platform sees UBL v2.2 a very possible candidate. In NIMBLE project the v2.1 version of the standard has been used; however, UBL always maintains backward compatibility when making minor standard revisions. In the scope of EFPF, the data model of NIMBLE will be upgraded to v2.2. On the other hand, UBL is a very active standard, which improves itself continually. Work has already begun on a future UBL 2.3 with a target publishing date of December 2019. The SDO will collect user requirements or usage scenarios to further develop/improve UBL data models. In the scope of EFPF standardisation activities, SRDC will submit additional user requirements and/or user usage scenarios to UBL community in order to contribute to UBL 2.3
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.
MUSIC | MUlti-layers control&cognitive System to drive metal and plastic production line for Injected Components
01-09-2012
-31-08-2016
Show more information
ICT performance characteristics
Interoperability (ICT)
SYMBIO-TIC | Symbiotic Human-Robot Collaborative Assembly: Technologies, Innovations and Competitiveness
01-04-2015
-31-03-2019
COMPOSITION | Ecosystem for Collaborative Manufacturing Processes _ Intra- and Interfactory Integration and Automation
01-09-2016
-31-08-2019
Show more information
ICT performance characteristics
Comment: Interoperability between installed equipment and infrastructure (machines, environment, people) is critical to capture and process data for the COMPOSITION IIMS components.
General interoperability framework
Integration level interoperability
Comment:
1) Security Information & Event Management API, 2) BPMN standard as part of the Integrated Digital Factory Model, 3) RabbitMQ implementation, 4) OGC sensor things compliant API through Integrated Digital Factory Metadata Model, 5) Part of the Integrated Digital Factory Model
Comment: Digital Factory Models’ instances will gather data in a common format. It is based on well-known standards such as BPMN, B2MML, gbXML and OGC. They are based XML and JSON syntax and provide a high level of simplicity, extensibility, interoperability and openness.
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
Comment: NFV-Low latency networks.NFV: Network functions virtualization)
Result items:
Semantic/information interoperability
Result items:
FAR-EDGE | Factory Automation Edge Computing Operating System Reference Implementation
01-10-2016
-31-10-2019
Show more information
ICT performance characteristics
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:
General interoperability framework
Comment: The FAR-EDGE architecture defines a protocol abstraction layer (the “connectivity middleware” box in the diagram provided here – this name is provisional) to decouple the field from its Edge Computing infrastructure: this is where OPC UA compatibility is going to be introduced.
Comment: The system blueprint is the FAR-EDGE RA. After having defined the requirements and the constraints for each block of the RA, a thorough analysis of the SotA has been done, which led to the identification of some existing software components meeting the specs. We then identified the gaps that the project will need to fill-in: not surprisingly, these where all the key enabling technologies, like the distributed ledger. However, hardly anything is going to be built totally from scratch in FAR-EDGE. The distributed ledger, for example, will be a customization of a generic, open source Blockchain platform (Hyperledger Fabric). Following the high-level functional decomposition defined in the FAR-EDGE RA, three Open APIs will be exposed by the Cloud layer of the FAR-EDGE Platform: Automation, Virtualization and Analytics. Automation will provide endpoints to monitor, control and manage automation workflows deployed on the Edge layer. Virtualization will create hooks for external simulation tools that need to read and manage factory models deployed on the Cloud layer (that are kept in-sync with the real world by the lower layers). Analytics will allow to manage distributed data analysis processes running on the Edge layer, and to collect aggregated results.
vf-OS | Virtual Factory Open Operating System
01-10-2016
-31-10-2019
Show more information
ICT performance characteristics
Interoperability (ICT)
General interoperability framework
Comment: The vf-OS publish-subscribe middleware will provide the data infrastructure and will be fully compatible with major industry standards (i.e. JBI, SCA, BPEL or WSDL). IO Toolkit to implement connectors to devices or business software and specific implementations for OPC UA and MQTT. Other standards as ANSI/ISA-95 will be followed.
Result items:
UPTIME | UNIFIED PREDICTIVE MAINTENANCE SYSTEM
01-09-2017
-28-02-2021
Show more information
ICT performance characteristics
General interoperability framework
Integration level interoperability
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
ICP4Life | An Integrated Collaborative Platform for Managing the Product-Service Engineering Lifecycle
01-01-2015
-31-12-2018
Show more information
ICT performance characteristics
Comment: Several communication technologies depending on the service:
Ethernet, OPC, OPC UA
General interoperability framework
Integration level interoperability
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:
OPC UA, NGSI
Result items:
Result items:
OPC UA Address Space for Testing Stations
Result items:
All the information is stored in a single context in the Orion Context Broker.
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
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
Comment: IEC-61499 established both a programming language and the rules for open communication protocols for real-time control over distributed applications. Interaction between non real-time and real-time IIoT could be guaranteed through the standard.
Comment: IEC-61499: Real-time (non strict) and pre-defined topology.
Daedalus: Auto-discovery and auto-binding over strict real-time
Result items:
Comment: Orchestration development framework. IEC 61499: Supervised orchestration of distributed devices.
Daedalus: SDK to design optimal distributed control solutions
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: DIGICOR Toolstore can host external/standalone applications
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:
NIMBLE | Collaboration Network for Industry, Manufacturing, Business and Logistics in Europe
01-10-2016
-31-03-2020
Show more information
ICT performance characteristics
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
Integration level interoperability
Comment: Web objects for IoT data ingestion
Result items:
THOMAS | Mobile dual arm robotic workers with embedded cognition for hybrid and dynamically reconfigurable manufacturing systems
01-10-2016
-31-03-2021
Integration with automation mecahinsms through pulg and produce capabilities based on OPC UA.