Research project PEGASUS EFFECTIVELY ENSURING AUTOMATED DRIVING.

Transcription

1 Research project PEGASUS EFFECTIVELY ENSURING AUTOMATED DRIVING.

2 Key Figures 42 Months Duration January 1, 2016 June 30, Partners OEM: Audi, BMW, Daimler, Opel, Volkswagen Tier 1: Automotive Distance Control, Bosch, Continental Teves Test Lab: TÜV SÜD SME: fka, imar, IPG, QTronic, TraceTronic, VIRES Scientific institutes: DLR, TU Darmstadt 12 Subcontracts i.a. IFR, ika, OFFIS Project Volume approx. 34,5 Mio. EUR Funding: 16,3 Mio. EUR Personnel Deployment approx man-month or 149 man-years 2

3 Current State of Development of HAD Prototypes Lab / Proving Ground Products current status 3

4 Goals and work contents of PEGASUS Current State of Development of HAD Prototypes Lab / Proving Ground Products Multitude of prototypes built by OEM with HAD-functionality Evidence, that HAD is technologically possible Partially tested in real traffic situations Test drives involve backup safety driver at all times Individual analyses to optimize prototypes Current test methods/ proving grounds do not provide enough test coverage for all HAD features currently in focus There is no procedure for adequate testing (particularly performance) of HAD-systems No release or introduction of variety of HAD features without sufficient assurance current status 4

5 PEGASUS - Selected Goals of the Project Development of a procedure for the determination of design criteria and establishment of quality measures. Considering the driver in regards to his abilities. Design of the development process for the release of highly automated vehicle systems. Conceptual design, assembly and demonstration of building blocks for an efficient tool chain for simulation, proving ground and field test. Embedding of findings into the industry. Distribution and pioneering of standardization. 5

6 Central Issues of the Project What level of performance is expected of an automated vehicle? How can we verify that it achieves the desired performance consistently? Scenario Analysis & Quality Measures Implementation Process Testing Reflection of Results & Embedding What human capacity does the application require? What about technical capacity? Is it sufficiently accepted? Which criteria and measures can be deducted from it? Which tools, methods and processes are necessary? How can completeness of relevant test runs be ensured? What do the criteria and measures for these test runs look like? What can be tested in labs or in simulation? What must be tested on test grounds, what must be tested on the road? Is the concept sustainable? How does the process of embedding work? 6

7 SP 1 Scenario Analysis and Quality Measures Deduction of requirements based on the accepted measure of quality Determination of safety level through assessment of probability of occurrence and mechanical manageability in critical situations Deduction of an accepted quality measure for automated driving features Determination of human and mechanical performance as well as effectiveness (accident avoidance potential) Determination of critical traffic situations Description of application scenario (sample application: Autobahn- Chauffeur + enhanced application scenario) 7

8 SP 2 Implementation Process Analysis of modification needs of existing metrics and automobile series development processes 1 Transfer of systematic scenario guidelines into process steps in consideration of system classifications and levels of vehicle utilization 2 Transfer of target value parameters into process steps Preparation of requirements definition for simulation, lab tests, testing ground and field coverage 3 4 Refinement of the guidelines for required documentation of process steps Guidelines and Protocols for the documentation of technological state-of-the-art compliance during the development process 5 6 8

9 SP 3 Testing Detailing and completion of test scenarios of subproject 1, including technical quality measures as well as approval criteria Construction and filling of test specification database Establishment and verification of testing methods, interfaces, tools in the lab, on testing grounds and in real traffic Compilation of a test catalog and requirements for lab, testing ground and field coverage Construction of reference elements for practical testing and demonstration of functions Testing in the lab, on proving grounds and on the street Development and coordination of industrywide established models, tools and interfaces for the simulation 9

10 SP 4 Reflection of Results & Embedding Statement about the distribution ratio between the applied test methods (from simulation to testing ground to field test) Proof of Concept Assessment, whether the test goal can be achieved with the utilized processes and methods in PEGASUS Assistance with embedding of acquired results with our project partners Verification of methods to identify relevant situations, quality and criticality measures for the assurance of HAD features Lessons learned regarding the implementation of the results in existing corporate structures 10

11 PEGASUS Project Summary Testing and validation of automated vehicles requires new methods and tools for an efficient safeguarding process. Core element of the circuit process is a database and a data processing chain for the relevant scenarios. Available and known methods and tools can be utilized in the overall circuit process and therefore increase effectiveness. The data processing chain needs to be able to process different data sources and heterogeneous data quality in order to provide common test specifications. The presented database concept allows an efficient processing of high data volumes by means of a flexible tool chain. 11

12 Contact: fka Forschungsgesellschaft Kraftfahrwesen mbh Aachen Adrian Zlocki