Situation
ESS sizing, electrical and control interfaces, RFP responses, supplier assumptions, and LCoE trade-offs arrived through different technical and commercial inputs.
Engineering case study
Utility-scale ESS review before EPC commitment.
At Vestas from 2018 to 2019, I supported energy-storage sizing, RFP inputs, technical due diligence, bidder comparison, and LCoE-informed value engineering for utility-scale hybrid-energy work.
Situation, task, action, result
A review system for assumptions that could otherwise hide in documents.
Task
Support the technical review so decision-makers could compare scope, risk, and bidder responses on a consistent basis.
Action
Organized requirements, interface ownership, assumptions, deviations, and open risks into a review sequence that multidisciplinary teams could follow.
Result
Technical gaps and ownership became easier to identify before procurement choices and execution commitments were fixed.
Review sequence
Four controls used to make bidder inputs comparable.
- Define the decision boundary.Separate fixed requirements, design assumptions, supplier choices, and unresolved owner inputs.
- Normalize technical responses.Review sizing, interfaces, operating cases, and exclusions against the same question set.
- Expose risk before scoring.Record deviations, dependencies, and missing evidence before a proposal is treated as technically complete.
- Carry decisions forward.Keep rationale and ownership visible for procurement, design development, and execution review.
Contribution, decision record and limits
My contribution described here is support for sizing, technical due diligence, bidder comparison and the organization of review inputs. It does not claim sole ownership of the multidisciplinary team's design, procurement or commercial decisions.
The qualitative outcome is a review trail that made technical gaps and ownership easier to inspect before commitment. The public material does not establish project savings, an improvement rate or a causal performance comparison.
An illustrative review entry
This newly written example explains the method; it is not a recovered Vestas record or a claim about an actual bidder.
- Decision:Can two storage proposals be compared on the same duty and interface boundary?
- Evidence needed:Record the duty profile, sizing assumptions, exclusions and interface owner beside each response.
- Review disposition:If an operating case or interface is unresolved, carry an explicit open item and owner into the comparison. Do not silently score the missing evidence as compliant.
- Next record:Link the clarified requirement and response revision before closing the item.
For a similar review, bring the decision boundary and one non-confidential example of a requirement or unresolved interface.
Evidence boundary
What this public case does and does not claim.
This page describes a transferable review method and the public role context. It does not publish client files, bidder data, project performance figures, or confidential commercial outcomes. No unsupported percentage improvement is claimed.