- the integration challenge€¦ · marketing and jvs apac operations group trucks sales &...

Volvo Group Trucks Technology

Vehicle Engineering - Peter Thorngren 1

“The Epic Split” of Software and Platform - The Integration Challenge

5/23/2014


Volvo Group

Group Trucks Sales &

Marketing and JVs APAC

Group Trucks Operations


Marketing Americas


Marketing EMEA

Group Trucks Technology

Volvo Financial Services

Business Areas

Construction Equipment

Vehicle Engineering - Peter Thorngren 2 5/23/2014


Technology, Product & Sourcing & Steering Comittees

Group Trucks Technology for the Volvo Group

Volvo Group Trucks

Technology

Advanced Technology & Research

Range & Projects Management

Vehicle Engineering

Global Product Planning

Purchasing - Direct & Indirect material and services

Complete Vehicle

Powertrain Engineering

External Customers (outside Volvo Group)



(1991-93) Banking – payment systems •SWIFT (Big data – financial services messaging)

(1994-2003) Internet and Agency (Business-to-Business) •Boplats, Telia.se, Hemnet and Blocket (Web portals)

(2004-07) Telecom – Smart Phones •Microsoft, Palm, Embedded Linux and windows Mobile

(2007- today) VOLVO

Integration and verification of the

complete electrical engineering system

About the Presenter… Background…



Automation

Online Mobility

Transport Needs

5

Megatrends in Our Future

Vehicle Engineering - Peter Thorngren 5/23/2014


6

Truck of the year 2024?

Vehicle Engineering - Peter Thorngren

TRUCK OF THE YEAR 2024?

5/23/2014


7

Possible criteria's… for Truck of the Year 2024

Todays criteria +

Road trains - platooning

Extreme fuel efficiency

focus

Cross docking Green corridors

– Electro mobility

Automated driving

Vehicle to X communication

+Things we don't know today,

that will exist then!



Functional and logical glue of the

Truck

Truck2x

Chassis

Powertrain

Human machine Interface

Cab

Safety

8

The Role of the Electrical System in a Truck



Features/ Customer REQ

System Requirements

Component Requirements

V-model in an iterative way


… in theory

5/23/2014

Volvo Group Trucks Technology Vehicle Engineering - Peter Thorngren 10 5/23/2014


Hardwire Connection IF

Design Architecture

Feature Architecture

Diagnostic Architecture

HW Architecture (BIHA)

Dom

ain

Targ

et A

rchi

tect

ure

(DBT

A) s

impl

e

Tent

ativ

e Al

loca

tion

Targ

et (I

TTA)

0..1

General Allocation Target (JGNO)

HW Sub Element (DBHP/ ITHP)

0..1

Tentative Allocations (DBDA)

FDA Allocation (ITDA)

0..1

*

HW Contents (DBHD)

HW Content (ITHD)

Realizes Generic Target (DBDN/ ITDN)

HW Element (BIHE)

*

Domain Allocation (BIAD)

Domain Allocation (ITDS)

Domain Allocations (DBDS) simple

*

Vehicle Architecture (3PTA)

Vehicle Design Architecture (3ADA/3VDA)

E2E Functions (RBFN)

E2E Function list (3PFL)

0..1 Collaborations (DBCD)

E2E Functions (3EFS)

E2E Function (3PEN) *

*

Real

ized

E2E

Func

tion

(3E2

F)

Vehicle Function List (3AFL)

E2E Function List (3EFL)

LDA list element (BISG)

Functional Component (ITFC)

ApplicationComponents (DBAP/ ITAP)

Functional Content (DBFD)

Functional Content (ITFD) 0..1

Functional Components (DBFC)

Allo

catio

n So

urce

(ITF

S)

0..1

Dom

ain

Sour

ce A

rchi

tect

ure

(DBF

S) S

impl

e

Collaboration (ITCO)

Abstract LDA (BISP)

LDA (BIDA)

Logical Component (ITSC)

Logical Components (DBSC)

0..1

Node Content (DBLD)

Node Content (ITLD)

Collaboration (BICO)

Abstract Logical Comp (BISC)

SensAct SoftwareComp

(BIDC)

Application SoftwareComp

(BIAC)

*

Composition SoftwareComp

(BICC)

Design Architecture

(BIVD)

RAT (BINA)

Node Channels (ITNC)

Logical BasicComp

(BIBC)

Vehicle Document List (3VDS)

