Solar SCADA Commissioning to COD: Timeline + Milestones

On a utility-scale PV project, “SCADA is late” is rarely a SCADA-only problem. Delays usually come from missing definitions (point lists that aren’t testable), unproven boundaries (device-to-historian values that look right but aren’t), or incomplete communications evidence (fiber that passes light but drops packets). The result is predictable: COD pressure rises, the punch list grows, and operations inherits data they can’t fully trust.

This article is for owners/operators, developers, EPCs, commissioning leads, SCADA/DAS engineers, and O&M teams who need a practical solar SCADA commissioning timeline with clear milestones and deliverables. Use it to plan the work, sequence dependencies, and ask for the evidence that keeps commissioning from turning into months of cleanup.

First: define what “commissioned” means (not just “online”)

In the field, a point “showing up” on an HMI only proves communications exist. It does not prove the value is correct, time-aligned, and usable for KPIs, utility telemetry, or control tests. A commissioning-ready definition is: the system is validated end-to-end with documented evidence and a turnover package O&M can use.

A simple validation framework: Measurement, Meaning, Control

Use this to structure every test step and every acceptance discussion:

1. Measurement: Is the underlying device reading/action correct (wiring, CT/PT ratios, sensor orientation, calibration, device setup)?
2. Meaning: Are units, scaling, sign conventions, timestamps, and quality flags consistent through the whole chain?
3. Control: When a setpoint/command is issued, does the plant respond predictably at the defined boundary (typically POI) within the required tolerances?

This prevents the most common failure mode: “It moves on the screen, so it must be right.” Movement is not validation.

Solar SCADA commissioning timeline: phases, milestones, and exit criteria

Every project’s sequence differs, but most commissioning programs follow a similar progression. The key is to tie each phase to testable deliverables and exit criteria.

Phase 0 (Pre-construction / early design): lock requirements before the field is busy

If you wait to interpret utility telemetry and control requirements until the last month, commissioning becomes an integration scramble. This phase is where you prevent that outcome.

• Milestone: Utility/ISO interface defined (protocol, point list, test plan, access method).
• Milestone: Control philosophy documented (PPC roles, inverter/block control, ramp strategy, fallback states).
• Milestone: Data boundaries defined (inverter vs MV vs POI for reporting and KPIs).

Exit criteria: a written requirements map that ties each utility requirement to a concrete plant source and a test method.

Phase 1 (Late construction): build commissioning into the install, not after it

This is the point where comms hardware, networks, field devices, and cabinets are being installed quickly. If evidence collection is not embedded here, teams end up re-opening cabinets and re-trenching late in the schedule.

• Milestone: Network architecture installed and documented (VLANs/subnets if used, IP plan, managed switch configs saved).
• Milestone: Fiber plant baselined (OTDR traces and insertion loss results where required; labeling and route documentation).
• Milestone: Time source implemented (NTP configuration and verification plan for controllers/servers/historian).

Exit criteria: field infrastructure is not just installed, but traceable in documentation (as-builts, configs, baseline tests).

Phase 2 (Device integration): prove each device locally before you blame SCADA

Before doing plant-level tests, validate each device class in isolation so troubleshooting stays fast and evidence-based.

• Milestone: Metering configured and reconciled (CT/PT ratios, sign conventions, SCADA vs meter front panel comparisons).
• Milestone: MET and irradiance channels validated (plane/orientation, scaling applied once, plausible values under clear conditions).
• Milestone: Inverter and tracker communications stable (register maps correct, scan rates reasonable, no polling overload).

Exit criteria: each device group has a short test record showing “raw value” to “engineered value” correctness and stable comms.

Phase 3 (SCADA/DAS functional commissioning): end-to-end point integrity and historian truth

This is where many projects discover they have “two truths”: the HMI looks okay, but the historian/KPI layer is wrong due to scaling, time alignment, or mapping errors.

• Milestone: Commissioning-ready point list finalized (source, address, data type, byte/word order, scaling math, units, expected ranges).
• Milestone: End-to-end value checks completed for critical points (POI MW/MVAR, irradiance, inverter totals, breaker/status points).
• Milestone: Quality flags implemented (stale/bad/substituted values handled intentionally, not silently shown as “good”).

Exit criteria: critical values match known-good references at the device and in the historian, with aligned timestamps and correct units.

Phase 4 (Controls and utility witness testing): prove command path and plant response

Controls are where schedule risk concentrates because multiple boundaries are involved: utility endpoint, RTU/RTAC, PPC, inverters, plant electrical boundary at POI, and metering truth.

