Functional specs and content requirements

Process Deep Dive | Vehicle Passport | Stage 2

Form follows Function

Form follows function. Always. No AI will ever change that. For this stage of the deep dive, we’ll treat the Vehicle Passport as a first-generation disruptor. That means the exact technical stack and functional layers will be defined after proof-of-concept. For now, we’ll generalize the likely technical stack and functional layers needed to support the Vehicle Passport experience.

Related material

[Content]

Technology: Exploitation

Technology should be exploited in order to:

Reduce (and likely remove) the burden of trade-in valuation distractions, errors and frustrations littering vehicle purchase funnels AND

Technology should be exploited in order to:

Create more personalized transaction experience across buy, sell and trade-in funnels

Technology: Hypothesis

Introducing new Vehicle Passport functionality will likely need to leverage smart car live cockpits, native mobile Apps and other emerging IoT technologies to digitally collect, track, interrogate and manage a vehicle’s static and dynamic data attributes from cradle to grave.

Additionally, it is hypothesized that a digital Vehicle Passport could broadcast sell/buy intentions to the world around it — creating a robust peer-to-peer, crowd-sourced buy/sell network that would drive direct sales engagements.

Examples of Static Attributes (these attributes are ‘hard’ and would not likely change over time due to events, conditions and activities):

VIN, Manufacturer, Origination Date, Year, Make, Model, Vendor, Color, Trim, Extras, Purchase Date (cradle), Sales Agent (cradle), Purchase Location (cradle), etc.

Examples of Dynamic Attributes (these attributes are ‘soft’ and would likely change over time due to events, conditions and activities):

Mileage, Number of Owners, Photos, Trade-In Value, Number of Accidents, After Market Installs, Purchase Date (resell), Purchase Location (resell), Sales Agent (resell), etc.