One integrated test in the delivered set is titled as an electrical source event concurrent with a liquid-cooling fault. Its initiating action is to trip one liquid pump or coolant-distribution unit at the same moment as the electrical source event. Its release authority still reads commissioning authority, owner and discipline record engineer, in the singular [TARGET]. That same column already names the utility on five other rows and the fire authority on two, so the register can carry more than one authority and does.
Joint Scenarios Already Name Two or Three Adjudicators
Closure responsibility is written in the commissioning index as a three-part field on every joint scenario: who executes, who adjudicates, who approves. Thirteen of the fourteen joint scenarios name two or three adjudicating parties [TARGET]. Three of those scenarios bear directly on this one:
- coolant leak and isolation: cooling adjudicates, electrical and fire counter-sign;
- fire interlock conflict: three record engineers adjudicate together;
- distribution-room cooling loss: electrical and mechanical adjudicate.
One level up, the heat-rejection basis sets the same pattern. Of its seven integrated checks, five are released jointly by the electrical and cooling sides, one by cooling alone and one by electrical alone [TARGET]. The heat-rejection chapter itself records that a joint integrated test must be held by both sides as a release condition.
The Self-Feedback Path Bypasses Every Cooling Redundancy
A self-feedback path is the reason the pairing is not administrative. With the incoming supply lost, the uninterruptible units run at their highest internal loss. If the cooling serving their own room has been graded non-critical and shed, that room then carries between 454 and 545 kW [MODELED] of the units' loss with no forced cooling. Over-temperature derating or a trip takes the protected load out entirely. Its hardest property is stated in the basis: the path bypasses every cooling redundancy because it never passes through the cooling system. A cooling functional test cannot find it. It is not an electrical fault.
Allowable loss-of-cooling time for that room has not been defined. The miscellaneous heat term it depends on has not been quantified. Both are recorded open against the electrical and mechanical disciplines jointly. So the scenario has no criterion of its own today. Executing it would produce a record in the executed-but-unadjudicated state instead of a verdict, whichever disciplines sign the release.
Read as a schema limit and not as an allocation, the singular rests on a convention the register does not print. If the register carries an unwritten rule that the singular expands at execution to whichever disciplines the scenario names, the row is already correct and the matrix is the place to look. No such rule appears in the register or in the package that publishes it.
Release Expands Only to Parties Outside the Design Team
That is not the only cross-discipline conflict the matrix expects the same class of test to expose. Its coolant leak scenario records, inside the acceptance criteria and not in a footnote, that the valve interlock requiring a de-energised valve to hold its position and the isolation command requiring it to close may contradict each other, and instructs that the actual behaviour be recorded when they do. Contradictions of that shape have an electrical cause and a mechanical consequence. That is exactly the pair the singular cannot name.
There is a pattern in which rows get a second authority. Eight of the thirty rows name a party beyond the commissioning authority, the owner and the discipline record engineer [TARGET]. In every one of the eight that party is the utility, the fire authority, or both. Each of those is outside the design team. Where both parties who must adjudicate sit inside it, the register writes one. Eleven of the thirty rows are graded critical and twelve high, so the singular is not confined to the low-consequence end of the set [TARGET]. The electrical-and-cooling row is itself graded critical. Every row in the register is still open.
Whether the singular is a schema limit or a deliberate allocation is not answerable from the file itself. The column holds free text and no legend accompanies it.
Limits and open items
Confirmed: the self-feedback path bypasses every cooling redundancy because it never passes through the cooling system; the coolant-leak acceptance text records that a de-energised hold and an isolation command may contradict each other. [FACT]
Study values, not a campaign: 454 to 545 kW of self-generated loss in a room whose own cooling has been shed. The efficiency and protected-load figures behind that band remain unfrozen. [MODELED]
Register figures: one of thirty rows crossing electrical and cooling with a singular discipline in its release authority; eight rows expanding, all to a party outside the design team; eleven critical and twelve high; five of seven integrated checks released jointly; thirteen of fourteen joint scenarios naming two or three adjudicating parties. Currently executable joint scenes: zero. [TARGET]
Open: the register author's written rule on whether the singular expands; an allowable loss-of-cooling time for the distribution room; a quantified miscellaneous heat term; any of the thirty hold points released. [HOLD]
Nothing here has been reviewed or sealed by an Engineer of Record. Nothing describes how any installed system behaved.
Whether the Singular Is a Schema Limit or an Allocation
The register's author still needs to say whether the singular is a schema limit or a deliberate allocation, and to say it before the first joint release is signed, not at the release meeting.
© 2026 K&K Data Service Inc. All rights reserved. Reproduction or republication is permitted only with clear attribution to K&K Data Service Inc. and a working hyperlink to the canonical URL of this article. Excerpts must preserve the technical context, maturity labels, assumptions, and limitations. No excerpt may imply project approval, field validation, certification, or endorsement that the original article does not state.
Source: K&K Data Service Inc., “Joint IST Needs Electrical and Cooling Release Stamps,” https://www.kkdatasvc.com/lab/rfq-vendor-review-and-commissioning/joint-ist-needs-electrical-and-cooling-release-stamps/.
Discuss This Constraint. If your project record shows a different result, or the same failure domain under another name, we want to see it. Email inquiry@kkdatasvc.com or use the contact page.