The Virtual Laboratory: Making it happen

1
The Virtual LaboratoryMaking it happen

• John Stawarz, COO, Invirtech

2
Topics

• First Steps
• What is a Virtual Lab
• Why a Virtual Lab
• Implementation
• Invirtech Virtecs
• Future

3
But before we get started

• Who am I

4
Topics

• First Steps
• What is a Virtual Lab
• Why a Virtual Lab
• Implementation
• Invirtech Virtecs
• Future

5
First Steps

• Accepted the concept of virtualization and the
  need for Virtual Verification Validation (V3)
• Accepted the validity of the enabling software
  technologies
• Vast
• Mathworks - Simulink or other simulation product
• Maplesoft, Modelica, VHDL
• How to institutionalize V3, i.e., Implement the
  software technologies within existing processes,
  infrastructure and corporate asset management

6
Topics

• Technology Deployment Process
• What is a Virtual Lab
• Why a Virtual Lab
• Implementation
• Invirtech Virtecs
• Future

7
What It Is Not

• Just installing applications on a desk top
  workstation
• An un-managed data environment, i.e., files on a
  workstation or server
• Necessarily a requirement for a user to have
  expert/detailed knowledge about the essential
  applications

8
What is a Virtual Lab

• Definition
• The ability to comprehensively verify and
  validate embedded control system (software)
  function and behavior without the need for
  physical hardware or instrumentation
• Support rapid assembly and configuration of
  complex, distributed embedded control systems
• Integrates all data and applications required for
  verification
• Minimally only require working knowledge of the
  applications
• Integrate into product development process
  providing a fast, effective and efficient VV

9
What is a Virtual Lab

• A managed data environment supporting access and
  use of data critical to the software VV process
• Parameter dictionaries
• ECU models
• Target embedded software
• Plant models
• Specifications and testable requirements
• Test vectors and procedures
• Results and reports
• Reliant upon accurate models
• Does not necessarily craft the models but uses
  them

10
Topics

• Technology Deployment Process
• What is a Virtual Lab
• Why a Virtual Lab
• Deployment
• Invirtech Virtecs
• Future

11
Why a Virtual Lab

• Minimize the need for physical hardware for
  embedded software VV
• Test stand/instrumentation
• ECU Module
• Enable more effective, efficient and thorough
  testing
• Initiate earlier in the process
• Reduce the break/fix repair cycle time
• Expand breadth and depth of tests
• Ensure robust, error free software delivery
  within current/future timing constraints
• Effectively drive the constraints in the cost
  ?, risk ?, timing ? and quality ?
  equation

12
Why a Virtual Lab

• Bridge the Virtual to Physical Gap

GAP
GAP
13
Topics

• Technology Deployment Process
• What is a Virtual Lab
• Why a Virtual Lab
• Implementation
• Questions
• Criteria
• Process Implications
• Usage Models
• Deployment Options
• Invirtech Virtecs
• Future

14
Questions

• What data are required ?
• What expertise is required ?
• What is the learning curve ?
• What are the costs ?
• How soon can we be up and running ?
• What are my process effects/changes ?
• What will be the reaction of the current users ?
• What do I do with the data produced ?
• How are the applications made available ?

15
Implementation - Requirements

• Execution of actual target code
• Accurate modelling of ECU hardware
• Plant model co-simulation
• Easy configuration and assembly of the virtual
  test rig
• Automated test execution
• Easy access to all data
• Integrated applications
• Integral to the overall product development
  process

16
Deployment - Process Implications
Product Development V
The Process Pursuit
Specification
MBD
Product
MIL
HIL
Auto Code Generation
SIL
Target Code
17
Deployment - Process Implications
Product Development V
What most likely happens
Specification
MBD
Product
MIL
HIL
Auto Code Generation
Bench Test
SIL
Target Code
18
Deployment - Process Implications
Product Development V
What we propose
Specification
MIL
MBD
Product
Auto Code Generation
HIL
Virtual Lab Virtual HIL supporting embedded
software verification and validation
19
Where Can the VL Be Applied

• Product Development Process
• Integral to independent audit of software
  adherence to specifications
• In software development
• Post Production Audit
• Verification of new software releases to current
  released production software
• Application Testing
• Provide virtual ECU for test of third party
  embedded software development
• Investigative
• Analysis of design and alternative network
  architectures

20
Deployment Requirements

• Data Integration
• specifications, requirements, test plans,
  procedure and vectors, target software, ECU
  Models, plant models, parameters, test operation,
  results
• Application Integration
• VaST, Simulation plus any additional software
  (e.g. requirements management tools)
• Configurability - quickly adapt new control
  system configurations and changing test
  requirements
• Usability - ease to use to allow any engineer
  (DR, Software, Systems, Test, etc.) to verify
  and validate software
• Interoperability - with existing corporate data
  backbone and adhere to corporate infrastructure
  guidelines

21
Deployment Options

• Do-It-Yourself.
• Outsource development of a Virtual Lab
• Purchase a Virtual Lab and then integrate it to
  corporate data backbone

22
Deployment Options - Comparison
23
Topics

• Technology Deployment Process
• What is a Virtual Lab
• Why a Virtual Lab
• Implementation/Deployment Options
• Invirtech Virtecs
• Usage
• Services
• Test Management
• Solution Concept
• Data Integration
• Operation
• Deployment
• Timetable
• Future

24
Virtecs

