Vethy parking AC integration with Geotab and MyGeotab add-in

• Table of Contents

1. Why Geotab fleets retrofit Vethy parking AC
2. Integration approach with Geotab
3. KPIs to report once Vethy is live on Geotab
4. Data engineering and ETL detail

Geotab is one of the largest commercial fleet telematics platforms in North America with deep idle-reduction reporting capability. Vethy parking AC integration with Geotab surfaces Vethy run-hours, battery SOC, ambient/cabin temperature, and service alerts directly inside MyGeotab so fleets can report parking-AC ROI alongside existing engine and fuel reports.

Why Geotab fleets retrofit Vethy parking AC

Geotab fleets typically run mature data programs on idle time, fuel economy, driver behaviour, and DEF/DPF events. The same data infrastructure that justifies a Geotab subscription is exactly what justifies parking AC retrofit: every saved idle hour is already measured per-tractor per-day in US, Canada, and EU markets operations, so the parking-AC payback case can be built directly from the existing Geotab dataset without bolt-on instrumentation. Fleets running Geotab typically see the cleanest pre/post baselines and the shortest internal approval cycles for Vethy retrofit programs.

Integration approach with Geotab

Vethy parking AC integrates with Geotab via the MyGeotab add-in framework and OAuth-authenticated REST API. Vethy publishes a Marketplace-listed add-in that registers as a custom data type within the fleet's MyGeotab tenant. The integration is read-mostly from Vethy to the fleet's Geotab tenant: Vethy run-hours, ambient temperature, cabin temperature setpoint, compressor cycle count, battery SOC, and any service alerts are surfaced as custom data items inside the Geotab tractor record. Geotab's native alerting, dashboards, and reports then operate on Vethy data the same way they operate on engine, fuel, DEF, and DPF data. No new dashboard product is required — Vethy data joins the fleet's existing operational view.

KPIs to report once Vethy is live on Geotab

Recommended Geotab report set after Vethy rollout: (1) per-tractor Vethy run-hours, (2) per-tractor idle-hour reduction vs the 90-day pre-install baseline pulled from the same MyGeotab dataset, (3) per-tractor fuel-cost reduction at the fleet's current cost-per-gallon, (4) DPF regen interval shift, (5) Vethy service alerts and uptime. These KPIs typically reach steady state 60-90 days after install for OTR fleets in US, Canada, and EU markets and 30-45 days for regional fleets with denser duty cycles. The same KPIs feed into ESG/SmartWay/CSRD reporting (see the sustainability hub) and into the fleet retention dashboard (see driver wellbeing hub).

Data engineering and ETL detail

For fleets with internal data engineering teams or analytics partners: Vethy publishes Vethy events to MyGeotab via the REST API on a 60-second cadence. Joins on serial number → device ID at the fleet level. Pre/post idle baselines join Vethy install date to the existing MyGeotab IdleTrip records. Vethy can deliver historical backfill on request for fleets that retrofit existing tractors mid-life, so the Geotab dashboard shows like-for-like pre/post comparison from day one. Vethy customer success works with the fleet's analytics owner to validate joins, units, and time zones during the first 30 days of rollout.

Frequently asked questions

Does Vethy integrate with Geotab?

Yes — Vethy publishes a MyGeotab add-in and uses the OAuth-authenticated REST API to surface run-hours, battery SOC, ambient/cabin temperature, and service alerts as custom data items inside the fleet's MyGeotab tenant.

Is custom dashboard development required?

No — Vethy data is surfaced as custom data items inside the Geotab tractor record. Geotab's native alerting, dashboards, and reports then operate on Vethy data the same way they operate on engine, fuel, DEF, and DPF data.

What KPIs should I track first?

Start with per-tractor Vethy run-hours, per-tractor idle-hour reduction vs the 90-day MyGeotab pre-install baseline, fuel-cost reduction at the fleet's cost-per-gallon, DPF regen interval shift, and Vethy uptime/alerts.

How long until KPIs reach steady state?

Typically 60-90 days after install for OTR fleets and 30-45 days for regional fleets. Vethy customer success works with the fleet's analytics owner during the first 30 days to validate joins, units, and time zones.