D4.1 - Report on Collaborative Tools Integration and ... · feeding the 3DEXPERIENCE to improve...

Copyright Manutelligence Consortium 2015-2018 Manutelligence N°636951

Horizon 2020

Acronym: Manutelligence

Project No: 636951

Call: H2020-FoF-2014

Topic: FoF-05- Innovative product-service design using manufacturing intelligence

Type of action: RIA

Duration: 01.02.2015 - 31.01.2018

D4.1 - Report on Collaborative Tools Integration

and Customization

Type Deliverable

Document ID: D4.1

Workpackage: WP4

Leading partner: DAS

Author(s): Maurizio Petrucciani,, Lorenzo Marangi, Ettore

Buzzoni; Massimiliano Agosta

Dissemination level: Public

Status: Released

Date: 18/01/2017

Version: 1.9

Confidential

Copyright Manutelligence Consortium 2015-2018 Page 2 / 53

Versioning and contribution history

Version Description Contributors

1.0 First Draft Maurizio Petrucciani

1.1 Added paragraph on Collaboration tool for Project

Management

Maurizio Petrucciani

1.2 Added paragraphs on Manutelligence architecture and

Customization on Project Management

Lorenzo Marangi

1.3 Added paragraph on Interface to LCC/LCA tools Lorenzo Marangi

1.4 Added paragraph on 3DEXPERIENCE environment setup Ettore Buzzoni

1.5 Added paragraph on Collaboration tool for Enterprise CM Massimiliano Agosta

1.6 Review Lorenzo Marangi, Maurizio

Petrucciani

1.7 SUPSI & Holonix suggestions incorporated Ida Critelli, Donatella Corti

1.8 Added paragraph about I-Like LCPA data exchange Ida Critelli

1.9 Approved by peer reviewer and released Maurizio Petrucciani

Reviewers

Name Affiliation

Pekka Puranen Meyer Turku

Deliverable Peer Review Summary

ID Comments Addressed ()

Answered (A)

1

2

3

Confidential


Table of Contents

1 Introduction .............................................................................................................. 4

1.1 Scope ........................................................................................................................... 4

1.2 Relations to the other WPs ........................................................................................... 4

1.3 Structure of the Deliverable .......................................................................................... 4

2 Collaborative Design Tools ........................................................................................ 5

2.1 Manutelligence components ........................................................................................ 5

2.1.1 3DEXPERIENCE ................................................................................................................... 5

2.1.2 I-Like ................................................................................................................................ 11

2.1.3 MaGA ............................................................................................................................... 12

2.1.4 LCPA ................................................................................................................................. 13

2.2 3DEXPERIENCE environment setup ............................................................................. 14

2.2.1 DS License Server ............................................................................................................. 16

2.2.2 Database Server ............................................................................................................... 17

2.2.3 Proxy Configuration ......................................................................................................... 18

2.2.4 3DPassport and 3DDashboard Installation ...................................................................... 20

2.2.5 Exalead Full Text Search Installation ............................................................................... 21

2.2.6 3DSpace installation ........................................................................................................ 22

2.2.7 3DIndex Installation ......................................................................................................... 23

2.3 Collaboration tool for Project Management ................................................................ 24

2.3.1 Project Management Objects & Setup ............................................................................ 24

2.3.2 Customization .................................................................................................................. 27

2.4 Collaboration tool for Enterprise Change Management process ................................... 30

2.4.1 Enterprise Change Management Objects ........................................................................ 30

2.4.2 Fast and Formal Change Process ..................................................................................... 31

2.4.3 Play the Change Process .................................................................................................. 34

2.4.4 Change Process into the industrial case .......................................................................... 38

2.5 Interface sustainability (LCA), LCC & IoT Configuration description .............................. 39

2.5.1 Exchange data between 3DEXPERIENCE and LCC/LCA tools ........................................... 39

2.5.2 Exchange data between I-Like vs. 3DEXPERIENCE .......................................................... 45

2.5.3 Exchange data between I-Like vs. LCPA ........................................................................... 47

2.5.4 I-LiKe Machine FABLAB Gateway API .............................................................................. 48

2.5.5 I-LiKe Machine Lindbäcks Gateway API ........................................................................... 49

3 Relation with the industrial use cases ...................................................................... 52

4 Conclusion .............................................................................................................. 53

Confidential


1 Introduction

1.1 Scope

This deliverable is a part of Manutelligence WP4 “Manufacturing Intelligence through the

development of a modular and interoperable Product-Service Engineering environment”.

The overall objective of the WP4 is to setup a coherent environment merging the diverse

concepts, software tools and components developed in the various WPs project.

This deliverable is linked to the task “Collaborative Design Tools“ whose aim is to integrate,

customize and deploy the collaborative design tools needed for the overall

Manutelligence platform. The work will start from the Catia and Simulia Dassault tools to

manage the codified engineering knowledge. These tools will be used as a basis wherever

needed and especially for the FERRARI, MEYER and FabLab industrial cases.

1.2 Relations to the other WPs

As described in the scope, this WP is intrinsically related to the others, especially WP6,

supplying the software platform to support the use cases that have been defined and being

the basis for the demonstration of the use cases implementation. A strict relation is also

present with WP3 and WP2 for the theoretical basis of the Product Service approach as well

as life cycle and data model definition. Interaction with WP5 is key for the definition of the

interface between the design tools and the LCC and LCA tools that allow the calculation of

cost and environmental impacts. WP1 was the basis to consolidate the requirements

adopted for the platform design. WP7 is getting info from this package in order to

understand the possible exploitation, based on the features and characteristics of the

platform being designed.

1.3 Structure of the Deliverable

The deliverable is organized in an initial chapter to introduce the items detailed in the

following chapters, a second chapter describing the architecture, the software components,

the configuration, the customization and the setup of the platform, a third chapter about

the industrial cases relationships and finally with a conclusion chapter.

Confidential


2 Collaborative Design Tools

2.1 Manutelligence components

