D8.1 - Standardization - Manutelligence · 2 Standardization objectives and methodology 2.1...

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

D8.1 - Standardization

Type Deliverable

Document ID: D8.1

Workpackage: WP8

Leading partner: HOLONIX

Author(s): Ida Critelli, Maurizio Petrucciani, Lorenzo

Marangi

Dissemination level: Public

Status: Final Version

Date: 01/06/2017

Version: 3.0

Versioning and contribution history

Version Description Contributors

1.0 First Draft HX, DAS

2.0 Second Version HX

3.0 Final HX, DAS

Reviewers

Name Affiliation

Michele De Santis/Giannicola Loriga DAPP

Deliverable Peer Review Summary

ID Comments Addressed ()

Answered (A)

1 Minor changes and suggestions

2

3

4

5

Table of Contents

Table of Contents.............................................................................................................. 3

List of Figures .................................................................................................................... 3

1 Introduction and scope of this deliverable ................................................................. 4

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

1.2 Relations to the other Manutelligence Documents ........................................................ 4

1.3 Relations to the other WPs ........................................................................................... 4

1.4 Structure of the Deliverable .......................................................................................... 4

2 Standardization objectives and methodology ............................................................ 5

2.1 Introduction ................................................................................................................. 5

2.2 Objectives .................................................................................................................... 5

2.3 Standards analysis ........................................................................................................ 6

2.3.1 STEP ................................................................................................................................... 6

2.3.2 QLM ................................................................................................................................... 7

2.4 Standards selection and development .......................................................................... 7

2.4.1 Exchange of Product Model Data ...................................................................................... 7

2.4.2 Exchange and communication between systems ............................................................. 8

2.4.3 Exchange data between i-LiKe cloud platform .................................................................. 8

2.4.4 Exchange data between 3DEXPERIENCE and LCC/LCA tools ........................................... 11

2.4.5 Exchange data between I-Like vs. 3DEXPERIENCE .......................................................... 21

2.4.6 Exchange data between I-Like vs. LCPA ........................................................................... 23

3 Conclusion .............................................................................................................. 25

List of Figures

Figure 1: overall architecture. ................................................................................................................................. 6 Figure 2: type of systems using STEP. ................................................................................................................... 6 Figure 3 - Interface Flow chart .............................................................................................................................. 18

1 Introduction and scope of this deliverable

1.1 Scope

According to the Description of Action, this deliverable is part of WP8 “Standardization,

dissemination and communication”. This document provides the description of P-S

standardization activities like developed and implemented methodology, the selected standards

to focus, as well as some examples of how the standardization activities can be adopted by

Manutelligence industrial use cases. D8.1 is a report which describes the infrastructure,

protocols and standards for data exchange between the different modules of Manutelligence

platform. This Deliverable D8.1 is due at project month PM 30.

1.2 Relations to the other Manutelligence Documents

D4.1 - Report on Collaborative Tools Integration and Customization,

D4.3 - Report on P-S IoT Middleware Development and Integration.

1.3 Relations to the other WPs

The deliverable “Report on P-S standardization”, regarding Task 8.1 of WP8, is closely linked

to WP3 and WP4 due to the fact that some fundamental elements (e.g. data exchange

methodologies and protocols) for retrieving data from the field and exchanging data from

different modules are developed in these WPs. In addition, it is strongly related to WP6,

providing examples of how the standardization activities can be adopted by Manutelligence

industrial use cases.

1.4 Structure of the Deliverable

The deliverable is structured in an initial chapter that contains introduction to the document; a

second chapter describing some methodologies for standardization, then standards selection

and development into the Manutelligence platform covering also different exchanging

implementation. The third and final chapter includes conclusions.

2 Standardization objectives and methodology

2.1 Introduction

The standardization activity is one of the means to maximize the impact of the Manutelligence

project.

Standardization in the field of industrial data integration is a complex and necessary task. This

task is particularly important for Manutelligence since standardization enables easier

integration and seamless communication between the various systems the IT Platform are

interacting with.

There are numerous business and technological standards to represent information on

processes, objects, architecture frameworks and data format, developed by various bodies as

