Community Research and Development Information Service - CORDIS


Manutelligence Report Summary

Project ID: 636951
Funded under: H2020-EU.

Periodic Reporting for period 1 - Manutelligence (Product Service Design and Manufacturing Intelligence Engineering Platform)

Reporting period: 2015-02-01 to 2016-07-31

Summary of the context and overall objectives of the project

The Product-Service is more and more a source a new business, providing to the end users the experience they need instead of a pure product, efficiently addressing customer needs. Then a new approach to design and manufacturing a Product-Service is needed.
The main scope of the Manutelligence project is to develop a software platform to support this emerging trend, allowing enterprises to develop sustainable innovative product-services. This platform will enable designers and manufacturers to have a holistic view on product-service lifecycle.
The Manutelligence platform will be composed by existing and new software components, which integration will provide a new tool for the industry digitalization support, leveraging on product virtualization, IoT and sustanaibility solutions.
The industrial use cases selected for the project are the current targets to develop and validate the platform.
As in the case of Lindbäcks, one of the industrial partner of the consortium, the use-case concept bases on the collection and analysis of real life data. The information will be used to improve the quality of the houses, to extend the life time by faster reaction of technical problems in the house and to reduce the energy (resources) consumption by influencing the end users (buyers or lodgers).

Work performed from the beginning of the project to the end of the period covered by the report and main results achieved so far

The project activities done in the first half of the project timeframe are the following