The Manutelligence Platform Architecture is composed by 3DEXPERIENCE (provided by

Dassault Systemes), I-LiKe (provided by Holonix), MaGA (provided by SUPSI) and LCPA

(provided by BALANCE).

3DEXPERIENCE Platform (web platform) is installed in “Politecnico – Milano”. The

Manutelligence’s User can access to the 3DEXPERIENCE Platform with WebTop Client

or Native Clients:

WebTop Client is a desktop environment embedded in a web browser used for

accessing most Governance & Lifecycle Management Processes;

Native Clients/Apps are native applications installed on the local workstation (Catia,

Simulia, SolidWorks, Delmia).

I-LiKe (web platform) is installed in Holonix premises.

MaGA and LCPA are native applications installed on the local workstation.

The originally proposed architecture was implemented, with some changes about the

interoperability of tools. In fact to exchange data between the different components the

standard WebServices technology was adopted due to its large diffusion in the software

world and recognition as a standard.

The backbone for the intra company data collaboration is the 3DEXPERIENCE that is

collecting and sharing the data coming from the different sources, feeding the sustainability

MaGA and LCPA tools. The I-Like is the field data collector and preliminary data analyser,

feeding the 3DEXPERIENCE to improve design and manufacturing. The data flow between

the different components is transparent for the end users.

The user interface can be from different access points to obtain the needed business

information or to create the business information in a seamlessly mode. This is the key

point of the platform concept. As example the CAD designer will interact using the so called

“native Client” of the 3DEXPERIENCE to create the 3D models, that the FEM analyst will

use to develop the FEM analysis using the “native Client” of the 3DEXPERIENCE getting the

loading conditions from the I-Like, where the telemetry analyst will retrieve the recorded

data using the I-Like user interface. The sustainability expert will use the MaGA GUI to

elaborate the environmental impacts using the data automatically coming from the BOM

analyst work done using the “WebTop Client” of the 3DEXPERIENCE.

2.1.1 3DEXPERIENCE

3DEXPERIENCE is a PLM (Product Lifecycle Management) Platform, which provides support

for Business Process applications. These applications contain pre-defined schema and

Confidential


processes to support many business industry sectors. A subset of processes that were used

for the Manutelligence platform are:

Program Management

Document Management

Engineering Change

3D modelling

FEM simulation

Cad Integration

2.1.1.1 Out of the box 3DEXPERIENCE Platform Capabilities

The following capabilities are present in 3DEXPERIENCE Platform:

1. 3DCompass

It’s the “key to the 3DEXPERIENCE Platform”

1. The compass manages access to the applications in the 3DEXPERIENCE

Platform”;

2. Each user has a personalized view and access to his/her licensed applications

based on their selected Roles;

3. Each quadrant of the compass opens a specific category of applications:

a. West : 3D Modelling (CATIA, SolidWorks)

b. South : Content and Simulation (SIMULIA, DELMIA)

c. East :Information Intelligence (3DDashboard)

d. North : Social and Collaboration apps (ENOVIA, 3DSwym)

Confidential


2. 3DPassport

3DPassport provides a secure single sign-on environment for the entire

3DEXPERIENCE Platform. It is based on the industry standard CAS (Centralized

Authentication Service – open standard for authentication management server). In

particular 3DPassport is implemented on top of CAS Server version 3.5.2

3. 3DDashboard

With 3DDashboard, user can create their own dashboard for rapid, intuitive

visualization of business and product data. 3DDashboard helps managers to ask

the right questions and connect the dots in the Platform. Also, the dashboard can

be used for Social Media Listening where widgets are automatically created for a

specific topic. The technologies used to display the information are UWA Widgets

in HTML5/CSS3/JavaScript.

Figure 1 - 3DDashboard Example

4. 3DSwym

3DSwym can create social communities to collaborate in an unstructured

environment. Communities contain Web 2.0 collaboration tools such as :

o Blogs

o Wikis

o iQuestions

Confidential


Figure 2 - 3DSwym Example

5. 3DSpace

It’s the “core” of 3DEXPERIENCE Platform, used to manage and share Content

(data, documents and related information) for Effective Collaboration.

The main functionalities used are:

Product Planning Programs: to Improve project management execution with

flexible calendars, interactive Gantt edition and monitoring the project

execution with new summary view and standardized reports. This

functionalities are used, in particular, to monitoring the Manutelligence

project as described in the paragraph “Collaboration tool for Project

Management”

Global Product Development: Engineering collaboration with Product

Structure / EBOM integrated experience (Lifecycle and Configuration) and

Improve end-to-end change governance from requirements to engineering.

The FERRARI, MEYER and FabLab industrial cases have been developed

based on these functionalities.

The 3DSpace is an object-oriented database stored within a relational model

Confidential


Figure 3 - Data Model Example

6. 3DSearch

Helps to find what you need when you need it. It’s a Federated Search for any

content: 3DSPACE, 3DSwym and 3DDashboard.

Figure 4 – Federated search

7. 6WTags

Filtering to find what you need faster. 6WTags reveal and enrich the semantics of

the Platform content and provide rapid filtering of search results. Automatically

extracted or user-defined, these tags help refine your search by filtering on one or

several of the six categories: Who, When, What, Where, Why, How.

Confidential


Figure 5 – 6WTags

2.1.1.2 3DEXPERIENCE Platform Logical Architecture

The 3DEXPERIENCE Platform Architecture is a three-tier architecture in which the

presentation, the application processing and the data management are logically

separate processes.

Figure 6 – Three-Tier Architecture

Confidential


The simplified view of logic Architecture is represented in the following picture:

Figure 7 – Logic architecture

2.1.2 I-Like

I-Like is the Holonix web platform supporting the Internet of Things (IoT) processes in the

Manutelligence platform.

2.1.2.1 Short Description of the component

The Holonix I-LiKe is a web platform aimed at retrieving, organising and visualising all the

data that are relevant to know the history and the current status of a machine or product.

The core of the solution consists of a cloud platform, a set of gateways to read data from

the field and a set of web and mobile apps to present the data to the users. Following

