Generator Monitoring and Diesel Reconciliation in South Africa

Draw the electrical and fuel boundaries together

A generator can supply one building, several circuits or a changing set of essential loads. Record the electrical boundary measured by the proposed meter and how it relates to the controller's own values. A meter downstream of selected circuits measures a different output from one at the generator terminals. Reports must identify that boundary before presenting energy or fuel intensity.

Draw the fuel path as well: bulk storage, day tank, supply, return and any shared connections. A refill to the day tank is a transfer within the site, while fuel consumed by the engine leaves the inventory boundary. If several generators share a tank, decide whether the project needs site-level reconciliation or separate consumption attribution for each machine.

The asset-monitoring service covers the wider equipment-health context. The industrial fuel service and bulk diesel tank scope connect this generator record with delivery and stock-control processes.

Review the controller and available interfaces

Obtain the controller make, model, interface documentation and current configuration through the equipment owner or service provider. Confirm which values and events can be read safely without changing control behaviour. A supported interface may expose run status, alarms, hours and electrical values; an older installation may provide only selected contacts or require separate meters.

Record the meaning of each point. A start command, engine-running indication and available electrical output are different states. The event sequence should distinguish them so a failed start or unsuccessful transfer can be investigated. A single “generator on” field may be insufficient for the operational question the customer wants answered.

Agree ownership of controller settings and access credentials. Monitoring configuration should follow the customer's change procedure, with the generator service provider involved where necessary. Test the proposed interface under the accepted operating conditions and retain its mapping, units, scaling and quality behaviour in the handover record.

Build a common event timeline

The useful timeline can include incoming supply status, start request, engine running, breaker or transfer state, measured load, stop and return to standby. Define which signals establish each event and how timestamps are generated. A controller log imported later should retain its original event time and the basis used to align it with other records.

Record a power interruption as a site observation. The event may relate to the upstream network, a local breaker, maintenance, transfer equipment or another cause. The monitoring system should preserve the measured sequence and let the responsible electrical team determine attribution using the site's evidence.

Test normal starts, planned exercises and representative load changes during a safe, approved commissioning window. Confirm that repeated signals and communication retries do not create duplicate starts or inflated running periods. Keep the event definitions consistent between the live display, alarm report and exported history.

Measure energy and running time deliberately

Energy should come from a suitable meter or an accepted controller value, with the measurement boundary and units recorded. Confirm cumulative-counter handling, including rollover, reset and replacement. A difference between two cumulative readings is meaningful only when the interval and counter history are understood.

Running hours provide useful maintenance context but do not describe the load carried throughout the interval. Retain load or energy information where the project requires fuel-performance comparison. A generator can run lightly loaded for a long period and produce a different litres-per-kWh result from a shorter period at another load.

The PNNL operations and maintenance guide provides background on maintenance records and condition-informed review. The installation should use the actual equipment owner's service requirements and observed operating history, rather than transfer a generic maintenance interval or savings figure into the project.

Reconcile fuel without losing return flow

If consumption is measured through flow, review both supply and return paths with the service provider. A supply-only measurement can include fuel returned to the tank. The selected arrangement and calculation need to match the engine's actual fuel circuit and the accepted measurement method.

Where tank inventory is used, record the capacity conversion, opening and closing observations, deliveries, transfers and other withdrawals. A stock decrease during a reporting interval is not automatically generator consumption if another asset uses the same tank. Keep the boundary explicit and retain unresolved or unmeasured movements as review items.

Temperature basis, settling, level variation and measurement uncertainty can affect the comparison. The fuel and energy records should share an agreed period cut-off. A delivery entered after the accounting day closes can change the apparent result even when the underlying instruments behaved correctly. Reports should distinguish late documents from measured stock events.

Use litres per kWh as a reviewed comparison

Calculate fuel intensity only when the fuel attributed to the generator and the generated energy cover the same accepted interval. State whether fuel was directly measured, reconciled from stock or estimated from another source. Keep estimated values distinguishable and show incomplete periods rather than silently treating missing input as zero.

For a hypothetical interval, 120 litres attributed to operation and 400 kWh of measured output gives 0.30 litres per kWh. If the energy record is incomplete, the apparent rate can rise without a real change in engine behaviour. This example explains the arithmetic; it is neither an acceptance target nor a measured project result.

Compare intervals with relevant load and operating context. Starting, idling, exercise runs, maintenance and changing electrical boundaries can all affect interpretation. A reviewed baseline from the customer's own accepted records is more useful than a universal rate applied to every generator. The maintenance owner should assess any persistent change with supporting evidence.

Configure alarms for actionable conditions

Separate generator alarms, low fuel, abnormal stock change, instrument fault and missing communication. Each should have a named response role and an escalation route appropriate to the site. An electrical fault may go to the generator service provider, while a delivery discrepancy belongs with receiving and finance.

Define the start, delay, acknowledgement and closure rule for each event. A message delivered remotely does not establish that a technician attended. The report should preserve the distinction between notification, accepted responsibility, site investigation and technical resolution. Test the actual channels and duty arrangements included in the proposed service.

Avoid making a fuel discrepancy automatically accuse an operator or supplier. Retain the original delivery, issue, tank and running records and route the difference for review. An explainable correction should preserve the earlier evidence and identify the person who approved the change.

Accept the installation against a shared schedule

Keep a record of failed tests and their resolution. A successful dashboard demonstration should not replace the witnessed field checks. The final acceptance should identify the controller version, meter configuration, fuel conversion and site boundaries that produced the agreed result.

Plan local retention and power continuity

The communication arrangement may use suitable LoRaWAN instruments and a 4G or existing network backhaul. Confirm signal availability and equipment mounting at the generator and tank locations. The installation should account for vibration, heat, weather exposure and the safe working access required by the facility.

If local storage is required, specify the device retaining data, its capacity and its behaviour during restart. Test the loss and recovery of the communication path and inspect both event order and missing periods. Historical data returned later can support reconciliation, while remote alarm delivery still depends on a working path at the time.

Power continuity should include monitoring equipment and the relevant network components. Define the required autonomy and recovery process from the actual load and site arrangement. A generator starting successfully does not automatically establish that every monitoring component recovered, so include those checks in the commissioning sequence.

Scope support, exports and service-provider handover

A quotation should separate interface work, meters or sensors, mounting, communications, software, alarms, reporting and commissioning. Confirm whether fuel reference measurements or tank assessment are included. Identify work requiring the customer's electrician, generator technician or other competent contractor, together with the approved installation window.

The service pack should contain the point list, wiring and mounting record, configuration, test evidence, user roles and export procedure. Define who maintains the asset register, receives faults, replaces instruments and reviews changes after generator service. A controller replacement or altered fuel circuit should trigger a review of the monitoring configuration and reconciliation boundary.

The logistics industry page provides context for depots and distributed facilities. For an enquiry, send controller details, electrical drawings where available, tank connections, current fuel records, operating hours and the report the team needs. Discuss generator monitoring with facilities, the service provider and finance to agree a first delivery that can be independently checked.

Frequently asked questions