Drive by Wire – “What Will Be Its Impact On Tomorrow’s Vehicles?” Craig Stephens Ford Motor Company.

Slides:



Advertisements
Similar presentations
Figures in Chapter 1. Learning objectives After studying this chapter, you should be able to; Define logistics and supply chain management. Describe logistics.
Advertisements

Vehicle-infrastructure integration: creating co-operative mobility systems and services Hearing EU Parliament, 22 January 2009 Hermann Meyer, CEO.
Powered-Two-Wheelers Road Safety The commitment of Piaggio & C. SpA Ljubliana, 23 April 2008.
What is Software Design?. Systems Development Life- Cycle Planning Analysis Design Implementation Design.
Steve Justice Allison Transmission. Hybrid Benefits Regenerative Braking 1.When stopping the vehicle, Allison Electric Drive automatically becomes an.
Product Lifecycle Management © 2003 IBM Corporation ArvinMeritor LVS (Light Vehicle Systems)  Customer Background o UK arm of worldwide group of companies.
MotoHawk Training Model-Based Design of Embedded Systems.
Flexible Manufacturing Systems (FMS)
Software Design & Development Year 12. Structure of the Course Development and Impact of Software Solutions Development and Impact of Software Solutions.
1 Software Testing and Quality Assurance Lecture 33 – Software Quality Assurance.
1 Computer Systems & Architecture Lesson 1 1. The Architecture Business Cycle.
Data Acquisition Real-Time System Integration Preston Schipper Matt Hulse Adrienne Baile DARSI II.
Welcome to Maastricht University Faculty of Economics and Business Administration The Marketing-Finance Interface: A new Master Program at UM Dr. Arvid.
SEG Software Maintenance1 Software Maintenance “The modification of a software product after delivery to correct faults, to improve performance or.
1 Analysys Mason undertook an international programme of customer satisfaction research for a telecoms billing system vendor  A billing systems vendor.
Becerra-Fernandez, et al. -- Knowledge Management 1/e -- © 2004 Prentice Hall Chapter 4 Organizational Impacts of Knowledge Management.
EV – HV (1) General description Market –failure in the past for EV –Public acceptance hard to determine Technology –A continuum from hybrid to full EV.
COMPUTER SOFTWARE ALISA RAHMANI PUTRI / VIDIYA RACHMAWATI /
PRTR Trends in the Automotive Industry Using PRTR data to measure & assess progress November 11, 2014.
TRIALOG 25 rue du Général Foy F Paris - France Tel Fax url:
WAO 2007 Andrej Košiček Dealing with the Obsolescence in state-of- the-art Electronic Components 27 September 2007.
ISO Tor Stålhane IDI / NTNU. What is ISO ISO 9001 was developed for the production industry but has a rather general structure ISO describes.
TECHNICAL UNIVERSITY OF DENMARK G. Singh Bhander LCM2003 Conference Seattle, USA 22 – 25 September 1 DEPARTMENT OF MANUFACTURING ENGINEERING AND MANAGEMENT.
Architecture Business Cycle
Chapter 3: Software Maintenance Process Omar Meqdadi SE 3860 Lecture 3 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Tomorrows technologies for today Automotive Electronics Market and Technologies Trends.
 To explain the importance of software configuration management (CM)  To describe key CM activities namely CM planning, change management, version management.
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
Using a Project Model for Assessment of CDIO skills Tomas Svensson, Svante Gunnarsson Linköping University Sweden June
Organizing the Requirements Information 1. Need for Organizing Requirements  Many stakeholders are involved in most projects.  They must reach agreement.
1 Automotive News - May 20, 2008 Enhancement of Virtual Development in FGA Harald J. Wester Chief Technical Officer Fiat Group.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
1 Advanced topics in OpenCIM 1.CIM: The need and the solution.CIM: The need and the solution. 2.Architecture overview.Architecture overview. 3.How Open.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
1 Software Engineering Ian Sommerville th edition Instructor: Mrs. Eman ElAjrami University Of Palestine.
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 systems analysis 1 what is systems analysis? preparation of the system’s requirements/definition,
Sanchez and Mahoney (1996). Modularity, flexibility, and knowledge management in product and organization design. SMJ.
Effort.vs. Software Product “Quality” Effort Product “Quality” Which curve? - linear? - logarithmic? - exponential?
HDM-4 Institutionalization. 2 HDM is for decision-support tool; not decision- making Institutionalization process should ensure that outcome is:  sustainable,
Scenario-Based Analysis of Software Architecture Rick Kazman, Gregory Abowd, Len Bass, and Paul Clements Presented by Cuauhtémoc Muñoz.
Improving Cosmetic Quality in the Automotive Design Process Stephen Taylor MPhil Study CAD Centre, University of Strathclyde.
Toulouse, September 2003 Page 1 JOURNEE ALTARICA Airbus ESACS  ISAAC.
Advanced Simulation Techniques for the coupled Fatigue and NVH Optimization of Engines. K+P Software, Schönbrunngasse 24, A Graz / Austria Tel.:
1 Chapter 8 Building the Analysis Model (1) Analysis Concepts and Principles.
Case Study SummaryChallenges Magellan delivers innovative GPS technology for vehicle navigation, outdoor recreation, iPhones, and GIS. With rising demand.
Information Architecture of ERP Systems at Globalised Enterprises in a Small EU Member State Bálint Molnár 1, Gyula Szabó 2 1 Eötvös University of Budapest,
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Rekayasa Perangkat Lunak Kuliah 2. Outline of this presentation Attributes of Good Software Why Software Engineering ? What is Software Product ? Software.
COMPANY INTERNAL — CONFIDENTIAL Unauthorized Use and Disclosure Prohibited Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. COMPANY INTERNAL.
CONTENTS: 1.Abstract. 2.Objective. 3.Block diagram. 4.Methodology. 5.Advantages and Disadvantages. 6.Applications. 7.Conclusion.
Software Design and Architecture
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
Decisive Themes, July, JL-1 ARTEMIS Decisive Theme for Integrasys Pedro A. Ruiz Integrasys July, 2011.
INTRODUCTION The economies of ALL developed nations are dependent on software. More and more systems are software controlled Software engineering is concerned.
BIL 424 NETWORK ARCHITECTURE AND SERVICE PROVIDING.
Global Anti-Lock Braking System (ABS) Market (2016 – 2022)
ANTI-COLLISON AND BRAKING SYSTEM
IT 440: SYSTEM INTEGRATION
Why PC Based Control ?.
Automotive Development Overview
Electronics Engineering Division
Safety-Critical Real-Time Support
Chapter 8 Software Evolution.
Embedded Systems Design and Development
Lecture 5: Organizational Impacts of Knowledge Management
Chapter 2: Building a System
Building a “System” Moving from writing a program to building a system. What’s the difference?! Complexity, size, complexity, size complexity Breadth.
CLASS® Compressible Liquid Adaptive Suspension System
European Week of Regions and Cities
Presentation transcript:

