Remote Generator Monitoring: What to Monitor, How to Filter Alarms and What It Saves

By Djordje Milivojevic, Electrical Engineer · Updated · 7 min read

Short answer

Remote generator monitoring connects each generator controller to a cloud platform through a cellular or Ethernet gateway, so status, alarms, fuel, battery voltage and run hours are visible from anywhere. Its value comes from filtering alarms into a short list of actions, catching battery and fuel problems early, and replacing routine check visits with visits that have a purpose.

In this article
  1. What is remote generator monitoring?
  2. What should you monitor on a generator?
  3. How to filter alarms so they stay actionable
  4. What does remote generator monitoring save?
  5. How to choose a remote generator monitoring system
  6. Frequently asked questions
  7. Sources

Most standby generators sit at sites nobody visits unless something is wrong. The controller on each unit already knows whether it is in AUTO, whether the battery is healthy, how much fuel is left and whether the last test passed. Remote monitoring simply brings that knowledge to the people who need it, before the next outage instead of after it.

This guide covers what to monitor, how to stop a monitoring system from drowning your team in alarms, and where the savings actually come from in a fleet of dozens or hundreds of generators.

Telecom mast at a remote hilltop site with an equipment shelterGenerator controller in AUTO mode with an emergency stop button below it
From our field operations: a remote hilltop site (left) and the generator controller that reports its status (right). Every trip to a site like this costs hours, so a visit should happen because the data asks for it.

What is remote generator monitoring?

Remote generator monitoring is a system that reads data from a generator's controller and sends it to a central platform over a cellular or Ethernet connection. The platform shows the status of every unit, sends alerts when something needs attention and keeps a history of readings, alarms and tests.

A typical setup has four parts:

  1. The controller on the generator, which measures voltages, frequency, load, engine readings and alarms.
  2. A communication gateway, usually a 4G modem or an Ethernet connection, often built into or plugged into the controller.
  3. A cloud platform that collects the data, filters alarms and stores history.
  4. The people and tools that act on it: a dashboard for the control room, alerts on the phone, work orders and a field app for technicians.
How remote generator monitoring worksThe generator controller sends data through a cellular or Ethernet gateway to a cloud platform, which drives the dashboard, alarm notifications, work orders and the technician field app.From the generator to the person who actsControlleralarms, readings, logGateway4G or EthernetCloud platformfilters, stores, plansDashboardevery site, one viewAlertsapp, SMS, emailWork orderscreated from alarmsField appjob, route, checklistSite side: no open ports. The gateway connects out to the platform over an encrypted link.
The controller already measures almost everything that matters. Monitoring adds a gateway to send it out and a platform that turns readings into decisions.

What should you monitor on a generator?

Not every signal deserves an alert. The table below separates what to watch continuously from what to alert on.

SignalWhy it mattersAlert when
Controller mode (AUTO, MAN, OFF)A unit not in AUTO will not start on grid failureNot in AUTO for longer than a site visit
Mains present and generator runningShows outages and whether the generator took the loadMains lost and generator not running
Shutdown and warning alarmsShutdowns stop the engine; warnings come firstAny shutdown; warnings that stay active
Starting battery voltageBattery problems are the most cited cause of failed startsBelow threshold or falling trend
Battery charger statusA failed charger drains the battery in daysCharger fault or no charging voltage
Fuel level and rate of changeRuntime reserve; theft and leaksBelow reserve level or sudden drop with engine off
Coolant temperature and oil pressureEngine health during runsOutside the manufacturer's limits
Load in kW or % of ratingLight load causes wet stacking; overload tripsTests below 30% for months; overload
Run hours and number of startsDrives the service planService interval reached
Transfer switch positionConfirms the load actually movedPosition does not match the generator state
Test resultsProof that monthly tests happened and passedMissed or failed test

Optional inputs such as enclosure door contacts, fuel tank water sensors or exhaust temperature add value at sites where theft, flooding or light load are known risks.

How to filter alarms so they stay actionable

A generator controller produces far more events than any person should read. Every mode change, every short mains dip and every warning that clears itself becomes an event. Send them all to the duty engineer and within a week the alerts are ignored, including the real ones.

Good alarm handling follows a few rules:

  1. Set priorities. Separate shutdowns and critical conditions (generator failed to start, running out of fuel) from warnings and from information events.
  2. Remove duplicates and flapping. The same alarm repeating every few minutes should become one event with a count.
  3. Use delays where they make sense. A mains dip of two seconds is not an outage. A low battery reading during cranking is normal.
  4. Suppress events during known work. When a technician is on site or a test is running, expected alarms should be logged but not escalated.
  5. Escalate what stays unresolved. If a critical alarm is not acknowledged or cleared within a set time, it moves to the next person.
  6. Turn alarms into work. An alarm that needs a site visit should create a work order with the site, the alarm history and the likely parts.
