APNIC Pty Ltd.

11/17/2026 | Press release | Distributed by Public on 11/16/2026 17:24

Solar photovoltaics for Internet resilience (Part 2): Choosing suppliers and components

A pair of 12 kW inverters, with network and local monitoring showing panel output by string. Photo supplied by author.

This is Part 2 in a three-part series. Read Part 1 first.

After you've worked out what you need from a solar photovoltaic (PV) system and modelled a design that meets those requirements, the next challenge is turning that design into a real-world project. However, a good design alone does not guarantee a reliable installation. The quality of suppliers, components, software support, and installation planning can have as much impact on long-term reliability as the technical design itself.

In Part 1, we established how to determine energy requirements, select an appropriate system architecture, and model system performance. The next step is selecting vendors and equipment that can deliver the required performance over the long term.

For Internet infrastructure operators, a solar PV system is not just an energy project. It is part of the infrastructure that keeps networks and services available during grid outages, fuel shortages, and other disruptions. Decisions made during procurement can therefore affect operational resilience for years to come.

Step 3: Getting a quote and selecting a vendor

You're probably familiar with some of this already, but it's still a case of buyer beware. Not every vendor claim stands up to scrutiny, so knowing which questions to ask is important. What looks cheap initially can end up costing considerably more.

Software, support, and cybersecurity

A monitoring platform that depends entirely on a vendor cloud service may become unavailable during Internet outages or if the vendor discontinues the service. Understanding these dependencies is as important as understanding the hardware itself.

A solar PV system is a long-term investment, so don't focus only on the hardware. Consider who will maintain and support the software over the life of the system. For grid-connected systems, software support is particularly important because outages, configuration issues, and cybersecurity vulnerabilities can all affect system reliability.

Ask:

  • Who will support the software over the next 20 years?
  • How will security patches and updates be delivered?
  • Who requires remote access to the system?
  • What cybersecurity measures are in place?
  • What happens if the manufacturer ceases operation or support?

System design and grid integration

The vendor should be willing to work through the design with you rather than simply proposing a standard package. Understanding how the system behaves during normal operation and power outages is critical.

Ask:

  • Is the vendor willing to refine the design to meet your requirements?
  • How will grid connection, islanding, and de-islanding be implemented?
  • Does the vendor have experience with grid protection relays?
  • Who is responsible for obtaining grid-connection approval?
  • Are there limits on exporting excess power to the grid?
  • Can the system supply the required load continuously in island mode?

Components and technical architecture

Not all components work well together, and some manufacturers only support specific combinations of batteries and inverters. Can the system continue operating and be monitored locally if Internet connectivity is unavailable?

Ask:

  • Are all proposed components fully compatible?
  • Are the panels from a reputable manufacturer with a strong warranty?
  • Will batteries be charged directly from Direct Current (DC), or through Alternating Current (AC) conversion?
  • If multiple inverters are used, can all of them contribute to battery charging?
  • What monitoring interfaces and Application Programming Interfaces (APIs) are available?
  • Can the system continue operating and be monitored locally if Internet connectivity is unavailable?

Training, monitoring, and ongoing support

A system is easier to maintain and troubleshoot if you can monitor it effectively and have access to the information needed to operate it.

Ask:

  • What training will be provided?
  • Will you have local access to configuration settings?
  • What documentation will be supplied?
  • Will the vendor assist with optimization after commissioning?
  • Who provides hardware support, and what are the associated costs?

Installation quality

Even an excellent design can be undermined by poor workmanship. Pay close attention to installation standards and the contractor's track record.

Ask:

  • Does the installer have experience with similar systems?
  • Have wind loading and structural requirements been considered?
  • What health and safety procedures are in place?
  • Will installation methods avoid future roof leaks or maintenance issues?

Get vendor responses in writing and compare them carefully. A supplier's willingness to answer detailed questions is often a good indicator of the quality of support you'll receive once the system is operational.

Finally, plug the vendor-proposed components into your model and see whether the design stacks up.

Looking ahead

Once you have selected a supplier and finalized the system design, the focus shifts from planning to delivery. In Part 3, we'll look at installation, commissioning, and the practical skills needed to monitor and operate a solar PV system successfully over its lifetime.

Dr Ulrich Speidel is a senior lecturer in Computer Science at the University of Auckland with research interests in fundamental and applied problems in data communications, information theory, signal processing, information measurement and assessment integrity. His work on connectivity research and implementation has been supported by the APNIC Foundation.

The views expressed by the authors of this blog are their own and do not necessarily reflect the views of APNIC. Please note a Code of Conduct applies to this blog.

APNIC Pty Ltd. published this content on November 17, 2026, and is solely responsible for the information contained herein. Distributed via Public Technologies (PUBT), unedited and unaltered, on November 16, 2026 at 23:24 UTC. If you believe the information included in the content is inaccurate or outdated and requires editing or removal, please contact us at [email protected]