Drive by Wire – “What Will Be Its Impact On Tomorrow’s Vehicles?” Craig Stephens Ford Motor Company

2 Why Drive by Wire Through the use of of electronics and software in drive by wire systems we can offer our customers new functions and improved attributes: – Fuel economy – Ride and handling – Driveability – Interaction with the environment and vehicle surroundings

3 Drive by Wire Considerations What value or enhancement does the system provide to the customer? How does the customer interact with the system? How do we manage the added system complexity? These new systems must be safe and reliable

What can we learn from other Industries?

5 Unique Automotive Factors Operator training Service & after market modification Cycle time Production volumes Product use

6 Complexity Considerations Safe operation must be ensured as the complexity of the systems increases: –Increased complexity creates new modes that have to be assessed and managed with respect to safety, reliability and availability –Interactions between previously separate subsystems (e.g. brakes & powertrain) create coupled modes which must be managed Has consequences for design, release, manufacture and service The management of the complexity will inevitably rely heavily on software for design, analysis,and implementation The increased complexity is often invisible

7 Techniques & Tools Techniques that help bridge the gap between written functional requirements and the end design Techniques to analyse behaviour in subsystems and systems that exhibit modal and continuous behaviour Hardware and Software in the loop systems to enable system analysis and testing

8 Standards & Best Practices Customer interface Architectures Operating systems and communication protocols Process Tool interfaces Model standards

9 Conclusions