Solar SCADA Commissioning: Utility Witness Pack

The day a utility engineer arrives at your solar farm to witness solar SCADA commissioning is not the time to discover a point list mismatch. Interconnection approval for a utility-scale PV facility requires every telemetry point, control function, and communication path to be verified against the utility’s exact specifications and documented in a format the utility can accept on the day. The witness pack is the structured evidence bundle that makes that verification possible. Get it right, and interconnection approval follows within days. Miss one field in the tag list, and the witness test fails, setting your commercial operation date back by weeks.

What Is the Utility Witness Pack in Solar SCADA Commissioning?

Solar SCADA commissioning for interconnection includes a gate that many project teams underestimate: the formal utility witness test. Before a solar facility can receive commercial interconnection authorization, the transmission operator, distribution utility, or independent system operator sends representatives to verify that the SCADA system operates as specified in the interconnection agreement. The utility witness pack is the complete documentation bundle that supports and records those tests. It is the document set the utility signs before issuing commercial operation authorization. Without a complete, properly formatted pack in hand before the witness appointment, a team cannot pass this gate regardless of how well the SCADA system itself performs on the day. One missing signature or one incorrectly scaled point list comparison is enough to trigger a reschedule.

The scope of the witness pack is defined by the interconnection agreement’s SCADA exhibit. Every project’s exhibit is different, but the pack typically includes:

• The approved interconnection agreement and its SCADA/telemetry requirements appendix
• A point list comparison showing the utility’s required tags mapped against the as-built RTU or DAS tag database
• Communication configuration evidence: DNP3 unsolicited response settings, address mapping, redundancy paths
• Factory acceptance test (FAT) and site acceptance test (SAT) evidence from prior testing phases
• Signed test procedures and data sheets for each function the utility witnesses
• Any exception logs with written utility concurrence

Each document has a counterpart in the interconnection agreement exhibit. Utilities do not accept substitutions or verbal assurances. Only signed, dated, format-compliant documentation passes the witness gate. Teams that treat the witness pack as a post-test paperwork step rather than a pre-test preparation milestone are the ones who reschedule.

Which Tests Does the Utility Witness?

The scope of utility witness testing in solar SCADA commissioning depends on the interconnection level (distribution versus transmission), the utility’s tariff requirements, and the project’s size and grid impact. However, three categories of tests appear in nearly every utility witness procedure.

Telemetry Point List Verification

The utility’s primary concern is accurate, timely data at its energy management system (EMS). Every point on the required tag list (real power in MW, reactive power in MVAR, voltage in kV, frequency in Hz, and breaker and switch status) must report correctly and in real time. During the witness test, a utility engineer at the EMS control center calls out each required point while the commissioning team at the site confirms the reported value against a calibrated local reference meter.

Key acceptance criteria that utilities typically apply:

• Analog telemetry within ±1% of the reference meter reading (or per the tolerance specified in the interconnection agreement)
• Deadband configured to prevent excessive polling, typically 0.1 to 0.5% of rated value per DNP3 Class 1 event configuration
• Scan period at or below 4 seconds for critical analog points, per DNP3 Annex G guidance
• All status points (breaker closed, protection relay active, inverter run/fault) mapped with the correct normal-state polarity

A single tag with the wrong engineering unit or inverted polarity fails the point list check for that point. The utility will not proceed to control function testing until every required point passes.

Control Function Testing: Reactive Power and Frequency Response

IEEE 1547-2018 requires DER to maintain reactive power capability of ±0.44 power factor at rated active power output for Category B and C interconnections. During solar SCADA commissioning, utilities verify this by issuing reactive power setpoint commands through the EMS automatic generation control (AGC) system and confirming that the inverters respond within the specified time window, with the SCADA feedback value updating accordingly. FERC Order 842, effective June 2020, requires all new generating facilities to demonstrate primary frequency response capability during commissioning via a droop-based frequency-Watt test.

Control tests the utility typically witnesses include:

• Reactive power dispatch: utility commands a MVAR setpoint via AGC; SCADA confirms inverter execution within 30 seconds and reports the new reactive power value
• Active power curtailment: utility commands a MW limit; site must reach the setpoint and hold within ±2% tolerance for a defined observation window
• Frequency-Watt response: under-frequency event is simulated; inverters must reduce active power in accordance with the configured droop setting; SCADA historian captures the response with sub-second timestamps
• Voltage ride-through: for Category B and C interconnections under IEEE 1547-2018, mandatory low-voltage and high-voltage ride-through bands are confirmed against the inverter configuration

