What an installed system is
An installed system in Powerlily represents a commissioned solar installation reporting through its manufacturer’s monitoring platform. It is different from a quote or sales project. The system record is the operational view of what was installed and how it is performing over time.
Powerlily supports installed-system monitoring from Enphase, SolarEdge, and APsystems. Provider data is normalized into one fleet workspace so the team can review different brands without maintaining separate operational lists.
What Powerlily can track
Available data depends on the provider and the equipment installed at the site. A system record can include:
- System name, address, location, and installation date
- Manufacturer and provider system identifier
- DC and AC capacity
- Provider-reported status and health
- Daily, annual, and lifetime production
- Consumption where compatible metering is available
- Equipment reported by the monitoring provider
- Recent sync results and open monitoring incidents
- Associated customers, projects, documents, and collections
Connect a monitoring provider
Monitoring connections are configured at the company level by a user with permission to manage systems.
- Open company settings.
- Select System monitoring.
- Choose Enphase, SolarEdge, or APsystems.
- Enter or authorize the credentials required by that provider.
- Save the connection and confirm that Powerlily can list available systems.
Use company-controlled provider credentials. If the provider changes its authentication requirements, reconnect the integration before the older credential stops working.
Import installed systems
After connecting a provider, browse the systems available through that monitoring account and select the installations you want to import. Powerlily can import multiple systems and pull their initial production, status, equipment, and site information into company-owned records.
Review the imported address, location, manufacturer, capacity, installation date, and customer association. Provider records are not always complete, so correct missing project context before relying on fleet reporting or public display.
Use the fleet workspace
Open Systems to access Fleet Management. The workspace summarizes the number of systems, total energy generated, and the time of the most recent successful sync.
Use the Operations & Maintenance view to search by address, location, or system ID. You can filter by health status and manufacturer, sort the list, and switch between grid and list views.
System statuses are normalized into practical categories such as Healthy, Needs Attention, Critical, Inactive, and Unknown. The underlying provider status remains available on the individual system.
Organize systems with collections
Collections let you group systems in ways that match your operating model. Examples include service regions, maintenance programs, commercial portfolios, acquisition cohorts, or equipment types.
Use collections for ongoing organization rather than changing the customer or provider identity of the system. A system can remain tied to its real owner and monitoring source while also belonging to an operational group.
Keep monitoring data current
Enable the company’s scheduled update so Powerlily refreshes connected systems automatically. The refresh updates available production, status, and equipment information from each provider. Without an automatic or manual refresh, the system continues to show data from its last successful sync.
The fleet header shows the last successful sync. Individual system records can also show recent synchronization activity to users who can manage the system.
Refresh systems manually
Use a manual refresh when you have corrected a provider connection, commissioned new equipment, or need current data before investigating an issue. Systems can be selected in bulk and refreshed from the fleet workspace.
A refresh requests current data from the provider. It does not guarantee that the manufacturer has received a new reading from the site. Always compare the provider-reported timestamp and health information when diagnosing stale data.
Review performance and impact
Open a system to review its production history and available performance details. Powerlily can show lifetime energy, annual production, specific yield, uptime, recent output, and daily values when enough source data is available.
Consumption appears only where the installed metering and provider integration supply it. Do not interpret missing consumption as zero consumption.
Use the Data & Insights view for fleet-level analysis and the individual system for site-specific investigation.
Understand the fleet health queue
The Operations & Maintenance workspace includes a health queue for active and resolved incidents. Powerlily can create warning or critical incidents for:
- Provider health: the monitoring provider reports a system or equipment problem.
- Sync failure: Powerlily cannot complete a provider data refresh.
- Zero production: expected production data remains at zero under the configured detection rules.
- Stale data: the provider has not supplied sufficiently recent monitoring data.
An incident is a signal to investigate. It is not, by itself, proof of a hardware failure.
Triage an incident
- Open Systems and select Operations & Maintenance.
- Expand the Fleet health queue.
- Filter by active or resolved status, severity, issue type, or owner.
- Open the system and review the provider status, production history, sync information, and related project context.
- Assign the incident to the person responsible for follow-up.
- Acknowledge it when someone has reviewed and taken ownership of the issue.
- Resolve it only after the issue has been corrected or the alert has been conclusively addressed.
Acknowledge marks an incident as seen and assigns it if necessary. It remains in the active queue. Resolve removes it from the active queue and places it in resolved history.
Move from monitoring to service work
The system can remain connected to its customer, original project, equipment, documents, tasks, messages, and history. Use that context before dispatching service:
- Confirm the customer and site address.
- Review the installed equipment and commissioning records.
- Check recent production and provider health.
- Review prior service notes, documents, and conversations.
- Create a task for diagnosis or customer contact.
- Create a scheduled visit when field attendance is required.
- Record the outcome and close the incident when appropriate.
This keeps the monitoring alert and the service response connected to the same installed asset.
Automate incident follow-up
Monitoring incidents can trigger automations when they open or resolve. An automation can notify a responsible person, create work, or coordinate another approved action in your company’s process.
Use automation to improve response consistency, but keep an accountable owner on the incident. Automated notification does not confirm that someone investigated the site.
Associate the system with its customer
Link the installed system to the correct customer so it appears in their client portal. A private system is available to authorized staff and associated customers, without exposing it to other customers.
Review the association after importing because a provider’s customer record and the Powerlily client record may not match automatically.
Control public visibility
Systems are private until you choose to make them public. A public system can appear on the company’s public systems page and map, contributing to portfolio totals such as system count, installed capacity, panels, and energy produced.
You can optionally show a referral link for an eligible public system. Before publishing, review the location, customer information, imagery, production data, and company privacy policy. Only expose information your company has permission to display.
The fleet workspace supports bulk actions for making selected systems public or private.
Use the system page with customers
Customers associated with a system can review authorized production and consumption information through the client experience. Staff can use the same system context to discuss performance, answer questions, and share relevant documents.
Provider availability and meter configuration affect what the customer sees. Explain missing or delayed data accurately rather than presenting every gap as lost production.
Troubleshooting
No systems appear for import
Confirm that the provider connection belongs to the correct installer account and has permission to list systems. Reauthorize the connection if the credential has expired or the provider has changed its authentication method.
A system has not updated
Check the fleet’s last successful sync, the system’s recent sync activity, and the provider portal. Try a manual refresh. A provider outage, expired credential, site communications problem, or delayed provider reading can each produce different symptoms.
Production is visible but consumption is missing
Consumption requires compatible metering and provider data. Confirm that a consumption meter is installed, configured, and reporting in the manufacturer’s platform.
A healthy site has an open incident
Review the incident kind, detection time, current provider status, and recent output. The alert may reflect an earlier condition, a provider delay, or a synchronization problem. Resolve it only after documenting why the system is considered healthy.
A customer cannot see their system
Confirm that the customer has an active portal account, is associated with the correct system, and has access through the correct company and branch context.
The system should not be public
Change it to Private from the system or fleet workspace. Review any public-map settings and confirm that no inappropriate customer information remains visible.
Monitoring checklist
- Provider connections are current and controlled by the company.
- Imported systems have accurate addresses, capacities, dates, and customer associations.
- Scheduled refresh is enabled where appropriate.
- The last successful sync is recent.
- Active incidents have an owner and documented follow-up.
- Resolved incidents are closed only after investigation.
- Customer portal visibility is correct.
- Public systems have been reviewed for privacy and accuracy.
Related guides
- The Client Portal
- Tasks, Events, Notes, Files, and Project History
- Scheduling Crews and Managing Installations
- Using Lilypad for Field Execution
- Automating Your Workflow: Triggers, Steps, and Conditions
- Conversations, SMS, and Team Collaboration
