Power Plant Controller Vendors Compared for Solar and Storage

Who wrote this, and how to read it

WATTMORE builds Intellect PPC, the power plant controller inside Intellect Operate. That is a reason to be careful with this page, not a reason to skip it. Every claim below about another vendor comes from that vendor’s own product page, datasheet, or press release, linked in the sources, as read in September 2026. Where a vendor does not publish a fact, the table says not published rather than guessing. Intellect PPC is described from the same kind of material, its public product page and technical brief, and gets no extra credit for being ours.

Read the table as a record of what each vendor is willing to state in writing. A blank is a question to ask, not a verdict. A vendor with a short public page may have a long datasheet under NDA, and the reverse is also true.

What does a PPC do that an EMS does not?

The energy management system decides what the plant should do: the MW setpoint that earns the most given prices, forecasts, and the battery’s state. The power plant controller decides what the plant is allowed to do: it measures frequency, voltage, and power at the point of interconnection and adjusts every inverter so the plant meets its interconnection agreement. Frequency watt droop, voltage and reactive power control, ramp rate limiting, curtailment, and state of charge protection are PPC functions. The EMS plans on one second to fifteen minute timescales; the PPC enforces in tens of milliseconds.

PPC, EMS, and SCADA are increasingly overlapping products. A vendor may call something an EMS that does not provide the deterministic POI control a PPC does, and a SCADA vendor may bundle a PPC on an industrial controller. The architecture should be specified functionally rather than by product name: who computes the setpoint, who enforces the grid code on it, and whether they share a control loop.

The vendors, side by side

Twelve vendors with a published PPC product for solar, storage, or hybrid plants. Grid codes and standards are listed only where the vendor names them on the cited page.

Which control functions does each vendor name?

Every vendor names active power control and some form of reactive power or voltage control. The differences are in what else is stated. Ramp rate control is named by WATTMORE, Power Factors, GE Vernova, Elum, TMEIC, Emerson, ETAP, IHI Terrasun, Gantner, and meteocontrol. Frequency response is named by WATTMORE, Power Factors, GE Vernova, Ingeteam, Elum, Emerson, ETAP, Gantner, and meteocontrol. Closed loop coordination of a hybrid PV plus BESS plant at the POI is described explicitly by Power Factors, FlexGen, Emerson, ETAP, IHI Terrasun, and Ingeteam.

Functions that only some vendors name are worth asking every vendor about: state of charge protection and balancing, which WATTMORE, Elum, ETAP, IHI Terrasun, and Hitachi Energy mention; automatic generation control signal following, which WATTMORE, Trimark on the SCADA side, and IHI Terrasun mention; islanding and black start, which Elum and Emerson mention; nighttime reactive power and capacitor bank control, which FlexGen and Power Factors mention; and zero export, which Gantner and meteocontrol mention. Fleet dispatch across inverters, with equal, proportional, and priority allocation, is a WATTMORE claim; Power Factors describes optimal power distribution.

Where does the PPC live, and why does it matter?

Three architectures appear in the table. A hardware cabinet or skid, from Ingeteam, Elum, Gantner, meteocontrol, TMEIC, and GE Vernova, arrives as a certified box and connects to whatever EMS and SCADA the site has. Software on an industrial controller, from Emerson, Hitachi Energy, and the SCADA vendors, runs in the plant automation platform. Software integrated into the EMS, from WATTMORE, FlexGen, IHI Terrasun, and Power Factors, shares a data bus with the optimizer.

The choice decides who owns the boundary between the setpoint and the grid code. When the EMS and the PPC come from different vendors, every dispatch command crosses a vendor boundary, and the integration between them is tested at commissioning and defended during every incident. When they share a control loop, the EMS cannot send a command the PPC cannot execute safely, and one support team answers for both. The counter argument is real too: a certified standalone cabinet with a national grid code component certificate is what some utilities and lenders want to see, and it survives a change of EMS vendor.

What should an RFP ask that the product pages do not answer?

The facts that separate PPC vendors in practice are rarely on a product page. A short scorecard of twenty to thirty criteria, weighted for the plant, settles the choice faster than a feature list.

• The plant dynamic model: is a validated PSCAD or PSS/E model of the controller available for the interconnection study, and who maintains it through firmware updates?
• Closed loop accuracy at the POI: the measured error between the commanded and delivered active and reactive power at the meter, under steady state and during a ramp.
• Response time as measured, not as claimed: from a frequency excursion crossing the deadband to the change in plant output at the POI.
• Inverter, PCS, and BMS interoperability: the list of models integrated in the field, and how a new register map is added.
• State of charge management: what the controller does as the battery approaches its limits, and whether derating is smooth or a step.
• Curtailment and ramp behavior: separate up and down rates, ramp limiter bypass during frequency events, and what happens when a curtailment order and a droop response conflict.
• Fault ride through and islanding: which functions are in the controller and which are executed and certified at the inverter.
• Redundancy and failure modes: what the plant does when the controller loses a block of inverters, the meter, or its own power.
• Cybersecurity: the named standard, the audit record, role based access, and the network posture the controller expects.
• Support: the escalation path during an event, the release cadence, and how a rollback is performed.

How Intellect PPC fits, stated plainly

Intellect PPC is a software power plant controller that ships as part of Intellect Operate and runs in the same control loop as the EMS on the site appliance. Its published functions are frequency watt droop with a configurable droop percentage and deadband and a ramp limiter bypass during frequency events, three reactive power modes including constant power factor, voltage regulation, and a volt var curve, asymmetric ramp rate limiting, soft and hard state of charge limits with derating curves, fleet dispatch with equal, proportional, and priority allocation, and AGC signal following. It communicates with inverters over Modbus TCP with flexible register mapping and is designed to the IEEE 2800 and IEEE 1547 grid support requirements.

What it is not: a standalone certified cabinet with a national grid code component certificate, and a product with a published redundancy architecture on its public page. A buyer who needs either should ask, and the table above shows which vendors publish them. The strongest reason to choose an integrated PPC is the one integration boundary it removes; the strongest reason to choose a standalone one is the certificate it carries.