international or national normalization bodies like ISO, CEN, DIN, AFNOR, etc.,

standardization consortiums or groups like W3C, OMG, TOG, etc. and industrial associations

as ASD, POSC CAESAR, ENERGISTICS, etc. About PLM it is worth of note to mention CPO,

Code of PLM Openness, a Prostep ivip initiative, which interoperability concepts and

methodologies were taken into account in the Manutelligence project.

Moreover, the existing information representation standards are not covering all the needs of

industry, particularly to support innovative processes, products, plants and services.

These standards need to be modified, extended and maintained to follow the new needs and

also the new technological capabilities for their implementation.

On the other hand, many projects develop in parallel new resources to capture semantics based

on semantic web technologies and there is a risk of discrepancy instead of standardization.

In short, it is a challenge to harmonize the approach of standard in the information field.

In this scenario, the Manutelligence consortium has developed some methodologies in order

to support standardization activities functional to development and deployment of the

Manutelligence platform.

2.2 Objectives

The Manutelligence platform (Figure 1) is a modular and distributed IT architecture which is

designed to achieve the following objectives:

1) to merge the current design, manufacturing and PLM systems with IoT (Internet of

Things) derived systems and enable designers to have holistic view on product and

product-items lifecycle, searching and managing data from heterogeneous data sources;

2) to access these information through an intuitive 3D interface representing the digital

representation of the product, containing both information from the digital mock up

(PLM) and those coming from the IoT.

Figure 1: overall architecture.

In this landscape, 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). These tools interoperate together to exchange data

between different components, using standard methodologies, and forming a complete platform

to fulfil the above goals.

2.3 Standards analysis

According to DoA the project should interact with two main standardization activities; STEP

(Standard for the Exchange of Product Model Data) and the OpenGroup QLM (Quantum

Lifecycle Management). The next paragraphs provide an overview on these standards.

2.3.1 STEP

STEP is an industry standard for product data representation and it is composed of several parts

(application protocols) whose aim is to focus on a specific industrial context. There are

application protocols for 3D product design, for mechanical and electrical engineering, for

sheet-metal manufacturing, for product assembly, for the automotive industry, etc.

STEP is an open and neutral standard managed by ISO, designed to cover the full scope of

needs for exchange and archival of PLM data. The types of systems that use STEP are shown

in

Figure 2.

Figure 2: type of systems using STEP.

2.3.2 QLM

The Quantum Lifecycle Management (QLM) is the name of a Work Group of The Open Group

where Work Group members work to establish open, vendor-neutral IT standards and

certifications in a variety of subject areas critical to the enterprise.

The QLM connectivity model is similar to that of the Internet itself. Where the Internet uses the

HTTP protocol for transmitting HTML coded information mainly intended for human users,

QLM uses the QLM Messaging Interface (MI) for transmitting XML coded information mainly

intended for automated processing by information systems. The MI provides an interface for

making and responding to requests for instance specific information. A defining characteristic

of the MI is that nodes do not have predefined roles, as it follows a “peer-to-peer”

communications model. This means that products can communicate directly with each other or

with back-end servers, but the MI can also be used for server-to-server information exchange

of sensor data, events, and other information. The MI allows one-off or standing information

request subscriptions to be made. Subscriptions can be made for receiving updates at regular

intervals or on an event basis, when the value or status changes for the information subscribed

to. The MI also supports read and write operations of the value of information items.

2.4 Standards selection and development

The objective of this paragraph is to provide a description of the standards that has been selected

and adopted inside the Manutelligence platform. The main goals of the standardization

activities carried out inside the project and also the adoption of the standards described in the

following, are to increase the interoperability and maximize the impact of the project. The

adoption of these standards is also a key element in terms of exploitation of the Manutelligence

platform.

2.4.1 Exchange of Product Model Data

In the context of the industrial use case and scenario of the Manutelligence project, the Product

Model Data Exchange mostly involved the BOM (Bill Of Material). This is clearly evident in

the case of the LCC/LCA and correspondent applications in charge of the computation, MaGA

and LCPA. In fact, such computations are based on Electronic E-BOM information coming

from the 3DExperience platform, which is the product data owner. The details of the Product

