Aerial view of rows of photovoltaic modules at a large solar farm

EngiQuest / Solar PV and electrical storage

Solar PV and Battery: Full Engineering Workbench

Take a solar PV and battery project from a written design basis through yield, electrical design, storage, dispatch, economics and a defended scenario choice, and export a limitation-aware report.

  • Practitioner
  • 13 stages
  • 150 min
  • Solar PV and electrical storage
Development preview All EngiQuest journeys

Utility-scale PV is the same energy balance as a roof, at a different scale. Screening still starts with load, resource and limits.

Development preview. The calculations on this journey run on existing EngiMetric engines, but the journey text and scope have not completed independent engineering review. The route is excluded from search while it remains a preview.
Professional review required.The engines are implemented and unit-tested in this repository, but the journey copy, defaults and boundary still require review by a licensed engineer before publication. The route remains a noindex preview. Current verification state: Needs engineering review.

The engineering outcome

Solar PV and electrical storage

A thirteen-stage workbench for a grid-tied, hybrid or off-grid PV + BESS study. You own the load schedule, resource, array, cables, battery, dispatch policy and tariff assumptions; the workbench recomputes every downstream result and records failed checks instead of hiding them.

Who it is for
Engineers and technical generalists who need a traceable first-pass design and a defensible comparison of PV and storage options before detailed design, procurement or a vendor quotation.
Stages
13
Estimated time
150 min
Level
Practitioner

What you will be able to do

Learning objectives
  • Write a design basis that later stages cannot quietly contradict.
  • Build a load profile with a coincident peak and a critical-load subset for backup.
  • Turn monthly irradiation into PV yield with explicit temperature, soiling, wiring, availability and clipping losses.
  • Check string voltage, current, cable drop and breaker selection before specifying equipment.
  • Size a battery for autonomy and daily cycling, then test it against a rule-based dispatch.
  • Compare NPV, IRR, payback and LCOE across PV and BESS sizes without hiding infeasible options.
  • Export a report that states assumptions, failed checks and unmodelled effects.

Journey map

Ordered stages
  1. Define the site and the design basis Fix the site, configuration, backup requirement, design life and study boundary before any number is computed. Introduction / 10 min
  2. Build the load profile Convert a listed load schedule into daily and annual energy, a diversified peak and a critical-load subset for backup. Calculation / 12 min
  3. Build the solar resource and PV yield Transpose monthly horizontal irradiation onto the array plane and compute hourly-shaped PV yield with explicit loss terms. Calculation / 14 min
  4. Configure the array Turn a target DC size into a whole-module layout and check the DC/AC ratio against the inverter. Calculation / 10 min
  5. Check the electrical design Check the string voltage window, current, DC and AC voltage drop, breaker selection and bill of materials. Calculation / 16 min
  6. Size the battery storage Size nominal and usable battery energy for autonomy and daily cycling, and estimate service life and replacement. Calculation / 14 min
  7. Dispatch the system hour by hour Run a rule-based hourly dispatch and read self-consumption, self-sufficiency, curtailment and unserved energy. Calculation / 14 min
  8. Decide the system architecture Choose DC- or AC-coupled storage and a grid-tied, hybrid or off-grid boundary, and record why. Decision / 10 min
  9. Build the financial case Compute CAPEX, OPEX, NPV, IRR, payback and LCOE, and test the result against deterministic sensitivities. Calculation / 14 min
  10. Compare PV and storage options Re-run yield, dispatch and economics for several PV/BESS sizes and reject options that fail the stated boundary. Comparison / 12 min
  11. Plan implementation Turn the design into a pre-construction checklist that names the responsible evidence for each item. Implementation / 10 min
  12. Commission and verify Define the tests that prove the installed system matches the design, and the measurements that would falsify it. Commissioning / 10 min
  13. Assemble the reviewed report Write the engineering narrative, apply the rubric, download the report and state the professional review still required. Capstone / 14 min

Before you start

Prerequisites
  • Comfort with units: W, kW, kWh, A, V, %, and the difference between energy and power.
  • A site and a load set you are willing to describe. No measured data is required, but every result inherits the quality of your inputs.
  • Willingness to read the failed checks. A green summary does not mean the design is buildable.

Solar PV + BESS engineering report

Capstone

A traceable record of the design basis, load, yield, electrical checks, storage, dispatch, economics and scenario choice, exported from one computed project state.

Deliverable
A downloaded Markdown report plus JSON snapshot, a written narrative and a signed review statement.
Evidence model
Rubric against produced artifacts, not completion ticks

Requirements

  • State the site, configuration, backup target, design life and study boundary.
  • Report the load schedule, diversified peak and critical energy behind the battery size.
  • Report the resource assumptions, monthly yield, PR, capacity factor and clipping.
  • List every failed electrical or battery check and what it means for the design.
  • Report the dispatch balance, self-consumption, self-sufficiency, curtailment and unserved energy.
  • Report CAPEX, NPV, IRR, payback, LCOE and the sensitivity that matters most.
  • Compare at least three PV/BESS options and reject any that fail the stated boundary.
  • Name every assumption that changes a result and every effect the model does not cover.
  • End with an explicit statement that the report is a preview screen, not a stamped design.

Rubric

Each criterion is scored from evidence, and weights sum to 100.
Weight Criterion Evidence
10% The design basis is explicit, internally consistent and used by every stage. A site/configuration/backup statement that matches the computed dispatch and economics.
15% The load profile is traceable and the critical subset is defended. Load schedule, diversified peak, critical energy and the autonomy decision.
15% Yield is reported with resource, loss and clipping assumptions. Monthly table, PR, capacity factor, clipping and the resource source.
15% Electrical checks and failed constraints are reported, not hidden. String voltage, current, cable drop, breaker and BOM results with failures visible.
15% Storage sizing and dispatch are consistent with the load and boundary. Usable/reserve energy, power, service life, SOC trace and the energy-balance result.
15% The financial case states its boundary and does not overclaim. CAPEX, NPV, IRR, payback, LCOE and sensitivity with assumptions.
15% The report distinguishes a preview screen from a professional design conclusion. Limitations, open risks and a named professional review requirement.
What this is not. This report is a preview screening record. It is not a stamped design, a yield guarantee, a code compliance certificate, a bankability opinion or a permit submission.

The workbench is deliberately deterministic. Measured weather files, shading, protection coordination, detailed structural design and probabilistic uncertainty belong to a later, reviewed phase.

Journey limits and sources

Provenance

Limitations

  • Preview only: the content has not completed independent engineering review.
  • Deterministic screening: one representative day per month, no measured weather year or probabilistic uncertainty.
  • Electrical screen only: no protection coordination, earthing design, structural design or utility interconnection study.
  • Financial screen only: no financing, tax, grant, demand-charge or merchant-price modelling.
  • No code compliance, constructability, warranty or bankability conclusion.

Review status

  • Needs engineering review
  • Professional review is required before publication or use as a design basis.