Illustrative alarm funnel for a generator fleetIn an illustrative month, 1200 raw controller events reduce to 420 after removing duplicates, 260 after suppressing maintenance and tests, 38 that need a person and 11 that need a site visit.From noise to action: one illustrative month, 50 sitesRaw controller events: 12001,200 Raw controller eventsevery status change, warning and alarmAfter removing duplicates and flapping: 420420 After removing duplicates and flappingsame alarm repeating, short dipsAfter maintenance and test suppression: 260260 After maintenance and test suppressionevents while a technician is on siteNeeds a person: 3838 Needs a personcritical or unresolved after a delayNeeds a site visit: 1111 Needs a site visitcannot be cleared remotely
Illustrative example. Without filtering, every event reaches a person and real alarms get lost in the noise. With rules for duplicates, delays and maintenance windows, only the events that need a decision reach the duty engineer.

What does remote generator monitoring save?

The savings in a fleet come from a handful of places. Each one can be measured with your own numbers.

Fewer wasted site visits. Routine trips just to check that a unit is in AUTO, read the fuel gauge or confirm a test are replaced by data. Technicians go to sites that need hands-on work.

Fewer emergency callouts. Battery, charger and fuel problems are caught days or weeks ahead and fixed on a planned visit, which is cheaper than a night callout and far cheaper than a failed start during an outage.

Better fuel logistics. Refuelling is planned from actual levels and consumption instead of fixed rounds, and theft or leaks show up the same day.

Proof for audits and clients. Every test, alarm and response is logged with time stamps, which is what NFPA 110 records, service contracts and SLA reports require.

Longer engine life. Load data shows which units run too lightly and need a load bank test, and run hours keep the service plan on time.

Illustrative fuel level over five daysFuel level falls slowly during two generator runs, then drops by 22 percentage points in two hours at night while the engine is off, which triggers a possible fuel theft alarm, and later rises after a planned refuel.0%25%50%75%100%Day 1Day 2Day 3Day 4Day 5Day 6runrunDay 3, 02:30: drop of 22 points with engine offEngine off, 22 points gone in 2 h: theft or leak alertDay 5: planned refuelPlanned refuel loggedFuel level, % of tank
Illustrative example. Fuel only falls slowly while the engine runs. A sharp drop with the engine off is the pattern that points to theft or a leak, and it is easy to detect automatically once the level is logged.

A simple way to estimate the value for your fleet:

ItemHow to estimate it
Check visits avoidedNumber of routine check visits per year × cost per visit (travel, time, vehicle)
Emergency callouts avoidedCallouts per year caused by battery, charger or fuel × (callout cost minus planned visit cost)
Fuel savedFuel lost to theft and leaks per year + fewer partial refuelling trips
Outage penalties avoidedSLA penalties or lost revenue per failed start × failed starts prevented

How to choose a remote generator monitoring system

  1. Controller compatibility. Check that the system reads the controllers you already have, across brands and models, not only one manufacturer.
  2. Communication. 4G with a fallback, or Ethernet where the site has it. Ask what happens when the connection drops: the gateway should buffer data and send it later.
  3. Security. The gateway should connect out to the platform over an encrypted link, with no open ports at the site and no default passwords.
  4. Alarm handling. Priorities, delays, suppression during maintenance and escalation rules should be configurable per site and per alarm.
  5. Maintenance link. Alarms and run hours should feed work orders and the service plan directly, not a separate system.
  6. Field app. Technicians should see the site history and alarms on the phone and log readings and photos at the site.
  7. Data ownership and API. You should be able to export history and connect the platform to your ERP or ticketing system.

Frequently asked questions

What is remote generator monitoring?

Remote generator monitoring is a system that reads data from a generator's controller and sends it over a cellular or Ethernet link to a central platform. It shows the status of each unit, sends alerts and keeps a history of readings, alarms and tests.

Can I monitor a generator from my phone?

Yes. Most monitoring platforms have a mobile app or a mobile web view that shows status, fuel, battery voltage and alarms, and sends push notifications or SMS when something needs attention.

Do I need internet at the generator site?

No fixed internet is needed. Most remote sites use a 4G cellular gateway with a data SIM card. Sites with a reliable local network can use Ethernet instead.

Can remote monitoring start a generator remotely?

Many systems can send start, stop and test commands to the controller. Remote control should be limited to authorised users and used with care, because a person could be working on the generator at the time.

Is remote generator monitoring secure?

It can be. A secure setup uses gateways that connect out to the platform over an encrypted link, with no open ports at the site, individual user accounts and up-to-date firmware.

How does remote monitoring help prevent generator failures?

It shows the early signs of most failures: falling battery voltage, a charger fault, low or disappearing fuel, a unit left out of AUTO, missed tests and tests run at too light a load. Each of these can be fixed on a planned visit before it causes a failed start.

Sources

See every generator's status and service plan in one place

GenSetCare reads alarms, fuel and run hours from the controller, schedules service by run hours and calendar, and gives technicians a field app with live checklists.