Comparing FFU bids becomes difficult once each supplier presents airflow, pressure, sound, and power figures without stating the conditions behind them. A buyer who ranks bids on the numbers alone risks selecting a unit that performs differently once installed at the project’s actual duty point. The question is not which bid shows the strongest figure, but whether the figures being compared were even measured the same way.

Identify what an IEST-RP-CC036 label does and does not prove

A citation to IEST-RP-CC036 tells the reader that a supplier’s FFU performance figures fall within a recognized testing scope for fan filter units — covering airflow, sound, power, and available static pressure. It does not, by itself, tell the reader what conditions were used to generate those figures, and it does not establish that two bids citing the same practice are describing comparable results. The recommended practice defines the scope of what gets tested; it does not fix a single universal value that every FFU must meet regardless of configuration or duty.

This distinction matters because a bid can reference IEST-RP-CC036 accurately while still leaving the buyer unable to compare it against another bid. Where a supplier states the standard by name but omits the test conditions attached to each figure, the citation confirms only that a recognized testing scope was applied — not that the resulting airflow, pressure, sound, or power values were derived under conditions matching the project or matching a competing bid. The buyer’s task is to look past the label and ask what stands behind it.

Where the underlying test conditions are stated alongside the figures, the buyer can begin checking whether those conditions correspond to how the unit will actually operate in the project — the duty point, the unit configuration, and the installation context. Where conditions are absent, the label functions as a reference to a testing framework rather than as evidence that the number is usable for comparison. This is the first filter a buyer should apply to any bid: does the citation come with enough detail to interpret the number, or does it stand alone as an assertion of compliance with a testing scope.

Full procedural detail — how the practice defines its test conditions and what its acceptance boundaries look like — sits behind the paywalled standard itself. What a buyer can work with at the bid-review stage is the scope summary: that IEST-RP-CC036 governs FFU performance testing across these specific parameters, and that any bid invoking it should be expected to disclose the conditions under which its figures were produced.

Normalize airflow and available-static-pressure conditions across bids

Airflow and available static pressure are related in a way that makes either figure meaningless on its own. An FFU’s airflow output depends on the resistance it works against — the available static pressure — because the fan curve for any unit describes a relationship between the two, not a fixed airflow value. A supplier can report a favorable airflow figure at a low resistance condition, and a different supplier can report a lower airflow figure at a higher resistance condition that more closely matches the project’s real duct or filter-loading environment. Comparing these two figures directly, without accounting for the pressure condition each was measured at, produces a ranking that has no connection to how the units will perform once installed.

This is why the buyer’s task is not to compare airflow values or pressure values in isolation but to identify the operating point — the combination of airflow and available static pressure — that each bid’s figures describe. Where a bid states a nominal rating without reference to project duty, that figure describes the unit’s capability under generic or catalog conditions, not necessarily under the resistance the unit will face once it is fitted into the project’s filter, duct, and terminal configuration. Where a bid states a result derived at or near the actual project duty, that figure is far more directly usable for comparison, because it reflects the same demand condition the buyer is trying to satisfy.

The consequence for bid ranking is direct: a bid showing a stronger airflow number at an unstated or lower-resistance condition may not remain stronger once normalized to the project’s actual operating point. A buyer who selects on the basis of nominal ratings without checking whether they were derived at comparable pressure conditions may be ranking suppliers by test convenience rather than by fitness for the project. Before any ranking is finalized, the buyer needs each bid’s airflow and available static pressure tied to a stated unit configuration and test condition, so that the comparison reflects one operating point rather than several different ones dressed as equivalent numbers. The reasoning developed in How to Write an FFU RFQ That Lets Suppliers Compare the Same Operating Point addresses how to request this alignment before bids are even submitted.

Align sound and power data with the proposed FFU configuration