Model Data Exchange are described in the paragraph 2.4.4. The CAD data exchange was not

required in the case of Ferrari and FabLab cases since they are using the already integrated

product CATIA and Solidworks within the 3DExperience platform. About the Meyer case, the

STEP format is supported by CADMATIC (the current CAD application used in Meyer Turku)

only for the hull structure, not for the outfitting. Then some CAD data exchange was done to

import CAD data in 3DExperience via dxf and idf neutral format. Anyway the principal data

exchange in the Meyer case was about the Issue management as described in the paragraph

2.4.5.

2.4.2 Exchange and communication between systems

According to the DoA, communication between different systems, should be done using the

QLM open standard. On the other hand, in compliance with the requirements of the use cases,

the communication is implemented using the REST approach, which in some way is inspired

to QLM, but it is more efficient and easy to implement. Furthermore, this could also be a

contribution to the communication standards to the Open Group. The REST (REpresentational

State Transfer) is an architectural style, and an approach to communications that is often used

in the development of Web services. REST's decoupled architecture, and lighter weight

communications and for such reason make REST a popular building style for cloud-based APIs,

such as those provided by the most common cloud provides (e.g. Google, Amazon). When web

services use REST architecture, they are called RESTful APIs (Application Programming

Interfaces) or REST APIs.

The Manutelligence platform is also based on the REST approach, exposing the relevant

entities of the data model and operating over them via HTTP verbs.

The REST approach grants easy to use and portable API, leveraging on the HTTP protocol,

well known by developers and widely supported on all platforms.

For specific tasks, in particular to ease the gateway operations and data retrieving, a few

endpoints following the concept of procedure over HTTP are present in the platform.

From the perspective of the programmer using the APIs, they can be seen as divided in two

main parts, gateway API and client API.

The gateway API enables the machine to cloud communication, and specifically includes:

gateway registration and notifications endpoints, used to track the gateways and

check the gateway status;

machine status endpoints, to receive machine general information (e.g. for machine

registration) and machine status updates;

alarm endpoints, to record alarm events on the machines, that will eventually trigger

all the notification chain on the cloud platform.

The client API enables the cloud to client (e.g. mobile app, web portal) communication, and

includes:

general and utilities endpoints, including user registration, login, logout, device

registration;

company endpoints, to retrieve all the information of the machines owned by a

company and to subscribe and track new machines;

manufacturer endpoints, to create and list the machine types and alarm types.

2.4.3 Exchange data between i-LiKe cloud platform

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 going to be

developed and so no technical details are currently available.

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.

General rules

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.

Workflow

A typical gateway workflow can be:

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 is 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.

Technical Specification

Gateway

POST /gateways/{id}/start

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

POST /gateways/{id}/touch

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

Machine

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

I-LiKe Machine Lindbäcks Gateway API

This paragraph is aimed to describe the interface between I-Like and the IoT gateway 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.

General rules

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 + "_" + 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.

Workflow

A typical gateway workflow can:

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

first time, but if repeated, the returned error 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.

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?cod

e=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

On top of that, data are exchanged between 3DEXPERIENCE, LCPA and MaGA as illustrated

in the next paragraphs.

2.4.4 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.

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

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


API (aka Gateway) developed

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

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)

POST /resources/MANUServiceModeler/lcclca/assessment/upload/{param1}/{param2}

Upload of the assessment results

Where:

IDProduct (IdPart)

ExternalToolUsed (can be LCC or LCA)

The following .JSON is an example of files to exchange Assessment between

3DEXPERIENCE and MaGA or LCPA:

