Standby equipment rarely runs and cannot be watched continuously
Battery voltage, charger supply, automatic mode and periodic test records expose risks that develop while the generator is idle.
Power-System Component / Operational Visibility and Maintenance Closure
Generator Remote Monitoring and Operations Management
Remote monitoring is not another screen. Its value is to make generator, ATS, distribution, fuel and environmental conditions visible early, describe abnormalities accurately and preserve the response record, reducing outage risk at unattended and multi-site facilities.
Operating DataAlarm PrioritiesEvent RecordsMaintenance Reminders
Why Add Remote Monitoring
When sites are unattended, equipment is dispersed or fault reports are unclear, operating data should become actionable information before an outage
Remote monitoring does not replace site personnel. It helps teams detect abnormalities earlier, shorten fault diagnosis, preserve test and maintenance evidence and manage multiple locations under the same rules.
Multiple sites or regions need one operating view
Generator, ATS, fuel, alarm and maintenance status can be organized so regional teams see priorities rather than isolated messages.
The project asks only for connectivity, without data points or response ownership
Uploading data without alarm levels, recipients and response rules does not shorten recovery time.
Remote monitoring is being treated as a replacement for inspection
Leaks, abnormal noise, loose connections, corrosion and blocked ventilation still require site checks; remote data adds evidence rather than replacing them.
Complete Data Path from Equipment to Responsible Person
Controller acquisition, gateway transmission, platform records and human response must all connect to create a monitoring loop
The system should answer where data originates, how it travels, who receives it, what action follows and how closure is recorded. A missing stage leaves alarms sitting on a screen.
Generators, ATS equipment, switchboards and sensors produce status
Collect voltage, current, frequency, power, speed, oil pressure, coolant temperature, battery, fuel level and switch positions.
Controllers execute protection and create events
Record starts, stops, automatic mode, protective actions and fault codes with a reliable event sequence.
RS485 or network interfaces connect the gateway
Select Modbus, Ethernet, cellular or another compatible path around controller protocol and site distance.
Real-time data, trends and history appear in one view
Organize status by site, device and severity while retaining run hours, events and maintenance records.
Alarms reach named responsible people
Use platform, email, SMS or other channels by severity instead of sending every alarm to everyone.
Acknowledge, act, retest and close the event
Record diagnosis, site action, replaced parts and recovery testing as traceable maintenance evidence.
Product and System Configurations
From a local controller to a multi-site platform, scale the system around device count, monitoring depth and maintenance capability
Do not begin with one fixed platform. First confirm controller compatibility, essential data, network conditions, alarm ownership and maintenance workflow, then define hardware and service boundaries.
Controller Display and Event Log
Shows electrical, engine and alarm parameters at the generator for single-site projects with regular local inspection.
Controller with Communications Gateway
Uploads one generator or a small group to a remote endpoint with basic alarms, trends and run-hour records.
Generator, ATS, Distribution, Fuel and Environment
Combines source transfer, switch positions, fuel level, temperature, water leakage and other critical points into one standby-power view.
Central Platform and Remote Inspection
Standardizes sites, alarm levels, permissions, maintenance plans and response records across cities, campuses or facility portfolios.
Remote start, stop, reset or control is enabled only where site safety, control logic, authorization and local management rules permit it. Monitoring, alarms and records should normally come before remote control.
Data Groups and Alarm Levels
Monitor data that changes maintenance decisions, then organize alarms and response by severity
More data does not automatically create a better system. Basic status, critical faults, developing trends and maintenance milestones should be separated so noise does not hide events that threaten power continuity.
Electrical and LoadThree-phase voltage, current, frequency, power, power factor, load percentage and generated energy.
Engine ConditionSpeed, oil pressure, coolant temperature, starts, run hours, charging and shutdown status.
Standby-System StatusUtility source, ATS position, breakers, paralleling, fuel level, battery and charger.
Environment and SiteRoom temperature, humidity, water leakage, smoke, access or video selected by project risk.
Immediate Shutdown AlarmsLow oil pressure, high coolant temperature, overspeed and emergency stop
Start and Transfer FailureFailed start or stop, ATS position failure or abnormal source
Electrical Protection AlarmsOver/undervoltage, over/underfrequency, overcurrent and reverse power
Standby Readiness WarningsBattery voltage, charger fault, low fuel and automatic-mode exit
Developing TrendsLong-term changes in temperature, vibration, loading, fuel use or alarm frequency
Maintenance DueTriggered by run hours, calendar interval, test results and spare-parts plan
Notification EscalationUnacknowledged, unresolved or repeated faults move to the next responsible level
Event Closure RecordCause, action, parts, retest and restoration time remain traceable
Controller, Gateway and Monitoring Interfaces
Remote-monitoring reliability depends on verifiable data compatibility, communications power, alarm logic and records
Customers do not need to learn communications protocols, but they should verify the controller model, readable data points, gateway interface, offline buffering, permissions and alarm tests before the platform goes live.
Generator Controller
Compatible DSE, HGM or other controllers provide operating data, protection alarms and event history.
Protocol and Data-Point List
Confirm RS485, Modbus or other interfaces, register addresses, read/write permissions and engineering units.
Remote Communications Gateway
Converts and uploads field data over wired Ethernet, cellular service or another project-defined path.
Independent Power and Outage Ride-Through
Gateways, routers and essential sensors need stable power so monitoring does not disappear during the outage.
Expanded Sensor Inputs
Fuel level, temperature, humidity, water leakage, vibration or access points are added by risk rather than by quantity.
Antenna and Network Quality
Verify room shielding, signal strength, antenna location, data allowance and local carrier coverage.
Permissions and Remote Actions
Separate viewing, acknowledgment, maintenance and control permissions and retain authorization and audit logs.
Offline Buffering and History
Store critical events during a network interruption and upload them after recovery so the fault sequence remains complete.
Six Project Inputs
Define devices, data points, network conditions and response workflow so monitoring can reduce recovery time
Controller and system inventory
Provide generator, ATS, paralleling, distribution, tank and sensor models, quantities and available communications interfaces.
Required live and recorded information
Separate real-time status, protection alarms, trends, maintenance hours and items that still require site inspection.
Site communications and power
Confirm Ethernet, cellular signal, antenna location, IP rules, gateway power, outage behavior and local data service.
Alarm levels, recipients and escalation
Define who receives each alarm, acknowledgment time, escalation timing and nighttime or holiday coverage.
Viewing, maintenance and remote-control boundaries
Assign sites and actions by role and define account, password, log and personnel-change procedures.
Inspection, work orders and maintenance records
Include alarm acknowledgment, site photos, actions, parts replacement, retesting and closure status.
Typical Monitoring Tasks
Staffing and risk differ by facility, so data points and response rules must be defined for each project
Preserve start, transfer, operation and test evidence to shorten critical-fault diagnosis
Hospitals and data centers connect generator, ATS, UPS auxiliaries, fuel and environmental status with drill and maintenance records.
Give regional engineering teams one view across stores and properties
Hotels, malls and schools standardize alarm levels, maintenance intervals and fault-reporting formats to reduce repeated clarification.
Bring unattended operation, fuel supply and equipment trends into regional maintenance
Factories, campuses and remote sites use loading, temperature, vibration, fuel and repeat-alarm trends to target site visits.
Review remote monitoring around the equipment list, required data points and response workflow
Share controller and equipment models, site count, required data, network conditions, alarm recipients, permission boundaries and maintenance workflow. HOHANK engineers will define gateways, point lists, platform functions, alarms and test scope.