Projects overview

Sort by


Toggle all information

SCOTT | Secure COnnected Trustable Things

01-05-2017

-

31-10-2020

Show more information
ICT performance characteristics
Cybersecurity
Risks addressed by security
Specific security standard(s) addressed and impact on implementation
Security mechanisms and technologies
Distributed ledger technology
Risk or security assessment
Trustworthy Systems in Platform Lifetime
A Security Architecture for Digital Manufacturing Platforms
Used guidelines and specific frameworks for security and/or privacy by design
Interoperability (ICT)
General interoperability framework
Integration level interoperability
APIs and Integration Protocols
Connectivity & network interoperability – communication protocols
Data/object model interoperability - Data exchange formats - APIs
Semantic/information interoperability
Platform level interoperability
AAA - Access, Authorisation and Authentication
Motivating Scenario / Use-Case
User Acccess and Rights Management
Application level interoperability
Modular Design and Deployment Approaches
Open APIs and Communication Protocols
Wireless communication protocols
Web-services / Composability
Integration with legacy systems
Privacy
Real-time communication capability
Resilience
Scalability
 Semantic/information interoperability Taxon description For example through APIs, WSDL, RESTFUL, SOAP, OPC UA, WEBSOCKET, ISA 95, ISA 88, IEC 61499  

INCLUSIVE | Smart and adaptive interfaces for INCLUSIVE work environment

01-10-2016

-

30-09-2019

Show more information
ICT performance characteristics
Interoperability (ICT)
General interoperability framework
Integration level interoperability
Semantic/information interoperability
Platform level interoperability
AAA - Access, Authorisation and Authentication
User Acccess and Rights Management
Application level interoperability
Open APIs and Communication Protocols
Privacy
 Semantic/information interoperability Taxon description For example through APIs, WSDL, RESTFUL, SOAP, OPC UA, WEBSOCKET, ISA 95, ISA 88, IEC 61499  

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

01-10-2016

-

31-03-2020

