Projects overview
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
A4BLUE | Adaptive Automation in Assembly For BLUE collar workers satisfaction in Evolvable context
01-10-2016
-30-09-2019
Integration with automation mecahinsms through pulg and produce capabilities based on OPC UA.
TWIN-CONTROL | Twin-model based virtual manufacturing for machine tool-process simulation and control
10-01-2015
-30-09-2018
COMPOSITION | Ecosystem for Collaborative Manufacturing Processes _ Intra- and Interfactory Integration and Automation
01-09-2016
-31-08-2019
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
Daedalus | Distributed control and simulAtion platform to support an Ecosystem of DigitAL aUtomation developerS
01-10-2016
-30-09-2019
AUTOWARE | Wireless Autonomous, Reliable and Resilient ProductIon Operation ARchitecture for Cognitive Manufacturing
01-10-2016
-30-09-2019
DIGICOR | Decentralised Agile Coordination Across Supply Chains
01-10-2016
-30-09-2019
DISRUPT | Decentralised architectures for optimised operations via virtualised processes and manufacturing ecosystem collaboration
01-09-2016
-31-08-2019
INCLUSIVE | Smart and adaptive interfaces for INCLUSIVE work environment
01-10-2016
-30-09-2019
FAR-EDGE | Factory Automation Edge Computing Operating System Reference Implementation
01-10-2016
-30-10-2019
SAFIRE | Cloud-based Situational Analysis for Factories providing Real-time Reconfiguration Services
01-10-2016
-30-09-2019
MANUWORK | Balancing Human and Automation Levels for the Manufacturing Workplaces of the Future
01-10-2016
-31-03-2020
5G-Ensure | 5G Enablers for Network and System Security and Resilience
01-11-2015
-31-10-2017
UPTIME | UNIFIED PREDICTIVE MAINTENANCE SYSTEM
01-09-2017
-31-08-2020
The UPTIME platform is built upon the predictive maintenance concept, the technological pillars (i.e. Industry 4.0, IoT and Big Data, Proactive Computing) and the existing baseline tools (i.e. USG, preInO, PANDDA, SeaBAR, DRIFT) resulting in a unified information system for predictive maintenance. The extended UPTIME baseline tools (SENSE, DETECT, PREDICT, DECIDE, ANALYZE, FMECA, VISUALIZE) will address the various steps of the unified predictive maintenance approach and will incorporate interconnections with other industrial operations related to production planning, quality management and logistics management.
Open Platform Communication Unified Architecture (OPC-UA) is considered for UPTIME platform and for modular edge data collection and diagnosis of UPTIME_SENSE component.
To ensure secure access, the UPTIME Platform offers appropriate authorization and authentication mechanisms. These are based on the JWT technology and are implemented by using the Spring Security framework. Currently, JWT is used to ensure a secure log-in; as components are iteratively integrated. JWT will also be used to ensure secure communications between components.
The UPTIME conceptual architecture was designed according to the ISO/IEC/IEEE 42010 “System and software engineering – Architecture description” and mapped to RAMI 4.0 in order to ensure that it can be represent predictive maintenance in the frame of Industry 4.0.
The UPTIME vision converges and synthesizes predictive maintenance, proactive computing, the Gartner’s levels of industrial analytics maturity and the ISO 13374 as implemented in MIMOSA OSA-CBM in order to create a consistent basis for a generic predictive maintenance architecture in an IoT-based industrial environment. In this way, the Operational Technology and the Information Technology can also be converged in the context of Industry 4.0.
One of the main functionalities of UPTIME Platform is the batch data analytics implemented by UPTIME_ANALYZE component to analyse maintenance-related data from legacy and operational data and UPTIME_FMECA component that provides estimation of possible failure modes. The interoperability interfaces with UPTIME End-Users' (e.g. Whirlpool) legacy systems are defined, specified and developed according to latest practices and standards for APIs.
PreCoM | Predictive Cognitive Maintenance Decision Support System
01-11-2017
-31-10-2020
SCOTT | Secure COnnected Trustable Things
01-05-2017
-31-10-2020
QU4LITY | Digital Reality in Zero Defect Manufacturing
01-01-2019
-31-07-2022
Details: Feldbus/Device level (EtheCAT, PROFINET): Generic concept of fieldbuse
Details: AMQP
Details: Production system engineering; process quality and optimisation designer; distributed industrial-process measurement and control systems
Details: MQTT: an extremel lightweight publish/subscribe messaging transport protocol
Details: JSON
Details: Production system engineering; process quality and optimisation designer; distributed industrial-process measurement and control systems
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
Details: AAS, Interoperability
Details: General principles of the Digital Factory framework
Details: Information security management systems; Vocabulary
Details: RA/RM (basic standard) applied for QU4LITY-RA
Details: Use of open souce plattform for messaging and data streaming.
Details: Production system engineering; process quality and optimisation designer; distributed industrial-process measurement and control systems
Details: Cyber Security in Industrial Environments
Associated to QU4LITY Reference Architecture: Corporate Network/ Production OT Access Network: Deterministic Ethernet (TSN), OPC-UA, IDS/NGSI-LD
Details: OPC UA: an industrial M2M communication protocol for Interoperability; Information modelling
Details: AAS, Interoperability
Details: General principles of the Digital Factory framework
Details: Blockchain
Details: OS: Robot Operating System
Details: Use of open souce plattform for messaging and data streaming.
Details: Vocabulary, Interoperability, used to define the schema and enable a publisher to describe datasets and data services in a catalog using a standard model and vocabulary that facilitates the consumption and aggregation of metadata from multiple catalogs.
Details: Feldbus/Device level (EtheCAT, PROFINET): Generic concept of fieldbuse
Details: Production system engineering; process quality and optimisation designer; distributed industrial-process measurement and control systems
Details: Cyber Security in Industrial Environments
Associated to QU4LITY Reference Architecture: Corporate Network/ Production OT Access Network: Deterministic Ethernet (TSN), OPC-UA, IDS/NGSI-LD
Details: OPC UA: an industrial M2M communication protocol for Interoperability; Information modelling
Details: AAS, Interoperability
Details: General principles of the Digital Factory framework
Details: Data Models: proposes an overarching integrated conceptual model that describes interactions between the physical world, the user, and digital information, the context for AR-assisted learning and other parameters of the environment
Details: Blockchain
Details: Qualit modelling and support of quality workflow scenarious
Details: Information model (QIF) and data formed into XML instance files support the entire scope of model based definition manufacturing quality workflow
Details: Cloud computing, Fundamentalsn for Cloud services and devices: data flow, data categories and data use;
Details: JSON
Details: IoT, Semantic interoperability
Details: LCM: Enabling digital physical asset lifecycle management spanning plants, platforms and facilities; functional and interoperability requirements for Critical Infrastructure Management on a cross-sector basis
Details: Interoperable information model, vocabulary, and encoding mechanisms for representing statements about the usage of content and services.
Details: Interoperability & Common APIs: straightforward integration of a machine tool into higher level IT systems
Details: Applied to address performance analysisi and porcess optimisazion (i.e. allows to capture data that is required to do performance analysis of production facilities)
Details: OS: Robot Operating System
Details: MT Connect: used to access real-time data from shop floor manufacturing equipment such as machine tools
Details: Use of open souce plattform for messaging and data streaming.
Details: Specification that standardizes the connection between cameras and frame grabbers and defines a complete interface (provisions for data transfer, camera timing, serial communications, and real time signaling to the camera)
Details: API, Interoperability: global camera interface standard using the Gigabit Ethernet communication protocol to allow fast image transfer using low cost standard cables over very long lengths.
Details: REST API: application of standards and specification for HTTP/REST APIs
Details: Feldbus/Device level (EtheCAT, PROFINET): Generic concept of fieldbuse
Details: Production system engineering; process quality and optimisation designer; distributed industrial-process measurement and control systems
Details: Cyber Security in Industrial Environments
Associated to QU4LITY Reference Architecture: Corporate Network/ Production OT Access Network: Deterministic Ethernet (TSN), OPC-UA, IDS/NGSI-LD
Details: OPC UA: an industrial M2M communication protocol for Interoperability; Information modelling
Details: AAS, Interoperability
Details: General principles of the Digital Factory framework
Details: Network: Wireless local area networks
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
Details: Communication: Protocols, procedures, and managed objects for the transport of timing over local area networks
Details: Blockchain
Details: AMQP
Details: MQTT: an extremel lightweight publish/subscribe messaging transport protocol
Details: IoT, information exchange, peer-to-peer connectivity and seamless communication both between different IoT systems
Details: Applied to address performance analysisi and porcess optimisazion (i.e. allows to capture data that is required to do performance analysis of production facilities)
Details: OS: Robot Operating System
Details: Specification that standardizes the connection between cameras and frame grabbers and defines a complete interface (provisions for data transfer, camera timing, serial communications, and real time signaling to the camera)
Details: Feldbus/Device level (EtheCAT, PROFINET): Generic concept of fieldbuse
Details: Cyber Security in Industrial Environments
Details: AAS, Interoperability
Details: General principles of the Digital Factory framework
Details: Information security management systems; Vocabulary
Details: Vocabulary, Interoperability, used to define the schema and enable a publisher to describe datasets and data services in a catalog using a standard model and vocabulary that facilitates the consumption and aggregation of metadata from multiple catalogs.
Details: Quality,; guidance for onfiguration management - activity that applies technical and administrative direction over the life cycle of a product and service, its configuration identification and status, and related product and service configuration information.
Details: Cloud computing general overview and vocabulary
Details: Big data vocabulary
Details: IoT, Vocabulary
Details: Cloud Compuitng, Terminology
Details: AI, foundational, concepts and terminology
Details: Vocabulary, Information technology (IT) in general
There was a risk that other developments made within this pilot do not follow the reference architecture of IDS and thus are incompatible. This would cause that certain applications could not be deployed and run within in the proposed data space approach.
Details: AAS, Interoperability
ZDMP | Zero Defect Manufacturing Platform
01-01-2019
-30-06-2023
Details: Messaging, message Exchange
Details: IoT/Device Integration
Details: Messaging, message Exchange
Details: Messaging, message Exchange
Details: IoT/Device Integration
Details: Data Interoperability/ OPC/I4.0
Details: Information Management
Details: Messaging, message Exchange
Details: Information Security
Details: Information Security
Details: Information Security
Details: Information Security
Details: Maintenance
Details: Maintenance
Details: Industrial Automation Systems, Product Catalogues
Details: IoT/Device Integration
Details: Industrial Automation Systems, Product Catalogues
Details: IoT/Device Integration
Details: Maintenance
Details: Information Security
Details: Data Interoperability/ OPC/I4.0
Details: Data Interoperability/ OPC/I4.0
Details: Maintenance
Details: Industrial Automation Systems, Product Catalogues
Details: Industrial Automation Systems, Product Catalogues
Details: Information Security
Details: Messaging, message Exchange
Details: Data Interoperability/ OPC/I4.0
Details: Industrial Automation Systems, Product Catalogues
Details: IoT/Device Integration
Details: IoT/Device Integration
Details: IoT/Device Integration
Details: Information Security
Details: Data Interoperability/ OPC/I4.0
Details: Industrial Automation Systems, Product Catalogues
Details: Data Interoperability/ OPC/I4.0
Details: Industrial Automation Systems, Product Catalogues
Details: Industrial Automation Systems, Product Catalogues
Details: Industrial Automation Systems, Product Catalogues
Details: Data Interoperability/ OPC/I4.0
Details: Information Management
Details: Messaging, message Exchange
Details: Messaging, message Exchange
Details: Messaging, message Exchange
Details: Data Management
Details: Industrial Automation Systems, Product Catalogues
Details: IoT/Device Integration
Details: IoT/Device Integration
Details: Information Security
Details: Data Interoperability/ OPC/I4.0
Details: Industrial Automation Systems, Product Catalogues
Details: Data Interoperability/ OPC/I4.0
Details: Industrial Automation Systems, Product Catalogues
Details: Messaging, message Exchange
Details: Messaging, message Exchange
Details: Messaging, message Exchange
Details: IoT/Device Integration
Details: IoT/Device Integration
Details: IoT/Device Integration
Details: Information Security
Details: Data Interoperability/ OPC/I4.0
Details: Information Security
Details: Maintenance
Details: IoT/Device Integration
Details: Maintenance
Details: Industrial Automation Systems, Product Catalogues
Details: Cloud Computing
EFPF (European Factory Platform) | European Connected Factory Platform for Agile Manufacturing
01-01-2019
-31-12-2022
Z-Fact0r | Zero-defect manufacturing strategies towards on-line production management for European factories
01-10-2016
-31-03-2020
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:
- Load test
- Stress test
- Spike test
- Endurance test
- Scalability test
- Volume test
The IIS and the Integration plan of the Z-Fact0r solution were based on the same APIs and protocols as the data exchange in the system. There were no new APIs designed for the integration process and the integration protocol implemented was derived by the IIS and the Integration plan of the Z-Fact0r system.
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.
The data exchange format throughout the project's components was JSON. JSON lightweight, easy for humans to read and write it and provides all relevant information in a formatted way. It is also easy to change to include further fields when necessary or to be restructured for other components. XML was also used as data exchange format. XML also has the same characteristics with JSON in regards to easiness and accessibility. An example of one of the JSON formats used the project is given below to describe the prediction outputs:
Semantic interoperability is desired in the project. An ontology was created to describe all the entities participating in the project components, system, communication protocols as well as the entities given by the end users. The Context Aware algorithm was based on this ontology to create the operation rules for the system. The algorithm provided the essential information to other components about the implementation of the solution. For example, the Context Aware algorithm provided the Reverse Supply Chain with all the necessary information about the production line, the production stages, the return levels and then the RSC was able to create a set of rules to implemented by the end user.
The whole platform of the Z-Fact0r solution was able to work with other external applications, through a message brocker which is able to receive and send data to external systems. The interoperability level between the Z-Fact0r platform and external applications is essential for communication and integration purposes. Security and safety issues arise when different platforms cooperate. The Z-Fact0r platform implemented an AAA mechanism (Access, Autorisation and Authentication) to secure the safety of the platform during the connection with other external applications.
Access was given to the Z-Fact0r platform to only authorised users. The platform installation was done either on the shop floor premises or servers deployed by the technical providing partners creating a limited access environment. There was also the authorisation between the components and external appl, where the each component was authorised in an authorisation server with their unique Bearer Token in order to subscribe in the message brocker and publish or receive the available data. Further steps, such as user authentication, were not included in the project scope.
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.
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:
- GET call by the component to initiate communication
- The component is authenticated by the iLike machine
- The iLike machine appoints the respective topics for the components to publish or subscribe to them
- 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 of the Z-Fact0r solution was based on Wi - Fi protocol.
Z-Fact0r hybrid framework, obtained by applying a software and hardware integration strategy, is installed on the industrial end users shop floors. This architecture exploits features from Relational Databases and Triplestore while using the blackboard architectural pattern which ensures efficient and accurate communication of data transfer among software applications and devices.
There is little integration with legacy systems, such as CMMS or ERP for the Z-Fact0r solution.
vf-OS | Virtual Factory Open Operating System
01-10-2016
-30-09-2019
NIMBLE | Collaboration Network for Industry, Manufacturing, Business and Logistics in Europe
01-10-2016
-30-09-2019
THOMAS | Mobile dual arm robotic workers with embedded cognition for hybrid and dynamically reconfigurable manufacturing systems
01-10-2016
-30-09-2020
ZAero | Zero-defect manufacturing of composite parts in the aerospace industry
01-10-2016
-30-09-2019
PROGRAMS | PROGnostics based Reliability Analysis for Maintenance Scheduling
01-10-2017
-30-09-2020
PROGRAMS interoperability at platform level is granted by the choice of a widely shared communication approach: JSON files over HTTP protocol. Common modules architectures and data formats for file exchange reinforce the PROGRAMS interoperable approach.
A Common Authentication System based on user credentials is shared by all PROGRAMS modules.
NIST guidelines are being followed to manage Users access.
PROGRAMS project aims at integrating its platform with a number of legacy system, like ERPs or Life Data Analysis tools. Since it is not possible to cover all commercial tools interfaces, the consortium decided instead to provide open interfaces (based on JSON files over HTTP protocol exchange) for all its modules.
PROPHESY | Platform for rapid deployment of self-configuring and optimized predictive maintenance services
01-10-2017
-30-09-2020
MANTIS | Cyber Physical System based Proactive Collaborative Maintenance
01-05-2015
-31-07-2018
I-MECH | Intelligent Motion Control Platform for Smart Mechatronic Systems
01-06-2017
-31-05-2019