Communication Protocol Validation: DNP3 and IEEE 2030.5

The communication link between the solar plant SCADA system and the utility EMS must use the protocol specified in the interconnection agreement. DNP3 (IEEE Std 1815-2012) is the dominant protocol for bulk electric system interconnections across North America. IEEE 2030.5, also known as SEP 2, has become the required protocol for distribution-level DER interconnections in California and FERC Order 2222 aggregation contexts. IEC 62351 adds the security layer: encryption, authentication, and role-based access control that transmission utilities now require on DNP3 links for new generation interconnections.

During solar SCADA commissioning, the utility witness verifies:

• Correct DNP3 master and outstation address assignment matching the interconnection agreement exhibit
• Unsolicited response mode is active and configured with the correct event class assignments (Class 1, 2, and 3)
• Communication path redundancy: primary fiber and backup cellular or radio path, with failover confirmed within the agreed maximum timeout
• Data timestamp accuracy within ±1 second of UTC, confirmed against a GPS or verified NTP time source

The Evidence Pack Your Commissioning Team Must Prepare

A well-organized utility witness pack makes the difference between a one-day sign-off and a multi-week rescheduling loop. The evidence pack is not a post-test summary. It is a pre-structured document set that the commissioning team completes progressively from FAT through SAT, ready for the utility to review on the day of the witness.

Teams that skip the pre-witness audit step are most likely to experience first-pass failures caused by documentation gaps, which are entirely preventable with a 2-hour audit against the interconnection agreement exhibit.

Failure Modes: Why Solar SCADA Commissioning Witness Tests Fail

Most solar SCADA commissioning witness tests that fail on the first attempt fail for one of four reasons. None require the utility to be unreasonable. Each is a gap in preparation that a structured pre-witness checklist would have caught. In our experience commissioning SCADA systems across multiple ISOs, teams that schedule the witness without completing a 24-hour pre-witness telemetry review fail at twice the rate of those who do.

Point List and Time-Sync Failures

Point list mismatch. Point list errors account for 38% of first-pass failures (REIG Solar field commissioning data). The utility’s required tag list specifies exact tag names, engineering units, and scaling factors. RTU configurations built from an older version of the interconnection agreement may report in kW where MW is required, reverse the polarity on reactive power (import versus export sign convention is a persistent source of confusion), or use tag names that were renamed during the design review. The fix is simple: request the current utility tag template one week before the witness, not months earlier during initial engineering.

Time synchronization drift. DNP3 timestamps must be accurate within ±1 second of UTC for most utility EMS systems to accept events without flagging the time quality bit as COMM_LOST or RESTART. A GPS receiver that lost satellite lock during a storm, or an NTP server that is polling a stratum-3 source with accumulated drift, will generate time-stamped events that the EMS rejects silently. The commissioning team must export and review the GPS or NTP sync log during the 24 hours immediately before the utility witness.

Control Non-Response and Documentation Gaps

Control non-response. If the inverter firmware was updated between FAT and the site acceptance test, or if the SCADA-to-inverter Modbus register map changed after the FAT, reactive power commands may execute at the inverter level without propagating the correct feedback value to the SCADA point the utility observes. This creates the frustrating scenario where the inverter physically responds correctly but the SCADA display still shows the previous setpoint, an automatic failure in the control function test.

Documentation gaps. Even when every test passes technically, a utility representative cannot sign off on evidence that is missing a required signature, uses a superseded form version, or doesn’t match the format specified in the interconnection agreement exhibit. Run an evidence pack audit against the IA exhibit checklist before requesting the witness appointment.

Timeline for Utility Witness Testing Relative to COD

Scheduling the utility witness without first completing the SAT and pre-witness verification is the most common timeline risk in solar SCADA commissioning projects. When a witness test fails, the next available appointment is typically 2 to 4 weeks out. It requires a utility engineer’s calendar, not just the commissioning team’s schedule.

The standard sequence for utility witness testing runs as follows:

1. FAT completion: integrator and owner sign factory acceptance test records; all required functions pass
2. Energization: medium-voltage switchgear energized, inverters brought online in commissioning mode
3. SAT completion: all site acceptance test procedures completed and data sheets signed by integrator and owner
4. Pre-witness verification: 24 to 48 hours of continuous SCADA telemetry monitoring to confirm stable operation, no timestamp errors, and no missing points
5. Utility witness scheduling: advance notice of 2 to 4 weeks is required by most interconnection agreements; some transmission utilities require 4 weeks minimum
6. Witness test execution: typically one full day for a 20 to 100 MW facility
7. Evidence submission: signed witness pack submitted to the utility within 5 business days of the witness date
8. Interconnection authorization: utility issues written authorization to operate commercially; COD is confirmed

