Federated and link-based System Lifecycle Management · PDF filefor „Industry 4.0“...

ProSTEP iViP Symposium 2017

Federated and link-based System Lifecycle Management (SYSLM) as Backbone of interdisciplinary Engineering Processes

Essen // Mai 18th, 2017

Prof. Dr. Martin Eigner, Thomas Eickhoff, Thomas PsotaTechnische Universität KaiserslauternLehrstuhl für Virtuelle Produktentwicklung

© Institute of Virtual Product Engineering // 2017 Slide 2

Professor Dr.-Ing. Martin EignerLehrstuhl für Virtuelle Produktentwicklung

Technische Universität Kaiserslautern

1968 - 1971 Toolmaker

1971 - 1976 University of Karlsruhe (TH)

Studies in Mechanical Engineering and Economy

1977 - 1980 University of Karlsruhe (TH)

PhD Institute of Computer Applications in Design

1980 - 1985 Robert Bosch GmbH

Head of Department Technical IT and Organization

1985 - 2003 Eigner & Partner GmbH, AG, Inc.

Solution Provider for PLM Soutions

Until 2001 chief executive office

Until 2003: chairman of the board and CTO

since 2003 EIGNER Engineering Consult

since 2004 University of Kaiserslautern

Institute of Virtual Product Engineering

since 1992 University of Karlsruhe (TH)

Visiting professor

since 1999 TU Sofia, Bulgaria

Visiting professor

Institute of Virtual Product Engineering (VPE)

2009 Awarded with

