1

©20

04 T

he M

athW

orks

, Inc

.

Model-Based Design of Automotive Systems with Automatic Code Generation

Steve Toeppe

Automotive Development Manager

Model-Based Design for Control Systems

This presentation is designed for seminar audiences that have little to no familiarity with the MathWorks products. However, existing customers who use Simulink to model and simulate control system designs can benefit from the information in this seminar concerning multidomain modeling, automatic code generation, rapid prototyping and test and verification. If the audience has a high percentage of people already using Real-Time Workshop or xPC Target, this is probably not the proper presentation for them.

The content of this seminar is modular and needs to be customized to fit the time allotted for the presentation. In addition, if the audience is primarily from one company or industry, the content can be further adjusted to fit their needs.

2

2

Electronic systems and software are part of mainstream vehicle functionality

Power Management

Transmission

EngineRide Control

ABS

Steering

Stability Controls

Traction Control

Obstacle Detection

Adaptive Cruise Control

Crash Avoidance

Airbags

Adaptive Front Lighting Systems

Passenger Detection

WindowsDoors

Lights

Climate Controls

Driver Drowsiness Infotainment

Instrumentation

Voice Recognition

Navigation

Wireless Connectivity

Today’s vehicle has become the singular most sophisticated consumer device on the market today when you consider the amount of software and electronics content in a vehicle. It was pointed out in a recently that the average vehicle today has more computing power than the Apollo spacecraft.

Software and Electronics are now pervasive in nearly every major system in today’s vehicles. It used to be just PT（Power Train）, but now elect and sw can be found in chassis, safety, comfort and convenience systems and driver information systems.

While this has led to vehicles with sophisticated performance & safety capabilities and creature comforts for drivers and passengers alike, it has also lead to a significant increase in work required during development of today’s vehicles.

3

3

Model elaboration

Design ImplementationRequirements and Specs

Test and Verification

Advantages of Model-Based Design

Continuous verification

Executable models-unambiguous-only “one truth”

Automatic code generation-minimizes coding errors

Test with Design - detects errors earlier

Simulation-reduces “real” prototypes-systematic “what-if”analysis

What we propose is a model-based design approach which avoids these pitfalls:

-Firstly models are used as the means of communication, and unlike paper documents, they are unambiguous because they can be simulated. You can see exactly what the design needs to achieve. -Simulation drastically reduces the need for real prototypes and allows you to perform fast design cycles and a lot of “what-if” studies which leads to greater innovation.-Automatic code generation eliminates hand coding errors.-And by coupling your tests with your designs within the context of the model, you catch errors much earlier in the development process where they are much easier and cheaper to fix.

[Build]

Our view is that design is just a process of elaboration, where you start with conceptual models at the beginning and gradually add more detail until you arrive at an implementation. With model-based design, the model is the concept, is the design, is implementation.

[Build]

And each step of the way, you can test and validate your design initially through simulation, but also in real-time and so you have continuous verification of the design.[build]And because model based design is based on the model, this lets you to move in both directions in the design cycle much more easily allowing for rapid iterations.

4

4

Typical Development Process

DefineRequirements

System-LevelSpecification

SubsystemDesign

SubsystemImplementation

SubsystemIntegration & Test

System-LevelIntegration & Test

Complete Integration & Test

Requirementsand

Specifications

Design

Implementation

Test and Verification

So to explain model based design we first need to look at the problems typically associated with a traditional development process.

We will use a design V, common in Automotive and familiar in some Aerospace companies and other industries.

The “V” is a 2D view of a development process – the x-axiz is time, while the y-axiz is abstraction. As you move down the left hand side of the V you add more and more details to the design with implementation at the vertex. As you move up the right hand side of the V, you do higher and higher levels of integration and test with final working products at the end.

[Build, step through animation]We can generalize this process into the phases of requirements and specification, design implementation, and test and Verification.

5

5

The Value of Model-Based DesignModel-Based Design

Executable specificationDesign with simulationImplementation through code generationContinuous test and verification

InnovationRapid design iterations“What-if” studiesUnique features and differentiators

