Bridging the Gap between

System and Component Design

for Vehicle Electrification using
Model Based Systems Engineering
(MBSE)

Date : 17-18 May 2022

Agenda

Introduction

Challenges in Electric Vehicle development

Bridging the gaps through MBSE

How MBSE helped

TCS Enablers for MBSE

2
Introduction

TCS Confidential
Speaker Introduction

Yutika Patwardhan Neha Surjekar

Tata Consultancy Services Tata Consultancy Services
IoT & Digital Engineering IoT & Digital Engineering
Head of Centre of Excellence for FuSa, MBSE, Auto MBSE - Solution Lead, Auto Electronics Centre of Excellence
Electronics
• 20 +Years in Automotive Embedded Systems- (EV, ADAS, Body Electronics) • 12 + Years experience in Automotive Embedded Systems
• INCOSE CAB representative for TCS • Experience in MBSE (UML, SysML), ADAS, Body domain
• SME-Functional safety, Functional Safety L2 Certified by TUV SUD • Member INCOSE, INCOSE India Chapter
• Technical manager for BMS software, Project lead for modeling and simulation( E/E
• Tools Expertise - MBSE tool chains, SysML tools, Requirement Management,
features)
ALM tool chains
• Tools Expertise – MBSE tool chains, SysML tools, Safety Analysis tool chain,
Requirement Management, ALM tool chains • Key member in deploying MBSE practices across various accounts

• Certified Scrum Master

4
TCS Automotive Experience Summary

TCS recognized as a
Leader in ACES Automotive Engineering Services
by Everest Group

USA UK India South Korea

EE
Brazil Europe China Japan Architecture Safety &
Electrification Security
11,000+ Connected
Engineers Digital
7000+ Car Engineering
Electrical & Electronics Engineers
Working in
15+ Countries 4000+ Autonomous
Vehicle & Powertrain Engineers Vehicle
Spread across Driving
50+ Customers TCS Engineering

5
 TCS Automotive Electrical & Electronics Portfolio

Domains
Autonomous Driving Connected & Infotainment Electrification
EE Architecture Platform

Base Platform Diagnostics Cybersecurity Functional Systems

OS, AUTOSAR Safety Engineering

Hypervisor

Bootloader & FOTA

Challenges in Electric Vehicle Development

TCS Confidential
Automotive Trend - Vehicle Electrification – Challenges

Handling inter- disciplinary

teams

Faster time to market No systematic method

Increased complexity of Field failures,

vehicle features Vehicle re-calls

8
 Traditional Vehicle Electrification Development
Stakeholder Needs & Functional Specs

OEM Program Management

OEM E/E Architecture Team Tier1 Suppliers

E/E Architecture
Safety, Cybersecurity, Diagnostics specs

Component Design and

implementation

EV System Team System Requirements SW/HW/Mechanical Team

Test specifications and reports
& Architecture

Vehicle Integration & Validation Team

Complex system design and development need complicated cross-functional interaction

9
Bridging the Gaps through MBSE

TCS Confidential
Adaption of MBSE for Vehicle Electrification Development

OEM Program Management

Stakeholder Needs & Functional Specs

OEM E/E Architecture Team Tier1 Suppliers

E/E Architecture
MBSE Approach
Concept Ship to Market
Component Design and implementation

Design Test

Implement

System Requirements Test specifications and reports

& Architecture
EV System Team SW/HW/Mechanical Team

Vehicle Integration & Validation Team

System Engineering aims to ensure, the pieces work together to achieve the objective of the whole

11
Motor Control System Development using MBSE

Vehicle Context System Context *

HV Battery Current/Voltage
Battery Pack
Control Module Battery Current/Voltage

Braking
System Power Management System

HV
Motor Battery
Control Steering Traction Torque PWM
System Power Request Inverter
System HVAC Management Circuit
Accelerator Battery
System Accelerator Vehicle current/voltage
Inverter temp 3 Phase
Pedal Pedal Position Motor DC Voltage current
Body Control Motor Control Current
Driving Position Fail Status Control Motor
Control Unit
Management Sensor Motor Position
System (VCU) Motor Speed
System
Charging Information Motor Speed
Inlet Motor Temperature
Phase current

Driving Management System Motor Control System

