User and Data stories for a Practical Autonomous Vehicles Ecosystem — Part 1

In this post, I am trying to highlight list of approaches when thinking about the data stories for autonomous vehicles.

Data is infinite — We can, depending on the industry choose to be either consumers of or generators of this data. In my area of industry, If one would sit down to write data stories for autonomous vehicles, I wonder what those stories be, so decided to sit down and do that myself.

Data ecosystem of AV — prediction

First of all, the data sources and the justification would be so that, in AV ecosystem, data :

1. Gets a vehicle from state A to state B as well as from source to destination — logical vs physical state transition.
2. Data availability real time — some vehicle specific data need to presented to the vehicle in real time and some data need to be accessible at later instance through generic interfaces.
3. Data that scales — Real time availability and size of data, both need to scale with the right owners in mind — Network providers, Subscribers to services/APIs, Any ML/filters and infrastructure requirements and limitations.
4. Determines the semantics, rules and the lay of the land for AV operations for this vehicle’s application in the real world.
5. Data that develops and builds the vehicle intelligence and peer vehicle’s operational intelligence and determines not-so-intelligent components and outcomes and recovers from it.
6. That enables vehicle to follow the rules and defends the vehicle state when contradicated in other system.

That was a good sketch of outlines for the operational and functional needs of the AV ecosystem’s data needs. Ownerships and intuitions about its life and consumptions would determine who owns which part and hence owners of the stories and outcomes.

Let’s dive deep into the use cases and examples in the next post…