2.6 KiB
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
- Dashboard: KPI summary, protocol distribution, vehicle map preview, quality issues, and link health.
- Vehicles: table-first identity and vehicle registry.
- Realtime: table/map switch for current vehicle state.
- Vehicle Detail: identity header and tabs for latest state, history, raw, mileage, and quality.
- History: location and raw-frame query workspace.
- Mileage: daily and range mileage analysis.
- 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.
Vehicle service coverage is always shown at VIN level. A vehicle may have one or more ingestion sources, but upper product views should summarize source count, online source count, last seen time, and binding status before drilling into protocol-specific diagnostics.
Vehicle lists should expose a vehicle-level service status derived from binding and source coverage: identity required, no data source, offline, degraded, or healthy. Protocol tags remain attribution and troubleshooting context, not the primary status.
Vehicle detail and top search context should expose one source-consistency conclusion, such as 来源一致, 部分来源离线, or 里程差异偏大. This diagnosis comes from sourceConsistency and turns GB32960, JT808, and Yutong MQTT into explainable evidence under one vehicle service rather than three competing realtime products.
Vehicle service lists and dashboard previews should label protocol coverage as 来源证据. The row should make the vehicle service coverage explicit, for example 2/3 来源在线, while protocol tags remain compact evidence labels underneath the same vehicle row.
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.