Quality Reduce design errorsMinimize hand coding errorsUnambiguous communication internally and externally

CostReduce expensive physical prototypesReduce re-workAutomate testing

Time-to-marketGet it right the first time

So with Model-Based Design, you develop your embedded system based on Simulink models which gives you an executable specification, where you can design with simulation, and implement through automatic code generation, with continuous test and verification throughout.Resulting in a process that:•Fosters Innovation-Improves Quality-Reduces Cost-Minimizes time-to-market

6

6

Collaboration in the supply chain

OEMCreates specification

Requires models from

supplier

Tier 1 SuppliersImplements and validates specification

Creates system and requires models for subsystems from suppliers

Tier 2 SuppliersCreates models for components

Specification

with

Models

Implementation

with Models

So we have just seen some good examples of Tier1 and OEM’s improving their internal processes, however Mode-Based Design can also improve oem/supplier collaboration

OEM Creates executable specs of their requirements, and can ask multiple suppliers to develop their design, allowing the oem to select the one that best meets their requirements

SupplierBy being given a model , there is no ambiguity with spec, and so they can evaluate and optimize their design before submitting their implementation back to the oem

This also allows better V&V as they can prove the implementation matches the model’s performance.

7

7

MATLAB & Simulink

System-level modeling– multidomain– graphical– interactive– hierarchical

Algorithm designData analysisSimulation– model is an

“executable specification”

The MathWorks MATLAB and Simulink products work together to provide the foundation for Model-Based Design. They help you develop system-level models, design algorithms, simulate your complete design and analyse results.

8

8

Stateflow– Design and simulate

event-driven systems

Real-Time Workshop– Automatic code

generation from Simulink models

StateflowDesign and simulate event-driven systems

Capture all the logic of your control system.

Stateflow integrates with Simulink to provide an environment for designing reactive systems using state charts, flow diagrams, and truth tables. Applications for Stateflow include supervisory logic and control, fault management, and other types of decision systems.

The MathWorks Real-Time Workshop lets engineers and designers automatically generate code for testing, implementation and deployment from the model.

There are a number of other products that we will highlight through the presentation today. These are application or industry specific, task specific and are based off MATLAB, Simulink or Real-Time Workshop.

9

9

Executable Specification from Models

Component-based modeling

Flexible levels of fidelity

Managing large models with Model Explorer

Define system interface and specification that will be elaborated by others

Executable model removes ambiguity from specification

10

10

Model-Based Design with Simulink

SimMechanicsSimPowerSystemsSimDrivelineSimulink Parameter EstimationSimulink Control Design

So with model-based design, we can really turn this linear process into a circle, so what could take months to do all phases of the process can now be done in hours or days which allows you to rapidly iterate and promotes much more of a spiral development method. And the centre of this process are the models which serve as the repository for the design.

------------------------------------------------------------------Rescue:Here is what me mean by Model-Based DesignMaps on to any process, including the “V”, waterfall, etc.No arrow…

11

11

SimMechanics

Rigid body motion– Multiple bodies and joints– Geometric relationships

(constraints)– Multiple local coordinate

systemsForward dynamic analysis

– Force, torque -> acceleration, velocity, position

– Acceleration, velocity, position -> force, torque

Kinematic analysisCode generationCAD translation

SimMechanics allows you to construct 3D mechanical models all within the Simulink environment. You can then use all of the capabilities of Simulink and MATLAB to analyze your machine, model actuator dynamics, linearize, and simulate transients. You can connect multiple bodies and joints to construct complex mechanical systems. SimMechanics allows you to create multiple coordinate systems and constrain portions of a mechanism together.

In version 2.0 released November of 2002, we added the ability to generate C-code from your SimMechanics model. Version 2.1 released yesterday on May 19th, 2003 allows users to translate a SolidWorks assembly to a SimMechanics model.

12

12

SimDriveline

Applications• Rotational Actuation• Electric Power Generation• Mechanical Power Generation and Distribution

