Fuel, idling & driver behavior

    Cut idle waste, not the work

    A refuse truck idles all day, and most reports call all of it waste. But compaction and lifting are the job. Navixy reads the PTO off the J1939 bus, so IoT Logic counts only parked idle against you, then reports the fuel you save.

    Reads J1939 / CANPTO-aware idleFuel & driver reports
    Navixy · Idle analysis Live
    Refuse fleet · 12 trucks on shift
    Truck 14 · route N
    Working idle · PTO on
    62%
    Truck 22 · route S
    Parked idle · engine on
    18%
    Truck 09 · route E
    Harsh idle at depot · 41 min
    9%
    Idle split this shift
    Working (PTO)Wasteful (parked)
    J1939 PTO → IoT Logic smart idleIllustrative analysis

    Fuel intelligence that tells work from waste

    A garbage truck is not a delivery van. Its idle, RPM and PTO tell a specific story, and Navixy turns that story into rules and reports instead of one generic idle number that blames every working stop.

    PTO-aware idle: compaction is work, not waste

    Raw idle monitoring flags every minute the engine runs, including the compaction and lift cycles that are the job. Navixy reads PTO state from J1939, so IoT Logic subtracts working idle and penalizes only parked, engine-on minutes.

    !Raw idle — every minute penalizedCompaction & lift counted as waste — driver looks like the problem.PTO-aware idle — only parked idle countsIoT Logic subtracts PTO-on time — only genuine parked idle fires an alert.Working (PTO on)Wasteful (parked idle)
    J1939
    Fuel rateRPMPTOSpeed

    Fuel & PTO straight off J1939

    Fuel rate, total fuel, RPM, speed and PTO state come off the SAE J1939 CAN bus on supported trackers: one manufacturer-neutral data layer for a mixed fleet.

    Working idleWasteful idle
    PTO-aware split

    Smart-idle rules in IoT Logic

    IoT Logic separates working idle (PTO engaged) from wasteful parked idle and alerts only on the waste. No false flags on compaction cycles.

    Driver score
    Route N · 82 / 100

    Driver behavior, in context

    Harsh events, excess parked idle and speeding roll up into a per-driver score: the fair way to coach a fleet where some idle is unavoidable.

    Fuel by route
    Idle by driver
    Utilization

    Fuel reports that hold up

    IoT Query builds fuel, idle and utilization reports by truck, route and driver, so the savings are measured, not asserted.

    How it works

    From the CAN bus to a fuel bill you can defend

    The same pipeline for every truck: read the bus, decide with rules that understand refuse work, coach the driver, report the fuel.

    1. 01

      Read J1939

      Supported trackers pull fuel rate, RPM, speed and PTO state off the CAN bus. No per-OEM integration, one data layer for a mixed fleet.

    2. 02

      Decide — IoT Logic

      IoT Logic classifies idle by PTO state and flags harsh events and excess parked idle. Compaction idle stays uncounted, so working stops aren't penalized.

    3. 03

      Coach the driver

      Per-driver behavior scores turn the signals into a fair coaching conversation, the honest way to manage a veteran refuse crew.

    4. 04

      Report — IoT Query

      IoT Query reports fuel and idle by truck, route and driver, so a reduction target is tracked against real data, not a spreadsheet guess.

    The economics

    Why idle is the waste fleet's most invisible cost

    Fuel is the biggest line item a hauler controls, and idle is the part that hides in plain sight, because on a refuse truck a lot of idle is real work. Measure the difference and you cut the waste without a fight over the working minutes.

    Top line
    fuel is typically the largest controllable cost in a refuse fleet
    iMatrix
    >900 gal/yr
    fuel a single long-haul truck can save by eliminating unnecessary idling
    US EPA
    PTO-aware
    idle split so compaction/lift work is never counted as waste
    Navixy

    Fuel and idle magnitudes are third-party figures (iMatrix, US EPA long-haul illustration) shown as context, not Navixy's own results. Refuse-truck idle varies by route and duty cycle.

    Measure the fuel you're actually wasting

    Bring one route's worth of trucks. We'll read the J1939 bus, split working idle from wasteful idle with IoT Logic, and show you the fuel report on your own fleet.

    J1939 fuel & PTO · PTO-aware idle · fuel & driver reports

    FAQ

    Straight answers on fuel & idle monitoring

    Refuse-truck idle monitoring has to separate working idle from wasteful idle, because compaction and lift cycles run the engine as part of the job. A generic idle report counts every engine-on minute, so a hard-working crew looks like the worst offender. Navixy reads PTO state from the J1939 bus and penalizes only parked idle: the minutes that burn fuel for no work.