WP1 - Engineering and business requirements for holistic P-S development processes in the targeted application sectors
Task 1.1 - Elicitation (Lead: POLIMI; Partners: DAS, FERRARI, MEYER, FAB, SUPSI, HLX, VTT, LIND, DAPP, BAL) - M1-M6
This task was led by POLIMI and it resulted into a deliverable: D1.1 Elicitation of Engineering and Business Requirements at M6. All the WP partners were involved in this task. The elicitation methodology was developed by POLIMI and discussed in the specific WP meeting in March 2015 between the research partners (VTT, SUPSI). The 4 end user cases (FERRARI, MEYER, FCIM, and LIND) acted as the main sources for requirements.
Task 1.2 - Structuration (Lead: VTT; Partners: POLIMI, SUPSI) - M4-M9
This task was led by VTT and it resulted into a deliverable D1.4 Structuration and organization of requirements at M9. The structuration included defining requirement categories and aggregating the about 200 requirements into a smaller number (20) in this category. The structuration methodology was developed by task leader VTT; as well as the first organization and aggregation approach.
Task 1.3 - Analysis and refinement (Lead: SUPSI; Partners: POLIMI, HLX, VTT) - M7-M12
This task was led by SUPSI and it resulted into a deliverable D1.2 Refinement and analysis of requirements at M10. The analysis included analysis of requirement trade-offs and prioritization. SUPSI developed the trade-off analysis and prioritization methodology.
Task 1.4 - Requirements Validation (Lead: VTT; Partners: DAS, FERRARI, MEYER, FAB, POLIMI, SUPSI, HLX, LIND, DAPP, BAL) - M7-M12
This task was led by VTT and it resulted into a deliverable D1.3 Requirement validation. The validation methodology, including both individual walk-through by VTT researchers and validation workshop with end users and other partners was developed by VTT. VTT facilitated the validation workshop and all the end users and supporting partners participated in it. VTT consolidated the results from the workshop and proposed some changes and additions to the list of aggregated requirements.
WP2 - Simulation and optimisation of PLM and SLM interaction
Task 2.1 - Combined Lifecycle Model for Collaborative Product-Service Engineering (Lead: BIBA; Partners: POLIMI, SUPSI) - M1-M6
This task was led by BIBA with key contributions by POLIMI. SUPSI and BAL (as well as VTT and other partners) contributed to the preliminary glossary provided as an annex.
Task 2.2 - Concept for a Combined PLM/SLM Product-Service Lifecycle Management (Lead: POLIMI; Partners: SUPSI, BIBA, HLX) - M7-M30
This task is led by POLIMI with key contributions from BIBA, SUPSI and HLX. So far, the work concerns: exploration of the practical adequacy of the LML and guiding concepts. POLIMI applied the approach for the FERRARI case while BIBA explored it for the FCIM case (3D printers): exploration of the required data, information and knowledge types based on the description of use cases from WP6: modelling of some parts of the use cases: starting with the LIND and FCIM cases.
Task 2.3 - Simulation and Optimization of Combined Product-Service Lifecycle Management (Lead: POLIMI; Partners: BIBA, HLX, BAL) – M13-M30
This task concerns the extension of BAL LCPA tool (Lifecycle Cost Assessment). The tool should be able to compare traditional, product-centric scenarios with Product-Service scenarios (e.g. extended by Internet of Things devices and service approaches). So far, the extension is in its concept phase, i.e. an assessment scenario is selected and described.
Task 2.4 - Refinement of results of the optimisation and analysis of the P-S engineering processes (Lead: BIBA; Partners: POLIMI, SUPSI, HLX, LIND) - M24-M33
This task is not yet started;
WP3 - Collaborative and cross-disciplinary procedures and tools to design and develop Smart Innovative Product-Service
Task 3.1 - Semantic facilitator for bridging Product and Service lifecycle phases. (Lead: BIBA; Partners: HLX, POLIMI, SUPSI) - M7-M24
This task is led by BIBA with contributions of HLX, POLIMI and SUPSI.
The work so far focused on the connection of the USG to IoT HLX platform (Universal Sensor Gateway serves as a modular data acquisition and integration device to the Product Lifecycle Management (PLM) ecosystem of a product).More in details, the connection between USG and HLX platform for LINDBÄCKS has been implemented. Data related to room temperature, humidity, water detection in the sink and dew point are measured at LINDBÄCKS houses and are sent to HLX platform.In addition, also the connection between current sensors, which are used to evaluate 3D printing energy consumption and HLX platform for Fundacio CIM is on working.Regarding Ferrari, data coming from different gateways (Ferrari telemetry, Vector telemetry, Slam Stick X data logger to measure mechanicals vibrations are already on the HLX platform.The implementation of the connection of HLX platform for condition-based maintenance and 3D experience is ongoing for the Meyer case.
Task 3.2 - Tools and procedures for embedding and retrieving P-S lifecycle knowledge. (Lead: HLX; Partners: DAPP, BAL) - M7-M30
This task is led by HLX with contributions of DAPP and BAL.

The work so far focused on the adaptation, development and verification of data models to retrieve data from the field for the different use cases: data model for LINDBÄCKS, Fundacio CIM, Ferrari, Meyer has been defined,
These adaptation and developments will be verified and tested during the project and will be used as experience for re-defining a generic data model and eventually a revised O-LM specification.

Task 3.3 - Methodologies and tools to involve customers in the P-S multi-disciplinary feedback (Lead: HLX; Partners: POLIMI, BIBA, VTT) - M13-M30
This task is led by Holonix with contributions of BIBA, POLIMI and VTT.
The work of this task is to enable flow of information from middle of life phase to beginning of life phase, meaning, to enable designers and manufacturers to benefit from information gathered during usage and exploitation (user behaviour, servicing, durability, etc.). For this purpose, connection of the USG to HLX Platform has been developed.
Task 3.4 - Engineering codified knowledge collaborative management (Lead: BIBA; Partners: HLX, POLIMI) - M7-M24
Main focus of BIBA’s activities in the reporting period for T3.4 was dedicated to the envisaged representation of codified engineering knowledge for an automated linkage of identified closed-loop PLM dependencies with the development of new products. In this context the work has been grounded on KBE related pre-works, namely the proposed modelling language KbeML (formerly RDF), which has been specified as a SysML extension for KBE purposes. The current approach foresees the implementation of KbeML in conjunction with SysML elements to allow next to the representation of design knowledge the modelling and formalization of life-cycle dependencies such as energy consumption or wastage reduction. Further, BIBA is currently analysing the applicability of the commercial modelling environment “Enterprise Architect” (EA) to become an appropriate modelling platform for the enhanced KbeML models. The core idea is to provide users a predefined modelling environment with a menu-library, offering UI controls etc. Finally, BIBA participated in WP3 calls and consortium meetings ensuring an alignment among the WP3 tasks (and other WPs).
Task 3.5 - Secure data sharing across the P-S lifecycle (Lead HLX) – M22-M30
This task is led by HLX.
The main outcomes of this task will be:
• Analysis of existing standards for security both in Thing2Thing; Thing2System; System2System
• Implementation of a pilot within the i-LiKe platform of the best solution (as it is now, HTTPS)
WP4 - Manufacturing Intelligence through the development of a modular and interoperable Product-Service Engineering environment
Task 4.1 – Collaborative Design Tools (Lead: DAS; Partners: POLIMI, HLX) - M7-M24
This task is still running and is led by DAS with the key contribution of POLIMI and HLX. According to the DoA the first activity performed was the deployment of the design tools such as CATIA and SIMULIA on the Manutelligence platform held in the POLIMI premises, in addition for developing the FCIM scenarios also the deployment of the authoring tool SolidWorks has been necessary. Once all the design tools were in place, all the relevant use case 3D models (FERRARI, MEYER) have been imported in the Manutelligence platform. The availability of the models on the platform has been the starting point for matching the field data with the virtual models. Preliminary studies for implementing such integration have been carried out by DAS and HLX. A prototype of a new service to exchange data between ENOVIA 3DExperience (provided by DAS) and LCC /LCA tools (provided by SUPSI and BAL) is being tested in order to integrate the environmental impact calculation as well as the life cycle cost calculation

Task 4.2 – Process design and Manufacturing Execution Design Tools (Lead: DAS; Partners: HLX) – M7-M24
This task is still running and is led by DAS with the contribution of HLX and the activities performed are mainly related to the development and integration within the platform of the i-Like module for managing the manufacturing data coming from field sensors. Many analyses have been carried out by DAS and HLX in order to understand which can be the best solution for connecting the field data to the virtual models, in addition also the integration of Delmia has been evaluated and will be done when the use case scenario complexity will be higher.

Task 4.3 – P-S Internet of things Middleware, data and Knowledge Management (Lead: HLX; Partners: DAS) - M7-M24
This task is still running and is led by HLX with the contributions of DAS. The activities performed in this task are mainly related to the development of the middleware. The main objective of this layer is the connection of the Internet of Things to the Manutelligence platform. Data acquisition for different use cases has already been performed. All the communication for the “physical items”, related to the Internet of Things, will be implemented using open standards.

Task 4.4 – P-S engineering and manufacturing ubiquitous search Tools (Lead: DAS; Partners: POLIMI, HLX) - M7-M24
This task is still running and is led by DAS and involves POLIMI and HLX. The main activity is to provide ubiquitous search capabilities of Product-Service related information from engineering to manufacturing and use. For these purposes, the Exalead Cloud View has been deployed in the Manutelligence platform. In detail, the powerful search engine of Exalead enable the manufacturing intelligence layer mainly for elaborating the big amount of data coming from the product.

Task 4.5 – P-S life-cycle data 3D visualisation and context based interaction Tools (Lead: DAS; Partners: POLIMI, HLX, LIND) - M7-M24
This task is still running and is led by DAS with the contribution of POLIMI, HLX and LIND. In particular, according to the DoA, the 3DEXPERIENCE suite has been deployed in the Manutelligence platform and it represents the backbone for accessing, managing and storing the large amount of information coming from the four use cases. In addition 3DEXPERIENCE provides within its suite a set of visualizing tools such as 3D viewer as well as interactive 3D dashboards that supported by the manufacturing intelligence layer can provide aggregate data and a clearly understandable view of the 3D models. The level of aggregation of the data and how to organize the dashboard should be still analysed in the next months.

Task 4.6 – Manufacturing Context Driven Intelligence Layer (Lead: HLX; Partners: POLIMI, HLX, LIND) – M7-M30
This task is still running and is led by HLX with the collaboration of POLIMI. The main activities are related to the development of a flexible environment to present data in a coherent way in order to unify the information and knowledge coming from different tools of the project. Virtual Obeya will be used. This task therefore takes also care of the further developments this tool needs for the Manutelligence project as well as the integration of the all the various tools used or developed within the project (WP2 and WP3). All the activities will be reported in the related deliverable D4.6. In addition a new service is provided to exchange data between ENOVIA 3DExperience (provided by DAS) and LCC /LCA tools (provided by SUPSI and BAL).

Task 4.7 – Testing and validation of the Product Service design and manufacturing collaborative engineering environment (Lead: DAS; Partners: POLIMI, HLX) - M19-M33
The activities of task 4.7 are not yet started.
WP5 - Decision Support System for managing LCA & LCC issues in PSS design and development

Task 5.1 - Reference LCC & LCA Model including Initial LCI (Lead: SUPSI; Partners: POLIMI, DAPP, BAL, Meyer and Fab) - M1-M9;
First, SUPSI carried out a brief overview of literature about LCA and LCC. This piece of work mainly aimed at understanding what already exists for the PSS context that could be taken as a starting point and, hence, what remains to be developed within the project to meet the target objective for LCA and LCC.
Next, the requirements LCA and LCC tools have to satisfy in order to be seamlessly integrated into the Manutelligence platform have been identified based on a collaborative analysis by SUPSI, DAPP and BAL.
Since there are several available tools, a first selection has been done and three tools have been identified as possible candidates to be extended, adapted and integrated into the Manutelligence platform. The candidate tools have been used in a comparative way against the identified requirements. In particular, BAL worked with the tool BAL.LCPA, SUPSI with the tool SAM and DAPP with GaBi.
Finally, SUPSI started to work on the Life Cycle Analysis (LCA) for PSS considering what information are needed as an input to perform the life cycle inventory (LCI) phase of the LCA analysis (and that are requested also for the LCC analysis).
Task 5.2 – Specification and implementation of tools for Product-Service LCC & LCA analysis (Lead: DAPP; Partners: SUPSI, BIBA, BAL) - M7-M24
This task aims at developing the LCA and LCC tools defined according to the work carried out in T5.1. First, DAPP reviewed and updated the list of requirements introduced in T5.1 checking, in particular, the pilots’ point of view. In parallel, several technical discussions took place between SUPSI, BAL and DAPP in order to define the specifications of the LCA and LCC tools. SUPSI is taking care in particular of the development of the LCA tool, whilst BAL is focused on the LCC tool. A first stand-alone version of the tools is expected to be ready by the end of June 2016. DAS is also contributing to this task by providing inputs to take into consideration the Manutelligence platform requirements since the initial tools definition.
Task 5.3– Evaluation of Product-Service LCA & LCC Models and Tools (Lead: SUPSI; Partners: POLIMI, DAPP, BAL, Meyer, Fab) - M10-M33
In this task the tools developed in previous tasks will be tested in the pilots. First, a template for the collection of data requested by the LCI phase of LCA and for the carrying out of LCC has been developed jointly by SUPSI, BAL and DAPP. It has been decided to use a BOM (Bill of Material)-oriented approach. The selection has been supported by Fab who tested the template and provided valuable feedback by using it for the collection of data for a simple product (a 3D-printed Manutelligence logo, see Figure 1).
A more complex product, a lamp (see Figure 1), is being designed by Fab and will be used to test the first version of the LCA and LCC tools. In the next step, SUPSI and BAL are working on the
data collection for the implementation of LCA and LCC tools in the Lindbäcks case.
Task 5.4 –LCA & LCC based Design Decision Support Tool (Lead: BAL; Partners: POLIMI, BIBA, DAPP) - M10-M33
The main focus for this task is the integration of the LCA and LCC tools into the Manutelligence platform to support the decision making process in the development product-service-systems (PSS). The technical discussions mentioned in the description of T5.2 also cover integration issues. In particular, in task 5.4 partners developed an approach for the exchange of the required LCA/LCC input data from the Manutelligence platform to the assessment tools and how the LCA and LCC results will be forwarded to- and visualised on the Manutelligence platform. During the development process, special emphasis was put on considering the limits of the technical feasibility as well as to fulfil the integration requirements of the LCA tool defined by SUPSI. Moreover, DAS provides information about to what extent the platform can fulfil LCA and LCC tool requirements and which DAS tools could be used for the development of the design decision support tool in the project.
Task 5.5 – Crowdsourced design and improvement of FAB products (Lead: POLIMI; Partners: SUPSI, Fab) - M10-M33
POLIMI is evaluating the possibility of using the 3D Dashboard by analysing if and how this tool can support co-design activities for the FabLab case. Furthermore, POLIMI is investigating how co-design activities can affect sustainability issues. At the same time, FCIM is providing information related to the co-design processes that take place in the FabLab environment and the related requirements concerning sustainability issues.
Task 5.6 – Definition and implementation of algorithms and tools for social data use and exploitation (Lead: BIBA) - M7-M33
BIBA has prepared a plan of activities to be carried out in order to develop a demonstrator. In particular, it has defined the scope and the boarders of the analysis identifying how existing tools can be used and adapted to the PSS context.
WP6 - Use-Case
Task 6.1 - Use-case Automotive (Lead: FERRARI; Partners: DAS, POLIMI, SUPSI, HLX, DAPP, BAL) - M1-M36
The Task 6.1 sets-up an instance of the Manutelligence tools which will be used by FERRARI to run the trials through three scenarios. The first scenario is related to linking the product requirements to the top level product architectural structure, the second one is focused on connecting the product requirements to the engineering analysis and the third one aims to communicate the virtual and physical tests results to the designers. The Automotive Use Case will be conducted in FERRARI facilities.

Task 6.2 - Use-case Ship (Lead: MEYER; Partners: DAS, VTT, DAPP, BAL) - M1-M36
The Task 6.2 involves the ship-related Use-cases, namely “Intelligent manufacturing and maintenance for Cruise Vessels of the Future”. The aim is to contribute to user engagement through engineering model based product-services. The potential for new services is identified through the analysis of product data that could be beneficial and interesting for the ship user and owner during the operational phase. Also the opposite direction of information flow is developed: feedback from manufacturing and customers to ship design and engineering. The basis for the new services is the 3D engineering models and databases. In the Task Ship use case scenarios are developed including the new service identification.
Task 6.3 - Use-case Smart house (Lead: LIND; Partners: BIBA, DAPP, BAL) - M1-M36
The Task 6.3 will develop the use case “Smart house”. The pilot consists of three scenarios. The first scenario is related to the product specification and configuration and focuses on the end user, the second one is focusing on production and assembly of smart houses and the third one aims to after sales services and maintenance. The main stakeholder groups involved are end users, sales people, and production, service and facility managers.
Task 6.4 - Use-case FabLab (Lead: FAB; Partners: DAS, POLIMI, HLX, DAPP, BAL) - M1-M36
The Task 6.4 will develop the use case of FabLab, facilities equipped with digital fabrication machinery (the most representative case is a 3D printer), where people go and convert their ideas into physical object. The pilot analyses five scenarios: i)supporting the generation of CAD design from user’s requirements, ii) Knowledge sharing within the FabLab/ADF network, iii) Developing the production cycle, iv) Cloud-based feedback and multidirectional information flow for the design of smart objects, v) Sustainability assessment. All the scenarios are identified as possible and desirable, yet not all of them are being actually developed and implemented.
Task 6.5 Assessment, start at M18. The objective of the Task is the evaluation and assessment of the Use Case Trials.

