0103 Presentation Neukirchen IBM

8/6/2019 0103 Presentation Neukirchen IBM

1/17

2009 IBM Corporation

Holistic PLM for the development of mechatronic systems

Proof of concept:Synchronized Mechatronics Engineering enabled by SOA

Dr. Gerd Oelerich IBM SWG, PLM SolutionsBernd Sartor IBM SWG ,PLM SolutionsHubert Aunkofer IBM SWG, RationalInes Merk IBM SWG, WebShpereMichael Buchholz PROSTEPFrank Weiblen IBM SWG, PLM Solutions


2/17

IBM Software Group | Lotus software

IBM Software Group Product Lifecycle Management

2

Challenges in development of mechatronics systemsand how to deal with

Challenges

Handle complexity

Ensure ability to innovate

Increase quality

Improve efficiency of developmentprocesses

Synchronize different lifecycles

Integrate different disciplines,cultures and organizations

Product

B1 B2 B3

F1

F2

AggregatesFunctions

Module

HW | SW | EE


3/17



3

Systems Engineering for development of mechatronicsystems compliant to requirements

Benefits through Systems Engineering:

From vertical towers to one system level

Synchronize communication, processes, methods andtools

Integration and reuse of deliverables

Systems Engineering principles:

Respects relations

and dependencies between elements

Integrates work products of

different development domains

to the synthesis of the whole system

Verification and validation of the system to ensure that

all requirements are met

Requirements

FunctionsSystem

Architecture

SoftwareSoftwareElectronicsElectronics

MechanicsMechanics

Test & Validation

Integration

Product/System


4/17



4

IterativeProcess V Process

V Process

MCAD E/E

HWAssets

SWDevelopment

Assets

EEAssets

SW Mgmt

???

The Solution Approach: Synchronized Change Process

Consistent rules andprocesses applied by allstakeholders

Overall status and processinformation available

Collaboration and sharing of

results

Traceability of artifacts andbusiness objects

Reuse of artifacts

Continuous validation againstrequirements on all systemlevels

Change Request

ECO

SW ECO

EE ECO

HW ECOECR

Approval

Process


5/17



5

The concept to integrative change within different development domains The concept for developing on a domain-comprehensive basis intends that the change request

on the system level is being broken down into requests for the particular domains

After the execution: the new baselines of the single domains are being aggregated to a newoverall baseline and the change request is being closed

StakeholderChangeRequest

Master OrderSystem

Baseline 1

System

Baseline 2

HW Order

E/E Order

SW Order

Baseline 1

HW Requirements

Baseline 1

E/E Requirements

Baseline 1

SW Requirements

Baseline 2

HW Requirements

Baseline 2

E/E Requirements

Baseline 2

SW Requirements

Requirement-Baseline 2

Requirement-Baseline 1

SW Baseline 1

E/E Baseline 1

HW Baseline 1

SW Baseline 2

E/E Baseline 2

HW Baseline 2


6/17



6

Advantages of the integration concept The state conditions within the domains facilitate synchronizing

the different development disciplines

ongoing visibility for easy monitoring

control on Gates or Milestones of the development process

Easy navigation into the processes and their work products at domain level end-to-end traceability Within the domains the, development follows specific procedure models and is being executed with

specific tools and data managers

The EC-interface delivers specific requirements and receives the work result that is relevant for thesynthesis of the complete system; sub-components and processes can be managed freely within thedomains

Developers use solely or predominately their standard tools

Master Order

HW Order

E/E Order

SW Order

Relational Design,CAD and VPLM

Design/Layout - Loops

Rational Unified Process,Activity Mgr and CM Tool


7/17



7

Synchronizing Engineering Changes in Mechatronics

Integration Architecture Overview

Team Data

SmarTeam

Mechanical

Authoring

ERP

Team Data

MatrixOne

ClearCase

ClearQuest

Master Order

HW Change Order

E/E Change Order

SW

Change Order

WAS/WID/WPSECRProcess

ECOManagement

Build Forge

E-CAD

System Level Integration Level

Application Level

BOMSoftware Authoring Electrical Authoring Mechanical Authoring

FederatedBOM

SWBOM

E/E

BOMMech.BOM


8/17



8

System Level - ENOVIA Reference architecture

BidirectionalPROSTEP

Adaplet(Web Services)

ENOVIA PROSTEP

Adaplet for OpenPDM


9/17



9

Using modular Web Services for theintegration of the SW domain

Modular Web Services have been developed which are

hosted by MatrixOne and ClearQuest resp. and are used indifferent phases of the scenario

check out and download files related toobjects

File service, check out

Upload and check in files, connect toobject

File service, Check in

Receives a new identification numberfrom the MOne numbering generator

Receive number

Connects objects through spec.relationshipConnect objects

Updates attributes of an existing objectUpdate Object

Creates an object in MOneCreate Object

MatrixOne

Update meta data of a recordUpdate record

Set the state of a recordSet record state

Link to recordsLink records

Provide state of a recordProvide record state

Create record of given typeSubmit record

ClearQuest

DescriptionMethod NameSystem


10/17



10

Integrating the mechanics domain We operate a Team Data Manager which is

ENOVIA SmarTeam for organizing the engineering procedures inthe mechanical domain.

The information flow towards SmarTeam goes through the IBMWebSphere Process Server and the ProSTEP OpenPDM gateway.

IBM WebSphere Process Sever OpenPDM


11/17



11

Scenario Overview

Analyse RequirementsSet up ECO structurePromote Master ECO

Perform transferof ECO andaffected part

OpenPDM

Navigate to affectedCAD models, perform

change,

Promote ECO,update ECO in ENOVIA

provide new BOM

Set up SW project,assign team,

RationalClearQuest

Perform changeBuild SW

RationalClearCase

Build Forge Promote ECO,update ECO in ENOVIA,

provide new SW part

RationalClearQuest

Check out schematics,Perform change,generate el. BOM

ECAD

Import el. BOM

Aggregate system BOM,transfer BOM to SAP,

complete ECOs

Incorporate materialmasters and BOM

SW ECO

EE ECO

Mech. ECO,Part


12/17



12

State display on system level

ECO state on

domain level

ECO state on

domain level


13/17



13

ECO in the mechanical domain system

A new ECO is created in thedomain data manager and

related information isattached.

A new ECO is created in thedomain data manager and

related information isattached.

A team leader can use thehyperlink to switch to the

system context.

.

A team leader can use thehyperlink to switch to the

system context.

.


14/17



14

ECO in the SW domain system

Again, a local ECO is initiated from thesystem level and related information is

forwarded to the SW configuration

management tool.

Again, a local ECO is initiated from thesystem level and related information is

forwarded to the SW configuration

management tool.

Requirements that were assigned tothe SW Change Order are forwarded

to the domain system for validating thedeliverables.

Requirements that were assigned tothe SW Change Order are forwarded

to the domain system for validating thedeliverables.


15/17



15

The federated BOM

Root nodeRoot node

Electricalparts

Electricalparts

Mechanicalparts

Mechanicalparts

SW partSW part


16/17



16

Values of a holistic Product Lifecycle Management in themechatronics engineering

Reduce development costs through process automation, flexibility andinter-domain collaboration

Accelerate development cycles through synchronization, faster feedbackand increased reuse of existing solutions

Increase product quality through

standardized development processes that ensure consistent resultsimproved reuse of approved assets

check and test results on all levels against initial requirements

Manage complexity through traceability and a single federated systemBOM

Protect and capitalize investments through leveraging of existing domainspecific knowledge and methodologies


17/17

2009 IBM Corporation

Thank You !

Documents

0103 Presentation Neukirchen IBM