Show more information
ICT performance characteristics
Cybersecurity
Comment: End-to-end security: Data integrity, confidentiality, identity and key management, authentication, fine-grained authorization and access control. Trust and reputation management. Advanced behavioural security (including game theory) Spring Cloud Security: Standardized security mechanisms are implemented using Spring Cloud Security. It provides out-of-the-box integration of security modules to Spring Cloud applications. Authentication and authorization between microservices are realized by using Spring Cloud Security, which supports OAuth2 and OpenID Connect and communicates with the authentication server (i.e. Cloud Foundry UAA).
Result items:
Design and Implementation of Security and Privacy for Core Business Services
Design and Implementation of Security and Privacy for Core Business Services
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
Integration level interoperability
Connectivity & network interoperability – communication protocols
Comment: Web objects for IoT data ingestion
Result items:
Design of an Open API for the NIMBLE Platform
Design of an Open API for the NIMBLE Platform
Data/object model interoperability - Data exchange formats - APIs
Comment: Open published API for 3rd party extensions. Intelligent support for business negotiation. Mainly driven by UBL documents connected to defined business processes; NIMBLE OpenAPI
Semantic/information interoperability
Comment: B2B collaboration: Semantic annotation of products and services. Business process design and execution. Open ontologies. UBL for business processes, eClass for products, domain specific ontologies aligned via light-weight upper ontology
Platform level interoperability
AAA - Access, Authorisation and Authentication
Comment: KeyCloak - based on Standards (OpenID Connect, OAuth 2.0 and SAML 2.0)
User Acccess and Rights Management
Comment: KeyCloak based Identity and Access Management of NIMBLE Platform
Application level interoperability
Modular Design and Deployment Approaches
Comment: (1) Docker-based (2) Bluemix/Kubernetes-based cloud solution
Open APIs and Communication Protocols
Comment: NIMBLE Task 2.3 OpenAPI for the NIMBLE Platform
Industrial Reference ICT Architectures
Comment: IIRA is the main reference. IIRA is closest in terms of conceptual design for NIMBLE. RAMI is not so applicable to us because we are closer to Internet B2C or B2B platforms. Industrial Data Space is on our radar, but was not sufficiently elaborated at the time of writing the proposal. See https://cloud.effra.eu/index.php/s/NiyTZgM3kw6VCxw The NIMBLE platform is designed to ingest data stemming from edge devices into the platform. Once data has reached the platform, data are stored for future uses such as offline analytics and auditing. In addition, processing of the data as it flows into the platform can be performed in real-time. Offline analytics complements the real-time view by enabling companies to gain insights from their data leading to more efficient processes. We follow the microservice approach for the NIMBLE architecture. Each microservice offers a specific and narrowly defined functionality that is deployed as an independent service [2]. It puts emphasis on real-time application monitoring, including architectural elements and business relevant metrics, e.g. number of orders per minute [2]. In addition, this approach provides decentralized data management and decentralized data storage decisions based on a polyglot persistence method. Microservices can still be combined with monolithic enterprise applications (monolith’s APIs) built as single units, fostering the federation and collaboration of various independent services in the Cloud. Figure 1 depicts the top-level architecture, which is inspired by the microservice infrastructure presented in [3]. Figure 2 then shows the core business services of the platform in more detail. The Gateway Proxy is the public entry point to the microservice application. All user requests are received via the Gateway Proxy and routed to the appropriate service. The Service Logging aggregates log outputs of each individual microservice and makes them available via a Web interface. The Service Monitoring collects data, which are necessary to monitor failures of services; this is implemented using the Circuit Breaker pattern [4]. The Service Monitoring can be used to monitor remote calls, or in any situation where parts of a system need to be protected from failures in other parts. After the number of erroneous executions exceeds a defined threshold, all future calls are immediately returned with an error without the actual function being executed. The Service Discovery enables registration of microservices, as well as mapping between service identifier and the endpoints of instances (e.g. URL or IP address). The role of the Service Configuration is to provide configuration settings for each service. The service communication is enabled either via REST (i.e. HTTP) or by using the Messaging Service (based on Apache Kafka), which provides asynchronous and scalable communication. Finally, the User Account and Authentication (UAA) & Identity Management administrates user identities on the platform. It combines the three standard protocols: OAuth2 for delegated authorization [5], OpenID Connect for session and authentication information [6], and the System for Cross-domain Identity Management (SCIM) for user and group management [7].
Reference Architectural Model Industrie 4.0 (RAMI 4.0)
RAMI 4.0 Hierarchy Axis
Product
Privacy
Result items:
Design and Implementation of Security and Privacy for Core Business Services
Design and Implementation of Security and Privacy for Core Business Services
Resilience
Comment: Resilience is partly addressed through the federation aspects: attackers need to “hack” more than one platform, each with a different security setup, chosen from NIMBLE modules.
Comments Cloud Foundry UAA).
 Semantic/information interoperability Taxon description For example through APIs, WSDL, RESTFUL, SOAP, OPC UA, WEBSOCKET, ISA 95, ISA 88, IEC 61499  
 Cybersecurity Comments Cloud Foundry UAA).
 Programming Frameworks – Software Development Kits (SDKs) Comments Cloud Foundry UAA).

THOMAS | Mobile dual arm robotic workers with embedded cognition for hybrid and dynamically reconfigurable manufacturing systems

01-10-2016

-

31-03-2021

Show more information
ICT performance characteristics
Interoperability (ICT)
General interoperability framework
Integration level interoperability
Connectivity & network interoperability – communication protocols
Data/object model interoperability - Data exchange formats - APIs
Semantic/information interoperability
Platform level interoperability
User Acccess and Rights Management
Application level interoperability
Modular Design and Deployment Approaches
Open APIs and Communication Protocols
Wireless communication protocols
Web-services / Composability
Industrial Reference ICT Architectures
Reference Architectural Model Industrie 4.0 (RAMI 4.0)
RAMI 4.0 Hierarchy Axis
Field Device
Work station
 Semantic/information interoperability Taxon description For example through APIs, WSDL, RESTFUL, SOAP, OPC UA, WEBSOCKET, ISA 95, ISA 88, IEC 61499  

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

