1. KPIT Cummins Infosystems Advance Technology Solution
Software Platforms
for
Automotive ECU
© 2009 KPIT Cummins Infosystems Limited
We value our relationship

2. About us Automotive Overview KPIT Overview KPIT DNA
4,800+ Employees. Revenue 07-08, $146m (Expected $175m 08-09)
15+ years in business with global operations and partnerships
Successful partnership model with Cummins
Automotive Overview
1300+ Engineers in Auto product engineering / 8 patents
13+ years in Auto
50+ relationships: OEMs, Tier 1s, Semiconductor & Tool Vendors
KPIT DNA
Relationship Oriented (Deep and Long)
Customer Centric
Sharp focus
Flexible
Risk taking ability
Technology Excellence
Only solutions company from India with #1 focus vertical as Automotive
6 July 2018

3. Agenda Software Platforms - Introduction Different Platform Approaches1
Software Platforms - Introduction 2
Different Platform Approaches 3
Recommended Approach 4
Roadmap for Adoption 5
Why KPIT ?
6 July 2018

4. What are Software Platforms?
Collection of common elements, especially the underlying core technology,
reusable across a range of applications
A software platform consists of Application Programming Interfaces that specify how a
software developer can use system functions or access useful modules of code built into
the platform. This helps in increased reusability
GENERAL ARCHITECTURE
FEATURES
Separation of application
and Infrastructure
Standard APIs
Common Components used
across applications /variants
Modular architecture to allow
scalability and flexibility
Reduces overall complexity
6 July 2018

5. Why do we need Software Platforms ?
Exponential growth of software
usage in automotive systems
Increased Complexity and hence
quality issues
Poor scalability and inflexible systems
High costs and long development time
1994
2008
ECU (w/o LIN nodes) 40 60
MIPS 45
1150
MHz 85
2000
MCU Memory (program + data)
1.1 MB KB
19MB MB
Transistors
21 million
340 million
Bus Bandwidth
700 kbit/sec
23 Mbit/sec
Source : leitner-autosar.pdf
6 July 2018

6. Platform Approach Advantages
Cost reduction
Shorter development time
Reuse of tested and validated modules
Scalability across product lines, covering multiple brands and
segments
Faster innovation
Competitive pricing through sourcing flexibility
Software Platforms are building blocks for Product Line
Architecture, which leads to further advantages
6 July 2018

7. Product Line Architecture(PLA) – Added Benefits
WHAT IS PLA ?
Even though software platforms result in several advantages, Management of
variability and evolution of systems, emerge as key concerns for adaptive
business-critical systems and products.
PLA addresses the issues of management of variability across a product line
In simple words, PLA involves adoption of a Software Platform and developing
components according to logical group sub-systems. It thus entails a change in
application layer as well
PLA aims to optimize the number of variable components while allowing to adapt
customer-visible variability as needed by the current market situation
SOFTWARE PLATFROM + PLA = MAXIMUM BENEFIT

8. Product Line approach & MBD
System Configuration
Concurrent Development
Calibration/ Data Management
Test
Component
Control
Development
Plant
Modeling
Relational database
based framework
Component Based
Configuration
Management Tool
Component Based
Miscellaneous
Manage
Tools
infrastructure
Model Based Development
Product Line Architecture 8

9. Product Line Architecture – Logical Process
Complete solution - Effective way of managing multiple vehicle platforms
6 July 2018

10. Typical System Architecture: PLA ( Powertrain)
ConfigurationSpecific
Machine
Engine
Engine Subsystems
Communications
General
Control Agent(s)
Control Agent(s)
Accessory Control Agent(s)
Accessory Control Agent(s)
Machine Manager (Only ONE)
Engine Manager (Only ONE)
Combustion Manager (Diesel)
Combustion Manager (Alt Fuels)
Lube & Cool Manager
Charge Manager
Fuel Manager
Aftertreatment Manager
Communication Agent(s)
Communication Agent(s)
Comm Translator(s)
Comm Translator(s)
Comm Presenters
Comm Presenters
Comm Manager (Only ONE)
Configuration Tracker
Configuration Build
Execution Manager
Software Utilities (Only ONE)
1…n
1…n
1…n
1…n
1…n
HAL Interface
Platform and components….
Component based
Boot Strap OS
FS Driver
AT Driver
AH Driver
Flash Loader
1…n
HW - SW Interface
6 July 2018