• Milestone: Telemetry mapping verified at the utility boundary (DNP3 or IEC 60870-5-104 points, quality, timing, and naming as required).
• Milestone: Active power control proven (MW or % setpoints, ramps, response time measured at POI).
• Milestone: Reactive power / PF / voltage modes validated (per interconnection agreement and PPC design).

Exit criteria: a staged control test report with measured results at POI, plus a rollback procedure that was verified during testing.

Phase 5 (Turnover to operations): deliver a system O&M can maintain

Turnover is not a folder dump. It should reduce future downtime by making troubleshooting fast and unambiguous.

• Milestone: As-builts complete (network drawings, IP plan, fiber routes, port maps, cabinet labeling).
• Milestone: Config backups delivered (managed switches, RTU/RTAC, PPC where applicable, servers).
• Milestone: Baselines archived (OTDR traces, OLTS loss results if required, calibration certificates, commissioning test evidence).

Exit criteria: O&M can answer “what changed?” when an issue arises because a baseline exists and the system is documented.

Milestones that matter most (and why they prevent rework)

Commissioning checklist (field-practical, COD-minded)

Use this list to drive daily commissioning progress and to avoid “we’ll fix that later” decisions that become COD risks.

1. Freeze a version-controlled point list and track any changes as controlled revisions.
2. Validate the POI meter truth: CT/PT ratios, signs, units, and reconciliation evidence.
3. Verify irradiance and MET install: correct plane (POA vs GHI), leveling/alignment, scaling, and cleaning plan.
4. Prove scaling is applied once: especially for irradiance sensitivity and 4–20 mA ranges.
5. Confirm time alignment: NTP everywhere, consistent logging intervals, and correct time zones/DST handling per project standard.
6. Stress-test comms stability: identify intermittent drops, overloaded polling, or switch misconfigurations before witness testing.
7. Validate alarms like operators: priorities, deadbands, clear text, and escalation rules to avoid alarm floods.
8. Run a controlled “day in the life” test: pick a period, compute key KPIs independently, confirm historian values match the HMI and reports.

Common COD blockers (and how to avoid them)

1) “Online but wrong” values

Typical causes are incorrect Modbus register mapping, wrong data type, swapped word order, or double scaling. Fix this by testing at each boundary: device reading, gateway/controller, SCADA ingestion, historian value, and report output.

2) Time drift and misaligned averaging windows

Even small timestamp misalignment can make PR and curtailment math unstable and can cause alarms to trigger “late.” Treat time sync as a first-class commissioning item, not an IT afterthought.

3) POI sign convention confusion

Export/import definitions vary. Align the sign convention early, document it, and validate with a controlled operating condition during commissioning. Do not wait until utility witness testing to discover the sign is flipped.

4) Fiber that passes light but still causes dropouts

Intermittent comms often comes from dirty connectors, marginal terminations, water intrusion, or undocumented splices. Baseline OTDR traces and organized loss results help isolate whether the issue is fiber, switching, or device-layer behavior.

What to require in the SCADA turnover package

If you want long-term reliability, contract for deliverables that make troubleshooting fast. A strong package typically includes:

• Final point list with sources, addressing, scaling, units, and data types
• Network as-builts (IP plan, VLAN/subnet mapping, port maps)
• Managed switch configuration backups and key gateway configs
• Fiber documentation (route as-builts, splice matrices, OTDR traces, OLTS results if required)
• Commissioning test reports (telemetry validation, control testing, meter reconciliation)
• Device inventory (models, serials, firmware versions, calibration certificates for sensors)

Where REIG fits: commissioning-ready SCADA + DAS integration

Renewable Energy Integration Group (REIG) is a solar SCADA and DAS integration contractor based in Charlotte, supporting utility-scale PV with end-to-end design, installation, commissioning, and ongoing support. REIG focuses on making plant data reliable from day one by integrating network communications (including fiber/optical services), device configuration, alarm strategy, and end-to-end validation—plus commissioning-ready hardware/enclosures through RenergyWare where a standardized build helps reduce variability and rework.

Conclusion: COD goes faster when milestones are evidence-based

Solar SCADA commissioning moves quickly when the project treats SCADA as a system-of-systems and plans the evidence early: a testable point list, proven meter truth at POI, validated time sync, baselined fiber/network health, and staged control test results. When those milestones are met, COD becomes a controlled finish—not an open-ended cleanup effort.

If you want a commissioning plan and turnover package that keeps data trustworthy after COD, REIG can help review your point list, validate signals end-to-end (including fiber verification), and deliver a commissioning-ready SCADA + DAS handoff that O&M teams can run with.