The Solar Resource

Two words sit at the base of everything, and they are worth getting exactly right because they are constantly muddled. Irradiance is the *power* of sunlight arriving on a surface at an instant - how intensely the sun is shining right now - measured in watts per square metre (W/m2). On a clear day with the sun high, irradiance on a surface facing it can reach roughly 1000 W/m2; that round figure is so central that it is the reference condition modules are rated against (you will meet it again as 'standard test conditions' in lesson 1.3). Irradiance rises and falls minute by minute as the sun climbs and sets and as clouds pass.

Insolation is the *energy* that accumulates over a period - irradiance added up across an hour, a day, a year - measured in watt-hours or kilowatt-hours per square metre (kWh/m2). If irradiance is the speed on the speedometer, insolation is the distance travelled. Daily insolation is what tells you how much a place can generate, and it is often expressed as peak sun hours: the number of hours of full 1000 W/m2 sun that would deliver the same day's energy. A location with, say, 5 kWh/m2 in a day has about 5 peak sun hours - a compact, useful way to compare sites. India across much of the country sits in a strong band on this measure.

Why does the distinction matter to a designer? Because a surface can see high peak irradiance yet poor daily insolation (a wall that catches intense but brief low-angle sun), or steady moderate irradiance with excellent insolation (a well-oriented roof in clear skies). It is the *accumulated* energy - the insolation on that particular surface, in that particular place - that drives yield, and it is what verified resource data and an engineer's assessment will quantify. Any figure here is illustrative; the point is the mental model: power at an instant (irradiance), energy over time (insolation), and the daily total (peak sun hours) as the resource number a designer learns to reach for first.

Picture a bright day and you imagine a beam straight from the sun. But the light landing on any surface actually arrives in two forms, and both count. Direct (beam) radiation travels in a straight line from the sun's disc; it is the crisp, shadow-casting light that dominates on clear days and that responds strongly to how a surface is angled toward the sun. Diffuse radiation is sunlight that has been scattered by the atmosphere - by air molecules, haze, dust and cloud - so it arrives from the whole dome of the sky rather than one direction; it is the soft, shadowless light of an overcast day. Add a usually small third part reflected from the ground and surroundings, and their sum on a surface is the global irradiance that actually does the work.

The split between direct and diffuse is not a footnote; it shapes design. On a clear desert-like day, direct beam can be the large majority of the total, so orientation and tilt matter enormously - point the surface at the sun and you win. Under a humid, hazy or cloudy sky (a monsoon afternoon, a polluted city), diffuse can become a large share, sometimes most, of the resource. Diffuse light is far less sensitive to orientation - it comes from everywhere - so a surface facing 'the wrong way' still collects a meaningful amount of it. This is quietly important for facades: a wall that captures little direct beam may still harvest useful diffuse light, which is one reason facade PV, though generally weaker than a good roof, is not worthless.

The practical lesson is humility about clear-sky intuition. Real skies over a real building are a mix, changing hour to hour and season to season, and the diffuse fraction can be surprisingly high in Indian conditions of haze, dust and monsoon cloud. Good resource data captures both components; good design does not assume every surface lives under a cloudless sky. When we come to orientation and shading (lesson 1.4), remember this: direct light rewards aiming, diffuse light forgives it - and every real surface lives on some blend of the two.

The resource is a moving target, and a designer has to hold four kinds of variation in mind at once. Location sets the baseline: latitude governs how high the sun climbs and how long it stays up, while regional climate - clear desert air versus persistent cloud or coastal haze - governs how much of the potential actually arrives. Two cities at the same latitude can have quite different resources because one is dry and clear and the other humid and overcast. Season swings the resource through the year: the sun rides higher and the days run longer in summer, lower and shorter in winter, so a surface's monthly insolation can vary a great deal - and, importantly, the season interacts with tilt and orientation, so the 'best' angle for summer is not the best for winter.

Time of day draws the familiar arc: little at dawn, a peak near solar noon when the sun is highest and its light passes through the least atmosphere, then a decline to dusk. This daily curve is why a PV surface produces nothing at night and most around midday, and why matching that production to when a building actually uses power becomes a central theme later in the course. Weather overlays all of it with short-term chaos: a passing cloud can drop irradiance by most of its value in seconds, and a cloudy week can slash a month's expected energy. Averages over a year are fairly predictable; any single hour is not.

For the designer the message is not to compute these swings - verified datasets and simulation tools do that, and an engineer signs off on yield - but to *reason* with them. A surface's real annual harvest is the accumulation of all these variations on that specific surface in that specific place, which is why a single headline 'India gets lots of sun' number never settles a project. It tells you the region is promising; it does not tell you what this roof, this facade, at this tilt, in this microclimate, behind those trees, will make. Reading the resource means holding the big regional picture and the brutal local specifics in the same thought.

Because the resource varies so much by place, it is captured in solar resource maps: datasets, usually shown as coloured maps, of long-term average irradiation across a region - often as annual or daily insolation (kWh/m2) for a horizontal surface or an optimally tilted one. Built from decades of satellite observation and ground measurement, these maps (and the point-by-point databases behind them) are the professional starting point for judging a site's potential: you find the location, read its long-term average, and you have an honest first estimate of the resource before a single panel is chosen. They are a design tool, not a guarantee - they give long-run averages, not the yield of a specific shaded, tilted, real-world surface - but they anchor the conversation in data rather than optimism.

On such maps, India holds a strong hand. Most of the country receives abundant solar radiation for most of the year, with the arid north-west and the Deccan among the sunniest zones and even the cloudier, wetter regions still holding a respectable resource by world standards. This abundance is the physical foundation of India's large and fast-growing solar programme and its push on rooftop solar - the raw material is genuinely plentiful. For a designer it means the *regional* answer to 'is there enough sun?' is usually yes, which is exactly why solar architecture is so relevant here.

But the map's promise must be handled with the same honesty the whole course insists on. A strong regional resource does not survive a badly shaded site, a poorly oriented facade, heavy dust and soiling (a real Indian issue that cuts output between cleanings), or the efficiency penalty of high heat on the modules themselves (which lesson 1.3 and Module 6 take seriously). The map tells you the sun is there; it does not tell you your surface will catch it. So use resource maps and verified site data to establish potential, then defer the binding yield assessment - the number that actually goes in a proposal - to qualified engineers using proper tools and site-specific data. The resource is the opportunity; capturing it well, honestly, on a real building is the craft this course builds.