Capacity Audit method
How a Capacity Audit turns constraints into a defensible decision
A GridNinja Capacity Audit maps claimed and modeled headroom to the evidence required for safe, usable, auditable capacity. It examines workload demand, topology, cooling, storage, bridge power, reserves, operating policy, telemetry quality, recovery, and SLA constraints. The deliverable separates accepted opportunities, repairable gaps, rejected assumptions, and no-proof conditions without promising a predetermined MW result.
Definition
What it is
The audit is a scoped discovery and evidence exercise that produces a capacity waterfall, constraint register, integration map, proof plan, and staged Shadow Mode recommendation.
Category boundary
What it is not
It is not an engineering stamp, safety certification, guaranteed savings study, or replacement for utility, equipment, commissioning, or facility sign-off.
Operational significance
Why operators care
Executives see where time-to-power and sellable-capacity assumptions depend on unresolved evidence. Technical teams receive a prioritized path to test those assumptions without beginning with control authority.
Mechanism
How the decision path works
- Step 01
Define scope, authority boundaries, protected outcomes, and data-handling limits.
- Step 02
Map capacity claims to topology, constraints, telemetry, policy, and recovery dependencies.
- Step 03
Classify each opportunity as presently acceptable, repairable, rejected, or no-proof.
- Step 04
Design a read-only Shadow Mode plan with acceptance tests, owners, and evidence outputs.
Textual diagram equivalent
Decision flow
Business capacity question → constraint and evidence inventory → proof-adjusted waterfall → gaps and refusal cases → Shadow Mode test plan → reviewed capacity report.
Synthetic audit output
Visibly scoped example
Synthetic illustrative scenario—not a customer or production result. A capacity waterfall identifies a promising tranche but leaves it no-proof until reserve policy, telemetry freshness, and recovery behavior can be validated.
Failure and no-proof cases
- The audit begins with a target MW and back-solves assumptions to support it.
- Data limitations are hidden in a single confidence score.
- Shadow Mode acceptance criteria or operational owners are undefined.
Limitations
- Findings depend on the agreed scope, evidence access, and topology accuracy.
- The audit cannot authorize control or override facility engineering and operating procedures.
- Commercial projections require separate assumptions and approval.
Evidence and sources
Inspect the basis, not just the answer
Local evidence objects show the GridNinja proof contract. Primary sources provide external standards and risk-management context; they do not validate GridNinja performance.
Related operator resources
Continue the proof path
- Quantify proof-adjusted capacity before you promise flexible MWRequest a Capacity Audit to quantify proof-adjusted safe MW, time-to-power, constraints, evidence gaps, and potential commercial value.
- Tell us where capacity is constrained.Talk with GridNinja about a Capacity Audit, Shadow Mode evaluation, virtual capacity pilot, or bridge-power partnership.
- Time-to-power improves when capacity claims become defensibleHow virtual capacity can complement interconnection and construction programs by making constrained infrastructure more usable and auditable.
Proof before autonomy
Test the evidence boundary against your capacity question
Start with a Capacity Audit or read-only Shadow Mode discussion. GridNinja does not require control authority to identify where a capacity claim remains unproven.