Key Features• Gears Library• Clutches, Backlash and Spring Damper blocks• Transmission and Vehicle Component Templates

The presentation should have a sales point of view. It’s intended not to be an informational presentation but to answerthe question How do I sell this product( or group of products)?

In order to have just one presentation, the content should be addressed to all of sales including GEO, MAT, SPECIALISTS AND EDU!!!

13

13

Design with Simulation

Drives modeled with SimDriveline

Model Reference for component design and testing

Integrated control design

First-principles and data-driven modeling

14

14

Simulink Verification and ValidationRapidly links models to requirements documentsSynchronizes models with projects in DOORSAssociates verification blocks with test cases Identifies untested portions of your model using industry-standard metrics Displays coverage information directly in the modelIncludes the requirements as comments in the C code generated for each block

There are many features to the Simulink Verification and Validation however I will just outline some of the key ones. Since we have discussed that this tool provides the ability to tie designs and test cases to requirements it is not surprising that a few of the key features are related to the requirements section.

First you can rapidly (and I mean as fast as you can right click) link models to requirements and even test cases. You can also associated these requirements to Telelogic’s DOORS and then navigate from the requirements to the model and from the model back to the requirements.

Next you can also associate verification blocks with particular test cases and rapidly change whether these assertions are enabled or disabled depending on the test case.

Finally as I have mentioned the third component of Simulink Verification and Validation is the ability to generate coverage reports. These coverage reports provide industry standard metrics and are fully integrated with the Simulink Model Viewer.

Segway: So lets look at how these pieces of requirements, verification, and model coverage fit together in the design flow.

SPEAKERS REFERENCEIndustry Standard Metrics include of structural coverage, including modified condition/decision coverage

15

15

Production Code Generation

Environment(Plant)

Application(ECU)

+-

Portion of Model-Based Design that bridges systems and software Software embedded in flight vehicle systems is automatically generated from modelsRequires fine grain control of software design details within modelsGenerated code must be small, fast, flexible, clear, traceable, easy to understand, and easy to integrate with legacy environments

16

16Visteon, SAE Technical Paper 2004-01-0269, March 2004

http://www.mathworks.com/mason/tag/proxy.html?dataid=4361&fileid=20307

Recent MetricsAutomatic code is smaller than production hand code

17

17

Standards• RTCA/DO178B Guidelines

• Commercial standard (FAA, JAA)• Software Integrity Levels A-E based on hazards • Level A if failure hazards can cause loss of life • Structural coverage analysis (MC/DC)

• MISRA Standards• Popular in automotive industry• Complete set of process standards • C programming rules are popular

• IEC-61508• Popular in industrial controls• World Trade Organization • European medical and automotive

• Other software process standards include SEI CMM, SPICE, ISO 9001, …

18

18

System Requirements

System Design

Software Design

Coding

SoftwareIntegration

Hardware/SoftwareIntegration

Vehicle Integration & Calibration

ECU Development Process

Requirements TraceabilityConfiguration Management

Documentation

with Model-Based Design

Sim

RP

OTRP SIL

PIL

HIL

PCGSim: SimulationRP: Rapid PrototypingOTRP: On-Target Rapid PrototypingPCG: Production Code GenerationSIL: Software in Loop TestingPIL: Processor in Loop TestingHIL: Hardware in Loop Testing

19

19

System RequirementsTelelogic DOORS

MS Word

Block that satisfies the requirement

Simulink Verification and Validation (Italics indicate MathWorks product)

and Traceability

20

20

System Design ModelNominal Sim

Failure Sim

Controller Plant

21

21

Bypass Rapid PrototypingSimulink

ECU

Cod

eG

ene r

ati o

nPlant ModelController Model

PlantHardwareReal-Time or

Embedded

Nominal RP

Failure RP

xPC Target Box

This represents a graphical description of our goal.

We want to take our controller model and through the process of automatic code generation get in on the Target System. This Target System will then connect to our real plant hardware.

Lets look closer at this xPC Target and xPC TargetBox. What is it and why is it useful?

22

22

Design Details

Subsystem Spec

Data Typing