For a detailed look at the full commissioning schedule from energization through COD, including milestone dates, NERC IRO-016 reporting triggers, and the evidence required at each step, see Solar SCADA Commissioning to COD: Timeline and Milestones.

Measurement, Meaning, and Control in Solar SCADA Commissioning

The REIG approach to solar SCADA commissioning structures every deliverable around three functions: Measurement, Meaning, and Control. The utility witness test evaluates all three, and failures in any one of the three categories are sufficient to delay interconnection.

Measurement is the telemetry accuracy and completeness layer. NERC IRO-016-2 requires reliability coordinators to collect real-time data including active and reactive power, and utilities mirror those requirements in their interconnection agreements. Every sensor value that flows from the field device through the RTU to the utility EMS must be present, correctly scaled, and within the tolerance specified in the interconnection agreement. A real power measurement that arrives 3 seconds late or a reactive power reading in kVAR when MVAR is required fails the Measurement standard, regardless of how accurate the physical transducer is.

Meaning addresses the data quality layer. DNP3 carries quality flags alongside every data object: ONLINE, RESTART, NOT_INITIATED, OVER_RANGE, and others. When a point reports with a RESTART quality bit, the utility EMS interprets it as unreliable and drops it from the real-time display. Meaning failures are often invisible during internal testing because the integrator’s own SCADA system may suppress quality bits that the utility EMS exposes. Pre-witness verification must include a review of quality codes seen from the utility-facing communication link, not just the internal historian.

NIST SP 800-82 (Guide to Operational Technology Security) provides the data integrity and communication path security framework that utilities increasingly reference when writing their interconnection monitoring requirements. Understanding these requirements before the witness date prevents control system configuration surprises on the day.

Control: The Highest-Risk Test Element

Control covers everything the utility can command: reactive power setpoints, active power curtailment, and frequency response activation. Control is the highest-risk test element because a failed control test requires a firmware change, configuration correction, or hardware fix before retesting. It cannot be resolved with a document revision. Teams must verify the full control chain from the utility EMS command to the inverter response and back to the SCADA feedback point before scheduling the witness.

Where RenergyWare Fits: Field-Proven Solar SCADA Commissioning Records

REIG Solar’s field-proven RenergyWare platform gives commissioning teams a structured environment for building, auditing, and submitting the utility witness pack. Rather than assembling the evidence bundle from scattered spreadsheets, PDFs, and email threads, RenergyWare maintains the live point list comparison, the DNP3 configuration export, and the test data sheets in a single commissioning record linked to the interconnection agreement exhibit.

Before the utility witness, the commissioning team runs a pre-witness audit in RenergyWare that checks every required tag against the current utility template, flagging mismatches in units, scaling, and tag names before the utility engineer arrives. RenergyWare captures the 24-hour GPS and NTP sync log and attaches it to the evidence pack automatically. After the witness, the signed pack generates in the utility’s required submission format with no reformatting, no missing pages. On interconnection projects REIG has commissioned across PJM and WECC queues, this pre-witness audit step typically catches 6 to 12 tag mismatches that would have triggered a reschedule.

For projects following a structured commissioning plan, RenergyWare also tracks the relationship between SAT procedure records and the specific witness test categories they support, ensuring that a signed SAT data sheet exists for every item on the utility’s witness procedure before the appointment is scheduled. For more detail on what the SAT covers and how it differs from the factory acceptance test, see Solar SCADA Commissioning: FAT vs SAT.

To understand how the witness test fits into the full commissioning sequence from FAT through COD, see Solar SCADA Commissioning Checklist: Controls, Alarms, and Evidence.

Ready to build a utility witness pack that passes first time? Contact the REIG Solar team or explore the RenergyWare platform to see how it supports solar SCADA commissioning evidence management from FAT through interconnection authorization.

• Further reading: Solar SCADA Commissioning Failures: Tag Mapping, Comms, and Time Sync
• Further reading: Solar SCADA Integrator: Roles and Deliverables
• Further reading: Solar Plant SCADA System: Reference Architecture Diagram
• Further reading: SCADA Integration Services: FAT/SAT Evidence Checklist