# Commissioning exception: a worked tracker case | SourceX

Canonical: https://refer.sourcex.si/guides/commissioning-punch-list-closure-exception-examples
Last updated: 2026-11-04

The records that explain an exception during startup testing are the failed run, the open item raised against it, the root-cause note, the approved fix, the repeat run that passed and the owner's sign-off on the closed item, all tied together by one item number. The hardest and most instructive version is a plant-wide test that fails after every unit passed on its own. The worked example below follows one such case on a solar tracker field, names who decided each step and which record kept it, and ends with signals that a client has similar cases.

This case belongs to the [commissioning punch list closure guide](/guides/workflow-commissioning-punch-list-closure), which covers the record inventory before project handover. Here the job is narrower: show one exception in full, so energy project systems advisors can recognize history worth an introduction.

## The setup (Illustrative)

A fictional 380-person engineering, procurement and construction contractor is bringing a solar plant online. The array sits on single-axis trackers grouped into 24 blocks, each with a network control unit. A plant supervisory system sends a stow command to every block when the on-site weather station reports high wind, so the panels flatten before gusts can damage them.

Three parties matter. The contractor's commissioning (Cx) lead runs the testing program on a Cx platform. The tracker supplier's field engineer configures the block controllers. The owner's engineer witnesses tests and signs off completed items.

The plant, the companies and the item number are invented for this page. Nothing here is a real project or a completed deal.

## The case, week by week

| Week | What happened | Who decided | Record that kept it |
|---|---|---|---|
| 1 | All 24 block controllers pass local checks: drive, limit switches, manual stow from the panel | Tracker supplier's field engineer, witnessed | 24 signed unit test forms |
| 3 | Plant-wide high-wind stow test, triggered by a simulated weather signal: 16 blocks stow, 8 stay tilted | Cx lead records the run as failed rather than quietly repeating it | Failed integrated run, dated, with the block list |
| 3 | Item CX-063 opened against the integrated test and assigned to the tracker supplier | Cx lead | Open item with status and responsible party |
| 4 | Network trace shows blocks 17 to 24 were set to the wrong broadcast group, so the plant command never reached them | Supplier's field engineer, reviewed by the contractor's controls engineer | Root-cause note attached to CX-063 |
| 4 | Addressing corrected under a configuration change | Contractor's project engineer approves | Configuration change record in document control |
| 4 | Stow test repeated with the same simulated signal; all 24 blocks stow inside the required time | Cx lead, witnessed by the owner's engineer | Repeat run linked to CX-063 |
| 5 | CX-063 closed with links to the failed run, the change record and the repeat run; owner's engineer signs it off | Cx lead closes; owner's engineer accepts | Closed item in the owner-accepted log |

## Why no unit test could have caught it

Each block did exactly what its local panel told it. The fault lived in the network: eight controllers listened on a group the supervisory system never addressed. A local test exercises the drive and the limits, not the path from the weather station through the plant network to each controller. Every unit form was valid, and the plant still could not protect itself in a storm.

That is what makes the case worth keeping. A reader holding only the unit forms would conclude the field was ready. Only the failed integrated run, the block list and the root-cause note show the reasoning that found a fault no unit checklist named.

## Four decisions that made the record valuable

The history is useful because people made specific calls and wrote them down. Remove any one and the case loses its explanatory power.

1. **Record the failure as a failure.** The Cx lead could have fixed the addressing informally and run the test again. Logging the first run as failed, with the list of blocks that did not move, is what preserves the evidence.
2. **Assign the item to the party who can fix it.** Opening CX-063 against the supplier, not as a general note, created accountability and a status that someone had to move.
3. **Approve the fix formally.** The configuration change record shows who authorized touching 8 controllers and why. Without it, the repeat run looks like the problem disappeared on its own.
4. **Repeat the same test, not an easier one.** Using the same simulated signal makes the second run comparable to the first. A different test would prove something else.

Industry practice expects this pattern. ASHRAE Standard 202 calls for a formal [issues and resolution log](https://www.ashrae.org/file%20library/technical%20resources/standards%20and%20guidelines/standards%20addenda/202_2018_e_20240104.pdf) kept until every item is resolved or accepted by the owner, with status and responsible party for each, repeat testing until systems pass, and a final log the owner accepts. For grid-connected PV, IEC 62446-1 describes the [tests, inspection criteria and documentation](https://webstore.iec.ch/en/publication/63726) handed to the customer. Contracts decide which standard governs a given job, and neither says the contractor's own working history survives after handover. The owner's set usually holds the 24 unit forms, the passing repeat run and the closed item; the failed run and the root-cause note often live only on the contractor's side. The [system map](/guides/commissioning-punch-list-closure-records-across-systems) shows which keys keep those pieces linked.

## How to recognize similar cases at a client

You can spot a company with history like this without seeing a single test sheet. Listen for:

1. **Integrated testing is in scope.** Plant, building or whole-system tests follow unit tests.
2. **Failed runs are kept as separate records.** Ask: "When an integrated test fails and is run again, do both runs survive?"
3. **Items are numbered and tied to tests.** The open items log and the test forms reference each other.
4. **Fixes have their own record.** Configuration changes, field changes or revised settings are documented, not left in email.
5. **Sign-offs name items.** The owner accepts a list, not a single batch signature.

If most apply, ask the director responsible for testing a metadata question: across how many jobs and years are failed runs and linked items kept, and on which platform? The [construction punch list process page](/data-types/construction-punch-list-process) covers the simpler visible-defect loop, and [defect closeout verification](/guides/workflow-defect-closeout-verification) covers defects that return after closure.

## Who to involve, and what stays open

The director who runs testing knows which platform holds failed runs and what each contract hands to the owner. Authority to discuss licensing usually sits with the CEO, COO or general counsel; the [who-can-say-yes decision tree](/questions/who-can-license-commissioning-punch-list-closure-records) walks through it. Ownership is contract by contract, and supplier configuration data can carry its own limits. Whether any records can be licensed, how they would be de-identified, whether a buyer wants them and any offer stay unknown until SourceX's rights review.

The introduced company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Partners sign the Channel Partner Agreement before submitting, and the first valid introduction within the 90-day window is credited when the company submits a verified application. The [energy and utilities page](/industries/energy-and-utilities) and the [data center electrical contractor page](/industries/data-center-electrical-contractor-private-equity) cover neighboring contractors.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a contractor client keeps failed integrated runs, linked items and repeat runs across its jobs, [register as a partner](/register), check the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce the director who runs testing.

## Sources

- https://www.ashrae.org/file%20library/technical%20resources/standards%20and%20guidelines/standards%20addenda/202_2018_e_20240104.pdf
- https://webstore.iec.ch/en/publication/63726
- https://refer.sourcex.si/terms
