> > > Hello Everyone – > Presentation on Wednesday, March 9 @ 5:00 pm - 6:00 pm PST.Product safety > includes electrical, mechanical, chemical and other physical hazards, of > course. But what about software – especially updates that must be sent to > users quickly, effectively, efficiently and safely? > For example, how much of your car’s functionality (and safety) depends on > its software and firmware? If your car has a safety problem, don’t you > want it fixed right away? > Join us for this short, fascinating presentation about how those > Over-The-Air (OTA) updates can be done. > Best regards, > John McBain, IEEE PSES SCV Chapter Secretary > ================================== March 9 @ 5:00 pm - 6:00 pm PST > *Presentation: OTA Software updates – the big picture* > > What is needed to get a system ready for over-the-air (OTA) updates? There > is an entire chain that has to be designed and maintained! > > Mobile phones and smart television sets are receiving continuous > improvements and patches and downloading the newest firmware as soon as it > is available. The automotive world is just starting to explore the vast > opportunities of updateable products. Customers soon will be able to choose > a car that is “final” when they buy it, or a car that offers new > functionality during the time of ownership. An important driver for the > need of OTA updates is the growing integration of transportation devices > with each other and their environment, and the associated security risks. > If there is a new vulnerability discovered in a product, it must be closed > immediately to prevent risk to the users and the business. > > *Presenter: **Florian Rohde* > > An Engineering Manager for over 15 years in several global > automotive-associated companies, Florian was the architect of the system > that allows Tesla to test and release vehicle firmware packages within > hours. > > At Siemens and Continental he managed the validation of the first > generation electric power steering systems. From 2012 to 2018 he > implemented a continuous validation concept at Tesla in his role as senior > manager of the vehicle firmware validation. The solutions put in place are > powerful enough to allow Tesla to launch vehicle software packages within > 24 hours from code change to over-the-air customer deployment. The > automated test coverage includes all static vehicle functionality, UI/UX, > chassis and powertrain as well as autopilot functionality. > > After Tesla Florian served as director of system integration and > validation at NIO before joining iProcess in 2019. He now is responsible > for the system development, integration and validation consulting at > iProcess. > > *Join Zoom Meeting* > Topic: Evaluating OTA Software Solutions > Time: Mar 9, 2022 05:00 PM Pacific Time (US and Canada) > > Link: > https://us02web.zoom.us/j/83512682854?pwd=aExXRmpxSnZPSkYxamFiaSttMzBPZz09 > <https://ieee.us15.list-manage.com/track/click?u=7e5118a091cb7d92d9d57d39e&id=30b7f45a18&e=0f3f2a34dc> > > Meeting ID: 835 1268 2854 > > Passcode: 496110 > > Dial by your location > > Find your local number: https://us02web.zoom.us/u/kby5R4dMR0 > <https://ieee.us15.list-manage.com/track/click?u=7e5118a091cb7d92d9d57d39e&id=4da018267e&e=0f3f2a34dc> > >
- ---------------------------------------------------------------- This message is from the IEEE Product Safety Engineering Society emc-pstc discussion list. To post a message to the list, send your e-mail to <[email protected]> All emc-pstc postings are archived and searchable on the web at: http://www.ieee-pses.org/emc-pstc.html Attachments are not permitted but the IEEE PSES Online Communities site at http://product-compliance.oc.ieee.org/ can be used for graphics (in well-used formats), large files, etc. Website: http://www.ieee-pses.org/ Instructions: http://www.ieee-pses.org/list.html (including how to unsubscribe) List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the list administrators: Scott Douglas <[email protected]> Mike Cantwell <[email protected]> For policy questions, send mail to: Jim Bacher: <[email protected]> David Heald: <[email protected]>