• VIRtual Test of Electronic Control Systems
• Data management framework integrating
  Off-the-shelf software key to a Virtual Lab
• Goals
• Reduce cost and timing to implement VL
• Fit into overall product development process
• Promote standardization, automation and evolution
  of the verification process

25
Usage What are the Steps to Test
Test Vectors
Procedures
Test Plan
Requirements
Plant Model
Specifications
ECU / ECU Model
Software
Assemble Test Environment
Product
Wiring
Applications
Run Test
Parameters
Analyze Results
Save

• Data Intensive
• Data is usually dispersed in multiple systems
• Data is of varied type
• Requires application specific knowledge

26
Virtecs Services

• Virtecs Services
• Information / Data Management
• Feature/Specification/Requirement Management
• Virtual Hardware/Target Code Management
• Parameter Management
• Model Management Services
• Behavior (Plant) Models
• Software Models
• ECU Models
• Test Manager
• Interoperability Services
• Integration with Corporate Data Systems

27
Virtecs Test Manager

• Test Case/Vector Management
• Auto-assembly/Configuration
• Testing
• Automated/Batch Test
• Regression Test
• Interactive/Ad-Hoc Test
• Virtual Vehicle Interactive Operation
• Test Vector, WaveForm, Drive File testing
  procedures

28
Virtecs Solution Concept
Data Management
Test Management/Execution Execute appropriate
mode (Automated batch, Regression,
Interactive/Ad-Hoc, Environmental) Manage Test
Execution Capture and report results
PDM Systems
Auto-generate Test Environment Auto-generate
Test Vectors Assemble Drive and Procedure
Files Assemble and Network Virtual ECUs Define
Test Control and Management Select Target
Software Select Plant Models Auto-configure the
Test Rig, i.e., virtual wiring
Assemble Feature/Specification Pair Requirements
Management Data and State Flow Diagrams Assignment
of Hardware, Plant Models Assignment of Target
Software Assignment of Parameters
Parameter Management Data/Signals DTCodes Test,
Procedure, Drive Operational and System
Model Management Virtual Hardware Models Plant
Models Software Models Advocate Models
29
Virtecs Data Integration
Data managed in harmony supporting re-usability
and synergy across the various data domains
Requirements Management
Validation and Test Results Management
ECU and Plant Model Management
System Integration Interoperability
Configuration and Test Assembly
Embedded Software Management
Parameter Dictionary Management
Interoperability strategy for internal and
external systems. The interoperability strategy
knits together systems allowing seamless access
and exchange of data and information
30
Virtecs Operational Model

• Select what to Test
• From specific feature sub-specification to full
  feature, full module/subsystem, product
• Configure test request
• Assemble test environment
• Hardware, plant models
• Software
• Test vectors, procedures, drive files
• Run test
• Collect and store results for retrieval and
  analysis

31
Virtecs Basic Operational Model
Data Vault
Simulink
ECU
Test Vector
Model
Software
Select and Load Embedded Software ltclickgt
Test Vector
VHIL Test Rig ltclickgt
VHIL
Select and Load Plant Model ltclickgt
Select ECU ltclickgt
Select Modeler - Simulink ltclickgt
Load Test Vectors and Initiate Testing ltwaitgt
Connect ECU and Modeler ltclickgt
Visualize
Data
Data
Data
Data can be saved back to Data Vault ltclickgt

• Objectives
• Enable a virtual test rig structure consisting
  of a ECU Model coupled to a Plant Model
• Integrate the virtual test rig to Virtecs data
  manager to allow access to software, models, and
  ECUs.
• Allow engineers to easily retrieve software and
  models from the Virtecs data manager and insert
  into VHIL
• Allow engineers to retrieve test vectors from the
  Virtecs data manager and apply to the VHIL
• Capture results either for visualization or to
  store back into the Virtecs data vault

32
Virtecs Operational Model
Data Vault
Test Vector
Test Vector
Test Vector
VHIL
VHIL
VHIL
Test Vector
Test Vector
Test Vector
Visualize
Visualize
Visualize
Data
Data
Data
Data
Data
Data
Data
Data
Data

• Objectives
• Enable a virtual test rig structure consisting
  of a ECU Model coupled to a Plant Model
• Integrate the virtual test rig to Virtecs data
  manager to allow access to software, models, and
  ECUs.
• Allow engineers to easily retrieve software and
  models from the Virtecs data manager and insert
  into VHIL
• Allow engineers to retrieve test vectors from the
  Virtecs data manager and apply to the VHIL
• Capture results either for visualization or to
  store back into the Virtecs data vault

33
Virtecs Deployment Alternatives
34
Virtecs Product Timetable

• Tiered Offering
• Basic (Q1/Q2-2009)
• Regression testing
• Single ECU configuration
• Enhanced (Q4/2009-Q2/2010)
• Multi ECU configuration
• Interactive (Q4/2010)
• Environment (Future)
• Vehicle in environment
• Services
• PDM Integration
• Document import/export
• Process Consultation

35
Topics

• First Steps
• What is a Virtual Lab
• Why a Virtual Lab
• Implementation
• Invirtech Virtecs
• Future

36
The Future of the Virtual Lab

• Knitting together of Modeling, Virtual Hardware
  and physical hardware (HIL, product) such that
  components can be interchanged
• Use of virtual environments to exercise and test
  the vehicle as a software system
• Virtual control system
• Vehicle models
• Environmental models

37
The End

• QA