For fleet heads · Transport · Police · Health · Local bodies

Every vehicle in your fleet,
read from its own port.

Palm Eye plugs into the diagnostic socket every BS‑VI vehicle already has. It reads the warning lamp and fault codes before they become a breakdown, records engine‑on and idle hours and harsh driving, and ties every trip to a named driver and vehicle.

  • OBD‑II / BS‑VIno wiring, no ECU change
  • Phone + cloudworks offline, uploads later
  • Audit‑readyVIN, driver, time, km, codes

Three steps. No wiring.

  1. Plug in

    A small adapter goes into the OBD‑II socket under the dashboard — the one every BS‑VI vehicle sold since April 2020 carries (on an OBD‑2 motorcycle or scooter, a small 6‑pin socket under the seat, through an adapter cable). Nothing is cut, wired or reprogrammed.

  2. Drive as usual

    The driver's phone reads the engine computer — and every other module that answers — records the trip under the driver's name, and keeps it until there is signal.

  3. See the fleet

    One dashboard: which vehicles have the warning lamp on, which codes appeared and when, engine‑on and idle hours, harsh events per driver, and an audit trail for every trip.

Your fleet

What Palm Eye would show you

Tell us about the fleet. Every figure below is worked out in the open: the formula, the benchmark behind it, and which numbers are your own assumptions. It is an estimate, not a quote.

Vehicles
Use
Maintenance & breakdowns
Drivers & tracking
Vehicles are
Tracking today
What hurts most
Your assumptions — Palm Eye measures these from day one

Not every breakdown leaves a trace in the engine computer (a puncture never does). We do not have a measured share for road vehicles yet, so this one is yours to set — the benchmark for industrial equipment is shown with the result.

A year, on what you entered

—–—

idling fuel, breakdown costs and maintenance, for the — vehicles Palm Eye can read.

  • Idling fuel
  • Breakdowns
  • Maintenance

Utilisation

measured

— vehicle‑hours available a year

Idling at your estimate: — engine hours, — litres, —

utilisation = engine‑on hours ÷ available hours idle share = idle hours ÷ engine‑on hours

Idling uses about a quarter to a half gallon (0.95–1.9 L) of fuel an hour, depending on engine size and air conditioning — US DOE / EPA, fueleconomy.gov.

Breakdowns caught early

measured

— of — breakdowns a year flagged before the road

Palm Eye lists every vehicle with the warning lamp on or codes stored, and the lead time from the first code to the repair.

caught = breakdowns a year × readable share × share with a warning first

Industrial predictive‑maintenance programmes report 70–75% fewer breakdowns and 35–45% less downtime — US DOE FEMP, O&M Best Practices Guide R3.0 (2010), §5.4. That survey is of plant equipment, not vehicles; we use your setting instead.

Downtime avoided

estimate

— vehicle‑days back on the road

— in towing and replacement vehicles not hired, and maintenance spend down —

days = caught × days off the road ₹ = caught × towing and replacement maintenance = spend × 8–12%

A working predictive programme saves 8–12% over preventive maintenance alone — US DOE FEMP, O&M Best Practices Guide R3.0, §5.4.

Safety

measured

— km a year scored for harsh events

Harsh acceleration and braking per 100 km, and the trend for each of your — drivers.

harsh rate = harsh events ÷ km × 100, per driver, per month

With onboard monitoring plus coaching, two fleets cut safety‑related events per mile by 37% and 52% — Hickman, Hanowski & Ajayi, VTTI (2009). Aggressive driving also costs 10–40% fuel economy in town — fueleconomy.gov.

Accountability

measured

— vehicle‑days of audit‑ready records a year

—

accountability = trips tied to a named driver and vehicle ÷ all trips

Each trip carries the vehicle's own identity (VIN, read from the engine computer), the signed‑in driver, the time, the distance and any codes — kept on the phone until it uploads.

Data coverage

Palm Eye's own measure

—

valid data points ÷ points the vehicle offers, median across the live fleet

coverage = valid data points ÷ data points the vehicle offers (implausible values are never counted)

Proof, not promises

The live fleet, right now

Figures read from the vehicles already connected. A number we cannot back with data is left out rather than guessed.

Pricing

Pricing starts with a conversation.

Fleets differ: the mix of vehicles, how many adapters, who installs them, where the data must live. Answer three questions and we'll draft your note, with the estimate above already filled in.

You are

When are you looking to start?

Answer the three questions first. Holding the button for a moment tells us a person is here; our address appears only after that.

Sources

  1. US Department of Energy & EPA, “Driving more efficiently”, fueleconomy.gov — idling uses a quarter to a half gallon of fuel per hour; aggressive driving lowers fuel economy by roughly 15–30% at highway speeds and 10–40% in stop‑and‑go traffic.
  2. US DOE Federal Energy Management Program, Operations & Maintenance Best Practices — A Guide to Achieving Operational Efficiency, Release 3.0 (August 2010), §5.4 Predictive Maintenance — 8–12% savings over preventive maintenance; independent surveys of industrial programmes: maintenance cost −25–30%, breakdowns −70–75%, downtime −35–45%.
  3. J. S. Hickman, R. J. Hanowski, O. Ajayi (Virginia Tech Transportation Institute), “Evaluation of an Onboard Safety Monitoring Device in Commercial Vehicle Operations”, Driving Assessment 2009 — safety‑related events per mile fell 37% and 52.2% at two carriers with monitoring plus coaching.
  4. Live‑fleet figures: Palm Eye Cloud, aggregated across connected vehicles (no vehicle, driver or place is identified), refreshed every ten minutes.