Load-bank step interval logs before generator commissioning witness

Direct answer

Before a datacenter generator load-bank commissioning witness, the step interval log should identify the generator or plant, test authority, approved procedure, load-bank type and capacity, load-bank power factor where applicable, connection point, cable or docking-station setup, instrument IDs, calibration status required by the project, safety boundary, prestart checks, fuel source, coolant and lube-oil condition, ambient condition, start method, each load step, each dwell interval, and each recovery interval.

For every load step, record commanded load, measured kW, kVA or kvar where used, percent of service load or rated output, time applied, time removed, voltage, current, frequency, power factor, engine speed, oil pressure, coolant temperature, lube-oil temperature, exhaust temperature where available, fuel pressure where available, alarms, smoke or exhaust observations, ATS or paralleling status, and the witness or operator who accepted the reading. If the procedure calls for transient response, record before and after values, overshoot or undershoot, recovery time, and whether the reading stabilized within the project criterion.

Do not make up a universal step interval. The accepted load percentages, dwell times, data interval, recovery criterion, load-bank type, witness hold points, and retest rules come from the commissioning plan, project specifications, manufacturer instructions, NFPA/AHJ basis where applicable, owner standard, test agency procedure, and site safety plan.

Step intervals make witness review possible

A load-bank witness does not need a vague note that says the generator passed. The witness needs to see how the set moved from no load to each applied block, how long each block was held, what the instruments read, what changed when load was added or removed, and whether any alarm, heat, fuel, exhaust, vibration, voltage, or frequency behavior forced a hold.

The interval log creates that chain. It lets the commissioning agent, owner, electrical contractor, generator vendor, switchgear team, and operations team compare the actual sequence to the approved script. It also shows whether the team skipped a hold point, shortened a dwell, changed the load bank, changed the connection, adjusted controls, or repeated a failed step.

In a datacenter, that matters because generator commissioning often sits between factory test data, field startup, switchgear testing, ATS testing, paralleling controls, UPS interaction, integrated systems testing, and owner turnover. A clean step log prevents one successful heat run from being mistaken for every required generator, paralleling, transfer, and integrated test.

Start with the approved test basis

The first line in the record should name the test basis. Use the commissioning plan, owner project requirements, basis of design, project specification, approved generator submittal, factory test report, manufacturer startup procedure, NFPA or AHJ requirement where applicable, NETA or test-agency procedure, MOP, and owner operations requirement that control the witness.

Then name the exact test. Continuous load run, step-load response, voltage and frequency droop, voltage regulator range, governor range, automatic operation with ATS, paralleling operation, load sharing, black-start, return-to-normal, or integrated systems testing are different records. The log should not hide them under one load-bank label.

If the procedure changes in the field, write the change. Record who approved it, why it changed, what step it affected, and whether the witness accepted the revised script. A revised load-bank setup, changed power factor, failed cable, unavailable building load, fuel restriction, weather hold, or controls adjustment can change what the test proves.

Identify the load bank and connection

Record the load-bank make, model, capacity, voltage, phase, frequency, resistive/reactive capability, step resolution, control method, fan/control power source, calibration or verification record required by the project, and whether the load bank is portable, trailer-mounted, radiator-mounted, permanent, rack-mounted, medium-voltage, or connected through a docking station.

The connection record should include generator ID, output breaker or paralleling gear section, load-bank connection cabinet, docking station, temporary cable count and size, cable routing, phase identification, grounding/bonding, barriers, weather protection, heat and exhaust clearance, fan discharge clearance, communication cable or remote-control location, and the person responsible for connection approval.

If the test uses actual building load along with load banks, separate the two. Identify actual load source, transfer switch, UPS or PDU state, load-shed state, paralleling controls, and the expected load contribution. A record that only says 75 percent load is weak if no one can tell how much came from the load bank and how much came from the facility.

Separate load level, dwell, and recovery

A step interval log should not treat a step as a single timestamp. It needs at least three ideas: the load level commanded, the dwell time at that load, and the recovery behavior after the load changed.

For each step, record the planned load, actual measured load, time load was applied, time the reading was taken, time the step ended, and whether the load was held long enough for the procedure. If the procedure requires readings every 15 minutes, 20 minutes, at each steady state, or before and after each block load, keep those labels visible in the table.

For recovery, record the values required by the script. That may include voltage and frequency just before the step, minimum or maximum excursion after the step, recovery time, steady-state band, strip chart or digital recorder file, and pass/hold decision. If the test only calls for operating readings, do not invent transient metrics. If it does call for transient metrics, do not replace them with a slow manual snapshot.

Use a table the witness can audit

Use the owner form, commissioning script, vendor startup sheet, NETA/test-agency form, or project test report first. Add a field table only where the required form does not make the step sequence easy to audit.

Record engine and electrical readings together

Electrical readings alone do not explain a generator load-bank result. Pair voltage, current, frequency, kW, kVA, kvar, and power factor with engine speed, oil pressure, coolant temperature, lube-oil temperature, fuel pressure where available, exhaust temperature where available, ambient temperature, jacket-water heater status, ventilation status, and alarms.

This helps the reviewer separate electrical performance from engine and support-system behavior. A voltage/frequency event may trace back to governor response, load block size, fuel supply, cooling airflow, controls, paralleling logic, or the load-bank setup. A thermal hold may have nothing to do with the alternator but still stops the witness.

Use the readings available from permanent meters, load-bank controls, calibrated test instruments, generator controller logs, strip charts, and digital recorders as the project allows. If a reading is not available, mark it not available and explain why. Do not leave a blank cell where a failed or unavailable reading should be.

Witness holds and retests need their own lines

A retest should not overwrite the failed attempt. Keep the original step, the reason it failed or was stopped, the correction, the approving person, and the retest step. That makes it clear whether the final pass followed an adjustment, repair, load-bank change, controls change, or changed acceptance criterion.

Typical hold reasons include unstable voltage or frequency, generator alarm, high coolant or oil temperature, low oil pressure, fuel pressure problem, smoke or exhaust issue, vibration concern, load-bank fan or control issue, temporary cable issue, unsafe clearance, weather issue, communications failure, ATS or paralleling control issue, or witness disagreement about the script.

If any adjustment is made between steps, write it. The WBDG generator specification language treats repeated readings and no-adjustment repeats as important in several test sequences. Field records should make the same distinction visible: no adjustment, adjustment made, repair made, step repeated, entire test repeated, or test held.

Keep generator test, ATS test, and IST separate

The load-bank step log can support later commissioning, but it should not claim that transfer, paralleling, UPS, switchgear, cooling, fuel, controls, and integrated systems testing are complete unless those tests were actually performed and witnessed.

If the load-bank test includes automatic transfer or paralleling, record the exact sequence. Loss of normal, engine start, breaker close, transfer, load share, load add, load shed, return to normal, cool-down, and reset are separate events. If the test is only a standalone generator load run, write that boundary.

For datacenter work, also record what the step log releases. It may release generator startup to the next commissioning step, support owner witness acceptance for one generator, clear a retest, or remain only a vendor startup record. It should not silently release IT load or operations handoff.

Before generator witness checklist

Run this check before the commissioning witness signs the load-bank step record or lets the team move to the next test.

• Confirm the generator ID, plant lineup, rating, voltage, fuel source, controller mode, switchgear, ATS, paralleling, and building-load boundary.
• Attach the approved test procedure, MOP, commissioning script, owner standard, manufacturer startup sheet, and revision used for the witness.
• Verify the load-bank type, capacity, voltage, phase, frequency, power factor capability, step resolution, connection point, temporary cable setup, and grounding/bonding record.
• Record instrument IDs, recorder files, load-bank controller logs, calibration or verification status required by the project, and who owns each reading.
• Record prestart checks: fuel, coolant, lube oil, battery, charger, heaters, ventilation, exhaust, alarms, ambient, enclosure condition, and safety boundary.
• Build the step table before starting: planned load, expected dwell, required reading interval, recovery metric, hold point, and witness signoff point.
• During each step, record commanded load, measured load, voltage, current, frequency, power factor, RPM, oil pressure, temperatures, alarms, start time, reading time, and end time.
• Where transient response is required, attach the strip chart or digital trace and record before/after values, excursion, recovery time, and pass/hold decision.
• Write every deviation: missed interval, shortened dwell, changed load block, load-bank issue, alarm, temperature hold, fuel issue, safety stop, controls adjustment, or witness objection.
• If a step is repeated, preserve the failed attempt, correction, approving person, retest readings, and final decision.
• Separate the release decision: generator startup accepted, load run accepted, step-load response accepted, ATS test pending, paralleling pending, IST pending, or owner acceptance held.

Weak and strong witness notes

Weak note: Generator load bank passed.

That note does not identify the generator, procedure, load-bank setup, load steps, intervals, readings, instruments, witness, deviations, retests, or what the pass actually released.

Stronger note: Generator G-3 load-bank witness completed for Data Hall 2 under MOP-EPSS-014 revision 6 and commissioning script CX-GEN-LB-03. Basis included project specification 26 32 15, manufacturer startup sheet, owner Cx plan, and AHJ witness hold point for this generator only. Load bank LB-2 was connected at the exterior docking station with verified phase rotation, grounding, cable count, and fan clearance. Instrument IDs and load-bank controller export are attached. Prestart checks recorded fuel day-tank level, coolant, lube oil, battery charger, jacket-water heater, ambient temperature, ventilation status, controller in auto, no active alarms, and safety boundary released by the electrical supervisor.

The step table records no load warm-up, 25 percent, 50 percent, 75 percent, and 100 percent service-load steps, with applied time, reading time, dwell duration, measured kW, voltage, current, frequency, power factor, RPM, oil pressure, coolant temperature, lube-oil temperature, exhaust temperature from the generator controller, and alarms at each interval. The 75 percent step was held for a fuel-pressure alarm investigation, correction documented under issue CX-241, then repeated with witness approval. The transient-response trace for the final 100 percent step is attached as recorder file G3-LB-20260609-TRACE01. Generator G-3 load-bank step sequence accepted for progression to ATS functional testing. Paralleling test, integrated systems test, and IT load release remain pending.

The stronger note works because it keeps the failed step, correction, retest, attached data, and release boundary visible. It does not turn one load-bank witness into total generator plant acceptance.

Common mistakes

The first mistake is recording only final percent load. A witness needs the path: each step, each interval, and what happened when load was added or removed.

The second mistake is mixing rated output, service load, actual building load, and load-bank command. The table should say which basis each percentage uses.

The third mistake is ignoring power factor. A resistive-only load bank and a resistive/reactive test do not prove the same things. Record the load-bank type and project requirement.

The fourth mistake is overwriting failed attempts. A later pass does not erase a shortened dwell, alarm, control adjustment, cable issue, or safety stop.

The fifth mistake is using the load-bank report as an integrated systems test. Generator load-bank data can support IST, but it does not prove transfer, paralleling, UPS, cooling, alarms, and operations sequences unless those tests are included and documented.

The sixth mistake is treating the witness signature as permission to bypass the safety plan. Energized work, temporary cables, load-bank heat, exhaust, fuel, noise, weather, and switching all need the approved site controls.

Questions that come up

What interval should readings be taken at? Use the approved procedure. Some specifications use fixed intervals during operating runs. Some step-load tests require before and after readings for each load change. The public field note should not invent a universal interval.

Does a 100 percent load-bank run prove the generator plant is commissioned? No. It can support generator acceptance or startup, but ATS operation, paralleling, load sharing, UPS interaction, alarm response, fuel system behavior, and integrated systems testing may be separate procedures.

Should the log include building load? Yes, if actual building load is part of the test. Separate load-bank contribution from actual load so the witness can see the source of the applied load.

Can a load-bank controller export replace a field log? It can support the record, but the field log should still identify the approved procedure, equipment, connection, instruments, witness, deviations, safety boundary, and release decision.

Who should sign the step interval log? Use the commissioning plan and contract. The signers may include the generator technician, electrical contractor, testing agency, commissioning agent, owner representative, AHJ, facility operations lead, or safety representative depending on the witness scope.

Compliance and safety limits

This field note is not a generator design, NFPA interpretation, NETA procedure, manufacturer startup instruction, commissioning script, MOP, hazardous-energy procedure, energized-work permit, load-bank operating manual, fuel-system approval, emissions approval, AHJ approval, or owner acceptance. The approved project documents, manufacturer instructions, commissioning authority, engineer, AHJ, owner, qualified electrical workers, generator vendor, testing agency, operations team, and site safety plan control the work.

Do not use this checklist to bypass lockout/tagout, switching orders, temporary-cable controls, arc-flash boundaries, PPE, grounding/bonding, fuel handling, exhaust routing, heat clearance, noise control, weather limits, fire protection, spill controls, emissions controls, confined-space rules, traffic control, lift plans, qualified-person requirements, or emergency procedures. The log preserves the commissioning witness record. It does not authorize unsafe testing or unapproved release.

Sources checked

• NFPA, NFPA 110 Standard DevelopmentUsed for official NFPA 110 standard identity and emergency and standby power system scope context.
• WBDG, UFGS 26 32 15 Engine-Generator Set Stationary 15-2500 KW, with AuxiliariesUsed for project-specification examples covering load-bank tests, service-load runs, 15-minute readings, step-load sequences, voltage/frequency recovery, load power factor, instruments, and retest treatment.
• WBDG, UFGS 26 08 00 Apparatus Inspection and TestingUsed for acceptance test procedures, certified reports, qualified testing organization context, start-up engineer ownership of load-bank tests, and system acceptance linkage.
• WBDG, VA Section 26 32 13 Engine GeneratorsUsed for generator load-test data fields, 20-minute factory-test interval example, cold-start records, and load-bank/instrument responsibility examples.
• Cummins, T-030 Liquid-Cooled Generator Set Application ManualUsed for generator application context, access for load-bank testing, load step considerations, and manufacturer-controlled application limits.
• Kohler, ISO 8528-5 and Generator Transient PerformanceUsed for transient-performance context around generator load acceptance, voltage/frequency deviations, recovery, and performance-class language.
• Avtron, Load Bank Testing to Ensure Generator Set PerformanceUsed for load-bank purpose, resistive versus resistive/reactive distinctions, voltage regulator, governor, cooling, fuel, wet-stacking, controls, and transient testing context.
• ASCO, Avtron and Froment Load Bank OverviewUsed for load-bank device definition, power systems commissioning, long-term tests, transient response tests, resistive/reactive options, and load-test data capture context.
• Caterpillar, Application and Installation Guide Generator SystemsUsed for generator application context and manufacturer-guided installation and system considerations.
• ASHRAE, CommissioningUsed for public commissioning-process context around owner requirements, procedures, documentation, reports, and new-system commissioning resources.
• Building Commissioning Association, New Construction Building Commissioning Best PracticesUsed for commissioning scope, schedule, roles, owner project requirements, basis of design, testing scope, issue logs, and turnover documentation context.
• CxEnergy, Commissioning Electrical Systems in Mission Critical FacilitiesUsed for mission-critical electrical commissioning context, interaction of energy supply and load, and normal-to-standby functionality.
• OSHA, 29 CFR 1910.147 Control of Hazardous EnergyUsed for hazardous-energy, lockout/tagout, testing/positioning, outside personnel, and shift-change safety-limit context.

Related guides