Simulink Fixed Point

Function and FilePartitioning

23

23

Simulink

Harness

Cod

eG

ener

atio

n

Plant ModelController Model

PlantHardwareReal-Time or

Embedded

On-Target Rapid PrototypingNominal RP

Failure RP

Embedded Target

This represents a graphical description of our goal.

We want to take our controller model and through the process of automatic code generation get in on the Target System. This Target System will then connect to our real plant hardware.

Lets look closer at this xPC Target and xPC TargetBox. What is it and why is it useful?

24

24

Production Code GenerationSelect Target Choose Optimizations

Specify Code Files

BuildReal-Time Workshop Embedded Coder

And you can script that

25

25

Integration

A B C

M

INPUTBLUE GREEN RED

POWER

RGBSplit-4BLACK BOX

V RCS

CoreSoftware

Algorithms and Logic

InputDrivers

OutputDrivers

SpecialDeviceDrivers

CommDrivers

Scheduler/Operating SystemAnd Support Utilities

CommunicationInterfaces

Sensors

Actuators

SpecialInterfaces

ASAP2

CCP

Legacy Algorithm

Code

Most development is focused on the core software algorithms and logic. Usually a special team of engineers focus on the drivers,scheduler and special interfaces.Most applications are partitioned into modules, features or other components that map closely to the application. Usually each module is managed by an individual engineer. Modifications are usually focused at the module level and then integrated back into the intended application.Scheduling is handled in a number of different ways. A common approach is to use an internally developed scheduler that is co-operative and driven by timer interrupts. Usage of OSEK or commercial RTOS are increasing.Special device interfaces usually have a unique set of drivers and place constraints on how the code is prepared.

26

26

Partner Target Solutions

See MathWorks Connections Partners (www.mathworks.com/products/connections)

27

27

Test Inputs

Signal Builder Block

Simulink Verification and Validation

28

28

Test Coverage Analysis for ModelsCoverage fromfirst simulation

Coverage from second simulation

Total coverage (includes Modified Condition/Decision Coverage - MC/DC)

Simulink Verification and Validation

29

29

In-the-Loop ModelsSIL

Nominal Test

Failure Test

PIL HIL

Reusing yourmodel for multiple applications is where you get the most benefit to MBD。

30

30

Automatically Generated Reports

Simulink Report Generator

31

31

Software Configuration Management InterfaceCheck inCheck out

PC support for all Microsoft Common Source Control compliant tools

UNIX support for ClearCase, CM Synergy, RCS, & PVCS

32

32

System Architecture

Modular Development– Model referencing– Incremental and

iterative development– Configurable items

Incremental Code Generation – Model blocks– Persistent identifiers

Component Interface– Non-virtual buses – C structures

R14 makes these things easier to do

33

33

Data Management

Model Explorer andSimulink Data Objects

Create data dictionaryManage Simulink

and Stateflow dataUse MPT data objects

for production dataModel workspacesConfiguration sets

>> daexplr

34

34

Multiple Domain ModelingSystems containing:

Sensors and actuatorsEnvironment or plantApplication or controller

Are naturally modeled using:SimulinkStateflowSignal Processing BlocksetEmbedded MATLAB FunctionSimMechanicsSimPowerSystemsAerospace BlocksetMuch more …

35

35

Multiple Domain Code GenerationReal-Time Workshop Embedded Coder 4 supports and extends all Real-Time Workshop 6

Real-Time Workshop (GRT)

Real-Time Workshop Embedded Coder (ERT)

Continuous time Module packaging

One code generator for multiple uses

Rapid Prototyping/HIL Embedded Code

If you are already using RTW for RP/HIL it is easy to add RTW-EC for PCG

RTW-EC

RTW

36

36

Software Code Efficiency

R14 includes many new optimizations – Optimized fixed-point operations (e.g., division)– For-loop fusion– Enhanced inlining of Stateflow library charts– Improved expression folding– Improved dead-path elimination– Efficient implementation of absolute and elapsed

time– And much more…

37

37