01-10-2016

-

30-09-2019

Show more information
ICT performance characteristics
Cybersecurity
Comment: Security, privacy & trust (SPT) based on situational awareness, based on: - Policy Enforcing Scheme - Distributed Reference Monitor (DRM) Functionalities: Encryption, Authorisation, Authentication, Monitoring, Auditing
Result items:
SAFIRE Electrolux pilot: Cloud-driven product optimization
SAFIRE Electrolux pilot: Cloud-driven product optimization
SAFIRE OAS pilot: Optimisation of production processes and preventive maintenance activities
SAFIRE OAS pilot: Optimisation of production processes and preventive maintenance activities
SAFIRE ONA pilot: Adaptive Machining
SAFIRE ONA pilot: Adaptive Machining
Interoperability (ICT)
General interoperability framework
Integration level interoperability
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
APIs and Integration Protocols
Comment: Data Ingestion module will contain a plug-in architecture to allow integration of various data-source (e.g. OPC-UA)
Platform level interoperability
AAA - Access, Authorisation and Authentication
Comment: Next Generation Access Control (NGAC) based authorisation and authentication
User Acccess and Rights Management
Comment: NGAC based access control management IN SAFIRE solution
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
Modular Design and Deployment Approaches
Comment: Docker based application packaging and deployment will beused in SAFIRE
Open APIs and Communication Protocols
Comment: Publish / Subscribe message system Apache Kafka will be used for communication in SAFIRE
Industrial Reference ICT Architectures
Reference Architectural Model Industrie 4.0 (RAMI 4.0)
RAMI 4.0 Hierarchy Axis
Field Device
Comment: Cloud based secure infrastructure for reconfiguration and optimisation. The envisaged SAFIRE infrastructure will be an add-on for an existing production system or next generation smart factory operating system, allowing to transform such production systems into advanced production systems capable of real-time reconfiguration and optimisation.
Result items:
SAFIRE OAS pilot: Optimisation of production processes and preventive maintenance activities
SAFIRE OAS pilot: Optimisation of production processes and preventive maintenance activities
Work station
Comment: Interconnected Systems of Production Systems (SoPS)
Result items:
SAFIRE OAS pilot: Optimisation of production processes and preventive maintenance activities
SAFIRE OAS pilot: Optimisation of production processes and preventive maintenance activities
SAFIRE ONA pilot: Adaptive Machining
SAFIRE ONA pilot: Adaptive Machining
Connected Enterprises - Factories
Comment: Interconnected Systems of Production Systems (SoPS)
Result items:
SAFIRE OAS pilot: Optimisation of production processes and preventive maintenance activities
SAFIRE OAS pilot: Optimisation of production processes and preventive maintenance activities
SAFIRE ONA pilot: Adaptive Machining
SAFIRE ONA pilot: Adaptive Machining
Privacy
Result items:
SAFIRE Electrolux pilot: Cloud-driven product optimization
SAFIRE Electrolux pilot: Cloud-driven product optimization
SAFIRE OAS pilot: Optimisation of production processes and preventive maintenance activities
SAFIRE OAS pilot: Optimisation of production processes and preventive maintenance activities
SAFIRE ONA pilot: Adaptive Machining
SAFIRE ONA pilot: Adaptive Machining
Resilience
Result items:
SAFIRE Electrolux pilot: Cloud-driven product optimization
SAFIRE Electrolux pilot: Cloud-driven product optimization
SAFIRE OAS pilot: Optimisation of production processes and preventive maintenance activities
SAFIRE OAS pilot: Optimisation of production processes and preventive maintenance activities
SAFIRE ONA pilot: Adaptive Machining
SAFIRE ONA pilot: Adaptive Machining
Scalability
Comment: Each SAFIRE service will be developed as own docker container, to allow easy distribution and scalability of whole SAFIRE solution in the cloud
Comments 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.
 Integration level interoperability Comments 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.
Powered by Chris Decubber BV