11. Agenda Software Platforms - Introduction Different Platform Approaches1
Software Platforms - Introduction 2
Different Platform Approaches 3
Recommended Approach 4
Roadmap for Adoption 5
MCAL abstraction layer (HAL)
OS Linux
Performance driver –Open GL
Middleware – direct x etc standard APIs
RTE – reuse middleware flexibility at MCAL
PLA – application level
Android.
Why KPIT ?
6 July 2018

12. Typical ECU Architecture & choices for Standardization
APPLICATION LAYER
Application Platforms (e.g. AUTOSAR)
RUN TIME ENVIRONMENT
Framework Platforms (e.g. AUTOSAR, MS DirectShow)
OPERATING SYSTEM
Operating System Platforms (e.g. Moblin, Linux)
HIGH PERFORMANCE DRIVER
Performance Platforms (e.g. OpenMAX DL)
MICROCONTROLLER ABSTRACTION LAYER
HW Platforms (e.g. OGL, OVG)
MICROCONTROLLER

13. Approaches to Software Platform
Comparison of the two approaches
PLATFORM APPROACH
Standardized
Proprietary
Benefits
Supported by
Industry Groups
Standardization –
interfaces and
middleware
Evolving and large
development
community
IP ownership
Control and flexibility
of development
Minimum external
dependency
Challenges
Some standards
may not be
suitable for lighter
ECUs
OEMs may mandate
Conformance to
standards
Upfront development
efforts
How to leverage
external development
Cost of ownership
STANDARDIZED
Conforming to
industry accepted
standards
No IP
AUTOSAR, Open GL
PROPRIETARY
Unique to a firm
based on perceived
requirements
IP ownership
WITH PLA
WITHOUT PLA

14. Agenda Software Platforms - Introduction Different Platform Approaches1
Software Platforms - Introduction 2
Different Platform Approaches 3
Recommended Approach 4
Roadmap for Adoption 5
Modular Platform – scalability.
Fresh
Legacy – Platform Approach
Why KPIT ?
6 July 2018

15. Parameters to Consider for Approach selection
STANDARD LIKE
AUTOSAR
PROPRIETARY
+ PLA
NOT ADVISABLE FOR LIGHTER ECUS
PROPREITARY
APPROACH SELECTION FOR SL
Number of Product Variants
Only a large number of product variants would mandate platforms like AUTOSAR and PLA approach
ECU
Choice of software platform would also depend upon the type of ECU (8 bit /16 bit) being used
OEM Perspective
OEM may mandate a standardized platform based on the benefits accruing to it
Development effort
The upfront effort that would be required to develop either a proprietary or a standardized platform is critical to make the choice
Disruption to existing system
The approach that will allow minimum disruption in migration to platform approach should be selected
NOT ADVISABLE FOR LIMITED PRODUCT RANGE
Recommended for the parameter
Not Recommended for the parameter
Proprietary Platform seems the best approach for SL to begin with, PLA could be a long term initiative
6 July 2018

16. Recommended Approach for SL Group
Platform Adoption
Design a platform based on product range and level of standardization
PLA Adoption
Move towards PLA as variability and feature differentiation becomes high
Product line ????
6 July 2018

17. Agenda Software Platforms - Introduction Different Platform Approaches1
Software Platforms - Introduction 2
Different Platform Approaches 3
Recommended Approach 4
Roadmap for Adoption 5
Why KPIT ?
6 July 2018

18. Software Platform Implementation Approach
Options
New Platform
Migration
NEW PLATFORM ( TOP DOWN APPROACH)
A new platform approach would have to be a strategic decision
This approach will have to be followed if the existing system is proving to be unsustainable and the maintenance costs are high.
It would give a benefit of total control and flexibility in designing the platform
It would entail huge investments
MIGRATION ( BOTTOM UP APPROACH)
Migration process would involve segregating the middleware from the applications
The components and applications then can be wrapped into a platform approach – so existing modules can be reused
In a proprietary platform the disruption would be less as interfaces can be developed for maximum reuse of applications
Top down and bottom up approach
6 July 2018

