
π Automotive Β· Database ERD
A database schema for a car dealership: vehicles in stock, customers, test drives, bookings, sales and service jobs.
Drawing diagramβ¦
ERD for a car dealer management system: VehicleModel and Vehicle (VIN, colour, status), Customer, Lead, TestDrive, Booking with payment, Sale with invoice and delivery date, and ServiceJob for vehicles brought back for servicing.
erDiagram
VEHICLE_MODEL ||--o{ VEHICLE : "stock of"
CUSTOMER ||--o{ LEAD : raises
LEAD ||--o{ TEST_DRIVE : includes
VEHICLE ||--o{ TEST_DRIVE : "used in"
CUSTOMER ||--o{ BOOKING : makes
VEHICLE ||--o| BOOKING : "reserved by"
BOOKING ||--o| SALE : "becomes"
VEHICLE ||--o{ SERVICE_JOB : "serviced in"
VEHICLE {
string vin PK
int model_id FK
string colour
string status
}
CUSTOMER {
int id PK
string name
string mobile
}
BOOKING {
int id PK
int customer_id FK
string vin FK
decimal booking_amount
}
SALE {
int id PK
int booking_id FK
decimal invoice_amount
date delivered_on
}
SERVICE_JOB {
int id PK
string vin FK
int odometer
date job_date
}Every state of an electric vehicle charging session at a public charger, from plug-in to payment, including faults and idle fees.
A connected vehicle platform: the telematics unit in the car, the cloud services that collect data and send commands, and the owner's mobile app.
How a carmaker updates vehicle software over the air: campaign targeting, owner consent, download, safe installation and reporting.
A charge point operator's platform: chargers speaking OCPP, a central management system, driver app, payments and roaming.
Where each part of a fleet management system runs: GPS devices in trucks, cloud services for tracking and analytics, and apps for managers and drivers.
What happens when a rider books a cab: fare estimate, driver matching, pickup, the trip and payment.