Mesa address audit: what should be resolved before equipment is ordered
Local review point 1
Mesa has a service-territory problem that should be treated as the first design constraint. The municipal electric area is concentrated around downtown and is small compared with the city as a whole. Most casual descriptions of “Mesa solar” skip that split. Do not. Ask the bidder to put the serving utility on the first page of the proposal and attach the basis for that determination. A street address, bill and service map inquiry are more useful than a neighborhood label. Until the provider is fixed, a savings calculation is not localized enough to evaluate.
Mesa documentation: eia · energysage · azcredit · statute · congress · pvgis · census · srpCompare · srpRoof · srpE27 · srpTou · srpRebates · srpRec · apsRcp · acc · ariseia · weather · faq · solar · fees · rates · territory · mesaGreen · climate.
Local review point 2
For an account in City of Mesa Electric territory, array size needs an annual-use conversation before equipment selection. The municipal program’s qualifying net-metering structure and its Self Generation Standby Rate threshold create a reason to compare expected production with actual annual consumption. This is not an argument against a larger system. It is an argument against adding panels before the modeled output has been tested against the policy that applies to the account. Ask for the prior twelve months of use, the proposed annual production and the calculation showing whether the threshold is approached.
Mesa documentation: eia · energysage · azcredit · statute · congress · pvgis · census · srpCompare · srpRoof · srpE27 · srpTou · srpRebates · srpRec · apsRcp · acc · ariseia · weather · faq · solar · fees · rates · territory · mesaGreen · climate.
Local review point 3
Mesa’s permit exemption can reduce administrative work, but it should not be turned into a blanket “no permit” claim. The city FAQ describes an exemption for a certified solar system under 10,000 square feet installed by a licensed Arizona contractor. It also identifies exceptions involving new meters or circuits and historic homes. The municipal utility material adds batteries and meter-panel upgrades to the items that can require Development Services permitting. A homeowner should ask which condition applies to this exact scope. The honest answer may be simple, but it needs to be address and equipment specific.
Mesa documentation: eia · energysage · azcredit · statute · congress · pvgis · census · srpCompare · srpRoof · srpE27 · srpTou · srpRebates · srpRec · apsRcp · acc · ariseia · weather · faq · solar · fees · rates · territory · mesaGreen · climate.
Local review point 4
The municipal utility review has its own calendar even where a construction permit is not the primary friction point. The cited Solar Program describes a design review phase, an installation review phase and interconnection subject to availability. A project schedule should name each of those gates, identify who submits the materials and show when an interconnection agreement becomes binding. That prevents a buyer from thinking the contractor’s installation date is the same as permission to energize. It is not. City approval, construction completion and utility operation are separate events with different owners.
Mesa documentation: eia · energysage · azcredit · statute · congress · pvgis · census · srpCompare · srpRoof · srpE27 · srpTou · srpRebates · srpRec · apsRcp · acc · ariseia · weather · faq · solar · fees · rates · territory · mesaGreen · climate.
Local review point 5
Mesa E1.1 is valuable as a ratebook reference because it gives a municipal customer an actual tariff structure instead of a generic Phoenix number. It includes a monthly system service charge and seasonal energy tiers. That still does not make it an automatic savings rate. A bill model should use the applicable tariff, consumption pattern and system behavior, then disclose the calculation. The statewide EIA value can be useful as a transparent initial calculator baseline, but it should disappear from a final municipal proposal once the actual account data is available.
Mesa documentation: eia · energysage · azcredit · statute · congress · pvgis · census · srpCompare · srpRoof · srpE27 · srpTou · srpRebates · srpRec · apsRcp · acc · ariseia · weather · faq · solar · fees · rates · territory · mesaGreen · climate.
Local review point 6
An SRP account needs a different kind of caution. The reviewed SRP plan pages publish 3.45 cents per kWh for export-rate plans, while SRP’s rooftop-solar page publishes 1.87 cents per kWh for the same plan family. SRP publishes conflicting figures. Both links belong in the project file. Do not average the numbers, silently select the higher one or call either the current settled value. Ask the installer to show the live ratebook and model self-consumption separately from exports. If the economics depend on a disputed export input, that is a decision finding.
Mesa documentation: eia · energysage · azcredit · statute · congress · pvgis · census · srpCompare · srpRoof · srpE27 · srpTou · srpRebates · srpRec · apsRcp · acc · ariseia · weather · faq · solar · fees · rates · territory · mesaGreen · climate.
Local review point 7
Mesa’s production model should be used with the territory split, not apart from it. The fixed PVGIS run gives a city-coordinate annual baseline and a month-by-month curve, but the economic consequence changes by provider. A municipal account may need its production compared with the annual-use threshold. An SRP account may need its exported share stress-tested at more than one provisional assumption. The same roof can produce the same electricity in both cases. The contract value of the marginal kilowatt-hour is what changes. Production and compensation are separate layers.
Mesa documentation: eia · energysage · azcredit · statute · congress · pvgis · census · srpCompare · srpRoof · srpE27 · srpTou · srpRebates · srpRec · apsRcp · acc · ariseia · weather · faq · solar · fees · rates · territory · mesaGreen · climate.
Local review point 8
The city’s small utility footprint has context worth keeping, without turning it into a sales promise. The cited business utility page reports more than 17,500 municipal customers, roughly 5.5 square miles of coverage, about one megawatt of customer-owned solar and a power supply with renewable content. Those facts explain why Mesa Electric has its own solar rules. They do not establish a return for any individual house. The homeowner still needs an address qualification, bill history, roof layout and program-specific interconnection review. Local adoption is context, not an economic guarantee.
Mesa documentation: eia · energysage · azcredit · statute · congress · pvgis · census · srpCompare · srpRoof · srpE27 · srpTou · srpRebates · srpRec · apsRcp · acc · ariseia · weather · faq · solar · fees · rates · territory · mesaGreen · climate.
Local review point 9
Mesa homeowners considering a battery should ask a different question from PV-only buyers. Is the battery intended to provide essential-load backup, change when energy is taken from the grid, participate in a utility program, or support a future electrification plan? The city material says a battery can change the permit path, so equipment choice should follow the operating objective. Draw the location, list the supported loads and clarify whether the electrical panel can accept the configuration. A battery described only as an add-on is likely to produce an incomplete scope and an incomplete price.
Mesa documentation: eia · energysage · azcredit · statute · congress · pvgis · census · srpCompare · srpRoof · srpE27 · srpTou · srpRebates · srpRec · apsRcp · acc · ariseia · weather · faq · solar · fees · rates · territory · mesaGreen · climate.
Local review point 10
The regional weather note needs honest labeling. The reviewed climate context is Phoenix metropolitan normal data, not a Mesa-specific weather-normal record. The production model itself uses Mesa coordinates. Keeping that distinction visible is not pedantry. It prevents regional heat and rainfall context from being misrepresented as a site or city measurement. A good production proposal will state its radiation model, orientation, tilt, loss assumption and the roof-specific deviations from those assumptions. That tells the buyer what is modeled instead of selling a weather adjective.
Mesa documentation: eia · energysage · azcredit · statute · congress · pvgis · census · srpCompare · srpRoof · srpE27 · srpTou · srpRebates · srpRec · apsRcp · acc · ariseia · weather · faq · solar · fees · rates · territory · mesaGreen · climate.
Local review point 11
Mesa’s final comparison should be divided into two folders. The municipal folder contains the City of Mesa Electric rate and solar-program path, annual-use test, utility review timeline and relevant permit exception. The SRP folder contains the named price plan, both conflicting export documents and the current ratebook evidence. Only one folder should apply to the address. If a bidder uses facts from both to create the most attractive forecast, the forecast is not a Mesa-specific model. It is a patchwork.
Mesa documentation: eia · energysage · azcredit · statute · congress · pvgis · census · srpCompare · srpRoof · srpE27 · srpTou · srpRebates · srpRec · apsRcp · acc · ariseia · weather · faq · solar · fees · rates · territory · mesaGreen · climate.
