WHY ALM AND PLM NEED TO COOPERATE. Jim Brogoitti, PLM Innovation Leader, General Motors

WHY ALM AND PLM NEED TO COOPERATE Jim Brogoitti, PLM Innovation Leader, General Motors

2 AGENDA Engineering Challenges at GM About GM & GM Global Electrical Systems Engineering Challenges The ultimate GM vision Summary Presentation based on Material jointly presented with IBM at Innovate2014

ENGINEERING CHALLENGES AT GM 3

GM GLOBAL ELECTRICAL SYSTEMS 11 DEVELOPMENT CENTERS

GM ELECTRICAL SYSTEMS FACE TO THE CUSTOMER

WHAT WE ACTUALLY PRODUCE

GM GLOBAL ELECTRICAL SYSTEMS ENVIRONMENT Dramatic increase in variation due to new propulsion systems and active safety Global diversity in legislative regulations Extreme economic and competitive pressures 3000 contributing engineers 300 hierarchical subsystems Thousands of variant features Millions of product instances per year Tens-of-thousands of unique product variants

GM ENABLES MASSIVE SW REUSE THROUGH PRODUCT LINES A Product Line is a set of systems sharing a common, managed set of features that are developed from a common set of core assets in a prescribed way Why Product Line over Products for GM Embedded Software? As much as an 85% reduction in effort for a second (third, fourth, etc.) application As much as a 70% quality improvement

MASSIVE SW PRODUCT LINES FACE TOOL CHALLENGES Change Management Ø Many products all wanting changes to the same assets Requirements Management Ø Many products with common and unique requirements People Management Ø Many products supported by central teams Deployment Management Ø Many products from the same pool of assets Configuration Management Ø Complex relationships between asset versions and product versions Data and Relationship Management Ø All the data and relationships of all the products combined Variation Management Ø All the variation of all the products combined WE REQUIRE A WORLD CLASS ALM SYSTEM!

OUR CONTRIBUTION

What we sell

GM IS AN AUTOMOTIVE OEM COMPANY OEM Original Equipment Manufacturer We are a manufacturing company 202,000 plus employees 396 facilities touching six continents 50 languages 23 time zones. $166.4 Billion in revenue (2016) 10 Million Global Deliveries (2016) 30,000 individual parts - one vehicle In this context GM Electrical Systems is a small piece of a large pie

Requirements Integrated PLM Tools Knowledge Gained Early Product Definition Design Refinement Tuning & Validation Manufacturing Sell & Service Constraints Engineering/ CAE Consistent Product Data Integrated Change Process 15

Major Initiatives Complex IT Systems Interactions Active Workspace Just. the right information, ALM Tools to the right people, at the right time. ERP TC-PLM 16

SO WHAT DOES THAT MEAN Change Management Ø Changes start in any system and are often resolved in more than one Requirements Management Ø Requirements interact with all systems People Management Ø People tend to work in one system, not multiple Deployment Management Ø Electrical deployments exist within mechanical deployments Ø Software deployments exist within electrical deployments Configuration Management Ø All the correct versions of all the engineering data are needed to define a product Variation Management Ø Variation starts at the system level and impacts all aspects of the system Data and Relationship Management Ø All the data and relationships of all the products combined

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

19 SO WHAT DOES THIS MEAN? We have non-integrated tools Systems Models and Requirements Software Development Electrical Circuit Board Design Wire Harness Design Mechanical Design We need a seamless ALM/PLM integration that bridges the development paradigms of the engineering competencies

OPEN SERVICES FOR LIFECYCLE COLLABORATION (OSLC) HOW LINKED DATA THROUGH OSLC CAN ENABLE THE SEAMLESS ALM/PLM INTEGRATION NEEDED BY GM 20

LINKED DATA: AN APPROACH TO INTEGRATION AND COLLABORATION ACROSS ENGINEERING DISCIPLINES Past Approaches to Integration Linked Data Approach to Integration 21 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

An Internet Inspired Architecture Leveraging the Linked Data concepts of Web Technology The Web has proven to be the most scalable, open, and flexible integration technology 22

23 A loosely coupled approach to integration Creating 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/designelement http://acme.com/mechanicalpart Requirement s Test s System design Wor k Item s Project plans EE design Mechanical design Source code

THE ULTIMATE GM VISION 24

NIRVANA SCENARIO 1 SEAMLESS DATA, OPTIMIZED TOOLS No difference between this Reqs CR Elec Mech SW PLM User Interface Prod Definition SW Config ALM User Interface Sys Test Unit Test Prod Config 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

NIRVANA SCENARIO 1 SEAMLESS DATA, OPTIMIZED TOOLS And this CR Reqs Elec Mech SW PLM User Interface Prod Definition SW Config ALM User Interface Sys Test Unit Test Prod Config 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

R e q s M e P c r h o d D e fi n Sit yi o s n T ep s r t o d C o n fi g C R E l e c S W S W C o n fi gu n it T e s t NIRVANA SCENARIO 2 THE REMOTE UPDATE CHALLENGE One hardware Validate build against (could have the few generation of these changes) + OS + Apps One OS with different Replace versions in this with the field a new version in the field User and App maker s Don t problem worry about these 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 data Is this data Up to 50 ECUs 100+ electrical components 1000s mechanical components 1000s build variants You can not Service updates explicitly Independent garages validate and Aftermarket parts track against all of these. Too many combination. Up to 50 BIOS Up to 50 OS Up to 50 SW Packages 1000s Calibration Parts Service Replace updates Independent garages These too + + App s some of this Aftermarket with a new parts versions in the field Have to worry about these, customers will expect them to still work (different expectations than a phone)

SUMMARY Developing modern vehicles is inherently complex Ø Massive data volume, huge challenges for parallel development and version and variant management Ø Complexity continues to rise Heterogeneous engineering environments are a reality Ø Best of breed tooling from multiple vendors Coordinating process and integration of data across multiple engineering disciplines is critical Ø Open data integration strategies are essential OSLC provides an open framework for integration across the engineering lifecycle Ø Key specifications for CM, RM and Product Structure provide necessary endpoints OSLC Tracked Resource Set(TRS) enables previously impossible views across the engineering lifecycle Ø Critical to unlocking engineering knowledge and coordinating engineering effort Continued involvement in shaping specifications and guiding implementation is required Ø Ø Ø GM and other customers have helped define this direction Current state and early implementations promise immediate ROI in key areas Achieving the nirvana vision will require continued collaborative effort the devil is in the detail!

THANK YOU!