UNICUM Germany`s Professor of the Year 2009

2014 Awarded „Lehre Plus“ award of the University of Kaiserslautern

for „Industry 4.0“ und „Information technology“

http://www.fck.de/

http://vpe.mv.uni-kl.de/lehrstuhl/lehrstuhlinhaber/

http://www.uni-kl.de/

https://twitter.com/LehrstuhlVPE

https://www.xing.com/profile/Martin_Eigner

https://de.linkedin.com/pub/martin-eigner/6/993/759

https://www.facebook.com/LehrstuhlVPE

http://link.springer.com/book/10.1007/b93672

http://link.springer.com/book/10.1007/978-3-642-24893-1




http://link.springer.com/chapter/10.1007/978-3-662-48278-0_9

https://vpe.mv.uni-kl.de/lehrstuhl


Das Buch zum Forschungsprojekt mecPro² „Dieses Buch befasst sich mit der fortschreitenden Digitalisierung, die in

der Produktion (Industrie 4.0), aber auch im Engineering vorangetrieben werden muss, um immer komplexere Produkte sowie deren Herstellung planen und verwirklichen zu können. Wichtigster Faktor für Unternehmen wird der Umstieg von einer dokumentenzentrierten zu einer modellbasierten Entwicklung sein. …“

ISBN

− Print: 978-3-662-55123-3− Ebook: 978-3-662-55124-0

Erhältlich auf Springer Link https://link.springer.com/book/10.1007/978-3-662-55124-0

Latest Publication

https://link.springer.com/book/10.1007/978-3-662-55124-0

https://link.springer.com/book/10.1007/978-3-662-55124-0


Evolution Towards Digitized Engineering

System LifecycleManagement(SysLM)

SysLMWeb

technologiesSysLM

BackboneSP²IDER


Vision: Digital Models Along the Product LifecycleAu

thor

ing

Syst

ems

TDM

and

PLM

/SYS

LM

Integration on Authoring System Level

Integration on TDM/PLM Level

Dig

ital M

odel

The Digital Thread (Traceability)

Engineering Processes (ERM, ECM, CM, Data Exchange, …)


From Document- to BOM-centric to Model-Based Design

Document and BOM centric Digital Model and Digital Twin

Hierarchical StructuresMechanic is dominant

Hierarchical, linear und network oriented StructuresMechatronic and Software is dominant

M. Eigner, C. Muggeo, M. Pfenning


The Hierachical BOM is not Able to Trace SW

Mechanics

…

Airplane

Wing

Hydraulic

Electronic

Software

PCB

Landing Gear

………

Manuals

…..

Purchased Assy

Sensor

AML / AVL

Electric

Landed

ReverseEngine

Aileron

BOM shows the physicalrelationships

Behavior Diagram shows thefunctional relationship

We need both of them!!!


Software Configurations Management (SCM)

− Optimized for the Management of Source Code + additional documents

− Branching, Tagging (Baseline), Merging

Product Data Management (PDM)

− Optimized for the Management of BOMs( hierarchical Objects) + additional documents

− Managed Items are belonging to Hardware and have Life Cycles

− Change Management for Items and BOMs based on rules

System Architecture Management (and Process Plan and BPMN)− Combination of Hierarchy and Network

− Intelligent Information: Ports, with Flow of Energy, Material, Information,…..

Different Processes for System Architecture, HW and SW

1.1

1.2

1.3

1.1

1.2

1.3

Element A Element B

1.1

1.2

1.3

Element C

Zeit

Ba

selin

e 1

.1


Managing SysML Models Based on Adapted ECM

FPD model is partial model inside a SysML model in a CASE tool and managed in Team Data Management (TDM) tool PLM backbone controls FPD model items after commit

FPD model under TDM control

FPD model under PLM control

1 4

4.1

5 6 8 9

A

4.2

A

107

branch

trunk

masterB

2 3 1

prelimnary released

In c

han

ge

A1

released

11 12 132 3

4.3

A2SysLMID 5456

ElementID 12356

Team Data Management(ALM/TDM)

Product/Appication Lifecycle Management

(PLM)Marc

(System Architect)

Jule(System Engineer)

Philipp(System Engineer)

review

Source: VPE Research Project mecPro² (T. Gilz)


Types of SysML (and all MBSE) PLM Integrations

Direct Integration 3 Layer, Simple TDM 3 Layer, ext. TDM

AuthoringSystem

Trend: Higher Intelligence of Authoring Tools Onshape

C. Muggeo


Integration of Intelligent (Database Oriented) Authoring Systems

Versioning and History as part of

Authoring Systems


Integration Technology Alternatives

1. Physical Data Exchange

• Data transfer of all systems to PLM-Cockpit (sync.)

• e.g. STEP AP242XML

• Redundant data which has to be synchronized

• High maturity, but extremely big data amount

• Less future sustainability because of high amount of systems to be integrated

2. Model based Repository

• Physical management of external objects and attributes in subsystems possible

• Integration of WEB Services passive und active

• High maturity in industrial usage

• Logic of modern repository based PLM Systems

• High future sustainability with option to switch over to solution 3

3. Fully linked Data Model based on REST Technology

• Linking in all subsystems currently only with proprietary Interfaces possible high license costs expected

• Currently no OSLC Standards for PLM available (up to now only for parts of ALM)

• No central repository

• No maturity for industrial use (currently content of research and standardization panels)

Maturity and Industrial Use

DRemember yesterday‘s talk?

Bimodal

PLM Cockpit Technology

OPEN Standards and

Web Technologies

SysLMWeb

technologiesSysLM

BackboneSP²IDER


Links instead of data exchange!

REST – Representational state transfer: Access resources using stateless operations, everything neededis encoded in the messages (as with URLs / "clicking a link")

OSLC – Open Services for Lifecycle Collaboration− Provides the required semantics− Based on the principles of Linked Data

− Use URIs as names for things− Use HTTP URIs so that people can look up those names.− When someone looks up a URI, provide useful information,

using the standards (RDF*, SPARQL)− Include links to other URIs. so that they can discover more things.

Open Standards and Web Technologies

Source: wikipedia

Abbreviations:URI: Uniform Resource IdentifierURL: Uniform Resource Locator, a kind of URIRDF: Resource Descriptor Framework


RDF− “The Resource Description Framework (RDF) is a framework for expressing information about

resources.”− Graphs, i.e. nodes and edges …

− … are stored as triples, transferred as RDF/XML, Turtle

Summary− Store links to ressources and relationships as RDF − Access the data via REST web services

RDF and all the REST of it

Source:W3C

B

DA

Cf

f g

g

<A> <f> <B><A> <f> <C><B> <g> <D><C> <g> <D>


From PLM Items to RDF Triples / Graph Nodes

Aras Relationship

<Item type="Part" id="1AB34..."><Relationships>

<Item type="Part BOM" action="get"><related_id>

<Item type="Part" id=“9876..."></Item>

</related_id></Item>

</Relationships></Item>

Aras AML representation

<rdf:RDF<rdf:Description rdf:about="aras://1AB34...">

<aras-mockup:PartBOMrdf:resource="aras://9876..."></aras-mockup:PartBOM>

</rdf:Description></rdf:RDF>

RDF/XML representation

<1AB34...> <Part BOM> <9876...>

//triple elements contain links to respective data

Triple representation

1AB34… 9876…Part BOM

Visual Representation


Umwandlung Relation in RDF Tripel

Z_ID Z_Name Z_Telefon Z_Email

1 Schrauben24 +49 1234 56789 [email protected]

2 Super Schrauben +49 0987 654321 [email protected]

3 Nuts and Bolts +1 555 1337 [email protected]

S_ID S_Bezeichnung

1 M5x10 – 8.8

2 M6x20 – 8.8

3 M8x60 – 6.8

4 M8x60 – 8.8

Z_ID S_ID

1 1

1 2

2 1

2 2

2 4

3 3

Relation „Zulieferer“

Relation „bestellbar“

Relation „Schraube“

Relationale Darstellung

RDF Tripel


Graph Darstellung

Syslm Backbone-Konzept

SysLMWeb

technologiesSysLM

BackboneSP²IDER


Level 2



















Bimodal



Realization of a Graph- and Repository-based ECMResearch Project VPE University of Kaiserslautern

Graphical GUIwith embedded

WEB Services

Graph BasedVisualization

Link Repository (WEB Services OSLC)

vis.js


Current Visualisation and Search

Disruptive Changes of the Technical IT Infrastructure through Engineering 4.0 | Dr. Fabrice Mogo Nem und Prof. Martin Eigner

SP²IDERSemantic Product & Process Information and Digital Engineering Repository

SysLMWeb

technologiesSysLM

BackboneSP²IDER


Towards Level 3



















Bimodal



Lightweight realization of a SYSLM Backbone

Everything (source systems, frontend) connects (as a client)to the SP²IDER Core (i.e. server)

Clients register their capabilities in the Service Directory

Communication via REST (use OSLC semantics when ready)

Data about objects in the source systems is stored in theMetadata Store (RDF)

SP²IDER

PDM

Client

ERP

Client

ALM

Client

Service Directory

Core

Service Directory---------------------------------------------------------------------

Metadata Store

Web Frontend

Client

Communication via REST


In theory, SP²IDER can be very lightweight

However, for many use cases this would require reinventing the wheel( Model Based Repository)

Use Aras Innovator as a metadata store, gain access to existing PLM intelligence Engineering WorkflowsMapping Rules

Aras als Metadata Store

Aras Innovator


Mapping between source systems is non-trivial

Web Frontend will provide an appropriate User Interfaceto create (manual and algorithmic) mapping rules

Everything old is new again – Biztalk

Mapping Between Source Systems

Source: Microsoft / BizTalk

E-BOM from Windchill M-BOM from SAP

1AB34…

Part

C0FF…

2

33245…

4711…

Part

4711

2

0815…

Mapping


Service

MCAD TDM

Digital FactorySystem Architectur Simulation/TestElectrik/ElektronicMechanicSoftwareRequirements

MRP/ERP

Team Data

Management

Authoring

Systeme

MRP/ERPR

M SysM

L, …

CASE

MCA

D 1 D

iFa

MCA

D 2

ECA

D 2

SIM

2

ECAD TDM

Sim PDM

ECA

D 1

SIM

2

System Lifecycle Management (SysLM)

Engineering

Backbone

Serv

ice

Enterprise Service

Platform

SIM

1MES

Authoring Systems via TDM integrated TDM SystemsAuthoring Systems direct integriert

OSLC / REST Technology API/Web Servic based Integration via Data Link or Exchange

RDF Semantic as basis for a REST approach

SYSLM 2017 // @LehrstuhlVPEBusiness of Engineeringam 10. und 11. Oktober 2017 // Kaiserslautern

#SysLM2017


Professor Dr.-Ing. Martin Eigner

TU Kaiserslautern Lehrstuhl für Virtuelle Produktentwicklung (VPE)

Postfach 304967653 KaiserslauternGottlieb-Daimler Straße 4467663 Kaiserslautern

Tel. +49 (0) 631 - 205 3873Fax: + 49 (0) 631 - 205 3872

[email protected] http://vpe.mv.uni-kl.de

Vielen Dankfür ihr Interesse!

http://vpe.mv.uni-kl.de/lehrstuhl/lehrstuhlinhaber/

https://www.xing.com/profile/Martin_Eigner

https://de.wikipedia.org/wiki/Martin_Eigner

https://de.linkedin.com/pub/martin-eigner/6/993/759

https://www.facebook.com/LehrstuhlVPE

Date post:	11-Feb-2018
Category:	Documents
Upload:	lamdien
View:	212 times
Download:	0 times

Federated and link-based System Lifecycle Management · PDF filefor „Industry 4.0“...

Documents