The platform
ZAPPP Data Layer: Channels, API, ownership
The data is the product. The dashboard is a bonus. ZAPPP decodes the signals your vehicles already broadcast, normalises them across OEMs into a single schema and gives them to you.
- One schema across every OEM, diesel and electric
- API-first: everything the dashboard shows, the API serves
- Isolated per customer, exportable in standard formats
- Your data leaves with you, complete, if you ever go
01 · Resolution
1Hz is not a specification. It is the difference between an event and a guess.
Legacy telematics polls every 30 seconds, 60 seconds, or worse. At that resolution a thermal event, a charge-acceptance anomaly or a regenerative-braking failure is invisible: averaged away between samples. At 1Hz the event is captured, timestamped and attributable. Degradation curves, charging-curve analysis and driver scoring are only possible at this resolution. Anything coarser is a summary, and summaries hide the thing you needed to see.
02 · The channels
What we read, and what each group enables.
| Signal group | Representative signals | What it enables |
|---|---|---|
| Pack summary | Pack voltage, current, reported SOC/SOH, available energy | SOC fusion, readiness forecasting, coulomb counting |
| Cell-level | Per-cell voltages, max/min spread, weakest-cell index | Imbalance detection, health scoring, rebalancing |
| Thermal | Module and cell temperatures, coolant in/out, rate of change | Thermal anomaly detection, derating context |
| Current & coulomb | Charge/discharge limits, accumulated amp-hours | C-rate, cycle depth, remaining-useful-life |
| BMS status | Contactor state, fault codes, balancing flags, isolation resistance | Safety guards, charger-fault inference |
| Powertrain | Motor torque, inverter temperature, speed, regenerative power | Driver scoring, energy attribution, duty cycle |
| Driver inputs | Accelerator, brake, drive mode | Behaviour analytics, harsh-event detection |
| Auxiliary loads | HVAC power, cabin and ambient temperature, DC-DC load | Temperature-aware consumption modelling |
| Charging | Charge mode, current, voltage, power, status | Charging-curve analysis, charger health |
| GNSS & dynamics | Position, speed, heading, gradient, odometer | Route association, duty-cycle context |
Individual OEMs expose more or fewer channels. Every signal is decoded from raw CAN frames via OEM-specific DBC maps into one normalised internal schema: the same schema across diesel and electric, across every OEM.
03 · Access
Everything the dashboard shows, the API serves.
REST endpoints with OAuth 2.0 and webhook streaming for live events. Vehicle-level SOC, SOH, RUL and alerts. Fleet summaries. Depot schedules. Residual-value and risk scores for finance integrations. Standard export formats for everything else. Your fleet management, ERP, insurance and finance systems read ZAPPP the same way we do.
04 · Ownership
Your data is yours. Here is what that means in practice.
01 · Ownership
Ownership
Every record collected on your fleet belongs to you. ZAPPP licenses analytical insight; it does not acquire your data.
02 · Isolation
Isolation
Your telemetry is stored isolated from every other operator. No competitor ever sees your fleet. Cross-fleet benchmarks are anonymised and aggregated.
03 · Export
Export
Full-fleet export in standard formats, available on request at any point in the contract, not just at the end of it.
04 · Exit
Exit
If you leave, your complete history leaves with you: structured, timestamped, readable. No ransom, no retention, no degradation of format. The devices come off as cleanly as they went on.
This section exists because "what happens to our data if we leave" decides deals. Now it is in writing.