Fuel Management Systems in South Africa

Start with the fuel question your records cannot answer

A delivery note, a tank gauge and an engine-hour report describe different parts of the operation. A discrepancy becomes useful only when those records refer to the same location, quantity basis and time window. Our first discussion identifies where fuel enters your responsibility, where it leaves, and which team investigates a difference. This keeps the project tied to a practical decision: accepting a delivery, checking a dispenser, arranging replenishment or examining unexpected consumption.

Typical buyers include industrial fleet managers, mine and construction plant teams, facilities managers and finance staff responsible for diesel invoices. A site with bulk storage needs a different measurement arrangement from a fleet refuelled at external stations. A generator supplied from a day tank introduces transfer and return flows. We map these arrangements before proposing sensors, so the quote covers the records your team actually needs.

Choose the measurement boundary before choosing hardware

The same dashboard can present several boundaries, but each needs its own calculation. Transfers between two tanks should appear as a linked issue and receipt. Treating the receiving tank increase as a fresh supplier delivery would inflate purchases. Similarly, an equipment tank reading taken while the machine is moving should carry enough context for the reviewer to distinguish slosh and slope from a real stock change.

Bulk storage: make deliveries and withdrawals comparable

For a fixed tank, we review tank geometry, available calibration information, access fittings, operating level range and the existing method of receiving fuel. The relationship between measured level and usable volume matters especially for horizontal or irregular tanks. A sensor can provide a repeatable distance reading while an incorrect tank curve still produces an inaccurate stock estimate. Commissioning therefore checks both the measurement and its conversion into the quantity used for reconciliation.

Delivery review brings together the supplier document, receipt time, observed stock movement and any dispensing that continued during the delivery. Where fuel temperature or a supplier's reference-volume basis affects the comparison, those conditions belong in the agreed method. The system should preserve original records and the reason for any accepted adjustment. This gives procurement a traceable query to raise with the supplier and helps operations check the installation before attributing a difference to loss.

Mobile plant: relate consumption to the job being done

Loaders, excavators and other yellow equipment work under changing loads, routes and idle periods. Fuel per operating hour is most informative when the team compares similar duties and records the source of the hour count. An engine-running contact, controller counter and operator shift sheet may each have different gaps. The project specifies which becomes the reporting reference and how a missing or reset counter is handled.

Installation also needs to account for vibration, electrical supply, tank access, service work and the position of the sensor. We agree when a tank reading is considered stable enough for reconciliation. A maintenance event, tank replacement or sensor removal should generate a record that explains a subsequent change in baseline. Supervisors can then review exceptions with the work assignment, instead of ranking unlike machines using one universal consumption target.

Generator fuel: keep storage, transfer and output in view

A fixed generator often draws from a day tank fed by bulk storage. Return lines and automatic transfers can make a falling level look like consumption even when part of the fuel has moved elsewhere. We map the plumbing and available controller signals, then decide which quantities can be measured directly and which need a clearly described balance. Runtime, start events, faults and electrical output provide operating context where compatible interfaces are available.

For a fuel-per-kWh report, both fuel and electrical output must cover the same interval. A running engine at low load will behave differently from one carrying a steady production load. The useful first output is a reconciled event record with visible measurement gaps, not a universal efficiency score. For equipment health alongside fuel records, see our asset monitoring service.

What the delivered system includes

The scope can combine level instruments, pulse or meter interfaces, equipment signals, gateways, data storage, dashboards, exception notifications and agreed report exports. Each item is selected against the physical installation and the customer's available data. Existing meters and controllers are assessed first; integration requires their model, interface details, permissions and a representative record. A procurement list should distinguish supplied hardware from instruments retained at the site.

LoRaWAN can connect suitable low-power monitoring points to a site gateway, while 4G provides connectivity where the coverage assessment supports it. The design checks antenna location, gateway backhaul, power supply and what remains operational during an outage. Buffering capacity and recovery behaviour are specified and tested. A remote alert needs a working delivery path, so the operating procedure also covers a communications fault and local checks during a prolonged interruption.

Agree a reconciliation method that finance can reproduce

A basic storage balance is opening stock plus accepted receipts, less recorded issues and closing stock. That calculation becomes meaningful after the team agrees tank boundaries, units, timestamps and treatment of transfers. The report should identify incomplete periods and distinguish a missing meter record from a measured zero. A corrected delivery quantity should retain the original entry, who changed it and the supporting document.

For example, consider an illustrative tank with 5,000 litres opening stock, a 2,000-litre receipt, 1,500 litres of recorded issues and 5,450 litres closing stock. The apparent difference is 50 litres. This is a teaching example, not a customer result or evidence of theft. Before assigning a cause, the reviewer checks measurement uncertainty, timing, deliveries in progress, tank conversion and unrecorded movements. Your acceptance criteria define when an exception is investigated and which evidence closes it.

Commission the full workflow, from instrument to reviewer

Testing starts with an agreed reference and an approved site window. The customer and commissioning engineer define tolerances from instrument specifications and operating conditions. We then follow a representative transaction through the complete data path. A successful sensor reading alone does not complete acceptance: the record must reach the right report, have the correct unit and time, and support the decision named in the scope.

What does a fuel management system cost?

Price the actual fuel boundary: a bulk tank, mobile equipment or a generator network. addanode provides measurement integration and fuel-reconciliation reporting. The equipment and installation depend on tank geometry, issue points, machine interfaces and the records already available.

Ask for separate lines for the site survey, level or flow measurement, mounting and power, data integration, reporting and ongoing support. Identify any dispensing-controller, vehicle or billing-system access fees. Compare one representative tank or machine group, a full site and multiple sites with common reporting; local installation and maintenance still vary by location.

Use the bulk-tank scope, mobile-equipment fuel scope or generator scope to prepare a comparable quotation. No universal savings percentage or installed price is assumed.

Budget for installation and continued use

The project cost depends on tank count and geometry, equipment types, retained instruments, access work, power, communications and report integration. Separate the initial engineering and installation amount from recurring platform, SIM, support and maintenance costs. If finance needs an interface into an existing purchasing or ERP system, provide the system version, export format and data owner before that integration is priced.

Operational ownership matters as much as the bill of materials. Decide who checks sensor mounting, investigates an implausible reading, reconciles delivery documents and updates equipment records after maintenance. Set the support hours, escalation route and spare-parts arrangement in the service scope. Sites with difficult access may favour a different power or instrument arrangement from a staffed depot, even when the nominal number of monitored tanks is the same.

Vehicle tracking supports the fuel record

Position and trip history can help explain where an authorised fuelling event occurred or why a machine operated outside a planned assignment. We include those records where they serve the agreed industrial fleet task. For depot entry, trailer identity and rental handover, RFID vehicle and gate automation provides a separate checkpoint record. The right approach follows the event your team needs to verify.

Fuel observations can also sit beside production and maintenance information in addaNet. This is useful when a generator event interrupts a shift or a plant assignment changes consumption. Linking records requires consistent equipment identifiers and a shared time basis; we define those mappings during scoping rather than assuming that matching names in two spreadsheets identify the same asset.

Frequently asked questions