Integrating Self-Generated Power Into the Texas Grid

Amazon and Meta have said they are building gas plants to power their data centers because it's the fastest path to power. But this week, Google proved you can do it even faster with co-located renewables. And I found documents showing their strategy. On Wednesday, Google announced a new data center in Texas that will be powered by renewables built by AES Clean Energy. The press release was light on details, so I used Cleanview's platform to try to learn more about the project. In December AES filed a document showing that it plans to connect an 850 MW data center (Google’s) to its massive solar and wind project in West Texas. The project would use 600 MW of solar and 945 MW of wind power. Using both solar and wind enables near round-the-clock clean energy. And by connecting to the grid, Google gets the reliability it needs when solar and wind output drop. But the creative part is how this deal enables Google to skip Texas’ large load queue and get online in 18 months instead of 5+ years. Like the rest of the country, Texas has a massive backlog of data centers trying to connect to its power grid. At the end of 2025, the backlog was 225 GW—equivalent to 20 New York City’s of power demand. For data center developers like Google that backlog means waiting years to connect to the grid. These delays have led some companies like Meta to start building their own gas power plants as I wrote in our latest report. But Google found an alternative path—one that relies on a huge amount of onsite renewable energy. Thanks to a recent rule change, a data center in Texas can piggyback off a power project’s interconnection agreement if its co-located. And that’s what Google appears to be doing here with AES. The documents we found suggest Google is using AES’ grid connection, which took years to secure to get around the ERCOT large load queue. The wind phase of the project is expected to come online in August 2027. If Google had gone the traditional route, there’s no way they could have achieved that timeline. If they had tried to connect this data center in Virginia, they would have had to wait until the early 2030s. It’s worth noting that this timeline is similar to the one Amazon and Meta are achieving by using natural gas. They’ve argued that they have to use gas because waiting for renewables delivered through the grid would take too long. But with this project, Google is proving that it’s possible to build a 850 MW data center in 18 months powered almost entirely by co-located renewables. Developers and policymakers should take note. We wrote more about this project in a brief for Cleanview research subscribers. That brief includes a detailed project timeline, the equipment being used, and the broader policy and market context. Send me a note or visit our website if you’re interested in becoming a subscriber.

Utility-Scale Solar + BESS Integration Engineering Case Study: 15 MW PV + ~55 MWh BESS System Objective The integration is driven by temporal mismatch between solar generation and load demand. Midday excess generation leads to curtailment risk, while evening peak creates supply deficit and grid stress. The objective is to convert intermittent solar into a dispatchable, grid-supportive resource using energy storage. Load–Generation Assessment Installed PV capacity is 15 MW with effective midday output of 12–14 MW. Evening peak demand reaches 16–18 MW with a deficit window of approximately 4 hours. This sustained transition from surplus to deficit makes the system ideal for BESS-based energy shifting. Storage Sizing Methodology Peak deficit is approximately 10 MW for 4 hours, resulting in a net energy requirement of 40 MWh. Considering Depth of Discharge (80%) and round-trip efficiency (90%), the installed battery capacity is approximately 55 MWh. Power System Design (PCS & C-rate) The PCS is rated at 10 MW (bi-directional). C-rate is approximately 0.18C, which supports lower degradation, improved thermal performance, and longer lifecycle. Battery Technology & Architecture LFP (Lithium Iron Phosphate) is selected due to high thermal stability, long cycle life, and improved safety. The system operates around a 1500 V DC bus with modular configuration: cell → module → rack → container. Each container typically ranges from 2–5 MWh. Auxiliary systems include HVAC for thermal management, BMS for monitoring and protection, and integrated fire suppression. Electrical Integration Power flow follows: PV → inverter → AC bus → PCS → battery (charging mode), and battery → PCS → transformer → grid (discharging mode). Grid integration typically occurs at 33 kV or 66 kV levels. Protection systems include overcurrent, earth fault, differential protection, and anti-islanding schemes. SCADA integration is essential. Energy Management System (EMS) EMS defines operational intelligence. It manages time-based dispatch (charge during solar surplus, discharge during peak), peak shaving, frequency response, and forecast-based optimization. EMS integrates with SCADA and grid signals for real-time control. Performance Indicators Round-trip efficiency ranges from 88–92%. Key parameters include State of Health degradation, cycle count, availability, and response time. Expected system life is 8–12 years depending on usage and operating conditions. Techno-Economic Considerations Project viability depends on revenue stacking: energy arbitrage, demand charge reduction, curtailment avoidance, and ancillary services. Under-utilization significantly impacts financial performance. Design Constraints Key practical considerations include thermal derating in high ambient conditions, land requirements, grid code compliance, degradation warranties, and fire safety systems.