140 likes | 325 Views
Response 4 – an AdaptIVe project. Andreas Knapp, RD/EDF October 1 st , 2013, VRA workshop. History of Response projects Activites based on Response 3 Plans for Response 4 Further activites. Outline. 1. 2. 3. 4. The Response story. 1978: ABS. 1981: Airbag. 1995 : ESP.
E N D
Response 4 – an AdaptIVeproject Andreas Knapp, RD/EDF October 1st, 2013, VRA workshop
Historyof Response projects Activitesbased on Response 3 Plans for Response 4 Further activites Outline 1 2 3 4 Titel der Präsentation in CorpoS Regular 9pt | Abteilung | Datum
The Response story 1978: ABS 1981: Airbag 1995: ESP 1996: Brake Assist 1999: Distronic 2000: Lane dep. warn. 2013: Avail. ADAS in a new S-Class 2006: Coll. mitigation 2010: Blindspot protect. 1978 1981 1995 1996 1999 2000 2006 2010 2013 Response: User- System – Law Response 2: Introductionscenariostowards a CoP Response 3: Code of Practice for ADAS Images: Mercedes-Benz Titel der Präsentation in CorpoS Regular 9pt | Abteilung | Datum
By 2006 „CoPfor ADAS“ was a projectdeliverableof IP PReVENT 2006-2009: ApplicationofCoPisevaluated in formerpartnercompanies;CoPisupdatedwithexperiencesfromevaluation ACEA (the European Car ManufacturerAssociation) endorsestheCoP Available on ACEA homepage „Inofficial“ German translationavailableforcompanyinternaluse CoPconsideredasinputfordevelopmentof ISO 26262-2011 Proveduseful also forcombinationsof ADAS Follow-upactivitiesto Response 3 Reference: http://www.acea.be/news/news_detail/acea_endorses_response_code_of_practice_for_advanced_driver_assistance_syst/ Titel der Präsentation in CorpoS Regular 9pt | Abteilung | Datum
The storycontinues – Response 4 • Targeted at highly and fully automated driving (beyond ADAS) • Proposed for funding as a subproject of IP AdaptIVe • Main objectives • Identify steps that need to be adopted to allow the market introduction of automated driving systems • Identify changes to provide legal certainty for those that are bringing automated driving systems into the market. Introduction of ADAS 2006 2013 Automated driving Response: User- System – Law Response 2: Introductionscenariostowards a CoP Response 3: Code of Practice for ADAS Response 4: Code of Practice for ADAS Image: Mercedes-Benz Titel der Präsentation in CorpoS Regular 9pt | Abteilung | Datum
Project outline Response 4 • System classification& safetyvalidation • Unambiguousclassificationofautomateddrivingfunctions • Technical systemlimits • Definerequirementsforthevalidationofautomateddriving • Legal aspects • Legal aspectsfortheintroductionofautomateddriving • Productliability • Data privacy and data security • Road traffic law/regulatory law Titel der Präsentation in CorpoS Regular 9pt | Abteilung | Datum
Further activities • UNECE WP.1Vienna ConventionArticle8, § 5 andArticle 13, §1: • Accordingtocommoninterpretation, driverassistanceandpartiallyautomatedsystems (the driver must monitor the system permanently) areaccepted. • Not compliantare high- andfullyautomatedsystems , wherethedriverisat least temporary not in theloop. • Timeline WP.1: • 23. September 2013, Geneva: Proposednewsystemcriteriaforcompliance • Conformity with the technical provisions of UN regulations • Or such systems can be overridden or switched off. • 4.-6. December2013, New Delhi: Aimistheadoptionoftheproposal Titel der Präsentation in CorpoS Regular 9pt | Abteilung | Datum
Vienna Convention: Relevant Content forAutonomousDriving • Withregardtoautonomousdriving, 2 requirementsareimportant: • Article 8, Paragraph 5: Every driver shall at all times be able to control his vehicle or to guide his animals. • Article 13 (Speed and distance between vehicles), Paragraph 1:Every driver of a vehicle shall in all circumstances have his vehicle under control so as to be able to exercise due and proper care and to be at all times in a position to perform all manoeuvresrequiredofhim. … • Accordingtocommoninterpretation, driverassistanceandpartiallyautomatedsystems (the driver must monitor the system permanently) areaccepted. • Not compliantare high- andfullyautomatedsystems , wherethedriverisat least temporary not in theloop.
Vienna Convention: Time Line Change Proposal • 23. September, 2013, WP.1, Geneva: • Informal document 4, submittedbyBelgium, France, Germany, Italy, Russian Federation andSweden • Introducesnewsystemcriteriaforcompliancewith Art. 8, paragraph 5 andArticle 13, paragraph 1: • conformity with the technical provisions of UN Regulations (1958 agreement) or with the technical provisions of UN Global Technical Regulations (1998 agreement) • or: such systems can be overridden or switched off. • 4.-6. December 2013, WP.1, New Delhi: • Aimistheadoptionoftheabovementionedproposalatthenextmeeting in December.
Backup Backup MB_presentation_slides_german.pot
Tabellenunterschriften werden in CorpoS 9 pt gesetzt. Tabellenunterschriften werden unterhalb der Tabelle mit einem Abstand von 0,4 cm platziert. Tabellenüberschrift in CorpoS bold 15pt Titel der Präsentation in CorpoS Regular 9pt | Abteilung | Datum
Corporate Grundlagen Grundfarben Textfarbe „Dark Grey“ (RGB: 102/102/102) Textauszeichnungs- und Überschriftenfarbe „Anthracite“ (RGB: 51/51/51) Hintergrundfarbe „White“ (RGB: 255/255/255 ) Objektfarbe 1 „Light Grey“ (RGB: 234/234/234) Objektfarbe 2 „Soft Grey“ (RGB: 182/187/193) Objektfarbe 3 „Solid Grey“ (RGB: 153/153/153) Akzentfarbe „Midnight Blue“ (RGB: 0/51/102) Akzentfarbe „Cyan“ (RGB: 0/173/239) Akzentfarbe „Dark Cyan“ (RGB: 0/130/230) Akzentfarbe „Error Red“ (RGB: 159/0/2) MB_presentation_slides_german.pot
Text Mögliches Szenario … Ziel xxx ! xxx xxx • xxx • yyy M. Pohl, Team FuSi, GR/PSP / Datum (Tag.Monat.Jahr)