feat(platform): align console with vehicle operations center

This commit is contained in:
lingniu
2026-07-04 18:53:52 +08:00
parent 48642726aa
commit 504a49a13c
8 changed files with 70 additions and 26 deletions

View File

@@ -13,6 +13,8 @@ Build one vehicle data management platform around a single vehicle service. GB32
The product direction should reference production telematics and fleet IoT platforms, but keep the Lingniu domain model simple: one vehicle service, multiple source evidences, auditable history, and operational alerts. Realtime data source pages are not product destinations; they are evidence and diagnosis layers under the vehicle.
The current product goal is therefore adjusted to: build a complete vehicle data management center with realtime monitoring, trajectory replay, history query, alert triggering and notification, statistics, and operations quality. GB32960, JT808, and Yutong MQTT remain source evidence and should disappear from the primary user mental model unless the user is diagnosing a specific source.
## Market Reference
Common telematics, fleet-management, and vehicle IoT platforms converge on a small set of durable workflows:
@@ -31,6 +33,12 @@ Relevant references:
- Commercial fleet platforms: live GPS tracking, historical route playback, geofence, driver behavior, alerts, reports, and asset management.
- Domestic vehicle-monitoring platforms: monitoring cockpit, vehicle monitor, trip replay, realtime alerts, running statistics, and alert management.
Reference principles used for the Lingniu platform:
- Samsara-style telematics products emphasize realtime GPS visibility, diagnostics, routing/navigation, energy/fuel, alerts, and operational efficiency.
- AMap Web JS should power map rendering, marker interaction, and trajectory display while keeping the security code behind a service proxy.
- TDengine vehicle IoT guidance fits the platform's realtime location monitoring and trajectory replay query pattern, while Redis remains the low-latency realtime projection.
## Information Architecture
The left navigation should be vehicle-service oriented:
@@ -83,6 +91,7 @@ Primary modules:
- Right-side vehicle queue: online, offline, degraded, abnormal, no location.
- Bottom table: latest position, speed, mileage, source freshness, service status.
- Map overlays: online state, protocol source, alert severity.
- Production readiness rail: AMap Web JS state, security proxy state, location point cap, latest refresh time, and fallback mode.
AMap behavior:
@@ -140,6 +149,7 @@ Primary modules:
- Playback controls: play, pause, speed, step, seek, and auto-stop at the last point.
- Evidence table: time, longitude, latitude, speed, mileage, protocol, raw frame link.
- Quality strip: missing points, time gaps, mileage jumps.
- Export and share controls: copy query link, open AMap line, export current page evidence.
Query:
@@ -193,6 +203,7 @@ Required alert domains:
- Raw parse failure or unknown field burst.
- Binding missing or VIN unresolved.
- Cross-source time/location/mileage inconsistency.
- AMap unavailable or security proxy misconfigured.
### Notification Rules
@@ -220,6 +231,7 @@ Primary modules:
- 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.
- Notification impact: affected vehicles, affected BI users, last normal data time, and recovery time after alert closure.
Rule:
@@ -250,6 +262,7 @@ Use Semi UI as the component base. The style should feel like a cloud operations
- Cards only for repeated metrics or detail blocks; avoid nested cards.
- Drawer for detail and evidence, full routes for heavy workflows.
- No landing page, no marketing hero, no oversized decorative cards.
- Primary navigation should use user jobs: operations cockpit, realtime monitor, vehicle center, trajectory replay, history query, alerts, statistics, notification rules, and ops quality.
## Data Model Boundaries