IMC 512.4 requires a rational analysis that proves the chosen smoke control method will work under real building forces.
Plain English: Plain-English Highlights
512.4 analysis required
Your smoke control system needs a documented engineering analysis that supports the system type, how it operates, what systems support it (HVAC, power, controls), and how it will be built.
512.4.1 stack effect
Design for worst-case normal and reverse stack effect using altitude/elevation, weather history, and indoor temperatures.
512.4.2 fire temperature effects
Account for buoyancy and expansion from the design fire (ties to 512.9).
512.4.3 wind effects
Include wind effects consistent with IBC provisions so facade pressures don't cause reversals.
512.4.4 HVAC interactions
Model how HVAC modes affect smoke and fire transport across all system permutations and shutdown modes.
512.4.5 climate impacts
Consider low temperature impacts and locate inlets/outlets to avoid snow/ice blockage.
512.4.6 duration of operation
Active/engineered smoke control must run after detection for at least 20 minutes OR 1.5 × calculated egress time, whichever is greater.
512.4.7 system interaction
If multiple smoke control systems exist, analyze interactions across scenarios so systems don't fight each other.
On Plans: Why it matters
Most smoke control failures aren't "bad fans." They're unmodeled forces (stack/wind/fire buoyancy) and conflicting sequences that reverse flow paths or collapse pressure targets.
Code Path: Where to show it
Smoke Control Report: assumptions, scenarios, and results for 512.4.1-512.4.7.
M-001 / life safety sheets: basis of design (method, zones, targets, duration) + reference to the report.
Controls diagram: smoke mode sequences and HVAC interaction logic by scenario.
Check: Do
Write the analysis around worst-case scenarios (stack + wind + fire) and document each assumption.
Review Risk: Don't
Don't assume "fans win" without pressure/flow verification under stack and wind.
Don't let separate smoke control subsystems run independently without an interaction check.
Field Tip: Field tip
Add a "SMOKE MODE WORST CASE SCENARIO TABLE" to the set: it shows the Controls sequence, fire location, doors assumed open, target ΔP or airflow method, commanded fans/dampers, HVAC shutdowns, and required runtime.
Comment "IMC512" for a paste-ready scenario table template.
Masterbuild QA Lens
Exhaust systems need a source-to-discharge story. Identify what is being captured, how it is captured, how it is routed, where it terminates, and what interlocks or separations protect the building.
Drawing / Submittal Check
Verify source classification, hood or pickup point, duct material, route, cleanouts or access, fan selection, discharge location, make-up air, controls, and required coordination with fire protection or alarms.
Common Review Risk
The expensive miss is treating all exhaust the same. Grease, dryer, dust, hazardous, smoke control, battery, and specialty exhaust systems carry different proof requirements.
When To Escalate
Escalate when exhaust involves grease, hazardous materials, combustible dust, battery charging, smoke control, rated shafts, energy recovery, or any discharge that can re-enter the building.
Load Assumption Check
For load-driven decisions, make the assumptions visible: weather basis, orientation, envelope, occupancy, ventilation, equipment gains, and any existing-building limitations that affect capacity.