Simulink Fixed PointFixed-Point Blockset fully consolidated with standard Simulink libraryUnified fixed-point functionality now added to more blocksBit-true simulation and code generation for multiplication and division with non-zero biasOptimized fixed-point code generation across productsAutoscaling of Simulink and Stateflow data

Engineers want to use standard Simulink blocks

38

38

Module Packaging Features

main.c

global.c

global.h

export.h

Normal files

special.c

special.h

extra.c

MPF DataPlacementRule Based

MPF DataObject SpecificData Placement

ExportedData

AdditionalCustomFiles

Model ExplorerData Dictionary

Files GeneratedPer MPF Options

RTW-EC Code Generation and Make Engine

CustomizationHooks ForExtra Files

Code and Data Templates

CustomComments

User DataTypes

User ObjectTypes

Data Naming

Rules

Coding standards and file formats -- Unique data definitions -- Industry Pilot Support

Module Packaging Features permit the generation of files to be extended to support data placement and specific file formats.

Data placement rules permit establishment of global data files or other data placement approaches. Additional data dictionary specific overrides permit special handling of unique data placement situations that don’t closely follow the broad rules.

All code and data files are generated to the formats specified in code and data style sheets or templates. The templates (.cgt) permit reordering and partitioning of data and code segments.

39

39

Multirate Systems

Rate grouping: each rate into separate functionTarget independent (priority based) rate transition block for periodic and asynchronous data transfersSample time constraints for models and subsystemsEnhanced asynchronous event supportProduction-quality Absolute and Elapsed time

Multirate is now much more efficient, clearer, and better for production

>> rtwdemo_async

MathWorks has 10 years experience in Multirate and async, R14 makes this easier

40

40

Interfaces

Simulink-based External Mode

Target-based C-API

Host-based ASAP 2

Interfaces offer a synchronized model/code platform for other technologies to leverage.

Tunable const now for StateflowC-API lets you interface to data elements in the generated code for logging, monitoring and tuning

void MdlStart(void) {…/* user code (Initialize function Body) */adderVar = createAdder(); }…

}

Generated Code

41

41

Embedded TargetsMathWorks offers Embedded Targets for:

– Motorola® MPC555, Motorola® HC12– Infineon C166® / ST10® family, OSEK/VDX®– TI C6000™ DSP, TI C2000™ DSP

Features vary per product but typically include:– Integration with select tool chains (IDE)– Automatic build and download– Preconfigured to run with popular evaluation board(s)– Scheduler for on-target execution– Target specific blocks such as device drivers blocks– Target interaction mechanism such as PIL with MPC555– Target profiling (RAM, ROM, execution speed)

Real-Time Workshop Embedded Coder also supports:• ANSI/ISO-C targets (Default)• User guide describes how to develop your own target

42

42

xPC TargetProvides drivers and multitasking kernel that executes code from models on a PCHard real-time performance (~ 100KHz)Host/Target operation with:

– Explorer to tune parameters & monitor signals (incl. Stateflow states)

– Target file system to access non-volatile data (sinks or sources)

Many hardware choices including:– Desk PC, Industrial PC, PC/104, CompactPCI, xPC Target Box– Over 250 I/O device drivers for ISA, PCI, PC/104 boards

• A/D, D/A, digital, PWM, encoder, CAN, ARINC 429Supports code from

– Real-Time Workshop– Real-Time Workshop Embedded Coder

xPC Target supports a large selection of different PC form factors and over 150 different I/O devices to let you get data into and out of your application, to talk to your real-time devices.

43

43

New Demo SuiteFull suite of demos showing seamless modeling and code generation environment

>> rtwdemos

44

44

Industry Examples: AutomotiveGeneral Motors Powertrain

Production deployment for powertrain controllersToyota and Denso

OEMs and suppliers in mass productionVisteon Powertrain

Automatic code smaller than hand codeCaterpillar

Single tool for rapid prototyping and production codeDelphi

Set & Forget Automatic Climate ControlMotorola Powertrain & Chassis Systems

Second-generation fixed-point useJaguar

