01
Decision contract
One capacity question, facility boundary, historical window, agreed alternatives, and acceptance criteria for the report.
A bounded, paid assessment
Scope your next capacity decision.
Evaluate one capacity question using authorized historical inputs. Agree the facility boundary, workload profiles, conditions, and review criteria before analysis begins.
Scoping is a conversation. Work begins only under an agreed paid scope.
What you receive
A decision brief with a traceable basis.
The engagement defines one decision, a facility boundary, a historical window, agreed alternatives, reviewers, deliverables, and review rounds. Inputs and conclusions remain scoped to that agreement.
02
Readiness and constraint findings
An input inventory, assumptions, binding constraints, and evidence gaps that limit what can be concluded.
03
Bounded model comparison
Requested and revised workload profiles assessed against the agreed conditions. Unassessed alternatives remain separate.
04
Review package
A concise decision brief with the supporting model record, limitations, unresolved questions, and agreed review rounds.
Before modeling
Confirm readiness, permissions, and responsibilities.
The site or data owner must authorize the historical inputs and confirm the relevant operating context. A useful assessment depends on that evidence being available and interpretable.
01
Customer responsibilities
Name the decision owner and operational reviewer. Confirm permission to share inputs, the facility boundary, workload requirements, and applicable operating constraints.
02
Historical inputs
Agree the relevant load and cooling history, capacity commitments, topology, reserve policies, and workload profiles. Readiness is reviewed before modeling is scoped.
03
GridNinja responsibilities
Document assumptions and gaps, perform the agreed analysis, distinguish modeled findings from operating permission, and deliver the contracted review package.
Do not submit telemetry, facility diagrams, credentials, or commercially sensitive files through this website. Any operational-data exchange is agreed separately. Review data handling.
How it starts
Fit, readiness, then a paid scope.
Schedule and price depend on the question, evidence, and agreed work. No fixed delivery period or performance improvement is promised here.
01
Start a scoping inquiry
Describe the capacity decision and organization. This starts a conversation; it does not purchase an assessment.
02
Review fit and readiness
Agree who owns the decision, what evidence is available, what may be shared, and whether a bounded assessment can answer the question.
03
Agree the paid scope
Confirm deliverables, schedule, price, review rounds, data handling, exclusions, and acceptance criteria before work starts.
Decision value
A useful answer need not be a larger number.
Report acceptance, commercial usefulness, modeled eligibility, and operating authorization are separate decisions.
01
A conditional path
A requested or revised profile fits the modeled conditions. Commercial usefulness and operating permission still require separate decisions.
02
A useful negative result
The request does not fit the agreed conditions, or a modeled revision does not meet the stated service requirement. The constraint is explicit.
03
An evidence gap
The available information cannot support a conclusion. The report identifies what is missing and the next investigation required.
Boundaries and change control
The assessment does not grant equipment control, guarantee safe sellable MW, certify facility safety, or replace engineering and operator approval. Live connectivity, operational-file ingestion, investment recommendations, recurring services, and autonomous control require separate evaluation and agreement. New facilities, time windows, profiles, or review rounds are scope changes to agree before additional work.
Start the conversation
Which commitment are you evaluating?
Share your organization and contact details. A short description of the decision is helpful but optional. This inquiry does not buy an assessment or authorize operational work.
Related operator resources
Continue the proof path
- Tell us where capacity is constrained.Start a scoping conversation about a bounded capacity assessment, input readiness, deliverables, decision responsibilities, or a partner investigation.
- Agree the data boundary before sharing operational inputs.Understand inquiry handling, historical input permissions, separate operational-data exchange, and the responsibilities to agree before sharing site data.
- How a Capacity Audit turns constraints into a defensible decisionPublication of this GridNinja technical resource awaits named ownership, evidence review, and permission. Inspect the synthetic decision brief meanwhile.