WP7 - Business plan and exploitation model
Task 7.1 - Business Evaluation of the distinctive features of the P-S engineering environment (Lead: DAPP; Partners: POLIMI, HLX, DAPP) - M1-M9
The scope of this task has been to analyse the business potential of the Smart Innovative Product-Service Engineering Environment and how the aggregation of product and service lifecycle engineering tools is able to generate added value. In this context, all the partners provided their inputs about their specific exploitable results. After this first step, detailed market analyses about the four sectors related to the use cases of the Manutelligence project have been performed by DAPP, illustrating market size, growth, trends and the level of Product-Service Life Cycle Management (P-SLM) implementation for each of them.
Then, according to the three defined levels of exploitation (Platform developers, Consulting business, Specific use cases) identified in T7.3, the business potential has been analysed and on the basis of the performed market analysis, a SWOT analysis for level of exploitation as well as for each pilot case has been performed by DAPP with the support of POLIMI and DAS.
The outcome of the task has been that business based on Product-Services is growing within the manufacturing sector, where companies are increasingly improving the service component of their offering to gain competitive advantage; thus, the integration of product and service lifecycle engineering tools is definitely able to generate significant added value. D7.1 has been delivered at M12 under the responsibility of DAPP.

Task 7.2 - Sustainable Business model Innovation (Lead: POLIMI; Partners: HLX, DAPP) – M9-M18
This task has been led by POLIMI and the aim was to define sustainable business models. By taking into account the inputs coming from T7.1 (business potential) and T7.3, potential business models have been investigated. The activities, in addition to POLIMI, involved in particular DAPP, DAS and HLX. An analysis of sustainable business model has been performed starting from the investigation of the state of the art. Then the focus has been moved on the analysis of the value proposition and the business model canvas has been used as tool for defining the business model. D7.2 has been delivered by POLIMI at M18.