In-vehicle rapid prototyping Siemens VDO

“Excellent local support from MathWorks Germany”DaimlerChrysler

“Designs Cruise Controller for Mercedes-Benz Trucks”

45

45

BackgroundExpanded model-based design to include on-target rapid prototyping and production code generation.Evaluated many vendors and tools.

Results (June 04)Pilot program using Simulink, Stateflow, and Real-Time Workshop Embedded Coder for powertrain ECU code generation.Decision to proceed with MathWorks based on:

– Seamless modeling and code generation environments (including Release 14).

– Code efficiency and flexibility.– Comprehensive pilot and technical support.

46

46

Toyota and DENSO Mass Production ECUs

Background– “Toyota has a ‘kaizen’ way of always pursuing evolution and

innovation, and challenging the improvement,” said Kazuhiko Hayashi, General Manager, Toyota

– “DENSO is improving our production processes using advanced software tools,” said Shinji Shirasaki, Director, DENSO. “We expect that our consistent use of these tools will allow us to accelerate our ability to bring DENSO products to the market more quickly

Results– Toyota and DENSO will use The MathWorks simulation, modeling, and

code generation products in a number of their software development for production programs, including powertrain control and other electronics control units

– Real-Time Workshop Embedded Coder is used to generate, test, and deploy production C code for complex, embedded systems

– “I think that The MathWorks and Cybernet Systems have understood our ‘kaizen’ way” [Kazuhiko Hayashi]

Press Release – January 04http://www.mathworks.com/company/pressroom/index.shtml/article/438

47

47

DaimlerChrysler Designs Cruise Controller for Mercedes-Benz Trucks Using MathWorks ToolsThe Challenge

To create and implement modular cruise control software on a target ECU

The SolutionUse MathWorks tools for Model-Based Design to reengineer the cruise control system by designing, testing, and implementing the software on an ECU

The ResultsCompact, efficient codeHigh test efficiencyFast development

“MathWorks tools for modeling and code generation enabled us to quickly and seamlessly perform design and test iterations, and release our product within a hard deadline of 18 months."

Mario Wunsche,DaimlerChrysler

Mercedes-Benz truck.

http://www.mathworks.com/company/events/programs_de/iac2004/Conference Paper – IAC 2004

Industry: AutomotiveApplication: Control Design, Production Code GenerationProducts: MATLAB, Simulink, Real-Time Workshop, Real-Time Workshop Embedded Coder, Stateflow, Stateflow Coder, Simulink Fixed Point

48

48

Nissan develops emission reduction system for mass-production vehicles using MathWorks Tools

The ChallengeTo design an emission reduction system certified by the California Air Resources Board (CARB) for the Partial Zero Emission Vehicle (PZEV) Standard

The SolutionUse MathWorks tools for model-based design to design an emission reduction system that was certified by CARB for the PZEV standard

The ResultsDevelopment time reduced by 50%Environmental Protection Agency award receivedNumber of sensors reduced

“Model-based design with MATLAB and Simulink is fully proven and indispensable to our engineering process, and gives us an edge over our competition."

Shigeaki Kakizaki, Nissan Motor Co., LTD.

The Nissan 350Z.

Development time reduced by 50%. “When applying advanced control theories, MATLAB and Simulink are far superior to in-house tools for analysis and design,” says Mr. Kakizaki. “MathWorks tools helped reduce our programming by half and improved communication among our engineering teams.”Environmental Protection Agency award received. For their innovations in improving fuel economy and reducing ozone-depleting hydrofluorocarbons, Nissan received the U.S. Environmental Protection Agency’s Climate Protection Award. Nissan is the only automaker to receive such a commendation.Number of sensors reduced. Using Simulink for their emissions control strategy, engineers reduced the number of sensors without losing any control capabilities. This technology was then applied to all 2003 Nissan Sentra models.

Products UsedMATLAB®Simulink®Stateflow®

49

49

The Value of Model-Based DesignModel-Based Design

Executable specificationDesign with simulationImplementation through code generationContinuous test and verification

