Fleet overview
Fleet Dashboard
Fault priority
Active fault severity
Telemetry totals
Fleet counters
Most recent
Fault activity
| EVi | Workflow | Machine | Code | Description | Level | First seen | Owner |
|---|
Live fleet
Machine locations
| Machine | Model | Customer | State | Faults | Coordinates | Last data |
|---|
| Machine | Model | Customer | Dealer | State | Hours | Idle | Total engine h | Fuel | Faults | Last data |
|---|
Historical telemetry
Machine performance report
For live testing, range sync is limited to 31 days per request. Syncing includes an extra baseline day so daily cumulative-meter differences are calculated correctly.
Daily trend
Hours and fuel
| Date | Operating h | Working h | Idle h | Total engine h | Idle % | Fuel used | L/h | EVi 24h fuel | Engine-on samples | Data intervals |
|---|---|---|---|---|---|---|---|---|---|---|
| No report loaded. | ||||||||||
Additional engine parameters
RPM & coolant temperature
The currently documented EVi EU telemetry service does not expose engine RPM or coolant-temperature history. The portal is structured to add those streams later if SANY enables another EVi/CAN endpoint; this test build will not invent values for them.
| EVi | Workflow | Machine | Fault | Description | Level | Started | Last seen | Assigned |
|---|
Recurrence
Most frequent fault codes
Machine focus
Machines with most fault events
Service queue
Workflow distribution
Telematics Plus
Native device positions
Live feed
Prototype status
Direct Telematics Plus messages are received independently of EVi and retained as a timestamped native history. The current bench interval is 60 seconds.
- Status
- Loading…
| Device | Linked machine | Status | GNSS | Location | Backup battery | LTE | CAN | Last contact |
|---|
Service & support
Fault report
Exports current and historic events with source status, service workflow, machine, code, level, timestamps, owner and resolution details.
Fleet management
Fleet report
Exports the latest machine state, hours, fuel, idle time, active fault count, location, customer/dealer allocation and last EVi timestamp.
Historical reporting
Daily utilisation & fuel
The new History area calculates daily operating hours, working hours, idle hours, idle percentage, cumulative fuel burn and litres per operating hour from stored EVi time-series data. Use the History page to backfill a selected machine and export the result as CSV.
Organisations
Dealers & customers
Alert routing
Fault alert rules
Accounts
Portal users
| Name | Role | Organisation | Last login |
|---|
Visibility
Machine allocations
| Machine | Model | Organisation | Relationship |
|---|
Telematics Plus
Native device provisioning
Provision each physical unit with its Device ID. The portal generates a high-entropy device key and stores only its hash. The key is displayed once and must then be configured on the device.
| Device | Label | Machine | Firmware | Last seen | Action |
|---|
SANY Admin diagnostics
Raw EVi Data
This screen is restricted to SANY Admin. It shows the unmodified JSON payload received from EVi so undocumented machine fields can be identified without changing the normalised portal data model.
Stored fleet snapshot makes no new EVi request. Live selections use the portal's existing authenticated EU EVi session and return page 1 only. Test fault login performs one credentialed login against the separately configured fault login URL and reuses the same encrypted appKey/appSecret; use it only when ready because the documented 30-minute login interval is enforced.
Request / response
Diagnostic metadata
- Status
- Select a machine and load data.
Detected structure
Field paths
No fields loaded.
Unmodified response body
JSON payload
Select a machine and load data.
Integration
EVi connection
Latest activity
Sync history
Scheduled ingestion
Background jobs
Fleet and fault snapshots can run independently from time-series history. This protects the fault workflow from long history imports and honours the EVi authentication cadence.
Alert outbox
Integration-ready notifications
New/cleared faults that match configured rules are written to an outbox. Production email/SMS/Teams delivery can consume this without changing fault ingestion.
Evidence model
Fault lifecycle
EVi status remains source evidence: active or cleared. Service workflow is a separate internal layer: new, acknowledged, investigating, actioned or closed. Portal users can add service activity without changing the original EVi fault identity, timestamps or severity.