Skip to main content

Solar Energy Plan: M2 Deliverables for Submission

General Overview of the items required to be submitted to M2 Activation Stage with references to detailed guides

Updated over 3 weeks ago

Overview

The Activation (M2) Milestone is the final stage of QC review before a project is certified as meeting all LightReach requirements. All deliverables must be submitted before this milestone can be approved — no exceptions.

The items listed below are required with every M2 submission. Any items flagged as Conditional Approval (No Action Needed for Install) during earlier milestones are also required for M2 approval.

​
​

M1 Conditional Approval Information

No Action Needed For Install Flags carried over from the installation milestone are ALL required to be actioned for Activation (M2) Milestone Submissions.

Item:

What we’re checking for:

DS1

M1 Items Not Provided

  • Item/work completed with clear evidence of necessary issues corrected

  • See KB Article for complete M1 Photo List if any were missed and requested for M2

DS2

Work Pending Due to Service Upgrade

  • Work matching planset provided (including as built planset)

  • Equipment all AVL compliant

All flags not properly addressed will be left as open and will require action from the install partner. Please ensure all items requested by PLR are actioned as requested to avoid packages being stalled for approval.

Monitoring & System Settings

Item:

What we’re checking for:

MSS1

Solar Energy Plan: Monitoring Portal Deliverables (M1)

  • Installation (M1) Milestone Deliverable

  • Required: Monitoring portal ID for the inverter (and battery, if applicable).

  • Ensure site access is shared to Palmetto as owner & CTs are configured.

Palmetto Lightreach has added the capability in the portal to confirm the monitoring access has been properly granted. This is easily selected next to the Monitoring ID box, please reference the access check example below.

Example of Portal Access Check Tool:

For an in-depth look at the information Palmetto Checks for at time of submission see below section - System Performance Checks

Permission to Operate

Item:

What we’re checking for:

PTO1

Permission to Operate

Documentation

  • PTO is double-checked at Activation for accuracy

  • Ensure PTO Date matches the Utility Granted date NOT the date of the communication.

Utility Bill

Item:

What we’re checking for:

UB1

Carried over from NTP Milestone

  • Cross referenced for accuracy and Market Specific Requirements

  • Ensure Utility here matches the Utility stated in the Energy Plan Contract and FinCo portal.

Market Specific Requirements (in applicable states)

Incentive deliverables are a significant point of friction in the Activation (M2) Milestone, please closely review the available documentation by state and market to ensure that all requirements are met.

Item:

What we’re checking for:

MSR1

M1 Incentives missing at Install

  • Mainly reserved for small details incorrect at Install, not applicable to all M1 incentives

MSR2

M2 Incentives

  • All necessary items for market incentives expected for Activation

Extended Warranty

Item:

What we’re checking for:

EW1

Solar Energy Plan: SolarEdge Extended Warranty

  • NOTE - SolarEdge Warranties not processed by EPC will be processed by Palmetto

  • Extended warranty purchased for inverter(s) without standard 25 year warranty.

  • Receipt or confirmation specific to installed inverters

Site Improvement

Item:

What we’re checking for:

SI1

Remaining actions from EPC

  • If applicable, photos of the site improvements made such as tree removal or main panel upgrade.

System Performance Checks

Each installation submitted at the Activation (M2) Milestone will be audited for performance by Quality Control Technicians. The below items are mission critical for ensuring the Activation (M2) Milestone can be approved and should all be confirmed accurate before submission to review.

Monitoring Access

Item:

What we’re checking for:

MA1

Monitoring ID from OEM URL

  • Should be aligning with the assigned ID when monitoring was created

  • Battery systems using the same OEM for inverter and battery will still want the same ID for both the Inverter and Battery ID sections

  • AC Coupled Battery systems with 2 different OEMs will require 2 IDs, one for each OEM

MA2

Access to Monitoring Site

  • Correct level of access needing to be provided, such as maintainer for Enphase or View/Edit for SolarEdge

  • View Only access to sites with insufficient permissions will lead to rejection

  • See each OEM section for specific details: Enphase, SolarEdge, Tesla, QCells

Enphase
SolarEdge
Tesla
QCells

Monitoring Data

Item:

What we’re checking for:

MD1

Production Data

  • Looking for bell shaped production curve relative to local weather data expectation

    • Sufficient normalized production before weather events may be utilized

  • No production data reporting outside of daylight hours

  • Ensuring all strings and equipment reporting reflected to installation evidence

MD2

Consumption Data

  • Should report independent of production data

  • Ensuring all home loads are accounted to provide accurate home loads monitoring

  • Should not see negative home loads, as this may be indication of items not properly monitored

  • Required for all battery functionality

MD3

Battery Charge and Discharge Cycle

  • Battery cycling as expected to production of PV and home load usage

  • Battery charging with production and discharging to reserve limit when loads demand more than PV production

Please see the following for examples of correct and incorrect data for each OEM partner in our associated KB articles for OEM Walkthrough, which include our Troubleshooting Guide:

(OEM walkthrough slated Q2 2026)

Enphase
SolarEdge
Tesla
Qcells

Solar System Layout

Item:

What we’re checking for:

SL1

Module layout matching site

  • Array layout will need to match installed on site, including module orientation and module series

  • Azimuth may be requested to be accurate if required for array identification

  • If existing PV is on site, do NOT model any arrays not associated with new project

SL2

Micro Inverters/Optimizers assigned to modules

  • All modules should have matching micros or optis assigned to it

  • If micros/optis are not reporting, this is grounds for flagging

Examples for each necessary OEM platform here:

Enphase

SolarEdge

QCells

System Settings

Item:

What we’re checking for:

SS1

Export Settings

  • Ensuring the system is not limited in its production by any export setting

  • Settings that restrict PV production and could affect the production guarantee include:

    • Setting "Export to Grid" to "No Export" for Tesla systems.

    • Applying export limitations for Enphase or QCells systems.

    • Any other site setting not essential for the site that limits PV production.

SS2

PCS settings

  • May be required for interconnection and NEC compliance

  • Can also affect system performance if set incorrectly

  • Confirmation of the SolarEdge PCS requires commissioning photos, which must be shared as necessary.

SS3

Battery Settings

  • Backup Batteries will always require our standard 20% minimum Battery Reserve level and have ‘Storm Guard’ settings enabled.

  • See our associated KB article for Battery Settings and Operational Modes

System Operation

Item:

What we’re checking for:

SO1

All equipment active, operational, and communicating

  • Ensuring all operational devices are registered

  • No missing batteries, ATS, comms devices or CTs

SO2

No open monitoring alerts

  • Active alerts in monitoring are expected to be closed for M2 approval

  • Alerts can range from individual equipment flags to full site unable to communicate

    • Troubleshoot with OEM as necessary to close

SO3

Cell modem registered

  • Cell modem is a requirement for all PLR sites (See Warranty & Service Information article)

  • Should be registered to devices with associated cell plan, can be utilized as backup if Wi-Fi connection is more reliable and utilized

Did this answer your question?