InnovationRapid design iterations“What-if” studiesUnique features and differentiators

Quality Reduce design errorsMinimize hand coding errorsUnambiguous communication internally and externally

CostReduce expensive physical prototypesReduce re-workReduce testing

Time-to-marketGet it right the first time

Locate and fix design flaws earlier

Avoid or delay building prototypes or writing code

Find the optimal design

Improve design team communication

Reduce manual work and opportunity for errors

50

50

The MathWorks at a GlanceHeadquarters:Natick, Massachusetts USAUSA: California, Michigan, Washington DC, TexasAsia-Pacific:KoreaHiRain in ChinaEurope:UK, France, Germany, Switzerland, Italy, Spain, Benelux, NordicWorldwide training and consulting Distributors in 25

countries

Earth’s topography on an equidistant cylindrical projection, created with MATLAB and the Mapping Toolbox

The MathWorks corporate headquarters are located in Natick, Massachusetts, just outside of Boston.In the US, we have field personnel in Michigan to serve our automotive customers, and in California, Washington, and Texas serving customers in aerospace and defense.The MathWorks also has offices throughout Europe, and in Korea.From these locations, The MathWorks offers not only sales and technical support, but also training and consulting for our customers around the world.Elsewhere, marked with the gray icons, The MathWorks is represented by distributors that represent and support our products in their regions.

Note: When appropriate, mention the capabilities of the local representative or one that’s important for the audience (such as Cybernet in Japan for the automotive market) and their close and long-term relationship with The MathWorks.Background: The graphic shows topology (elevation) data, rendered in this map projection using MATLAB and the Mapping Toolbox.

51

51

Key Industries

Core– Aerospace and Defense– Automotive– Communication, Electronics, and

Semiconductor– Computers and Office Equipment– Education

Emerging– Biotech, Pharmaceutical（制药）, and

Medical– Financial Services– Industrial Equipment and Machinery– Instrumentation

Ongoing– Chemical and Petroleum– Earth and Ocean Sciences– Utilities and Energy

Our customers work in many different industries. The “core” industries represent our largest markets and longest-term customers, who are using our products in a deep and comprehensive manner, applying them throughout their processes.

Companies in the “emerging” areas are ramping up quickly in their adoption of our products, as they address challenges in new and fast-moving areas such as biotech and financial engineering, or applying new approaches in areas such as industrial equipment and instrumentation.

The range of industrial applications shows the broad appeal of our products, their flexibility. Our products also enable a cross-pollination of ideas and approaches across these markets

52

52

The MathWorks Connections Program

Over 300 add-on products and services from partners that complement and extend MathWorks products

– Specialized third-party toolboxes for MATLAB– Interfaces to partners’ software and hardware products– Specialized training courses and consulting services– System integrators and suppliers that incorporate

MathWorks products

Through our Connections Program, The MathWorks works with companies who provide over 300 products and services that work with MathWorks products. These are commercial offerings from the other company. Some examples include:- toolboxes with functions for a specialized application or technique- products that can use MATLAB as a computation engine for running user-specified algorithms- co-simulation and model import interfaces between Simulink and specialized modeling tools (such as hydraulics, mechanical systems, etc.) so that preexisting or specialized models can be incorporated into a Simulink simulation- real-time systems that support Real-Time Workshop automatic code generation- domain-specific trainers and consultants- system integrators that can integrate MathWorks products in a larger system or process

For more information, refer to the URL on the bottom right of the slide.

53

53

Commitment to the Automotive Industry

The MathWorks maintains close interaction with our automotive customers (through MAAB and J-MAAB)

– Large-scale modeling and enterprise usage– Code generation technology for simulation, prototyping,

testing, and production software development– Testing capabilities to support verification and validation efforts

Strong domain expertise within the company– WW offices and technical personnel in key automotive markets

Model-Based Design is the de facto standard for controls development across OEMs and suppliers

Our product planning reflects the needs of the industryStrong development ties with our customers through the MALC forum and strong customer interaction

Strong domain expertise within the company

54

54

Thank you for comingThank you for coming