How does this company make money?
AES Indiana and AES Ohio collect electricity rates that state public utility commissions have approved — customers pay those rates and there is no competing offer. Separately, AES earns payments under power purchase agreements with grid operators and utilities each time it delivers a megawatt-hour of electricity in countries like Chile and Vietnam. Fluence brings in money two ways: upfront from selling battery systems, and on an ongoing basis from long-term service contracts. On top of that, PJM and other grid operators pay AES capacity payments just for having generation available, whether or not it is actually used.
What makes this company hard to replace?
Residential and business customers in AES Indiana and AES Ohio territories have no legal option to pick a different electricity provider — state monopoly rules prohibit it. Industrial customers who signed long-term power purchase agreements face financial penalty payments if they try to exit early. Customers using Fluence battery installations are also tied in because those systems require specialized maintenance procedures that only AES service teams are equipped to carry out.
What limits this company?
Every country where AES wants to build or operate a power asset requires its own environmental permits and grid connection approvals, and those approvals cannot be done in parallel — each one moves through its own national process on its own timeline. Having more money or more engineers does not move those queues faster. The number of regulatory proceedings AES can actively push forward at once across 15 different national systems is the real ceiling on how fast it can grow.
What does this company depend on?
AES cannot operate without power purchase agreements with national grid operators in countries including Chile and Vietnam. Its US renewable projects require FERC transmission interconnection rights before any power can flow. Fluence systems depend on lithium-ion battery cells from Samsung SDI and other manufacturers. Peaking plants run on natural gas supply contracts. And the Indiana and Ohio distribution businesses operate under PJM grid operator dispatch protocols that govern how power moves across the regional network.
Who depends on this company?
The PJM regional grid operator faces frequency regulation gaps when Fluence battery systems go offline. Codelco and other Chilean mining companies face production interruptions when AES wind farms cut output. Residential customers in Indianapolis and Columbus lose power during outages on the AES Indiana and AES Ohio networks. Industrial customers in Vietnam experience manufacturing delays when AES coal plants reduce generation.
How does this company scale?
Once Fluence's battery storage software is built, copying it across new installations costs very little — the software does not need to be rewritten for each new site. What does not scale automatically is everything on the international side: each new country requires AES to build its own regulatory relationships, hire local permitting expertise, and set up currency hedging to manage revenues arriving in Chilean pesos, Vietnamese dong, and other local currencies. None of that can be centralized or handled from a single office.
What external forces can significantly affect this company?
When the US dollar strengthens, revenues that AES earns in Chilean pesos or Vietnamese dong are worth less when converted back — that directly squeezes returns from international assets. Paris Agreement timelines are forcing coal plant retirement schedules in Vietnam and other developing markets, which compresses how long those assets can operate. And lithium prices, which swing sharply when electric vehicle demand rises, affect how much Fluence battery systems cost to build and whether the economics hold up for customers.
Where is this company structurally vulnerable?
If AES and Siemens fall into a serious dispute over intellectual property rights or the direction of Fluence, and the joint venture breaks apart, the software stops being developable. AES would keep its grid operational knowledge but lose the Siemens automation layer. Siemens would keep its automation capability but lose AES's multi-grid dispatch data. The combined product that neither company could build alone would simply cease to exist.
CompanyGraph