Spec vs. Standard: Which Tolerance Governs?
The air-side specification for a laboratory building states: "Testing, adjusting and balancing shall be performed in accordance with the NEBB Procedural Standards for Testing, Adjusting and Balancing of Environmental Systems. Individual terminal airflow shall be within ±5% of design." Your report shows 74 of 80 terminals inside ±5%. Six exhaust terminals on a fume-hood manifold read 8–9% below design and cannot be raised: the associated exhaust fan VFD is at 60 Hz and the fan is at the end of its curve. The general contractor wants the report issued with a note that the NEBB tolerance is ±10% and the system therefore "passes." Separately, you notice the calibration sticker on your micromanometer expired six weeks ago, partway through the project.
1. Which tolerance governs, and how do you handle the six terminals?
Read the worked answer
The project specification governs. A published procedural standard supplies a default tolerance where the contract documents are silent; it never overrides a tighter contractual requirement. Here the contract says ±5%, so ±5% is the acceptance criterion, full stop.
For the six terminals at 8–9% low:
- Report the measured values as found. They are out of tolerance.
- List them individually in the deficiency log with the measured value, design value, and the reason they could not be corrected (drive at maximum, fan at curve end).
- Do not relabel them as passing with a note citing ±10%. A note cannot change a contract requirement.
- Before you finalize, re-verify the reading itself - instrument condition, the test method, and duct leakage on the exhaust side - so the deficiency is defensible.
- Escalate by RFI: the engineer must decide whether to accept, derate the hoods, or approve a fan/drive change. That is a design decision with code implications on a lab exhaust system.
2. The micromanometer calibration lapsed mid-project. What is the correct response, and what does it do to your data?
Read the worked answer
Instrument calibration and traceability to a recognized standard is a basic procedural requirement, and it is also what makes your report defensible. Once the sticker lapses, the instrument's readings are unverified, not automatically wrong.
Response:
- Stop using the instrument for acceptance data and have it recalibrated/verified immediately.
- Identify exactly which readings were taken during the lapsed window (from your field notes and daily logs) and quantify the exposure - by system, by date range.
- Retest the affected readings that carry acceptance weight. On a lab project, that means all terminals used for the final report, not a sample, unless the engineer agrees in writing to a reduced retest scope.
- Record the lapse, the recalibration date, the certificate, and the retest in the report so the trail is complete.
If a new calibration shows a shift, you must also assess whether any earlier reported values are in question and notify the owner's representative in writing. Quietly replacing the numbers is not acceptable, and neither is issuing acceptance data from an out-of-calibration instrument.
3. Draft the substance of what the GC should be told, in technical terms.
Read the worked answer
- The specification's ±5% is the acceptance criterion; the NEBB ±10% default does not apply where the contract is more stringent. The report will show actual measured values, not a pass/fail referendum on the standard.
- 74 of 80 terminals comply. Six exhaust terminals on the fume-hood manifold are 8–9% below design and cannot be corrected by balancing; the drive is at maximum frequency and the fan is at the end of its curve.
- These six are reported as deficiencies with measured vs. design values and the physical cause. Recommended resolution is an engineering decision (fan/drive change, hood derating, or written acceptance of the deviation).
- Acceptance data taken while the micromanometer calibration was expired has been retested following recalibration; the certificate and retest results are included in the report appendix.
- The report will be issued as a complete document with a deficiency list and a retest scope. It will not be issued "with a note" that converts a deficiency into compliance.