WHY ALM AND PLM NEED TO COOPERATE - icmhq.com · PDF fileWHY ALM AND PLM NEED TO COOPERATE ... “Just . the right information, to the right people, ... PLM User Interface ALM User

WHY ALM AND PLM NEED TO COOPERATE

Jim Brogoit t i , PLM Innovat ion Leader, General Motors

• EngineeringChallengesatGM• AboutGM&GMGlobalElectricalSystems• EngineeringChallenges

• TheultimateGMvision• Summary• PresentationbasedonMaterial jointlypresented

withIBMat Innovate2014

AGENDA

2

3

ENGINEERING CHALLENGES AT GM

GMGLOBALELECTRICALSYSTEMS11DEVELOPMENTCENTERS

GMELECTRICALSYSTEMSFACETOTHECUSTOMER

WHATWEACTUALLYPRODUCE

§ Dramatic increase in variation due to new propulsion systems and active safety

§ Global diversity in legislative regulations

§ Extreme economic and competit ive pressures

§ 3000 contributing engineers§ 300 hierarchical subsystems§ Thousands of variant features§ Mill ions of product instances

per year§ Tens-of-thousands of unique

product variants

GM GLOBAL ELECTRICAL SYSTEMS ENVIRONMENT

AProductLineisasetofsystemssharingacommon,managedsetoffeaturesthataredevelopedfromacommonsetofcoreassetsinaprescribedway

WhyProductLineover Products for GMEmbeddedSoftware?

§ Asmuchasan85%reductionineffortforasecond(third,fourth,etc.) application

§ Asmuchasa70%quality improvement

GM ENABLES MASSIVE SW REUSE THROUGH PRODUCT LINES

Change ManagementØ Many p roduc t s a l l want ing changes to the

s ame a s se t s

Requi rements ManagementØ Many p roduc t s w i th common and un ique

requ i rements

People ManagementØ Many p roduc t s suppor ted by cent ra l teams

Deployment ManagementØ Many p roduc t s f rom the s ame poo l o f a s se t s

MASSIVE SW PRODUCT LINES FACE TOOL CHALLENGES…

WE REQUIRE A WORLD CLASS ALM SYSTEM!

Configuration ManagementØ Complexrelationshipsbetweenassetversions

andproductversions

Data and Relationship ManagementØ Allthedataandrelationshipsofall the

productscombined

Variation ManagementØ Allthevariationofall theproductscombined

OUR CONTRIBUTION

What we sell

OEM– Original EquipmentManufacturerWeare a manufactur ingcompany

202,000plus employees396fac i l i t ies touchings ix cont inents50 languages23t imezones.

$166.4 Bi l l ion in revenue(2016)10Mi l l ionGlobal Del iver ies (2016)

30,000 indiv idual parts - onevehic le

In th is context GMElectr ical Systems i s a smal l p ieceof a largep ie

GM IS AN AUTOMOTIVE OEM COMPANY

Integrated PLM Tools

Integrated Change ProcessConsistent Product Data

Requirements

Constraints

Early Product

DefinitionSell &

ServiceManufacturing

Engineering/CAE

Knowledge Gained

Design Refinement

Tuning & Validation

15

TC-PLM

ERP

Active Workspace

Major InitiativesComplex IT Systems Interactions

ALM Tools“Just …. the right information,

to the right people,at the right time”.

16

Change ManagementØ Changes s ta r t i n any sys tem

and a re o f ten re so l ved i n more than one

Requi rements ManagementØ Requ i rements i n te rac t w i th

a l l sys temsPeople ManagementØ Peop le tend to work i n one

sys tem, no t mu l t i p l eDeployment ManagementØ E lec t r i ca l dep loyments ex i s t

w i th in mechan i ca l dep loyments

Ø So f tware dep loyments ex i s t w i th in e l e c t r i ca l dep loyments

SO WHAT DOES THAT MEAN…Conf igurat ionManagementØ Al l thecorrect versionsof

al l theengineer ingdataareneededtodef ineaproduct

Var iat ionManagementØ Variat ionstarts at the

systemlevel and impactsal l aspectsof thesystem

DataandRelat ionship ManagementØ Al l thedataand

relationshipsof al l theproductscombined

Requirements

R1

R2

R3

R4

R5

R6

R7

R8

R9

Rn

Logical

L1

L2

L3

L4

L5

L6

L7

L8

L9

Ln

Functional

F1

F2

F3

F4

F5

F6

F7

F8

F9

Fn

As Designed

D1

D2

D3

D4

D5

D6

D7

D8

D9

Dn

As Delivered

B1

B2

B3

B4

B5

B6

B7

B8

B9

Bn

As Ordered

O1

O2

O3

O4

O5

O6

O7

O8

O9

On

As Serviced

S1

S2

S3

S4

S5

S6

S7

S8

S9

Sn

Configuration Managed

Variant Managed

Changed Managed

Wehavenon-integratedtools• SystemsModels andRequirements• SoftwareDevelopment• Electr ical Circuit BoardDesign• WireHarnessDesign• Mechanical Design

WeneedaseamlessALM/PLMintegrationthatbridgesthedevelopmentparadigmsoftheengineeringcompetencies

SO WHAT DOES THIS MEAN?

19

HOW LINKED DATA THROUGH OSLC CAN ENABLE THE SEAMLESS ALM/PLM INTEGRATION NEEDED BY GM

20

OPEN SERVICES FOR LIFECYCLE COLLABORATION (OSLC)

LINKED DATA: AN APPROACH TO INTEGRATION AND COLLABORATION ACROSS ENGINEERING DISCIPLINES

Linked Data Approach to Integration