Task 7.3 - Exploitation plan definition for the P-S Manufacturing Intelligence Engineering Platform (Lead: DAPP; Partners: DAS, FERRARI, MEYER, Fab, POLIMI, SUPSI, BIBA, HLX, VTT, LIND, BAL) - M1-M36
This task has been led by DAPP and started since the beginning of the project in order to define the preliminary exploitable results which have been the main inputs to T7.1 and T7.2. In order to support the work of the partners, DAPP organized during the first years tailored conference calls with the partners and the responsible of the pilot cases. The scope of the conference calls was to illustrate the approach for the characterization of the exploitable results. This activity brought to a first definition and characterization of the exploitable results completed at M10. Input from all the partners have been received during this phase.
Then, an exploitation strategy seminar has been organized in April during the general meeting in Lecce (Italy). The scope of the seminar was to refine the exploitable results, to investigate carefully about the background/foreground as well as the exploitation claims of each partner for each exploitable results. After the seminar, a new characterization of the exploitable results has been carried out by involving all the partners and this activities has been preparatory with respect to the exploitation plan delivered by DAPP at M18.

Task 7.4 Modular IPR strategy definition (Lead: DAPP; Partners: DAS, POLIMI, HLX) - M18-M34
Although this task will start formally at M18, a preliminary analysis of project IPR has been already carried out in close cooperation with the activities of T7.3. Actually, the background and the foreground of each exploitable result has been carefully evaluated as well as the exploitation claims of each partner through the MULO tables.