Sound and power figures share the same dependency problem as airflow and pressure: neither value means anything detached from the configuration and condition under which it was measured. An FFU’s power draw changes with the airflow it is driving and the resistance it works against, because the fan has to do more work to move the same air through a higher-resistance filter or duct path. Sound output changes for related reasons — a fan running harder to overcome higher resistance, or to deliver higher airflow, generates a different acoustic result than the same unit running at a lower demand point. A power or sound figure quoted without its associated airflow and pressure condition describes a data point that cannot be projected onto a different operating point without distortion.

This creates a specific risk in bid comparison: a supplier’s sound or power figure that appears favorable in isolation may correspond to a lower-demand condition than the project actually requires, while a less favorable figure from another supplier may already reflect the project’s real duty. Without the configuration and test condition stated alongside each result, the buyer cannot tell which situation applies. The unit configuration itself matters here too — filter media, housing arrangement, and control type can all shift how a given airflow and pressure translate into sound and power, so a bid’s figures are only informative when tied to the specific configuration being proposed for the project rather than to a generic model designation.

Where the buyer requires the proposed configuration’s sound and power figures to be reported at the same operating point already established for airflow and pressure, the comparison becomes internally consistent — every parameter for every bid refers to one duty condition. Where sound or power figures are reported at a different or unstated condition than the airflow and pressure figures in the same bid, the bid is internally inconsistent, and no ranking based on it can be trusted until that inconsistency is resolved. The buyer’s task in this section is to confirm that all four figures — airflow, pressure, sound, and power — describe the same unit, in the same configuration, at the same condition, rather than treating them as independent claims that can each be optimized separately by the supplier presenting them.

Separate factory performance results from installed cleanroom acceptance

Factory FFU test data and installed cleanroom acceptance evidence answer different questions, and treating them as interchangeable creates a gap the buyer may not discover until the room is already built. Factory data describes how a specific unit, in a specific configuration, performed under stated test conditions before it left the manufacturing environment. It says nothing directly about how that unit will behave once mounted in a ceiling grid, integrated with adjacent units, and operating inside a room with its own layout, obstruction pattern, and airflow interactions with other equipment.

Installed cleanroom acceptance depends on the completed room as a system — the arrangement of units relative to each other, the room’s return or exhaust path, the presence of equipment or fixtures that affect airflow distribution, and the acceptance plan the project has approved for verifying room performance. Two rooms built with FFUs carrying identical factory data can produce different acceptance outcomes if their layouts, adjacent equipment, or approved acceptance criteria differ. This is a structural distinction, not a matter of one type of evidence being better than the other: factory data qualifies the unit; room qualification evidence qualifies the room.

The consequence for the buyer during bid comparison is that strong factory data narrows the field of units worth considering but does not substitute for the room-level verification the project’s acceptance plan will eventually require. A bid that presents only factory results has not yet addressed how the buyer’s completed room will be qualified, and a bid that references installed performance without identifying the specific room and acceptance plan it draws from cannot be used to judge a different project’s outcome. Where the buyer’s evaluation conflates these two evidence types — for instance treating a strong factory airflow result as if it already satisfies the room’s acceptance requirement — the project risks discovering a mismatch only after installation, when correcting it is far more disruptive than catching it at the bid stage. Keeping the two evidence types distinct at review time is what allows the buyer to use factory data for its proper purpose: comparing candidate units, not predicting room outcomes.

Record deviations, missing conditions, and supplier clarifications

Once bids have been checked against the operating point and evidence-scope distinctions already established, what typically remains is a set of gaps — figures without stated conditions, configurations that are not clearly tied to the numbers presented, or evidence categories that have been blended together in ways that make the bid hard to evaluate on its own terms. Recording these gaps systematically, rather than resolving them informally as they are noticed, gives the buyer a basis for asking each supplier the same set of clarifying questions and for judging whether a supplier’s response actually closes the gap or simply restates the original figure.

