Paul,
For Array footprint I mean the physical area for an non shaded ground mount array including modules, area lost to self-shading, and possibly maintenance area required per code or by racking specification. Factors to describe and determine footprint would include: locale sun path input; worst case solar azimuth and elevation inputs; module type input; module orientation input; module stacking input; modules in a row input; module row number input; fixed, single axis, dual axis, or azimuth axis tracking input. A next step might even be to include a database of commercial racking and tracking systems to help define the physical footprint. Also, I realize these costs are in BOS Direct Capital Cost but a commercial database with a little more transparency would be helpful.
Question while I am on a roll. It would be great to see the cost change when working in DC Subarrays "System Design". I believe one achieves improved IRR, NPV, and Payback results with more energy production without the cost of improved tracking. So, is there a reason why the two are not connected since I believe you have the $/Wdc capacity data for the various tracking systems. Maybe I am missing something.
Thanks for the discussion.
Andy