D2.4 The COMPOSITION architecture specification II

A public report, led by CNET, documenting the COMPOSITION architecture specification; this updates D2.3

In this deliverable, the first version of the software architecture for the COMPOSITION project is described.

COMPOSITION has two main goals: The first goal is to integrate data along the value chain inside a factory into one integrated information management system (IIMS) combining physical world, simulation, planning and forecasting data to enhance re-configurability, scalability and optimisation of resources and processes inside the factoryto optimise manufacturing and logistics processes.

The second goal is to create a (semi-)automatic ecosystem, which extends the local IIMS concept to a holistic and collaborative system incorporating and interlinking both the supply and the value Chains.This should be able to dynamically adapt to changing market requirements.The objectives are achieved by the use of number of IoT enabling technologies and services together with sophisticated big data analytics and deep learning as well as a trusted framework based on blockchain technology.

The main services realised by COMPOSITION are:

• Material and Component Tracking
• Product Quality Monitoring
• Manufacturing Forecasting
• Automated Procurement
• Ecosystem Collaboration Framework

The COMPOSITION architecture has been designed with consideration to compliance with RAMI 4.0

The purpose of this report is to provide a high-level overview of the design of the COMPOSITION system. It documents the main elements of the system and the relations between these elements. It also documents the stakeholder concerns - expressed in the project specification and user requirements – that drive the architecture design and the resulting design decisions that affect the system on an architectural level.

This deliverable will focus on the fundamental concepts and properties of the COMPOSITION system. Properties and design decisions for architectural elements are described when these affect the overall design or are needed for the understanding of the components’ impact on architecture design.

Detailed descriptions of the elements of the architecture, e.g. the Security Framework, Decision Support System or Digital Factory Model, are available as separate deliverables. The reader should refer to these for implementation details and specifications; references have been included in the appropriate sections. This report will include some diagrams and descriptions from detailed deliverables. Sections in D2.3 that have since been provided as separate deliverables have been abbreviated or left out of this document.

Several key functional requirements and architectural constraints are defined in the project specification, available at the start of the project. Gathering and validation of requirements and definition of pilot scenarios and use cases have been performed in parallel to the architecture definition process. The results of these activities have been reported in D2.1 “Industrial use cases for an Integrated Information Management System” and D2.2 “Initial requirements specification”. The D2.5 report “Lessons Learned and updated requirements report I” provided an update of the requirements which has served as input to the architecture design activities in WP2.