EE Architecture Design - An Engineering Service Provider s Perspective. Dr.-Ing. Jan Gačnik, 7th Vector Conference, Stuttgart, November PDF

Description
EE Architecture Design - An Engineering Service Provider s Perspective Dr.-Ing. Jan Gačnik, 7th Vector Conference, Stuttgart, November 2014 EE Architecture Design A Business for ESP? An appropriate EE

Please download to get full document.

View again

of 14
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Information
Category:

Computers & Electronics

Publish on:

Views: 10 | Pages: 14

Extension: PDF | Download: 0

Share
Transcript
EE Architecture Design - An Engineering Service Provider s Perspective Dr.-Ing. Jan Gačnik, 7th Vector Conference, Stuttgart, November 2014 EE Architecture Design A Business for ESP? An appropriate EE architecture is a key factor for a brand s identity! Should an ESP work in an OEM s core competence area? IAV 11/2014 skö VI-A 2 Yes from a Different Perspective OEM: EE architecture design in DEPTH (Basically) one philosophy, methodology, tool chain In deep access to technology and product strategy ESP: Adding value in WIDTH & SPECIALITIES Range of customers: broad range of philosophies, methodologies, tooling, technologies and boundary conditions Range of service: from routine work to sophisticated special services IAV 11/2014 skö VI-A 3 WIDTH: From European Style OEM Architecture Patterns ESP Architecture Derivatives ESP focus is on architecture derivatives, mastering several patterns. IAV 11/2014 skö VI-A 4 WIDTH: to Global Style OEM Architecture Patterns ESP Architecture Derivatives ESP focus is on architecture patterns. Patterns reflect global market needs. IAV 11/2014 skö VI-A 5 WIDTH: Scope Setup Experience E/E Concept Benchmark Architecture Distr. functions Series Development Functions Systems Network Integration & Test Functions Systems Network Our Setup One common business unit for the whole chain ~ 200 engineers ~ 15 yrs of experience Global activities Tooling & infrastructure Some of our Experience Vehicle classes Passenger cars commercial vehicles Sports cars Markets / Customers (OEMs) Europe China, Japan, India, Brazil IAV 11/2014 skö VI-A 6 WIDTH: Customer Benefit 1. Analyze 4. Validate Range of services EE architecture: benchmark, concept design Vehicle network design Distributed systems design/development EE integration, e.g. cross brand concepts EE integration test 2. Design 3. Verify Value added for customers Access to a wide set of methods & tools Sparring for thinking different Useful customer independent knowledge, e.g. about new markets IAV 11/2014 skö VI-A 7 SPECIALITIES: Facing High Tech Challenges How to integrate high tech E/E features into given EE architectures? IAV 11/2014 skö VI-A 8 SPECIALITIES: Timing Aware Distributed Systems Development How will our brand new feature fit into our EE architecture? Task: Integration of a new feature into a given EE architecture Boundary Conditions E/E architecture not to be changed significantly Performance of legacy features to be kept How to gain confidence it will work? Bus load estimation Engine Control Driver Assist. But what if it becomes tight? Gateway Driver Info Navigation Methodology & tool chain required to analyse overall system timing effects IAV 11/2014 skö VI-A 9 SPECIALITIES: Methodology & Tool Chain Feature / Function Derive logical architecture Define system architectures Analyse system architectures Architecture specification Final system design PREEvision PREEvision Model based architecture design Architecture topologies / function variants Assign timing information / parameters Fixed parameters per topology.arxml SymTA/S Perform timing verification Evaluate quickly different parametrisations with respect to bus load and latencies according to the timing constraints IAV 11/2014 skö VI-A 10 SPECIALITIES: Modeling Workflow ECO Drive Network Designer.dbc E2E ECO Drive PREEvision FCT SYS TIMING Timing Characteristics AUTOSAR.arxml Timing Analysis SymTA/S CAN Define function net Derive system architecture Assign timing information Map communication to PDU Transfer model data Perform timing analysis Create reports Result: Predicted effect of new feature to & bus load Decision support by comparing various scenarios IAV 11/2014 skö VI-A 11 SPECIALITIES: Customer Benefit Addressing timing aspects on overall system level in early function development leads to: Management of project risk Stable requirements for suppliers Proper dimensioning of system resources A valid EE architecture Reliable design decisions Front loading of timing issues in the development process Tool chain: room for improvement by close cooperation of engineering & tool suppliers IAV 11/2014 skö VI-A 12 EE Architecture Design A Business for ESP An appropriate EE architecture is a key factor for a brand s identity. An ESP can help to: Broaden the view on process, tools & methods Enhance performance and output by support of routine work (e.g. derivatives) Adjust to global market needs Receive special services Mediate within a multi brand company Establish a firewall in OEM cooperations IAV 11/2014 skö V-IA 13 Thank You For Your Attention! Dr.-Ing. Jan Gacnik IAV 11/2014 skö V-IA 14
Related Search
Similar documents
View more...
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks