Handover should explain the equipment identity, intended duty and normal operating arrangement. The operator needs to know where the applicable instructions and records are held, what routine observations are required and when competent assistance is needed. Familiarisation should reflect the installed configuration rather than a generic presentation about generators.
Confirm the documents being handed over
Relevant records may include the equipment manuals, installed drawings, commissioning results, settings references and maintenance requirements. Identify their revisions and any outstanding items. A collection of unrelated manuals is not a reliable substitute for documentation that matches the actual engine, alternator, controller and installation.
Application details
Handover should transfer enough information for the customer to operate and maintain the system responsibly.
Related photographs and videos
Handover can include
- asset identification
- operating information
- controller overview
- alarm awareness
- maintenance requirements
- manuals/documentation
- commissioning records
- outstanding items
Operator boundary
- bypass safety devices
- alter protection
- perform live electrical work
- override shutdowns
Explain warnings and shutdowns
The handover should identify the relevant alarms, the expected operator response and the conditions requiring competent assistance. A warning, controlled stop and emergency shutdown have different purposes. Use the approved equipment logic rather than a generic alarm list.
Keep responsibilities clear
Agree the point at which operating responsibility transfers and how defects or support requests will be reported. Clarify the routine checks assigned to the site, the maintenance arrangements and any contractual support boundaries. If part of the installation remains incomplete or a test is deferred, record that condition explicitly. Handover should leave the operator with a clear understanding of the system’s intended use and its current status.
Request Generator Service
Request Generator Service. Share the application, location and information available so the next discussion can address your actual requirement.
Related guidance
Engineering intent
Start-Up & Handover should be evaluated as part of the complete power system rather than as an isolated catalogue item. Operating duty, connected load, interfaces, protection, controls, installation conditions, testing requirements and lifecycle consequences determine whether the arrangement is appropriate.
Engineering considerations
Auto / manual / stop mode
| Availability during real outage | Start / stop logic |
|---|---|
| Reliable cranking, running and shutdown sequence | Alarm history |
| Evidence of what happened before failure | Sensor inputs |
| Oil pressure, coolant temperature, speed, fuel, battery | Output relays |
| Start, stop, common alarm, common shutdown, breaker signals | AMF / ATS interface |
| Source failure to generator start and transfer readiness | AVR / voltage sensing |
| Voltage alarm and output stability interface | Communication |
| BMS, SCADA, remote monitoring or gateway signals | Settings |
| Timers, thresholds, crank attempts, cooldown and delays | Documentation |
| Configuration sheet, alarm matrix and handover record | Controller service must prove what the controller sees, what it decides, what it commands, what it records, and what the operator must do next. |
Selection and design considerations
Required runtime affects tank planning and operating strategy. The generator and surrounding system should distinguish normal operating conditions from abnormal conditions requiring alarms, controlled shutdowns or protective trips. A successful start is not the same as demonstrated readiness. Testing and ongoing maintenance help determine whether the system can perform when required. Control-system design should remain understandable, maintainable and appropriate to the operating requirement. Automation should reduce operational risk—not create unnecessary complexity. Protection Is a Strategy, Not a Collection of Relays Selectivity — isolate the appropriate part of the system. Coordination — ensure breakers, relays and system logic work together. • reverse-power or other functions where relevant to the architecture. Specific protection requirements depend on machine rating and system configuration.
Integration and protection considerations
Monitoring data should be checked for meaning, not merely connection. A system may report generator status without allowing remote operation. Read-only visibility and remote start/stop are different capabilities. Commissioning documentation should record relevant configuration according to project scope. A useful commissioning package can include an alarm matrix. Do not decide after the test what “pass” means. Condition noted; may require monitoring or later action. Testing cannot proceed until an issue is resolved. A vague “OK” is not a commissioning record. Punch items should be assigned, tracked and closed. Critical unresolved items should not disappear into informal conversation. Commissioning should identify whether the installed system matches the design drawings.
Testing, commissioning and verification
rental power, installation, commissioning, testing, service, AMC, diagnostics, repairs and emergency support. Each public case study is published only after Core proof should include rental order, deployment details, generator rating, load requirement, cable/distribution scope, fuel scope and handover record. Core proof should include supply scope, site readiness, installation support, cable/ATS/fuel/exhaust/ventilation boundaries, commissioning record and handover notes. Core proof should include controller/panel status, functional test, auto-start test, transfer test, retransfer test and alarm records. The complete power-continuity source describes the practical backup sequence: UPS supplies load, AMF detects mains failure, generator starts, voltage/frequency stabilise, ATS transfers load and UPS returns to charging. Core proof should include test objective, load level, duration, readings, alarms, observations, limitations and final report.
Operating and lifecycle considerations
A project should not hand over drawings that no longer represent reality. Handover should explain how the system is intended to be operated. The operating team should not inherit an unexplained power system. Training does not replace technical maintenance, but it reduces operational confusion. Standby commissioning should verify readiness for source failure. Standby power is not proven by unloaded running alone. Rental commissioning may need a tighter site-specific sequence because the system is temporary. A generator-only test is not a complete data-centre power-chain proof. Critical facilities should commission according to the actual facility requirements and applicable project/professional standards.
Direct answer
Handover should explain the equipment identity, intended duty and normal operating arrangement. The operator needs to know where the applicable instructions and records are held, what routine observations are required and when competent assistance is needed.
The practical decision for Start-Up & Handover should be based on verified load, equipment, interface and site information. Where equipment-specific data, regulatory applicability or a project study is required, this guidance does not replace that verification.