Kyle Taylor

There's a good coverage of the interview I gave SAE International in anticipation of my talk at #WCX in #Detroit last week. We discuss how traditional and new automotive companies are different but also beginning to learn from one another. In that interview I also point out that established automakers are exceedingly practiced at R&D, design, engineering, manufacturing and distribution, a process that is sometimes overlooked, dismissed, ignored by newcomers. And I also explain that newcomers are diving headfirst into the digital world, and with software, they can innovate much more quickly because coding something new goes much faster than building new hardware. Read the article under the link below and let me know what you think. #automotive #engineering #mobility #electricvehicles #automateddriving #detroit #siliconvalley https://lnkd.in/eSC5zfRD

37

Californian drivers appear to be losing some enthusiasm for Tesla. A California Auto Outlook report shows year-over-year Tesla registrations are down again in the state. The report, published on Monday by the California New Car Dealers Association, summarizes first-quarter vehicle registration figures statewide. The report said Tesla saw a 7.8% dip in sales in California in the first quarter, down from 54,265 in the last quarter of 2023 to 50,025 in Q1. The drop follows last quarter's 9.8% decline. Read more in Business Insider https://lnkd.in/exaHWtm5

10

1 Comment

General Motors hiring Tim Twerdahl from Apple as their new vice president of product management might appear counterintuitive at a time when the company is reducing headcount by 1,000 software engineers. It isn’t. Twerdahl’s background with ApplePay among other post-sales services hints at #gm ‘s desire to keep customers engaged with post-vehicle sale digital products and services. What those could be aren’t yet known. But the company now has a digital direction that can build on the legacy of the auto industry’s first interactive and telematic based service, OnStar. #electricvehicles #ev #evs #automotiveindustry #oem #softwaredefinedvehicles #autonomousvehicles #forecasting #autoforecastsolutions

14

Wow. VW Group will invest up to $5 billion in Rivian to form a new, equally controlled joint venture sharing #EV architecture + software. JV's HOT TAKE: (a) Rivian gets the cash it needs before the R2 goes into production 2 yrs hence; (b) VW desperately needs software help on SDVs; (c) VW gets a US-based JV to build new products; so (d) Is THIS what underpins the new (and so far largely unknown) Scout Motors Inc. brand? More to come on this, for sure. #electriccars #electricvehicles #autoindustry #automotive #VWgroup #Rivian https://lnkd.in/eJsauZfs

405

45 Comments

Thanks for pointing this out to the community, Philip Koopman In the comments to Phil's post, I read a lot about who's at fault. It's a relevant question, but in my view it's more important that we learn from it as #automateddriving community and find solutions that decrease the likelihood of such mishaps. Here are the insights that we at TNO got from this: 1️⃣ European regulation makes sense. The recent regulation introduces the concept of "foreseeable scenario" and requires a safe reaction if it's a "preventable scenario". As was mentioned by someone, overspeeding is foreseeable. 2️⃣ European regulation doesn't make sense 😉. Overspeeding in general is a foreseeable scenario, but how to make sure that you can deal with all relevant variations of that scenario. In our view there is only one solution: measure in your actual operational domain. We are publishing our new position paper on Scenario-Based Safety Assessment with real-world data soon (send me a message if you'd like to receive a copy). 3️⃣ Public opinion and regulators ask for more than traditional safety standards can offer. ISO 26262 is about unreasonable risk of harm to people and is aiming at avoiding collisions. This example shows that safe driving is also about careful and responsible driving. In European regulation this is addressed with the requirement of being as good as a "competent and attentive" driver. Obviously the challenge for us as community is to translate this into engineering terms. If you are interested in more details and the innovations we are developing on the road to safe automated driving, join our upcoming online sessions > https://tno.to/big #TNO #AV #AutomatedDriving #SmartMobility https://lnkd.in/eRrfX9qC

34

6 Comments

After some exchanges in the post below, Antonello De Galizia, Ph.D. and I had an interesting talk on safe #automateddriving. Because the community indeed struggles to navigate the complexity of this domain and to call things by their name, we didn’t want to spread the confusion and leave the discussion unsolved. We found out to be very well aligned and thought it was worth sharing our conclusions with you:   🚗 While both ISO26262 and ISO21448 are strong guidelines for ensuring safety during the development and design of automated driving system, they address different sources of risk, and these should be all tacked according to best practices and state of the art engineering. 🚗 While both standards are in place and provide the key concepts for safe automated driving, the complexity is in their implementation. This is especially true in the case of ISO21448, due to the lack hands-on experience. For example, investigating all possible scenarios within the target operational domain (TOD), considering all relevant combinations of the relevant factors (e.g., environmental conditions) is key to study the system functionalities and claim absence of unreasonable risk. 🚗 Following (to the letter) these standards is not sufficient to achieve truly safety automated driving. In fact, limiting the safety process only to cases where a malfunctioning (26262) or hazardous behavior (21448) result in safety relevant hazards (i.e., severity classes S1, S2 and S3) would mean that situations where unpredictable, irresponsible, or unlawful driving actions would be neglected if not found to be directly leading to harm. These need to be addressed too for a much more solid and proactive safety approach.   We hope to have contributed to a little more structured discussion on safety in this way. Feel free to reach out, Antonello & Henk Here is the link to the original post including our discussion: https://lnkd.in/e8ekRTtp

22