
🚗 Automotive · Deployment · Pro
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.
Deployment diagrams are part of Pro. Anyone can view this one; generating and editing it needs Pro.
Drawing diagram…
Deployment for fleet management: each truck has a GPS tracker reading CAN bus data (fuel, speed, engine hours) and a driver app on a phone. Trackers send data over 4G/MQTT to the cloud: an ingestion service on Kubernetes, stream processing for live location and alerts (overspeed, idling, geofence), a time-series DB and PostgreSQL, a route optimisation service, and a fleet manager web dashboard.
flowchart TB
subgraph Truck[Each truck]
GPS[GPS tracker with CAN bus reader]
DAPP[Driver app on phone]
end
subgraph Cloud[Cloud - Kubernetes]
ING[Ingestion Service - MQTT]
STR[Stream Processing - alerts]
TS[(Time-series DB)]
PG[(PostgreSQL - vehicles, trips)]
ROUTE[Route Optimisation]
API[Fleet API]
end
DASH[Fleet Manager Dashboard]
GPS -->|4G MQTT| ING
DAPP -->|HTTPS| API
ING --> STR
STR --> TS
STR -->|Overspeed, idling, geofence| API
API --> PG
ROUTE --> API
DASH --> APIEvery 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.
What happens when a rider books a cab: fare estimate, driver matching, pickup, the trip and payment.
A database schema for a car dealership: vehicles in stock, customers, test drives, bookings, sales and service jobs.