Vethy parking AC integration with ISAAC Instruments for Canadian fleets

• Table of Contents

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

ISAAC Instruments is the dominant fleet telematics platform across Canadian long-haul fleets with bilingual EN/FR support and strong winter-climate reporting capability. Vethy parking AC integration with ISAAC surfaces parking-AC data inside the ISAAC dashboard with hours-of-service alignment under Canadian regulation.

Why ISAAC Instruments fleets retrofit Vethy parking AC

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

Integration approach with ISAAC Instruments

Vethy parking AC integrates with ISAAC Instruments via the ISAAC API. Vethy publishes events with serial-number-to-vehicle-ID mapping and Vethy customer success works with ISAAC's onboarding team for fleet activation. The integration is read-mostly from Vethy to the fleet's ISAAC Instruments 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 ISAAC Instruments tractor record. ISAAC Instruments'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 ISAAC Instruments

Recommended ISAAC Instruments report set after Vethy rollout: (1) per-tractor Vethy run-hours aligned to ISAAC hours-of-service off-duty/sleeper-berth segments under Canadian regulation, (2) idle-hour reduction by climate zone (summer cooling vs winter cab pre-heat), (3) fuel cost reduction in CAD, (4) ESG CO2 reduction tonnes, (5) Vethy uptime and alerts with bilingual EN/FR notification. These KPIs typically reach steady state 60-90 days after install for OTR fleets in Canadian long-haul fleet markets (and US cross-border) 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 events flow via the ISAAC API with HOS-segment joins under Canadian regulation. Bilingual EN/FR notification routing for fleets with Quebec operations. Climate-zone segmentation allows fleets to report summer-cooling vs winter-cab-preheat parking-AC value separately. Vethy can deliver historical backfill on request for fleets that retrofit existing tractors mid-life, so the ISAAC Instruments 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 ISAAC Instruments?

Yes — Vethy publishes events via the ISAAC API, surfacing run-hours, idle reduction, fuel savings, and ESG metrics inside the ISAAC dashboard with bilingual EN/FR notification and climate-zone segmentation.

Is custom dashboard development required?

No — Vethy data is surfaced as custom data items inside the ISAAC Instruments tractor record. ISAAC Instruments'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 aligned to ISAAC HOS segments under Canadian regulation, idle-hour reduction by climate zone (summer vs winter), fuel-cost reduction in CAD, ESG CO2 reduction, and 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.