Data Communication
High Voltage Line
* High level Representation of Motor torque control,
not an exhaustive architecture
Hardwired Connection
12
 MBSE applied to Motor Control System Development
Authoring System Requirements System Architecture & Req Allocation Sys Req to Architecture Traceability System Verification End – End Traceability
System
Sub-system

Authoring Sub Sys Requirements Defining Interfaces Sub Sys Architecture & Req Allocation Sub Sys Req to Arch traceability
Component

Component Requirements Authoring Software Requirements SW Architecture & Req Allocation Software Design & Implementation Stakeholder Views

13
How MBSE helped

TCS Confidential
 Benefits Seamless traceability:
EV Propulsion system requirements

Motor Control sub- system requirements

Motor, Motor control ECU detailed requirements, design

Gaps between System and
Component design Identified
before implementation

Stakeholder views for

OEM System team,
TCS team, Suppliers

Reduction in time
taken for adapting
MBSE
Classified and Precise
Information exchange
between OEM Team,
TCS team, Suppliers
15
TCS in MBSE

TCS Confidential
TCS in MBSE

8+ Customer INCOSE Working 10+ years of SysML

Engagements Group Contributor Cross-industry Experience

System Requirement Decomposition & Maturation

System Architecture & Design

Simulation of System Functional behavior

Integration of System Engineering & Functional Safety

Expertise in Multiple Tools & Tool Chain Integration

ADAS Body - Chassis Infotainment Powertrain Electrification

17
Thank you
Contact : [email protected]

Copyright © 2022 Tata Consultancy Services Limited

Authoring System requirements Toolbox used -
Simulink Requirements

Specify System requirements consistent with Stakeholder requirements, functional boundaries, functions, constraints, critical performance measures

19
System Architecture & Requirement Allocation

20
 Toolbox used -
System Composer

Data Communication
High Voltage Line

Identify system elements, interaction between them to satisfy the system requirements.

21
 Toolbox used -
System Composer

Establish “implements” relationship between architectural elements and requirements

22
System Req to System Architecture traceability Toolbox used -
Simulink Requirements

System
Architecture Element
System
Requirement

Establish and maintain traceability between System Requirements and System Architecture elements

23
Traceability

Show same traceability req

End to End traceability can be maintained. System<->Sub System<-> Software and component requirements

24
 Toolbox used -
Simulink Requirements

System
Requirement

Sub -System
Requirement

25
 Toolbox used -
Simulink Requirements

Sub - System
Requirement

Software
Requirement

26
Sub System requirements Authoring Toolbox used -
Simulink Requirements

Derive Sub system requirements from System requirements. Requirement writing guidelines help to author quality requirements

27
Defining Interfaces

28
 Toolbox used -
System Composer

Perform interface definition for defining the required interface and understanding of architecture.

29
 Toolbox used -
System Composer

Defined interfaces are represented using data dictionary

30
Sub System Architecture & Requirement Allocation

31
 Toolbox used -
System Composer

System Composer

Data Communication
High Voltage Line
Hardwired Connection

Define the stereotype and apply it on sub sys elements like block and connection, trace sub system elements to system elements

32
 Toolbox used -
System Composer

Data Communication
High Voltage Line
Hardwired Connection

33 TCS Confidential
 Toolbox used -
System Composer

Establish allocation relationship between architectural elements and requirements

34
Sub System Requirement to Architecture Traceability Toolbox used -
Simulink Requirements

Sub System
Architecture Block

Sub System
Requirement

35
 Toolbox used -
Component Requirements Simulink Requirements

36
Software Requirements Toolbox used -
Simulink Requirements

37
Software Architecture

38
39
40
Software Design and Implementation

41
System Verification

42
Stakeholder views System Composer

Hierarchical View

43
 System Composer

Hierarchical View

OEM
Perspective

Apply stereotypes to see the System views which can help OEMs to explain system from their perspective

44
 System Composer

Tier 1
Supplier
Perspective

Generate the sub system view to share precise information with the Tier1 Supplier

45
 System Composer

Motor
Vendor
Perspective

Generate the component view to share with the vendors

46
 System Composer

Hierarchical View

Motor
Specifications

Share the generated component specification along with the requirements with the vendor

47