This system map is part of the commissioning punch list closure guide, which covers what to inventory before commissioning handover. It answers a narrower question for energy project systems advisors: can a contractor's records actually be joined into one story, issue by issue?
The map: system, record, linking key, owner
Three places hold the pieces. The graphic shows them as columns with the keys moving between them.
| System | Record | Linking key | Typical owner |
|---|---|---|---|
| Cx platform | Component and system test runs, pass or fail, with date and witness | Equipment tag, test ID, run number | Cx manager |
| Cx platform | Issues and resolution log entries | Issue ID, linked test ID, equipment tag | Cx manager |
| Document control | Drawings and equipment schedules | Equipment tag | Document controller |
| Document control | Field changes, requests for information, revised drawings | Field change number, cited issue ID | Project engineer, filed by document control |
| Document control | Owner sign-offs listing accepted items | Item list with issue IDs or tags | Document controller |
| Handover set | Final test sheets and closed issues log handed to the owner | Equipment tag, issue ID | Owner, under the contract |
Two keys carry the whole map. The equipment tag joins anything about a piece of equipment across systems. The issue ID joins a failure to its fix and its proof. When both survive, a case can be rebuilt; when either is lost, it cannot.
Where each link breaks
| Link | Cx platform side | Document control side | Common break |
|---|---|---|---|
| Equipment tag | Tag on each test form | Tag on drawings and schedules | Tags renumbered between design and construction |
| Test runs | Each run with date and witness | Only the final successful form in handover | Failed runs overwritten by the pass |
| Issue to test | Issue linked to the failing test | Punch item with its own numbering | Issue and punch item never reference each other |
| Issue to fix | Note on the issue | Field change or RFI | Fix recorded only in an email thread |
| Issue to repeat run | New run linked to the issue | Final test sheet | Repeat run not linked back to the failure |
| Acceptance | Issue closed by the commissioning lead | Owner sign-off | Batch acceptance with no item list |
A single break is enough to orphan a case: the repeat run exists, the fix exists, but nothing says they belong to the same failure.
One fully joined case (Illustrative)
A fictional 420-person energy contractor commissions a battery storage project. The project, tag and issue number are invented for this page; nothing here is a real job or a completed deal. Follow equipment tag PCS-03, a power conversion system, through the map:
- Commissioning platform, test run 1. PCS-03 fails its grid-forming response test; the run is saved with date and witness.
- Commissioning platform, issues log. Issue CX-112 opens, linked to run 1 and tagged PCS-03, assigned to the integrator.
- Document control, field change. Field change FC-041 updates a controller setting and cites CX-112.
- Commissioning platform, test run 2. PCS-03 passes; the run is linked to CX-112.
- Commissioning platform, issue closed. The commissioning lead closes CX-112 with links to run 1, FC-041 and run 2.
- Document control, acceptance. The owner's sign-off lists CX-112 by number among accepted items.
- Handover set. The owner receives the successful run 2 and the closed log entry.
From any one of these records, the rest can be found: the tag finds the tests and the drawing, the issue ID finds the fix, the repeat run and the acceptance. That is a joined case. The exception examples page walks a harder case in which every unit passed and the system did not.
Test an archive with one closed issue
Ask the commissioning manager to pick one closed issue from a finished project, two or more years old. Then ask, without opening anything for you:
- Can they find the original failing run from the issue ID?
- Can the document controller find the fix record that cites the issue?
- Is the successful repeat run linked back to the same issue?
- Does the owner acceptance name the issue or the tag?
- Do the tags on the test forms match the tags on the as-built drawings?
Industry practice expects the linked version. ASHRAE Standard 202 calls for an issues and resolution log that tracks each open item, its status and the responsible party until the owner accepts it, with testing repeated until systems pass. For grid-connected PV, IEC 62446-1 covers the documentation handed to the customer. Neither says the contractor's working links survive after handover.
Five yes answers mean the archive can tell stories, not just show that equipment passed. Each no is a finding to write down plainly: "runs kept only since 2021" or "sign-offs are batch signatures" helps SourceX more than an optimistic summary. For general project platforms, the page on Procore project data lists questions to ask an administrator about what survives export. If handover happens alongside closing a site office, the office closure checklist covers what disappears with it.
Owners, rights and what stays open
The map names who holds each record, not who may license it. The owner typically has rights in the handover set; the contractor's working records may be its own, subject to confidentiality terms in each contract, and manufacturer data can carry further limits. Start with the commissioning director, who can name the executive with authority. The referral brief template has room for the findings from the test above, and the construction punch list process page and construction and field services page give wider context.
Unknown until SourceX reviews it: which projects and record classes the company can license, how they would be de-identified, whether a buyer wants commissioning histories and whether any offer follows. 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.
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 one closed issue at a contractor client leads back to its failed test, fix and repeat run, register as a partner, check the company against who qualifies and read the program terms before you introduce the commissioning director.