Fault Symptom list Element (3GDL)

Fault Symptom List (3VFL) 0..1

Fault Symptom (3GDS)

Symptom (3GST)

Fault Symptoms (3GFS)

Possible Causing Functional Fault (3GFF)

Functional Fault (3GDF)

Vehicle Fault Symptom List (3VSS)

Asso

ciat

ed E

nd-T

o-En

d Fu

nctio

n (3

GCC

)

*

Communication (3VDA)

Approved Signals (3VDA)

Context Free Requirements (3CFR)

Local Requirement (IBAR)

Component Responsibility

(3REY)

Functional Requirement

(RFRQ)

Configurability Requirement

(3PCR)

Supportability Requirement (3PSR)

Maintainability Requirement

(3PMR)

...

* Associated Logical Component (3GLD)

Associated Logical Component s (3GFL)

Hardware Architecture

Abstract Design Function (BIDF)

Use Case (JUSC)

Signal IF

Realized E2E Functions (3RE2)

TEA2+

00 Architectures and Baselines

Product Definition Meta data model


Product data repository

5/23/2014


Why?


x Integration – the assembly line combining software with the rest of the truck

x Verification – the crash test of software from drivability and maintainability perspective



TEA2+ – Cab

Each with ~20.000 selectable parameters, messages and functions as possible choices


Hardware Architecture

Rig Architecture

Implementation Architecture (a.k.a. HW/SW model)

Real SW Element (3SWE, parent: RIAR)

- KOLA variant ID (3KOL) - Supplier ID (3SUP) - V3P Part Number (3IID) - Release Name (3REL) - SW Type (3SWT)

Real HW (Release) (3RHW, parent: RIAR)

- Release Name() - Release Type ()

Real SW Build (3SWR, parent: 3REE)

Real HW Build (3RHB, parent: 3REE)

Real Builds (3RBA, parent:3REE)

