Fuel and Utilisation Monitoring for Yellow Equipment

Select the machine and work cycle first

An excavator, loader, grader and haul unit can consume fuel under very different duty cycles. Begin with the machine categories, attachments, work areas and available operating records. The useful comparison may be fuel per engine hour, per productive hour or per measured unit of work, but each denominator needs an agreed definition and a reliable source.

Engine running does not necessarily mean productive work. A machine can idle, warm up, travel, queue or operate an attachment without moving. Identify which states can be established from available signals and which require operator or supervisor input. Keep uncertain states visible rather than assign every running minute to productive utilisation.

The industrial fuel-monitoring service provides the wider scope. Bulk diesel tank monitoring covers the store or bowser supply boundary, while this page concentrates on the moving asset, its refuelling events and the operating context needed to interpret consumption.

Review the signals the equipment can actually provide

Inventory controller outputs, engine-hour records, existing telematics and accessible sensors before selecting additional hardware. Confirm permissions and interface documentation with the equipment owner and service provider. A usable engine-hour value or operating-state signal should have a known meaning, update interval and failure behaviour.

Electrical current, movement or engine speed can provide context but should not be treated as universal proof of work. Define the rule for each machine type and verify it against observed operations. Where the equipment exposes limited information, a simple, well-labelled record can be more useful than an elaborate classification built on assumptions.

Record the source and timestamp of each signal. A controller total imported once per day and a live level trend have different time resolution. Reports should align their periods before calculating a rate. If the source resets after service or replacement, retain the event and adjust the interpretation explicitly rather than create a negative or inflated usage interval.

Account for slope, movement and tank shape

A level sensor on mobile equipment sees a tank operating through acceleration, braking and changes of inclination. The observed surface position can change without fuel entering or leaving. Record the tank geometry, mounting, baffles where known and the conditions under which a stable stock comparison can be made.

Define the accepted measurement windows using representative operating evidence. A stationary observation on an agreed surface may provide a useful reference, while a moving-machine trend may need additional interpretation. The application should distinguish these contexts rather than display every transient change as a precise consumed volume.

The capacity conversion must correspond to the actual tank and measurement reference. Test representative stock levels and operating positions with the responsible team. A replacement tank, altered mounting or changed sensor requires a configuration review. Preserve the accepted table and offsets with the machine record so the basis of later comparisons remains clear.

Capture refuelling as a controlled transaction

For each issue, identify the supplying bowser or fixed point, destination machine, operator, start and end time and quantity source. Retain the delivery or issue reference. If a meter supplies the quantity, record its identity and accepted configuration; if the quantity is manually declared, label that basis and the person who entered it.

Compare the issue record with the machine's stock change only under suitable conditions. The machine may continue running, the fuel may settle after filling, and the two observations may use different time boundaries. Keep those details with the comparison so the reviewer can explain why an apparent difference arose.

A bowser also needs its own stock balance. Fuel loaded into the bowser, issued to machines and remaining at shift end should be reconciled separately from machine consumption. Linking the records helps identify missing or misassigned transactions without assuming every discrepancy belongs to the receiving machine.

Define utilisation in operational language

Agree the states the project needs: available, running, productive, idling, travelling, stopped for maintenance or unavailable, for example. State how each is determined and who can correct a classification. The categories should fit the site's work planning rather than impose a generic fleet vocabulary on all equipment.

A supervisor may need to distinguish waiting for trucks from waiting for an operator, while finance may need total hours assigned to a project. Preserve the underlying events and the reason codes used for review. A change in classification should not silently rewrite historical project allocations without a recorded reason and effective period.

If a productive-output denominator is required, establish its independent source. Buckets, tonnes, metres or completed tasks are not interchangeable measures. Test the mapping against the actual work record and retain excluded or incomplete periods. A rate calculated from an unreliable output total can be more misleading than reporting fuel and hours separately.

Compare like duty with like duty

Fuel per hour can change with load, ground conditions, travel distance, attachment and operator practice. Group comparisons using the relevant operating context and review the sample period. A machine working a difficult face should not be judged against an unloaded unit based only on total fuel and engine hours.

Use a local baseline from representative accepted records if the customer wants to identify changes. Retain maintenance events, component replacements and changes in work assignment. A trend can direct an investigation, while the responsible maintenance and operations teams determine the cause using supporting evidence.

For a hypothetical example, 240 litres over 12 engine hours gives 20 litres per engine hour. If only six of those hours meet the agreed productive-state rule, the same fuel corresponds to 40 litres per productive hour. Neither result is a universal benchmark or a measured customer outcome; the example shows why the denominator must be stated.

Assign the acceptance evidence across the team

The first trial should include representative work, idle periods, travel, refuelling and a shift change. Where safe and appropriate, include slopes and movements that challenge the measurement arrangement. Record the conditions under which the result is accepted and those where the system should flag uncertainty or wait for a stable observation.

Plan communication around moving work areas

Coverage can change as machines move between faces, yards or projects. Survey the intended work area and define which observations are expected locally and which need a remote path. LoRaWAN or 4G can be used according to the site and equipment arrangement, with the actual communication role and limitations documented in the design.

Where local retention is supported and required, specify capacity, power behaviour and recovery. Test delayed transfer into the reporting system and inspect event ordering. A backfilled history can support later reconciliation, but it does not establish that a remote alert was delivered during an interruption.

Show observation age and missing intervals. The dispatcher and fuel reviewer need to distinguish a machine that has stopped reporting from one that has stopped working. Define separate technical and operational alerts, with responsible owners for each, so communication faults do not become unexplained utilisation losses.

Hand over the workflow and support responsibilities

The installation plan should identify mounting approvals, safe access, isolation, cable protection and the equipment service windows. Confirm who can authorise modifications and who supports the interface after installation. The work should fit the owner's maintenance procedures and the site's requirements for mobile machinery.

A quotation should separate hardware, mounting, signal integration, communications, software, project reporting, training and support. Include the effort to maintain machine and project registers, replace damaged equipment and revalidate a unit after significant service work. Define recurring charges and any agreed support response in the contract.

The handover pack should contain machine associations, signal definitions, capacity conversion, accepted operating conditions, test results and the exception procedure. Provide a usable export and train the staff who approve refuelling and project allocation. Those records should remain understandable when the machine moves to a new job or the original installer is absent.

Prepare the first project enquiry

Provide the machine list, makes and controller information where available, tank details, work-cycle descriptions, current issue records and the project reporting requirement. Include whether the main concern is stock reconciliation, idle time, allocation or a specific abnormal trend. A focused first scope makes the acceptance decision clearer.

The logistics industry page connects this work with depots and material movement. Discuss yellow-equipment monitoring with operations, maintenance and fuel control so the proposed signals and reports answer the same operational question.

Reference for operating records

The PNNL operations and maintenance guide provides background on equipment records and maintenance review. Apply the customer's actual asset history, operating context and approved measurement evidence to the proposed fuel workflow.

Frequently asked questions