Getting Started with Solar Design

The first move needs nothing but your eyes and a rough sense of direction. Stand on the site (or work from the plan and a compass) and read the envelope as a set of surfaces that face the sky. Three things govern how well each surface could generate, and you can judge all three qualitatively: orientation (which way it faces), tilt (its angle), and shading (what blocks the sun). In the northern hemisphere the sun spends the day in the southern sky, so south-facing surfaces collect most, east and west collect a useful but time-shifted amount, and north collects least; roofs at a sensible pitch are usually the prize, and large facades come into play on taller buildings. Flip the compass for the southern hemisphere.

The quiet killer is shading, and it is worth training your eye on because a little shade does disproportionate damage. Look for what will throw shadow across your best surfaces across the day and across the year: neighbouring buildings, especially taller ones to the sun-facing side; trees, remembering they grow and that deciduous ones change with the season; and the building shading itself - parapets, plant, an overhanging wing, a stair core. A surface that looks perfect at noon in June may be in shadow for hours in December or from a tower next door. Reading shade is a design skill you already half-have from thinking about daylight and overlooking; here you point it at generation.

The output of this first move is not a number - it is a ranked mental map: *these one or two surfaces are the real prizes, these are marginal, these are hopeless*. That ranking is genuinely valuable and entirely within your competence. It tells you where, if anywhere, solar wants to live on this building, and it does so before you have spent a rupee or called anyone. Do this honestly and you have already done the most important thing the next steps only refine: you have seen the envelope as surfaces that generate, and you have found the ones worth taking further.

Once you know which surfaces are worth it, the next move is to get an order-of-magnitude feel for how much they might generate - deliberately rough, explicitly not a specification. The point is to answer 'are we talking about a meaningful fraction of this building's energy, or a token gesture?' The reasoning chain is simple: usable area, times a rough power density, times a rough capacity factor for your climate, gives a ballpark annual generation you can compare against the building's likely demand.

The mechanics are approachable. Estimate the usable area of a promising surface (not the whole surface - subtract shaded parts, edges, obstructions). Apply a rough rule of thumb for power per area - modern modules produce on the order of a couple of hundred watts of rated capacity per square metre, and integrated or coloured products produce less, so you deliberately use a conservative figure. That gives a rated capacity (in kilowatts-peak, kWp). Then apply a rough capacity factor for the region - a fraction that folds together how sunny the site is and real-world losses - to turn rated capacity into an estimate of energy per year. Sunny locations like much of India sit at a healthier fraction than cloudy northern ones; you are looking for the right order of magnitude, not a decimal.

Two disciplines make this honest rather than dangerous. First, use conservative numbers and round hard - the goal is scale, so a figure good to a factor of roughly two is doing its job; false precision here is worse than useless. Second, label every figure as illustrative and site-dependent, because it is: real yield depends brutally on orientation, tilt, shading, dirt, heat and system quality, and the true numbers will come from an engineer's modelling and the manufacturer's data. Used this way, the back-of-envelope is a fantastic design tool - it tells you quickly whether solar is worth pursuing seriously on this project and roughly what part of the building's needs it could touch - without ever pretending to be the binding calculation it is not.

You do not have to trust your eye and your arithmetic alone - there is a rich layer of free, public tools that lets a designer sanity-check a site quickly. Open solar-resource and irradiance maps show, for any location, roughly how much solar energy arrives per square metre per year - the raw resource that sets the ceiling. Free online solar calculators and estimators let you enter a location, a rough system size and an orientation and get a first-pass generation estimate that you can compare against your back-of-envelope. Satellite and street imagery lets you study roofs, surrounding heights and likely shading before you ever visit. None of these is a design authority, but together they turn intuition into something you can defend and iterate.

Use them to *check*, not to *decide*. If your eye said the south roof was the prize and the irradiance map plus a free calculator agree it could cover a serious fraction of the load, your concept is on solid ground; if they sharply disagree with your intuition, that is a signal to look again at shading or orientation you may have misjudged. This triangulation - eye, arithmetic, free tool - is exactly the kind of fast, low-cost reasoning that belongs at concept stage, and it keeps you honest without slowing you down.

The payoff move is a concept study: a simple drawing or model that shows PV living on your chosen surfaces *as architecture*. This is where solar stops being a spreadsheet idea and becomes design. Show the generating surfaces, the module rhythm and colour, how the PV meets the other materials and turns corners, how a glazed unit sits in the facade. Test the look, not the wiring. A good concept study does two jobs at once: it lets you and the client see and decide whether the integration is beautiful and coherent, and it gives the PV engineer you bring in next a clear, buildable intent to engineer toward rather than a blank brief. It is the natural bridge from your qualitative first moves to the specialist's binding work.

The final skill of getting started is knowing where *started* ends - the clean handover point at which qualitative design must give way to binding engineering. Everything so far - reading the site, the back-of-envelope, the free-tool checks, the concept study - is legitimately the designer's, because none of it is a binding result; it is scale, direction and architectural intent. The moment you need a real answer that someone will rely on, the work changes hands.

Bring in a qualified PV (and, as needed, structural) engineer when the project moves from *whether and roughly how* to *exactly what and is it safe*. Concretely: when you need a real yield prediction rather than a ballpark; when the array must be sized, strung and matched to inverters; when anyone needs to know whether the envelope and its fixings can carry the loads; when electrical and fire safety must be assured; when grid interconnection, metering and export have to be arranged with the utility; and when a cost, payback or performance figure is going to be put in front of a client as something to count on. Each of these is a binding result, and each defers to the specialist, the manufacturer's verified data, the utility/DISCOM and the codes - never to the designer's estimate.

The best time to make that handover is *earlier than feels necessary*, because the engineer's input is far more valuable shaping a still-fluid concept than validating a fixed one. Bring them a clear concept study and your honest read of the site, and they can tell you whether your ambition is realistic, catch a structural or electrical problem while it is still cheap to fix, and refine the design with you. Get the sequence right - designer opens with qualitative moves, engineer closes with binding results, and they overlap early - and getting started with solar design stops being intimidating. It becomes what it should be: a natural extension of the design process, begun by the designer, completed with the specialists, honest at every step about which is which.