There’s by no means a uninteresting second on this business. The know-how is advancing (see examples right here and right here), authorities laws are being developed (see replace on U.S. laws right here), and new partnerships proceed to be shaped (e.g., Ford teaming with Walmart and Postmates). New demonstration and testing actions are cropping up every day (see examples right here and right here) and the media continues to cowl all of this with unwavering dedication! It’s an thrilling time.
Trade is advancing their pursuits whereas governments – internationally and in any respect ranges – are struggling to maintain up. The query of requirements creeps into lots of the discussions; nonetheless, there was little agreed-upon. The subjects that typically are mentioned as needing requirements embody: security (usually), cybersecurity, knowledge privateness, linked automobiles (DSRC), signage, and even requirements on how the automobiles talk with different street customers. These are all big subjects independently and the implications of those requirements, as a rule, may have implications for a lot of industries (not simply the driverless business).
Who ought to set up these requirements? Seemingly, it is smart for the federal government to take the lead as a impartial third get together representing the higher good. However, business is getting patents for all facets of the driverless know-how, together with, for instance, pedestrian communication instruments (see hyperlink right here), which might affect requirements. Ford can also be growing their very own customary for a way driverless automobiles talk with different street customers, however they’re encouraging the business to undertake them (see hyperlink right here). There are additionally examples the place authorities works with business teams and requirements organizations (e.g., linked automobile requirements or cybersecurity framework…not requirements!). And right here’s one other instance: the RAND Company, on the request of Uber’s Superior Expertise Group, developed an “firm impartial framework for AV security” (hyperlink right here).
I’m certain we’ll proceed to see each number of strategies to growing requirements. My hope is that requirements usually are not developed too late within the know-how improvement course of, the requirements might be agreed-upon by most stakeholders, and that the requirements don’t restrict innovation or development. What are your ideas on how/when requirements must be developed?
Observe: I’ll be on the Shopper Electronics Present (CES) – will you? Please electronic mail me (lauren.isaac@easymile.com) in case you’d like to fulfill up!
