Commissioning software for solar tracker systems where thousands of tracker rows, each with its own motor, controller and comms link, have to prove out before the plant can chase the sun.

A tracker system is not a fixed rack: every row has a slew drive, gearbox, controller and a comms segment tying it back to a master controller, installed and calibrated row by row across weeks of construction, often by a crew separate from the module installers.

When row calibration sheets, backtracking test results and comms commissioning records sit in a tracker OEM's own spreadsheet, the EPC cannot tell which rows are still running open loop or defaulting to flat stow rather than tracking the sun under the plant's control algorithm.

Deskely tags every tracker row, controller and comms segment individually, so a site can see exactly which rows are calibrated and networked, instead of trusting a tracker vendor's summary that the block is 'substantially complete'.

Slew drive torque, row levelness and zero-position calibration are captured against each row before the controller is commissioned to accept commands from the zone or master controller over the comms network.

Backtracking logic is functionally tested to confirm rows shade-avoid correctly at low sun angles, and wind-stow response is verified against the plant's wind speed thresholds, tripping rows to a safe stow position on command.

Comms dropouts, calibration failures and OEM punch on a slew drive or controller are logged against the specific row, so a handful of open rows in one zone does not block the rest of the plant from being released to auto-tracking.

Every tracker row's controller runs firmware that determines its backtracking algorithm, wind-stow thresholds and command response, and a mixed fleet — rows commissioned in different construction phases, or replaced under warranty — can end up running different firmware versions that behave subtly differently under the same master controller command, a discrepancy invisible until a wind event stows some rows late.

Deskely tracks the firmware version installed on every controller against the OEM's approved version list, so a row still running a superseded version is a visible finding rather than a fact only the tracker OEM's field technician happens to remember from the last site visit.

SCADA point-to-point verification confirms every tracker row's status, position and fault flags actually map through the zone controller to the plant historian correctly, because a row that is tracking perfectly but reporting to the wrong SCADA point looks, from the control room, exactly like a row that isn't tracking at all.

An electrolyser stack can commission cleanly on voltage, current density and gas production rate and still produce hydrogen that fails the offtake agreement's purity specification, because moisture carryover or incomplete oxygen removal in the purification skid shows up as a gas quality certificate problem, not a stack performance problem, and the two are tested and signed off separately.

Deskely holds gas purity certification — moisture content, oxygen content and any trace contaminant results against the offtake specification — as its own record set tied to the purification skid and the specific batch or continuous run it applies to, distinct from stack commissioning data, so a buyer's quality claim can be checked against the actual certificate rather than an assumption that the stack passed so the gas must be fine.

Hazardous area classification drawings define which zones require ATEX or equivalent explosion-protected equipment, and Deskely ties every electrical device installed in a classified zone back to its certification and the zone it was rated for, so a standard-rated fitting installed inside a Zone 1 boundary by mistake is a visible mismatch rather than something found during a safety audit years later.

Hydrogen sulphide scrubber media in a gas upgrading skid has a finite service life measured in cubic metres of gas throughput, not calendar time, and an environmental permit's odour control condition is usually written against media replacement being kept current, not against the gas leaving the plant smelling acceptable on the day of an inspection.

Deskely tracks scrubber media replacement against cumulative throughput on the specific skid, flagging an approaching replacement threshold the same way it flags an overdue preservation cycle, so odour control compliance is evidenced from a replacement log rather than reconstructed after a neighbour complaint triggers a regulator visit.

Digestate handling and land application on an anaerobic digestion site is typically governed by a nutrient management plan with its own permit conditions on volume, timing and nutrient content, and Deskely holds digestate sampling results and land application records as their own compliance record set, distinct from the digester's process commissioning data, because the two are audited by different parts of the regulator.