{

"indicators": [{ "id": "d83f28cd-ef1e-4fbe-9b73-564aa65baf3c",

"name": "Abiotic depletion potential",

"description": "Methodology: CML2001 - The ADP indicator measures the depletion of non-renewable abiotic natural resources (i.e. fossil and mineral resources) as the fraction of the resource reserve used for a single unit out of the solution

space weighted by the fraction of the resource reserve that is extracted in one year.",

"acronym": "ADP", "unit": "kg eq. Sb"

}, {

"id": "104860e3-7a89-4100-875c-4da2a872167b", "name": "Eutrophication potential",

"description": "The ETP indicator measures the contribution to the water eutrophication (enrichment in

nutritive elements) of lakes and marine waters caused by the release of polluting substances.", "acronym": "ETP",

"unit": "kg eq. PO?"

}, {

"id": "d8d97925-97dd-49f7-8df8-2460c3eee8bc",

"name": "Human toxicity potential",

"description": "Methodology: CML2001 - The HTP measures the relative impact of the emitted substances on humans due to emission to environmental compartments (air, fresh water, sea water, agricultural and industrial soil).",

"acronym": "HTP",

"unit": "kg eq. 1,4DCB" }, {

"id": "7384e90e-1f1e-4410-98ba-192fa176edde",

"name": "Metal depletion", "description": "Methodology: ReCiPe - The MD indicator measures the depletion of metal resources as the

fraction of the resource reserve used weighted by the fraction of the resource reserve that is extracted in one year.",

"acronym": "MD", "unit": "kg eq. FE"

}, { "id": "c68e9ebc-2217-4d42-8cb3-b7ff24571237",

"name": "Endpoint total",

"description": "Methodology: ReCiPe - The ReCiPe endpoint indicator (EP) summarize the damages generated on the environmental areas of protection (Human Health, Nature, Resources).",

"acronym": "EP",

"unit": "points"

}, {

"id": "83a8f02b-8fe1-48a2-b357-b423e598eefa",

"name": "Acidification potential", "description": "Methodology: CML2001 - The AP indicator measures the contribution to the acidification

caused by gas emissions in the atmosphere.",

"acronym": "AP", "unit": "kg eq. SO?"

}, {

"id": "73a61296-bcf6-43e7-a269-de1faadc58a1", "name": "Photochemical oxidation potential",

"description": "Methodology: CML2001 - The POCP indicator calculates the potential creation of

tropospheric ozone (\"summer smog\" or \"photochemical oxidation\") caused by the release of those gases which will become oxidants in the low atmosphere under the action of the solar radiation.",

"acronym": "POCP",

"unit": "kg eq. C?H?" }, {

"id": "0744cbd0-630b-47f0-82df-2675f213b71d",

"name": "Land use", "description": "Methodology: CML2001 - The LD indicator measures the space used by factories and

warehouses belonging to the solution space.",

"acronym": "LD", "unit": "m²a"

}, {

"id": "e03dae42-a425-4dd0-855b-7713ef0eeaf2", "name": "Global warming potential",

"description": "Methodology: CML2001 - The GWP indicator measures the contribution to the global

warming caused by the emission of green house gasses in the atmosphere.", "acronym": "GWP",

"unit": "kg eq. CO?"

}, { "id": "55ea6d1e-d44d-497e-99eb-e25f7ac8cb1a",

"name": "Stratospheric ozone depletion",

"description": "Methodology: CML2001 - The SOD indicator measures the contribution to the depletion of the stratospheric ozone layer caused by gas emissions.",

"acronym": "SOD",

"unit": "kg eq. CFC-11" }, {

"id": "b1724903-e7ba-4f65-92b8-1a72a26eef7b",

"name": "Water depletion",

"description": "Methodology: ReCiPe - The WD indicator measures the water of any quality (drinkable,

industrial,...) consumed during the whole life cycle of the product.",

"acronym": "WD", "unit": "m³"

}], "phases": [{

"id": "8759816a-98d6-469e-b4d6-4052bea0650e",

"name": "Materials" }, {

"id": "8e13ee5a-f24c-4966-bddc-4103e5d1634c",

"name": "Usage" }, {

"id": "df2d557b-a56d-45ef-81ac-7829bb375ed6",

"name": "End of life"

}, {

"id": "468a9913-6419-457c-a919-1469f119a2f0", "name": "Transportation"

}, {

"id": "cefa9b28-8718-4eb4-b469-ad304d222d2d", "name": "Manufacturing"

}],

