General Service
A Clear Site Report Can Significantly Shorten Diagnosis Time
Reporting a fault does not shift troubleshooting responsibility to site personnel. It turns what has already happened into useful clues for the engineer. Alarms, operating status, transfer sequence, affected loads, sounds and smells help distinguish starting, fuel, cooling, ATS, distribution and downstream load problems.
Probable Causes
A Vague Report Starts the Investigation from Zero; Clear Symptoms Point to the Affected Section
“It will not start,” “there is an alarm,” or “there is no power” describe only the result. They do not show whether the fault is in starting, operation, transfer, distribution or the load side. Professional support connects the symptoms, timing, status and impact to locate the affected section before confirming the root cause.
Fault Timing Guides the Diagnostic Path
A fault before the utility outage, during starting, after ATS transfer or after running under load leads to a different diagnostic path.
The Alarm Display Is More Precise Than a Verbal Description
Controller alarms, operating readings, ATS status and low-voltage switchgear indications help distinguish a protection trip, a sensor issue and a genuine operating risk.
Load Impact Sets the Response Priority
If the fault affects an ICU, checkout systems, production lines, cold rooms, guest rooms or data halls, immediate on-site intervention may be required.
Diagnostic Process
The Engineer Turns the Report into a Diagnostic Path
- 01
Confirm the time, whether utility power was lost, whether the generator started, whether the ATS transferred and which loads were affected.
- 02
Review alarms, operating hours, voltage, frequency, oil pressure, coolant temperature, battery voltage and fuel status.
- 03
Use the symptoms to prioritize the starting system, fuel and cooling systems, controller, ATS, low-voltage distribution or downstream loads.
- 04
If a site visit is required, use the preliminary diagnosis to prepare tools, spare parts and a safe isolation plan, reducing trial-and-error on site.
When an On-Site Inspection Is Required
These Conditions Require On-Site Inspection, Not Remote Observation Alone
- There is an oil or coolant leak, abnormal noise or smoke, an electrical burning smell, breaker tripping or unusual switchboard heating.
- Critical loads cannot be restored, or the status of the ATS, low-voltage switchgear and downstream circuits cannot be confirmed.
- The same fault keeps returning, and a remote reset does not explain the root cause.
Prevention and Maintenance
To Find Problems Before an Outage, Every Inspection Must Be Recorded and Reviewable
Preventive Checks
- Keep a brief fault-report form in the generator room covering time, status, alarm, load impact and observed symptoms.
- During inspections, take consistent photos of the controller, ATS, low-voltage switchgear, fuel level and battery condition.
- Record every test run, maintenance visit and fault recovery to create a useful operating baseline.
Maintenance Routine
- When a fault occurs, protect people and loads first, then record the key observations and avoid repeated starting attempts without a clear reason.
- Retain alarm screens, meter readings, abnormal sounds and site photos to help the engineer locate the affected section.
- After power is restored, record the final cause, corrective action and follow-up prevention items to avoid a repeat.
Engineering Recommendation
A good fault report improves diagnostic efficiency. It does not replace engineering work; it reduces wasted effort so time can be focused on confirming the root cause and restoring power.