Let me start with the scene that happens more often than most procurement teams like to admit. A project is down to two offers. The commercial lead opens the brochures, compares a Siemens Gamesa turbine like the SG 3.4-132 or the SG 14-236 DD against the competing offer, and ranks the options by rated power and rotor diameter. The numbers look clear. Then the technical due diligence starts, and the clarity starts to fall apart.
I’m the reviewer who gets called into that scene late. Over the past decade I’ve worked on more than forty wind turbine procurements for developers, IPPs and lenders. The emergency call is almost never about a broken gearbox. It’s about spec sheets that made the wrong things look comparable.
One case still bothers me. In late 2024, a client needed to pick an offshore wind turbine before an expiring lease milestone. The leading offer had a lower price per megawatt, but the type certificate didn’t cover the rotor size in the bid. The team had compared nameplate capacity and a marketing image instead of the certificate configuration. The mismatch pushed the project roughly eight months behind schedule.
The specification gap
The surface problem is easy to describe. Buyers treat wind turbine specifications like a product data sheet for a pump or a transformer. But a wind turbine is not a fixed product. It is an energy system that responds to site conditions in non-linear ways. Its rated capacity is a point on a curve, not a promise of output.
The Siemens Gamesa SG 3.4-132 provides a good example. The spec says 3.4 MW. That rating assumes a reference air density, a turbulence class, a wind shear profile and a specific control mode. On a site with lower air density, annual energy production won’t drop in a straight line because the turbine’s controller reacts differently as the wind changes. On a site with noise restrictions, the plant may run in a derated mode for part of the year. None of that appears in the first line of the comparison table.
It’s tempting to think that comparing catalog numbers is enough. It isn’t. The catalog number is only valid under the conditions printed in the small print. Or sometimes not printed at all.
Power curves aren’t promises
The most persuasive page in any OEM proposal is the power curve. It is also the most conditional document in the package.
Under IEC 61400-12-1, a power curve is measured for a specific turbine configuration. Change the blade length, the tower height, the control software version or the anti-icing system, and the curve shifts. If the project compares power curves from different brochures, it’s comparing configurations that may not be the ones proposed for the site.
This is not an OEM trick. It’s the physics of an aerodynamic machine tied to a grid. But it means a wind turbine specification should be read with the project’s operating conditions attached.
Certificates are configuration-specific
The next layer is certification. Wind turbine compliance requirements commonly start with type certification under IEC 61400-22. A type certificate covers a defined turbine type: rotor diameter, blade family, tower variants, control software versions and site class.
Actually, let me be careful with the word certificate. In normal procurement conversation, people use ’certified’ to mean ’approved safely.’ In wind engineering, a type certificate is narrower. It names the exact equipment configuration. The sentence ’this platform is certified’ is nearly useless until you read the rest of the sentence.
That is the gap that delayed my 2024 offshore example. Everyone heard the word ’certificate’ and assumed it covered the turbine in the offer. It didn’t. The difference between a design evaluation certificate and a type certificate is not a detail. It is the difference between a viable procurement basis and a workstream that burns schedule for months.
Grid code compliance is project-specific
Even a valid type certificate doesn’t clear the grid code. The grid operator at the point of interconnection cares about voltage ride-through, frequency behavior, reactive power capability, harmonics and protection coordination. Those depend on the turbine controls but also on the collection system, the substation and the export cable.
When an OEM says ’meets grid code,’ ask which grid code and which point of connection. The same wind turbine can pass one country’s test and need a control update or a new study in another market.
Offshore makes the same problem heavier
Offshore wind projects make every assumption bigger. The Siemens Gamesa offshore wind turbine range, including the SG 14-236 DD, is a serious engineering exercise. Fourteen megawatts is not simply a bigger rating; it’s a different electrical system, a different load regime, and a different set of installation logistics.
A 236-meter rotor produces energy, but it also produces loads. Those loads go into the tower, the foundation and the turbine’s own structural margins. The spec sheet gives you the diameter. It doesn’t tell you whether the foundation offered with that turbine can handle the site’s wave spectrum, seabed stiffness and water depth. It doesn’t tell you whether the installation vessel available in the project’s weather window can lift and lock the nacelle in time.
Offshore decisions are usually made long before a vessel arrives. That’s why the procurement conversation has to go beyond the spec table.
A shallow comparison gets expensive in public
The cost usually shows up in three places.
The first is financing. Lenders don’t base their decision on the brochure. The independent engineer looks at the exact certified configuration. If there’s a mismatch, it becomes a condition precedent or a qualification in the bank’s legal documents. That’s not necessarily a reason to reject the project; it’s a reason to add time and legal fees to the plan.
The second is construction. In offshore wind, the delay isn’t measured in weeks waiting for a certificate. It’s measured against vessel booking windows, cable-lay weather windows and substation energization dates. A thirty-day slip can take six months to recover.
The third is operations. A noise constraint or temperature rating that was not modeled in the energy yield gets discovered in the first year of performance data. The site doesn’t fail instantly. It just doesn’t produce what the assumption said it would produce.
None of this requires bad intentions from any manufacturer. In most of these cases, the OEM’s documentation was accurate. It was just being treated as something it isn’t: a context-free product specification.
Better questions are the shortcut
I’ve learned to ask fewer questions about the top-level spec and more questions about conditions and boundaries.
Here are the ones I use on every offer:
- What reference site conditions are behind the rated power, power curve and annual energy production figures?
- Which control mode did the energy model assume—standard, noise-reduced, or cold-weather?
- Does the type certificate cover the exact rotor, tower, software and site class in this offer?
- What evidence will the OEM supply for grid code compliance at our actual point of interconnection?
- What is inside the wind turbine OEM scope: tower, blades, installation, commissioning, warranty, service, and performance guarantees?
- If something about this site falls outside the OEM’s standard assumptions, who owns the analysis?
That last question is often where trust is built. An OEM that says ’this isn’t the right machine for your site’ is more credible than the one that stretches a platform to fit every wind condition.
I won’t tell you that Siemens Gamesa is right for every project, because no serious supplier is. But the Siemens Gamesa wind turbine platform documentation, from SG 3.4-132 onshore to SG 14-236 DD offshore, improves when it is read against those questions. That is true of any wind turbine OEM. The spec sheet is only as good as the conditions behind it.