"entries": [{ "indicatorId": "d8d97925-97dd-49f7-8df8-2460c3eee8bc",

"phaseId": "df2d557b-a56d-45ef-81ac-7829bb375ed6",

"value": 0.07993049615999999 }, {

"indicatorId": "d8d97925-97dd-49f7-8df8-2460c3eee8bc", "phaseId": "468a9913-6419-457c-a919-1469f119a2f0",

"value": 0.00822890485

}, { "indicatorId": "d8d97925-97dd-49f7-8df8-2460c3eee8bc",

"phaseId": "cefa9b28-8718-4eb4-b469-ad304d222d2d",

"value": 2.1780552163999998

}, {

"indicatorId": "d8d97925-97dd-49f7-8df8-2460c3eee8bc",

"phaseId": "8759816a-98d6-469e-b4d6-4052bea0650e", "value": 16.7678188185

}, {

"indicatorId": "d8d97925-97dd-49f7-8df8-2460c3eee8bc", "phaseId": "8e13ee5a-f24c-4966-bddc-4103e5d1634c",

"value": 0.6997488

}, { "indicatorId": "d83f28cd-ef1e-4fbe-9b73-564aa65baf3c",


"value": 4.265149248000001E-4 }, {

"indicatorId": "d83f28cd-ef1e-4fbe-9b73-564aa65baf3c",

"phaseId": "468a9913-6419-457c-a919-1469f119a2f0", "value": 2.6341180379999994E-4

}, {

"indicatorId": "d83f28cd-ef1e-4fbe-9b73-564aa65baf3c", "phaseId": "cefa9b28-8718-4eb4-b469-ad304d222d2d",

"value": 0.03732979463600001

}, { "indicatorId": "d83f28cd-ef1e-4fbe-9b73-564aa65baf3c",

"phaseId": "8759816a-98d6-469e-b4d6-4052bea0650e",

"value": 0.026932224944999993 }, {

"indicatorId": "d83f28cd-ef1e-4fbe-9b73-564aa65baf3c",

"phaseId": "8e13ee5a-f24c-4966-bddc-4103e5d1634c", "value": 0.019425008

}, {

"indicatorId": "104860e3-7a89-4100-875c-4da2a872167b", "phaseId": "df2d557b-a56d-45ef-81ac-7829bb375ed6",

"value": 3.3519332448E-4

}, { "indicatorId": "104860e3-7a89-4100-875c-4da2a872167b",

"phaseId": "468a9913-6419-457c-a919-1469f119a2f0",

"value": 1.33688221195E-4 }, {

"indicatorId": "104860e3-7a89-4100-875c-4da2a872167b",


"value": 0.019508038177600003

}, {

"indicatorId": "104860e3-7a89-4100-875c-4da2a872167b", "phaseId": "8759816a-98d6-469e-b4d6-4052bea0650e",

"value": 0.026032578377499997 }, {

"indicatorId": "104860e3-7a89-4100-875c-4da2a872167b",


}, {

"indicatorId": "7384e90e-1f1e-4410-98ba-192fa176edde", "phaseId": "df2d557b-a56d-45ef-81ac-7829bb375ed6",

"value": 0.002750678568

}, {

"indicatorId": "7384e90e-1f1e-4410-98ba-192fa176edde",

"phaseId": "468a9913-6419-457c-a919-1469f119a2f0", "value": 0.00123539962285

}, {

"indicatorId": "7384e90e-1f1e-4410-98ba-192fa176edde", "phaseId": "cefa9b28-8718-4eb4-b469-ad304d222d2d",

"value": 0.307127110008

}, { "indicatorId": "7384e90e-1f1e-4410-98ba-192fa176edde",


"value": 3.152953131 }, {

"indicatorId": "7384e90e-1f1e-4410-98ba-192fa176edde", "phaseId": "8e13ee5a-f24c-4966-bddc-4103e5d1634c",

"value": 0.08575456

}, { "indicatorId": "55ea6d1e-d44d-497e-99eb-e25f7ac8cb1a",


"value": 2.0527547903999997E-8

}, {

"indicatorId": "55ea6d1e-d44d-497e-99eb-e25f7ac8cb1a",

"phaseId": "468a9913-6419-457c-a919-1469f119a2f0", "value": 5.862714742999999E-9

}, {

"indicatorId": "55ea6d1e-d44d-497e-99eb-e25f7ac8cb1a", "phaseId": "cefa9b28-8718-4eb4-b469-ad304d222d2d",

"value": 4.3023667901600007E-7

}, { "indicatorId": "55ea6d1e-d44d-497e-99eb-e25f7ac8cb1a",


"value": 2.4324096365E-7 }, {

"indicatorId": "55ea6d1e-d44d-497e-99eb-e25f7ac8cb1a",

"phaseId": "8e13ee5a-f24c-4966-bddc-4103e5d1634c", "value": 2.665376E-7

}, {

"indicatorId": "73a61296-bcf6-43e7-a269-de1faadc58a1", "phaseId": "df2d557b-a56d-45ef-81ac-7829bb375ed6",

"value": 2.2132868976E-5

}, { "indicatorId": "73a61296-bcf6-43e7-a269-de1faadc58a1",

"phaseId": "468a9913-6419-457c-a919-1469f119a2f0",

"value": 6.113924318499999E-6 }, {

"indicatorId": "73a61296-bcf6-43e7-a269-de1faadc58a1",

"phaseId": "cefa9b28-8718-4eb4-b469-ad304d222d2d", "value": 0.0014885612385600003

}, {

"indicatorId": "73a61296-bcf6-43e7-a269-de1faadc58a1", "phaseId": "8759816a-98d6-469e-b4d6-4052bea0650e",

"value": 0.0020999902332

}, { "indicatorId": "73a61296-bcf6-43e7-a269-de1faadc58a1",

"phaseId": "8e13ee5a-f24c-4966-bddc-4103e5d1634c",

"value": 7.562216E-4 }, {

"indicatorId": "c68e9ebc-2217-4d42-8cb3-b7ff24571237",


"value": 0.04263364367999999

}, {

"indicatorId": "c68e9ebc-2217-4d42-8cb3-b7ff24571237", "phaseId": "468a9913-6419-457c-a919-1469f119a2f0",

"value": 0.0039963383289999994 }, {



}, {

"indicatorId": "c68e9ebc-2217-4d42-8cb3-b7ff24571237", "phaseId": "8759816a-98d6-469e-b4d6-4052bea0650e",

"value": 1.2847816797500005

}, {



}, {

"indicatorId": "e03dae42-a425-4dd0-855b-7713ef0eeaf2", "phaseId": "df2d557b-a56d-45ef-81ac-7829bb375ed6",

"value": 0.8123702831999999

}, { "indicatorId": "e03dae42-a425-4dd0-855b-7713ef0eeaf2",

"phaseId": "468a9913-6419-457c-a919-1469f119a2f0",

"value": 0.036365680035 }, {

"indicatorId": "e03dae42-a425-4dd0-855b-7713ef0eeaf2", "phaseId": "cefa9b28-8718-4eb4-b469-ad304d222d2d",

"value": 5.424984314319999

}, { "indicatorId": "e03dae42-a425-4dd0-855b-7713ef0eeaf2",


"value": 4.0371839795

}, {

"indicatorId": "e03dae42-a425-4dd0-855b-7713ef0eeaf2",


}, {

"indicatorId": "0744cbd0-630b-47f0-82df-2675f213b71d", "phaseId": "df2d557b-a56d-45ef-81ac-7829bb375ed6",

"value": 0.006039676944

}, { "indicatorId": "0744cbd0-630b-47f0-82df-2675f213b71d",

"phaseId": "468a9913-6419-457c-a919-1469f119a2f0",

"value": 0.0023800858829999996 }, {

"indicatorId": "0744cbd0-630b-47f0-82df-2675f213b71d",


}, {

"indicatorId": "0744cbd0-630b-47f0-82df-2675f213b71d", "phaseId": "8759816a-98d6-469e-b4d6-4052bea0650e",

"value": 1.4330505460149998

}, { "indicatorId": "0744cbd0-630b-47f0-82df-2675f213b71d",


"value": 0.2401408 }, {

"indicatorId": "b1724903-e7ba-4f65-92b8-1a72a26eef7b",

"phaseId": "df2d557b-a56d-45ef-81ac-7829bb375ed6", "value": 0.021382505423999998

}, {

"indicatorId": "b1724903-e7ba-4f65-92b8-1a72a26eef7b", "phaseId": "468a9913-6419-457c-a919-1469f119a2f0",

"value": 3.1445706845E-5

}, { "indicatorId": "b1724903-e7ba-4f65-92b8-1a72a26eef7b",


"value": 0.15112548048880003 }, {

"indicatorId": "b1724903-e7ba-4f65-92b8-1a72a26eef7b",


"value": 0.4091209435414999

}, {

"indicatorId": "b1724903-e7ba-4f65-92b8-1a72a26eef7b", "phaseId": "8e13ee5a-f24c-4966-bddc-4103e5d1634c",

"value": 0.011577216 }, {

"indicatorId": "83a8f02b-8fe1-48a2-b357-b423e598eefa",

"phaseId": "df2d557b-a56d-45ef-81ac-7829bb375ed6", "value": 3.649008672E-4

}, {

"indicatorId": "83a8f02b-8fe1-48a2-b357-b423e598eefa", "phaseId": "468a9913-6419-457c-a919-1469f119a2f0",

"value": 1.2039387175E-4

}, {

"indicatorId": "83a8f02b-8fe1-48a2-b357-b423e598eefa",


}, {

"indicatorId": "83a8f02b-8fe1-48a2-b357-b423e598eefa", "phaseId": "8759816a-98d6-469e-b4d6-4052bea0650e",

"value": 0.053528780187000004

}, { "indicatorId": "83a8f02b-8fe1-48a2-b357-b423e598eefa",


"value": 0.019097384000000002 }]

}