19. PLA Implementation- Likely Roadmap
Modeling + Software Platform Framework
Phase I
Executable Specifications + Software Platform Adoption
Phase II
Autocode & HIL Testing
Phase III
Core Group
Application teams
Conceptualize and Define
Develop central database
Tool and Framework selection
Adopt MBD
Implement pilot
Re-usable control components
Adoption of platform
Automated build framework
MBD for V cycle
Multiple product artifacts
Plant model components
Test automation framework
Re-usable test components
Complete electronic product development
18-24 months
24 months
Phases
Owner
Description
Timelines
Note :The timelines depends upon the effort required for architecture redesigning and product line
6 July 2018

20. Agenda Software Platforms - Introduction Different Platform Approaches1
Software Platforms - Introduction 2
Different Platform Approaches 3
Recommended Approach 4
Roadmap for Adoption 5
Why KPIT ?
6 July 2018

21. Platform Development Expertise
KPIT Cummins specializes in software platforms for several automotive sub-domains like Body , Networking , Infotainment etc
KPIT is a premium member of AUTOSAR and is a general contractor for writing conformance test specification
KPIT was involved in AUTOSAR related Joint Development Activity with an OEM and Tier 1
Co-development and maintenance of engine software platform for a Diesel Engine manufacturer
KPIT has developed a Proprietary Infotainment Platform for a Tier 1 and is developing a Telematics and Vision primitives Platform as part of R & D activity
KPIT follows a consultative approach to Platform adoption – suggesting most effective solution based on client profile
6 July 2018

22. AUTOSAR Implementation
UPDT4FEB09
PRODUCTS
SERVICES
Development, Integration in ACC Application
AUTOSAR R 2.0 compliant BSW
AUTOSAR SC1 OS
Integration of BSW with MCAL
Integration of BSW + MCAL with SC1 OS
Integration of application & Validation of integrated stack
Joint development activity with OEM & Tier1
RTE tool, Diagnostic Components
Memory Services, Mode Management, LIN interface,
COM Cluster with PDU Router
Validation of components in the OEM Application
Final Road Testing
KPIT AUTOSAR Solution in an Adaptive Cruise Control (ACC) Application of a production vehicle
6 July 2018

23. Software Platform for Tier 1
Platform Sub-Systems
Kernel Services - Kernel services wrap the functionalities of
mostly used kernels such as WinCE, uCOS-II.
Device Services - Device services must abstract commonly
used devices like I2c UART etc.
Com Services - Communication services provide an
abstraction for various Communication
systems such as TCP/IP, Flexray, CAN, FTP, LIN etc
GUI Services - GUI Services abstracts all GUI functionality for User
Application Development
Simulation Services - Simulation services for simulating the
Real-time application on Host PC
Database Services - Database services for abstracting database
functionality
Re-Configuration tool - Re-Configuration tool has to be provided
for selecting the SW Platform components
selecting the target hardware, selecting
the target OS etc.
GUI Designer - A GUI designer for designing User Interface of the
Real-time application.
General Libraries - Provides support for Error logging, Unicode,
Internationalization
SOFTWARE PLATFORM
6 July 2018

24. Telematics Platform
1609.4
1609.3
1609.1
802.11p
1609.2
Communication stack for automotive Wireless LAN based on p.
Used for CAR to CAR and CAR to Infrastructure Safety Applications
Software stack for p, , completed.
Available on Linux and PowerPC and X86 Platform.
5.9 GHz Radio interface hardware based on Atheros Wireless Chipset
Enhancement Roadmap
Support for SAE J2735 Message set
Jan. 09
Simulation test bed development
Feb. 09
Upgrading to 5.9GHz hardware
Mar. 09
Field testing and trials
May 09
Support on other OS
May. 09
Support for ISO standards
Aug 09
Support for CEN standards 24
6 July 2018 24

25. Thank You!
“Companies that focus on what they are very good at can thrive despite these
difficult times. That has been the case for software companies like
KPIT Cummins…” - Paul Hansen – Sept’08
“KPIT is fast-growing and ambitious and represents the sort of company that in
a decade could seriously challenge existing automotive software providers”
Paul Hansen –Jan’08
We are committed to help our customers become efficient, integrated and innovative
6 July 2018