CarPass is a system currently being rolled out in Germany and eventually across the EU. The aim is to create and store a complete digital record of the service history of every vehicle owned by the (current) owner. However, the data is updated by workshops, dealers and insurance companies and eventually passed on to the new vehicle owner when the vehicle is sold. While the long-term goal is to capture all service and component information about the vehicle - i.e. create the vehicle's digital twin - the initial data is the original manufacturer information, service history, mileage, number of owners bangladesh telegram screening and every modified/repaired part of the vehicle since production. An initial business focus is to combat mileage fraud, which currently costs billions of euros. In the longer term, the current vehicle owner is to be granted the right to view a complete history of the vehicle without compromising the privacy of previous owners.
At first glance, CarPass seems like a simple application: create a relational database and give car owners and relevant organizations appropriate access to it. But the reality is anything but simple.
Although the current data is limited, the future scope envisages a wide range of data types, many of which will vary from vehicle to vehicle. The data is thus semi-structured across the different types and variable over time. Such features point to a document repository rather than a relational database as the base technology to avoid issues such as schema switching and null value propagation. However, a traditional document repository cannot solve data protection issues if all vehicle data associated with a known owner-vehicle combination is in a single document/order. Some or all of this data has personal characteristics under the GDPR, as determined by the Lower Saxony State Data Protection Authority [2] . In addition, the authorization to access or update different parts of the vehicle dataset must be assigned to different parties and revoked over time. Even if this were technically feasible in a traditional document repository, the administrative effort for access management under GDPR would be enormous.