How construction fleets improve asset utilization with custom analytics

    Andrew M., VP of Data and Solutions
    AuthorAndrew M., VP of Data and Solutions
    May 12, 2026
    Construction fleet management software for custom analytics

    Most construction fleet management systems can tell where a machine is. Far fewer can answer the exact question about the fleet: which vehicles produced useful work, which ones burned fuel doing nothing, and which assets are quietly moving toward failure?

    What information should a telematics platform provide to a construction fleet manager

    A UK heavy machinery operator manages hundreds of connected assets, including more than 100 excavators, generators, and industrial machines all with installed telematics devices. Though GPS tracking worked, engine-hour reports existed, and fault codes arrived on time, the operations team still struggled to answer practical questions:

    • Which excavators were genuinely under load versus idling at high RPM?
    • Which generators were oversized for the sites they powered?
    • Which operators consistently overloaded or under-loaded machines?
    • Which assets were drifting toward expensive maintenance events?

    The fleet already generated enormous volumes of data but most of this information stayed trapped inside standard reports.

    Working with system integrator Plug N Play Solutions, the company rebuilt its data strategy around Navixy’s IoT Query fleet analytics platform, transforming raw telemetry into actionable signals critical to the business. They created machine-specific operational states, productive-hours metrics, condition-based maintenance triggers, and operator-level analytics tailored to heavy equipment operations.

    This case study is based on the Navixy Telematics Talks podcast episode.

    Why traditional construction fleet management metrics need to be reviewed

    The fleet had no shortage of telemetry. The problem appeared when operations managers tried to make maintenance and utilization decisions from that data.

    An excavator could show eight active engine hours while spending half the shift idling near maximum RPM. A generator could run continuously while carrying only a fraction of its intended load. Two operators using identical machines could produce completely different wear patterns and fuel consumption profiles without anyone noticing. Standard telematics reports flattened all of that operational nuance into generic metrics.

    Modern industrial GPS devices from vendors like Teltonika and Galileosky can stream hundreds of sensor parameters from a single machine. But most construction fleet management software surfaces only a narrow subset of that telemetry through predefined reports and dashboards.

    That distinction matters because construction fleets behave differently from logistics fleets. For heavy machinery operations, what matters is not where the assets moved, but how it operated under load during those hours.

    That changes the entire analytical model. For example, instead of relying on ignition states, they correlated RPM, engine load, duty cycles, and machine-specific thresholds.

    How the construction fleet started measuring productive hours instead of engine hours

    One of the most important changes in the project was redefining what “working time” actually meant. In many heavy machinery fleets, engine hours are treated as a utilization metric. But in practice, engine-on time says very little about productive work.

    The Plug and Play team replaced the traditional engine-hours model with productive-hours analytics. To do that, they combined multiple telemetry signals: RPM ranges, engine load, duty cycles, idle status, machine-specific operational thresholds.

    Instead of a binary “engine on/engine off” view, machines were classified into operational states such as:

    • Productive load
    • Low-load operation
    • Idle
    • High idle
    • Heavy-duty cycle

    This created a far more realistic picture of asset utilization across the fleet. The shift immediately exposed a major source of hidden inefficiency: high idle.

    What high idle revealed about fleet utilization in heavy machinery

    Some operators pushed the throttle to maximum RPM and left the machine idling while away from the cab. Traditional reports counted those hours as active utilization because the engine was running. From a business perspective, those machines produced zero value while still generating:

    • Fuel costs
    • Engine wear
    • Maintenance accumulation
    • Artificially inflated utilization metrics

    The team introduced a dedicated “high idle” operational state based on a simple combination: High RPM + low engine load = high idle.

    That single metric changed how the fleet evaluated productivity. Machines that previously appeared “busy” suddenly showed large portions of wasted operational time. Fleet managers could now distinguish between assets performing real work and assets consuming fuel without output.

    Once high-idle behavior became measurable, supervisors could:

    • identify problematic operating habits,
    • compare utilization across sites,
    • improve scheduling decisions with significantly more confidence.

    Importantly, none of this required investments in new hardware. The value came from interpreting the data differently.

    How custom fleet analytics reshaped maintenance planning

    The same approach transformed maintenance management. Traditional maintenance workflows in heavy machinery fleets are usually reactive. A fault code appears, a machine fails, and an engineer gets dispatched.

    The problem is that many operational issues develop long before fault codes trigger alarms. Persistent under-loading gradually clogs DPF systems. Unstable RPM patterns indicate abnormal engine behavior. Load spikes reveal operational stress before mechanical failures become visible.

    Because the fleet had access to historical telemetry, the team could monitor those patterns over time rather than reacting only to final-stage failures.

    Matt Watson, Managing Director at Plug and Play Solutions, described the value this way:

    “If you can see that trend over time, you can intercept that problem before the engine error even occurs.”

    That changes the economics of maintenance completely. A scheduled service event on a quiet operational day is dramatically cheaper than emergency breakdowns, unplanned downtime, field engineer dispatches, replacement equipment costs, and missed project deadlines.

    How load balancing helps construction fleets extend equipment life

    Heavy machinery fleets rarely distribute workload evenly. Some machines carry extreme operational loads while others remain lightly utilized. Over time, that imbalance creates predictable consequences: accelerated wear on heavily loaded assets, uneven depreciation, premature replacements, higher maintenance costs, lower overall fleet efficiency.

    With direct visibility into engine load and productive workload, the operations team could manage assignments more intelligently.

    The approach is especially valuable for generator fleets. In one example, industrial sites routinely requested 100 kVA generators regardless of actual consumption needs. Telemetry later showed some sites drawing only 18 kVA.

    That mismatch created persistent under-loading problems. Modern emission-controlled engines need sufficient load to operate efficiently. Running oversized generators at low load accelerates soot buildup and shortens component life.

    With custom analytics, the fleet could identify those patterns early and right-size equipment before failures occurred. After implementation, operators can proactively recommend equipment adjustments based on real operational data.

    How operator-level analytics improved accountability

    The final layer of the construction fleet custom analytics project focused on the operator. Bluetooth beacons linked every telemetry stream to a named individual. The same credential used to start the machine identified who operated it.

    That enabled several operational improvements at once:

    1. Untrained personnel could be blocked from operating specific equipment. Only authorized operators could start designated machines.
    2. Suspicious events became traceable. The fleet identified recurring nighttime fuel-access incidents by combining beacon-based identification with video telematics data. What previously looked like unexplained fuel loss became a documented operational pattern.
    3. Operator behavior became measurable in a way that standard telematics rarely provides. Some of them consistently generated cleaner duty cycles. Others produced significantly more idle time. Once those patterns became visible, supervisors could introduce targeted coaching.

    That distinction matters because behavioral differences between operators often create larger efficiency gaps than differences between machines.

    Why IoT Query mattered in the construction fleet analytics

    None of these analytics would have been practical without direct access to raw telemetry data in IoT Query. Most telematics systems expose only predefined reports and fixed dashboards. That works for standard GPS tracking workflows but becomes limiting when heavy machinery fleets need custom operational logic.

    IoT Query exposes the full telemetry database and organizes data into multiple analytical layers: raw data layer for original telemetry signals and transformation layer for operational entities and custom logic.

    That architecture gave the integrator the flexibility to build machine-specific states, custom KPIs, and operational models without waiting for vendor-side feature development. For construction fleet management that matters because no two operational environments behave exactly the same way.

    What construction fleet managers can learn from this project

    Several lessons from this deployment apply broadly to large heavy machinery fleets. First, engine hours alone are a weak utilization metric. Until fleets separate productive workload from idle operation, utilization reporting remains incomplete.

    Second, engine load is one of the most valuable operational signals in heavy equipment environments. It directly affects maintenance planning, fuel efficiency, machine wear, and asset lifespan.

    Third, operator behavior matters more than many fleets realize. Once telemetry is tied to individual operators, training opportunities and inefficiencies become significantly easier to identify.

    Finally, the value of construction fleet analytics depends less on collecting more data and more on using existing telemetry intelligently.

    Contact us to explore how IoT Query helps construction fleets turn raw telemetry into productive-hours analytics, maintenance intelligence, and custom heavy machinery KPIs.

    Frequently asked questions about heavy machinery fleet analytics

    Q.: What’s the role of telematics in construction fleet management?

    A.: Telematics gives construction fleet management teams visibility into equipment location, engine behavior, fuel usage, operator activity, and maintenance conditions. In heavy machinery operations, the biggest value often comes from analyzing workload, idle behavior, and engine load rather than GPS tracking alone. To feel the difference use Heavy Machinery dashboard templates in Dashboard Studio), an embedded data visualization application that allows users to create custom panels for their specific workflows and KPIs without external services or BI tools directly in Navixy.

    Q.: What is the difference between engine hours and productive hours for construction fleets?

    A.: The difference between engine hours and productive hours is that engine hours measure total engine runtime, while productive hours measure operation under meaningful load. Productive-hours analytics gives fleets a more accurate view of utilization, fuel efficiency, and operational output.

    Q.: Can IoT Query work with existing heavy equipment telemetry hardware?

    A.: IoT Query works with data received from existing heavy equipment telemetry hardware, including industrial GPS devices, CAN bus integrations, and bespoke machine-control systems. The Navixy telematics platform successfully completes industrial GPS devices and CAN bus integrations, including Teltonika, Galileosky, and bespoke machine-control systems. As a result, IoT Query can ingest both standard and custom telemetry streams.

    Q.: How does operator-level analytics improve heavy machinery operations?

    A.: Operator-level analytics improves heavy machinery operations by connecting telemetry data to individual personnel through Bluetooth beacons or RFID identification. This helps fleets improve accountability, reduce idle time, investigate unauthorized activity, and identify training opportunities.

    Q.: How does advanced analytics improve maintenance planning?

    A.: Advanced analytics improves maintenance planning by identifying abnormal operating patterns before fault codes appear. Monitoring load behavior, RPM stability, and operational trends allows maintenance teams to schedule service proactively and reduce unplanned downtime. Explore a blog post “How to control actual work on heavy machinery fleets in Navixy” to learn more about RPM based analytics for better construction fleet management.

    Share article