Search on this blog

Search on this blog

Lessons Learned From Commissioning a Hybrid Solar + BESS Site (Lonestar Solar and BESS)

Lonestar Solar and BESS

Hybrid sites are where “normal” solar commissioning collides with reality: multiple OEM ecosystems, layered networks, more control surfaces, more data, more stakeholders, and way more ways for a minor comms miss to become a schedule hit. 

Renewable Energy Integration Group (REIG) lives right in that blast radius—building data acquisition and communication infrastructure for utility-scale solar and battery storage projects so plant data lands reliably in end-user software platforms for O&M and performance/financial analysis.  

In REIG’s Lonestar Solar example, the scope wasn’t just “get SCADA talking.” The project combined 26 inverters and 26 BESS units, plus fiber cabling, weather sensors, surveillance systems, and centralized routing through a substation network rack, including network video recorders (NVRs) and camera feeds—a genuinely multi-layered integration.  

Below are the most transferable lessons for utility-scale renewables communication companies commissioning hybrid solar + storage sites—using Lonestar as the anchor. 

1) Treat hybrid commissioning as “system-of-systems,” not a device checklist 

On a hybrid site, your communications scope is usually the integration glue between solar plant controls, storage controls, substation networks, utility/ISO telemetry, and owner-facing analytics. Lonestar’s design centralized site data through a substation network rack, while also pulling in non-traditional “plant” subsystems like surveillance and NVRs.  

Lesson: Build your commissioning plan around interfaces first: 

  • PCS/BMS/EMS ↔ plant controller/SCADA 
  • Solar inverter networks ↔ SCADA/plant controller 
  • Weather/MET ↔ historian/SCADA/forecasting inputs 
  • Substation rack ↔ WAN/backhaul ↔ owner/utility endpoints 
  • Surveillance ↔ NVR ↔ network segmentation policies 

If you validate each subsystem in isolation but delay interface testing, the last 10% of integration will consume the last 50% of the schedule. 

2) Centralize routing and documentation like it’s a deliverable (because it is) 

Lonestar routed all data through a centralized substation rack, which is a smart architectural choice for manageability—but it also becomes a single point of commissioning truth.  

Lesson: Your “rack-as-a-product” needs its own commissioning storyline: 

  • Rack build standards, labeling, fiber management, power/UPS, grounding 
  • Port maps, VLAN/segmentation, firewall rules, remote access 
  • As-built network diagrams that match reality (not “design intent”) 
  • Evidence: photos of terminations, patch panels, labeling, and final rack state 

REIG’s broader workflow emphasizes photo uploads and rich documentation as part of getting field reality captured and turned into report-ready evidence.  

3) Use phase-based checklists that match how comms work actually happens 

REIG structured work around multiple checklists tied to phases—installation, testing, commissioning, and internal project management—rather than one mega checklist.  

Lesson: Hybrid sites demand phased verification because failures propagate.

Lonestar Solar and BESS project

This structure reduces “we did the work but can’t prove it” moments—especially when you’re handing off to owners, EPCs, and utilities who want objective evidence. 

4) Design for crew rotation and continuity—because the crew will change 

REIG uses a crew-based access model rather than assigning tasks to individuals, specifically because crews rotate and availability changes.  

Lesson: Communication commissioning suffers when knowledge is trapped in one tech’s notes. Crew-based workflows (with clear permissions) reduce bottlenecks when: 

  • the installer who pulled fiber isn’t the one doing final OT/SCADA validation 
  • multiple crews hit different blocks of the site concurrently 
  • you’re commissioning in waves (solar first, storage later, then integrated testing) 

Continuity is not a “process nice-to-have” on hybrids—it’s how you prevent rework. 

5) Avoid rigid templates—hybrids vary too much site to site 

REIG intentionally avoids one-size-fits-all templates. Instead, they keep a library of checklists and tailor them per project, because scale and topology change dramatically across sites.  

Lesson: For comms companies, the “same” hybrid site can still differ in: 

  • number of fiber pads / enclosures 
  • OEM mixes (inverters, PCS, EMS, met) 
  • substation interfaces and utility telemetry requirements 
  • security segmentation and remote access rules 
  • surveillance scope and retention requirements 

A flexible checklist library lets you standardize quality without pretending every site is identical. 

6) Non-traditional subsystems (like surveillance) will bite you unless you commission them like SCADA 

Lonestar explicitly included surveillance systems integrated with the network via NVRs and camera feeds.  

Lesson: Treat surveillance as an OT-adjacent system with: 

  • bandwidth and QoS considerations 
  • segmentation/VLAN design 
  • evidence of camera provisioning, naming conventions, and recording verification 
  • failover behavior (power loss, link drop, storage full) 

Owners remember when their security system “mostly works.” Don’t let that become your perceived quality signal. 

7) Client trust is earned in reporting, not in your toolset 

In REIG’s model, customers often interact more with outputs than the platform itself, and REIG emphasizes professional, consistent reporting as a differentiator.  

Lesson: For communication infrastructure providers, your report is your product: 

  • clear interface test results (not just “pass”) 
  • traceable evidence (photos, logs, tag lists, serials) 
  • standardized closeout packages that make O&M easier 
  • fast answers when a performance analyst asks, “Is this a field sensor issue or a data path issue?” 

Hybrid sites add complexity; your reporting has to reduce it. 

What this means for comms specialists on hybrid projects 

Lonestar is a great reminder that the communications scope on hybrid sites is no longer a “supporting function.” It’s foundational infrastructure that enables: 

  • real-time operational visibility (across solar + storage)  
  • reliable data delivery to the owner’s analytics and decision tools  
  • confident handover, audits, and troubleshooting based on defensible evidence 

Bluerithm for Utility-Scale Solar + Storage 

Bluerithm helps solar and BESS teams turn commissioning into a repeatable, evidence-backed process—from first install checks through integrated testing and closeout. With configurable checklists, mobile field capture (photos, notes, results), and centralized issue tracking, your crews, subs, and stakeholders stay aligned while you produce clean, audit-ready turnover packages. If you’re building data acquisition and communications infrastructure on utility-scale hybrid sites, Bluerithm gives you the structured workflow and traceability to commission faster, reduce rework, and hand owners a system they can operate with confidence. 

REIG Case Study

“We’ve gotten really positive feedback from our customers on the professionalism and the consistency of our reporting. That probably is what has separated us from others.” – Brian Otto, CEO, Renewable Energy Integration Group (REIG)

Additional resources:

Case Studies

Learn how Bluerithm's customers have used the software

Read

Guides

Learn more about commissioning and related topics

Read

Videos

Learn how Bluerithm can help you by viewing these videos

View

Webinars

Recordings of previous webinars

View