POST

/resources/MANUServiceModeler/blob/upload/{param1}/{param2}/{param3}/{param4}/{

param5} Upload of the proprietary (MaGA - LCPA) project file

Where:

IDProduct (IdPart)

TitleDocumentToBeUpload

FileNameToBeUpload

Description

Comment

GET

/resources/MANUServiceModeler/blob/download/{param1}/{param2}/{param3}/{param4

}/{param5} Download of the proprietary (MaGA - LCPA) project file

Where:

IDProduct (IdPart)

TitleDocumentToBeDownlaod

FileNameToBeDownlaod

Figure 3: Interface Flow chart

Copyright Manutelligence Consortium 2015-2018 Manutelligence N°636951

Sample

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

a/listproducts

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

a/listproducts?id=54216.39772.45328.39486

Confidential

Copyright Manutelligence Consortium 2015-2018 Page 20 / 25

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

ca/ebom?id=54216.39772.45328.39486&expand=0

Confidential


2.4.5 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) has been developed,

whereas the interface about telemetry data (Ferrari case) is in progress.

General rules

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


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.


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 https://webtest187.dmz.polimi.it:444/3dspace/resources/MANUServiceModeler/iss

ue/addissuejson

{

"Issue": {

"Id": "ID1",

"Type": "Issue",

"Description": "Value Description",

"Type_ReportedAgainst": "Part",

"Name_ReportedAgainst": "LFK01",

"Rev_ReportedAgainst": "1",

"attribute_EscalationRequired": "Yes",

"attribute_EstimatedStartDate": "06/08/2017",

"attribute_EstimatedEndDate": "06/08/2017",

"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",

Confidential


"ReportingOrganization": "Meyer",

"Policy": "Value Policy",

"Vault": "Value Vault",

"Owner": "Value Owner"

}

}

2.4.6 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 interface has the same structure also for the usage of the data related to the 3D printer of

Fablab.

General rules

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

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).

Confidential


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 their id.

Confidential


3 Conclusion

The Manutelligence standardization activities are focusing on the objective of interoperability

to maximize the impact of the project.

The methodology has been implemented in a pragmatic way to focus on the most important and

more useful standards and to take into account the requirements of the users of these standards,

here the Manutelligence software providers, who are developing the technological innovative

exploitable assets and integrating them in the Manutelligence platform.

The interest and completeness of the standards is proven in the Manutelligence industrial use

cases demonstrations. In addition, the adopted standards are in accordance with the current state

of the art.

Date post:	08-Apr-2018
Category:	Documents
Upload:	vodien
View:	221 times
Download:	1 times