WP8 - Standardization, dissemination, communication
Task 8.1 - Open Standards (Lead: HLX; Partners: DAS) - M6-M36
HLX, with the support of DAS, is addressed to conduct the standardization activities within the Manutelligence project. They will enable easier integration and seamless communication between the various systems the IT Platform will interact with. Indeed, the project needs to use standards and protocols for data exchange due to the large number of systems the IT platform developed will interact with. The project will interact with two main standardization activities; STEP (Standard for the Exchange of Product Model Data) and the OpenGroup QLM (Quantum Lifecycle Management). The dialogue with STEP will be carried out through the PRO-STEP industrial association, which BIBA was member and has good contacts. STEP is particularly important for the Beginning of Life and the design phase. The OpenGroup QLM dialogue will be instead carried out by HLX, QLM aims in particular the Middle and End of Life, therefore from the production till the disposal.
Task 8.2 - Industrial Dissemination and communication (Lead: DAPP; Partners: Fab, POLIMI, HLX, BAL) - M6-M36 and Task 8.3 - Scientific communication ((Lead: POLIMI; Partners: SUPSI, HLX, VTT) - M6-M36
In the first 18 months Polimi, assisted by WP8 partners (DAS, FundacióCIM, SUPSI, HLX, VTT, DAPP, BAL) achieved the following results:
• Launching of the website (
• Launching of Twitter (
• Creation of a group on Linkedin (
• Creation of a roll-up of the project for Industrial and Scientific fairs
• Creation of flyers of the project
• Creation of a gadget with the shape of the Manutelligence Logo. Furthermore, a QR code has been added, resending to the website of the project
• Participation at several conference (PLM15, CIRP Design 2015, APMS 2015, ICE2016, IPSS2016, DLM 2016 (German conference), CIRP Design 2016, etc.)
• Scientific workshops on Manutelligence project (ICE2015, ICE2016, IPSS2016)
• Participation at several fairs (MECSPE, Nuovamacut Live 2015, Advanced Manufactory Strategies, ARea16, etc.)
• Organization (by FCIM and Polimi) of World Manufacturing Forum 2016 ( WMF brings together policy experts, industry leaders of large multinationals and small to medium-sized enterprises, as well as academic leaders across the globe to discuss the economic, social and technical challenges that will impact global manufacturing in the future.

WP9 – Project Management
Task 9.1 – Planning & Scheduling (Lead: DAS) - M1-M36;
The main goal of this objective is to organize a planning to drive the project tasks execution defining
• Work Packages tasks, with duration, start and end date
• Dependencies between tasks
• Assignee of each task
• Phases and milestones
This has been done utilizing the Manutelligence platform, where was defined the project memberships, the work breakdown structure of the project with related scheduling and milestones.
Task 9.2 – Progress & cost reporting (Lead: DAS, M1-M36)
The management of the budget was organized as follows
• Forecast: each consortium partner was asked to provide the effort forecast for the overall project timeframe
• Actual: each consortium partner was asked to provide the actual effort spent by quarter in order to allow a monitoring of the effort spent and the compliance with project budget.
A template was sent to all consortium partner to ease the data entry and make it consistent..
So, with the inception of the forecast data, the upload into the platform was done to share in a single source all such data and being able to get also a synthetic and graphical view.
The values from the template are referred to the man per month effort, then we applied the average person rate provided by each partner (and part of the financial data of the Grant Agreement) when uploading such data into the platform to calculate the forecast Personnel cost.
The data organization in the platform is the same of the budget organization of the Grant Agreement, then we have the Personnel cost, the Equipment, the Indirect cost, the Other goods, the Travel & Living. In this way it is immediate to check the consistency with the project budget.
In order to trace the actual values, the same template was utilized, having already arranged the table to receive also such data.
As done for the forecast data, the actual data have been uploaded into the platform with the same logic. Each quarter the consortium partner were asked to provide the actual data to keep the financial part of the project under control.
The Personnel cost is calculated in the same manner as for the forecast, unless updated values about the average person rate are provided into the meanwhile by the partners themselves.
Having all such data into the platform, the dashboarding capabilities are used to get graphs of the project cost, allowing a quick check about the status and enabling, where needed, actions to converge to the project budget.

Task 9.3 – Monitoring, control & quality management (Lead: DAS, M1-M36)
The objective is to monitor and control the whole project execution based on the initial planning and scheduling, updating it as needed in the context of the overall project scope and budget. This has been done utilizing the platform, where the progress of the activities was traced updating the work break structure (WBS) tasks by each of the assignees to provide scheduling progress in real time. The WP1 was completed on time as planned, meanwhile all the other WPs started as planned and are currently progressing as traced into the platform.
The delivery process was monitored checking the documentation released by the consortium partners, verifying the peer review process and approval respect the timeline of the project.
The milestone monitoring was done with the same tool.

Task 9.4 – Communication management & administration infrastructure (Lead: DAS, M1-M36)
The communication is a very important factor for a project success. Then a particular attention was put on this item by utilizing a platform where to share all the documentation produced by the consortium partners, from the official one, like Grant Agreement, Consortium Agreement and related amendments as well as the project deliverables to the technical documentation developed for the solution design, to the meetings presentation, agenda and minutes.
This is really the project handbook, allowing all the consortium partners to be on the same page, avoiding typical risks of misalignment of independent silos of information and dispersion when utilizing only mails to communicate.
Regular consortium meetings were held, around one per quarter.
o Kickoff Meeting, held in Milan (Italy), hosted by POLIMI on February 11th –
13th 2015
o Meeting in Turku (Finland), hosted by Meyer Turku on May 4th – 5th 2015
o Meeting in Milan (Italy), hosted by Dassault Systemes on June 24th – 25th 2015
o Meeting in Barcelona (Spain), hosted by Fundacio CIM on October 4th – 5th 2015
o Meeting in Bremen (Germany), hosted by BIBA on December 3rd – 4th 2015
o Meeting in Lecce (Italy), hosted by D’Appolonia on April 3rd – 4th 2016
o Meeting in Öjebyn (Sweden), hosted by Lindbäcks on June 27th – 29th 2016
The Review Meeting with Project Officer is planned in Maranello (Italy), hosted by Ferrari on September 28th 2016.
Bi-weekly conference calls were setup to align all the partners about the project progress and relationships with the Project Officer.

Progress beyond the state of the art and expected potential impact (including the socio-economic impact and the wider societal implications of the project so far)

The Manutelligence project stems from the awareness of the transformation of behaviors and needs of people, with a change of pace compared to the past. From here the need to proceed to a product-service design, which then exceeds the concept of the supply of a product to the market but rather that it addresses to propose a new experience and responsive to the needs of the person. The design driven by IoT informations, with a 3D virtual representation and manufacturign simulation, has the potential to provide to the end users product-services freeing the end users from management tasks, making available the most precious thing, that is the time. On the business side, it is foreseen a potential for new activities, as consulting for platform support as well as platform services for SME. Last but not least, the capability to evaluate environment impacts and life cycle costing can have a positive social effect, especially for the future generations.
In particular
1. Fast production and delivery of personalized P-S
An integrated platform is being developed, initial deployment done, with the 3D virtual representation and manufacturing simulation available, IoT data used (integration to be developed in the second part of the project), sustainability calculation integrated for the FabLab case
2. Decreasing lead time in P-S process development
The platform will be validated with the industrial use case, currently end users data for Ferrari and Lindbacks are available for the PS process development, demonstrating the effectiveness of the improvement for the lead time reduction while working with the end users (then services) data
3. Set-up and ramp-up time reduction for new processes and plant designs (30%)
Simulation processes are being used to analyze and validate the virtual 3D representations based on the field data captured with the IoT devices developed for the Ferrari, Lindbacks and FabLab
4. P-S Business Strategy for aligning and managing all processes
Sustainibility solution is being tested for the FabLab case allowing an evalution of the most environment compliant materials and manufacturing processes, to reduce the impact. Life cyucle costing module will enable the evaluation of the overall cost.

Related information

Record Number: 193670 / Last updated on: 2017-01-24