Define The Boundary
Define the target zone, sensor height, sampling, fan command, speed cap, enable schedule and fault behavior. Keep sensors away from direct heaters, doors, diffusers and the fan's local jet.
Sensors Should Change A Decision
A sensor is useful only when its location, threshold, control action and stop condition are clear to the people who operate the building.
Direct Answer
A sensor is useful only when its location, threshold, control action and stop condition are clear to the people who operate the building.
Define the target zone, sensor height, sampling, fan command, speed cap, enable schedule and fault behavior. Keep sensors away from direct heaters, doors, diffusers and the fan's local jet.
A percentage command is not a universal air speed. Controller scaling, fan diameter, mounting height, direction and room obstructions change the result; commission with occupied-zone observations. Do not let a sensor quietly mask a failed fan or an open dock door. Alarm, manual override and trend data should make the control sequence diagnosable.
Engineering scope and sources reviewed 6 October 2026 · Project conditions still govern final selection
Decision Framework
Keep the recommendation tied to a field decision and a measurable boundary.
Define the target zone, sensor height, sampling, fan command, speed cap, enable schedule and fault behavior. Keep sensors away from direct heaters, doors, diffusers and the fan's local jet.
A percentage command is not a universal air speed. Controller scaling, fan diameter, mounting height, direction and room obstructions change the result; commission with occupied-zone observations.
Do not let a sensor quietly mask a failed fan or an open dock door. Alarm, manual override and trend data should make the control sequence diagnosable.
Record the assumptions, test condition, responsible reviewer and stop criteria so a later change does not erase the original decision.
Field Inputs
Use one row for every assumption that can change the answer.
| Record | What to capture | Why it matters |
|---|---|---|
| Design input | Document the measured or specified condition | A generic label does not define duty |
| Physical path | Check inlet, fan, outlet, supports and access | Local geometry can dominate the result |
| Control condition | Record speed, schedule, interlocks and alarms | The fan may not run at one fixed point |
| Verification | Measure airflow, pressure or the relevant acceptance signal | Running is not proof of performance |
| Change trigger | Define what requires a new review | Chemistry, layout and duty can change |
Boundary: The values and limits are project-specific. Confirm the exact equipment instructions, standards and responsible engineer before release.
Practical Sequence
Connected Decisions
These links continue the same project workflow rather than sending the reader to loosely related content.
Start with required airflow, pressure and the actual air path before picking a series.
Use a repeatable field measurement when a symptom could be caused by the system rather than the fan.
Short elbows, transitions, dampers and discharge restrictions can change the operating point.
Replacement air and pressure balance belong in the same design conversation as exhaust.
Questions Buyers Actually Ask
Define the target zone, sensor height, sampling, fan command, speed cap, enable schedule and fault behavior. Keep sensors away from direct heaters, doors, diffusers and the fan's local jet. The input should be written down before a model or setting is treated as final.
No. Catalog values are screening evidence. Verify the actual operating condition, measurement method and system configuration before accepting performance.
Send the duty, air or process condition, layout, pressure assumptions, controls, power, environment, photos and any baseline measurements.
No. The correct value depends on the exact fan, building, air path, controls, environment and acceptance requirement.
Review it after a change in process, contaminant, temperature, layout, filter condition, duty, control sequence or observed performance.
Use a sensible sampling location, stable control bands, a minimum run time and a defined speed limit. Tune the response against occupied-zone measurements, and make the fail-safe state explicit before enabling automatic control.
Source Boundary
Sources define methods and safety boundaries. They do not certify a proposed AirMoveX model or replace the adopted code, OEM instructions or a qualified project designer.
AMCA International
AMCA separates fan performance, system effects, sound and application conditions; use the applicable publication and test basis for a project decision.
Open sourceU.S. Department of Energy
DOE guidance supports measured operating data, controls and whole-system comparisons rather than unsupported universal savings claims.
Open sourceOSHA
Safe access, guarding, energy control and competent-person requirements remain site-specific and apply before field work.
Open sourceProject Review
Share the building or process objective, airflow and pressure basis, air condition, layout, controls, power, access and existing measurements. AirMoveX can prepare a shortlist while keeping the assumptions visible.
Start With The Space
Share the dimensions, installation height, available power and operating problem. We will prepare a practical starting configuration.