BESS pre-investment evidence screening
Know what the BESS file actually supports before you commit more capital.
BiP Omega runs a written, evidence-first screening of a utility-scale battery storage project's technical file. We tell you what the documents support, what is missing, what conflicts, the questions to put to the developer, and a traceable screening verdict — signed by an analyst.
Document-based, non-licensed pre-investment screening. It is not an Independent Engineer engagement, a bankability certification, or an investment recommendation. It is the disciplined read of the file before those.
A BESS project can look investable and still have a file that doesn't hold up
The model looks fine. The OEM deck looks fine. The interconnection story sounds plausible. Each piece is reasonable on its own. The diligence failures usually live in what connects them:
Missing evidence: the decision-critical document simply isn't in the room
Wrong configuration: the file describes a different product than the one being priced
Contradictory documents: two sources disagree on a material number
Unresolved interfaces: who owns the OEM-to-EPC gap is undefined
Unsupported assumptions: a headline figure with no project-specific basis
Outdated studies: the interconnection or geotech work predates the current design
Warranty / dispatch mismatch: the revenue model cycles harder than the warranty allows
Test / site mismatch: the UL 9540A scope doesn't match the installed arrangement
None of this shows up in a narrative summary. It shows up when someone reads the documents against a fixed set of requirements, classifies every relied-upon value by how well it's evidenced, and writes down what the file does not answer. That read is what BiP Omega does — before the term sheet, before the diligence budget, before a full independent engineering scope is commissioned.
Two engagements
No menu. Both are document-based, non-licensed pre-investment screening. A narrower engagement means a narrower scope — not a lower evidence discipline.
BESS Red-Flag Screen
For the pursue / pass and "is this ready for a full independent engineering review" decision. It answers: what should worry me about this project before I spend more money on it?
- → Evidence inventory + project / configuration identity
- → Material gaps and document contradictions
- → Interconnection, safety / fire, warranty and performance red flags
- → Critical technical interfaces + specialist-escalation items
- → Prioritised RFI list
- → Screening verdict + traceable written report
7 priority domains. Working turnaround assumption for scoping: 5–10 business days from a complete data room, confirmed per engagement.
Full Pre-Investment BESS Screen
A deep document-based screening before acquisition, investment, major expenditure, an EPC / OEM commitment, or financing preparation. It answers: does the evidence support advancing this project?
- → Everything in the Red-Flag Screen, plus:
- → Complete review across all twelve BESS domains
- → Requirements → evidence mapping with a full traceability appendix
- → Configuration identity + declared-vs-evidenced mismatch analysis
- → Bounded screening calculations (decision support only, fully sourced)
- → Analyst sign-off + institutional report
All 12 domains. Working turnaround assumption for scoping: 10–20 business days from a complete data room, confirmed per engagement.
Every mandate is scoped individually and priced fixed — the price is set in the proposal, before you commit. No hourly billing. No scope creep. Specialist fees, if any, are pass-through and only incurred with your approval. Where this sits relative to a full independent engineering scope →
What you receive
Concrete deliverables, not "advanced analytics". Every conclusion traces: verdict → gate → requirement → evidence item → source document.
Evidence inventory
Every relied-upon value, with its source document and an explicit confidence classification — confirmed, single-source, asserted, or a named gap. A value the developer merely asserts is recorded as an assertion, not a fact.
Material gaps register
The decision-critical evidence that is not in the file — each with the requirement it relates to and what would close it.
Contradictions register
Documents that disagree on a material point. A material contradiction is only resolved by a named person with a supporting document — never silently.
Prioritised RFI list
The specific questions to put to the developer or seller, driven by real gaps, not filler.
Specialist-escalation register
Items that need a licensed or credentialed specialist we are not — flagged, not glossed over, and never given a fabricated conclusion.
Screening verdict
The worst applicable gate outcome under a non-compensatory requirements model — a strong domain never offsets a decision-critical gap. Signed by a human analyst.
Institutional report (PDF)
Produced by the same canonical pipeline as the public reference report, with a requirement-to-evidence traceability appendix.
Integrity manifest
A SHA-256 manifest binding the report to its evidence set and methodology versions (tamper-evidence — no cryptographic non-repudiation is claimed).
What we review
The Full Pre-Investment Screen covers all twelve BESS domains. The Red-Flag Screen covers the priority subset (D01, D02, D03, D05, D07, D08, D12). Each requirement is applied only where it is relevant to the declared configuration and jurisdiction; items marked not-applicable are recorded with the reason.
Project Definition / Configuration Baseline
MW / MWh / duration and their internal consistency, use case, project stage, and the declared configuration identity of every major subsystem that all other evidence must match
Battery & Integrator Architecture
cell / module / rack / enclosure architecture, chemistry substantiated by evidence, battery-level listing basis (UL 1973 / IEC 62619), integrator scope, thermal-management architecture
Interconnection, Grid Performance & Modelling
queue and study status, executed IA / LGIA, network upgrades and cost allocation, deliverability, grid-performance capability and its evidence, RMS / EMT models and their validation
Electrical, Protection, Transformer & Collection
single-line design, protection philosophy and coordination, grounding, short-circuit study basis, MV collection, main power transformer sizing, and consistency with the interconnection study
Safety, Fire, Thermal Runaway & AHJ
UL 9540 system certification and its configuration linkage, UL 9540A / IEC 62933-5-4 fire-test evidence, deflagration and suppression design, NFPA 855 / IFC basis at the adopted edition, AHJ status
Performance, Efficiency, Availability, Degradation & Augmentation
round-trip efficiency (AC / DC basis, auxiliaries and HVAC), usable energy vs nameplate, the degradation model and its assumptions, availability definition, and the augmentation plan against any capacity guarantee
Warranty, Guarantees, Operating Envelope & Remedies
throughput and capacity / EOL-floor warranties, availability and degradation guarantees, the operating envelope the warranty assumes, measurement method, exclusions, liquidated damages, and consistency with D06
Site, Civil, Structural & Environmental Exposure
geotechnical basis, flood and drainage, seismic and wind design (ASCE 7 at the adopted edition), wildfire exposure, foundations, heavy-haul access, and environmental permitting posture
EMS / BMS / PCS / SCADA / Controls, Communications & Cyber
BMS functional behaviour, plant-controller / EMS modes and their match to the grid requirements, PCS ride-through firmware, SCADA / ICCP interface, firmware and configuration management, remote-access governance, OT / cyber posture
EPC / Execution / Commissioning & Acceptance Testing
the EPC / OEM scope boundary, the construction and commissioning plan, the acceptance-test protocol (capacity, RTE, functional / grid tests), and whether the records demonstrate the guaranteed metrics
O&M, Reliability, Spares, Lifecycle & Decommissioning
O&M / LTSA scope and responsibilities, spares and augmentation logistics, monitoring and reliability approach, and the end-of-life and decommissioning plan and financial assurance
Technical Contract Interfaces, Schedule & Supply Chain
the interfaces between the technical contracts — scope gaps and overlaps, back-to-back obligations, milestone and COD dependencies, and technical supply-chain exposure against schedule
Domains marked non-compensatory can carry a critical gate: a strong position elsewhere never offsets a decision-critical gap there.
How an engagement works
Six steps, entirely on the record. A call is available if you need one; it is never required to complete an engagement.
1. Scope
You describe the project and the decision it supports. We agree the engagement type — Red-Flag or Full — and freeze the scope in a hashed, versioned scope baseline. The price is fixed in the proposal.
2. Secure intake
Your data room goes into an isolated, mandate-scoped workspace — not the public form on this site. Every file is hashed on receipt, checked at a security boundary, and recorded in a data-room index. Nothing is silently discarded; duplicates and superseded versions are tracked.
3. Evidence review
Every relied-upon value is classified by confidence and mapped to the technical requirement it supports. Material gaps and contradictions are registered as first-class items.
4. Written clarification
You receive a prioritised RFI register. Each item names the requirement, the question, and why it matters. Route items to whoever holds the source documents — multiple people can answer different items, on their own schedule.
5. Analyst review
A human analyst reviews the assessment against an attestation checklist and signs the screening. The verdict is a non-compensatory function of the requirement dispositions — no weighted average, no keyword score, no algorithm deciding the outcome.
6. Delivery
You receive the report, the supporting registers, a scope summary, and a SHA-256 integrity manifest. If the engagement was a Red-Flag Screen, we note whether a Full Pre-Investment Screen is warranted.
The public reference report
An illustrative BESS screening, produced by the same canonical pipeline a client report uses — not a hand-edited document. It is not a client engagement and implies no client, lender, site visit, or confidential data room. Read it to judge the analytical discipline before you engage.
Illustrative BESS — Pre-Investment Technical Screening
Built from an illustrative, anonymized evidence package — not a real project and not a real data room. Focus on the evidence register (how each value is graded), the material-gap analysis (what the record does not answer and why it matters), and the screening verdict (the rationale, not just the outcome).
- ✓ Evidence register with confidence grades
- ✓ Material-gap analysis per requirement
- ✓ Per-domain assurance positions
- ✓ Requirement-to-evidence traceability appendix
- ✓ Screening verdict with documented rationale
- ✓ Cryptographic integrity manifest
Written-first, by design
BiP Omega engagements are built around a documented asynchronous workflow. That is a discipline, not a limitation: evidence requests, assumptions, clarifications and conclusions all stay part of the engagement record.
Nothing rests on a call
No material assumption or clarification depends on someone's memory of a meeting. Every technical exchange has a written record you can point to later.
Multiple stakeholders, in parallel
RFIs can be routed internally and answered by different people on their own schedule. You forward the register; the right person answers the right item.
The independence is structural
BiP Omega does not design, supply, build, own, operate, or finance the assets it screens. It has no financial interest in the asset, the developer, the OEM, the EPC contractor, the financing outcome, or the transaction outcome. Fees are fixed and non-contingent. The conclusion reflects the evidence.
Who this is for
Acquirers and M&A teams, developers preparing a project for market or financing, and investors screening an opportunity before an investment committee — anyone deciding whether a BESS project is worth pursuing, pricing, or advancing, and whether it is ready for a full independent engineering review.
On validation — stated plainly
What is established is software and process verification: continuous integration, deterministic behaviour, adversarial and security testing, methodology traceability, and fail-closed controls. What is not yet established is prospective predictive performance — a real-mandate track record of screening positions resolved against real outcomes. No predictive-accuracy or historical-accuracy figure is claimed anywhere on this site.
Verification & validation status in full →Why there are no testimonials or client logos
For this type of confidential pre-investment diligence, project logos and testimonials are often inappropriate or unavailable — the work concerns a specific transaction and a specific project file. We therefore publish the methodology, the security posture, the honest validation status, and a full reference report produced by the same pipeline a client report uses, so the work can be judged directly.
What BiP Omega is — and is not
What it is
- ✓Document-based, non-licensed pre-investment technical and evidence screening
- ✓An analyst-led service supported by proprietary software and a formal methodology
- ✓A traceable written position on what the evidence supports, what is missing, and what conflicts
- ✓A screening verdict signed by a human analyst, with a requirement-to-evidence trace
- ✓Fixed scope, fixed price, set in the proposal before you commit
What it is not
- ×Not an Independent Engineer or Lender's Engineer, and not a Technical Advisor appointment for a financing
- ×Not a bankability certification, a credit opinion, or an insurance opinion
- ×Not a code-compliance, NFPA, UL, or IEEE conformity assessment, and not a licensed engineering opinion
- ×Not a site visit, a factory audit, a legal opinion, or an investment recommendation
- ×Not a prediction of project success — predictive performance has not been established through a completed prospective track record
The screening reflects only the evidence available as of an agreed cut-off date. Where the evidence does not support a conclusion, we record a gap rather than an assumption. It is not a substitute for a full independent engineering review, a site visit, or a licensed professional-engineer stamp.
Request a screening
Tell us about the project and the decision it supports. We reply in writing with a short scope summary — what we can screen, what it covers, and a fixed price — before anything is committed. No call required.
This form is for the initial inquiry only. Do not attach confidential project documents — a secure, mandate-isolated intake is set up once an engagement is agreed.