Figure offers a graphical representation of the architecture.

Confidential


`

Figure 8 - Holonix I-Like architectural overview

2.1.2.2 Summary of main functionalities

The cloud platform is in charge of the following four main tasks:

Storing of the relevant information collected during the machine or product

lifecycle,

Maintaining a complete representation, at any moment, of the machine or

product current status

Keeping track of the machine or product status history

Detecting machines or product alarms and anomalous conditions and notify the

users and maintainers about them

To feed the cloud platform, data must be collected from the field. This is achieved by

implementing a software component (gateway) that talks to the machine or product, does

the basic computations that are easy to be performed with low latency access to the

machine and sends the data in a secure way to the cloud platform adhering to its API. This

part is often customised to the specific case, as protocols might change across various

machines types and might be proprietary. It can reside on hardware already present on

the machines or on embedded systems added on purpose.

2.1.3 MaGA

MaGA is a software for Life Cycle Assessment developed by SUPSI. It is a standalone

application installed on the local workstation.

The Assessment calculation is based on the availability of a Bill of Material (BOM) of the

Product to be analysed.

Confidential


The Manutelligence platform is designed in order to let MaGA import the BOM from

3DEXPERIENCE Platform. Anyway MaGA can be used standalone and the BOM can be

created from scratch using the MaGA UI.

A specific interface was developed, as explained in the paragraph about the Interface that

follows, so that the user can, during the MaGA session, import the BOM automatically and

add all the information needed for the environmental impact calculation.

The MaGA session data can be saved into the 3DEXPERIENCE Platform, so that the

calculation can be carried out and refined by different users on different workstation as

needed by the work organization.

Once the Assessment calculations are completed, the final results can be uploaded in

3DEXPERIENCE Platform, making it available to all the users, as per the access rules

implemented.

Figure 9 – Screen shot from the MaGa software showing the import of the BOM

2.1.4 LCPA

LCPA is a software for Life Cycle Costing developed by Balance. It is a standalone

application installed on the local workstation.

As in the case of MaGA, the Assessment calculation is based on the availability of a Bill of

Material (BOM) of the Product to be analysed.

The Manutelligence platform is designed in order to let LCPA import the BOM from

3DEXPERIENCE Platform. Anyway LCPA can be used standalone and the BOM can be

created from scratch using the LCPA UI.

Confidential


A specific interface was developed, as explained in the paragraph about the Interface that

follows, so that the user can, during the LCPA session, import in the BOM automatically

and add all the information needed for the environmental impact calculation.

Once the calculations are completed, the final result can be uploaded in 3DEXPERIENCE

Platform, making it available to all the users, as per the access rules implemented,

Figure 10

2.2 3DEXPERIENCE environment setup

The required server infrastructure components for 3DEXPERIENCE platform are the

following, in order of installation and configuration:

Dassault Systemes (DS in the following) License Server (DSLS)

Database Server (DB)

3DPassport

3DDashboard

Federated Search

Full Text Search (FTS)

3DSpace, one unified installer for

o Live Collaboration Server (CSR)

o Business Process Services (BPS)

o Multi-Discipline Collaboration Services (CSG)

o Collaborative Space Management Services (CSG)

o 3DEXPERIENCE Apps Management (MYA)

3DIndex

Except for DSLS and DB, the 3DEXPERIENCE Platformsetup can be thought as delivering a

set of several standard basic “services” grouped together in an architecture as shown on

the bottom diagram

Confidential


Figure 11 – 3DEXPERIENCE Services

All the deployment of all the DS software components in a single server (one machine) on

Microsoft Windows environment

Confidential


2.2.1 DS License Server

Installed the DSLS V6R2015x software code

Figure 12

on a physical host (LMW-2D.polimi.it) with enrolled V6R2015x trigrams licenses

Figure 13

Then on the application server machine (webtest187.dmz.polimi.it) was created the

following license file

C:\ProgramData\DassaultSystemes\Licenses\DSLicSrv.txt

Confidential


with license server hostname and port number

LMW-2D.polimi.it:2002

2.2.2 Database Server

Performed the MS SQL Server 2012 SP2 installation on database server

VWRESSQLC06.polimi.it

and run the commands in the SQL script below to create users and tables.

Figure 14

Created ODBC Sources with SQL Server Native Client driver on the 3DEXPERIENCE

machine which have the following servers which will connect to the database:

3DPassport

3DSpace

3DDashboard

Confidential


Figure 15

2.2.3 Proxy Configuration

Installed Apache HTTP Server 2.2 with Open SSL Module, at folder C:\Apache2.2 by

httpd-2.2.22-win32-x86-openssl-0.9.8t.msi

and activate modules and declare virtual hosts configuration in file

C:\Apache2.2\conf\httpd.conf

Created the virtual hosts for the endpoints at folder

C:\Apache2.2\conf\vhosts

A “service endpoint” is the URL where your service can be accessed by a client application,

and each service in the 3DEXPERIENCE platform must have dedicated endpoints defined

before you start the installation.

Declared the endpoints on the server will most likely be registered in the DNS or in file

C:\Windows\System32\drivers\etc\hosts.

We’ll use the java JDK 1.8 & TomEE 1.7.1 with the following ports number:

Confidential


Figure 16

Of course all services – 3DPassport, 3DDashboard, and 3DSpace must be contacted from

each other and from the client only through HTTPS, and the certificates can be generated using

the OpenSSL project implementing the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security

(TLS) protocols as well as a full-strength general purpose cryptography library.

Confidential


2.2.4 3DPassport and 3DDashboard Installation

The location of the DS Installer is

C:\R2015x\DS_Installer

This same installer will be used for both 3DPaspport and 3DDashboard installation.

3DPassport was introduced for allowing seamless single sign-on access to all

applications of the platform in a secure manner. All communication with the DS

services is now over HTTPS

3DDashboard was introduced to leverage Netvibes UWA / dashboarding technology

for creating visually compelling collections of widgets for rapid decision making

Figure 17

Confidential


2.2.5 Exalead Full Text Search Installation

Via The Full Text Search server (FTS) you can find, analyze, and refine vast volumes of product information using an intuitive search interface. You can also refine and reduce results quickly, by navigating the libraries, taxonomies, type hierarchies or attribute data. FTS was installed before 3DSpace in order to minimize post-configuration, using the media in the ENOVIAFull-textSearchServerwithExalead.Windows64.zip on localhost with the following configuration and port number

Figure 18

Then the FTS URL console for administration will be http://localhost:19001/admin

Figure 19

http://localhost:19001/admin

Confidential


2.2.6 3DSpace installation

3DSpace refers to what we used to call the “ENOVIA Server”. There are two ways a user can be authenticated when accessing 3DSpace

“Internal” (3DSpace NoCAS) authentication : when logging in, it is the user

definition within the 3DSpace database

“Passport” (3DSpace CAS) authentication : Using the 3DPassport server for

authentication

The 3DSpace installer media allows you to concatenate the installation of the principal

individual components and deploy the 3DSpace service which is then up and running

therefore ready to use:

Live Collaboration Server (CSR)

Business Process Services (BPS)

Multi-Discipline Collaboration Platform (EVP)

Collaborative Space Management Services (CSG)

3DEXPERIENCE Apps Management (MYA)

Get the code 3DSpace-V6R2015x.Windows64.zip and installed on folder

Figure 20

Confidential


2.2.7 3DIndex Installation

3DIndex server required for enabling 3D searching through PLM data, for geometrically

similar parts and also creates coherent lightweight visualization with 3D Thumbnails for

leaf nodes and 3D Index information.

There are two separate environments: index creation (Build-time) and index serving

(Run-time).

Optimized run-time for both LAN and WAN access.

Figure 21

Used the following media filename to install the software components

ENOVIA3DIndexingServer-V6R2015x.Windows64.zip

Configured it to connect to localhost on port 8070 and application ENOVIA

Figure 22

Confidential


2.3 Collaboration tool for Project Management

The Project Management configuration and usage has been done adopting it for the

Manutelligence project itself, as real example of solution for a real project. This approach

can be then adopted for any other project.

2.3.1 Project Management Objects & Setup

The setup of the project management environment was done following the steps

Project creation

Figure 23

Adding members as per Consortium partner personnel list

Figure 24

Confidential


Creating the work breakdown structure (WBS) creation with the tasks as per the

Description of Action (DoA) document

Figure 25

Adding the financial forecast section organized with the items as per the Description

of Action (DoA) document

Figure 26

Create folders structure for work package deliverables as per the Description of

Action (DoA) document and the document placeholder for each deliverable

Confidential


Figure 27

Figure 28

The solution has been customized for the financial data dashboarding in order to provide

the quarter result view per each consortium partner, plus to show the cumulative result all

along the project for each partner as well as for the whole consortium, as described in the

following paragraph.

Confidential


2.3.2 Customization

2.3.2.1 Background

One of the element to control a project is to define a forecast of the budget all along the

project timeframe and compare it against the effective costs executing the project, to check

any difference between estimated and actual values. This will allow to execute appropriate

corrective and preventive actions to respect the targeted budget; the more the budget is

detailed with Cost Items, the more the control will be effective.

In Manutelligence Platform, with OOTB functionalities, we create Budget, added Expense

and monitored the Budget status. So, we can navigate to the project page that displays

graphical representations of all the details related to the project’s execution.

Figure 29

In above BUDGET graphical representation, the vertical axis represents the budget spent

and the horizontal axis represents the budget time intervals.

Since the Budget is the sum of all the cost items, we don’t have view of an individual Cost

Item.

Also, there is no view of “Cumulative Budget”. The Cumulative budgeted cost is the amount

that was budgeted to accomplish the work that was scheduled to be performed up to that

point in time.

2.3.2.2 Customization execution

Since we have to monitor the difference in the estimated and actual values of each Cost

Item and the Cumulative values a new functionality has been realized.

Figure 30

Confidential


Figure 31

The page consists of the following charts:

1. Budget Split

In the combo box you can select a single Cost Item.

The vertical axis represents the budget spent for the Cost Item and the horizontal axis

represents the budget time intervals.

2. Budget Split Cumulative

In the combo box you can select a single Cost Item.

The vertical axis represents the budget Cumulative spent for the Cost Item and the

horizontal axis represents the budget time intervals.

3. Budget

The vertical axis represents the budget spent and the horizontal axis represents the budget

time intervals.

4. Budget Split Cumulative

The vertical axis represents the budget Cumulative spent and the horizontal axis represents

the budget time intervals.

Confidential


Figure 32

2.3.2.3 Components added

The following components have been added:

Database Side : UI3

o Jpo MANU_BudgetChart

o Command MANU_PMCBudgetStatusReportCommand

o Channel PMCGateDashboardChannel1

Web side

o \programcentral\MANU_ProgramCentralBudgetStatusReport.jsp

o WEB-INF\classes\emxProgramCentralStringResource.properties

o WEB-INF\classes\emxProgramCentralStringResource_en.properties

o WEB-INF\classes\emxProgramCentralStringResource_it.properties

Confidential


2.4 Collaboration tool for Enterprise Change Management

process

The Enterprise Change Management process is a key element in any design &

manufacturing development process. The following paragraphs describes the main

components of this process implemented in the Manutelligence project.

Figure 33

The Change Management is a recursive process composed by four different steps, the full

cycle must be completed in order to execute, if needed, a new one. Each of the four phase

have a specific scope into the process, it is an end-to-end collaborative change process

that analyzes the Issues, defines the Actions and communicates Change Decisions and

assignments to all Impacted Domains.

2.4.1 Enterprise Change Management Objects

For each phase of the process we have into the system a corresponding element that

supports the user to archive and manage data (attributes and information), files

(documents and specification) and approval (signatures and authorization).The different

elements that we have into the process are: Issue, Change Request, Impact Analysis,

Change Order and Change Action.

2.4.1.1 Issue

Definition: Describes a problem or enhancement in generic terms ; can be

submitted by any employee (non-technical)

Goal: Maintain the integrity of the original reported statement with resolution

traceability;

Activities include: investigate the reported statement; assign to qualified

assignee for disposition; can identify internal resolution (CR or CO)

2.4.1.2 Change Request (CR)

Definition: describes the intent and scope of the proposed change; Used as a

vehicle to obtain a full assessment & feasibility of the change

Confidential


Goal/Output: make an informed decision before any physical change is done;

obtain business owner approval

Activities include: Analyzes impact, collect cost, time, and list of affected domains

2.4.1.3 Impact Analysis (IA)

Definition: identify the elements affected by the change and his effect on the part

of the structure that we need to modify

Goal/Output: list of affected item, evaluate implementation effort and costs

Activities include: Analyzes impact

2.4.1.4 Change Order (CO)

Definition: governance level implementation & execution of the change; plans,

assigns and monitors the progress of the change;

Goal/Output: complete the change from incorporation, validation to final

implementation for all impacted functions/domains

Activities include: creating change order, assign change actions to each affected

function/domain, monitor progress and status

2.4.1.5 Change Action (CA)

Definition: execution vehicle of the change; each technical function is empowered

to incorporate the changes necessary, obtain peer validation approval

Goal/Output: Complete the assigned change action

Activities include: make changes, capture logs, validate change, obtain peer

approval, notify completion to parent change process (CO)

2.4.2 Fast and Formal Change Process

There are two different flavours for the execution of the Change Management process in

the 3DEXPERIENCE context. The “formal” change process id used for relevant modifications

of the products. The “fast track” change process is a simplified version adopted for minor

changes.


2.4.2.1 Formal Change Process

The formal change process is used when the change requires an approval involving different functional areas of the company due to

the economic impact of the huge product change. Typical case is a change requiring the certifying authorities’ approval or the customer

approval. In the following you can find the flow representation.

Figure 34

Confidential


2.4.2.1 Fast track Change Process

The fast track process is used when the modification affects minor change of the products and does not have a relevant impact on the

economics or the product planning or certification. As shown in the following flow chart, Issue, IA and CR objects are not required.

Figure 35


2.4.3 Play the Change Process

The next paragraph explains the evolution of the Change Process of the formal flow of the

change.

2.4.3.1 Change Identification

Step 1: The Issue Owner will perform the following actions:

o Describe the problem, define Priority and the Estimated Start Date

and End Date (Reference Documents).

o Identify the product for which report a problem. (Reported Against).

o Identify a Co-Owner to manage the Issue and promote it to Assign state.

Step 2: Co-Owner perform the following actions:

o Identify who will be able to manage the Issues from the technical stand point and

assign him or them to the Issue (Assignee).

o Promote the Issue to active

Step 3: Assignees

o Review the reported problem and the related documentation if exists.

o Instantiate the resolution process (Resolved By).

2.4.3.2 Change Evaluation

Step 1: Issue Assignee perform the following actions:

o Create a new CR and:

Select the Responsible Technical Organization (RTO) of the

change.

Identify the Change Coordinator that will oversee the Assessment and Impact

Analysis

Change Coordinator is a member of the change board

responsible to oversee the completion of the request

Responsible Technical Organization (RTO) is used to identify the

organization that has ownership of the change.

Change Coordinator can be populated with the organization’s ‘lead role’

users.

Confidential


o Associate the Issue items (Reported Against) to the CR as Affected Items. When we

add an Affected Item, a new Change Action is automatically generated.

o Identify the Assignee of the Change Action

o Assign Technical Assignee and Senior Technical Assignee on each CAs associated to

the CR

o Promote the CR to Evaluate state

Step 2: Technical Assignee perform the following actions

o The CA assignee is notified by the new assignment, review the

CR and perform the analysis

o Create Impact Analysis objects associated to the CA to deeper

analyze the problem.

o Attributes of an Impact Analysis :

Quality Impact : How the quality of the product will be affected by the change

order

Lifecycle Cost Issues : Number of days to resolve the change

order (development + analysis)

Prioritization Benefit : Number indicating the priority of the

perceived benefit

Relative Cost : Relative cost to be incurred, on a scale of 1 (least) to 9 (highest)

Relative Penalty : Relative penalty, on a scale of 1 (least) to 9 (highest)

Impact Analysis Effort : Number of days to determine what the impact will be

on products and schedules

Estimated Schedule Impact : Estimated number of days to add to the schedule

due to the change order

Implementation Effort : Number of days to resolve the change order

(development + analysis)

Validation Effort : Number of days to validate the change order

Relative Risk : Relative risk, on a scale of 1 (least) to 9 (highest)

Confidential


Step 3: Once the Analysis is completed, Change Coordinator

associate to the CR the “Evaluation Reviewers List” and promote the

CR to the “In Review” state.

Step 4: The Review board analyze the documents, analysis, CR and

CA, if everything it’s correct they approve all the review tasks. The

CR is promoted to the “In Process CO” state and a new CO is created and

associated to the CR and CA.

2.4.3.3 Change Steering and Orchestration

Step 1: Technical Assignee perform the following actions

o Set the proper value for the filed “Requested Change” into CO

Affected Item.

Step 2: Define the “Estimated Completion” for every CA connected

to the CO, and promote the CA at the “In Work” state.

o If the values of “Requested Change” into CO Affected Item table

is “For Revise”, the promotion of the CA to “In Work” perform the

action to revise the objects. On the CA “Implemented Item” it’s possible

to find the new revision of the objects.

o When the last CA is promoted to “In Work”, the CO will automatically

promoted to “In Work”.

Confidential


2.4.3.4 Change Implementation

Step 1: he Engineers work on the design activities to implement the

changes.

o If the change require to develop new elements, he will associate

it to the CA as Implemented Items.

o To be able to move forward all CA’s Implemented Items must be

in Approved state.

Step 2: Promote the CA in “In Approval” state, the CA ownership

change to the Senior Technical Assignee.

Step 3: The Senior Technical Assignee review the CA and if OK,

promote it to “Complete” state.

Step 4: When the last CA is promoted to “Complete”, the CO will

automatically promoted to “Complete”.

Step 5: When the change will be applied into the production system, the

CO will be promoted to “Implemented”.

Confidential


Step 6: When the last CO is promoted to “Complete”, the CR will automatically

promoted to “Complete”.

2.4.4 Change Process into the industrial case

One of the Meyer Use Cases is addressed by the application of the change process. In fact

in the case of a failure of a component on board, the I-Like application captures the event

to launch the maintenance action and triggers the change process by creating

automatically into the 3DEXPERIENCE an Issue describing the problem.

In the simulation done, the Change Management process highlighted that the problem,

identified by the sensor on a critical component, was originated by another component.

The process, started with the automatic creation of the Issue, underwent the Evaluation

and the Analysis steps that identified that the problem was due to a filter and the Change

Order and Activities perform the substitution of such a component into the BOM (Bill of

Material) of the sister ships being manufactured in the shipyards.

Figure 36

Confidential


2.5 Interface sustainability (LCA), LCC & IoT

Configuration description

The following paragraphs describe the approach used to design the interoperability

between the software components of the Manutelligence platform

Some of the interfaces are already developed or being completed; for such interfaces it is

provided a technical detail reflecting the implementation done. Other interfaces are to be

developed so no technical details are currently available.

Depending on the testing phase with the industrial partners, some refinements could be

added in the next phase of the project.

2.5.1 Exchange data between 3DEXPERIENCE and LCC/LCA tools

This paragraph is aimed to describe the interface between 3DEXPERIENCE and MaGA

(LCA tool) and LCPA (LCC tool). The developed interfaces are about Product list and

BOM exchange, whereas the LCA/LCC assessment and proprietary project files

interfaces are being developed.

2.5.1.1 General rules

The API are used to retrieve data from the 3DEXPERIENCE Platform and import it

inside the MaGA Tool and LCPA Tool.

Involved systems Technology Used Exchange Format data

MaGA 3DEXPERIENCE REST web service XML format

LCPA 3DEXPERIENCE REST web service XML format

2.5.1.2 Workflow

A typical workflow can be:

Retrieve the list of existing products in 3DEXPERIENCE Platform and import it

into MaGA or LCPA tool

Retrieve the BOM (Bill of Material) for a specific product 3DEXPERIENCE Platform and import it into MaGA or LCPA tool

Perform the Assessment with MaGA or LCPA tool.

Send the Assessment from MaGA or LCPA tool to 3DEXPERIENCE Platform

2.5.1.3 Technical Specification

API (aka Gateway) developed

GET /resources/MANUServiceModeler/lcclca/listproducts Return the list of the product

Confidential


GET /resources/MANUServiceModeler/lcclca/listproducts?id={id} Returns the head version of the

specific product

GET /resources/MANUServiceModeler/lcclca/ebom?id={id}&expand={expandlevel} Returns the Bill of

Material of the specific product (Exchange of “BOM” information for LCCLCA Interface)

PUT /resources/MANUServiceModeler/lcclca/impact Upload of the assessment results

The following .XSD format file will be used to exchange the Assessment between

3DEXPERIENCE and MaGA or LCPA:

<?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <xs:complexType name="MaterialType"> <xs:attribute name="id" type="xs:long" use="required"/> <xs:attribute name="density" type="xs:double"/> <xs:attribute name="name" type="xs:string"/> </xs:complexType> <xs:complexType name="CountryType"> <xs:attribute name="id" type="xs:long" use="required"/> <xs:attribute name="name" type="xs:string"/> </xs:complexType> <xs:complexType name="CompanyType"> <xs:attribute name="id" type="xs:long" use="required"/> <xs:attribute name="name" type="xs:string"/> <xs:attribute name="countryId" type="xs:long"/> <xs:attribute name="salesTurnover" type="xs:double"/> </xs:complexType> <xs:complexType name="TripletType"> <xs:sequence> <xs:element name="name" type="xs:string" minOccurs="1" maxOccurs="1"/> <xs:element name="type" type="xs:string" minOccurs="1" maxOccurs="1"/> <xs:element name="value" type="xs:string" minOccurs="1" maxOccurs="1"/> </xs:sequence> </xs:complexType>

<xs:complexType name="OperationType"> <xs:attribute name="id" type="xs:long" use="required"/> <xs:attribute name="name" type="xs:string"/> <xs:attribute name="assemblyId" type="xs:long"/> <xs:sequence> <xs:element name="values" type="TripletType" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:complexType name="AssemblyCountType"> <xs:sequence> <xs:element name="assembly" type="AssemblyType" minOccurs="1" maxOccurs="1"/> </xs:sequence> <xs:attribute name="count" type="xs:int"/> </xs:complexType> <xs:complexType name="AssemblyType">

Confidential


<xs:sequence> <xs:element name="operations" type="OperationType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="childCounts" type="AssemblyCountType" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="id" type="xs:long" use="required"/> <xs:attribute name="name" type="xs:string"/> <xs:attribute name="description" type="xs:string"/> </xs:complexType> <xs:complexType name="MaterialQuantityType"> <xs:attribute name="materialId" type="xs:long"/> <xs:attribute name="quantity" type="xs:double"/> </xs:complexType> <xs:complexType name="ComponentType"> <xs:complexContent> <xs:extension base="AssemblyType"> <xs:sequence> <xs:element name="materialQuantities" type="MaterialQuantityType" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="companyId" type="xs:long"/> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="ProductType"> <xs:complexContent> <xs:extension base="AssemblyType"> <xs:attribute name="year" type="xs:int"/> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="LCAProductType"> <xs:sequence> <xs:element name="materials" type="MaterialType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="countries" type="CountryType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="companies" type="CompanyType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="product" type="ProductType" minOccurs="0" maxOccurs="1"/> </xs:sequence> <xs:attribute name="version" type="xs:long"/> </xs:complexType> <xs:element name="LCAProduct" type="LCAProductType"/> </xs:schema>

PUT /resources/MANUServiceModeler/lcclca/blob Upload and download of the proprietary

(MaGA - LCPA) project file


Figure 37 - Interface Flow chart


Sample

GET http://manutelligencetest.dmz.polimi.it/enovia/resources/MANUServiceModeler/lcclca/listproducts

GET http://manutelligencetest.dmz.polimi.it/enovia/resources/MANUServiceModeler/lcclca/listproducts?id=5

4216.39772.45328.39486

Confidential


GET http://manutelligencetest.dmz.polimi.it/enovia/resources/MANUServiceModeler/lcclca/ebom?id=54216

.39772.45328.39486&expand=0

Confidential


2.5.2 Exchange data between I-Like vs. 3DEXPERIENCE

This paragraph is aimed to describe the interface between 3DEXPERIENCE and I-Like

for the IoT data sharing. The interface about Issue management (Meyer case) is being

developed, whereas the interface about telemetry data (Ferrari case) will be developed

in the next phase of the project.


The API are used to exchange:

“Issue” information for the Meyer UseCase between i-Like and 3DEXPERIENCE

Platform.


i-Like 3DEXPERIENCE REST web service JSON format

Telemetry data information for the Ferrari UseCase between i-Like and

3DEXPERIENCE Platform.

Confidential


2.5.2.2 Workflow

A typical gateway workflow can be:

The “Meyer Turku management system”, hosted by Holonix, is retrieving, organising

and visualising all the data that are relevant to know the history and the current status

of a specific Boat.

When an anomalous condition occurs, the on board system launches the alert to the

operator for the local action and transmits the information anomalous condition to the

3DEXPERIENCE Platform creating automatically an Issue.

The Issue can be the start point for the Change Management process described in previous

Confidential


Collaboration tool for Enterprise Change Management process paragraph.


Gateway

POST /resources/MANUServiceModeler/issue/addissuejson Create an Issue object in

3DEXPERIENCE Platform

Input : JSON structure

Output : HTTP Status Codes

200 : Issue created – Return name of Issue created

501 : Issue NOT created - Return error message

Sample

POST http://manutelligencetest.dmz.polimi.it/enovia/resources/MANUServiceModeler/issue/addissuejson

{

"Issue": {

"Id": "ID1",

"Type": "Issue",

"Description": "Value Description",

"Type_ReportedAgainst": "Part",

"Name_ReportedAgainst": "LFK01",

"Rev_ReportedAgainst": "1",

"attribute_EscalationRequired": "Yes",

"attribute_EstimatedStartDate": "11/21/2016",

"attribute_EstimatedEndDate": "11/23/2016",

"attribute_Priority": "High",

"attribute_CoOwner": "lfk|zpi|Test Everything",

"attribute_ProblemType": "Performance",

"attribute_ResolutionRecommendation": "Value Resolution Recommendation",

"attribute_StepsToReproduce": "Value Steps To Reproduce",

"CategoryClassification": "Value Category_Classification",

"ReportingOrganization": "Meyer",

"Policy": "Value Policy",

"Vault": "Value Vault",

"Owner": "Value Owner"

}

}

2.5.3 Exchange data between I-Like vs. LCPA

This paragraph is aimed to describe the interface between I-Like and LCPA tool

developed by BALANCE in order to use data acquired in Lindbäcks apartment for Life

Cycle Costing.


The API are used to exchange:

Data coming from Lindbäcks apartment (e.g. temperature, alarm, humidity )


I-Like LCPA REST web service JSON format

Confidential


2.5.3.2 Workflow

A typically workflow can be:

Balance tool BAL.LCPA downloads the averages measured values of the sensors

for a given interval.

By using the values the energy consumption will be calculated in BAL.LCPA

Price models of different energy suppliers are stored in the system.

The real energy consumption based on measurements in the apartment and the

energy costs based on actual price models are calculated.

The BAL.LCPA tool compares the “real” energy consumption of the apartment

based on measurements with the calculated energy consumption based on

mathematical models.

GOAL for the designer: The designer gets a feedback of his calculations done

during the construction phase. He is able to improve the energy consumption

due to optimised isolations for the next apartment.

The energy consumption values/costs will be published for the tenant.

GOAL for the tenant: The tenant is aware of his energy consumption and the

energy consumption costs on a daily basis and also room-related (in case the

measurements are done in every room).

The tenant is able to adapt his energy consumption habits based on real

measured data.


In order to get a listing of the buildings/units it’s possible to use the following endpoints:

GET /debug/buildings

GET /debug/buildings/{buildingId}

GET /debug/buildings/{buildingCode}?code=true

GET /debug/buildings/{buildingId}/units

GET /debug/buildings/{buildingCode}/units?code=true

GET /debug/buildings/{buildingId}/units/{unitId}

GET /debug/buildings/{buildingCode}/units/{unitCode}?code=true

In order to get data:

GET /buildings/{buildingId}/units/{unitId}/snapshots/aggregate

This command returns the averages sensors reading aggregated with a given interval.

GET /buildings/{buildingId}/units/{unitId}/snapshots/aggregate?code=true

This command returns the averages sensors reading aggregated with a given interval, but

uses the building and unit code instead of theirs id.

Confidential


2.5.4 I-LiKe Machine FABLAB Gateway API

This paragraph is aimed to describe the interface between I-Like and the 3DPrinter of

the FabLab industrial case. The interface is being developed, testing are running to

refine it.


The API is currently supporting resource lookup by both id (meaning database generated

id), or by code; the code is intended to be a unique (globally or locally) identifier

meaningful in the domain context, that can be computed by all parties. E.g. for a milling

machine, it may be manufacurerCode + "_" + machineCode + "_" +

machineSerialNumber. The code lookup is the one likely to be used, as with few

assumptions, greatly simplifies the interaction between the parties. The id lookup will

eventually be dropped if deemed useless.

2.5.4.2 Workflow


Send machine information to create the machine, this is needed only the first

time, but if repeated, the error returned can just be ignored. This step can be

skipped if the machine is intended to be created by other means, e.g. via web

portal or by providing a hardcoded list of the machines on the back end.

Send the gateway start information, this will create the gateway entry on the

backend if it's unknown.

Every x minutes, send a gateway touch message, so the last gateway activity

(independently of the monitoring tasks) can be tracked.

Every x minutes, send a machine sample, to update its status on the back end.

When an anomalous condition occurs or an alarm signal is raised on the machine,

send an alarm message to the backend, including the alarm start date and a

UUID.

When the anomalous condition terminates or the alarm signal is dropped on the

machine, send an alarm message to the backend, including the alarm end date

and the same UUID used to start the alarm.


Gateway

POST /gateways/{id}/start

POST /gateways/{code}/start?code=true

POST /gateways/{id}/touch

POST /gateways/{code}/touch?code=true

Machine

Confidential


POST /machines

Sample

POST /gateways/{gatewayId}/machines/{machineId}/samples

POST /gateways/{gatewayCode}/machines/{machineCode}/samples?code=true

Alarm

POST /gateways/{gatewayId}/machines/{machineId}/alarms

POST /gateways/{gatewayCode}/machines/{machineCode}/alarms?code=true

PUT /gateways/{gatewayId}/machines/{machineId}/alarms/{uuid}

PUT /gateways/{gatewayCode}/machines/{machineCode}/alarms/{uuid}?code=true

2.5.5 I-LiKe Machine Lindbäcks Gateway API

This paragraph is aimed to describe the interface between I-Like and the black box

developed by BIBA to capture the sensors information of the Lindbäcks industrial case.

The interface is being developed, testing are running to refine it.


The API is currently supporting resource lookup by both id (meaning database generated

id), or by code; the code is intended to be a unique (globally or locally) identifier

meaningful in the domain context, that can be computed by all parties. E.g. for a milling

machine, it may be manufacturerCode + "_" + machneCode + "_" +

machineSerialNumber. The code lookup is the one likely to be used, as with few

assumptions, greatly simplifies the interaction between the parties. The id lookup will

eventually be dropped if deemed useless.

2.5.5.2 Workflow


Send building information to create the building, this is needed only the first

time, but if repeated, the error returned can just be ignored. This step can be

skipped if the building is intended to be created by other means, e.g. via web

portal or by providing a hardcoded list of the buildings on the back end.

Send the gateway start information, this will create the gateway entry on the

backend if it's unknown.

Every x minutes, send a gateway touch message, so the last gateway activity

(independently of the monitoring tasks) can be tracked.

Every x minutes, send a building or unit sample, to update their status on the

back end.

Confidential


When an anomalous condition occurs or an alarm signal is raised on the machine,

send an alarm message to the backend, including the alarm start date and a

UUID.

When the anomalous condition terminates or the alarm signal is dropped on the

machine, send an alarm message to the backend, including the alarm end date

and the same UUID used to start the alarm.


Gateway

POST /gateways/{id}/start

POST /gateways/{code}/start?code=true

POST /gateways/{id}/touch

POST /gateways/{code}/touch?code=true

Building

POST /buildings

Sample

POST /gateways/{gatewayId}/buildings/{buildingId}/samples

POST /gateways/{gatewayCode}/buildings/{buildingCode}/samples?code=true

POST /gateways/{gatewayId}/buildings/{buildingId}/units/{unitId}/samples

POST /gateways/{gatewayCode}/buildings/{buildingCode}/units/{unitCode}/samples?code=true

Alarm

POST /gateways/{gatewayId}/buildings/{buildingId}/alarms

POST /gateways/{gatewayCode}/buildings/{buildingCode}/alarms?code=true

PUT /gateways/{gatewayId}/buildings/{buildingId}/alarms/{uuid}

PUT /gateways/{gatewayCode}/buildings/{buildingCode}/alarms/{uuid}?code=true

POST /gateways/{gatewayId}/buildings/{buildingId}/units/{unitId}/alarms

POST /gateways/{gatewayCode}/buildings/{buildingCode}/units/{unitCode}/alarms?code=true

PUT /gateways/{gatewayId}/buildings/{buildingId}/units/{unitId}/alarms/{uuid}

PUT /gateways/{gatewayCode}/buildings/{buildingCode}/units/{unitCode}/alarms/{uuid}?code=true

Confidential


3 Relation with the industrial use cases

The Manutelligence platform design was organized to support the industrial cases of the

Manutelligence project. The Ferrari case has been developed using the CAD design and

simulation capabilities for the frequency and modal analysis as well as the IoT

functionalities to capture and elaborate the driver usage of the car, recording the info via

telemetry. The Meyer case has been managed with the enterprise change management

fed via the IoT issue data coming from the operation. The FabLab made usage of the CAD

design & BOM management functionalities to develop the lamp 3d-printing case, predicting

the environmental impact with the sustainability tool and measuring the on operation

energy consumption via the IoT solution. The Lindbäcks case utilized the IoT functionalities

to monitor in real time the apartment usage via a remote device, like a smartphone.

Based on the result obtained right now, it appears that the Manutelligence exploitation

can be extended not only to the companies of the same industrial sector, meaning

automotive, shipbuilding, construction, but also to other industries where the service

component can be a source of new business, like, as example, the white goods sector. In

fact also in this sector there is the need to gather informations about the usage of the

products to improve design and manufacturing.

Confidential


4 Conclusion

The Manutelligence solution is an integrated platform that enables the usage of different

tools in a seamless design environment. The architecture of this platform is based on the

utilization of existing software for the design, manufacturing and IoT components, whereas

for the sustainability assessment (economic and environmental aspects) software that are

being developed by project partners have been adopted.

The platform is able to support the industrial cases taken as project references and can be

further utilized by other sectors.

The openness of the platform is an important factor for the possible further interoperability

extensions.

Date post:	02-May-2018
Category:	Documents
Upload:	lenga
View:	215 times
Download:	2 times