...

1. Data Models: the live data models - VSS as the abstracted view of the vehicle, along with other adjacent data models such as personal data.
2. Persistence: history of the model and signals etc - historical and cached timeseries data.
3. Application logic / APIs: for accessing the data such as VISS or GraphQL.

It is recognised that additional features, such as synchronisation are absolutely desirable and have been a part of discussions in the Data Architecture group. For this proposal a base feature set is described to help readers quickly grasp the concept. If the proposal proceeds then additional details will be created collectively based on interest and participation.

Of course the Service has connections southbound to data feeders integrating it into lower level parts of the vehicle. As well as northbound to

The Service in context

Implementation Concepts

...