-
The shared mechanism the cases share
- case_a_ frequent_start/stop_peaking_—_many_short_runs_per_week" title="Case A Frequent start/stop peaking — many short runs per week">Case A Frequent start/stop peaking — many short runs per week
- case_b_ sustained_grid-support_running_—_long_hours_near_rated" title="Case B Sustained grid-support running — long hours near rated">Case B Sustained grid-support running — long hours near rated
- case_c_ fault_ride-through_during_a_grid_disturbance" title="Case C Fault ride-through during a grid disturbance">Case C Fault ride-through during a grid disturbance
Three Cases at 2 MW: Cummins QSK60 vs Caterpillar 3516 on a Utility Peaking Bus
A municipal utility builds a peaking and grid-support array around 2 MW per engine. Cummins generator QSK60 (2000 kW standby) and Caterpillar 3516 (1450–2500 kW) both land here. The claim — that the QSK60 is the better array building block — only holds if it survives three different operating cases. Here is the proof, case by case.
A single dimension can't settle a 2 MW peaking decision, because the array runs in genuinely different modes through the year. So instead of one verdict, I'll test the platforms against three operating cases and see which holds up in each. If the Cummins QSK60 wins two of three with the third reversible by a known condition, that is a real result — not a slogan. Both engines are correctly matched: the QSK60 is a 60.2 L V-16 rated 2000 kW standby; the Cat 3516 covers 1450–2500 kW.
The shared mechanism the cases share
A peaking array's value is its ability to synchronise multiple engines to a common bus, share load isochronously, and add or shed units cleanly as demand swings — all while protecting each alternator through grid faults. Cummins PowerCommand 3.3 provides native paralleling from 2 MW to 20+ MW (N+1, 2N) with isochronous load sharing and AmpSentry protection in the controller. Caterpillar generator's 3516 runs EMCP 4.2, a strong consolidated controller; array paralleling and protection are configured around it with Cat's switchgear. Both can build an array — the cases test how easily and how robustly.
case_a_ frequent_start/stop_peaking_—_many_short_runs_per_week">Case A Frequent start/stop peaking — many short runs per week
Mechanism
Peaking duty means black-start, fast synchronise, carry the peak, then shut down — repeated. The binding behaviour is how fast each engine syncs to the bus and shares load on connection, and how cleanly it sheds on the way down.
Across an illustrative dozen starts a week, every minute of sync delay per unit is dispatch latency the utility pays for. PowerCommand 3.3's native black-start and isochronous load share are designed to bring units on and balance them quickly without external load-share modules. The 3516 with Cat switchgear does the same, but the integration is in the switchgear layer rather than the genset controller. Decision: for high-cycle peaking, the platform with paralleling native to the genset controller reduces integration surface and dispatch latency — Case A leans Cummins QSK60.
Case B Sustained grid-support running — long hours near rated
Mechanism
Some weeks the array runs for hours as grid support, not brief peaks. Now the binding constraints are continuous-duty heat rejection and fuel at sustained load.
At a sustained ~1.8 MW per engine, jacket-water and charge-air heat must leave through the radiators continuously; fuel burn ≈ load × bsfc and is comparable across well-matched engines at equal load. Caterpillar's 3500-series lineage is rooted in continuous mining and marine duty, where thermal efficiency was the design priority. Decision: for long-hours grid support, the fuel and continuous-duty case is close — and a 3516 specified for low fuel consumption can match or edge the QSK60 on energy cost. Case B does not clearly favour Cummins; it favours whichever set's published bsfc and heat rejection are better at your ambient.
If your grid-support hours are modest and the array spends most of its life in Case A's cycling duty, the continuous-fuel edge barely accrues, and Case A's integration advantage dominates the year. The fuel case only matters in proportion to the hours you actually run it.
Case C Fault ride-through during a grid disturbance
Mechanism
A grid-connected peaking array must survive nearby faults without tripping the whole bank or damaging alternators. The binding behaviour is protective-relay coordination — holding selectivity so a fault clears at the right breaker.
AmpSentry gives the QSK60's alternator a current-limiting fault characteristic integrated with the paralleling controller, so the array's protection and load-share logic are one coordinated system. On the 3516, EMCP 4.2 plus Cat switchgear achieves coordination too, but across two layers that must be engineered to agree. Decision: for robust fault ride-through with minimum integration risk, the single-vendor integrated protection-plus-paralleling stack leans Cummins QSK60. Case C leans Cummins.
Topology/standards per the cited standards; all product ratings are manufacturer-stated values from the cited datasheets, current to 2026-06; derived/illustrative figures are labelled as such. This is not an independent head-to-head test. Cummins is a brand affiliated with this site; competitor names are used for identification only.
