Site parameters
The plant-wide settings — perimeter road width, lightning arrester coverage, the capacity one control room serves, line corridors and area setbacks.
Site Parameters holds the settings that apply to the plant as a whole rather than to an individual table: how much ground is kept clear around the fence, whether lightning arresters are placed and how far apart, how much capacity one control room serves, and how wide a strip is cleared either side of a line, and how far tables stay from an area.
Three of them — the perimeter road width, the line corridor and the area setback — decide how much ground is available before a single table is placed. The rest decide what equipment is then placed on the ground that remains.
The card is the second one on the Site tab, between the Input Boundary File card and the two keep-clear cards, Structures & Shadow and Topography.


At a glance
| Field | Default | Range | What it does |
|---|---|---|---|
| Perimeter road width | 6.0 m | 0.0–50.0 m | Shrinks the plant boundary inward by this distance. Nothing is placed in the band that is left. |
| Place Lightning Arresters | off | — | When on, arresters are placed on a coverage grid and the tables under each mast's pile and shadow are cleared. |
| LA protection radius | 100.0 m | 10.0–500.0 m | The circle one arrester is taken to protect. The grid they sit on is 1.4 times this. Enabled only when arresters are on. |
| ICR Block | 18.000 MWp | 0.1–500.0 MWp | The DC capacity one inverter control room serves. Sets how many control rooms each piece of land gets. |
| Line corridor (each side) | 15.0 m | 0.0–500.0 m | No tables within this distance of a line in the boundary file, so the cleared strip is twice this figure. |
| Area setback | 0.0 m | 0.0–100.0 m | No tables within this distance of an area in the boundary file. At 0 tables can go up to its edge. |
Perimeter road width
The plant boundary is shrunk inward by the perimeter road width to give the usable area — the ground the layout is allowed to occupy. Obstructions and terrain exclusions are then subtracted from it, and a table or tracker unit is placed only where it fits entirely inside what is left.
So this is not a road you design here. It is a setback, kept clear of modules around the whole plant, wide enough to take the internal ring road, the fence line and the working space a construction crew needs to get plant and cable drums around the perimeter. Widen it and every edge of the plant pulls inward at once; the capacity you lose is roughly the perimeter length multiplied by the extra width.
The band is computed once from the boundary and reused everywhere the plant is drawn, on screen and in the deliverables, so the road you see on the screen is the road that reaches the contractor.
Entering 0 leaves no band at all, and tables are placed right up to the boundary. That is worth doing only when the boundary you supplied already excludes the road.
DC string cables are kept off the perimeter road band. AC feeders, and the DC trunks of a central-inverter design, are held inside the plant boundary wherever a route exists; a run that cannot be kept inside is reported by design check E-07 rather than hidden. See Cable routing.
Place Lightning Arresters
Off by default. Lightning arresters (LA) are the masts that carry the plant's lightning protection over the array.
With the option off, no arresters are placed and the tables fill the whole usable area. Nothing is reserved for them, and the plant's capacity is the capacity of a fully packed field.
With the option on, arresters are placed on a square coverage grid once the tables are down, each mast moved to the nearest gap between rows or tracker columns, and every table or tracker unit touched by a mast's pile, or by its shadow swept over the Shadow Window through the year, is removed. The rules are the same for fixed tilt and trackers. The pile and the mast height are on the Structures & Shadow card.
Arresters only ever sit inside the usable area, so the grid never puts a mast in the perimeter road band, in a water body or on excluded ground.
Arresters cost capacity. On the sample site, at the defaults, 26 masts removed 89 of 1,589 tables on fixed tilt, and 21 masts removed 90 of 582 tracker units. The tick and the radius are both kept in the project file.
The placed count appears on the Lightning arresters row of the Summary view and on a Lightning arresters chip in the row of plant chips under the plot. The masts draw with the Plant layout layer; the Arrester coverage row in the Layers ▾ popover shows their protection circles, and Shadows (keep-clear) the ground they keep clear. Lightning arresters covers the grid, the coverage circles and the keep-clear in full.
LA protection radius
Enabled only when Place Lightning Arresters is ticked.
This is the radius of the circular area one arrester is taken to protect, measured from the mast. The square grid the arresters are placed on follows from it: its spacing is 1.4 times the radius, 140 m at the default. The farthest point of a grid square is then just inside one radius of a mast.
The grid alone can leave something at the edge of the array uncovered, so after the grid pass any table, ICR, MCR or USS whose centre lies beyond the radius from every placed arrester gets an extra arrester in the nearest gap.
The radius is the main lever on the arrester count, and it is a strong one: doubling it doubles the grid spacing in both directions, so roughly a quarter as many masts are placed. Halving it does the reverse. That change in count feeds straight through to lost tables, because each mast clears its own pile and shadow.
Raising the radius does not make the protection cheaper — it asserts that one mast protects further. The value has to be justified for your mast height, your array geometry and the local lightning density before you take the reduced count into a design.
ICR Block
An inverter control room (ICR) is the building a block of the array is collected into — in a central-inverter design it also houses the central inverters. ICR Block is the DC capacity, in MWp, that one such room serves. The field shows three decimals — 18.000 MWp as shipped — because the AC-capacity study can write a block capacity into it to the kilowatt.
The count follows from it, for each separate piece of land. Tables linked by gaps of no more than 300 m are one piece; internal roads, corridors and setbacks never split one. Each piece gets its capacity divided by the block size, rounded up to the next whole room, with a half table counted at its share of a full table's modules, and the plant's count is the sum over its pieces:
- On a site in one piece, that is the plant's DC capacity divided by the block size, rounded up. A plant whose capacity exceeds a multiple of the block size by any margin at all gets another room.
- On a site in several distant pieces it can be more, because each piece — even a small one — gets a room of its own.
You cannot set the count directly: it follows the capacity actually placed and how the land splits.
Where the rooms go is not a grid. The tables of each piece are divided into exactly as many compact groups as the piece has rooms, each carrying close to the same capacity, and a control room is put at the centre of each group — so every group of tables surrounds its own room rather than being cabled across the site to a distant one. An extra room therefore makes every block a little smaller rather than adding one small block. Each room must fit entirely inside the usable area, and any table overlapping its footprint is removed. Because that removal reduces the plant's capacity, the required number of rooms is then re-checked against the reduced figure — and, on a fixed-tilt plant, once more after the building-shadow keep-clear, when it can only fall.
Choosing the block size is a cabling trade-off:
| Smaller block | Larger block |
|---|---|
| More control rooms, more buildings, more switchgear | Fewer buildings, less switchgear |
| Shorter AC or DC runs from the array to each room | Longer runs, heavier conductor, higher cable loss |
| More ground lost to building footprints | Less ground lost |
| More medium-voltage circuits back to the main control room | Fewer, larger circuits |
The footprint and height of the room itself are not set here — they are in the Structures & Shadow (keep-clear) card below. How the rooms are placed, and how to move one, is in Inverter control rooms; the tables wired to each room, and the summary and exports per block, are in ICR blocks.
Line corridor
A transmission line, canal or road crossing the site is drawn in the boundary file as a line, not as a polygon, because it has no width of its own. This field supplies the width: the setback is applied to each side of the line, so the total cleared strip is twice the value you enter. At the default of 15 m per side, a line clears a 30 m strip through the array.
A line drawn through the middle of a plot splits the array into two blocks with a clear corridor between them.
Higher-voltage lines need more room. The application's own guidance is to raise the setback accordingly, for example 30 m per side for a 400 kV line. For a road, enter half its width.
Once a boundary file is loaded, each line gets its own row under this field, with its name and length, so a nala and a transmission line can have different corridors. Changing the common field moves every row still at the old value; a row you edited keeps its own.
The corridor is subtracted from the usable area before any table is placed, so it costs capacity in the same way the perimeter road does — but unlike the road it also breaks the array up, which matters for cable routing and for cleaning robot runs.
How to draw a line feature is in Boundary file requirements.
Area setback
An area in the boundary file, such as a pond, a building or a temple, keeps tables off its own ground. The Area setback keeps them a further distance away, for a bund, a clearance from a nala drawn as an area, or a maintenance strip. At the default of 0 m, tables can go up to the area's edge.
Once a boundary file is loaded, each area gets its own row under this field, with its name and size, and the rows follow the common field in the same way.
Where to go next
How placement works
The order the usable area is built up and the tables are placed
Structures and shadow
Footprints and heights for the control rooms, substations and street lights
Topography
Keeping tables off ground that is too steep to build on
Every parameter and its default
The complete input reference
Spacing and tilt
Tilt from the site latitude, and row pitch shade-free across the Shadow Window on 21 December, unless you override them; plus what ground coverage ratio reports.
Structures and shadow
Footprints and heights for the control rooms, unit substations, arresters and street lights on the Site tab, and the shadow they clear tables out of.