Network Release (3LIN, parent: RIAR

Real HW Element (RHRW, parent: RIAR)

- KOLA variant ID (3KOL) - Supplier ID (3SUP) - V3P Part Number (3IID) - Release Name (3REL) - Maturity Level (3PML) - Maturity Level Version (3PMV)

Real SW (Release) (3SWR, parent: RIAR)

- Release Name() - Release Type ()

DA IF

HW Architecture (BIHA)

Tent

ativ

e Al

loca

tion

Targ

et (I

TTA)

0..1

HW Sub Element (DBHP/ ITHP)

0..1

HW Content (ITHD)

HW Element (BIHE)

*

Abstract Hard Wire Connection

(CBHW, parent: CN)

Real Artifacts (RIAR, parent: AAR)

Abstract Rig HW (3ARH, parent: RIAR

Real Rig (3ARG parent:RIAR)

Real Rig HW (3RRH, parent: 3ARH)

Real Interface Box (3RIF, parent: 3ARH)

CanCASE (3CCA, parent: I)

Rig Control PC (3CPC, parent: I)

- ID (ABII) - LicenseBits (3LIC)

- ID (ABII) - CANoe Version 3CAO - SE-tool Version 3SEV)

IF Box Pin (3IBP, parent: I)

IF Box Design (3IFD, parent: I)

Test Setup (3IBC, parent: I)

PLC (3PLO, parent: I)

Rig Function Group (3RFG, parent: I)

- PLC Version (3PLC)

RFG Signal (CBRS, parent: CBAS)

I/O Buffer (Name) (3BUF, parent: I)

- Direction (3R17)

- Direction (3R17)

- Sahara slot so (3R22) - Sahara channel no (3R23) - Sahara type (3R01) - Beckhoff I/O terminal no (3R04) - Beckhoff I/O terminal type (3R02) - Beckhoff terminal channel no (3R05) - LED threshold voltage (3R18) - LED activation (3R19) - LED inverting (3R20) - Short circuit protection (3R07) - Real/simulator switch protection (3R06) - DRP0 Short circuit to +BAT (3R21) - DRP1 Short circuit to -BAT (3R24) - DRP2 Real switch (3R25) - DRP3 Simulated switch (3R26)

Abstract HW (AHW, parent: I)

Rig HW Element (RHWE, parent: AHW)

Abstract System (3ASY, parent: RIAR

Real System (3RSY, parent: 3ASY)

ECU Pin (Name) (3RCH, parent: RHWE)

- Pin Number (3R10) - Pin Type (3ept)

Real Node (3RNO, parent: 3ASY)

ECU Specification (3RIB, parent: RHWC)

- EE_Package (3fun)

ATA

Test Architecture

Test Suite (JBTE, parent: I)

Test Specification (JTSP, parent: I)

- Test Description Level (3PTL) - Test Sub Level (3PSL) - Test Type (3PTT) - Development Status (DEST)

Test Scope (JTSD, parent: I)

- Development Status (DEST)

Test Case (JTCS, parent: I)

- Test Sequence List (TSQL)

- Development Status (DEST) - Vehicle Modes (3PVM) DA IF

Test (JSES, parent: I)

- Test Sub Level (3PSL) - Test Type (3PTT)

Product Test and Verification Meta Model



5/23/2014


Modeling in Integration



17

Distributed Functions in many ECU:s driving Integration Complexity

1. Age of the Cable

2. Age of the ECU

3. Age of the Service

Unnecessary complexity

5/23/2014 Vehicle Engineering - Peter Thorngren


TIME

1. Age of the Cabel • Volvo Öv (Jacob)

2. Age of the ECU • Intelligent ECU:s • Automotive Signal

Networks • TEA2

3. Age of the Services • Software Components • Internet

Communication Networks

• Not yet existing…or ???


Electrical System in Vehicles

2.5 TEA2+ • Software

Components • Automotive Signal

Networks • TEA2



The Function Washer Wiper

5/23/2014


The Software used in the Truck

Washer Wiper and the software in Trucks


AUTOsar Software

component

Ambient Temperature

Sensor

AUTOsar Software

Component

Washer Wiper HMI

Handler

AUTOsar Software

Component Head Lamp

Cleaner Controller

~10 Components

AUTOsar Software

Component WasherFluid

Sensor

AUTOsar Software

Component

Washer Wiper

Controller

5/23/2014

Volvo Group Trucks Technology Vehicle Engineering - Peter Thorngren 22

Code

AUTOsar Component

Washer Wiper

Controller

5/23/2014


Software Components

Virtual Function Bus

Electrical model that uses the Function Interface

Signal Interface for Washer Wiper




Functional Model in use…



Software Components

Virtual Function Bus

CAD 3D Model that could use the Function

Interface

Signal Interface for Washer Wiper




AUTOsar component

Ambient

Temperature sensor

AUTOsar Component

Washer Wiper HMI

Handler

AUTOsar Component Head Lamp

Cleaner Controller

AUTOsar Component

Washer Wiper

Controller

~10 Components

AUTOsar Component WasherFluid

Sensor

Mechanical model Electrical Model

= =

Business Model

=

Virtual Function Bus (and Similar Abstractions)

Real Model


Washer Wiper Virtual Truck with many usages

Volvo Group Trucks Technology Vehicle Engineering - Peter Thorngren 28

Collision Warning – Emergency Brake (CW-EB) – Manual test in Truck

5/23/2014


Product data

Use Case Modelling

Test Automation Workflow Today

Product data with test cases

Use Case

CANoe Configuration (databases, functions)

Subversion (storage)

CANoe XML

<xml> <…> <…>

CAN NET

XML

CAPL

ODX LIN

LIN CAN

Test rig CANoe

Test Verdict

Preparation Execution

Log server (storage)

<xml> <…> <…>

log … …

Test Report Log File CANoe XML

<xml> <…> <…>

log … …

Design Model



Create an Automatic Truck Test


Create a step-by-step sequence of keywords

Abstractions from the problem domain

Use Case driven Test Case

Product data repository 5/23/2014


32

Automated Test in RIG – CW EB



The Specifications in the Product Data Repository Creates the Truck



5/23/2014


ECU and Software to The release process

Function delivery to EE System Integration (The supplier delivering to GTT EE)


ECU

Build for ECU

AUTOSAR component


5/23/2014


AUTOSAR sent to Product database

for reuse

ECU

Build for ECU

Function delivery to EE System Integration (The supplier delivering to GTT EE)


AUTOSAR component


5/23/2014


36

The Truck is both Real Model for actual sale and a Virtual Model for improvements




37

The “Friday Truck” Virtual model is a Huge part of the “Spec” for the new “Monday Truck”


Virtual Truck Modell



38

The “Friday Truck” Virtual Truck model as the “Monday Truck” for new projects




The end of…



The dawn of…


- the integration challenge€¦ · marketing and jvs apac operations group trucks sales &...

Documents