14.4 Customer Expectations, Value Engineering, and Design Adaptation

Customer Expectations, Value Engineering, and Design Adaptation

Two tasks in the System Design domain bracket the technical work: reviewing customer expectations before the design is final, and adapting the system design when field conditions do not match the plans. Both are about decisions, documentation, and communication. A design that meets code but surprises the customer, or a field change that never reaches the as-built drawings, creates problems that show up later as disputes, failed inspections, or unsafe conditions for the next technician.

---

1. Reviewing Customer Expectations

Equipment Location

Agree early on where the inverter, disconnects, batteries, monitoring gateway, and conduit runs will go. Consider:

• Code requirements: working space in front of electrical equipment (NEC 110.26: generally 30 inches wide, 3 feet deep for systems up to 150 V to ground, and 6.5 feet high), readily accessible disconnects, rapid shutdown initiators outside one- and two-family dwellings, and ESS location limits (no sleeping rooms; capacity limits in garages and utility spaces).
• Utility requirements: some utilities require a visible-break ac disconnect within a set distance of the meter or a specific meter location.
• Environment: shade and ventilation for inverters (heat derates output), protection from vehicles, and sound from inverter fans near bedrooms.
• Access: future maintenance access to equipment and roof penetrations.

Aesthetic Concerns

Common requests include all-black modules, front skirts that hide racking, conduit routed through the attic instead of across the roof face, and equipment placed out of view from the street. Homeowner associations may also have rules, although many states limit how far an HOA may restrict solar. Note any aesthetic choice that costs energy or money (for example, using a less productive roof plane) and get the customer's agreement in writing.

Electric Load Assessment

• Existing grid-tied homes: Use 12 months of utility bills (or interval data) to find annual and seasonal energy use, and ask about future loads such as electric vehicles, heat pumps, or induction cooking.
• New construction: Estimate loads from the plans, appliance schedules, and energy models, because there are no bills yet.
• Stand-alone systems: Build a detailed load table (watts × hours per day = watt-hours per day) and size for the worst month, including surge loads such as well pumps.
• Multimode (backup) systems: Identify the critical loads to be backed up, their running and surge power, and the backup duration the customer expects.

Example: A home used 10,800 kWh last year, and the site averages 4.8 peak sun hours per day on the chosen roof plane. With an overall system derate of 0.80, the array needed to offset 100% of use is:

$P_{\text{array}} = \frac{10{,}800\text{ kWh}}{365 \times 4.8\text{ h} \times 0.80} = \frac{10{,}800}{1{,}401.6} \approx 7.7\text{ kW dc}$

Functionality and Performance Requirements

Clarify what the customer actually wants the system to do: offset a percentage of annual use, provide backup for a stated time, limit export to meet a utility rule, or report data to a monitoring platform. Base production estimates on recognized tools (such as PVWatts or other simulation software) with stated assumptions, and never promise more than the modeling supports.

Value Engineering

Value engineering means delivering the required function at the lowest life-cycle cost, not simply the lowest first cost. Examples:

• Using a string inverter instead of module-level electronics on an unshaded roof, if rapid shutdown can still be met (for example, with listed rapid shutdown devices or a listed PV hazard control system).
• Making a supply-side connection instead of upgrading a service panel, where the service conductors and equipment allow it.
• Using aluminum feeders for long runs, rail-less racking, or a different attachment that saves labor.

Value engineering never trades away code compliance, safety, or the performance the customer was promised.

---

2. Adapting the Design in the Field

Site Condition Assessment

Before and during construction, compare the site with the plan set. Common discrepancies include rafters of a different size or spacing than shown, hidden roof damage, a different service panel or busbar rating, new shading (a tree or a neighbor's addition), obstructions such as vents not shown on the layout, rock or refusal during pile driving, and underground utilities in the planned trench path.

Design Options and Contingency Plans

For each discrepancy, evaluate options and their effect on code compliance, performance, cost, and schedule:

• Structural: a different attachment spacing, sistering rafters, or an engineer's revised letter.
• Electrical: re-stringing within the inverter voltage window, moving the point of interconnection, derating the main breaker, or a supply-side connection.
• Layout: moving modules to keep fire pathways and setbacks.
• Civil: a different foundation type or trench route.

Good project plans identify likely contingencies in advance (for example, an alternate attachment if tile breaks are excessive).

Interpreting the Scope of Work and Gap Analysis

Read the contract scope and compare it, line by line, with the plans and the actual site. A gap analysis finds work that is needed but not included, such as reroofing under the array, trenching, a service upgrade, tree removal, or a utility-required disconnect. Resolve gaps before work starts so they become planned changes instead of surprises.

Change Orders

A change order is the written agreement that changes the contract scope, price, or schedule. A complete change order describes the change and its reason, states the cost and time impact, and is signed by the customer before the work is done. When the change affects permitted work, such as a different inverter, module, or attachment, the string configuration, or the point of interconnection, submit a plan revision to the AHJ and, if the inverter ac rating or interconnection changes, notify the utility before inspection or permission to operate. Equipment substitutions must still be listed for the application and match the approved design calculations.

Document Control

Keep one controlled, current plan set on site. Mark revisions with a revision number, date, and description, and cloud the changed areas. At closeout, deliver as-built drawings that show what was actually installed (string layout, conductor sizes, conduit routes, equipment locations, and device settings). Record drawings are the final, verified set kept by the owner and AHJ. The next technician relies on them to work safely.

Budget: Time and Money

Track labor hours and materials against the estimate. Field adaptations consume contingency; when a change exceeds the contingency or affects the schedule, it goes through the change order process rather than being absorbed silently.

---

3. Worked Example: Adapting a Residential Design

The approved plans show 2×6 rafters at 16 inches on center with attachments every 48 inches. In the attic, the crew finds 2×4 rafters at 24 inches on center over part of the roof.

1. Stop and assess: The structural letter no longer matches the framing, so work on that roof plane pauses.
2. Options: The engineer evaluates closer attachment spacing on that plane, sistering the rafters, or moving those modules to another plane.
3. Decision: The engineer issues a revised letter requiring attachments at every rafter (24 inches) and sistering three rafters.
4. Change order: The contractor documents the added labor and materials; the customer signs before the work proceeds.
5. Permit revision: The revised structural sheet goes to the AHJ for approval before the inspection.
6. As-builts: The final drawings show the revised attachment layout and the sistered rafters.

---

4. Summary Table