System Lifecycle Management as a Bimodal IT Approach

Size: px

Start display at page:

Download "System Lifecycle Management as a Bimodal IT Approach"

Nathaniel West
6 years ago
Views:

1 System Lifecycle Management as a Bimodal IT Approach PDT EUROPE 2017, October 18 th 2017 Prof. Dr.-Ing. Martin Eigner Technische Universität Kaiserslautern Lehrstuhl für Virtuelle Produktentwicklung

Institute for Virtual Product Engineering (VPE)

Kaiserslautern 1968-1971 Toolmaker 1971-1976

Mechanical Engineering and Economy 1977-1980

Computer Applications in Design 1980-1985

IT and Organization 1985-2003 Eigner & Partner

Solution Provider for PLM Soutions Until 2001

the board and CTO since 2003 EIGNER Engineering

Lehrstuhl für Virtuelle Produktentwicklung 2009

0 und Information technology since 1992 since

2 Institute for Virtual Product Engineering (VPE) Professor Dr.-Ing. Martin Eigner Lehrstuhl für Virtuelle Produktentwicklung Technische Universität Kaiserslautern Toolmaker University of Karlsruhe (TH) Studies in Mechanical Engineering and Economy University of Karlsruhe (TH) PhD Institute of Computer Applications in Design Robert Bosch GmbH Head of Department Technical IT and Organization 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 Lehrstuhl für Virtuelle Produktentwicklung 2009 Awarded with UNICUM Germany`s Professor of the Year Award Lehre Plus of the University of Kaiserslautern for Industry 4.0 und Information technology since 1992 since 1999 University of Karlsruhe (TH) Visiting professor TU Sofia, Bulgaria Visiting professor 2017 // Lehrstuhl für Virtuelle Produktentwicklung Folie 2

3 PLM

4 SIM1 MCAD 1 MCAD 2 ECAD 1 ECAD 2 SIM2 SIM2 RM SysML, CASE DiFa Service The Vision: Traceability of Engineering Data all along the Product Lifecycle Requirements System Architecture Software Mechanic Electrics / Electronics Simulation / Test Digital Factory Service Enterprise Service Platform MRP/ERP MRP/ERP Engineering Backbone System Lifecycle Management (SysLM) MES Team Data Management MCAD TDM ECAD TDM Sim PDM Authoring Systems SysLM = PLM + ALM + SLM ALM PDM/PLM ERP/MES SLM Authoring Systems integrated via TDM Authoring Systems directly integrated TDM Systems OSLC / REST Technology API / Web-Service based Integration via Data Link or Exchange 2017 // Institute of Virtual Product Engineering Slide 4

5 SIM1 MCAD 1 MCAD 2 ECAD 1 ECAD 2 SIM2 SIM2 RM SysML, CASE DiFa Service Typical Challenges in Automotive Industry Requirements System Architecture Software Mechanic Electrics / Electronics Simulation / Test Digital Factory Service Enterprise Service Platform MRP/ERP MRP/ERP Engineering Backbone System Lifecycle Management (SysLM) MES Team Data Management Authoring Systems MCAD TDM ECAD TDM Sim PDM > 100 fragmented TDM / PDM and Authoring Systems + Excel and other hidden DBs ( Shadow IT ) Authoring Systems integrated via TDM OSLC / REST Technology Authoring Systems directly integrated TDM Systems API / Web-Service based Integration via Data Link or Exchange 2017 // Institute of Virtual Product Engineering Slide 5

6 SIM1 MCAD 1 MCAD 2 ECAD 1 ECAD 2 SIM2 SIM2 RM SysML, CASE DiFa Service Typical Challenges in Automotive Industry Requirements System Architecture Software Mechanic Electrics / Electronics Simulation / Test Digital Factory Service Enterprise Service Platform MRP/ERP MRP/ERP Engineering Backbone System Lifecycle Management (SysLM) MES Team Data Management MCAD TDM ECAD TDM Sim PDM Authoring Systems Harmonization Strategy only partially successful Authoring Systems integrated via TDM OSLC / REST Technology Authoring Systems directly integrated TDM Systems API / Web-Service based Integration via Data Link or Exchange 2017 // Institute of Virtual Product Engineering Slide 6

7 SIM1 MCAD 1 MCAD 2 ECAD 1 ECAD 2 SIM2 SIM2 RM SysML, CASE DiFa Service Typical Challenges in Automotive Industry Requirements System Architecture Software Mechanic Electrics / Electronics Simulation / Test Digital Factory Service Enterprise Service Platform MRP/ERP Engineering Backbone System Lifecycle Management (SysLM) A fully integrated Engineering Backbone does not exist (Exception: DAIMLER Smaragd comes close) MRP/ERP MES Team Data Management MCAD TDM ECAD TDM Sim PDM Authoring Systems Authoring Systems integrated via TDM OSLC / REST Technology Authoring Systems directly integrated TDM Systems API / Web-Service based Integration via Data Link or Exchange 2017 // Institute of Virtual Product Engineering Slide 7

8 SIM1 MCAD 1 MCAD 2 ECAD 1 ECAD 2 SIM2 SIM2 RM SysML, CASE DiFa Service Typical Challenges in Automotive Industry Requirements System Architecture Software Mechanic Electrics / Electronics Simulation / Test Digital Factory Service Enterprise Service Platform MRP/ERP MRP/ERP Engineering Backbone System Lifecycle Management (SysLM) High redundancy between all connected systems MES Team Data Management MCAD TDM ECAD TDM Sim PDM Authoring Systems Authoring Systems integrated via TDM OSLC / REST Technology Authoring Systems directly integrated TDM Systems API / Web-Service based Integration via Data Link or Exchange 2017 // Institute of Virtual Product Engineering Slide 8

SIM1 MCAD 1 MCAD 2 ECAD 1 ECAD 2 SIM2 SIM2 RM SysML, CASE DiFa Service Typical Challenges in Automotive Industry Requirements System Architecture Software Mechanic Electrics / Electronics Simulation

9 SIM1 MCAD 1 MCAD 2 ECAD 1 ECAD 2 SIM2 SIM2 RM SysML, CASE DiFa Service Typical Challenges in Automotive Industry Requirements System Architecture Software Mechanic Electrics / Electronics Simulation / Test Digital Factory Service Enterprise Service Platform MRP/ERP Engineering Backbone MRP/ERP Highly customized TDM / PDM System Lifecycle / PLM Management Systems (SysLM) demand re-customizing with each new release of the basic system MES Team Data Management MCAD TDM ECAD TDM Sim PDM Authoring Systems Authoring Systems integrated via TDM OSLC / REST Technology Authoring Systems directly integrated TDM Systems API / Web-Service based Integration via Data Link or Exchange 2017 // Institute of Virtual Product Engineering Slide 9

10 Gartner: Bimodal IT Not the one or the other but both in addition A lot of Criticism: Forrester: The False Promise of Bimodal IT Forbes: Gartner s recipe for disaster CIO Insight: Good bye Bimodal IT TechBeacon: Old Wine in New Bottles? Gartner Research s bimodal IT framework recognizes that traditional development practices are no longer sufficient for organizations with growing enterprise application demand. Instead, the bimodal IT strategy calls for two parallel tracks that support rapid application development for digital innovation priorities, alongside existing application maintenance and operational stabilization projects // Institute of Virtual Product Engineering Slide 10

Instead, the bimodal IT strategy calls for two parallel tracks that support rapid application development for digital innovation

11 Gartner: Bimodal IT Not the one or the other but both in addition Gartner Research s bimodal IT framework recognizes that traditional development practices are no longer sufficient for organizations with growing enterprise application demand. Instead, the bimodal IT strategy calls for two parallel tracks that support rapid application development for digital innovation priorities, alongside existing application maintenance and operational stabilization projects // Institute of Virtual Product Engineering Slide 11

12 The CIMdata Platform Approach Product Innovation Platforms: Definition, Their Role in the Enterprise, and Their Long-Term Viability CIMdata, Position Paper 2017 // Institute of Virtual Product Engineering Slide 12

What does this mean for PLM? From document-based to model-based (System Architecture becomes the driving Structure) Support of the full Product Lifecycle incl.

13 What does this mean for PLM? From document-based to model-based (System Architecture becomes the driving Structure) Support of the full Product Lifecycle incl. the Digital Twin From hierarchical (traditional BOMs) to networks (SysML) and linear structures (software). Support for Engineering Change Management (ECM) and Configuration Management (CM) for mechanic, electric / electronic and software design 2017 // Institute of Virtual Product Engineering Slide 13

14 What does this mean for PLM? From monolithic to federated and light weighted systems based on Model Based Repository and linked data technology (REST / RDF / OSLC and / or WEB services) Split of application data and meta data based on an Model based Repository means: agile implementation based on dramatically decrease of customization effort automatically upgrade even of customized applications (this is the absolute prerequisite for a SaaS Cloud Concept) Offering at different cloud levels (IaaS, PaaS und SaaS) Different levels of TDM / PLM and Authoring Systems integration (the challenge for Shadow IT) New flexible business models based on subscriptions instead of licenses 2017 // Institute of Virtual Product Engineering Slide 14

15 MBSE SYSTEM ARCHITECTURE AND THE DIGITAL MODEL

With horizontal integration the customer benefit will be 20+30% higher!!! Source: C.

16 Specification of Car Systems Complexity of Mechatronic and Cybertronic Systems: Problem: Vertical integration is defined but no horizontal integration. With horizontal integration the customer benefit will be 20+30% higher!!! Source: C. Huwig, J. Rambo: prostep ivip Sysmposium // Institute of Virtual Product Engineering Slide 16

17 Specification of Car Systems Complexity of Mechatronic and Cybertronic Systems: Problem: Vertical integration is defined but no horizontal integration. With horizontal integration the customer benefit will be 20+30% higher!!! Source: C. Huwig, J. Rambo: prostep ivip Sysmposium // Institute of Virtual Product Engineering Slide 17

New Business and Cooperation Models based on MBSE Standardized Data

Engineering Automotive System Architecture Communication along the Supply

Engineering-IT Standardisierung im Systems Engineering der frühen Phase,

18 New Business and Cooperation Models based on MBSE Standardized Data Exchange of Mechatronic System Architecture in the Early Phase of Systems Engineering Automotive System Architecture Communication along the Supply Chain via System Architecture Model System Model Based on: Julia Seeßle, Engineering-IT Standardisierung im Systems Engineering der frühen Phase, PhD Thesis, VPE // Institute of Virtual Product Engineering Slide 18

Supply Chain for Electronic, Software and Embedded

19 New Business and Cooperation Models based on MBSE Upper Level of System Architecture (OEM) Transfer along the Supply Chain for Electronic, Software and Embedded Systems 2017 // Institute of Virtual Product Engineering Slide 19

20 Authoring Systems Digital Model TDM and PLM / SYSLM MBSE: Digital Models along the Product Lifecycle Engineering Processes (ERM, ECM, CM, Data Exchange, ) Integration on TDM/PLM Level Integration on Authoring System Level 2017 // Institute of Virtual Product Engineering Slide 20

21 Aras Innovator The MBSE Integration into a PLM / SYSLM (2013/2014) MagicDraw T. Gilz, VPE // Institute of Virtual Product Engineering Slide 21

22 IOT AND IOS SERVICE ORIENTED BUSINESS MODELS AND DIGITAL TWIN

23 Scenario: Autonomous Construction Area 4.0 Requirements diagram Use Case System context Source: Eigner, M.; Schäfer, P.; Apostolov, H.; Tyagi, M.K.: Early Description and Simulation of Complex Mechatronic Systems Based on Methods of Model-Based System Engineering - at the Example of a Wheeled Excavator, CVT Symposium // Institute of Virtual Product Engineering Slide 23

Internal block diagram Source: Eigner, M.

: Early Description and Simulation of Complex

System Engineering - at the Example of a Wheeled

24 Scenario: Autonomous Construction Area 4.0 Autonomous Truck Loading (Communicating Systems) Internal block diagram Source: Eigner, M.; Schäfer, P.; Apostolov, H.; Tyagi, M.K.: Early Description and Simulation of Complex Mechatronic Systems Based on Methods of Model-Based System Engineering - at the Example of a Wheeled Excavator, CVT Symposium // Institute of Virtual Product Engineering Slide 24

Real World Real Product Digital Twin for Prototypes, Production and Service Virtual World Digital

R2c Product Line B Enterprise IoT Plattform (EIP) PTNz8c PT Ny9b PRnx1a PRny1a SNy1 a 1b SNx1 a

Prototype Twin Production Twin 100% Service Twins < 100% SNy1 a 2b 2c SNx1 a 1b 1c 1d PR =

25 Real World Real Product Digital Twin for Prototypes, Production and Service Virtual World Digital Model SysLM Digital Model and Digital Twin Product Line A PR = Product Release 150% PR R1a R2a R2c Product Line B Enterprise IoT Plattform (EIP) PTNz8c PT Ny9b PRnx1a PRny1a SNy1 a 1b SNx1 a 1b 1c 1d 2b? Prototype Twin Production Twin 100% Service Twins < 100% SNy1 a 2b 2c SNx1 a 1b 1c 1d PR = Product Release PT = Prototype PR = Production N = Number (Prototype/Serial) Feedback in Development with impact on the Digital Model 2017 // Institute of Virtual Product Engineering Slide 25

Digital Model & Digital Twin Digital Model Virtual representation of an existing physical product (evolves over time) Virtual World Digital Twin - Derived from one version of the Digital Model (less

26 Digital Model & Digital Twin Digital Model Virtual representation of an existing physical product (evolves over time) Virtual World Digital Twin - Derived from one version of the Digital Model (less than 100%) - Matches the state of the corresponding physical product Physical World Physical instances of the product (Digital twin tracks real-time sensor/field data, maintenance data, replaced parts, ) Not all of the complex PLM data is required (depends on when/where the Digital Twin should be used) Pred. PLM Succ. DT DT DT Digital Model Production Twin (as-built) Service Twin (as-maintained) 2017 // Institute of Virtual Product Engineering Slide 26

Digital Model & Digital Twin Digital Model Virtual representation of an existing physical product (evolves over time) Not all of the complex PLM data is required

Who is the Owner of the PLM Dig. Twin? Pred. Succ. Who is Stakeholder / User of the Digital Twin DT DT How is the Dig. Twin being reduced?

Virtual World Digital Twin - Derived from one version of the Digital Model (less than 100%) - Matches the state of the corresponding physical product Physical

27 Digital Model & Digital Twin Digital Model Virtual representation of an existing physical product (evolves over time) Not all of the complex PLM data is required Questions: (depends on when/where the Digital Twin should be used) Application Area? Use Case? Where is the Digital Twin located / saved? Who is the Owner of the PLM Dig. Twin? Pred. Succ. Who is Stakeholder / User of the Digital Twin DT DT How is the Dig. Twin being reduced? Temporary snapshot (disconnected PLM)? Context information needed: Position indicator Supplier Flat or structured? DMU needed? Virtual World Digital Twin - Derived from one version of the Digital Model (less than 100%) - Matches the state of the corresponding physical product Physical World Physical instances of the product (Digital twin tracks real-time sensor/field data, maintenance data, replaced parts, ) DT Digital Model Production Twin (as-built) Service Twin (as-maintained) 2017 // Institute of Virtual Product Engineering Slide 27

28 LIGHT WEIGHT BACKBONE SP²IDER REST / RDF SP2IDER = Semantic Product/Process Information & Digitized Engineering Repository

29 SP²IDER Level 1 (based on Model Based Repository and WEB Services) Graphical GUI with embedded WEB Services SP 2 IDER = Semantic Product/Process Information & Digitized Engineering Repository Graph Based Visualization vis.js Link Repository (WEB Services OSLC) 2017 // Institute of Virtual Product Engineering Slide 29

30 Graph-based Presentation of Affected Items for ECM Requirements Functions Logical Elements Items and Assemblies (BOM) Processes Tools and resources Documents Supplier 2017 // Institute of Virtual Product Engineering Slide 30

31 Schaeffler approaches and Solutions Source: Schaeffler AG 2017 // Institute of Virtual Product Engineering Slide 31

32 Schaeffler approaches and Solutions Source: Schaeffler AG 2017 // Institute of Virtual Product Engineering Slide 32

SP²IDER Level 2 (Linked Data and Web Technologies) Links instead of data exchange!

link") OSLC Open Services for Lifecycle Collaboration Based on the principles of Linked Data and REST Provides the required semantics in

expressing information about resource graphs, i.e. nodes and edges are stored as triples, transferred as RDF/XML, JSON-LD,.

33 SP²IDER Level 2 (Linked Data and Web Technologies) Links instead of data exchange! REST Representational state transfer: Access resources using stateless operations is encoded in the messages (as with URLs / "clicking a link") OSLC Open Services for Lifecycle Collaboration Based on the principles of Linked Data and REST Provides the required semantics in RDF Until now only a subset of ALM (RM) is standardized RDF The Resource Description Framework (RDF) is a semantical framework for expressing information about resource graphs, i.e. nodes and edges are stored as triples, transferred as RDF/XML, JSON-LD,. Source: open-services.net Abbreviations URI: Uniform Resource Identifier URL: Uniform Resource Locator, a kind of URI RDF: Resource Descriptor Framework 2017 // Institute of Virtual Product Engineering Slide 33

SP²IDER = Semantic Product/Process Information & Digitized Engineering Repository Lightweight realization of a SysLM Backbone Links instead of data exchange!

their capabilities in the Service Directory Communication and access of data via REST (use of OSLC semantics when ready) Representation of links to resources and objects in the source systems via RDF

34 SP²IDER = Semantic Product/Process Information & Digitized Engineering Repository Lightweight realization of a SysLM Backbone Links instead of data exchange! Service-oriented architecture: Everything (source systems, frontend) connects (as a client) via specific services to the SP²IDER Core (i.e. server) Clients provide specific services and register their capabilities in the Service Directory Communication and access of data via REST (use of OSLC semantics when ready) Representation of links to resources and objects in the source systems via RDF triples ( Graph-oriented DB) Storage of link data and object metadata in the Metadata Store SP²IDER Level 2 (Based on Linked Data) Source System-specific Service Client Client with Frontend-specific Service Web Frontend, Tablet, Mobile phone Service Directory Mappings Roles & Rights 2017 // Institute of Virtual Product Engineering Slide 34 ALM Plugin Client PDM REST RDF/JSON-LD/ Core Source System-specific Service API Metadata Store (database) REST RDF/JSON-LD/ Source System-specific Service Web Interface Client ERP Application Layer SysLM Layer Data Abstraction Layer Source Layer

Dynamic extraction of semantics from source systems based on user-defined metrics and heuristics No strict global schema of the data is enforced Vertical Mapping (different units, locale settings, )

35 Dynamic extraction of semantics from source systems based on user-defined metrics and heuristics No strict global schema of the data is enforced Vertical Mapping (different units, locale settings, ) source systems and SP²IDER Core is managed by the Source System-specific Services SP²IDER and Semantics Source System-specific Service Client ALM Plugin Client with Frontend-specific Service Web Frontend, Tablet, Mobile phone Service Directory Mappings Roles & Rights PDM REST RDF/JSON-LD/ Core Source System-specific Service Metadata Store (database) Source System-specific Service ERP REST RDF/JSON-LD/ Application Layer SysLM Layer Data Abstraction Layer Horizontal Mapping (correlating objects Web across source API systems) is created manually using a rule-based Interface Client Client approach (see Biztalk, Conweaver, ) Source Layer 2017 // Institute of Virtual Product Engineering Slide 35

36 Realization of a RDF- and Repository-based Backbone PLM Repository RDF Graph-based Visual Representation Why RDF? Trend to RDF for Enterprise Data Modeling Easy to generate Graph DB Prerequisite for OSLC access RESTful Web Service Architecture 2017 // Institute of Virtual Product Engineering Slide 36

37 From PLM Items to RDF Triples / Graph Nodes and Vice Versa <Item type="part" id="1ab34..."> <Relationships> Aras Relationship <Item type="part BOM" action="get"> <related_id> <Item type="part" id= "> </Item> </related_id> </Item> </Relationships> </Item> Aras AML representation <rdf:rdf <rdf:description rdf:about="aras://1ab34..."> <aras-mockup:partbom <1AB34...> <Part BOM> < > rdf:resource="aras:// "> </aras-mockup:partbom> //triple elements contain links to respective data </rdf:description> </rdf:rdf> RDF/XML representation Triple representation Graph-based Visual Representation Part BOM 1AB // Institute of Virtual Product Engineering Slide 37

Produktentwicklung (VPE) Gottlieb-Daimler Straße 44 67663 Kaiserslautern Tel.

38 Professor Dr.-Ing. Martin Eigner THANK YOU FOR YOUR KIND ATTENTION TU Kaiserslautern Lehrstuhl für Virtuelle Produktentwicklung (VPE) Gottlieb-Daimler Straße Kaiserslautern Tel.: +49 (0) Fax: + 49 (0) eigner@mv.uni-kl.de Höllhäuserweg 38 a // Baden-Baden Mobil: martin.eigner@eigner-ec.com

System Engineering with Aras Innovator

System Engineering with Aras Innovator Neptune Conference 28 th May 2015 1 Outline Who is Aras? System Engineering with Aras Demo - OSLC interoperability between PLM and ALM 2 Who is Aras? 3 3 Aras background