model based systems engineering in automotive industry ... · • changan, founded in 1862, is the...
TRANSCRIPT
© 2016. Changan UK R&D Centre Limited. Published and used by INCOSE UK Ltd with permission
Model Based Systems Engineering in Automotive IndustryProgress and Next Steps*
Changan UK R&D Centre | 2017.04.27
Andrew HowellsIan Aitchison
MBSE Working Group – 27th April 2017
*Extract from INCOSE ASEC 2015 & 2016 papers
1. Introduction to Changan
2
Changan Parent Company:• Changan, founded in 1862, is the pioneer of China's modern
industry. It has existing assets 68 billion yuan and nearly 50,000 employees.
• Changan's own domestic brand sales ranked first in China and 13th in the world, with a brand value of 27 billion RMB Yuan. [2010]
• Changan also have joint ventures with Suzuki, Ford, Mazda, Volvo, and PSA Peugeot-Citroen.
Changan UK(R&D) founded in 2010:• Taking a lead in developing System Engineering Capability to
strengthen core capabilities• Designing and develop high quality, high performance
powertrains to support Changan’s global requirements
MBSE Project Background
3
Key Challenge: Sustaining MBSE rollout and more focus on Verification and Validation
Initial C207 Hybrid Prototype Vehicles
2015 Summary:• MBSE Process and Toolset Established – C207 pilot• Improved Collaboration • Structured and clearer Requirements• Technical Issues identified earlier• Features and Re-use considered from the Outset
2016 Challenges:• Improving Processes – Focus on whole lifecycle• Integration of more functional areas • Ensuring our Engineers Capabilities are developed
4
System modelling using CHASE enables consistent and technically correct implementation confidence in the system design
Historically disciplines working in isolation resulted in fragmented design with low confidence
Auditing of CHASE is led by automated model validation and tailored process training
CHASE unifies the design space making it easier to track overall progress and check consistency
Requirements
System Model
Functions
Interface Spec’s
Test Spec’s
Safety Analysis
Failure Modes
Realising the value of Systems Engineering
CHASE approach
5
CHASE has defined a way to transform the historical approach to develop an integrated holistic design
Implementation
Test Test
Specifications and Procedures
CHASE provides an environment to combine the specialist areas into a single integrated model
All input for implementation is provided from a single consistent source
Test and validation procedures defined to verify requirements and capture lessons learnt
System Design
SafetyDiagnostics
Holistic System Design from single source
CHASE team
Applying Systems Engineering in context – Knowledge management
6
CHASE allows reuse of the system design in multiple contexts driving effort reduction and consistency in implementation
Pilot project constrained by physical architecture Cannot be directly reapplied
Behavioural model focuses on the traditional approach of “features” within an Automotive context
Pilot project – Behaviour + Physical Architecture
Behavioural Model
Implementation Model
Implementation Model
Logical Model
Implementation Model
Implementation Model
2014 - 2015
2016 2017
Combining Behavioural and Logical Models allows application to multiple implementations
7
Behavioural Model
Customer Selectable Options
FEATURE GROUP - Driving Assist
FEATURE - Cruise Control (Variant 1)
FEATURE - Cruise Control (Variant 2)
BEHAVIOURBEHAVIOUR
BEHAVIOURBEHAVIOUR
BEHAVIOURBEHAVIOUR
OPERATION OPERATION OPERATION OPERATION OPERATION
Supporting content
8
SysMLCHASE
«block»Block1
Actor1
Requirement1
«operation»Operation1
«message»Message1
«element»Element1
«system»System1
«behaviour»Behaviour1
«variant ele...Block2
«variation p...Variation Point1
«stakeholder role»Stakeholder Role1
Need Description1
MetaClass
«metaclass»Class
«metaclass»Actor
«metaclass»Requirement
extend generalisation
TV [Package] Operations [TV - Standard Cruise Control - Behaviour Summary]
«behaviour»Standard Cruise Control Driver
Interaction
«variant elem...Standard Cruise
Control
«behaviour»Standard Cruise
Control Determine Torque Demand
«behaviour»Standard Cruise
Control Mode Arbitration
«operation»Arbitrate Standard
Cruise Control Mode
«operation»Determine
Standard Cruise Control Driver
Output
«operation»Determine
Standard Cruise Control Driver
Input
«operation»Calculate Standard
Cruise Control Vehicle Speed
Delta
«operation»Determine
Standard Cruise Control Torque Authorisation
«operation»Determine
Standard Cruise Control Speed
Setpoint Request
«realise»«realise»
«exhibit»
«realise»
«exhibit»
«realise»«realise»
«realise»
«exhibit»
Behaviour model example – Cruise Control
9
TV [Package] Documentation - System Behaviours [Standard Cruise Control - Behaviour Su...
«behaviour»Standard Cruise Control Driver
Interaction
«variant elem...Standard Cruise
Control
«behaviour»Standard Cruise
Control Determine Torque Demand
«behaviour»Standard Cruise
Control Mode Arbitration
«exhibit» «exhibit»«exhibit»
Behaviour model example – Cruise Control
10
SSV [Package] Standard Cruise Control Connectivity [Standard Cruise Control - Operation Connectivity]
Determine Standard Cruise Control Torque
Authorisation
Calculate Standard Cruise Control Vehicle
Speed Delta
Output to Vehicle System
Determine Standard Cruise Control Driver
Input
Arbitrate Standard Cruise Control Mode
Determine Standard Cruise Control Driver
Output
Determine Standard Cruise Control Speed
Setpoint Request
Input from Vehicle System
«message» Cruise Control Mode
«flow»«message» Torque Authorisation Decision
«flow»
«message» Vehicle Speed
«flow»
«message»CruiseSpeedSetpoint_Value«flow»
«message» Drive Mode Actual, «message» Drive Mode Request
«flow»
«message» Driver Demanded Wheel Torque
«flow»
«message»CruiseSpeedSetpoint_Value«flow»
«message» Vehicle Brake Demand
«flow»
«message» CruiseSpdSptIpReq_Status
«flow»
«message» Vehicle Speed
«flow»
«message» Cruise Control Mode
«flow»
«message» CruiseControl_Status
«flow»
«message» Cruise Control Mode
«flow»
«message» CruiseModeInputReq_Status
«flow»
Implementation model example – Cruise Control
11
TV [Package] Cruise Control Example implementation [Cruise Control deployment]
«operation»Calculate
Standard Cruise Control Torque
Demand
«operation»Calculate Torque
Demand
«operation»Arbitrate
Standard Cruise Control Mode
«operation»Determine
Standard Cruise Control Torque Authorisation
«operation»Calculate
Standard Cruise Control Vehicle
Speed Delta
«message»Actual
Transmission Clutch Carry
Torque
«message»Torque
Authorisation Decision
«message»Cruise Control
Mode
«message»Cruise Wheel
Torque Demand
«message»Cruise Speed
Delta Value
«item»Driver Requests
(DR)
«operation»Determine
Standard Cruise Control Driver
Input
«operation»Manages Vehicle
Behaviour
«message»Driver Wheel
Torque Demand
«message»Cruise Mode Input Request
«element»PCU
«operation»Manages Power
Generation
«operation»Determine
Standard Cruise Control Speed
Setpoint Request
«item»Powertrain Control App
«item»Processor
«send» «receive» «receive»«send»«receive» «send»
«deploy»«deploy»
«receive»«receive»«receive» «send»«receive»
«deploy»
«receive»«receive»
«deploy»
«receive»«send»
«deploy» «deploy»
12
Feature specifications will be linked to a corresponding test specification This package of work will provide first level of validation
Applying Systems Engineering in context – V&V