28 lines
1.5 KiB
Markdown
28 lines
1.5 KiB
Markdown
# Vehicle Data Platform Product Spec
|
|
|
|
## Visual Direction
|
|
|
|
The UI is a professional vehicle data operations console. It uses Semi UI as the component base, a restrained gray-white control-room palette, dense but readable tables, right-side drawers for detail, and blue-cyan accents for primary actions. It should feel closer to a cloud data console than a marketing dashboard.
|
|
|
|
## Primary Screens
|
|
|
|
1. Dashboard: KPI summary, protocol distribution, vehicle map preview, quality issues, and link health.
|
|
2. Vehicles: table-first identity and vehicle registry.
|
|
3. Realtime: table/map switch for current vehicle state.
|
|
4. Vehicle Detail: identity header and tabs for latest state, history, raw, mileage, and quality.
|
|
5. History: location and raw-frame query workspace.
|
|
6. Mileage: daily and range mileage analysis.
|
|
7. Quality: data quality and link health workspace.
|
|
|
|
## Domain Principle
|
|
|
|
The product model is vehicle-first. GB32960, JT808, and Yutong MQTT are ingestion sources for one vehicle service, not separate business products. The UI should lead with VIN, plate, online state, location, mileage, and data quality; protocol appears only as source attribution, diagnosis, and raw-frame traceability.
|
|
|
|
## Interaction Rules
|
|
|
|
- Tables are the default data surface.
|
|
- Filters stay above the table.
|
|
- Details open in a right drawer unless a full route is needed.
|
|
- Error and empty states must be explicit.
|
|
- No decorative hero, no oversized marketing card layout, no dark large-screen style.
|