If the recovery check is run in January, which column on the closed set tells you it was January? None of them. A capacity test measured in winter against summer capability scores half a mark in the commissioning index, not a full one, and the fourth hard gate fails any object that counts such a test at full value [TARGET]. The heat-rejection basis states the same rule as a pass criterion: the recovery check has to be measured near the summer design condition, and a winter measurement is invalid [FACT]. Neither requirement can be applied to the delivered test set as it stands, because that set carries no field anywhere for the outdoor-air state, and until the acceptance schema gains one, a winter execution and a summer execution produce records that cannot be told apart.
The Index and the Recovery Check Both Require Season Validity
Season validity is a conditionally mandatory field at the system-performance level of the index, alongside the operating-case matrix and the load-normalisation rule. A test that does not meet it is marked season-limited and may not be counted at full value. One level up, the evidence grading makes the same case its worked example: partial or condition-limited measurement, given as winter measurement of summer capability, scaled load or single-component substitution, scores 0.50 where a judged and approved result scores 1.00 [TARGET]. Measured data with no approved criterion scores zero, which is the harder penalty of the two.
Season validity does not travel alone in that field list. Beside it sit the load method, which has to state how the applied load differs from real computing load and what that difference limits in the conclusion, and a normalisation rule requiring results taken under different load conditions to be converted before they may be compared, without which they may not be cited across tests. Both fields bound the same record from a different side, and neither can be filled from a row the delivered schema does not have.
Physics brings the heat-rejection chapter to the same place. Its recovery check requires the primary supply temperature to fall back to the design value, and attaches the condition that the measurement be taken near the summer design case, with the parenthetical that a winter measurement is invalid. Seven integrated checks sit in that table, and this is the only one released by the cooling side alone.
The Test Set Has No Field for Outdoor-Air State or Season
Thirty cases in sixteen columns make up the closed test set. Preconditions are identical on all thirty. Sampling frequency is identical on all thirty and defers the interval to the commissioning authority and the suppliers. No ambient column exists, no season column and no operating-case column. Every row is marked not executed. Below it, the acceptance parameter file holds 151 rows across those 30 tests, using 62 distinct parameter names and 20 units [TARGET]; not one of the 62 names an outdoor-air state, a season or a weather case.
Consequence shows up in a single row. The heat-rejection module failure test carries two physical thresholds, both to be confirmed:
- an approach temperature, in degrees Celsius;
- a fan ramp, in seconds.
An approach temperature is defined as a difference from an air state. So the one thermal criterion on the one heat-rejection test is expressed relative to a quantity the file has no way to record.
The Summer Design Case Has No Site-Valid Temperature
Summer design is a placeholder case with no site validity. Its dry-bulb and wet-bulb columns came from a weather chain the errata downgraded wholesale, and the chapter retains the numbers on display, annotated as a wrong chain kept for traceability, so that downstream documents can still recognise what they cited. Case codes survived the downgrade and the values did not, which is why the pass criterion still reads as a code and not as a temperature.
Both halves of the rule are therefore unusable today: the record cannot say what the outdoor air was, and the design condition it would be compared against has no number. The gate that would catch a season-limited record operates on a flag nobody is able to set.
The acceptance parameter file is the object the commissioning authority reviews, and each test record inherits its rows, so an ambient row is a condition on that review and not on any test. Unless it is in the file when the commissioning authority reads it, no execution downstream of that review can be marked season-limited by anybody.
Season validity is a conditional field and not an unconditional one, with its trigger written into the note beside it, so a party has to decide that the trigger applies to a given execution before the field can be filled at all. The index assigns that decision to nobody, and the responsibility matrix that would assign it is published as a proposal no party has accepted.
Limits and open items
Confirmed: a winter measurement does not constitute evidence of summer capability; a record that fails the season-validity field is marked season-limited and may not be counted at full value. [FACT]
Register figures, not a campaign: the 0.50 condition-limited score against 1.00; thirty cases in sixteen columns; 151 acceptance rows using 62 names and 20 units; two unconfirmed thresholds on the heat-rejection failure test. Every case is not executed. The closed-set filename does not mean the tests are closed. [TARGET]
Open: an ambient column; a party named to apply the season trigger; a summer design value with site validity; an approved criterion on the approach temperature and the fan ramp. Nothing here has been run. Nothing is a pass. [HOLD]
Ask Who Marks a January Run as Season-Limited
The useful test is not whether winter testing is allowed. Name the person who would mark a January run season-limited. If the matrix has no name, the gate that would catch it has nobody to arm it.
© 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., “A Winter Power-Failure Test Is Not Summer Rejection Evidence,” https://www.kkdatasvc.com/lab/rfq-vendor-review-and-commissioning/a-winter-power-failure-test-is-not-summer-rejection-evidence/.
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.