21

Past Approaches to Integration

§ Import/export workflow

§ One super DB schema

§ Always some tool/data “outside”

§ Semantic loss

§ Distributed internet architecture using standard internet technologies

§ Uses “http” to link to resources

§ Data is kept in native authoring tools

§ Scale and incrementally add tools

22

The Web has proven to be the most scalable, open, and flexible integration technology

An Internet Inspired ArchitectureLeveraging the Linked Data concepts of Web Technology

23

A loosely coupled approach to integrationCreating systems of tools where the whole is greater than the sum of its parts

http://acme.com/Requirement

http://acme.com/Test

http://acme.com/MechanicalPart

http://acme.com/DesignElement

Requirements

Tests

Mechanicaldesign

Work

Items

Systemdesign

EEdesign

Projectplans

Sourcecode

THE ULTIMATE GM VISION

24

NIRVANA SCENARIO 1 – SEAMLESS DATA, OPTIMIZED TOOLS

• Users operate in their optimal tool and UI• Data appears seamless regardless of storage• Data is linked based on engineering data relationships, not storage• All in real time

PLM ALM

CR

Reqs

SW

Elec

Mech

Unit Test

Sys Test

Prod Definition

Prod Config

SW Config

PLM User Interface

ALM User Interface

No difference between this

NIRVANA SCENARIO 1 – SEAMLESS DATA, OPTIMIZED TOOLS

• Users operate in their optimal tool and UI• Data appears seamless regardless of storage• Data is linked based on engineering data relationships, not storage• All in real time

PLM ALM

CR

Reqs

SW

Elec

Mech

Unit Test

Sys Test

Prod Definition

Prod Config

SW Config

PLM User Interface

ALM User Interface

And this

One hardware build(could have generation changes)

NIRVANA SCENARIO 2 – THE REMOTE UPDATE CHALLENGE

+ OS Apps+One OS with different versions in the field

User and App maker’s problemReplace this

with a new version in the field

Validate against the few of these

Don’t worry about these

• Up to 50 ECUs• 100+ electrical components• 1000s mechanical components• 1000s build variants• Service updates

• Independent garages• Aftermarket parts

• Up to 50 BIOS• Up to 50 OS• Up to 50 SW Packages• 1000s Calibration Parts• Service updates

• Independent garages• Aftermarket parts

+ Apps+

These too

Replace some of this with a new versions in the field

You can not explicitly validate and track against all of these. Too many combination.

Have to worry about these, customers will expect them to still work (different expectations than a phone)

Cross domain analysis is the only way to get here• Managed compatibility• Query the car to figure out what it really is• Query the data to figure out what the correct

update is• Apply the update

Query the dataIs this data

C

R

R

e

q

s

S

W

E

l

e

c

M

e

c

h

U

n

i t

T

es

t

S

y

s

T

es

t

P

r

o

d

De

fi

n

i t

io

n

P

r

o

d

Co

n

fi

g

S

W

C

o

nfi

g

Requirements

R1

R2

R3

R4

R5

R6

R7

R8

R9

Rn

Logical

L1

L2

L3

L4

L5

L6

L7

L8

L9

Ln

Functional

F1

F2

F3

F4

F5

F6

F7

F8

F9

Fn

As Designed

D1

D2

D3

D4

D5

D6

D7

D8

D9

Dn

As Delivered

B1

B2

B3

B4

B5

B6

B7

B8

B9

Bn

As Ordered

O1

O2

O3

O4

O5

O6

O7

O8

O9

On

As Serviced

S1

S2

S3

S4

S5

S6

S7

S8

S9

Sn

Configuration Managed

Variant Managed

Changed Managed

Develop ing modern veh ic les i s inherent ly complexØ Mass i ve data vo lume , huge

cha l l enges fo r pa ra l l e l deve lopment and ve rs ion and va r i ant management

Ø Complex i t y cont inues to r i s eHeterogeneous eng ineer ing env i ronments are a rea l i tyØ Bes t o f b reed too l i ng f rom

mu l t i p l e vendorsCoord inat ing process and integrat ion of data across mul t ip le eng ineer ing d i sc ip l ines i s cr i t i ca lØ Open data i n teg rat ion

s t ra teg ie s a re e s sent i a l

SUMMARY

OSLC p r ov i de s an open f r amewor k f o r i n t e g r a t i on a c r o s s t he eng i nee r i n g l i f e c y c l eØ K e y s p e c i f i c a t i o n s f o r CM , RM a n d

P r o d u c t S t r u c t u r e p r o v i d e n e c e s s a r y e n d p o i n t s

OSLC T r a c ked Re sou r ce Se t ( TRS ) enab l e s p r e v i ou s l y impos s i b l e v i ews a c r o s s t he eng i nee r i ng l i f e c y c l eØ C r i t i c a l t o u n l o c k i n g e n g i n e e r i n g

k n ow l e d g e a n d c o o r d i n a t i n g e n g i n e e r i n g e f f o r t

Con t i nued i n vo l v emen t i n shap i ng spe c i f i c a t i on s and gu i d i ng imp l emen ta t i on i s r equ i r edØ GM a n d o t h e r c u s t om e r s h a v e

h e l p e d d e f i n e t h i s d i r e c t i o nØ C u r r e n t s t a t e a n d e a r l y

i m p l em e n t a t i o n s p r om i s e i mme d i a t e RO I i n k e y a r e a s

Ø A c h i e v i n g t h e n i r v a n a v i s i o n w i l l r e q u i r e c o n t i n u e d c o l l a b o r a t i v e e f f o r t – t h e d e v i l i s i n t h e d e t a i l !

THANK YOU!