GoSense PowerGuard

Make generator and fuel behavior visible.

Bring runtime, fuel-level movement, consumption context, refilling events, supported electrical signals, maintenance history, and tamper indicators into one review path.

Hardware, signal compatibility, accuracy, connectivity, and return assumptions are proposal-dependent and subject to technical survey.

GoSense360 sensor enclosures on a fuel tank and a standby generator
Illustrative image
ObserveRuntime, level movement, and supported load signals.
InvestigateRelate unusual changes to refill, use, location, and maintenance.
DocumentKeep evidence and follow-up without claiming automatic theft prevention.

Monitoring scope

Signals that support a better investigation.

The exact bill of materials and supported measurements follow a survey of the generator, tank, electrical panel, operating pattern, and installation constraints.

Generator runtime

Track running state and operating hours to support usage review and service planning.

Fuel level & refilling

Review level movement, consumption context, refills, and sudden changes against the approved sensing method and tank geometry.

Current & load

Include current or load signals only where the selected hardware, panel arrangement, and electrical safety design support them.

Tamper indicators

Record approved enclosure, sensor, or wiring indicators as investigation evidence; final coverage depends on the installation.

Maintenance context

Relate operating hours, observed events, inspections, and service records to the asset and site workflow.

Responsible claim

Detection supports investigation.

PowerGuard helps teams detect unusual fuel-level changes and investigate potential loss or tampering. It does not claim to eliminate theft, prevent every failure, or prove the cause of a change on its own.

  • Tank shape, fuel movement, temperature, vibration, and installation affect readings.
  • Accuracy is confirmed only for the approved sensing and installation design.
  • ROI depends on baseline consumption, operating discipline, site conditions, and response.

Example workflow

From change to reviewed action.

Workflow automation is configured only after the rule, duration, recipients, review authority, and failure handling are agreed.

Measure

Capture the approved fuel or runtime signal.

Validate

Check identity, time, and input quality.

Compare

Relate change to operating and refill context.

Flag

Highlight a configured unusual pattern.

Investigate

Review site evidence and maintenance records.

Record

Document the reviewed outcome.

FAQ

Common questions.

Can PowerGuard prove fuel theft?

No. Monitoring highlights unusual level changes and when they happened. Establishing the cause needs supporting site evidence and human review.

How accurate is the fuel reading?

It depends on the sensing method, tank geometry and installation. Accuracy is stated in the proposal for the approved design, after the tank and site are surveyed.

What does discovery need from us?

Generator count and ratings, tank shape and size, fuel type, access to the electrical panel, site connectivity, and who reviews an unusual change.

Can it work with our maintenance records?

Yes. Runtime hours and events can be related to service history, either in GoSense360 business modules or through a scoped integration with your system.

PowerGuard discovery

Start with the generator, tank, panel, and decision you need to support.

Discuss generator monitoring