Application of Model Based System Engineering (MBSE) Principles to an Automotive Driveline Sub-System Architecture - Presented by Robert Kraus, George Papaioannou and Arun Sivan

Oct 26, 2026

Discusses how to apply Model Based System Engineering (MBSE) principles to an automotive driveline sub-system architecture using SysML. Starts from a “document based” current state that often yields incomplete or conflicting requirements, then outlines a project that decomposes existing methods, improves requirements traceability, and adds parametric constraints for sizing. Defines driveline architecture components and system engineering constructs (V-Model, context and P-diagrams), then models requirements, functional/logical architecture, and functional decomposition mapped to logical blocks.

LanguageEnglish

CategoryResearch & Report

FormatPDF

Pages20

Reading Time50 min

AccessFree to download

Introduction & Project Summary

Driveline Definitions and Concepts

Systems Engineering Concepts

MBSE Concepts

Driveline Model Structure: Functional and Logical Decomposition

Requirements & Test Case Management

Requirements Management: Satisfy Relationships

Parametric Relationships: Constraint Modeling Applied to Sizing

Benefits of Applied MBSE

Application of Model Based System Engineering (MBSE) Principles to an Automotive Driveline Sub-System Architecture Presented By: Robert Kraus, George Papaioannou andArunSivan Discussion Agenda ● Introduction & Project Summary ● Driveline Definitions and Concepts ● Systems Engineering Concepts ● MBSE Concepts ● Driveline Model Structure-Functional and Logical Decomposition ● Requirements & Test Case Management ● Requirements Management : Satisfy Relationships ● Parametric Relationships-Constraint Modeling Applied to Sizing ● Benefits of Applied MBSE Introduction & Project Summary Current State: Today’s automotive driveline system engineering process is “document based” ● Complex system requirements and specifications are communicated through large amounts of electronic data ● Often leads to incomplete or conflicting requirements ● Inefficient, redundant, error prone ● Running changes introduce potential problems Project Summary: ● Obtained and deconstructed existing driveline system methods and sizing tools ● Identified need for improved requirements traceability in driveline systems engineering ● Created detailed driveline system model to apply the concepts of MBSE using SysML ● Added parametric constraints for sizing calculations ● Delivered functional MBSE model as proof of concept Driveline Definitions and Concepts Architecture: Complete AWD Driveline ● A driveline system links the powertrain output to the drive wheels ● Primary function is to transmit drive torque from the powertrain to the ground (wheels) ● Driveline subtypes such as FWD, RWD, AWD are treated as generalizations in SysML Components: ● Driveshaft / half shaft-transmits torque to front/rear or left/right ● Axle-multiplies driveshaft torque and directs to wheels ● Additional-Transfer case, PTU, disconnect device, U-joints, CV-joints, flex coupler Sizing: ● Design optimization of each component, system and subsystem is the primary objective ● A sizing tool converts input data into torque outputs for all vehicle variations and uses industry standard equations and some correction factors. System Engineering Concepts ● V-Model: ○ Top level requirements are decomposed to the subsystem and component levels, each with a specific validation plan flowing down the left side of the V and back up the right side. ● Context Diagram: ○ Represents system interactions to an external environment ○ Interacting systems are defined as “black boxes” ● P-Diagram: ○ Expands and refines context for more detailed black boxes ○ Includes detail on input signals, control factors, noise factors, outputs, and potential failure modes ● MBSE ○ Modeling Language (SysML, UML etc) ○ Modeling Method ○ Modeling Tool (Magicdraw, IBM Rational Rhapsody etc) V-Model Context Diagram P-Diagram Model Based System Engineering Concepts: System Requirements ● Requirements define customer and stakeholder needs in technical terms ● In SysML, system requirement statements are defined as objects ● Each object contains the requirement text & a unique identifier ● The requirement type defines the features a requirement can be associated with ● Generalizations manage and allocate requirements through inheritance relationships ● Requirements must be verified by test cases ● Test cases are checkpoints, such as design reviews or physical tests Standard type requirements within SysML are used to provide rigor and clarity when defining the system Model Based System Engineering Concepts: Functional & Logical Architecture ● Functions define what actions / activities must be accomplished or completed to achieve a desired outcome ● An operation is a property of a block ● A block is an abstract representation of any part of a system, like physical hardware or a signal ● Functions are linked through logical relationships to the various subsystems and components ● The logical architecture descri

FAQs

Why is the current automotive driveline engineering process considered problematic?

The process is largely document-based, with complex requirements communicated through large amounts of electronic data, which can lead to incomplete or conflicting requirements, inefficiencies, redundancy, and errors. Running changes can further introduce potential problems.

How does the project apply MBSE to the driveline system?

It obtains and deconstructs existing driveline methods and sizing tools, identifies the need for improved requirements traceability, and creates a detailed driveline system model using SysML. It also adds parametric constraints for sizing and delivers a functional MBSE model as a proof of concept.

What role do requirements and test cases play in the SysML MBSE approach?

Requirements are defined as SysML objects that include requirement text and a unique identifier, and they must be verified by test cases. Test cases serve as checkpoints, such as design reviews or physical tests, ensuring each requirement is validated.

Oct 26, 2026

Upload by Indoniesian Boy