feat(platform): add vehicle-first statistics overview

This commit is contained in:
lingniu
2026-07-04 16:44:55 +08:00
parent bdb2ebc723
commit d7f1a9279f
4 changed files with 104 additions and 2 deletions

View File

@@ -22,7 +22,7 @@ The platform navigation should use vehicle-service language rather than protocol
6. History Query: historical locations, raw frames, and flattened parsed fields with pagination and field trimming.
7. Alert Events: alert trigger records, affected vehicles, rule evidence, manual state, notification state, and escalation readiness.
8. Notification Rules: alert trigger rules, notification targets, channels, escalation windows, acceptance criteria, and copyable runbooks.
9. Statistics: daily/range mileage, online rate, offline duration, data completeness, and source consistency.
9. Statistics: one vehicle-service statistics workspace covering daily/range mileage, online rate, offline duration, data completeness, and source consistency.
10. Ops Quality: GB32960, JT808, Yutong MQTT, Kafka, NATS, Redis, TDengine, MySQL, AMap, gateway, and runtime health.
See `docs/vehicle-platform-blueprint.md` for the detailed page-level blueprint and phased implementation plan.
@@ -94,6 +94,7 @@ Statistics must stay vehicle-first and evidence-backed:
- Online rate should be computed by vehicle and then broken down by source.
- Data completeness should report missing location, mileage, SOC, speed, and source freshness.
- Source consistency should compare GB32960, JT808, and Yutong MQTT only when the same VIN has multiple sources.
- The statistics page should show these four domains together, because all protocol data ultimately supports one vehicle service view.
## Interaction Rules

View File

@@ -192,6 +192,7 @@ Primary modules:
- Online: online rate, offline duration, no update duration, source online distribution.
- Completeness: location, mileage, SOC, speed, source freshness.
- Consistency: cross-source time delta and mileage delta for multi-source vehicles.
- Statistics overview: show the four domains together so operations users understand that GB32960, JT808, and Yutong MQTT are evidence feeding one vehicle service.
Rule: