How to Commission a VFD-Controlled Pump Skid: FAT, SAT, and Startup Steps for Panel Builders

Why commissioning matters on VFD pump skids

A VFD-controlled pump skid is only as good as its commissioning record. By the time the skid leaves your shop, the panel may look complete, the wiring may test out, and the HMI may respond to every button. But if the pump, motor, drive, instruments, and PLC are not validated as one system, the first startup becomes the real test.

That is where FAT, SAT, and startup come in.

For panel builders, commissioning is not just a final checkbox. It is the point where you prove compliance with IEC 60204-1, IEC 61800-5-1, IEC 61800-3, NFPA 70, NFPA 70E, and, where applicable, NFPA 79. If the skid includes process safety functions, add ISA-84.00.01 and the site’s functional safety requirements. For pump performance, ISO 9906 and API 610 / ISO 13709 often govern the acceptance logic for centrifugal pumps.

The practical goal is simple: hand over a skid that starts cleanly, controls flow or pressure accurately, and survives 24/7 operation without nuisance trips.

Define the skid and the acceptance criteria first

Before you energize anything, freeze the system boundaries. A typical package might include:

• 50 HP, 460 V, 60 Hz motor
• centrifugal pump
• ABB ACS880 or Siemens SINAMICS G120 VFD
• NEMA 3R or NEMA 12 panel
• pressure transmitters, flowmeter, level switch, and E-stop loop
• PLC such as Siemens S7-1500, Rockwell ControlLogix, or Schneider Modicon M580
• SCADA integration through Ignition, AVEVA System Platform, or COPA-DATA zenon
• Modbus TCP, EtherNet/IP, or PROFINET communications

Write the acceptance criteria before FAT. Typical examples:

Item	Acceptance target
Motor rotation	Correct direction at first bump test
Ground continuity	Verified to panel ground bus
Insulation resistance	Within vendor and project spec
VFD tuning	Completed and saved
Flow control	Stable at setpoint with no hunting
Vibration	Within baseline and vendor limits
Alarms/interlocks	All cause-and-effect points proven

If you do not define pass/fail before the test, you will define it during the argument.

1. Pre-commissioning checks before FAT

Pre-commissioning is where most avoidable failures are caught. This work aligns with IEC 60204-1:2016 Clause 14 on verification and NFPA 70E Article 130.5 for energized work risk control. It also supports the EU Machinery Directive conformity path when the skid is CE marked.

Mechanical checks

Start with the machine side:

• confirm baseplate is level and fully grouted
• verify anchor bolt torque
• inspect coupling guards
• check pump-to-motor alignment with a laser
• confirm piping is supported independently of the pump nozzles
• open and stroke valves
• flush lines before connecting instruments
• verify seal flush, cooling water, and drain paths

For alignment, a practical target is often around 0.05 mm/m or better, subject to the pump vendor’s tolerance. Do not assume the factory alignment survived shipping. It rarely does.

Hydrotest piping and pressure-containing components per project spec and the governing piping code, often ASME B31.3 Clause 345.4. For a 100 psi design system, a 1.5x hydrotest would be 150 psi, held with no leakage for the specified duration.

Electrical checks

The panel builder’s side should include the following:

Check	Procedure	Typical pass criteria	Reference
Grounding	Measure continuity to panel ground bus	Low resistance, per project spec	IEC 60204-1 Clause 8.2, NEC 250
Insulation resistance	Megger motor and field wiring with drives isolated	Project and vendor minimums met	IEC 61800-5-1 Clause 4.5.2
Terminations	Torque per terminal schedule	No loose strands, no damage	NEC 110.14
Control power	Verify 120 VAC or project voltage	Stable under load	Panel design spec
Drive nameplate data	Match motor volts, amps, Hz, RPM, kW	Exact match to motor nameplate	Vendor commissioning guide
EMC measures	Check shield terminations and routing	No obvious noise paths	IEC 61800-3

A VFD installation lives or dies by grounding, shielding, and cable segregation. If the encoder, pressure transmitter, or analog loop shares a noisy route with the output cable, expect trouble later.

Practical pre-FAT checklist

Use a signoff sheet with at least:

1. mechanical completion
2. torque verification
3. cable megger results
4. I/O point-to-point checks
5. drive parameter backup
6. PLC program version control
7. HMI screen review
8. safety circuit continuity
9. instrument calibration status
10. spare parts and manuals delivered

Commissioning fatigue is real. A disciplined checklist prevents the classic “we assumed that was already done” failure.

2. FAT at the panel builder’s facility

The Factory Acceptance Test is your best chance to catch defects while the skid is still on your floor and the client is still available. It is also the cheapest place to fix a problem. Reliability studies consistently show that post-installation corrections can cost many times more than shop fixes.

What to prove during FAT

For a VFD-controlled pump skid, FAT should prove:

• wiring correctness
• drive parameterization
• PLC logic
• HMI alarms and graphics
• safety interlocks
• communications
• simulated process response

If the pump can be run uncoupled or dry-tested safely, do it. If not, use a suitable test arrangement to validate the drive and controls without risking the pump.

FAT sequence

1. Visual and mechanical review

Confirm:

• nameplates
• wire labels
• terminal numbering
• cable gland integrity
• enclosure sealing
• fan filters
• panel clearances
• door interlocks
• printed documentation set

2. Electrical power-up

Energize the control system first, then the drive according to the vendor procedure. For an ABB ACS880 or Siemens SINAMICS G120, verify DC bus behavior, precharge, and no active fault before enabling run commands.

3. Drive setup and motor identification

Enter the motor data exactly as shown on the nameplate:

• kW or HP
• voltage
• current
• frequency
• RPM
• power factor if required

Then perform the vendor’s motor identification routine. On many drives this includes a static test and, if allowed, a rotating tune. This step is critical for torque control, current limiting, and stable speed regulation.

4. I/O simulation

Simulate the process signals:

• 4-20 mA pressure input
• 4-20 mA flow input
• discrete permissives
• E-stop
• level switch
• overload trip
• phase loss
• communication loss

Validate scaling in both PLC and SCADA. A common error is one layer scaling 4-20 mA as 0-100% while another layer treats it as engineering units.

5. No-load or uncoupled run

Ramp the drive from minimum speed to full speed. Check:

• motor rotation
• current draw
• fan operation
• abnormal noise
• vibration
• bearing temperature
• drive status words
• command response

A useful benchmark for many rotating machines is vibration in the acceptable range per ISO 10816-3 or the newer ISO 20816-1, depending on the asset and project basis.

FAT test matrix

Test	Method	Expected result
Start/stop	Local and remote commands	Stable run and stop
Speed reference	HMI, analog, and comms	Correct response
Interlocks	Open permissive one at a time	Safe trip response
Alarm handling	Simulate fault conditions	Clear alarm text and latch logic
Communications	Modbus TCP, PROFINET, or EtherNet/IP	No packet loss or mapping errors
Safety circuit	E-stop and door interlock	Immediate safe shutdown

Example drive settings

For a Siemens SINAMICS G120 or ABB ACS880, FAT usually includes:

• motor data entry
• acceleration and deceleration times
• minimum and maximum frequency
• current limit
• flying start or catch-on-the-fly if the process requires it
• PID loop tuning if the drive closes the pressure or flow loop

A simple pump PID often starts with a modest proportional gain and a moderate integral time, then gets refined during SAT:

# example commissioning calculation for pump speed reference
# target flow = 400 GPM, measured flow = 360 GPM
# assume proportional gain Kp = 0.5 % speed per % error
target = 400
measured = 360
error_pct = (target - measured) / target * 100
speed_trim = 0.5 * error_pct
print(speed_trim)

The point is not the exact tuning value. The point is to establish a repeatable method and document the final settings.

3. SAT at the customer site

The Site Acceptance Test proves the skid works in its real environment. This is where piping, utilities, process fluid, upstream controls, and actual site conditions reveal what the FAT could not.

If the skid is part of a safety instrumented function, apply the site’s ISA-84.00.01 lifecycle requirements and the project’s SIL verification records.

SAT sequence

1. Site readiness review

Before startup, confirm:

• utilities are live
• suction and discharge piping are complete
• strainers are clean
• valves are in the correct position
• instruments are calibrated
• grounding is intact
• MCC or feeder protection is coordinated
• SCADA tags match the as-built database

2. Dry run

If permitted, perform a short dry or uncoupled run. The goal is to verify:

• rotation
• direction
• command response
• no mechanical interference
• stable drive behavior

Never force a dry run if the pump vendor prohibits it. For some pump types, especially process-critical or seal-sensitive units, the vendor’s limits govern.

3. Water or clean-fluid run

Bring the skid up on clean fluid first. This confirms the hydraulic side before you introduce the actual process media.

Check:

• suction pressure
• discharge pressure
• flow
• speed
• motor current
• temperature rise
• vibration
• control stability

Compare the operating point to the pump curve. If the pump is not near its intended duty point, do not tune around a bad system curve. Fix the piping or process assumption first.

4. Process-fluid run

If the application involves slurry, sludge, or a viscous product, observe pulsation, cavitation, and pressure ripple. Positive displacement pumps, double-disc pumps, and some specialty pumps may need dampening or pulsation control. A bouncing needle on the gauge is not a “small issue.” It is a sign the system is not stable.

5. Control loop tuning

For pressure or flow control, tune the loop in the actual plant environment. A typical pump loop may use:

• pressure transmitter feedback
• VFD speed output
• anti-windup logic
• minimum speed limit
• sleep/wake logic for energy savings

SAT acceptance table

Parameter	Example target	Notes
Flow stability	No hunting at setpoint	Verify at multiple loads
Bearing temperature	Within vendor limit	Record baseline
Vibration	Within project limit	Save trend data
Drive faults	None during steady run	Investigate any nuisance trips
Pressure pulsation	Acceptable for process	Add dampener if needed
Communications	No dropouts	Confirm at SCADA and PLC

Useful standards during SAT

• IEC 60204-1 for machine electrical equipment
• IEC 61800-5-1 for drive safety
• IEC 61800-3 for EMC
• NFPA 70E for energized work controls
• NFPA 70 for installation rules
• ISO 20816-1 for vibration assessment
• ISO 9906 for pump performance testing

4. Startup and performance validation

Once SAT is complete, startup becomes a controlled handover rather than an experiment.

What startup should prove

• the skid starts from a cold condition
• the operator can run it from local and remote stations
• alarms are understandable
• shutdowns are safe and repeatable
• the process reaches performance targets
• the maintenance team has the baseline data

A good startup package includes:

• final drive parameter backup
• PLC and HMI backups
• as-built drawings
• instrument calibration sheets
• FAT and SAT signed records
• spare parts list
• recommended maintenance intervals

OEE and baseline data

If the client wants performance tracking, establish a simple baseline during startup:

• availability
• speed stability
• energy use
• average current
• vibration trend
• temperature trend

For example, if the skid runs 8 hours at 80% load, capture the data and define what “normal” looks like. That baseline becomes your reference for future troubleshooting.

Handover to operations

Train the operator and maintenance team on:

• start/stop sequence
• local/remote transfer
• alarm reset logic
• safe isolation points
• filter and fan maintenance
• how to restore a drive backup
• how to interpret flow, pressure, and speed trends

If the site uses SCADA platforms such as Ignition, AVEVA System Platform, or zenon, verify tag naming, alarm priorities, and faceplate behavior before release.

Common commissioning mistakes panel builders should avoid

Mistake	Consequence	Prevention
Wrong motor data in VFD	Overcurrent or poor tuning	Match nameplate before energizing
Poor shield termination	Noise and unstable analog signals	Follow EMC best practice
Scaling mismatch between PLC and HMI	Operator confusion	Validate one tag at a time
Skipping uncoupled tests	Mechanical damage risk	Prove drive first
No backup of final parameters	Slow recovery after fault	Save and archive everything
Ignoring pump curve	Bad process performance	Confirm duty point during SAT

A practical commissioning mindset

The best panel builders treat commissioning as a design verification process, not a field formality. FAT proves the build. SAT proves the installation. Startup proves the process.

If you keep the sequence disciplined, document every result, and anchor your work to the relevant IEC, NFPA, ISA, and pump standards, you reduce risk for everyone downstream. You also protect your margin, because rework after shipment is always more expensive than getting it right in the shop.

For complex VFD pump skids, the winning formula is straightforward: verify the hardware, prove the logic, tune in the real environment, and leave the customer with a complete record set. If you need help planning a standards-based commissioning workflow for a pump skid or control panel, /contact