The reasoning behind this step follows from everything already established: a figure is only comparable when its test condition is known, an operating point is only comparable when airflow and pressure are considered together, sound and power are only interpretable when tied to the same configuration and condition as the rest of the bid, and factory data cannot stand in for installed acceptance evidence. Each of these checks can fail independently, and a bid can pass one check while failing another. A structured record — noting exactly which items are missing their conditions, which configurations are ambiguous, and which suppliers have not yet distinguished factory data from room-level evidence — turns an informal sense that “something is unclear” into a specific, answerable request.

Where a supplier’s clarification supplies the missing condition or configuration detail, the buyer can fold the revised figure back into the comparison and reassess the ranking. Where a supplier cannot supply it, or supplies a condition that still does not match the project’s duty point, the buyer has learned something equally useful: that the original figure was not, in fact, comparable to the other bids, and should be weighted accordingly rather than left in the ranking at face value. This record also becomes the reference point later, when the project moves from bid comparison into the configuration and quotation review stage — the same gaps identified here are the details a project team supplies when engaging with a manufacturer’s configuration process, since the operating point, configuration, and evidence scope the buyer has already clarified are what that review depends on to produce a comparable quotation.

Select the bid only after the operating point and evidence scope match

Selection follows once the operating point across bids has been normalized and the evidence scope for each bid has been separated into factory results and installed acceptance evidence. A bid earns consideration for ranking only after its airflow, available static pressure, sound, and power figures are confirmed to describe the same configuration at the same condition as the figures being compared against it — not before. Ranking bids on raw figures before this normalization is complete produces a comparison that reflects differences in test conditions rather than differences in unit performance.

Where two bids reach this stage with figures that genuinely correspond to the same operating point, the remaining basis for comparison is whichever figures the project has defined as decision-relevant — the airflow and pressure combination that matches the project’s duty, and the sound or power result at that same combination. Where one bid still carries unresolved gaps after the clarification step, that bid is not yet ready for ranking regardless of how favorable its stated figures appear, because a stronger number tied to an unconfirmed or mismatched condition does not carry to the project’s actual operating point.

This is also the point where the buyer’s own project information becomes relevant to what happens next. The duty point, configuration, and acceptance-plan details that were used to normalize and clarify the bids are the same details a manufacturer needs in order to configure a specific fan filter unit for the project and produce a quotation grounded in the project’s actual requirements rather than in catalog defaults. A conditional distinction is worth holding onto here: where the project’s operating point sits close to a unit’s nominal rating, factory data alone may give the buyer enough confidence to proceed toward configuration discussions; where the operating point departs materially from nominal conditions, the buyer has more reason to press for project-duty-specific figures, and for clarity on how installed acceptance will be verified, before treating any bid as settled. The selection decision, in either case, rests on whether the operating point and the evidence scope have been matched — not on which bid presented the most favorable number first.

Frequently Asked Questions

Q: Is an IEST-RP-CC036 reference enough to treat an FFU bid as comparable?
A: No. Use the reference to identify the testing scope, then check whether the bid states airflow, available static pressure, sound, power, unit configuration, and test conditions at an operating point relevant to the project.

Q: Should the lowest sound or power value automatically rank first?
A: No. Rank those values only after confirming they apply to the same airflow, available static pressure, proposed unit configuration, and test conditions; otherwise, the apparent advantage may come from a different operating point.

Q: How should a buyer handle nominal ratings that are not tied to project duty?
A: Record them as unresolved rather than equivalent performance. Ask the bidder to identify the operating point and configuration behind each rating, then decide whether that evidence covers the proposed project duty.

Q: Can factory FFU test data serve as installed cleanroom acceptance evidence?
A: No. Use factory data to compare the tested unit and conditions, while evaluating the installed cleanroom separately under its actual layout and approved acceptance plan.

Q: What should happen when a bid still lacks comparable test conditions at selection time?
A: Keep the gap visible as a bid deviation and avoid treating the result as like-for-like. Resolve which condition is missing or different, whether it affects the project operating point, and what evidence will close the clarification before selection.