A practical workflow begins with a clearly bounded emissions problem, then moves through deployment blockers before it gets seduced by TAM language. If a technology cannot survive financing, siting, or interconnection reality, the technical elegance alone will not rescue it.
The IEA and DOE material is useful because it frames market structure and infrastructure constraints. PyPSA and related open models are useful because they force system claims into something closer to math instead of leaving them in keynote space. The metrics that matter are cost against the incumbent, speed of deployment through real project cycles, and whether the climate impact survives realistic assumptions about adoption and utilization. If those numbers are hazy, the story is usually still upstream of reality.
A grounded version usually starts with three moves: Start by defining the emissions problem and the system boundary around it.; Track deployment blockers such as supply chain, permitting, and project finance.; and Compare company claims with market structure, customer behavior, and policy timing.. Save the version that survived real constraints, not the one that only sounded elegant in a planning doc.
Useful operating references:
- DOE Liftoff reports: liftoff.energy.gov/
Useful for understanding commercialization pathways and deployment bottlenecks in the US.
- PyPSA documentation: docs.pypsa.org/
An accessible place to start with open power-system analysis and optimization.
